public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "CSÉCSY László" <boobaa@frugalware.org>
Cc: "Don Zickus" <dzickus@redhat.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	aris@redhat.com, peterz@infradead.org,
	"Ingo Molnar" <mingo@elte.hu>,
	"VAJNA Miklós" <vmiklos@frugalware.org>,
	linux-kernel@vger.kernel.org,
	"Steven Rostedt" <rostedt@goodmis.org>
Subject: Re: 2.6.36 does not boot properly
Date: Mon, 13 Dec 2010 18:04:49 +0300	[thread overview]
Message-ID: <4D063611.7010908@gmail.com> (raw)
In-Reply-To: <201012130019.41234.boobaa@frugalware.org>

On 12/13/2010 02:19 AM, CSÉCSY László wrote:
> Hi all,
> 
> I have recently upgraded from kernel-2.6.35-5-i686.fpm (which is a 2.6.35.7 
> speaking upstream's terms) to kernel-2.6.36-1-i686.fpm (which is a 2.6.36) on 
> my ASUS K50IJ laptop running Frugalware Linux -current, and it failed to boot 
> when I used the usual command line:
> 
> kernel (hd0,1)/boot/vmlinuz root=/dev/sda2 ro quiet resume=/dev/sda5
> 
> "Failed to boot" means that the thing does not even output even a single 
> character after "[Linux-bzImage, setup=0x3000, size=0x3c5380]" but hangs - 
> even C-A-Del does not do anything (I do have waited for half an hour). 
> Pressing the power button (it does not matter for how long) turns the laptop 
> off immediately.
> 
...

It's weird that bisect pointed to this nmi code snipped movement, I
think the issue in strcmp, and in event_create_dir. Better to
CC Steven.

-- 
    Cyrill

  reply	other threads:[~2010-12-13 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 23:19 2.6.36 does not boot properly CSÉCSY László
2010-12-13 15:04 ` Cyrill Gorcunov [this message]
2010-12-13 15:09 ` Don Zickus
2010-12-14  4:22 ` Len Brown

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=4D063611.7010908@gmail.com \
    --to=gorcunov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=aris@redhat.com \
    --cc=boobaa@frugalware.org \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vmiklos@frugalware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox