Hello all,
[please CC me on replies, I'm not subscribed to this list]
I had this following kernel oops while compiling a new kernel.
Dec 27 19:02:00 sidney kernel: [14896.995613] Unable to handle kernel paging request at virtual address 76f7104d
Dec 27 19:02:00 sidney kernel: [14896.995665] printing eip:
Dec 27 19:02:00 sidney kernel: [14896.995682] c013a392
Dec 27 19:02:00 sidney kernel: [14896.995692] *pde = 00000000
Dec 27 19:02:00 sidney kernel: [14896.995711] Oops: 0002 [#1]
Dec 27 19:02:00 sidney kernel: [14896.995726] PREEMPT
Dec 27 19:02:00 sidney kernel: [14896.995744] Modules linked in: md5 ipv6 lp capi capifs kernelcapi nls_iso8859_15 nls_cp437 vfat fat parport_pc parport joydev evdev tuner tvaudio msp3400 bttv video_buf firmware_class v4l2_common btcx_risc tveeprom videodev snd_bt87x snd_ens1370 gameport nvidiafb snd_rawmidi snd_seq_device snd_pcm snd_timer snd_page_alloc snd_ak4531_codec rivafb uhci_hcd ide_cd snd 8139too mii i2c_viapro usbcore cdrom soundcore crc32
Dec 27 19:02:00 sidney kernel: [14896.996038] CPU: 0
Dec 27 19:02:00 sidney kernel: [14896.996044] EIP: 0060:[shrink_slab+95/315] Not tainted VLI
Dec 27 19:02:00 sidney kernel: [14896.996053] EFLAGS: 00010246 (2.6.15-rc6.sidney.10)
Dec 27 19:02:00 sidney kernel: [14896.996117] EIP is at shrink_slab+0x5f/0x13b
Dec 27 19:02:00 sidney kernel: [14896.996141] eax: c1154900 ebx: 00000000 ecx: 00006830 edx: 00000000
Dec 27 19:02:00 sidney kernel: [14896.996172] esi: 700f0b05 edi: 0000002b ebp: c125df3f esp: c125df1c
Dec 27 19:02:00 sidney kernel: [14896.996200] ds: 007b es: 007b ss: 0068
Dec 27 19:02:00 sidney kernel: [14896.996224] Process kswapd0 (pid: 51, threadinfo=c125c000 task=c1256580)
Dec 27 19:02:00 sidney kernel: [14896.996248] Stack: 000000d0 0002a300 00000000 0002a300 00000080 00000000 c029f100 c029f100
Dec 27 19:02:00 sidney kernel: [14896.996339] 0000000c c125dfac c013b53d 00000000 000000d0 0000682f c029f100 c125df78
Dec 27 19:02:00 sidney kernel: [14896.996426] 00000001 00000000 00000000 c125dfd4 00000002 0000682f 00000000 00000020
Dec 27 19:02:00 sidney kernel: [14896.996512] Call Trace:
Dec 27 19:02:00 sidney kernel: [14896.996550] [show_stack+120/131] show_stack+0x78/0x83
Dec 27 19:02:00 sidney kernel: [14896.996600] [show_registers+306/415] show_registers+0x132/0x19f
Dec 27 19:02:00 sidney kernel: [14896.996646] [die+202/332] die+0xca/0x14c
Dec 27 19:02:00 sidney kernel: [14896.996687] [do_page_fault+910/1211] do_page_fault+0x38e/0x4bb
Dec 27 19:02:00 sidney kernel: [14896.996748] [error_code+79/96] error_code+0x4f/0x60
Dec 27 19:02:00 sidney kernel: [14896.996791] [phys_startup_32+329596353/-1073741824] 0x13b53dc1
Dec 27 19:02:00 sidney kernel: [14896.996834] Code: 00 00 00 8b 35 f4 f8 29 c0 c1 e1 02 89 4d ec 83 ee 04 c7 45 f0 00 00 00 00 e9 ba 00 00 00 ff 75 0c 6a 00 ff 16 89 c7 8b 45 ec 31 <d2> 8b 4d 10 f7 76 0c 41 f7 e7 89 45 e0 89 55 e4 89 d3 89 45 e8
please let me know if you need more informations/how I can help you solve
this problem.
Mathias Klein
Mathias Klein wrote:
> Hello all,
>
> [please CC me on replies, I'm not subscribed to this list]
>
> I had this following kernel oops while compiling a new kernel.
>
> Dec 27 19:02:00 sidney kernel: [14896.995613] Unable to handle kernel paging request at virtual address 76f7104d
> Dec 27 19:02:00 sidney kernel: [14896.995665] printing eip:
> Dec 27 19:02:00 sidney kernel: [14896.995682] c013a392
> Dec 27 19:02:00 sidney kernel: [14896.995692] *pde = 00000000
> Dec 27 19:02:00 sidney kernel: [14896.995711] Oops: 0002 [#1]
I might be wrong, but that is the second oops for this run, probably the first [#0] is more
interesting...
> Dec 27 19:02:00 sidney kernel: [14896.995726] PREEMPT
> Dec 27 19:02:00 sidney kernel: [14896.995744] Modules linked in: md5 ipv6 lp capi capifs kernelcapi nls_iso8859_15 nls_cp437 vfat fat parport_pc parport joydev evdev tuner tvaudio msp3400 bttv video_buf firmware_class v4l2_common btcx_risc tveeprom videodev snd_bt87x snd_ens1370 gameport nvidiafb snd_rawmidi snd_seq_device snd_pcm snd_timer snd_page_alloc snd_ak4531_codec rivafb uhci_hcd ide_cd snd 8139too mii i2c_viapro usbcore cdrom soundcore crc32
> Dec 27 19:02:00 sidney kernel: [14896.996038] CPU: 0
> Dec 27 19:02:00 sidney kernel: [14896.996044] EIP: 0060:[shrink_slab+95/315] Not tainted VLI
> Dec 27 19:02:00 sidney kernel: [14896.996053] EFLAGS: 00010246 (2.6.15-rc6.sidney.10)
> Dec 27 19:02:00 sidney kernel: [14896.996117] EIP is at shrink_slab+0x5f/0x13b
> Dec 27 19:02:00 sidney kernel: [14896.996141] eax: c1154900 ebx: 00000000 ecx: 00006830 edx: 00000000
> Dec 27 19:02:00 sidney kernel: [14896.996172] esi: 700f0b05 edi: 0000002b ebp: c125df3f esp: c125df1c
> Dec 27 19:02:00 sidney kernel: [14896.996200] ds: 007b es: 007b ss: 0068
> Dec 27 19:02:00 sidney kernel: [14896.996224] Process kswapd0 (pid: 51, threadinfo=c125c000 task=c1256580)
> Dec 27 19:02:00 sidney kernel: [14896.996248] Stack: 000000d0 0002a300 00000000 0002a300 00000080 00000000 c029f100 c029f100
> Dec 27 19:02:00 sidney kernel: [14896.996339] 0000000c c125dfac c013b53d 00000000 000000d0 0000682f c029f100 c125df78
> Dec 27 19:02:00 sidney kernel: [14896.996426] 00000001 00000000 00000000 c125dfd4 00000002 0000682f 00000000 00000020
> Dec 27 19:02:00 sidney kernel: [14896.996512] Call Trace:
> Dec 27 19:02:00 sidney kernel: [14896.996550] [show_stack+120/131] show_stack+0x78/0x83
> Dec 27 19:02:00 sidney kernel: [14896.996600] [show_registers+306/415] show_registers+0x132/0x19f
> Dec 27 19:02:00 sidney kernel: [14896.996646] [die+202/332] die+0xca/0x14c
> Dec 27 19:02:00 sidney kernel: [14896.996687] [do_page_fault+910/1211] do_page_fault+0x38e/0x4bb
> Dec 27 19:02:00 sidney kernel: [14896.996748] [error_code+79/96] error_code+0x4f/0x60
> Dec 27 19:02:00 sidney kernel: [14896.996791] [phys_startup_32+329596353/-1073741824] 0x13b53dc1
> Dec 27 19:02:00 sidney kernel: [14896.996834] Code: 00 00 00 8b 35 f4 f8 29 c0 c1 e1 02 89 4d ec 83 ee 04 c7 45 f0 00 00 00 00 e9 ba 00 00 00 ff 75 0c 6a 00 ff 16 89 c7 8b 45 ec 31 <d2> 8b 4d 10 f7 76 0c 41 f7 e7 89 45 e0 89 55 e4 89 d3 89 45 e8
>
> please let me know if you need more informations/how I can help you solve
> this problem.
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
On Wed, Dec 28, 2005 at 11:28:50PM +0900, Kalin KOZHUHAROV wrote:
> Mathias Klein wrote:
> > Hello all,
> >
> > [please CC me on replies, I'm not subscribed to this list]
> >
> > I had this following kernel oops while compiling a new kernel.
> >
> > Dec 27 19:02:00 sidney kernel: [14896.995613] Unable to handle kernel paging request at virtual address 76f7104d
> > Dec 27 19:02:00 sidney kernel: [14896.995665] printing eip:
> > Dec 27 19:02:00 sidney kernel: [14896.995682] c013a392
> > Dec 27 19:02:00 sidney kernel: [14896.995692] *pde = 00000000
> > Dec 27 19:02:00 sidney kernel: [14896.995711] Oops: 0002 [#1]
>
> I might be wrong, but that is the second oops for this run, probably the first [#0] is more
> interesting...
Probably yes but there is no [#0] Oops in the logs.
(Indeed I do have another [#1] Oops in another run with that kernel without
an [#0] Oops)
Mathias
On 12/28/05, Mathias Klein <[email protected]> wrote:
> On Wed, Dec 28, 2005 at 11:28:50PM +0900, Kalin KOZHUHAROV wrote:
> > Mathias Klein wrote:
> > > Hello all,
> > >
> > > [please CC me on replies, I'm not subscribed to this list]
> > >
> > > I had this following kernel oops while compiling a new kernel.
> > >
> > > Dec 27 19:02:00 sidney kernel: [14896.995613] Unable to handle kernel paging request at virtual address 76f7104d
> > > Dec 27 19:02:00 sidney kernel: [14896.995665] printing eip:
> > > Dec 27 19:02:00 sidney kernel: [14896.995682] c013a392
> > > Dec 27 19:02:00 sidney kernel: [14896.995692] *pde = 00000000
> > > Dec 27 19:02:00 sidney kernel: [14896.995711] Oops: 0002 [#1]
> >
> > I might be wrong, but that is the second oops for this run, probably the first [#0] is more
> > interesting...
>
> Probably yes but there is no [#0] Oops in the logs.
> (Indeed I do have another [#1] Oops in another run with that kernel without
> an [#0] Oops)
#1 is the first oops. See die() in arch/i386/kernel/traps.c. Anyway,
try enabling CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC to see if
they pick up anything.
On Wed, 28 Dec 2005, Mathias Klein wrote:
> On Wed, Dec 28, 2005 at 11:28:50PM +0900, Kalin KOZHUHAROV wrote:
> > Mathias Klein wrote:
> > > Hello all,
> > >
> > > [please CC me on replies, I'm not subscribed to this list]
> > >
> > > I had this following kernel oops while compiling a new kernel.
> > >
> > > Dec 27 19:02:00 sidney kernel: [14896.995613] Unable to handle kernel paging request at virtual address 76f7104d
> > > Dec 27 19:02:00 sidney kernel: [14896.995665] printing eip:
> > > Dec 27 19:02:00 sidney kernel: [14896.995682] c013a392
> > > Dec 27 19:02:00 sidney kernel: [14896.995692] *pde = 00000000
> > > Dec 27 19:02:00 sidney kernel: [14896.995711] Oops: 0002 [#1]
> >
> > I might be wrong, but that is the second oops for this run, probably the first [#0] is more
> > interesting...
>
> Probably yes but there is no [#0] Oops in the logs.
> (Indeed I do have another [#1] Oops in another run with that kernel without
> an [#0] Oops)
The first Oops is #1.
That is the one that we are interested in most of the time.
--
~Randy
On Wed, Dec 28, 2005 at 05:15:54PM +0200, Pekka Enberg wrote:
> #1 is the first oops. See die() in arch/i386/kernel/traps.c. Anyway,
> try enabling CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC to see if
> they pick up anything.
I'll give it a try and come back if it occurs again...
Thanks
Mathias
On Wed, Dec 28, 2005 at 02:50:22PM +0100, Mathias Klein wrote:
> Hello all,
Hi Mathias,
> [please CC me on replies, I'm not subscribed to this list]
>
> I had this following kernel oops while compiling a new kernel.
>...
> please let me know if you need more informations/how I can help you solve
> this problem.
older kernels (e.g. 2.6.14.x) are working without problems?
> Mathias Klein
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
On Fri, Dec 30, 2005 at 11:37:21PM +0100, Adrian Bunk wrote:
> On Wed, Dec 28, 2005 at 02:50:22PM +0100, Mathias Klein wrote:
>
> > Hello all,
>
> Hi Mathias,
>
> > [please CC me on replies, I'm not subscribed to this list]
> >
> > I had this following kernel oops while compiling a new kernel.
> >...
> > please let me know if you need more informations/how I can help you solve
> > this problem.
>
> older kernels (e.g. 2.6.14.x) are working without problems?
Before there was running version 2.6.12.3 and 2.6.13.4 whithout problems.
>
> > Mathias Klein
>
> cu
> Adrian
Mathias