From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Török Edwin" <edwintorok@gmail.com>,
linux-next@vger.kernel.org,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"Vegard Nossum" <vegard.nossum@gmail.com>,
"Andreas Herrmann" <andreas.herrmann3@amd.com>,
"ACPI Devel Maling List" <linux-acpi@vger.kernel.org>
Subject: Re: today's linux-next fails to boot
Date: Sat, 12 Jul 2008 06:47:07 +0200 [thread overview]
Message-ID: <20080712044707.GA6675@elte.hu> (raw)
In-Reply-To: <200807120250.16459.rjw@sisk.pl>
* Rafael J. Wysocki <rjw@sisk.pl> wrote:
> Hi Ingo,
>
> On Friday, 11 of July 2008, Rafael J. Wysocki wrote:
> > On Friday, 11 of July 2008, Ingo Molnar wrote:
> > >
> > > * Rafael J. Wysocki <rjw@sisk.pl> wrote:
> [--snip--]
> >
> > Well, it turns out that linux-next from today doesn't boot on my box too
> > (64-bit) and I don't see anything obviously suspicious. Bisection time.
>
> I have identified the source of the breakage on my box, but I don't
> really think it's the same problem that Edwin is observing.
>
> Namely, it turns out that some code in arch/x86/kernel/acpi/boot.c, as
> in today's linux-next, doesn't really make sense, because we have two
> conflicting DMA-based quirks in there for the same set of boxes (HP
> nx6325 and nx6125) and one of them actually breaks my box.
>
> I have reported that already, but it probably got lost somewhere.
>
> Below is a patch that fixes things for me, on top of today's
> linux-next. Please apply.
thanks Rafael, i have applied your fix to tip/x86/core and to
auto-x86-next as well.
what happened is a case of too many fixes for the same problem :-/
Ingo
next prev parent reply other threads:[~2008-07-12 4:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 11:12 today's linux-next fails to boot Török Edwin
2008-07-11 13:03 ` Takashi Iwai
2008-07-12 15:03 ` Takashi Iwai
2008-07-11 13:13 ` Török Edwin
2008-07-11 13:59 ` Ingo Molnar
2008-07-11 14:48 ` Török Edwin
2008-07-11 14:53 ` Ingo Molnar
2008-07-11 15:10 ` Rafael J. Wysocki
2008-07-11 19:07 ` Ingo Molnar
2008-07-11 21:06 ` Rafael J. Wysocki
2008-07-12 0:50 ` Rafael J. Wysocki
2008-07-12 4:47 ` Ingo Molnar [this message]
2008-07-11 14:54 ` Vegard Nossum
2008-07-11 14:54 ` Vegard Nossum
2008-07-11 15:00 ` Vegard Nossum
2008-07-11 15:00 ` Vegard Nossum
2008-07-11 15:27 ` Török Edwin
2008-07-16 21:11 ` Thomas Meyer
2008-07-16 21:57 ` Frédéric Weisbecker
2008-07-11 13:04 ` Takashi Iwai
2008-07-11 13:36 ` Vegard Nossum
2008-07-11 13:36 ` Vegard Nossum
2008-07-15 2:11 ` Frédéric Weisbecker
2008-07-15 11:06 ` Takashi Iwai
2008-07-15 11:15 ` Bernhard Walle
2008-07-15 11:17 ` Bernhard Walle
2008-07-15 11:53 ` Takashi Iwai
2008-07-15 12:02 ` Bernhard Walle
[not found] ` <c62985530807150800l4f34a6a3m22d58d66316c1e09@mail.gmail.com>
2008-07-15 15:14 ` Bernhard Walle
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=20080712044707.GA6675@elte.hu \
--to=mingo@elte.hu \
--cc=andreas.herrmann3@amd.com \
--cc=edwintorok@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
--cc=vegard.nossum@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 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.