From: Martin Zwickel <martin.zwickel@technotrend.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-mm3: SIS5513 DMA problem (set_drive_speed_status)
Date: Tue, 22 Mar 2005 09:47:01 +0100 [thread overview]
Message-ID: <20050322094701.1d17b401@phoebee> (raw)
In-Reply-To: <20050314211755.5e686c50.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Mon, 14 Mar 2005 21:17:55 -0800
Andrew Morton <akpm@osdl.org> bubbled:
> Martin Zwickel <martin.zwickel@technotrend.de> wrote:
> >
> > Hi,
> >
> > just tried the 2.6.11-mm3 and at boot-time my start scripts try to
> > enable DMA on my disk (hdparm -m16 -c1 -u1 -X69 /dev/hda).
> >
> > But while running hdparm, the kernel waits many seconds and gives me
> > some DMA warnings/errors:
> >
> > ...
> >
> > hda: set_drive_speed_status: status=0xd0 { Busy }
> >
> > ide: failed opcode was: unknown
> > hda: dma_timer_expiry: dma status == 0x41
> > hda: DMA timeout error
> > hda: dma timeout error: status=0xd0 { Busy }
> > ...
> >
> > That happened also with 2.6.11-rc3 since I thought I should switch
> > away from my 2.6.8-rc2-mm1 (the best kernel ever ;)).
>
> Could you please check whether 2.6.11-rc1 does this? It should be
> released mid-week. Thanks.
ps.: just booted 2.6.12-rc1-mm1 and hdparm works now much better on boot
than 2.6.11-mm3. ;)
--
MyExcuse:
We're upgrading /dev/null
Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-22 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 15:15 2.6.11-mm3: SIS5513 DMA problem (set_drive_speed_status) Martin Zwickel
2005-03-15 5:17 ` Andrew Morton
2005-03-15 9:27 ` Martin Zwickel
2005-03-22 8:47 ` Martin Zwickel [this message]
2005-03-22 1:22 ` Andrew Morton
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=20050322094701.1d17b401@phoebee \
--to=martin.zwickel@technotrend.de \
--cc=akpm@osdl.org \
--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