Dear Maintainer, i've installed the package and at the next reboot the system stopped the bootprocess with: [ ok ] Setting parameters of disc: (none). ^[[24;2R if i press strg+c on the serial console the bootprocess run's again ... first following message is ... activating swap. if i change the kernel cmdline to start withou serial console booting runs without errors. normally i use the following cmdline for the kernel: (console=tty0 console=ttyS0,57600n8) changed to (console=tty0) works, but i need the serial line. If i remove/purge bootlogd booting runs without errors. the archived Bug #522211 describes the same problem. i think it's an critical bug.
What's the root cause of the problem here? Why does the boot block here? What is strg-c (Control-C?)? This is definitely a serious bug if bootlogd is installed by default, but I think it's strictly optional. Still, it would be ideal if the bug is fixable. Regards, Roger
What's the root cause of the problem here? Why does the boot block here? What is strg-c (Control-C?)? This is definitely a serious bug if bootlogd is installed by default, but I think it's strictly optional. Still, it would be ideal if the bug is fixable. Regards, Roger
Am 22.12.2012 16:58, schrieb Roger Leigh: yes, (strg+c) is the german version of (control+c) i've pasted an copy of the Output of the console from the serial line at pastebin: http://paste.debian.net/218305/ and attach the bootlog at this email: i suppose it has something to to with an buffer ... but i've no experience with this.
I managed to get my machine to boot again by adding "init=/bin/bash" as kernel parameter, and then mount -o remount,rw / chmod -x /etc/init.d/bootlogd What I don't understand is: root@(none):/# /etc/rcS.d/S03mountdevsubfs.sh start root@(none):/# /etc/rcS.d/S04bootlogd start root@(none):/# /etc/rcS.d/S05keymap.sh start ▒ ^[[24;2R I could start bootlogd manually without problems. The bootprocess hang on S05keymap.sh start But removing bootlogd fixed it anyway. Ingo
Hello, I can confirm that the bug is still there. We experienced it now and then. Was not easy to find out it was bootlogd. # update-rc.d bootlogd disable made the system come back to normal. After fixing another daemon that produce strange output, re-enabling of bootlogd was possible and all worked again. Best Jan
I know this has been waiting for a long time... This looks the same as #514253. Reassigning to console-common. Mark
I know this has been waiting for a long time... This looks the same as #514253. Reassigning to console-common. Mark