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

Bug#365770: kernel panic with 2.6.16-12



On Tue, May 30, 2006 at 05:33:33PM +0200, maximilian attems wrote:
: 
: clone 365770 -1
: reassign -1 initramfs-tools
: retitle -1 swsusp boot panic
: stop
: 
: On Tue, May 30, 2006 at 05:02:15PM +0200, Roberto Lumbreras wrote:
: > I can confirm this bug. My box refuses to boot with
: > linux-image-2.6.16-1-686-smp version 2.6.16-12.
: 
: how about opening a proper bug report?
: instead of posting to unrelated bug report
: 365770 has no evidence of any error message yet.

ok

: > kernel-image-2.6.8-2-686-smp version 2.6.8-16sarge1 boots without a
: > problem.
: > 
: > The message is something like...
: > 
: > [raid1 devices started ok]
: > [lvm message about no volumes found, ok]
: > Begin: Running /scripts/local-premount ...
: > Attempting manual resume.
: > Kernel panic - not syncing: I/O error reading memory image
: 
: funny never seen that ;)
: care to send please the ouput of belows commands to the newly cloned
: bug report, thanks:
: cat /proc/cmdline
: cat /proc/mounts

$ cat /proc/cmdline
BOOT_IMAGE=Linux ro root=900
$ cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/md0 / ext3 rw,data=ordered 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/md0 /dev/.static/dev ext3 rw,data=ordered 0 0
tmpfs /dev tmpfs rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/md1 /home ext3 rw,nosuid,nodev,data=ordered 0 0
/dev/md2 /repo reiserfs rw,nosuid,nodev,noexec 0 0
/dev/hdd8 /extra reiserfs rw,nosuid,nodev,noexec 0 0
tmpfs /tmp tmpfs rw,nosuid 0 0
tmpfs /var/tmp tmpfs rw,nosuid 0 0

: > In directory scripts/local-premount of initrd.img it's only one script:
: > suspend.
: > 
: > Ideas?
: 
: not yet as you didn't provide lots of info,
: but looks like an b0rked swsusp image.

no swsups at all...

Salud,
-- 
Roberto Lumbreras           .''`.            
                    <rover : :' : debian.org>
Debian Developer           `. `'             
                             `-              



Reply to: