public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Greg KH <gregkh@suse.de>, Marcos Pinto <markybob@gmail.com>,
	linux-kernel@vger.kernel.org, Jan Beulich <jbeulich@novell.com>,
	Alan Cox <alan@redhat.com>,
	linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: 2.6.20.7 locking up hard on boot
Date: Sat, 21 Apr 2007 14:44:03 +0200	[thread overview]
Message-ID: <200704211444.03365.bzolnier@gmail.com> (raw)
In-Reply-To: <20070421103632.GC4016@stusta.de>


On Saturday 21 April 2007, Adrian Bunk wrote:
> On Fri, Apr 20, 2007 at 10:34:20PM -0700, Greg KH wrote:
> > On Fri, Apr 20, 2007 at 11:30:59PM -0500, Marcos Pinto wrote:
> > >  Yes, I just tried 2.6.20.3 with ACPI enabled and it booted perfectly.
> > >  I'm hoping this means you know what's wrong? :-)
> > 
> > Can you do a 'git bisect' on the versions between 2.6.20.3 and 2.6.20.7
> > to try to find the problem patch?
> 
> Considering where it failed and that 2.6.20.3 worked, I would be 
> extremely surprised if this wasn't one more report of 
> adjust-legacy-ide-resource-setting.patch breaking booting (and we 
> already have confirmed reports for this)...
> 
> But AFAIK we still don't understand how this patch managed to break 
> things.

Same here but 2.6.21 is near and we need to do something about this issue.

I'm thinking about reverting this patch for 2.6.21-final - having broken
X server is better than having broken and not booting kernel.

Jan, Alan?

Thanks,
Bart

  parent reply	other threads:[~2007-04-21 12:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-21  0:47 2.6.20.7 locking up hard on boot Marcos Pinto
2007-04-21  1:34 ` Adrian Bunk
2007-04-21  4:30   ` Marcos Pinto
2007-04-21  5:34     ` Greg KH
2007-04-21 10:36       ` Adrian Bunk
2007-04-21 10:54         ` Marcos Pinto
2007-04-22  2:00           ` Len Brown
2007-04-21 12:44         ` Bartlomiej Zolnierkiewicz [this message]
2007-04-23  8:06         ` Jan Beulich
2007-04-23 22:58           ` Marcos Pinto
2007-04-24 19:11             ` Marcos Pinto

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=200704211444.03365.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@redhat.com \
    --cc=bunk@stusta.de \
    --cc=gregkh@suse.de \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=markybob@gmail.com \
    /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