From: Carlo Calica <ccalica@gmail.com>
To: Paul Blazejowski <paulb@blazebox.homeip.net>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, xorg@lists.freedesktop.org
Subject: Re: 2.6.14-rc2-mm1
Date: Wed, 28 Sep 2005 12:07:59 -0700 [thread overview]
Message-ID: <b41d010d05092812079475644@mail.gmail.com> (raw)
In-Reply-To: <20050928045630.GA9960@blazebox.homeip.net>
On 9/27/05, Paul Blazejowski <paulb@blazebox.homeip.net> wrote:
> No 2.6.12 is not OK. I don't think there's any regression between the
> recent kernels. It just does not work on 3 of them i tried so far.
>
Another data point:
I'm unable to reproduce on a PATA install. Specifically, booting on a
PATA HD with sata_nv as a module. When booting on a SATA HD with
sata_nv compiled in, I get the race. Setting irq 1,5 (keyboard and
libata) handlers to cpu0 affinity and X affinity to cpu0 solves the
problem.
I haven't had time to try booting SATA with sata_nv as a module in initrd.
--
Carlo J. Calica
next prev parent reply other threads:[~2005-09-28 19:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 22:00 2.6.14-rc2-mm1 Paul Blazejowski
2005-09-25 23:44 ` 2.6.14-rc2-mm1 Andrew Morton
2005-09-26 4:32 ` 2.6.14-rc2-mm1 Carlo Calica
2005-09-28 4:56 ` 2.6.14-rc2-mm1 Paul Blazejowski
2005-09-28 19:07 ` Carlo Calica [this message]
2005-09-26 7:14 ` 2.6.14-rc2-mm1 Tim Schmielau
2005-09-28 5:01 ` 2.6.14-rc2-mm1 Paul Blazejowski
-- strict thread matches above, loose matches on Subject: below --
2005-09-22 5:28 2.6.14-rc2-mm1 Andrew Morton
2005-09-22 6:35 ` 2.6.14-rc2-mm1 Joel Becker
2005-09-22 6:46 ` 2.6.14-rc2-mm1 Reuben Farrelly
2005-09-22 7:03 ` 2.6.14-rc2-mm1 Andrew Morton
2005-09-22 18:59 ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-22 19:52 ` 2.6.14-rc2-mm1 Andrew Morton
2005-09-22 20:14 ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-23 0:28 ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-24 17:43 ` 2.6.14-rc2-mm1 Mattia Dongili
2005-09-24 17:58 ` 2.6.14-rc2-mm1 Mattia Dongili
2005-09-24 18:23 ` 2.6.14-rc2-mm1 Andrew Morton
2005-09-26 19:33 ` 2.6.14-rc2-mm1 Seth, Rohit
2005-09-27 18:57 ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 20:05 ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27 21:18 ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 21:51 ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27 21:59 ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 22:49 ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27 22:49 ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 23:16 ` 2.6.14-rc2-mm1 Rohit Seth
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=b41d010d05092812079475644@mail.gmail.com \
--to=ccalica@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulb@blazebox.homeip.net \
--cc=xorg@lists.freedesktop.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