[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#499386: marked as done ([etch] NULL pointer dereference in sys_exit_group)

Your message dated Mon, 23 Apr 2012 04:21:14 -0500
with message-id <20120423092113.GB4832@burratino>
and subject line Re: [etch] NULL pointer dereference in sys_exit_group
has caused the Debian Bug report #499386,
regarding [etch] NULL pointer dereference in sys_exit_group
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
499386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499386
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-6-486
Version: 2.6.18.dfsg.1-22
Severity: important

After several cases of kernel panic which we blamed on just using old 
hardware, we caught this one in the log. The system is Etch, it serves as a 
firewall & dhcp server on one card, and the other is connected to an ADSL 
modem/router for uplink.

It seems this happened when the router temporarily disconnected from its 
uplink -- it took a minute or two after the firewall reboot to restore 
internet connectivity.

Please find attached the relevant log piece -- it ends with "reboot is 
needed!", and it wasn't kidding, the firewall froze about four minutes later; 
and also the relevant lspci -vv output.

I'm drafting the bug report by hand as reporbug and the services it requires 
don't belong on the firewall; if there's any more info I can give, please let 
me know.

Thanks,
	Shai.

Sep 18 10:56:01 tarante kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 00000045
Sep 18 10:56:01 tarante kernel:  printing eip:
Sep 18 10:56:01 tarante kernel: c0751ce0
Sep 18 10:56:01 tarante kernel: *pde = 00000000
Sep 18 10:56:01 tarante kernel: Oops: 0000 [#1]
Sep 18 10:56:01 tarante kernel: Modules linked in: ipt_LOG xt_tcpudp xt_multiport ipt_MASQUERADE iptable_nat xt_state ip6table_filter ip6_tables iptable_filter ip_tables x_tables ip_nat_tftp ip_nat_snmp_basic ip_nat_sip ip_nat_pptp ip_nat_irc ip_nat_h323 ip_nat_ftp ip_nat_amanda ip_conntrack_tftp ip_conntrack_sip ip_conntrack_proto_sctp ip_conntrack_pptp ip_conntrack_netlink ip_nat ip_conntrack_netbios_ns ip_conntrack_irc ip_conntrack_h323 ip_conntrack_ftp ts_kmp ip_conntrack_amanda ip_conntrack nfnetlink ipv6 dm_snapshot dm_mirror dm_mod parport_pc parport psmouse floppy rtc serio_raw pcspkr evdev ext3 jbd ide_generic ide_cd cdrom ide_disk piix generic ide_core 8139cp 8139too mii processor
Sep 18 10:56:01 tarante kernel: CPU:    0
Sep 18 10:56:01 tarante kernel: EIP:    0060:[<c0751ce0>]    Not tainted VLI
Sep 18 10:56:01 tarante kernel: EFLAGS: 00010083   (2.6.18-5-486 #1) 
Sep 18 10:56:01 tarante kernel: EIP is at 0xc0751ce0
Sep 18 10:56:01 tarante kernel: eax: c18bde2c   ebx: c18bde2c   ecx: 00000000   edx: 00000003
Sep 18 10:56:01 tarante kernel: esi: c100de04   edi: 00000001   ebp: c10a5e80   esp: c10a5e60
Sep 18 10:56:01 tarante kernel: ds: 007b   es: 007b   ss: 0068
Sep 18 10:56:01 tarante kernel: Process named (pid: 1812, ti=c10a4000 task=c1b5e030 task.ti=c10a4000)
Sep 18 10:56:01 tarante kernel: Stack: c01114ed 00000000 00000003 c18bdeb8 00c000ff 00000246 c1be93b4 c1b5e030 
Sep 18 10:56:01 tarante kernel:        c10a5e94 c0112414 00000000 00000000 c1be9380 c10a5ec8 c0115a84 0000000b 
Sep 18 10:56:01 tarante kernel:        c1b5e030 00000000 c0116c3c 0000000b bfc5e6e4 c10a5f14 c1b5e030 0000000b 
Sep 18 10:56:02 tarante kernel: Call Trace:
Sep 18 10:56:02 tarante kernel:  [<c01114ed>] __wake_up_common+0x2e/0x4d
Sep 18 10:56:02 tarante kernel:  [<c0112414>] complete+0x1f/0x28
Sep 18 10:56:02 tarante kernel:  [<c0115a84>] exit_mm+0x57/0xa3
Sep 18 10:56:02 tarante kernel:  [<c0116c3c>] do_exit+0x18e/0x65f
Sep 18 10:56:02 tarante kernel:  [<c0117169>] sys_exit_group+0x0/0xd
Sep 18 10:56:02 tarante kernel:  [<c011d91c>] get_signal_to_deliver+0x310/0x320
Sep 18 10:56:02 tarante kernel:  [<c0102219>] do_notify_resume+0x70/0x5ab
Sep 18 10:56:02 tarante kernel:  [<c0274ef4>] schedule+0x46e/0x4d2
Sep 18 10:56:02 tarante kernel:  [<c0102ade>] work_notifysig+0x13/0x25
Sep 18 10:56:02 tarante kernel: Code: 81 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 63 07 00 00 00 00 00 00 da 8b d1 48 00 00 00 00 81 47 ec 45 00 00 00 00 <3e> d3 b1 45 00 00 00 00 0c 00 00 00 00 10 00 00 01 00 00 00 08 
Sep 18 10:56:02 tarante kernel: EIP: [<c0751ce0>] 0xc0751ce0 SS:ESP 0068:c10a5e60
Sep 18 10:56:02 tarante kernel:  <1>Fixing recursive fault but reboot is needed!

00:00.0 Host bridge: Intel Corporation 430VX - 82437VX TVX [Triton VX] (rev 02)
	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

00:07.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
	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

00:07.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] (prog-if 80 [Master])
	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
	Region 4: I/O ports at f000 [size=16]

00:11.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (rev 54) (prog-if 00 [VGA])
	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 A routed to IRQ 12
	Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=64M]
	[virtual] Expansion ROM at 10000000 [disabled] [size=64K]

00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. RT8139
	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 (8000ns min, 16000ns max)
	Interrupt: pin A routed to IRQ 12
	Region 0: I/O ports at 6100 [size=256]
	Region 1: Memory at e4000000 (32-bit, non-prefetchable) [size=256]
	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-

00:14.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. RT8139
	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 (8000ns min, 16000ns max)
	Interrupt: pin A routed to IRQ 12
	Region 0: I/O ports at 6200 [size=256]
	Region 1: Memory at e4001000 (32-bit, non-prefetchable) [size=256]
	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-

--- End Message ---
--- Begin Message --- 
Shai Berger wrote:
> On Monday, April 23, 2012 10:40:22 AM Jonathan Nieder wrote:

>>  - did you ever figure out what was causing the kernel panics?  was
>>    there a workaround or fix?
>>  - was the backtrace always the same when the bug was encountered?
[...]
> * In most kernel crashes, I could find nothing in the log.
> * I never figured out the cause, or a workaround preventing the crashes.

I'm closing this now but if you have logs of the same backtrace
appearing multiple times or it ever happens again, we'd be happy to
revisit it.

Thanks for the quick feedback.

Sincerely,
Jonathan

--- End Message ---
Reply to: