From: Devilkin <Devilkin-LKML@blindguardian.org>
To: Alan Cox <alan@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-ac2
Date: Sun, 4 Aug 2002 20:57:57 +0200 [thread overview]
Message-ID: <200208042057.57130.Devilkin-LKML@blindguardian.org> (raw)
In-Reply-To: <200208041746.g74Hkgr24437@devserv.devel.redhat.com>
On Sunday 04 August 2002 19:46, Alan Cox wrote:
<snip>
There seems to be some problem with VIA IDE IRQ's on 2.4.19-ac2.
With 2.4.19-ac2 i get the following message in the logs:
PCI: No IRQ known for interrupt pin A of device 00:07.1. Please try using
pci=biosirq.
00:07.1 is the IDE Interface on my mainboard!
checking with lspci gives this output:
----------------
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) (prog-if
8f [Master SecP SecO PriP PriO])
Subsystem: VIA Technologies, Inc. Bus Master IDE
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Interrupt: pin A routed to IRQ 0
Region 0: I/O ports at <ignored>
Region 1: I/O ports at <ignored>
Region 2: I/O ports at <ignored>
Region 3: I/O ports at <ignored>
Region 4: I/O ports at d400 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
----------------
whereas with older kernels (2.4.19-ac1 and previous kernels) this error isn't
given, and lspci looks as follows:
----------------
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) (prog-if
8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. Bus Master IDE
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Region 4: I/O ports at d400 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
----------------
which somehow looks healthier.
I've reverted to -ac1 for now, which works fine on my box.
DK
next prev parent reply other threads:[~2002-08-04 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 17:46 Alan Cox
2002-08-04 18:57 ` Devilkin [this message]
2002-08-04 20:27 ` Alan Cox
2002-08-04 19:39 ` Daniela Engert
2002-08-04 21:01 ` Alan Cox
2002-08-05 10:21 ` Eric W. Biederman
2002-08-05 13:00 ` Alan Cox
2002-08-05 5:44 ` Clemens 'Gullevek' Schwaighofer
2002-08-04 21:24 Tony Spinillo
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=200208042057.57130.Devilkin-LKML@blindguardian.org \
--to=devilkin-lkml@blindguardian.org \
--cc=alan@redhat.com \
--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®