From: Matt Domsch <Matt_Domsch@dell.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Olaf Hering <olaf@aepfle.de>, jurriaan <thunder7@xs4all.nl>,
linux-kernel@vger.kernel.org
Subject: Re: wanted: more informative message if root device can't be found/mounted
Date: Sat, 11 Nov 2006 08:11:26 -0600 [thread overview]
Message-ID: <20061111141126.GB16744@lists.us.dell.com> (raw)
In-Reply-To: <1163246257.3293.11.camel@laptopd505.fenrus.org>
On Sat, Nov 11, 2006 at 12:57:37PM +0100, Arjan van de Ven wrote:
> On Sat, 2006-11-11 at 12:44 +0100, Olaf Hering wrote:
> > On Sat, Nov 11, jurriaan wrote:
> >
> > > kernel panic - unable to mount root device 09:02
> >
> > These numbers are the root cause.
> > Use mount by filesystem UUID. On-disk content does unlikely change.
> > And if it does, you have to reconfigure the bootloader anyway.
> >
> > All this luxury doesnt belong into the kernel.
>
> one thing that we should consider is to not panic(). Panic() tends to
> cause the backscroll capability to go away.. which is rather useful to
> see what went wrong for this scenario...
+1. To the untrained eye, "kernel panic" gets filed as a Sev 1 issue
by end users and testers alike, when most often it's a system
configuration error rather than a kernel bug.
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2006-11-11 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 8:52 wanted: more informative message if root device can't be found/mounted jurriaan
2006-11-11 11:44 ` Olaf Hering
2006-11-11 11:57 ` Arjan van de Ven
2006-11-11 14:11 ` Matt Domsch [this message]
2006-11-11 14:41 ` Dr. David Alan Gilbert
2006-11-13 16:03 ` Phillip Susi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061111141126.GB16744@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=thunder7@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox