EHCI Kernel panic on current BK 2.5

EHCI Kernel panic on current BK 2.5

Post by chr.. » Wed, 27 Nov 2002 21:50:11



I try to setup the usb 2.0 hard disk on my desktop in 2.5.
It works great with uhci driver. (2.4 and 2.5).

When I try modprobe ehci-hcd in 2.5. Kernel panic. It seems
that kernel OOPS inside the panic handle code again.

I can't get the full OOPS from the serial console either.

I am typing it here. I can only see the last screen.
It might have some typo and emotion.

EIP is at scheduler_tick+0x92/0x360
eax: 00000000 ebx: 00000000 ecx: 00000001  edx: 00000003
esi: dd5e3000 edi: 00000001 ebp: dd5b9ed0  esp: dd5b9ec0
ds: 0068   es: 0068  ss:068
Process (pid:26, threadinfo=dd5b8000 task=dd5e3000)
Stack: 0000002 000000 0000001 000000 dd5b9f80
....
Call Trace:
[<c011de1a>] update_process_times+0x2a/0x30
[<c011dffa>] do_timer+0x2a/0xf0
[<c010de22>] timer_interrupt+0x22/0x130
             __call_console_drivers+0x46/0x60
             handle_IRQ_event+0x2a/0x60
             do_IRQ+0xa0/0x130
             common_interrupt+0x18/0x20
             xfrm4_dst_destory+0x8/0x20
             xfrm4_dst_detrory+0x8/0x20
             die+0x5c/0x80
             do_page_fault+0x14e/0x467

Code: 0f ab 50 08 8d 65 f4 5b 5e 5f 5d c3 89 f6 b8 00 e0 ff ff 21
 <0>Kerenl panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing

Here is another one without the serial console:

Call Trace:
            update_process_times+0x2a/0x30
            do_timer+0x2a/0xf0
            timer_interrupt_0x22/0xff
            _call_console_drivers+0x46/0x60
            handle_IRQ_event+0x2a/0x60
            do_IRQ+0xa0/0x130
            do_page_fault+0x43/0x467
            do_page_fault_0x43/0x467
            common_interupt+0x18/0x20
            do_page_fault+0x43/0x467
            do_page_fault+0x43/0x467
            xfrm4_dst_destroy+0x8/0x30
            xfrm4_dst_destroy+0x8/0x30
            die+0x5c/0x80
            do_page_fault+0x14e/0x467
            scrup+0x100/0x110
            vgacon_consor+0x168/0x1f0

Code: <same as above>

PS. I notice that some line are duplicated. That is the way
it is on the screen.

-
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/

 
 
 

EHCI Kernel panic on current BK 2.5

Post by Zwane Mwaikamb » Wed, 27 Nov 2002 22:50:06



Quote:> I try to setup the usb 2.0 hard disk on my desktop in 2.5.
> It works great with uhci driver. (2.4 and 2.5).

> When I try modprobe ehci-hcd in 2.5. Kernel panic. It seems
> that kernel OOPS inside the panic handle code again.

> I can't get the full OOPS from the serial console either.

> I am typing it here. I can only see the last screen.
> It might have some typo and emotion.

> EIP is at scheduler_tick+0x92/0x360
> eax: 00000000 ebx: 00000000 ecx: 00000001  edx: 00000003
> esi: dd5e3000 edi: 00000001 ebp: dd5b9ed0  esp: dd5b9ec0
> ds: 0068   es: 0068  ss:068
> Process (pid:26, threadinfo=dd5b8000 task=dd5e3000)
> Stack: 0000002 000000 0000001 000000 dd5b9f80

Possibly it could be this?

/* Task might have expired already, but not scheduled off yet */
if (p->array != rq->active) {
        set_tsk_need_resched(p); <-- [1]
        return;

Quote:}

static inline void set_ti_thread_flag(struct thread_info *ti, int flag)
{
        set_bit(flag,&ti->flags); <-- [2]

Quote:}

static __inline__ void set_bit(int nr, volatile unsigned long * addr)
{
        __asm__ __volatile__( LOCK_PREFIX
                "btsl %1,%0"
                :"=m" (ADDR)
                :"Ir" (nr));

Quote:}

Code;  00000000 Before first symbol
00000000 <_EIP>:
Code;  00000000 Before first symbol
   0:   0f ab 50 08               bts    %edx,0x8(%eax)
Code;  00000004 Before first symbol
   4:   8d 65 f4                  lea    0xfffffff4(%ebp),%esp

So addr was NULL it seems, perhaps we're not supposed to be in here in the
first place ?

--
function.linuxpower.ca
-
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/

 
 
 

1. timer hang with current 2.5 BK

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/

2. Observations and reservations over BeOS compared to Linux

3. fix 3c59x for current 2.5-bk

4. Applets in "Kicker"

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

6. scandir problem... (compiling with a reentrant compiler....)

7. 2.5 bk current ohci1394 breakage

8. CDR and kernel

9. Compile fix for current 2.5 BK.

10. DAC960 breakage, 2.5 bk current

11. compile problem in current BK 2.5

12. AIC7xxx error messages with linux 2.5 BK-CURRENT

13. 2.5-bk-current drivers/pnp/interface.c