timer hang with current 2.5 BK

timer hang with current 2.5 BK

Post by Duncan Sand » Wed, 26 Mar 2003 13:10:08



If I remove the uhci_hcd or ehci_hcd module, then I
systematically get the following:

(EIP) run_timer_softirq+0xe3/0x400
timer_interrupt+0x1a3/0x3f0
do_softirq+0xa1/0xb0
do_IRQ+0x23f/0x380
common_interrupt+0x18/0x20
code: 89 50 04 89 02 C7 41

kernel/timer.c:302: spin_lock (kernel/timer.c:c02f7b00) already
locked by kernel/timer.c/398.

killing interrupt handler etc

Presumably this is related to the stall_timer.
This has been happening for ?one week?, and
still occurs with current BK.  Occurs with and
without preempt (UP).

Any ideas?

Thanks,

Duncan.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

timer hang with current 2.5 BK

Post by David Brownel » Wed, 26 Mar 2003 18:10:12



> If I remove the uhci_hcd or ehci_hcd module, then I
> systematically get the following:

> (EIP) run_timer_softirq+0xe3/0x400
> timer_interrupt+0x1a3/0x3f0
> do_softirq+0xa1/0xb0
> do_IRQ+0x23f/0x380
> common_interrupt+0x18/0x20
> code: 89 50 04 89 02 C7 41

> kernel/timer.c:302: spin_lock (kernel/timer.c:c02f7b00) already
> locked by kernel/timer.c/398.

> killing interrupt handler etc

> Presumably this is related to the stall_timer.
> This has been happening for ?one week?, and
> still occurs with current BK.  Occurs with and
> without preempt (UP).

> Any ideas?

I'm not getting it any more, but then I'm also running with
this patch too ... the current source prevents drivers from
properly disconnect()ing, which means all kinds of state
doesn't get cleaned up.

What usually gets me lately is that the whole system locks
up when I remove certain modules.  SysRq behaves but little
else (no console).  The common behavior seems to be that
the call_usermode_helper() logic is waiting forever; such
as waiting for network interface "remove" events to finish.

- Dave

[ p5.patch < 1K ]
--- 1.15/drivers/usb/core/urb.c Thu Mar 13 10:45:40 2003

        /* FIXME
         * We should not care about the state here, but the host controllers
         * die a horrible death if we unlink a urb for a device that has been
-        * physically removed.
+        * physically removed.  (after driver->disconnect returns...)
         */
        if (urb &&
            urb->dev &&
-           (urb->dev->state >= USB_STATE_DEFAULT) &&
+           // (urb->dev->state >= USB_STATE_DEFAULT) &&
            urb->dev->bus &&
            urb->dev->bus->op)
                return urb->dev->bus->op->unlink_urb(urb);

 
 
 

1. 2.5.xx (BK current) hangs executing rpcinfo

Hallo List,

Debian Linux checks the availibility of NFS v3 by using

# rpcinfo -u localhost nfs 3

Kernel 2.4.18 immediatly returns successful, but current
2.5 BK kernels timeout in the sendto() syscall.

Could someone please verify this ? Is this a known problem ?
Both kernels have v3 server support enabled.

It would be very kind if someone could try the above an send
a reply to me, or tell me why it's not working.

thanks,
Patrick

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Need help with nic ... please

3. Latest 2.5 BK: oops in timer.c

4. Follow-up (WAS cat'ting a binary file blows console)

5. fix 3c59x for current 2.5-bk

6. cut and paste with linux

7. EHCI Kernel panic on current BK 2.5

8. SunFastEthernet

9. 2.5 bk current ohci1394 breakage

10. Compile fix for current 2.5 BK.

11. DAC960 breakage, 2.5 bk current

12. compile problem in current BK 2.5

13. AIC7xxx error messages with linux 2.5 BK-CURRENT