From: nicholas black <dank@trellisinc.com>
To: linux-kernel@vger.kernel.org
Cc: Lionel Bouton <Lionel.Bouton@inet6.fr>
Subject: Re: sis 5591 ide in 2.4.19-pre3 consumes souls
Date: Thu, 21 Mar 2002 12:18:51 -0500 (EST) [thread overview]
Message-ID: <20020321171851.A0D29A3C21@fancypants.trellisinc.com> (raw)
In-Reply-To: <3C9A0C22.3090702@inet6.fr>
In article <3C9A0C22.3090702@inet6.fr> you wrote:
> There's definitely a problem with some UDMA 33 chipsets. I'll ask SiS
> for 5591 chipset info RSN and look into this as soon as I find some time.
i look forward to it :). in light of this problem (i've recieved mail from
one michal dorocinski echoing this behavior and referencing an -ac patch; i've
asked him to mail it here), will this driver stay in .19 for the time being?
> Could you send us the output of "lspci -vxxx" with 2.4.18-jl11 and boot
> logs of 2.4.19-pre3-jl11 please ?
i shall do as much tonight, when i'm at the machine.
> Did you "make oldconfig" on the 2.4.19-pre3-jl11 sources with the your
> old 2.4.18-jl11 .config or made a new config from scratch ?
of course; i don't have time for the latter :). i just recreated this, and
here were applicable questions from oldconfig, and my responses:
no to auto-geometry resizing support
no to ide taskfile access
no to force enable legacy hosts to dma
no to dma only
no to noop elevator
the previous setup enabled generic pci ide chipsets, sharing of pci ide
interrupts, generic pci bus-master, use dma by default, and sis5513. nothing
else regarding ide chipset support/bugfixes is enabled.
> If so assuming you didn't modify your source trees could you send us the
> result of :
> diff <2.4.18-jl11_tree>/.config <2.4.19-pre3-jl11_tree>/.config | grep
> "^. CONFIG"
using said simulated .configs:
[ouzo](1) $ diff linux-2.4.18/.config linux-2.4.19-pre3/.config | grep "^.
CONFIG"
> CONFIG_X86_MCE=y
< CONFIG_PACKET_MMAP_FILTER=y
< CONFIG_BLK_DEV_ADMA=y
> CONFIG_BLK_DEV_ADMA=y
[ouzo](0) $
one other perhaps relevant piece of information: this is not the finest hard
drive in the world; some months ago i broke off the grounding 40 pin. that
line of the ide cable is now spliced off, and wrapped around a screw :).
--
nicholas black (dank@trellisinc.com)
"c has types for a reason. c++ improved the type system for a reason. perl
and php programs have run-time failures for a reason." - lkml
next prev parent reply other threads:[~2002-03-21 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 16:04 nicholas black
2002-03-21 16:36 ` Lionel Bouton
2002-03-21 17:18 ` nicholas black [this message]
2002-03-21 17:27 ` Michal Dorocinski
2002-04-02 13:17 ` Michal Dorocinski
2002-04-02 13:47 ` Lionel Bouton
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=20020321171851.A0D29A3C21@fancypants.trellisinc.com \
--to=dank@trellisinc.com \
--cc=Lionel.Bouton@inet6.fr \
--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®