2.4.2-ac12 unknown southbridge

2.4.2-ac12 unknown southbridge

[Mike Galbraith]

Hi,

The driver forget what it always called a vt82c596b before.  Reverting
the below brought it back on-line, and all seems well again.  (hope I
don't receive any unpleasant suprises.. I've not the foggiest clue what
that number means;)

-	{ "vt82c596b",	PCI_DEVICE_ID_VIA_82C596,   0x12, 0x2f, VIA_UDMA_66 },
+	{ "vt82c596b",	PCI_DEVICE_ID_VIA_82C596,   0x10, 0x2f, VIA_UDMA_66 },

lspci -vvx

00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev 06)
	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: 0
	Region 0: Memory at e0000000 (32-bit, prefetchable) [size=64M]
	Capabilities: [a0] AGP version 1.0
		Status: RQ=7 SBA+ 64bit- FW- Rate=x1,x2
		Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
00: 06 11 91 06 06 00 90 a2 06 00 00 06 00 00 00 00
10: 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00

00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode])
	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: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: e8000000-e9ffffff
	Prefetchable memory behind bridge: e4000000-e7ffffff
	BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
00: 06 11 98 85 07 00 20 22 00 00 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 d0 d0 00 00
20: 00 e8 f0 e9 00 e4 f0 e7 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0c 00

00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 11)
	Subsystem: VIA Technologies, Inc. VT82C596/A/B PCI to ISA Bridge
	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: 0
00: 06 11 96 05 87 00 00 02 11 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
	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
	Region 4: I/O ports at e000 [size=16]
00: 06 11 71 05 07 00 80 02 06 8a 01 01 00 40 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00

00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 05) (prog-if 00 [UHCI])
	Subsystem: Unknown device 0925:1234
	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, cache line size 08
	Interrupt: pin D routed to IRQ 9
	Region 4: I/O ports at e400 [size=32]
00: 06 11 38 30 07 00 00 02 05 00 03 0c 08 40 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 e4 00 00 00 00 00 00 00 00 00 00 25 09 34 12
30: 00 00 00 00 00 00 00 00 00 00 00 00 09 04 00 00

00:07.3 Host bridge: VIA Technologies, Inc. VT82C596 Power Management (rev 20)
	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-
00: 06 11 51 30 00 00 80 02 20 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 RL (prog-if 00 [VGA])
	Subsystem: ATI Technologies Inc: Unknown device 0008
	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 (2000ns min), cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
	Region 1: I/O ports at d000 [size=256]
	Region 2: Memory at e9000000 (32-bit, non-prefetchable) [size=16K]
	Expansion ROM at e8000000 [disabled] [size=128K]
	Capabilities: [50] AGP version 2.0
		Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
		Command: RQ=0 SBA+ AGP- 64bit- FW- Rate=<none>
	Capabilities: [5c] Power Management version 1
		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 02 10 4c 52 a7 00 b0 02 00 00 00 03 08 40 00 00
10: 08 00 00 e4 01 d0 00 00 00 00 00 e9 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 08 00
30: 00 00 00 e8 50 00 00 00 00 00 00 00 0b 01 08 00

Re: 2.4.2-ac12 unknown southbridge

[Vojtech Pavlik]

On Tue, Mar 06, 2001 at 10:09:05AM +0100, Mike Galbraith wrote:

> The driver forget what it always called a vt82c596b before.  Reverting
> the below brought it back on-line, and all seems well again.  (hope I
> don't receive any unpleasant suprises.. I've not the foggiest clue what
> that number means;)
> 
> -	{ "vt82c596b",	PCI_DEVICE_ID_VIA_82C596,   0x12, 0x2f, VIA_UDMA_66 },
> +	{ "vt82c596b",	PCI_DEVICE_ID_VIA_82C596,   0x10, 0x2f, VIA_UDMA_66 },

Can you verify it's a 596b and not 596a? Preferably by looking on the
chip? This change was brought in because I wasn't sure for the 10 and 11
revisions. 586a doesn't have a functional UDMA66 engine and causes
crashes if programmed to UDMA66.

> 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 11)

It's the revision number - 11 in your case.

-- 
Vojtech Pavlik
SuSE Labs

Re: 2.4.2-ac12 unknown southbridge

[Mike Galbraith]

On Tue, 6 Mar 2001, Vojtech Pavlik wrote:

> On Tue, Mar 06, 2001 at 10:09:05AM +0100, Mike Galbraith wrote:
>
> > The driver forget what it always called a vt82c596b before.  Reverting
> > the below brought it back on-line, and all seems well again.  (hope I
> > don't receive any unpleasant suprises.. I've not the foggiest clue what
> > that number means;)
> >
> > -	{ "vt82c596b",	PCI_DEVICE_ID_VIA_82C596,   0x12, 0x2f, VIA_UDMA_66 },
> > +	{ "vt82c596b",	PCI_DEVICE_ID_VIA_82C596,   0x10, 0x2f, VIA_UDMA_66 },
>
> Can you verify it's a 596b and not 596a? Preferably by looking on the
> chip? This change was brought in because I wasn't sure for the 10 and 11
> revisions. 586a doesn't have a functional UDMA66 engine and causes
> crashes if programmed to UDMA66.

*blur* SQUINT (I _definitely_ need new glasses) it's a 596b.

Probably dumb question wrt hdparm -i output...

/dev/hda:

 Model=IBM-DJNA-352030, FwRev=J58OA30K, SerialNo=GQ0GQFP8740
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=34
 BuffType=DualPortCache, BuffSize=1966kB, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39876480
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4
 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4

Why is it defaulting to udma4, and :) why the heck does it work?

	-Mike

Re: 2.4.2-ac12 unknown southbridge

[Vojtech Pavlik]

On Tue, Mar 06, 2001 at 10:29:00AM +0100, Mike Galbraith wrote:
> On Tue, 6 Mar 2001, Vojtech Pavlik wrote:
> 
> > On Tue, Mar 06, 2001 at 10:09:05AM +0100, Mike Galbraith wrote:
> >
> > > The driver forget what it always called a vt82c596b before.  Reverting
> > > the below brought it back on-line, and all seems well again.  (hope I
> > > don't receive any unpleasant suprises.. I've not the foggiest clue what
> > > that number means;)
> > >
> > > -	{ "vt82c596b",	PCI_DEVICE_ID_VIA_82C596,   0x12, 0x2f, VIA_UDMA_66 },
> > > +	{ "vt82c596b",	PCI_DEVICE_ID_VIA_82C596,   0x10, 0x2f, VIA_UDMA_66 },
> >
> > Can you verify it's a 596b and not 596a? Preferably by looking on the
> > chip? This change was brought in because I wasn't sure for the 10 and 11
> > revisions. 586a doesn't have a functional UDMA66 engine and causes
> > crashes if programmed to UDMA66.
> 
> *blur* SQUINT (I _definitely_ need new glasses) it's a 596b.
> 
> Probably dumb question wrt hdparm -i output...
> 
> /dev/hda:
> 
>  Model=IBM-DJNA-352030, FwRev=J58OA30K, SerialNo=GQ0GQFP8740
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=34
>  BuffType=DualPortCache, BuffSize=1966kB, MaxMultSect=16, MultSect=off
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39876480
>  IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes: pio0 pio1 pio2 pio3 pio4
>  DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
> 
> Why is it defaulting to udma4, and :) why the heck does it work?

Thanks. That means your change is correct. I'll send an update to Alan.

-- 
Vojtech Pavlik
SuSE Labs