From: James G. <ach...@ho...> - 2007-10-31 20:08:56
|
Hi everyone, =20 I've run into a little trouble with paging requests, and I'm not sure what = it means - can anyone shed any light? =20 The symptoms: Verdex boots okay, I can logon from the console, or from the = LCD + keyboard. Everything goes okay for a short while, and then out of the= blue the following happens: =20 # ls /Unable to handle kernel paging request at virtual address c8034708 pgd =3D c72bc000 [c8034708] *pgd=3D00000000 Internal error: Oops: 0 [#1] Modules linked in: ipv6 mcf25(P) af_packet smc911x usbhid hid gumstix_smc91= 1x cfio(P) ohci_hcd usbcore pxa2xx_cs pxa2xx_core pcmcia pcmcia_core firmwa= re_class smc91x mii gumstix_smc91x pxamci mmc_block mmc_core unix CPU: 0 PC is at 0xc8034708 LR is at try_to_wake_up+0x24/0x17c pc : [<c8034708>] lr : [<c00359d8>] Tainted: P=20 sp : c754fd88 ip : c754fd48 fp : c754fdb4 r10: 00000001 r9 : 00000000 r8 : 00000000 r7 : c7475134 r6 : 00000000 r5 : c7475134 r4 : 00000001 r3 : 20000093 r2 : 00000001 r1 : c754fd4c r0 : 00000000 Flags: NzCv IRQs off FIQs on Mode SVC_32 Segment user Control: 397F Table: A72BC000 DAC: 00000015 Process sh (pid: 431, stack limit =3D 0xc754e260) Stack: (0xc754fd88 to 0xc7550000) fd80: c00f9fa4 60000013 c01faf24 0000000a 00000000 c754e000=20 fda0: c750c400 c7ce91c0 c754fdd4 c754fdb8 c0034770 c00346d8 00000000 c754fd= c8=20 fdc0: c010d880 c7475000 c754fdec c754fdd8 c00f9fa4 c0034750 00000000 c01faf= 24=20 fde0: c754fdfc c754fdf0 c010be74 c00f9f58 c754fe14 c754fe00 c003df00 c010be= 68=20 fe00: c754fe2c 00000001 c754fe34 c754fe18 c003dd9c c003de84 c750c400 000000= 16=20 fe20: c01e4580 00000000 c754fe44 c754fe38 c003e174 c003dd48 c754fe64 c754fe= 48=20 fe40: c002a59c c003e13c c754fe64 ffffffff c754fe9c 00400000 c754fefc c754fe= 68=20 fe60: c0029830 c002a560 00000001 c7c43160 f2100000 c010b434 00000001 c74750= 00=20 fe80: c750c401 00000000 c754e000 c750c400 c7ce91c0 c754fefc c754fe58 c754fe= b0=20 fea0: c010b240 c00fc800 60000013 ffffffff c00fde1c c7475134 a0000013 000000= 00=20 fec0: c7ce4820 c0035b30 c7475134 c7475134 000000b2 00000001 400d882c c74750= 00=20 fee0: 400d882c 00000001 00000001 c754e000 c754ff4c c754ff00 c00f9724 c00fc5= 84=20 ff00: c7475000 c7ce91c0 c00fc578 c747500c c74753bc 00000000 00000000 c75063= 04=20 ff20: 00000000 c7ce91c0 400d882c 00000001 c754ff78 c0029d64 c754e000 400d5e= 58=20 ff40: c754ff74 c754ff50 c00760c4 c00f95ac 00000000 00000000 c7ce91c0 ffffff= f7=20 ff60: 00000000 00000000 c754ffa4 c754ff78 c0076684 c0076018 00000000 000000= 00=20 ff80: 08000000 00000000 400d6160 00000001 00000001 00000004 00000000 c754ff= a8=20 ffa0: c0029be0 c007664c 400d6160 00000001 00000001 400d882c 00000001 400635= fc=20 ffc0: 400d6160 00000001 00000001 00000004 00000001 00009494 400d5e58 000094= 98=20 ffe0: 000b9010 bea4e958 40062ce4 4004c210 20000010 00000001 00000000 000000= 00=20 Backtrace:=20 [<c00346cc>] (__wake_up_common+0x0/0x78) from [<c0034770>] (__wake_up+0x2c/= 0x38) [<c0034744>] (__wake_up+0x0/0x38) from [<c00f9fa4>] (tty_wakeup+0x58/0x5c) r4 =3D C7475000=20 [<c00f9f4c>] (tty_wakeup+0x0/0x5c) from [<c010be74>] (uart_tasklet_action+0= x18/0x1c) r5 =3D C01FAF24 r4 =3D 00000000=20 [<c010be5c>] (uart_tasklet_action+0x0/0x1c) from [<c003df00>] (tasklet_acti= on+0x88/0xe4) [<c003de78>] (tasklet_action+0x0/0xe4) from [<c003dd9c>] (__do_softirq+0x60= /0xd4) r4 =3D 00000001=20 [<c003dd3c>] (__do_softirq+0x0/0xd4) from [<c003e174>] (irq_exit+0x44/0x4c) r6 =3D 00000000 r5 =3D C01E4580 r4 =3D 00000016=20 [<c003e130>] (irq_exit+0x0/0x4c) from [<c002a59c>] (asm_do_IRQ+0x48/0x60) [<c002a554>] (asm_do_IRQ+0x0/0x60) from [<c0029830>] (__irq_svc+0x30/0x80) r6 =3D 00400000 r5 =3D C754FE9C r4 =3D FFFFFFFF=20 [<c00fc578>] (write_chan+0x0/0x358) from [<c00f9724>] (tty_write+0x184/0x22= 8) [<c00f95a0>] (tty_write+0x0/0x228) from [<c00760c4>] (vfs_write+0xb8/0x138) [<c007600c>] (vfs_write+0x0/0x138) from [<c0076684>] (sys_write+0x44/0x70) r7 =3D 00000000 r6 =3D 00000000 r5 =3D FFFFFFF7 r4 =3D C7CE91C0 [<c0076640>] (sys_write+0x0/0x70) from [<c0029be0>] (ret_fast_syscall+0x0/0= x2c) r7 =3D 00000004 r6 =3D 00000001 r5 =3D 00000001 r4 =3D 400D6160 Code: bad PC value. Kernel panic - not syncing: Aiee, killing interrupt handler! =20 I'm a little nervous about rebuilding and reflashing as I don't know whethe= r this is an indication of a hardware problem that will reappear in the mid= dle of reflashing or not. =20 Buildroot is at 1541. =20 The only recent change has been the introduction of a KeySonic mini-keyboar= d through a powered USB hub. =20 Any pointers to the cause of this would be much appreciated. =20 Cheers, =20 James _________________________________________________________________ Explore the seven wonders of the world http://search.msn.com/results.aspx?q=3D7+wonders+world&mkt=3Den-US&form=3DQ= BRE= |
From: Dave H. <dhy...@gm...> - 2007-10-31 21:39:26
|
Hi James, > # ls /Unable to handle kernel paging request at virtual address c8034708 > pgd = c72bc000 > [c8034708] *pgd=00000000 > Internal error: Oops: 0 [#1] > Modules linked in: ipv6 mcf25(P) af_packet smc911x usbhid hid > gumstix_smc911x cfio(P) ohci_hcd usbcore pxa2xx_cs pxa2xx_core pcmcia > pcmcia_core firmware_class smc91x mii gumstix_smc91x pxamci mmc_block > mmc_core unix > CPU: 0 > PC is at 0xc8034708 So it looks like some code tried to jump through a function pointer to address c8034708 and there is no memory mapped in at that address. > LR is at try_to_wake_up+0x24/0x17c LR indicates the place where the call came from. > Backtrace: > [<c00346cc>] (__wake_up_common+0x0/0x78) from [<c0034770>] > (__wake_up+0x2c/0x38) > [<c0034744>] (__wake_up+0x0/0x38) from [<c00f9fa4>] (tty_wakeup+0x58/0x5c) > r4 = C7475000 > [<c00f9f4c>] (tty_wakeup+0x0/0x5c) from [<c010be74>] > (uart_tasklet_action+0x18/0x1c) > r5 = C01FAF24 r4 = 00000000 > [<c010be5c>] (uart_tasklet_action+0x0/0x1c) from [<c003df00>] > (tasklet_action+0x88/0xe4) So looking at the backtrace it seems to be crapping out while doing something related to the uart, but it could also be that some other driver has corrupted some data structure used by the uart driver (that would be my guess). In particular, since the regular load doesn't experience this problem, it would most likely be related to the usbhid, hid, since these are new modules that most people haven't used before. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |