From: Frank van Maarseveen <frankvm@frankvm.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.20*: PATA DMA timeout, hangs (2)
Date: Mon, 12 Mar 2007 14:25:46 +0100 [thread overview]
Message-ID: <20070312132546.GC12265@janus> (raw)
In-Reply-To: <200703121207.19042.s0348365@sms.ed.ac.uk>
On Mon, Mar 12, 2007 at 12:07:18PM +0000, Alistair John Strachan wrote:
> On Monday 12 March 2007 11:24, Frank van Maarseveen wrote:
> > On Mon, Mar 12, 2007 at 09:54:47AM +0100, Frank van Maarseveen wrote:
> > > 2.6.19 is ok, 2.6.20.[12] hangs from the moment DMA is turned on (hdparm
> > > -d 1 /dev/hda):
> > >
> > > hda: dma_timer_expiry: dma status == 0x20
> > > hda: DMA timeout retry
> > > hda: timeout waiting for DMA
> > > hda: status error: status=0x58 {
> > > DriveReady
> > > SeekComplete
> > > DataRequest
> > > }
> [snip]
> > This system has SATA but there's only one PATA disk
>
> Not a solution, unfortunately, but try disabling CONFIG_IDE and using Alan's
> new PATA drivers. For your Intel systems, this should mean you need only:
>
> CONFIG_ATA_PIIX
>
> For both SATA and PATA support. You'll need the appropriate SCSI modules built
> in (if you say =y), i.e. SCSI disk and SCSI CDROM should be built in.
yes, that worked... after booting with root=/dev/sda2 and s/hda/sda/
/etc/fstab /etc/lilo.conf + lilo. didn't mount a /dev/sr0 for a loong
time.
So, are /dev/hd* going to disappear in a few years? iow, does it make
sense to _slowly_ start to migrate to /dev/sd*?
The problem is there's no plan B in case of any troubles except rename
everything back again to boot an old kernel.
--
Frank
next prev parent reply other threads:[~2007-03-12 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 8:54 2.6.20*: PATA DMA timeout, hangs Frank van Maarseveen
2007-03-12 11:24 ` 2.6.20*: PATA DMA timeout, hangs (2) Frank van Maarseveen
2007-03-12 12:07 ` Alistair John Strachan
2007-03-12 13:25 ` Frank van Maarseveen [this message]
2007-03-12 13:52 ` Alistair John Strachan
2007-03-19 8:22 ` Tejun Heo
2007-03-12 12:21 ` Bartlomiej Zolnierkiewicz
2007-03-12 12:40 ` Frank van Maarseveen
2007-03-12 20:40 ` Bartlomiej Zolnierkiewicz
2007-03-13 9:19 ` Frank van Maarseveen
2007-03-13 11:04 ` Bartlomiej Zolnierkiewicz
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=20070312132546.GC12265@janus \
--to=frankvm@frankvm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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;
as well as URLs for NNTP newsgroup(s).