From: Con Kolivas <kernel@kolivas.org>
To: ck@vds.kolivas.org
Cc: Joshua Schmidlkofer <kernel@pacrimopen.com>,
jch@imr-net.com,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Cliff Wells <clifford.wells@comcast.net>
Subject: Re: [ck] Re: 2.6.8.1-ck7, Two Badnessess, one dump.
Date: Sat, 14 Jan 2006 13:19:58 +1100 [thread overview]
Message-ID: <200601141319.59227.kernel@kolivas.org> (raw)
In-Reply-To: <4145BAE9.1040800@pacrimopen.com>
On Tuesday 14 September 2004 01:21, Joshua Schmidlkofer wrote:
> Con,
>
>
> I did not mention before, I thought it was a fluke on my system. Now
> its affecting two systems since applying ck7.
>
>
> <snip>
> hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
>
> ide: failed opcode was: unknown
> hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete
> DataRequest }ide: failed opcode was 100
> hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
>
> ide: failed opcode was: unknown
> hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete
> DataRequest }ide: failed opcode was 100
> hda: CHECK for good STATUS
> <snip>
>
> That is happening while applying the dma settings to the hard drive.
It's not a very informative message but probably just means the kernel is
complaining about what that (evil) program hdparm is trying to do. Anyway
this kernel is _ancient_. Please move to a newer one if you can (yes I
understand the reasons stick to older kernels so don't bother explaining them
- that's why I said "if you can").
Cheers,
Con
prev parent reply other threads:[~2006-01-14 2:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 4:02 2.6.8.1-ck7 Con Kolivas
2004-09-13 1:23 ` 2.6.8.1-ck7, Two Badnessess, one dump Joshua Schmidlkofer
2004-09-13 3:51 ` [ck] " Con Kolivas
2004-09-13 15:21 ` Joshua Schmidlkofer
2004-09-13 19:12 ` Jens Axboe
2004-09-14 3:45 ` Joshua Schmidlkofer
2004-09-15 7:21 ` Jens Axboe
2004-09-14 3:46 ` Joshua Schmidlkofer
2004-09-15 7:21 ` Jens Axboe
2006-01-14 2:19 ` Con Kolivas [this message]
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=200601141319.59227.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.kolivas.org \
--cc=clifford.wells@comcast.net \
--cc=jch@imr-net.com \
--cc=kernel@pacrimopen.com \
--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