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

Bug#535440: marked as done ([REGRESSION] 2.6.30 fails to boot [amd64] )

Your message dated Tue, 25 Aug 2009 22:42:44 +0200
with message-id <20090825204244.GB28058@inutil.org>
and subject line Re: Works
has caused the Debian Bug report #535440,
regarding [REGRESSION] 2.6.30 fails to boot [amd64] 
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.)


-- 
535440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535440
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-1
Severity: critical

This kernel fails to boot on my computer.. I have a whole screen of backtrace info. It is not saved in the syslog. I wrote down some of the lines.

[	6.230405]	[<ffffffff8023411b>]	?	wakeup_preempt_system+0x91/0x9e
....
[	6.231010]	<EOI>	[<ffffffff8031e7>]	?	cap_inode_alloc_security+0x0/0x3
....
[	6.231300]	[<ffffffff8020fa42]	?	system_call_fastpath+0x16/0x1b

2.6.29 works.

-- Package-specific info:

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable-i386
  APT policy: (500, 'unstable-i386'), (500, 'transitional-i386'), (500, 'transitional'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-2-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.30-1-amd64 depends on:
ii  debconf [debconf-2.0]         1.5.26     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93.3     tools for generating an initramfs
ii  module-init-tools             3.9-2      tools for managing Linux kernel mo

linux-image-2.6.30-1-amd64 recommends no packages.

Versions of packages linux-image-2.6.30-1-amd64 suggests:
ii  grub                          0.97-53    GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.30              <none>     (no description available)

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

--- End Message ---
--- Begin Message --- 
Version: 2.6.30-2

On Thu, Jul 09, 2009 at 10:22:49PM +0200, Nicolas DEGAND wrote:
> Latest upgrade of the kernel seems to have fixed the problem.

Thanks for the feedback, marking as closed.

Cheers,
        Moritz

--- End Message ---
Reply to: