I wrote:
I will try to rework this patch
While doing so I discovered an old bug which happens with current code
as well as with Linux 2.6.16.x and 2.6.15.x, maybe also on older kernels:
When "modprobe ohci1394" is followed shortly by "modprobe -r ohci1394"
(say, 1 second after the previous modprobe finished), one of the
following may happen:
- kernel panic due to exception in interrupt
(happened on 2.6.15.x preempt uniprocessor)
or
- modprobe -r hangs in D state, as does knodemgrd_0
(happened on 2.6.16.x preempt SMP on a uniprocessor machine).
I have two FireWirew host adapters installed. The knodemgrd_1 slept
interruptibly (S state) while the other slept uninterruptibly (D state)
right after modprobe -r was issued. This happens with or without other
nodes attached to the FireWire ports. Host adapters are based on a TI
1394b chip (host 0) and on a VIA 1394a chip (host 1).
"All's right with the world" if a longer pause is put between modprobe
and modprobe -r, say 4 seconds.
(I will add a bugzilla entry and try to resolve this eventually...)
--
Stefan Richter
-=====-=-==- -==- =--=-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
