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

Bug#449024: marked as done (linux-image-2.6.18-5-amd64: general protection fault)

Your message dated Sun, 28 Dec 2008 04:04:42 +0100
with message-id <20081228030441.GA19357@galadriel.inutil.org>
and subject line Re: Voltage spike
has caused the Debian Bug report #449024,
regarding linux-image-2.6.18-5-amd64: general protection fault
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.)


-- 
449024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449024
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-5-amd64
Version: 2.6.18.dfsg.1-13etch4
Severity: critical
Justification: breaks the whole system

I am running a content filtering caching proxy server (Dansguardian + Squid). 
After a day of successful run in production (not so much load - 8 local PCs), server suddenly hanged with the following error message on console: 
Pid: 3888, comm: dansguardian Not tainted 2.6.18-5-amd64 #1
Server stopped responding to the pings and I could not ssh into the server.
The server runs on Intel Pentium 4 CPU 3.00GHz with 1G of RAM.

Here is a part of the log file, related to the problem:

Nov  2 17:08:56 office kernel: general protection fault: 0000 [1] SMP
Nov  2 17:08:56 office kernel: CPU 0
Nov  2 17:08:56 office kernel: Modules linked in: ipv6 button ac battery xt_tcpudp iptable_nat ip_nat ip_conntrack nfnetlink iptable_filter 
ip_tables x_tabl
es reiserfs loop evdev psmouse serio_raw i2c_i801 i2c_core intel_agp pcspkr ext3 jbd mbcache dm_mirror dm_snapshot dm_mod sd_mod 8139cp generic e100 
8139too
 mii ata_piix libata scsi_mod piix ide_core ehci_hcd uhci_hcd thermal processor fan
Nov  2 17:08:56 office kernel: Pid: 3888, comm: dansguardian Not tainted 2.6.18-5-amd64 #1
Nov  2 17:08:56 office kernel: RIP: 0010:[<ffffffff8022d5d7>]  [<ffffffff8022d5d7>] do_sys_poll+0x1b7/0x36d
Nov  2 17:08:56 office kernel: RSP: 0018:ffff81000ccd1b98  EFLAGS: 00010282
Nov  2 17:08:56 office kernel: RAX: e8ffffff80477a20 RBX: 0000000000000000 RCX: 0000000000000304
Nov  2 17:08:56 office kernel: RDX: ffff81003e752690 RSI: ffff81000ccd1f24 RDI: ffff81003f5f19c0
Nov  2 17:08:56 office kernel: RBP: ffff81003e95c844 R08: ffff81000ccd0000 R09: ffff810015b6da08
Nov  2 17:08:56 office kernel: R10: 00000000ffffffff R11: ffffffff8022e14f R12: ffff81003f5f19c0
Nov  2 17:08:56 office kernel: R13: ffff81003e95c800 R14: ffff81000ccd1f78 R15: 0000000000000000
Nov  2 17:08:56 office kernel: FS:  00002b5debd14cf0(0000) GS:ffffffff80521000(0000) knlGS:0000000000000000
Nov  2 17:08:56 office kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Nov  2 17:08:56 office kernel: CR2: 0000000007c1cf28 CR3: 000000002cedd000 CR4: 00000000000006e0
Nov  2 17:08:56 office kernel: Process dansguardian (pid: 3888, threadinfo ffff81000ccd0000, task ffff810036202770)
Nov  2 17:08:56 office kernel: Stack:  00000000045d9180 00000000045d9548 0000000100000001 ffff81000ccd1e18
Nov  2 17:08:56 office kernel:  ffff81000ccd1e18 ffff81003e95cae4 ffffffff8021c719 ffff8100399fd000
Nov  2 17:08:56 office kernel:  0000000a00000000 ffff810037b2cc80 0000000000000000 ffff810036202770
Nov  2 17:08:56 office kernel: Call Trace:
Nov  2 17:08:56 office kernel:  [<ffffffff8021c719>] __pollwait+0x0/0xe0
Nov  2 17:08:56 office kernel:  [<ffffffff8027c917>] default_wake_function+0x0/0xe
Nov  2 17:08:56 office last message repeated 10 times
Nov  2 17:08:56 office kernel:  [<ffffffff80247e65>] sys_poll+0x38/0x3f
Nov  2 17:08:56 office kernel:  [<ffffffff80257b56>] system_call+0x7e/0x83
Nov  2 17:08:56 office kernel:
Nov  2 17:08:56 office kernel:
Nov  2 17:08:56 office kernel: Code: 48 8b 40 38 48 85 c0 74 0c 4c 89 fe 4c 89 e7 ff d0 89 c2 eb
Nov  2 17:08:56 office kernel: RIP  [<ffffffff8022d5d7>] do_sys_poll+0x1b7/0x36d
Nov  2 17:08:56 office kernel:  RSP <ffff81000ccd1b98>

Thank you!

Best regards,
Meder

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-5-amd64 depends on:
ii  coreutil 5.97-5.3                        The GNU core utilities
ii  debconf  1.5.11                          Debian configuration management sy
ii  e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib
ii  initramf 0.85h                           tools for generating an initramfs
ii  module-i 3.3-pre4-2                      tools for managing Linux kernel mo

linux-image-2.6.18-5-amd64 recommends no packages.

-- debconf information:
  linux-image-2.6.18-5-amd64/postinst/create-kimage-link-2.6.18-5-amd64: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-5-amd64/postinst/old-system-map-link-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/initrd-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/preinst/elilo-initrd-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/postinst/depmod-error-2.6.18-5-amd64: false
  linux-image-2.6.18-5-amd64/preinst/bootloader-initrd-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/prerm/removing-running-kernel-2.6.18-5-amd64: true
* linux-image-2.6.18-5-amd64/preinst/already-running-this-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/preinst/lilo-initrd-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/abort-overwrite-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/preinst/failed-to-move-modules-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/prerm/would-invalidate-boot-loader-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/postinst/bootloader-error-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/postinst/old-initrd-link-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/overwriting-modules-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/postinst/old-dir-initrd-link-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-5-amd64/postinst/depmod-error-initrd-2.6.18-5-amd64: false
  linux-image-2.6.18-5-amd64/postinst/bootloader-test-error-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/postinst/kimage-is-a-directory:
  linux-image-2.6.18-5-amd64/preinst/abort-install-2.6.18-5-amd64:

--- End Message ---
--- Begin Message --- 
On Tue, Dec 23, 2008 at 08:14:22PM +0600, ?????????????? ?????????? wrote:
> Today I have caught another oops. Now it happened with the 2.6.24 based 
> kernel. I think I have found the root cause of the problem. It seems to be 
> because of voltage spikes. I don't know if it is a bad power unit, or non-ECC 
> memory module (I will give another memory check), but this oops happened after 
> the voltage spike. Here is the log snippets:

Thanks, closing the bug since the error is caused by a hardware failure.

Cheers,
        Moritz

--- End Message ---
Reply to: