From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Anssi Saari <as@sci.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: booting 2.6.7 hangs with IRQ handling problems
Date: Fri, 25 Jun 2004 21:06:03 +0200 [thread overview]
Message-ID: <200406252106.04029.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20040623180431.GA8963@sci.fi>
On Wednesday 23 of June 2004 20:04, Anssi Saari wrote:
> On Wed, Jun 23, 2004 at 05:48:33PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > On Tuesday 22 of June 2004 21:29, Anssi Saari wrote:
> > > Hello,
> >
> > Hi,
> >
> > > On my home PC I have an AMD Athlon XP 1900+ on an Aopen AK77-600Max
> > > motherboard, VIA KT600 chipset. It works fine with Linux 2.6.6, apart
> > > from the apparently nonexistent support for PATA devices on the Promise
> > > PDC20378, but I can't boot 2.6.7. I've tried vanilla 2.6.7, 2.6.7 with
> > > acpi-20040326 patch and 2.6.7-bk4. acpi=off, noapic or nolapic don't
> > > seem to help.
> >
> > Since 2.6.6 works and 2.6.7-bk4 doesn't can you try -bk1/2/3 and
> > do bisection search on specific changesets? Thanks!
>
> OK. I find that 2.6.6-bk1 seemed fine, but 2.6.6-bk2 already prints out
> these messages. It did boot, but then hanged shortly after. I hope this
> helps to narrow it down?
Does it hang the same way as 2.6.7?
There were no IDE changes between 2.6.6-bk1 and 2.6.6-bk2.
Can you do a diff between dmesg outputs from -bk1 and -bk2?
You can also try narrowing it down to a specific changeset
[ http://linux.bkbits.net:8080/linux-2.5/ ] but it can take a while.
Bartlomiej
next prev parent reply other threads:[~2004-06-25 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 19:29 Anssi Saari
2004-06-23 15:48 ` Bartlomiej Zolnierkiewicz
2004-06-23 18:04 ` Anssi Saari
2004-06-25 19:06 ` Bartlomiej Zolnierkiewicz [this message]
2004-06-26 18:10 ` Anssi Saari
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=200406252106.04029.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=as@sci.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®