Your message dated Tue, 6 Mar 2018 22:31:10 +1100
with message-id <20180306113110.ga5...@enc.com.au>
and subject line Re: Bug#243438: snmpd causes kernel oops when poled
has caused the Debian Bug report #243438,
regarding snmpd causes kernel oops when poled
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 ow...@bugs.debian.org
immediately.)
--
243438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=243438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: snmpd
Version: 5.1.1-2
Severity: important
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.24-2-686-actusa
Locale: LANG=C, LC_CTYPE=C
Versions of packages snmpd depends on:
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libsensors1 2.6.5-4 Library to read temperature/voltag
ii libsnmp5 5.1.1-2 NET SNMP (Simple Network Managemen
ii libssl0.9.7 0.9.7d-1 SSL shared libraries
ii libwrap0 7.6-ipv6.1-3 Wietse Venema's TCP wrappers libra
-- no debconf information
Not sure the cause is snmpd, but that's what catched the oops. This began after
a reasonable large update to testing. Here is the oops...
Apr 12 19:21:20 reno-gw kernel: Unable to handle kernel NULL pointer dereference
at virtual address 000000ec
Apr 12 19:21:20 reno-gw kernel: printing eip:
Apr 12 19:21:20 reno-gw kernel: d0a764ea
Apr 12 19:21:20 reno-gw kernel: *pde = 00000000
Apr 12 19:21:20 reno-gw kernel: Oops: 0002
Apr 12 19:21:20 reno-gw kernel: CPU: 0
Apr 12 19:21:20 reno-gw kernel: EIP: 0010:[<d0a764ea>] Not tainted
Apr 12 19:21:20 reno-gw kernel: EFLAGS: 00010246
Apr 12 19:21:20 reno-gw kernel: eax: 00000000 ebx: cc2b3f68 ecx: 00000000
edx: cc2b3f04
Apr 12 19:21:20 reno-gw kernel: esi: 00000000 edi: cc2b3f14 ebp: cfe01800
esp: cc2b3ef4
Apr 12 19:21:20 reno-gw kernel: ds: 0018 es: 0018 ss: 0018
Apr 12 19:21:20 reno-gw kernel: Process snmpd (pid: 941, stackpage=cc2b3000)
Apr 12 19:21:20 reno-gw kernel: Stack: cc2b3f04 00000000 cc2b3f54 cf98c680 927cf
547 00000000 00000000 00000000
Apr 12 19:21:20 reno-gw kernel: 000089f0 cfe01800 cc2b3f54 cc2b3f54 c0224
7bf cfe01800 cc2b3f54 000089f0
Apr 12 19:21:20 reno-gw kernel: cc2b3f54 00000000 00000001 000089f0 c0224
9e1 cc2b3f54 000089f0 00000020
Apr 12 19:21:20 reno-gw kernel: Call Trace: [dev_ifsioc+975/1088] [dev_ioctl+
433/800] [sock_ioctl+38/48] [sys_ioctl+201/592] [sys_fstat64+73/128]
Apr 12 19:21:20 reno-gw kernel: [system_call+51/56]
Apr 12 19:21:20 reno-gw kernel:
Apr 12 19:21:20 reno-gw kernel: Code: ff 0d ec 00 00 00 0f 94 c0 84 c0 75 0a b8
fa ff ff ff e9 ff
Thanks
--- End Message ---
--- Begin Message ---
Hi,
This old bug report is for an old version of snmpd and is 14 years
old. kernel panics usually are reported against the kernel not the
binary that causes them, but in any case its for kernel 2.6
In any case, its ancient history, so I'll be closing the bug.
- Craig
--
Craig Small https://dropbear.xyz/ csmall at : enc.com.au
Debian GNU/Linux https://www.debian.org/ csmall at : debian.org
Mastodon: @smalls...@social.dropbear.xyz Twitter: @smallsees
GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
--- End Message ---
