From: Erik Andersen <andersen@codepoet.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Philippe Lochon <plochon.n0spam@free.fr>, linux-kernel@vger.kernel.org
Subject: Re: P4C800E-Dlx: ICH5/S-ATA and Intel Pro onboard network incompatibility ?
Date: Mon, 6 Oct 2003 01:03:24 -0600 [thread overview]
Message-ID: <20031006070324.GA10474@codepoet.org> (raw)
In-Reply-To: <3F80B68D.8090109@pobox.com>
On Sun Oct 05, 2003 at 08:25:49PM -0400, Jeff Garzik wrote:
> Erik Andersen wrote:
> >When I have the Bios set to compatible mode everything works --
> >except for the obvious problem that I have to put my SATA drive
> >onto my promise SATA card (since the ICH5 SATA is disabled).
> >
> >When I have the Bios set to Enhanced mode (so the ICH5 provides
> >both SATA and PATA) then my system will wedge solid as a rock.
> >
> >It turns out it was locking up while loading up the ide-scsi
> >kernel module. I have
> >
> > options ide-cd ignore='hdc'
>
>
> So, things work in Enchanced mode if ide-scsi module is not loaded?
After a bit more testing.... loading either ide-scsi or
ide-cd is sufficient to lock my system dead dead dead if
the bios is set to Enhanced mode.
After _not_ loading ide-scsi or ide-cd I was able to boot in
Enhanced mode. I think I am getting some sortof wierd interrupt
storm. Everything freezes for a few second every so often...
Here is what I am seeing.
$ uptime
00:51:41 up 25 min, 3 users, load average: 0.04, 0.10, 0.07
$ cat /proc/interrupts
CPU0 CPU1
0: 152450 0 IO-APIC-edge timer
1: 5334 0 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
8: 4 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
12: 36125 0 IO-APIC-edge PS/2 Mouse
16: 105720 0 IO-APIC-level usb-uhci, usb-uhci, radeon@PCI:1:0:0
17: 0 0 IO-APIC-level Intel ICH5
18: 175250680 2019 IO-APIC-level ide0, ide1, libata, usb-uhci
19: 0 0 IO-APIC-level usb-uhci
22: 90380 0 IO-APIC-level SysKonnect SK-98xx, bttv
23: 0 0 IO-APIC-level ehci_hcd
NMI: 0 0
LOC: 156771 156777
ERR: 0
MIS: 2019
I have a P4 with hyperthreading so my kernel is SMP. The huge
number of interrupts on 18 (I'm not doing very much beyong ssh to
another box to write this email) looks suspicious to me.
> And, drivers/ide is picking up your PATA devices as expected?
yes.
> As a tangent, I wonder if the latest cdrecord works in 2.4 with
> 'dev=/dev/hdc' ... that would elimiante the need for ide-scsi.
I'll check...
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2003-10-06 7:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 14:44 P4C800E-Dlx: ICH5/S-ATA and Intel Pro onboard network incompatibility ? Philippe Lochon
2003-10-04 18:03 ` Erik Andersen
2003-10-04 19:25 ` Jeff Garzik
2003-10-04 19:27 ` Jeff Garzik
2003-10-04 19:53 ` Erik Andersen
2003-10-05 20:16 ` Erik Andersen
2003-10-06 0:25 ` Jeff Garzik
2003-10-06 7:03 ` Erik Andersen [this message]
2003-10-06 7:52 ` Jens Axboe
2003-10-10 1:00 ` Greg Stark
2003-10-10 1:06 ` Erik Andersen
2003-10-10 1:26 ` Greg Stark
2003-10-04 20:07 ` ph75
-- strict thread matches above, loose matches on Subject: below --
2003-10-06 13:46 Daniel Blueman
2003-10-08 18:53 P4C800E-Dlx: ICH5/S-ATA and Intel Pro onboard network incompatibility? Jon Burgess
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=20031006070324.GA10474@codepoet.org \
--to=andersen@codepoet.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plochon.n0spam@free.fr \
/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