PROBLEM: kernel OOPS

PROBLEM: kernel OOPS

[Jeffrey Ross]

Bear with me, this is my first attempt at sending the output of a kernel 
oops.  I believe I have all the desired information.  Here goes...

The system appears to randomly lock up, with X running, without X 
running etc.  it appears to be occuring whenever the CD drives are accessed.

The multi question form:

[1-3] I'm not sure exactly how to answer
[4] Linux version 2.4.21-pre3-ac3 (root@wisdom2) (gcc version 3.2 
20020903 (Red Hat
Linux 8.0 3.2-7)) #6 Sat Jan 11 14:29:12 EST 2003
[5] see http://www.bubble.org/~jeff/crash.tar.gz (includes console 
output from bootup until the crash plus everything asked for in 
"oops-tracing.txt" (I think)
[6] I don't think its possible
[7] not sure ??
[7.X] all files are included in the tar file

I've tried to make the contents of the files self explanitory.

Although I'm not a programmer, I am willing to help out in any way I can 
to find and squash this problem.

Other information...

System Motherboard is an Intel Model# D845GBV the BIOS is the dated 
November 20,2002 on Intel's website.

Both CDrom drivers are IDE and I'm using the IDE to scsi shim.

Jeff

Problem: Kernel oops

[Mockern]

Hi,

I have the Linux kernel oops problem sometime.
How can I fix it?
Thank you

---------------------------------------------------------------------------------
Unable to handle kernel NULL pointer dereference at virtual address 00000004
pgd = c0004000
[00000004] *pgd=00000000
Internal error: Oops: 17 [#1]
Modules linked in:
CPU: 0
PC is at serial_pxa_irq+0x14/0x510
LR is at __do_irq+0x4c/0x88
pc : [<c0171aa4>]    lr : [<c00229f8>]    Not tainted
sp : c024fea4  ip : c024fee4  fp : c024fee0
r10: c029dc20  r9 : 69052d06  r8 : c024ff54
r7 : 0000000d  r6 : 00000000  r5 : 00000000  r4 : 00000000
r3 : 40000013  r2 : c024ff54  r1 : 00000000  r0 : 0000000d
Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  Segment kernel
Control: 397F  Table: A3B30000  DAC: 00000017
Process swapper (pid: 0, stack limit = 0xc024e198)
Stack: (0xc024fea4 to 0xc0250000)
fea0:          c02a5160 c024feec c024feb8 c00453c8 c0052a20 c3d47d00 00000000
fec0: 00000000 0000000d c024ff54 69052d06 c029dc20 c024ff04 c024fee4 c00229f8
fee0: c0171a9c c029def8 0000000d c024ff54 c02b3048 c024ff54 c024ff20 c024ff08
ff00: c0022c34 c00229b8 c029def8 f2d00000 00100000 c024ff50 c024ff24 c0022cd0
ff20: c0022bd8 c024e018 00000000 ffffffff f2d00000 00100000 c02b3048 a001e4ac
ff40: a001e44c c024ffa8 c024ff54 c00219a4 c0022c90 00000001 c036e000 00000000
ff60: 60000013 c00235f4 c024e000 c02a7918 c02b3048 a001e4ac 69052d06 a001e44c
ff80: c024ffa8 c024ffac c024ff9c c0023634 c0023640 60000013 ffffffff c024ffc0
ffa0: c024ffac c0023690 c0023600 0000397d c029d7dc c024ffd0 c024ffc4 c0021024
ffc0: c0023654 c024fff4 c024ffd4 c000881c c002100c c00082e4 c029f4a8 0000397d
ffe0: c029f444 c0251ba0 00000000 c024fff8 a0008030 c000865c 00000000 00000000
Backtrace:
[<c0171a90>] (serial_pxa_irq+0x0/0x510) from [<c00229f8>] (__do_irq+0x4c/0x88)
[<c00229ac>] (__do_irq+0x0/0x88) from [<c0022c34>] (do_level_IRQ+0x68/0xb8)
 r8 = C024FF54  r7 = C02B3048  r6 = C024FF54  r5 = 0000000D
 r4 = C029DEF8
[<c0022bcc>] (do_level_IRQ+0x0/0xb8) from [<c0022cd0>] (asm_do_IRQ+0x4c/0x118)
 r6 = 00100000  r5 = F2D00000  r4 = C029DEF8
[<c0022c84>] (asm_do_IRQ+0x0/0x118) from [<c00219a4>] (__irq_svc+0x24/0x80)
[<c00235f4>] (default_idle+0x0/0x54) from [<c0023690>] (cpu_idle+0x48/0x64)
[<c0023648>] (cpu_idle+0x0/0x64) from [<c0021024>] (__init_end+0x24/0x2c)
 r5 = C029D7DC  r4 = 0000397D
[<c0021000>] (__init_end+0x0/0x2c) from [<c000881c>] 
(start_kernel+0x1cc/0x224)
[<c0008650>] (start_kernel+0x0/0x224) from [<a0008030>] (0xa0008030)
Code: e92ddff0 e24cb004 e24dd014 e1a04001 (e5911004)
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler

Re: Problem: Kernel oops

[Russell King]

On Mon, Mar 05, 2007 at 01:23:24PM +0300, Mockern wrote:
> I have the Linux kernel oops problem sometime.

serial_pxa_irq() was passed a NULL dev_id parameter by the interrupt
layer.  This can only happen if request_irq() was called with a NULL
dev_id parameter.

> How can I fix it?

Show me your modifications to drivers/serial/pxa.c

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of: