[lkml]   [1999]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ide_set_handler: timer already active
On Fri, 12 Mar 1999, Gadi Oxman wrote:
> 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.
> 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.

I added some printks to the calls that modify the timers (I have only one IDE
chain, so hwgroup->timer is always the same):

'A' -> add_timer()
'D' -> del_timer()
'M' -> mod_timer()

and I catched these:

| DADADADMide_set_handler: timer already active
| Apr 5 12:30:17 cassandra 4>Apr 5 12:30:17 kernel: MDADADADADADADADA

| ADADADADADADADADADADMide_set_handler: timer already active
| Apr 5 12:30:19 cassandra 4>Apr 5 12:30:19 kernel: MDADADMDADADMDA

As you can see, there are two consecutive `M's. At all other places, you have
something like

^ ^
which is OK.

Then I added an `asm("illegal")' to force a stack backtrace:

Illegal instruction in

[<0005f1f0>] 0005f012 t ide_do_request


[<0008eae0>] 0008e799 r ide_hwif_to_major
[<00002700>] 000026d4 T copy_thread
[<000119a8>] 0001196a T make_pages_present
[<0000ffff>] 0000ffd4 T copy_page_range (odd address??)
[<00064c5c>] 00064bcc t write_intr
[<0005f5d2>] 0005f592 t start_next_request
[<00002010>] 00002008 T get_options
[<00064bcc>] 00064bcc t write_intr
[<0005f822>] 0005f76e T ide_intr
[<0002bd16>] 0002bcd2 T amiga_do_irq_list
[<0002c39e>] 0002c32e t cia_handler
[<000032dc>] 000032a2 T process_int
[<000023da>] 000023b0 T inthandler
[<000119a8>] 0001196a T make_pages_present
[<0000232c>] 000022fc T system_call
[<000119a8>] 0001196a T make_pages_present
[<0000215a>] 0000215a t init
[<0000215a>] 0000215a t init

Nothing interesting, I'm afraid.

Since I also get `eth0: Re-entering the interrupt handler.' from the Ariadne
Ethernet driver, I brought the net down, removed the ariadne LKM and even
disconnected the UTP cable to make sure no interrupts would happen from the
Ariadne (Ariadne and IDE share the same interrupt), but I still get
`ide_set_handler: timer already active' messages...



Geert Uytterhoeven
Wavelets, Linux/{m68k~Amiga,PPC~CHRP}
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:51    [W:0.059 / U:2.456 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site