Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: status for Marvell Orion support



On Tue, Jan 26, 2010 at 10:11:33PM +1300, Mark Davies wrote:
> On Monday 25 January 2010 07:24:48 you wrote:
> > > I'm trying to get a kurobox pro going with a current -current and the
> > > most recent patch set from kiyohara and I'm still seeing this panic. 
> > > Any suggestions how to track it down?
> > 
> > The problem is in the md code. What IDE controller is it; does it use
> > a MD attachement, or does it sit on a ISA or PCI bus ?
> 
> Here are the relevant bits of the dmesg output.
> 
> mvsata0 at mvsoc0 offset 0x80000-0x87fff irq 29: Marvell Serial-ATA Host 
> Controller (SATAHC)
> mvsata0: GenIIe, 1hc, 2port/hc
> atabus0 at mvsata0 channel 0
> atabus1 at mvsata0 channel 1
>    [...]
> mvsata0 port 0: device present, speed: 3.0Gb/s
> wd0 at atabus0 drive 0: <ST380819AS>
> wd0: drive supports 16-sector PIO transfers, LBA48 addressing
> wd0: 76293 MB, 155009 cyl, 16 head, 63 sec, 512 bytes/sect x 156250000 
> sectors
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
> wd0(mvsata0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using 
> DMA)

OK, so the issue could be in mvsoc as well.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--


Home | Main Index | Thread Index | Old Index