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

Bug#433597: marked as done (linux-image-2.6.18-4-amd64: Panic with CR2: 0000000000100108 on SATA with software raid-1)



Your message dated Sun, 29 Jun 2008 18:44:49 +0200
with message-id <20080629164449.GC11284@stro.at>
and subject line re: linux-image-2.6.18-4-amd64: Panic with CR2: 0000000000100108 on SATA with software raid-1
has caused the Debian Bug report #433597,
regarding linux-image-2.6.18-4-amd64: Panic with CR2: 0000000000100108 on SATA with software raid-1
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.)


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

The problem only happened to me once, and before my last upgrade (with
version 2.6.18.dfsg.1-12), but the changelog does not seem to indicate
that this problem was solved, so I'm opening the bug report anyways.

The machine is running two SATA disks with Raid-1 and LVM. This seems to
be relevant to some of the internet discussions I found, though not all
of them.

I was connected to the machine over SSH (a remote machine) when I got
the following messages:
Message from syslogd@fiasco at Tue Jul 17 22:10:04 2007 ...
fiasco kernel: Oops: 0002 [1] SMP

Message from syslogd@fiasco at Tue Jul 17 22:10:04 2007 ...
fiasco kernel: CR2: 0000000000100108

After that, no user space program would interact with me, but pings
still worked. The machine was rebooted by the hosting company, and now
seem to be functioning again.

Searching the internet I found two discussions that may be relevant. One
is http://lists.openwall.net/linux-kernel/2006/11/04/69, which includes
a patch, and the other is http://lkml.org/lkml/2006/1/4/196. Since the
machine has been up for almost a year before this problem happened, and
from the version numbers and frequencies mentioned by Linus, I believe
that the first link contains the solution to this problem.

Thanks,
Shachar

-- 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-4-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=he_IL (charmap=ISO-8859-8)

Versions of packages linux-image-2.6.18-4-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.85g                           tools for generating an initramfs
ii  module-i 3.3-pre4-2                      tools for managing Linux kernel mo

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

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


--- End Message ---
--- Begin Message ---
Version: 2.6.24-1

no evidence that the seen oops corresponds to 
http://lists.openwall.net/linux-kernel/2006/11/04/69

also not really a backport fix if not yet done,
please checkout etch + half 2.6.24 kernel
http://wiki.debian.org/EtchAndAHalf

-- 
maks


--- End Message ---

Reply to: