From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: chris2553@googlemail.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.30-rc8 Oops whilst booting
Date: Sun, 07 Jun 2009 18:55:40 +0530 [thread overview]
Message-ID: <1244381140.30664.12.camel@ht.satnam> (raw)
In-Reply-To: <200906062215.30571.chris2553@googlemail.com>
Hello Chris,
On Sat, 2009-06-06 at 22:15 +0100, Chris Clayton wrote:
> Sorry, I've just realised what a poor report my earlier email was. I should also have said that the
> kernel has booted succesfully. At the time of reporting I had had two panics. I've just done
> another git pull, so the kernel is bang up to date with kernel.org, but after building and
> installing, a reboot resulted in another panic. The system then booted OK after switch off and on
> again.
>
> Please cc me to any reply, I'm not subscribed.
>
>
> On Saturday 06 June 2009, Chris Clayton wrote:
> > Hi,
> >
> > After a git pull earlier today, I've had oopsen whilst booting the system
> > twice today: A photo of the oops message can be viewed at:
> >
> > http://img231.imageshack.us/img231/8931/dscn0610.jpg
> >
> > I haven't used the 2.6.30-rc kernels very much, so I don't have a clue when
> > the problem was introduced. I have no problems at all with 2.6.29.4.
> >
Can you provide your .config and dmesg of working and non-working
kernel.
Thanks,
--
JSR
next prev parent reply other threads:[~2009-06-07 13:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 18:59 2.6.30-rc8 Oops whilst booting Chris Clayton
2009-06-06 21:15 ` Chris Clayton
2009-06-07 13:25 ` Jaswinder Singh Rajput [this message]
2009-06-07 18:38 ` Chris Clayton
2009-06-07 22:31 ` Jaswinder Singh Rajput
2009-06-07 22:55 ` NeilBrown
2009-06-08 8:08 ` Chris Clayton
2009-06-08 8:08 ` Chris Clayton
2009-06-08 10:58 ` Chris Clayton
2009-06-08 10:58 ` Chris Clayton
2009-06-08 11:34 ` Jaswinder Singh Rajput
2009-06-08 12:53 ` Chris Clayton
2009-06-08 12:53 ` Chris Clayton
2009-06-08 16:21 ` Linus Torvalds
2009-06-08 16:21 ` Linus Torvalds
2009-06-08 16:51 ` James Bottomley
2009-06-08 17:06 ` Jaswinder Singh Rajput
2009-06-08 17:45 ` Chris Clayton
2009-06-08 17:45 ` Chris Clayton
2009-06-08 18:21 ` Linus Torvalds
2009-06-08 19:17 ` Chris Clayton
2009-06-08 19:17 ` Chris Clayton
2009-06-08 20:03 ` Chris Clayton
2009-06-08 20:03 ` Chris Clayton
2009-06-08 17:21 ` Linus Torvalds
2009-06-08 17:37 ` Arjan van de Ven
2009-06-08 17:38 ` James Bottomley
2009-06-08 17:06 ` James Bottomley
2009-06-08 17:42 ` Linus Torvalds
2009-06-08 17:49 ` James Bottomley
2009-06-08 18:33 ` Chris Clayton
2009-06-08 18:33 ` Chris Clayton
2009-06-08 14:23 ` James Bottomley
2009-06-08 15:04 ` Chris Clayton
2009-06-08 15:04 ` Chris Clayton
2009-06-08 15:17 ` Chris Clayton
2009-06-08 15:17 ` Chris Clayton
2009-06-08 15:32 ` James Bottomley
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=1244381140.30664.12.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=chris2553@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.