I too have had problems exactly like you describe. RedHat 7.1. I start
getting oopes from the printer module and the system will not shut down.
Once rebooted the primary file system is totally hosed. fsck could not
make heads or tails out of it. This has happened twice. I have not had
time to risk killing my system again but it appears to be either related
to postscript printing or the lm_sensors modules. Do you by chance use
> My hardware:
> Abit BP6 motherboard, 2 x Celeron, 512 MB RAM, IBM DJNA-371350
> disk on the classic controller, IBM IC35L040AVER07-0 disk on the
> HPT 366 controller, root USB hub on the 440BX chipset,
> "noname" USB hub, HP PSC 750 printer/scanner/copier connected
> to the hub, no other switched-on USB devices at the time
> of my experiments (otherwise I have Compaq iPAQ PocketPC
> and HP 315 digital camera; the camera works quite OK under
> Linux with usb-storage).
FIC AD11 motherboard.
AMD 1.4 Athlon
40GB Western Digital
NVIDIA GeForce 2 (XFree driver not NVIDIA binary ones)
HP 648C USB printer
The only other USB device I use is a Logitech mouse.
> Unfortunately the problems are not 100% reproducible - sometimes
> it works, sometimes it does not. Some datapoints collected so far:
I am pretty sure I can make it happen again but I don't have the time to
reinstall my system right now...
> - The most frequent symptom is a lockup - I send something
> to the printer, it prints a few lines and then the machine
> locks up - no mouse reaction etc. SysRq does work, but
> despite sync - unmount - boot sequence I get some fs problems
> on the subsequent reboot.
Although I do not get lockups the printer symptoms are the same. Partial
output then tons of oopes spilled to the console.
> - I have problems with both Mandrake's kernel (heavily patched
> 2.4.8) and vanilla 2.4.12
Vanilla 2.4.10. I have not had this happen on 2.4.12 but I have really
been avoiding anything I thought might cause this again.
> - It does not matter whether I use uhci or usb-uhci
I use usb-uhci
> - The worst crash had another symptoms shortly before - a few Oopsen
> in processes completely unrelated to printing (unfortunately
> the Oops data were lost after the fs exitus :-() and messages
> stating that some processes cannot be started.
In my case whatever programs were running appears to continue to run
fine. Starting new processes did not work.
> - I got a corruption of the files that were surely _not_
> opened for writing.
Here too. Many system libs were corrupted. When fsck tried to repair the
file system it spewed all kinds of errors about libs.
> - At least one another person on a local mailing list got
> very similar problem - loaded USB modules, got a lockup and lost
> sd_mod and /usr/bin/kdeinit - this time not with a printer, but
> using usb-storage (which needs sd_mod)
I do not use usb-storage.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/