From: Mikael Pettersson <mikpe@csd.uu.se>
To: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Cc: martin@dalecki.de, linux-kernel@vger.kernel.org
Subject: Re: 2.5.31 boot failure on pdc20267
Date: Thu, 15 Aug 2002 22:13:09 +0200 [thread overview]
Message-ID: <15708.2901.701484.171663@kim.it.uu.se> (raw)
In-Reply-To: <217C4D61227@vcnet.vc.cvut.cz>
Petr Vandrovec writes:
> On 15 Aug 02 at 17:15, Mikael Pettersson wrote:
> > Booting 2.5.31 (non-bk) on hde5, a UDMA(66) Quantum Fireball
> > on a PDC20267 add-on card, resulted in a complete hang as init
> > came to its "mount -n -o remount,rw /" point. No visible messages
> > or anything in the log.
>
> Known bug. Apply IDE113 (Aug 06, 11:02 CEST, from Martin), or just open
> drivers/ide/pcidma.c in your favorite text editor, look for (first)
> #ifdef CONFIG_BLK_DEV_TRM290, and replace whole ifdef block with
> '*--table |= cpu_to_le32(0x80000000);'
Tested. First time 2.5.31 + the patch booted it seemed to work, but hung
later on while compiling a 2.4.19 kernel. No messages of any kind. The
hang _seemed_ to coincide with the console screen blanker kicking in.
Second boot went ok and I made sure the screen blanker wouldn't kick
in while doing the compile, and it didn't hang.
This box is the only one so far I've seen this problem on, my other
Intel chipset boxes actually seem to work fairly well with 2.5.31.
/Mikael
next prev parent reply other threads:[~2002-08-15 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 15:34 2.5.31 boot failure on pdc20267 Petr Vandrovec
2002-08-15 20:13 ` Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-16 9:48 Petr Vandrovec
2002-08-16 10:10 ` Andre Hedrick
2002-08-16 9:21 Petr Vandrovec
2002-08-16 9:27 ` Andre Hedrick
2002-08-15 15:15 Mikael Pettersson
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=15708.2901.701484.171663@kim.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
/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