* OOPS: 2.6.9
@ 2004-11-10 7:48 Mark Hindley
2004-11-10 8:28 ` Nick Piggin
0 siblings, 1 reply; 5+ messages in thread
From: Mark Hindley @ 2004-11-10 7:48 UTC (permalink / raw)
To: linux-kernel
I got this oops this morning with 2.6.9
I have rebooted without the nvidia module and will let you know if it
hapens again.
Let me know if you need more info
Mark
Nov 10 07:40:01 titan kernel: kernel BUG at mm/vmscan.c:370!
Nov 10 07:40:01 titan kernel: invalid operand: 0000 [#1]
Nov 10 07:40:01 titan kernel: PREEMPT
Nov 10 07:40:01 titan kernel: Modules linked in: ide_cd cdrom nvidia ipv6 nfs nfsd exportfs lockd sunrpc snd_als100 snd_opl3_lib snd_hwdep snd_sb16_dsp snd_sb_common snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore 3c59x dummy ipt_REJECT ipt_LOG ipt_limit ipt_MASQUERADE ipt_owner ipt_REDIRECT iptable_nat ipt_state iptable_filter ip_conntrack ip_tables hangcheck_timer 8250_pnp 8250 serial_core
Nov 10 07:40:01 titan kernel: CPU: 0
Nov 10 07:40:01 titan kernel: EIP: 0060:[shrink_list+155/1064] Tainted: P VLI
Nov 10 07:40:01 titan kernel: EFLAGS: 00010202 (2.6.9)
Nov 10 07:40:01 titan kernel: EIP is at shrink_list+0x9b/0x428
Nov 10 07:40:01 titan kernel: eax: 20001045 ebx: c102ffe0 ecx: c102fff8 edx: c1060338
Nov 10 07:40:01 titan kernel: esi: c1172000 edi: c10d7490 ebp: c10d7490 esp: c1173e44
Nov 10 07:40:01 titan kernel: ds: 007b es: 007b ss: 0068
Nov 10 07:40:01 titan kernel: Process kswapd0 (pid: 41, threadinfo=c1172000 task=c115ab10)
Nov 10 07:40:01 titan kernel: Stack: c1173ee4 c1172000 c02b59ac 00000021 00000001 00000001 00000009 00000005
Nov 10 07:40:01 titan kernel: c1059398 c10713d8 00000009 00000001 c104b320 c105e800 c1079160 c1062f20
Nov 10 07:40:01 titan kernel: c10798e0 c104e9a0 c1045120 c1076d00 c10433e0 00000001 c105f1e0 c013c763
Nov 10 07:40:01 titan kernel: Call Trace:
Nov 10 07:40:01 titan kernel: [refill_inactive_zone+1267/1380] refill_inactive_zone+0x4f3/0x564
Nov 10 07:40:01 titan kernel: [shrink_cache+463/824] shrink_cache+0x1cf/0x338
Nov 10 07:40:01 titan kernel: [shrink_zone+147/172] shrink_zone+0x93/0xac
Nov 10 07:40:01 titan kernel: [balance_pgdat+399/668] balance_pgdat+0x18f/0x29c
Nov 10 07:40:01 titan kernel: [kswapd+216/224] kswapd+0xd8/0xe0
Nov 10 07:40:01 titan kernel: [kswapd+0/224] kswapd+0x0/0xe0
Nov 10 07:40:01 titan kernel: [autoremove_wake_function+0/64] autoremove_wake_function+0x0/0x40
Nov 10 07:40:01 titan kernel: [autoremove_wake_function+0/64] autoremove_wake_function+0x0/0x40
Nov 10 07:40:01 titan kernel: [kernel_thread_helper+5/12] kernel_thread_helper+0x5/0xc
Nov 10 07:40:01 titan kernel: Code: 50 04 89 02 c7 01 00 01 10 00 c7 41 04 00 02 20 00 31 c0 0f ab 41 e8 19 c0 85 c0 0f 85 05 03 00 00 8b 41 e8 a9 40 00 00 00 74 08 <0f> 0b 72 01 84 ab 26 c0 8b 41 e8 a9 00 20 00 00 0f 85 de 02 00
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: OOPS: 2.6.9
2004-11-10 7:48 OOPS: 2.6.9 Mark Hindley
@ 2004-11-10 8:28 ` Nick Piggin
2004-11-11 7:27 ` Mark Hindley
0 siblings, 1 reply; 5+ messages in thread
From: Nick Piggin @ 2004-11-10 8:28 UTC (permalink / raw)
To: Mark Hindley; +Cc: linux-kernel
Mark Hindley wrote:
> I got this oops this morning with 2.6.9
>
> I have rebooted without the nvidia module and will let you know if it
> hapens again.
>
> Let me know if you need more info
>
> Mark
>
> Nov 10 07:40:01 titan kernel: kernel BUG at mm/vmscan.c:370!
> Nov 10 07:40:01 titan kernel: invalid operand: 0000 [#1]
> Nov 10 07:40:01 titan kernel: PREEMPT
> Nov 10 07:40:01 titan kernel: Modules linked in: ide_cd cdrom nvidia ipv6 nfs nfsd exportfs lockd sunrpc snd_als100 snd_opl3_lib snd_hwdep snd_sb16_dsp snd_sb_common snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore 3c59x dummy ipt_REJECT ipt_LOG ipt_limit ipt_MASQUERADE ipt_owner ipt_REDIRECT iptable_nat ipt_state iptable_filter ip_conntrack ip_tables hangcheck_timer 8250_pnp 8250 serial_core
> Nov 10 07:40:01 titan kernel: CPU: 0
> Nov 10 07:40:01 titan kernel: EIP: 0060:[shrink_list+155/1064] Tainted: P VLI
> Nov 10 07:40:01 titan kernel: EFLAGS: 00010202 (2.6.9)
> Nov 10 07:40:01 titan kernel: EIP is at shrink_list+0x9b/0x428
> Nov 10 07:40:01 titan kernel: eax: 20001045 ebx: c102ffe0 ecx: c102fff8 edx: c1060338
> Nov 10 07:40:01 titan kernel: esi: c1172000 edi: c10d7490 ebp: c10d7490 esp: c1173e44
> Nov 10 07:40:01 titan kernel: ds: 007b es: 007b ss: 0068
> Nov 10 07:40:01 titan kernel: Process kswapd0 (pid: 41, threadinfo=c1172000 task=c115ab10)
> Nov 10 07:40:01 titan kernel: Stack: c1173ee4 c1172000 c02b59ac 00000021 00000001 00000001 00000009 00000005
> Nov 10 07:40:01 titan kernel: c1059398 c10713d8 00000009 00000001 c104b320 c105e800 c1079160 c1062f20
> Nov 10 07:40:01 titan kernel: c10798e0 c104e9a0 c1045120 c1076d00 c10433e0 00000001 c105f1e0 c013c763
> Nov 10 07:40:01 titan kernel: Call Trace:
> Nov 10 07:40:01 titan kernel: [refill_inactive_zone+1267/1380] refill_inactive_zone+0x4f3/0x564
> Nov 10 07:40:01 titan kernel: [shrink_cache+463/824] shrink_cache+0x1cf/0x338
> Nov 10 07:40:01 titan kernel: [shrink_zone+147/172] shrink_zone+0x93/0xac
> Nov 10 07:40:01 titan kernel: [balance_pgdat+399/668] balance_pgdat+0x18f/0x29c
> Nov 10 07:40:01 titan kernel: [kswapd+216/224] kswapd+0xd8/0xe0
> Nov 10 07:40:01 titan kernel: [kswapd+0/224] kswapd+0x0/0xe0
> Nov 10 07:40:01 titan kernel: [autoremove_wake_function+0/64] autoremove_wake_function+0x0/0x40
> Nov 10 07:40:01 titan kernel: [autoremove_wake_function+0/64] autoremove_wake_function+0x0/0x40
> Nov 10 07:40:01 titan kernel: [kernel_thread_helper+5/12] kernel_thread_helper+0x5/0xc
> Nov 10 07:40:01 titan kernel: Code: 50 04 89 02 c7 01 00 01 10 00 c7 41 04 00 02 20 00 31 c0 0f ab 41 e8 19 c0 85 c0 0f 85 05 03 00 00 8b 41 e8 a9 40 00 00 00 74 08 <0f> 0b 72 01 84 ab 26 c0 8b 41 e8 a9 00 20 00 00 0f 85 de 02 00
>
>
a9 40 00 00 00 test $0x40,%eax
74 08 je 33 <_EIP+0x33>
0f 0b ud2a
So eax (20001045) is page->flags, which is
PG_locked | PG_referenced | PG_active | PG_private, I think.
You might have flipped a bit. Can you run memtest86 on the system overnight?
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: OOPS: 2.6.9
2004-11-10 8:28 ` Nick Piggin
@ 2004-11-11 7:27 ` Mark Hindley
2004-11-11 8:35 ` Nick Piggin
0 siblings, 1 reply; 5+ messages in thread
From: Mark Hindley @ 2004-11-11 7:27 UTC (permalink / raw)
To: Nick Piggin; +Cc: linux-kernel
On Wed, Nov 10, 2004 at 07:28:44PM +1100, Nick Piggin wrote:
> a9 40 00 00 00 test $0x40,%eax
> 74 08 je 33 <_EIP+0x33>
> 0f 0b ud2a
>
> So eax (20001045) is page->flags, which is
> PG_locked | PG_referenced | PG_active | PG_private, I think.
>
> You might have flipped a bit. Can you run memtest86 on the system overnight?
>
Ran for 12 hours overnight. Extended tests, no errors.
M
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: OOPS: 2.6.9
2004-11-11 7:27 ` Mark Hindley
@ 2004-11-11 8:35 ` Nick Piggin
2004-11-11 10:18 ` Arjan van de Ven
0 siblings, 1 reply; 5+ messages in thread
From: Nick Piggin @ 2004-11-11 8:35 UTC (permalink / raw)
To: Mark Hindley; +Cc: linux-kernel
Mark Hindley wrote:
> On Wed, Nov 10, 2004 at 07:28:44PM +1100, Nick Piggin wrote:
>
>
>> a9 40 00 00 00 test $0x40,%eax
>> 74 08 je 33 <_EIP+0x33>
>> 0f 0b ud2a
>>
>>So eax (20001045) is page->flags, which is
>>PG_locked | PG_referenced | PG_active | PG_private, I think.
>>
>>You might have flipped a bit. Can you run memtest86 on the system overnight?
>>
>
>
> Ran for 12 hours overnight. Extended tests, no errors.
>
OK, it's just that it's a pretty common path in the kernel, and if
there was a bug there you'd be very unlucky to be the only one
hitting it. Still, it's possible. Probably the best thing to do is
report it if it happens again.
Oh, what sort of system is it? CPU, how much RAM, etc?
Sorry I can't be of more help.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: OOPS: 2.6.9
2004-11-11 8:35 ` Nick Piggin
@ 2004-11-11 10:18 ` Arjan van de Ven
0 siblings, 0 replies; 5+ messages in thread
From: Arjan van de Ven @ 2004-11-11 10:18 UTC (permalink / raw)
To: Nick Piggin; +Cc: Mark Hindley, linux-kernel
On Thu, 2004-11-11 at 19:35 +1100, Nick Piggin wrote:
> OK, it's just that it's a pretty common path in the kernel, and if
> there was a bug there you'd be very unlucky to be the only one
> hitting it. Still, it's possible. Probably the best thing to do is
> report it if it happens again.
well he's using the nvidia binary driver... maybe that's interacting
funny....
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-11-11 10:18 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-11-10 7:48 OOPS: 2.6.9 Mark Hindley
2004-11-10 8:28 ` Nick Piggin
2004-11-11 7:27 ` Mark Hindley
2004-11-11 8:35 ` Nick Piggin
2004-11-11 10:18 ` Arjan van de Ven
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox