* 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"
@ 2004-09-19 1:41 Mike Kirk
2004-09-19 12:07 ` Hugh Dickins
0 siblings, 1 reply; 6+ messages in thread
From: Mike Kirk @ 2004-09-19 1:41 UTC (permalink / raw)
To: linux-kernel
Not sure what this means: but the system kept running and I only lost a
bzip2 process: 2.6.9-rc2 w/preempt AMD 2700+ on A7N8X motherboard, 1GB
DDR400:
==============================
kernel BUG at mm/rmap.c:473!
invalid operand: 0000 [#1]
PREEMPT
Modules linked in:
CPU: 0
EIP: 0060:[<c014a8f9>] Not tainted VLI
EFLAGS: 00010286 (2.6.8.1N)
EIP is at page_remove_rmap+0x29/0x40
eax: ffffffff ebx: 00005000 ecx: c1017a18 edx: c1017a00
esi: fffedffc edi: 00006000 ebp: c1017a00 esp: f6c99e84
ds: 007b es: 007b ss: 0068
Process bzip2 (pid: 11701, threadinfo=f6c98000 task=c0ec8560)
Stack: c0143f21 c1017a00 00000007 c0ecab7c c0ecab7c 00bd0067 00000000
bfffa000
c04f9c94 c03fa000 c0ecac00 c0000000 00000000 c0144087 c04f9c94 c0ecabfc
bfffa000 00006000 00000000 c04f9c94 bfffa000 c0ecac00 c0000000 00000000
Call Trace:
[<c0143f21>] zap_pte_range+0x161/0x270
[<c0144087>] zap_pmd_range+0x57/0x80
[<c01440fb>] unmap_page_range+0x4b/0x80
[<c014422d>] unmap_vmas+0xfd/0x1c0
[<c0148a53>] exit_mmap+0x83/0x160
[<c011abb4>] mmput+0x64/0xa0
[<c011ef42>] do_exit+0x152/0x420
[<c011f29a>] do_group_exit+0x3a/0xb0
[<c0105c07>] syscall_call+0x7/0xb
Code: 26 00 8b 54 24 04 8b 02 f6 c4 08 75 28 83 42 08 ff 0f 98 c0 84 c0 74
11 8b 42 08 40 78 0d 9c 58 fa ff 0d 90 7e 50 c0 50 9d 90 c3 <0f> 0b d9 01 6d
eb 3c c0 eb e9 0f 0b d6 01 6d eb 3c c0 eb ce 8d
<6>note: bzip2[11701] exited with preempt_count 2
bad: scheduling while atomic!
[<c03aac06>] schedule+0x4c6/0x4d0
[<c0155773>] wake_up_buffer+0x13/0x40
[<c01558e3>] unlock_buffer+0x13/0x20
[<c015903f>] ll_rw_block+0x4f/0x80
[<c01a8212>] search_by_key+0xfc2/0x1030
[<c0268550>] pty_write+0x130/0x140
[<c02b8897>] ppp_async_push+0x97/0x170
[<c02b87f2>] ppp_async_send+0x42/0x50
[<c02b3e68>] ppp_push+0x98/0x100
[<c0124983>] __mod_timer+0x123/0x170
[<c0328e09>] htb_delay_by+0x49/0xb0
[<c032903f>] htb_dequeue+0x1cf/0x260
[<c01a8331>] search_for_position_by_key+0xb1/0x3e0
[<c031fa77>] qdisc_restart+0x17/0x1d0
[<c0314c61>] net_tx_action+0xa1/0xd0
[<c0191629>] make_cpu_key+0x59/0x70
[<c01aa2f6>] reiserfs_do_truncate+0xc6/0x5a0
[<c019529d>] reiserfs_truncate_file+0xed/0x240
[<c0196de6>] reiserfs_file_release+0x266/0x470
[<c016bba4>] dput+0x24/0x210
[<c01554e0>] __fput+0x110/0x130
[<c0153c09>] filp_close+0x59/0x90
[<c011e23a>] put_files_struct+0x5a/0xc0
[<c011ef7d>] do_exit+0x18d/0x420
[<c0107220>] do_invalid_op+0x0/0x120
[<c0106e68>] die+0x188/0x190
[<c014a8f9>] page_remove_rmap+0x29/0x40
[<c0115676>] fixup_exception+0x16/0x60
[<c0107332>] do_invalid_op+0x112/0x120
[<c014a8f9>] page_remove_rmap+0x29/0x40
[<c0124eeb>] update_wall_time+0xb/0x40
[<c012535f>] do_timer+0xdf/0xf0
[<c01212bd>] __do_softirq+0x7d/0x90
[<c0106611>] error_code+0x2d/0x38
[<c014a8f9>] page_remove_rmap+0x29/0x40
[<c0143f21>] zap_pte_range+0x161/0x270
[<c0144087>] zap_pmd_range+0x57/0x80
[<c01440fb>] unmap_page_range+0x4b/0x80
[<c014422d>] unmap_vmas+0xfd/0x1c0
[<c0148a53>] exit_mmap+0x83/0x160
[<c011abb4>] mmput+0x64/0xa0
[<c011ef42>] do_exit+0x152/0x420
[<c011f29a>] do_group_exit+0x3a/0xb0
[<c0105c07>] syscall_call+0x7/0xb
==============================
Regards,
Mike
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"
2004-09-19 1:41 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!" Mike Kirk
@ 2004-09-19 12:07 ` Hugh Dickins
2004-11-30 15:06 ` 2.6.10-rc2-mm3 [was: Re: 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"] Benoit Boissinot
0 siblings, 1 reply; 6+ messages in thread
From: Hugh Dickins @ 2004-09-19 12:07 UTC (permalink / raw)
To: Mike Kirk; +Cc: Andrew Morton, linux-kernel
On Sat, 18 Sep 2004, Mike Kirk wrote:
> Not sure what this means: but the system kept running and I only lost a
> bzip2 process: 2.6.9-rc2 w/preempt AMD 2700+ on A7N8X motherboard, 1GB
> DDR400:
> ==============================
> kernel BUG at mm/rmap.c:473!
> EIP is at page_remove_rmap+0x29/0x40
Was there a "Bad page state" message and backtrace shortly before this?
I say "shortly" because I don't suppose bzip2 had been running for hours,
I'd expect the underlying error to have occurred while it was running.
BUG_ON(page_mapcount(page) < 0);
Previous incidents of this BUG (or its antecedents: the mapcount has
recently changed to atomic from guarded by spinlock) have been after
something elsewhere has freed a page it no longer owned, which has
meanwhile got mapped into process address space.
If that's the case this time around, then I hope the bad_page backtrace
will shed light on what's freeing that shouldn't. But if there was no
"Bad page state" message before, then I'll have to start worrying about
rmap mapcount consistency.
(The page_remove_rmap BUG follows as a consequence of bad_page resetting
the mapcount on such a page. This is unsatisfactory: that code remote
from the cause should force a BUG, whereas code nearer the cause try to
continue without forcing a BUG. Just removing the BUG from mm/rmap.c
would let me off the hook, but seems irresponsible. Adding a BUG into
bad_page would revert an intentional relaxation. I don't know.)
Hugh
^ permalink raw reply [flat|nested] 6+ messages in thread
* 2.6.10-rc2-mm3 [was: Re: 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"]
2004-09-19 12:07 ` Hugh Dickins
@ 2004-11-30 15:06 ` Benoit Boissinot
2004-12-01 0:49 ` Hugh Dickins
0 siblings, 1 reply; 6+ messages in thread
From: Benoit Boissinot @ 2004-11-30 15:06 UTC (permalink / raw)
To: Hugh Dickins; +Cc: Linux Kernel, Andrew Morton, Mike Kirk
[-- Attachment #1: Type: text/plain, Size: 3869 bytes --]
On Sun, 19 Sep 2004, Hugh Dickins wrote:
> On Sat, 18 Sep 2004, Mike Kirk wrote:
> > Not sure what this means: but the system kept running and I only lost a
> > bzip2 process: 2.6.9-rc2 w/preempt AMD 2700+ on A7N8X motherboard, 1GB
> > DDR400:
> > ==============================
> > kernel BUG at mm/rmap.c:473!
> > EIP is at page_remove_rmap+0x29/0x40
>
> Was there a "Bad page state" message and backtrace shortly before this?
> I say "shortly" because I don't suppose bzip2 had been running for hours,
> I'd expect the underlying error to have occurred while it was running.
>
> BUG_ON(page_mapcount(page) < 0);
>
I had the same BUG_ON with 2.6.10-rc2-mm3 while transcoding a video.
------------[ cut here ]------------
kernel BUG at mm/rmap.c:479!
invalid operand: 0000 [#1]
Modules linked in: radeon drm snd_seq snd_via82xx snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore ide_cd cdrom sk98lin
CPU: 0
EIP: 0060:[<c01454a4>] Not tainted VLI
EFLAGS: 00010286 (2.6.10-rc2-mm3-arakou)
EIP is at page_remove_rmap+0x34/0x40
eax: ffffffff ebx: 00007000 ecx: c03be100 edx: c17712c0
esi: cbfa60bc edi: 003ce000 ebp: c6648d78 esp: c6648d78
ds: 007b es: 007b ss: 0068
Process transcode (pid: 14505, threadinfo=c6648000 task=dac3aaa0)
Stack: c6648dac c013f2af c6648e34 c02d74dd 00000003 0000000e 3b896067 c17712c0
b2028000 c03be100 b2428000 c8027b24 b23f6000 c6648dd4 c013f439 003ce000
00000000 00000000 c0310524 c03be100 b2028000 c8027b24 b23f6000 c6648df4
Call Trace:
[<c0103b2a>] show_stack+0x7a/0x90
[<c0103cad>] show_registers+0x14d/0x1c0
[<c0103e82>] die+0xc2/0x140
[<c01042a3>] do_invalid_op+0xa3/0xb0
[<c01037e3>] error_code+0x2b/0x30
[<c013f2af>] zap_pte_range+0x13f/0x280
[<c013f439>] zap_pmd_range+0x49/0x70
[<c013f49d>] zap_pgd_range+0x3d/0x70
[<c013f4fb>] unmap_page_range+0x2b/0x40
[<c013f600>] unmap_vmas+0xf0/0x1f0
[<c014399b>] exit_mmap+0x6b/0x120
[<c0116431>] mmput+0x41/0xd0
[<c011a2db>] do_exit+0x15b/0x420
[<c011a616>] do_group_exit+0x36/0x70
[<c0122b0b>] get_signal_to_deliver+0x1bb/0x2b0
[<c0102b76>] do_signal+0x66/0x120
[<c0102c69>] do_notify_resume+0x39/0x3c
[<c0102daa>] work_notifysig+0x13/0x15
Code: 08 75 1e 83 42 08 ff 0f 98 c0 84 c0 74 11 8b 42 08 40 78 17 9c 58 fa ff 0d d0 c4 3c c0 50 9d c9 c3 0f 0b dc 01 db 95 2d c0 eb d8 <0f> 0b df 01 db 95 2d c0 eb df 89 f6 55 89 e5 83 ec 18 89 5d f4
BUG: atomic counter underflow at:
[<c0103b57>] dump_stack+0x17/0x20
[<c011a51e>] do_exit+0x39e/0x420
[<c0103efc>] die+0x13c/0x140
[<c01042a3>] do_invalid_op+0xa3/0xb0
[<c01037e3>] error_code+0x2b/0x30
[<c013f2af>] zap_pte_range+0x13f/0x280
[<c013f439>] zap_pmd_range+0x49/0x70
[<c013f49d>] zap_pgd_range+0x3d/0x70
[<c013f4fb>] unmap_page_range+0x2b/0x40
[<c013f600>] unmap_vmas+0xf0/0x1f0
[<c014399b>] exit_mmap+0x6b/0x120
[<c0116431>] mmput+0x41/0xd0
[<c011a2db>] do_exit+0x15b/0x420
[<c011a616>] do_group_exit+0x36/0x70
[<c0122b0b>] get_signal_to_deliver+0x1bb/0x2b0
[<c0102b76>] do_signal+0x66/0x120
[<c0102c69>] do_notify_resume+0x39/0x3c
[<c0102daa>] work_notifysig+0x13/0x15
Bad page state at prep_new_page (in process 'mpd', page c17712c0)
flags:0x40020114 mapping:00000000 mapcount:-1 count:0
Backtrace:
[<c0103b57>] dump_stack+0x17/0x20
[<c0136352>] bad_page+0x72/0xb0
[<c013669b>] prep_new_page+0x2b/0x80
[<c0136d8b>] buffered_rmqueue+0xcb/0x170
[<c0136ffd>] __alloc_pages+0x11d/0x340
[<c013925c>] do_page_cache_readahead+0xcc/0x120
[<c0139476>] page_cache_readahead+0x1c6/0x1f0
[<c0132ecb>] do_generic_mapping_read+0x11b/0x630
[<c013361d>] __generic_file_aio_read+0x16d/0x1e0
[<c0133784>] generic_file_read+0x94/0xc0
[<c014e6f1>] vfs_read+0x101/0x140
[<c014e99d>] sys_read+0x3d/0x70
[<c0102d0d>] sysenter_past_esp+0x52/0x71
Trying to fix it up, but a reboot is needed
Regards,
Benoit
[-- Attachment #2: config.gz --]
[-- Type: application/x-gunzip, Size: 7688 bytes --]
[-- Attachment #3: output of lspci -vv --]
[-- Type: text/plain, Size: 10478 bytes --]
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80)
Subsystem: ASUSTeK Computer Inc. A7V8X motherboard
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR+
Latency: 0
Region 0: Memory at f0000000 (32-bit, prefetchable)
Capabilities: [80] AGP version 3.5
Status: RQ=32 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3+ Rate=x4,x8,x@
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: d7000000-d7ffffff
Prefetchable memory behind bridge: d8000000-efffffff
Expansion ROM at 0000d000 [disabled] [size=4K]
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:09.0 Ethernet controller: 3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12)
Subsystem: ASUSTeK Computer Inc. P4P800 Mainboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (5750ns min, 7750ns max), cache line size 08
Interrupt: pin A routed to IRQ 177
Region 0: Memory at d6800000 (32-bit, non-prefetchable)
Region 1: I/O ports at b800 [size=256]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] Vital Product Data
0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
Subsystem: ASUSTeK Computer Inc. A7V600 motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Interrupt: pin A routed to IRQ 0
Region 0: I/O ports at b400
Region 1: I/O ports at b000 [size=4]
Region 2: I/O ports at a800 [size=8]
Region 3: I/O ports at a400 [size=4]
Region 4: I/O ports at a000 [size=16]
Region 5: I/O ports at 9800 [size=256]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. A7V600 motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Interrupt: pin A routed to IRQ 169
Region 4: I/O ports at 9400 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600 motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, cache line size 08
Interrupt: pin A routed to IRQ 0
Region 4: I/O ports at 9000 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600 motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, cache line size 08
Interrupt: pin A routed to IRQ 0
Region 4: I/O ports at 8800 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600 motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, cache line size 08
Interrupt: pin B routed to IRQ 0
Region 4: I/O ports at 8400 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600 motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, cache line size 08
Interrupt: pin B routed to IRQ 0
Region 4: I/O ports at 8000 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. A7V600 motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, cache line size 08
Interrupt: pin C routed to IRQ 0
Region 0: Memory at d6000000 (32-bit, non-prefetchable)
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:10.5 Network controller: VIA Technologies, Inc. VT8237 Integrated Fast Ethernet Controller
Subsystem: VIA Technologies, Inc. VT8237 Integrated Fast Ethernet Controller
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32, cache line size 08
Interrupt: pin D routed to IRQ 240
Region 0: Memory at d5800000 (32-bit, non-prefetchable) [disabled]
Capabilities: [80] Power Management version 2
Flags: PMEClk+ DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800 South]
Subsystem: ASUSTeK Computer Inc. A7V600 motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Subsystem: ASUSTeK Computer Inc. A7V600 motherboard (ADI AD1980 codec [SoundMAX])
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin C routed to IRQ 185
Region 0: I/O ports at e000
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) (prog-if 00 [VGA])
Subsystem: Hightech Information System Ltd.: Unknown device 2012
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (2000ns min), cache line size 08
Interrupt: pin A routed to IRQ 193
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=e7fe0000]
Region 1: I/O ports at d800 [size=256]
Region 2: Memory at d7800000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at 00020000 [disabled]
Capabilities: [58] AGP version 3.0
Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
0000:01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (Secondary) (rev 01)
Subsystem: Hightech Information System Ltd.: Unknown device 2013
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (2000ns min), cache line size 08
Region 0: Memory at d8000000 (32-bit, prefetchable) [disabled]
Region 1: Memory at d7000000 (32-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.10-rc2-mm3 [was: Re: 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"]
2004-11-30 15:06 ` 2.6.10-rc2-mm3 [was: Re: 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"] Benoit Boissinot
@ 2004-12-01 0:49 ` Hugh Dickins
2004-12-01 1:10 ` Andrea Arcangeli
0 siblings, 1 reply; 6+ messages in thread
From: Hugh Dickins @ 2004-12-01 0:49 UTC (permalink / raw)
To: Benoit Boissinot; +Cc: Linux Kernel, Andrew Morton, Mike Kirk
On Tue, 30 Nov 2004, Benoit Boissinot wrote:
>
> I had the same BUG_ON with 2.6.10-rc2-mm3 while transcoding a video.
>
> kernel BUG at mm/rmap.c:479!
> CPU: 0
> EIP: 0060:[<c01454a4>] Not tainted VLI
> EFLAGS: 00010286 (2.6.10-rc2-mm3-arakou)
> EIP is at page_remove_rmap+0x34/0x40
...
> BUG: atomic counter underflow at:
> [<c0103b57>] dump_stack+0x17/0x20
> [<c011a51e>] do_exit+0x39e/0x420
> [<c0103efc>] die+0x13c/0x140
...
> Bad page state at prep_new_page (in process 'mpd', page c17712c0)
> flags:0x40020114 mapping:00000000 mapcount:-1 count:0
> Backtrace:
> [<c0103b57>] dump_stack+0x17/0x20
> [<c0136352>] bad_page+0x72/0xb0
> [<c013669b>] prep_new_page+0x2b/0x80
Thanks for the report. I'm still searching for something useful
to say. I've recently spent several days trying to deduce what's
behind such page_remove_rmap BUGs, but not yet come up with any
convincing hypothesis. Yours is the first I've seen without
CONFIG_PREEMPT, so that's another potential culprit exonerated.
Some things which _might_ help me to shed more light on your case:
outputs of "objdump -rd" on your mm/memory.o, mm/rmap.o, kernel/exit.o;
and "cat /proc/$(pidof transcode)/maps" while transcode is running.
The atomic counter underflow in do_exit does suggest corruption
elsewhere than in transcode's page table (though I'm not at all
sure that is corrupt) - as always, it is worth giving memtest86
a thorough run to check your memory.
Thanks,
Hugh
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.10-rc2-mm3 [was: Re: 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"]
2004-12-01 0:49 ` Hugh Dickins
@ 2004-12-01 1:10 ` Andrea Arcangeli
2004-12-01 11:09 ` Benoit Boissinot
0 siblings, 1 reply; 6+ messages in thread
From: Andrea Arcangeli @ 2004-12-01 1:10 UTC (permalink / raw)
To: Hugh Dickins; +Cc: Benoit Boissinot, Linux Kernel, Andrew Morton, Mike Kirk
On Wed, Dec 01, 2004 at 12:49:39AM +0000, Hugh Dickins wrote:
> The atomic counter underflow in do_exit does suggest corruption
> elsewhere than in transcode's page table (though I'm not at all
> sure that is corrupt) - as always, it is worth giving memtest86
> a thorough run to check your memory.
Transcode should be 99% cpu bound in userspace and it shouldn't be
kernel intensive at all. It's one of the few desktop apps 99% cpu bound,
in turn the reasoning that the cpu is overheating sounds reasonable to
me. It might also be using sse2 to compress faster etc...
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.10-rc2-mm3 [was: Re: 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"]
2004-12-01 1:10 ` Andrea Arcangeli
@ 2004-12-01 11:09 ` Benoit Boissinot
0 siblings, 0 replies; 6+ messages in thread
From: Benoit Boissinot @ 2004-12-01 11:09 UTC (permalink / raw)
To: Andrea Arcangeli; +Cc: Hugh Dickins, Linux Kernel, Andrew Morton, Mike Kirk
On Wed, 1 Dec 2004 02:10:46 +0100, Andrea Arcangeli <andrea@suse.de> wrote:
> On Wed, Dec 01, 2004 at 12:49:39AM +0000, Hugh Dickins wrote:
> > The atomic counter underflow in do_exit does suggest corruption
> > elsewhere than in transcode's page table (though I'm not at all
> > sure that is corrupt) - as always, it is worth giving memtest86
> > a thorough run to check your memory.
>
> Transcode should be 99% cpu bound in userspace and it shouldn't be
> kernel intensive at all. It's one of the few desktop apps 99% cpu bound,
> in turn the reasoning that the cpu is overheating sounds reasonable to
> me. It might also be using sse2 to compress faster etc...
>
I just did a memtest86 and it reported errors. It looks like my
hardware is faulty here.
Sorry for the inconvenience.
regards,
Benoit
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-12-01 11:09 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-09-19 1:41 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!" Mike Kirk
2004-09-19 12:07 ` Hugh Dickins
2004-11-30 15:06 ` 2.6.10-rc2-mm3 [was: Re: 2.6.9-rc2: "kernel BUG at mm/rmap.c:473!"] Benoit Boissinot
2004-12-01 0:49 ` Hugh Dickins
2004-12-01 1:10 ` Andrea Arcangeli
2004-12-01 11:09 ` Benoit Boissinot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).