Another bug in 2.5.47, this time with USBFS. When attempting to read
/proc/bus/usb/drivers, the program reading the "file" terminates with
a segmentation fault:
/proc/bus/pci:58$ cat devices
Segmentation fault
$lspci
Segmentation fault
-Joseph
--
Joseph===============================================trelane@digitasaru.net
"[The question of] copy protection has long been answered, and it's only
a matter of months until more or less all CDs will be published with
copy protection." --"Ihr EMI Team"
http://www.theregister.co.uk/content/54/27960.html
On Fri, Nov 15, 2002 at 11:42:34AM -0600, Joseph Pingenot wrote:
> Another bug in 2.5.47, this time with USBFS. When attempting to read
> /proc/bus/usb/drivers, the program reading the "file" terminates with
> a segmentation fault:
> /proc/bus/pci:58$ cat devices
> Segmentation fault
> $lspci
> Segmentation fault
You are trying to read /proc/bus/pci/* not /proc/bus/usb files. So why
would you think usbfs would have a problem?
Also, a decoded oops report would help out a lot.
thanks,
greg k-h
>From Greg KH on Saturday, 16 November, 2002:
>On Fri, Nov 15, 2002 at 11:42:34AM -0600, Joseph Pingenot wrote:
>> /proc/bus/pci:58$ cat devices
>> Segmentation fault
>You are trying to read /proc/bus/pci/* not /proc/bus/usb files. So why
>would you think usbfs would have a problem?
>Also, a decoded oops report would help out a lot.
heh. I *am* an ass. That is indeed /proc/bus/pci, not /proc/bus/usb.
Ewps. lsusb *does* segv, although the fact that I was in the wrong
directory is intriguing. Maybe I'll get the same problem as I got
with lsusb when trying lspci. Hmm.
To my knowledge, there is no oops data. I'll send more data when I get a
chance to reboot into that kernel.
-Joseph
--
Joseph===============================================trelane@digitasaru.net
"[The question of] copy protection has long been answered, and it's only
a matter of months until more or less all CDs will be published with
copy protection." --"Ihr EMI Team"
http://www.theregister.co.uk/content/54/27960.html