public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Martin Dalecki <dalecki@evision-ventures.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.20 hardlock w/ hdparm
Date: Mon, 17 Jun 2002 15:31:56 +0200	[thread overview]
Message-ID: <3D0DE4CC.9010901@inet6.fr> (raw)
In-Reply-To: Pine.LNX.4.44.0206150948140.30400-100000@netfinity.realnet.co.sz

Zwane Mwaikambo wrote:

>Hi Lionel, Martin,
>2.5.20, hdparm + IDE deadlocks on my testbox
>  
>

I don't follow 2.5 dev (yet). I merely follow Andre's work on 2.4 and 
code a new chipset capabilities detection code in order to support newer 
 chipsets.
Is the v0.13 driver driver already forward ported to 2.5 by somebody ?
If there's a need (some 2.5 developpers needing a more uptodate driver 
and uncomfortable with forward porting IDE chipset drivers), I'll do it...

>kernel:Linux version 2.5.20+prempt (zwane@montezuma.mastecende.com) (gcc version
>2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #24 SMP Wed Jun 5 21:48:07 SAST 2002
>
>ata subsys:
>ATA/ATAPI device driver v7.0.0
>ATA: PCI bus speed 33.3MHz
>ATA: Silicon Integrated Systems [SiS] 5513 [IDE], PCI slot 00:00.1
>PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try using pci=biosirq.
>ATA: chipset rev.: 208
>ATA: non-legacy mode: IRQ probe delayed
>SiS620
>

Unless the SiS620 is not compatable with the 630 IDE support spec or 
affected by some bugs I corrected for PIO mode timings (unlikely as they 
were unnoticed for a quiet long time) since sis5513.c v0.11 this should 
not be an IDE chipset problem.

>[...] btw Martin you seem to like pain so get ready for when i whip out the old 
>Quantum mavericks, 486 (SiS) and Opti621 card ;)
>  
>

Hum, 486 SiS chipsets might bring pain to me also...
I've received several bugreports for old SiS IDE chipset (ie pre ATA66) 
that I couldn't solve without disabling the SiS driver or passing 
"ide=nodma". I've triple-checked the specs and couldn't see the problem.

>Thanks,
>	Zwane Mwaikambo
>  
>
LB


  parent reply	other threads:[~2002-06-17 13:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-15  7:54 2.5.20 hardlock w/ hdparm Zwane Mwaikambo
2002-06-15  9:36 ` Bartlomiej Zolnierkiewicz
2002-06-15  9:18   ` Zwane Mwaikambo
2002-06-17 13:31 ` Lionel Bouton [this message]
2002-06-17 14:02   ` Martin Dalecki
2002-06-17 15:05   ` Zwane Mwaikambo

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=3D0DE4CC.9010901@inet6.fr \
    --to=lionel.bouton@inet6.fr \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linux.realnet.co.sz \
    /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