Re: ide_set_handler: timer already active

Gadi Oxman (gadio@netvision.net.il)
Fri, 12 Mar 1999 20:17:11 +0200 (IST)


On Fri, 12 Mar 1999, Mark Lord wrote:

> Geert Uytterhoeven wrote:
>
> > Do you share the interrupts of your IDE interfaces with other devices? I do.
>
> Yes, but only with other PCI devices (all level-triggered).
> Right now I have two IDE interfaces (RAID0) and an EEpro100 sharing IRQ
> 11.
>
> > > The message is is only there "temporarily" anyway,
> > > just to check for bugs seen (but not understood) on other architecture(s).
> >
> > I see the message several times a day. Each of these would have been a full
> > crash in the days before I replaced the call to add_timer() by mod_timer().
> >
> > Strange... Where is the bug????
>
> Must be somewhere in the M68k interrupt layer.
> The ia32 interrupt stuff was also fairly buggy last fall.
>
> Cheers
> --
> mlord@pobox.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/

This error is very strange -- del_timer() is performed on all entry
points to ide_do_request(). Geert, can you log each add_timer() and
del_timer() performed by the IDE driver, and verify that indeed two
add_timer() were called in a raw? We can also try to force an oops
at that place and look at the stack trace for some hints.

Gadi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/