Bug 3389 - fatal irq exception
Summary: fatal irq exception
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: IEEE1394 (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Ben Collins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-13 10:09 UTC by Johan Dahlin
Modified: 2006-02-02 16:02 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.8-1.521
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Johan Dahlin 2004-09-13 10:09:10 UTC 
Distribution: Fedora Core 2

Hardware Environment:
P4/3GHz
Sony DV camera

Software Environment:
Fedora Core 2 + updates

Problem Description:
Kernel crashes after DV capturing

Steps to reproduce:
Turn on the DV camera and start capturing, after some time, hours/days it crashes.

Backtrace:
CPU:    0
EIP:    0060:[<2226c4a4>]  Not tainted
EFLAGS: 00010013   (2.6.8-1.521)
EIP is at handle_selfid+0xcd/0xf2 [ohci1394]
eax: 00000000   ebx: ffe06eb7   ecx: 00000000   edx: 0994b5e8
esi: 18d62ae8   edi: 1953e734   ebp: 18d60000   esp: 023c7fa0
ds: 007b   es: 007b   ss: 0068
Process swapper (pid: 0, threadinfo=023c7000 task=02341b80)
Stack: 00000000 0994b5e8 18d62ae8 00000006 00010000 00000000 2226f0dc 00000000
       02126b63 00000000 18d60000 18cf0880 04000001 00000000 00000003 0210782f
       0239af9c 02399180 023c7000 00000003 02107d2e 00000003 0239afb8 18cf0880
CallTrace:
[<2226f0dc>] ohci_irq_handler+0x7d6/0x9d0 [ohci1394]
[<02126b63>] update_wall_time+0x9/0x31
[<0210782f>] handle_IRQ_event+0x21/0x41
[<02107d2e>] do_IRQ+0x1be/0x303
=======================
[<0210403b>] default_idle+0x23/0x26
[<0210408c>] cpu_idle+0x1f/0x34
[<0239b6ae>] start_kernel+0x221/0x224
Code: ff b0 70 29 00 00 68 e9 10 27 22 68 29 12 27 22 e8 7a 2a eb
 <0>Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing
Comment 1 Adrian Bunk 2005-08-01 01:19:19 UTC 
Is this problem still present in kernel 2.6.13-rc4?
Comment 2 Adrian Bunk 2006-02-02 16:02:34 UTC 
I'm assuming this issue is already fixed.

Please reopen this bug if it's still present in recent 2.6 kernels.
Note You need to log in before you can comment on or make changes to this bug.