From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: 101551.753@compuserve.com
Cc: linux-ide@vger.kernel.org
Subject: Re: [BUGREPORT 3/3] Kernel Oops with HPT372A IDE controller
Date: Wed, 17 May 2006 18:41:29 +0400 [thread overview]
Message-ID: <446B3619.9090909@ru.mvista.com> (raw)
In-Reply-To: <200605142111.42329.it21@arcor.de>
Hello.
Foli Ayivoh wrote:
> This is lspci -vvv from ubuntu 5 distro bootable CD-ROM with kernel 2.6.12-9-386
> 0000:01:08.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
> Subsystem: Creative Labs: Unknown device 2001
> 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-
Looks like the PCI bus in question was running at 33 MHz...
> 0000:01:0a.0 RAID bus controller: Triones Technologies, Inc. HPT372A (rev 02)
> Subsystem: Triones Technologies, Inc.: Unknown device 0001
> 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: 120 (2000ns min, 2000ns max)
> Interrupt: pin A routed to IRQ 16
> Region 0: I/O ports at 7c00 [size=8]
> Region 1: I/O ports at 8000 [size=4]
> Region 2: I/O ports at 8400 [size=8]
> Region 3: I/O ports at 8800 [size=4]
> Region 4: I/O ports at 8c00 [size=256]
> Capabilities: <available only to root>
Please send me the results of running 'lspci -xxx -s 1:a' as root; disable
the driver and rebuild/boot the kernel without it before doing this, so that I
can see what the regs look like as the BIOS leaves them, untainted by the
driver...
MBR, Sergei
prev parent reply other threads:[~2006-05-17 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 19:11 [BUGREPORT 3/3] Kernel Oops with HPT372A IDE controller Foli Ayivoh
2006-05-17 14:41 ` Sergei Shtylyov [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=446B3619.9090909@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=101551.753@compuserve.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).