Bug 4247 - Frequent kernel crash BUG at boot/init time
Summary: Frequent kernel crash BUG at boot/init time
Status: REJECTED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-24 05:13 UTC by Rui Nuno Capela
Modified: 2005-03-12 05:41 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.11-rc4
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
Complete dmesg output (14.53 KB, text/plain)
2005-02-24 05:15 UTC, Rui Nuno Capela
Details
Kernel config.gz (8.13 KB, application/x-gzip-compressed)
2005-02-24 05:16 UTC, Rui Nuno Capela
Details

Description Rui Nuno Capela 2005-02-24 05:13:19 UTC
Distribution: Mandrake 10.1 Official
Hardware Environment: Laptop P4@2.533Ghz 512MB 
Software Environment: Ingo Molnar's realtime-preempt patch
Problem Description:  Frequent kernel crash BUG at boot/init time. 

Running 2.6.11-rc4-RT-V0.7.39-02 (PREEMPT_RT=y).

This BUG is happening in some probabilistic fashion, like 1 on each 3
boots, rendering the whole USB subsystem completely unusable as the most
notable consequence.

Taken from dmesg:

BUG: Unable to handle kernel paging request at virtual address 0811eb68
 printing eip:
c0127927
*pde = 1e41d067
*pte = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in: natsemi crc32 ohci1394 ieee1394 loop subfs evdev
ohci_hcd usbcore video thermal processor fan button battery ac
CPU:    0
EIP:    0060:[<c0127927>]    Not tainted VLI
EFLAGS: 00010082   (2.6.11-rc4-RT-V0.7.39-02.0)
EIP is at change_owner+0x1a/0x5a
eax: de65c550   ebx: de65c550   ecx: 0811eb68   edx: df180550
esi: df0c3cc8   edi: df180a48   ebp: df0c3cc8   esp: de59ded0
ds: 007b   es: 007b   ss: 0068   preempt: 00000004
Process IRQ 10 (pid: 1439, threadinfo=de59c000 task=df406000)
Stack: de65c550 df0c3cc8 df03ff70 df180550 c0127b5c de65c550 df0c3cc8
c0127d31
       00000000 df03ff70 00000286 00000000 de59c000 de558000 00010000
00000001
       c01283f5 e00d4400 e00c2cb0 00000001 de55a4d4 e00b0bf6 00000001
00000017
Call Trace:
 [<c0127b5c>] set_new_owner+0x17/0x2b (20)
 [<c0127d31>] __up_mutex+0xa4/0x193 (12)
 [<c01283f5>] up+0x35/0x3d (36)
 [<e00c2cb0>] highlevel_host_reset+0x3b/0x49 [ieee1394] (8)
 [<e00b0bf6>] ohci_irq_handler+0x576/0x713 [ohci1394] (12)
 [<c029ec06>] __sched_text_start+0x5a/0x5d7 (28)
 [<c012d77a>] __do_IRQ+0xca/0x180 (4)
 [<c012d634>] handle_IRQ_event+0x5c/0xc8 (36)
 [<c012dd86>] do_hardirq+0x61/0x112 (48)
 [<c0110dbd>] do_sched_setscheduler+0x73/0xa0 (4)
 [<c012de37>] do_irqd+0x0/0x96 (20)
 [<c012de9d>] do_irqd+0x66/0x96 (4)
 [<c0127018>] kthread+0x94/0xc8 (28)
 [<c0126f84>] kthread+0x0/0xc8 (16)
 [<c0100791>] kernel_thread_helper+0x5/0xb (16)
Code: 8b 6c 24 18 83 c4 1c c3 b8 da ff ff ff c3 90 90 c3 55 39 ca 89 c5 57
89 c8 56 53 74 49 8b 8a f8 04 00 00 8d ba f8 04 00 00 39 cf <8b> 19 74 37
8d b0 f8 04 00 00 eb 08 89 d9 8b 1b 39 cf 74 27 39
 <6>note: IRQ 10[1439] exited with preempt_count 3
BUG: scheduling while atomic: IRQ 10/0x00000003/1439
caller is do_exit+0x1da/0x34d
 [<c029f03a>] __sched_text_start+0x48e/0x5d7 (8)
 [<c01163bb>] exit_notify+0x60b/0x8f4 (24)
 [<c01148fc>] vprintk+0x101/0x142 (24)
 [<c011687e>] do_exit+0x1da/0x34d (32)
 [<c010349f>] do_trap+0x0/0xfe (40)
 [<c010e8fc>] do_page_fault+0x0/0x524 (48)
 [<c010e8fc>] do_page_fault+0x0/0x524 (12)
 [<c010ec42>] do_page_fault+0x346/0x524 (4)
 [<c029f2ea>] preempt_schedule+0x50/0x6b (80)
 [<c010fcdb>] try_to_wake_up+0x104/0x106 (20)
 [<e00b0516>] dma_trm_reset+0x36/0x11e [ohci1394] (24)
 [<c01106ab>] __wake_up_common+0x35/0x55 (16)
 [<c010e8fc>] do_page_fault+0x0/0x524 (60)
 [<c0102d57>] error_code+0x2b/0x30 (8)
 [<c0127927>] change_owner+0x1a/0x5a (44)
 [<c0127b5c>] set_new_owner+0x17/0x2b (28)
 [<c0127d31>] __up_mutex+0xa4/0x193 (12)
 [<c01283f5>] up+0x35/0x3d (36)
 [<e00c2cb0>] highlevel_host_reset+0x3b/0x49 [ieee1394] (8)
 [<e00b0bf6>] ohci_irq_handler+0x576/0x713 [ohci1394] (12)
 [<c029ec06>] __sched_text_start+0x5a/0x5d7 (28)
 [<c012d77a>] __do_IRQ+0xca/0x180 (4)
 [<c012d634>] handle_IRQ_event+0x5c/0xc8 (36)
 [<c012dd86>] do_hardirq+0x61/0x112 (48)
 [<c0110dbd>] do_sched_setscheduler+0x73/0xa0 (4)
 [<c012de37>] do_irqd+0x0/0x96 (20)
 [<c012de9d>] do_irqd+0x66/0x96 (4)
 [<c0127018>] kthread+0x94/0xc8 (28)
 [<c0126f84>] kthread+0x0/0xc8 (16)
 [<c0100791>] kernel_thread_helper+0x5/0xb (16)
prev->state: 2 != TASK_RUNNING??
IRQ 10/1439: BUG in __schedule at kernel/sched.c:3028
 [<c029efa9>] __sched_text_start+0x3fd/0x5d7 (8)
 [<c011687e>] do_exit+0x1da/0x34d (80)
 [<c010349f>] do_trap+0x0/0xfe (40)
 [<c010e8fc>] do_page_fault+0x0/0x524 (48)
 [<c010e8fc>] do_page_fault+0x0/0x524 (12)
 [<c010ec42>] do_page_fault+0x346/0x524 (4)
 [<c029f2ea>] preempt_schedule+0x50/0x6b (80)
 [<c010fcdb>] try_to_wake_up+0x104/0x106 (20)
 [<e00b0516>] dma_trm_reset+0x36/0x11e [ohci1394] (24)
 [<c01106ab>] __wake_up_common+0x35/0x55 (16)
 [<c010e8fc>] do_page_fault+0x0/0x524 (60)
 [<c0102d57>] error_code+0x2b/0x30 (8)
 [<c0127927>] change_owner+0x1a/0x5a (44)
 [<c0127b5c>] set_new_owner+0x17/0x2b (28)
 [<c0127d31>] __up_mutex+0xa4/0x193 (12)
 [<c01283f5>] up+0x35/0x3d (36)
 [<e00c2cb0>] highlevel_host_reset+0x3b/0x49 [ieee1394] (8)
 [<e00b0bf6>] ohci_irq_handler+0x576/0x713 [ohci1394] (12)
 [<c029ec06>] __sched_text_start+0x5a/0x5d7 (28)
 [<c012d77a>] __do_IRQ+0xca/0x180 (4)
 [<c012d634>] handle_IRQ_event+0x5c/0xc8 (36)
 [<c012dd86>] do_hardirq+0x61/0x112 (48)
 [<c0110dbd>] do_sched_setscheduler+0x73/0xa0 (4)
 [<c012de37>] do_irqd+0x0/0x96 (20)
 [<c012de9d>] do_irqd+0x66/0x96 (4)
 [<c0127018>] kthread+0x94/0xc8 (28)
 [<c0126f84>] kthread+0x0/0xc8 (16)
 [<c0100791>] kernel_thread_helper+0x5/0xb (16)


Steps to reproduce:
As said, this occurs on almost every other boot/init time.
Comment 1 Rui Nuno Capela 2005-02-24 05:15:11 UTC
Created attachment 4599 [details]
Complete dmesg output
Comment 2 Rui Nuno Capela 2005-02-24 05:16:59 UTC
Created attachment 4600 [details]
Kernel config.gz
Comment 3 Greg Kroah-Hartman 2005-02-24 11:11:07 UTC
As you are using Ingo's patches, please post this to him, in an email, not
on here.
Comment 4 Andreas Kuckartz 2005-03-12 05:41:35 UTC
I think I encountered the same bug using the 2.6.11 DeMuDi kernel and therefore
subscribed to this one in case it is reopened.

Note You need to log in before you can comment on or make changes to this bug.