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

Bug#449438: marked as done (linux-image-2.6.22-2-k7 kernel panic)

Your message dated Tue, 20 May 2008 20:24:48 +0200
with message-id <20080520182448.GH13383@stro.at>
and subject line Re: linux-image-2.6.22-2-k7 kernel panic
has caused the Debian Bug report #449438,
regarding linux-image-2.6.22-2-k7 kernel panic
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.)


-- 
449438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449438
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
debian:/home/mystified# dpkg --status linux-image-2.6.22-2-k7
Package: linux-image-2.6.22-2-k7
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 52584
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Architecture: i386
Source: linux-2.6
Version: 2.6.22-4
Provides: linux-image, linux-image-2.6, linux-modules-2.6.22-2-k7
Depends: module-init-tools (>= 0.9.13), initramfs-tools (>= 0.55) | yaird (>= 0.0.12-8) | linux-initramfs-tool 
Recommends: libc6-i686
Suggests: linux-doc-2.6.22, grub (>= 0.97-3) | lilo (>= 19.1)
Conflicts: grub (<= 0.95+cvs20040624-17), initramfs-tools (<< 0.55), yaird (<< 0.0.12-8) 
Description: Linux 2.6.22 image on AMD K7
This package provides the binary image and pre-built loadable modules for
Linux kernel 2.6.22 on 32bit AMD Duron/Athlon/AthlonXP/Sempron machines.

When I try to boot into this kernel I get a lot of errors which include:
/device/sys/blocks/sda/sda5/dev no such file or directory
/device/sys/blocks/sda/sda5/dev seems to be down
/bin/mknod missing operand after 'b'
kernel panic not synching

--- End Message ---
--- Begin Message --- 
closing as kernel never guaranteed stable device names.
use UUID to be on the safe side.

if they change you need to adjust bootparam of your bootloader
and fstab this can be done from rescue debian installer command
or from any life cd.

-- 
maks

--- End Message ---
Reply to: