public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Johnson <livewire@gentoo.org>
To: <lk@trolloc.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: siimage driver status
Date: Fri, 30 May 2003 16:44:12 -0500	[thread overview]
Message-ID: <200305301644.14880.livewire@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0305301156510.17286-100000@ip-64-7-1-79.dsl.lax.megapath.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


This is the exact problem i have with onboard siimage (asus a7n8x)
 or a siimage controller card on a abit motherboard. (kt7a)

echo "max_kb_per_request:15" > /proc/ide/hde/settings
is a work around for 2.4.XX.

				Bob

> I get two console messages before the machine locks hard:
> hde: dma_timer_expiry: dma status == 0x22
> hde: dma_timer_expiry status = 0xd8 { Busy }
>
> I'd love to get this tracked down...
>
>
> Brian.
>
> -----------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+19CuxJgsCy9JAX0RArvcAJ9JdNeIAGCcDvrSSqvam6XgPklm9ACfSPx5
M+JgErtFM9OoqP/6yZuMxnQ=
=q97p
-----END PGP SIGNATURE-----


  reply	other threads:[~2003-05-30 21:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 14:32 siimage driver status Wm. Josiah Erikson
2003-05-29 13:54 ` Alan Cox
2003-05-29 15:00   ` Wm. Josiah Erikson
2003-05-29 14:56     ` Alan Cox
2003-05-29 19:32       ` Wm. Josiah Erikson
2003-05-29 22:26   ` Gutko
2003-06-03  7:17     ` Marco Tedaldi
2003-06-03 12:43       ` Alan Cox
2003-06-03 14:11       ` Wm. Josiah Erikson
2003-06-03 13:49         ` Alan Cox
2003-06-03 15:07           ` Wm. Josiah Erikson
2003-06-03 15:13           ` Bob Johnson
2003-06-03 15:29             ` Wm. Josiah Erikson
2003-06-03 15:58               ` Bob Johnson
2003-06-03 14:45         ` Justin Cormack
2003-05-30 18:57   ` lk
2003-05-30 21:44     ` Bob Johnson [this message]
2003-05-29 15:00 ` lk
  -- strict thread matches above, loose matches on Subject: below --
2003-05-31  9:34 Inigo Surguy
2003-06-04 17:23 Rob Browning

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=200305301644.14880.livewire@gentoo.org \
    --to=livewire@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@trolloc.com \
    /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