[EMAIL PROTECTED] said:
The sysrq-e output is probably just standard ext3 journalling unrelated to
the problem... what does dmesg say? lspci? What's your hardware setup?
dmesg ; smartd ; dmesg yields no new entries in dmesg. It seems on disk
accesses are dead. it still routes packets
[EMAIL PROTECTED] said:
So that's using the old IDE drivers. And the network and USB are sharing
IRQ#11 with each other.
If you are going to be using newer kernels like this (2.6.23+), then you
might consider shifting those drives over to libata drivers.
This involves a little bit of work
[EMAIL PROTECTED] said:
the comment on the very top of drivers/ata says:
tristate Serial ATA (prod) and Parallel ATA (experimental) drivers
That's the one I was referring to.
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
[EMAIL PROTECTED] said:
But at this point libata is working much better than the old IDE stuff, and
it really is worth moving things over if you can.
Ok, I'll take a stab at that tomorrow. Two things...
Having switched to ata_piix i can confirm that smartd doesn't hand the system
anymore.
[EMAIL PROTECTED] said:
Could you try bisecting it down to the guilty commit using git-bisect?
[ the old stuff got few hundred commits in 2.6.25 ]
Thanks, Bart
Will do. It'll take a while though. Not a fast machine and used by the
household...
/A
-
To unsubscribe from this list: send the
[EMAIL PROTECTED] said:
Could you try bisecting it down to the guilty commit using git-bisect?
[ the old stuff got few hundred commits in 2.6.25 ]
Thanks, Bart
Ok, I got this:
852738f39258deafb3d89c187cb1a4050820d555 is first bad commit
commit 852738f39258deafb3d89c187cb1a4050820d555
