On Wed, 28 Feb 2001, Andrew Morton wrote:
> This untested patch should fix the scheduling-in-interrupt
> thing.
>
>
> --- kernel/sys.c.orig Thu Mar 1 10:06:14 2001
> +++ kernel/sys.c Thu Mar 1 10:07:43 2001
> @@ -330,6 +330,12 @@
Yes, this fixed the oops. Now it's possible to ctrl-alt-d
> Run it through ksymoops and I might be able to guess what went wrong.
>
> In theory however i2o is a standard and all i2o works alike. In
> practice i2o
> is a pseudo standard and nobody seems to interpret the spec the
> same way, the
> implementations all tend to have bugs and the hardware some
> > Kernel panic: Aiee, killing interrupt handler !
> > In interrupt handler - not syncing
>
> Run it through ksymoops and I might be able to guess what went wrong.
>
> In theory however i2o is a standard and all i2o works alike. In
> practice i2o
> is a pseudo standard and nobody seems to interpr
Can somebody comment on usability of current i2o drivers
from 2.4.2 kernel with Promise SuperTrak100 controller?
There seems to be some interrupt issue causing kernel
to panic when i2o_block is loaded. Transcript as follows:
Scheduling in interrupt
kernel BUG at sched.c:707!
invalid operand:
4 matches
Mail list logo
