https://bugzilla.novell.com/show_bug.cgi?id=327601 User atolboo@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=327601#c54 Antoon Tolboom <atolboo@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|atolboo@hotmail.com | --- Comment #54 from Antoon Tolboom <atolboo@hotmail.com> 2008-04-02 07:25:04 MST --- Before trying the /etc/pm/config.d/config file I retested the "'powersave -U' from root-shell" (comment #48). To my surprise the behaviour from my first description could not be reproduced (see also comment #48). I tested this 5 times. Going into hibernation the ZZ screen with the progressionbar stops at 15% from the right, and the powerled stays on. After activating the reset button (this is the only possibility) a normal coldstart is performed (no blue 'Resume from Hibernation' screen). On this PC I still have Suse 10.2 with kernel 2.6.18.8-0.9-default (I will not remove this as long as this bug is open). To exclude behaviourchange with hardware I retested hibernation with 10.2. a number(5x?) of times It passed without any problems. I decided to do a new 10.3 installation from DVD + all updates. The kernel has now changed from 2.6.22.13-0.3-default (comment #42) to 2.6.22.17-0.1-default The hibernation behaviour is still the above mentioned '15% progressionbar ZZ' screen. Tested 5 times. After this I modified /boot/grub/menu.lst (see comment #15) to do a minimal systemtest. The result is the same as in attachment 'Behaviour of suspend to disk with no kernelpanic' (including the attempt to put it into hibernation for the second time). In comment #15 I wrote: To repeat the test I had to start in fullsystem(KDE) mode and then in minimalsystem mode. But not this time. It always (minimal and KDE-mode) ends with: Waiting for device /dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L50LYG1G-part12 to appear: ok fsck 1.40.2 (12-Jul-2007) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L50LYG1G-part12 SUSE10.3GM (/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L50LYG1G-part12: recovering journal SUSE10.3GM (/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L50LYG1G-part12: clean, 128880/669120 files, 785072/1337403 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L50LYG1G-part12 kjournald starting. Commit interval 5 seconds EXT3 FS on sda12, internal journal EXT3-fs: mounted filesystem with ordered data mode. /bin/run-init: /bin/sh: Permission denied Kernel panic - not syncing: Attempted to kill init! And I am not able to end this 'Kernel panic' situation. Is there a way to end this situation? I will do a new installation and then apply the /etc/pm/config.d/config file and restart testing. I hope I do not have to do a new installation every time I get in a 'Kernel panic' situation. So the behaviour has changed and gone from bad to worse. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.