How to stop kernel rebooting during startup?
in [Kernel]
|
Prev: [PATCH 3/3] hpwdt: implement WDIOC_GETTIMELEFT
Next: [net-next-2.6 PATCH 1/2] skbuff: add check for non-linear to warn_if_lro and needs_linearize
From: Grant Coady on 2 Jun 2010 18:30 Hi there, Kernel has a problem mounting root, but it reboots before I can read the message. Of course nothing gets logged so I cannot see exactly why the kernel wants to reboot. Can I stop kernel doing an automatic reboot? How? It's version 2.6.33.5, .4 has same behaviour. Filesystem is Reiserfs, Intel ICH9R with Core2Duo, .config is on: http://bugsplatter.id.au/kernel/boxen/pooh64/config-2.6.33.5a.gz which worked fine on slackware64-13.0, has this behaviour on slack- ware64-13.1. Because I cannot read the screen before reboot, no idea where to look next, or what is actually happening. Thanks, Grant. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Bob Copeland on 2 Jun 2010 18:40 On Wed, Jun 2, 2010 at 6:20 PM, Grant Coady <gcoady.lk(a)gmail.com> wrote: > which worked fine on slackware64-13.0, has this behaviour on slack- > ware64-13.1. �Because I cannot read the screen before reboot, no idea > where to look next, or what is actually happening. Maybe try CONFIG_BOOT_PRINTK_DELAY to see the message? -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Randy Dunlap on 3 Jun 2010 13:20
On Wed, 2 Jun 2010 18:35:45 -0400 Bob Copeland wrote: > On Wed, Jun 2, 2010 at 6:20 PM, Grant Coady <gcoady.lk(a)gmail.com> wrote: > > which worked fine on slackware64-13.0, has this behaviour on slack- > > ware64-13.1. �Because I cannot read the screen before reboot, no idea > > where to look next, or what is actually happening. > > Maybe try CONFIG_BOOT_PRINTK_DELAY to see the message? That's one option. Can you alter the kernel command line (boot options)? like add: initcall_debug debug ignore_loglevel pause_on_oops=30 Sounds like it would also be good to have something like: reboot=hang|spin (TBD) --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |