mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: Diego Calleja <diegocg@teleline.es>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: hang in 2.4.18-rc2-ac1
Date: Thu, 21 Feb 2002 02:21:54 +0100	[thread overview]
Message-ID: <20020221022154.A6241@bouton.inet6-interne.fr> (raw)
In-Reply-To: <20020220192127.622006ff.diegocg@teleline.es> <E16dcvN-0004YR-00@the-village.bc.nu> <20020220213715.0a741080.diegocg@teleline.es>
In-Reply-To: <20020220213715.0a741080.diegocg@teleline.es>; from diegocg@teleline.es on Wed, Feb 20, 2002 at 09:37:15PM +0100

On Wed, Feb 20, 2002 at 09:37:15PM +0100, Diego Calleja wrote:

> [...
> Chipset is SIS 5571, ide chipset SIS 5513. I've some problems with
> latest updates about SIS Ide driver update: When I sleep the drive with
> hdparm -Y /dev/hda
> then the drive sleeps. But it doesn't 'awake'. I can do 'Login: XXX \n Password: XXX' or write a command
> in the shell. But when the unit has to read/write, it just does nothing.
> 
> Latest kernels without this patch (2.4.18-preX....) did something different:
> I could sleep drive normally. But when the system had to read/write something:
> 
> Feb 15 18:13:08 localhost kernel: hda: timeout waiting for DMA
> Feb 15 18:13:08 localhost kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> Feb 15 18:13:08 localhost kernel: hda: status timeout: status=0xd0 { Busy }
> Feb 15 18:13:08 localhost kernel: hda: drive not ready for command
> Feb 15 18:13:08 localhost kernel: ide0: reset: success
> 
> The system just stopped a few seconds, and then it started as always.
> [...]

I don't know anything about the SiS5571 yet, please send me your boot logs related
to SiS IDE (you can't miss them...). If you know what your chip
capabilities are (see your motherboard doc, ATA33/66/100 should
be printed somewhere if the chipset supports these ATA generations).
As the driver is not yet aware of this chip it defaults to
original SiS5513 behaviour, this is most probably the source of your problem.

LB.

      reply	other threads:[~2002-02-21  1:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020220211318.14f953dd.diegocg@teleline.es>
2002-02-20 18:21 ` Diego Calleja
2002-02-20 18:26   ` Mike Fedyk
2002-02-20 20:38     ` Diego Calleja
2002-02-20 20:01   ` Alan Cox
2002-02-20 20:37   ` Diego Calleja
2002-02-21  1:21     ` Lionel Bouton [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=20020221022154.A6241@bouton.inet6-interne.fr \
    --to=lionel.bouton@inet6.fr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=diegocg@teleline.es \
    --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

all inboxes | Powered by JetHome®