NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
port-i386/40697: kernel panic with VIA 6421 host adapter
>Number: 40697
>Category: port-i386
>Synopsis: kernel panic with VIA 6421 host adapter (5.0RC and -current)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: port-i386-maintainer
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Feb 20 10:40:00 +0000 2009
>Originator: Bernhard Moellemann
>Release: NetBSD 5.0_RC1 and -current from 20.2.2009
>Organization:
Home entertainment construction site
>Environment:
System: NetBSD arcanic 5.0_RC1 NetBSD 5.0_RC1 (GENERIC) #0: Tue Feb 3 11:46:51
CET 2009 root@arcanic:/mnt/top/src/src-5dm/obj/sys/arch/i386/compile/GENERIC
i386
Architecture: i386
Machine: i386
>Description:
The VIA VT6421 Serial RAID Controller is a combi controller featuring
two SATA ports and one PATA port. When connecting a disk (250 GB or 1397 GB)
or a DVD-RW to a SATA port, the kernel panics during autoconf:
cd0 at ...
fatal page fault in supervisor mode
trap type 6 code 0 eip c0660310 cs 8 eflags 10206 cr2 423033 ilevel 6
kernel: supervisor trap page fault, code=0
Stopped in pid 0.2 (system) at netbsd:bus_space_read_multi_stream_4+0x20:
m
ovl 0(%edx),%eax
This is with NetBSD 5.0RC1 from 3. Feb. 2009. A similar panic is
encountered with -current, but the machine boots and the panic
disappears to fast to be read and typed into a nearby computer.
The more helpful portions of the dmesg are:
NetBSD 5.0_RC1 (GENERIC) #0: Tue Feb 3 11:46:51 CET 2009
root@arcanic:/mnt/top/src/src-5dm/obj/sys/arch/i386/compile/GENERIC
total memory = 3071 MB
avail memory = 3004 MB
timecounter: Timecounters tick every 10.000 msec
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
FUJITSU SIEMENS MS-7504VP-PV (10601016878)
mainbus0 (root)
cpu0 at mainbus0 apid 0: Intel 686-class, 2333MHz, id 0x10677
cpu0: Enhanced SpeedStep (1228 mV) 700 MHz
cpu0: Enhanced SpeedStep frequencies available (MHz): 700 600
cpu1 at mainbus0 apid 1: Intel 686-class, 2333MHz, id 0x10677
cpu2 at mainbus0 apid 2: Intel 686-class, 2333MHz, id 0x10677
cpu3 at mainbus0 apid 3: Intel 686-class, 2333MHz, id 0x10677
[...]
pdcsata0 at pci1 dev 6 function 0
pdcsata0: Promise PDC40718 SATA300 controller (rev. 0x02)
LNKC: Picked IRQ 16 with weight 0
pdcsata0: interrupting at ioapic0 pin 16
pdcsata0: bus-master DMA support present
atabus0 at pdcsata0 channel 0
atabus1 at pdcsata0 channel 1
atabus2 at pdcsata0 channel 2
atabus3 at pdcsata0 channel 3
[The Promise is not the problem, but the last device probed before VIA]
pci_mem_find: expected type mem, found i/o
viaide0 at pci1 dev 7 function 0
viaide0: VIA Technologies VT6421 Serial RAID Controller (rev. 0x50)
viaide0: bus-master DMA support present
LNKD: Picked IRQ 17 with weight 0
viaide0: using ioapic0 pin 17 for native-PCI interrupt
viaide0: primary channel wired to native-PCI mode
atabus4 at viaide0 channel 0
viaide0: secondary channel wired to native-PCI mode
atabus5 at viaide0 channel 1
[...]
cd0 at ...
fatal page fault in supervisor mode
Note the "pci_mem_find: expected type mem, found i/o" message before the
first viaide0 line.
Here the relevant part of lspci -vvx
01:07.0 RAID bus controller: VIA Technologies, Inc.: Unknown device 3249 (rev
50)
Subsystem: VIA Technologies, Inc.: Unknown device 3249
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: 64
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at c480
Region 1: I/O ports at c400
Region 2: I/O ports at c080
Region 3: I/O ports at c000
Region 4: I/O ports at bc00
Region 5: I/O ports at b800
Capabilities: [e0] 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-
00: 06 11 49 32 07 00 90 02 50 00 04 01 00 40 00 00
10: 81 c4 00 00 01 c4 00 00 81 c0 00 00 01 c0 00 00
20: 01 bc 00 00 01 b8 00 00 00 00 00 00 06 11 49 32
30: 00 00 fb f9 e0 00 00 00 00 00 00 00 11 01 00 00
The cards BIOS finds SATA and PATA devices and reports them correctly.
As a side note: Devices at the PATA port are not recognized.
So the card is currently complete useless.
>How-To-Repeat:
Insert a card with VIA VT6421, connect a SATA device, boot *boom*
>Fix:
Not known.
Unhelpful Workaround: Do not connect any SATA device to VT6421
Bernhard //
\X/
Home |
Main Index |
Thread Index |
Old Index