From: Ola Leifler <olale@ida.liu.se>
To: linux-kernel@vger.kernel.org
Cc: Ola Leifler <olale@ida.liu.se>
Subject: Re: PROBLEM: siimage.o on AMD768 platform
Date: Tue, 16 Dec 2003 10:04:22 +0100 [thread overview]
Message-ID: <3FDECA96.8050603@ida.liu.se> (raw)
In-Reply-To: <3FDEC5BE.2070200@ida.liu.se>
Ola Leifler wrote:
> Hi!
> [Formatted according to
> http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html]
> 1. Brief description:
> My Silicon Image 3112A controller doesn't recognize any of the two
> Seagate 7200.7 80Gb discs attached to it. Neither do the ide2/ide3
> interfaces show up in /proc, according to the information below.
>
> 2. Full description:
> When using siimage.o to access a dual channel Serial ATA controller
> with a Silicon Image 3112 chipset, none of the two hard discs are
> detected (No program can access /dev/hd[e-h]). However, the module
> refuses to unload (device busy). During boot, the card BIOS lists
> both discs.
Some additional information which may or may not be of any assistance to
Andre or Alan:
There doesn't seem to be any device on interrupt 19 though lspci -vvv
suggested that.
# cat /proc/interrupts
CPU0 CPU1
0: 234977 236815 IO-APIC-edge timer
1: 6117 6152 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
8: 3 1 IO-APIC-edge rtc
12: 87594 88013 IO-APIC-edge PS/2 Mouse
14: 9 20 IO-APIC-edge ide0
15: 204 269 IO-APIC-edge ide1
16: 179228 178555 IO-APIC-level nvidia
17: 15291 15367 IO-APIC-level sym53c8xx, eth0, CMI8738-MC6
18: 19569 19540 IO-APIC-level eth1
NMI: 0 0
LOC: 471710 471740
ERR: 0
MIS: 0
# cat /proc/devices
Character devices:
1 mem
2 pty/m%d
3 pty/s%d
4 tts/%d
5 cua/%d
7 vcs
10 misc
14 sound
21 sg
89 i2c
116 alsa
128 ptm
136 pts/%d
162 raw
195 nvidia
Block devices:
1 ramdisk
3 ide0
8 sd
11 sr
22 ide1
65 sd
66 sd
/Ola
prev parent reply other threads:[~2003-12-16 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 8:43 PROBLEM: siimage.o on AMD768 platform Ola Leifler
2003-12-16 9:04 ` Ola Leifler [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=3FDECA96.8050603@ida.liu.se \
--to=olale@ida.liu.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.