Re: Hard Hangs with 2.0.35+Jumbo-9, reproducable

Michel Aubry (giovanni@sudfr.com)
Thu, 3 Sep 1998 17:09:17 +0200 (MET DST)


On Wed, 2 Sep 1998, Andre M. Hedrick wrote:

> On Wed, 2 Sep 1998, Hans de Goede wrote:
>
> > rnel: ide: VIA VT82C586B (split FIFO) UDMA Bus Mastering IDE
> > rnel: Controller on PCI bus 0 function 57
> > rnel: ide: timings == ba09c20b
> > rnel: ide0: BM-DMA at 0x6000-0x6007
> > rnel: ide1: BM-DMA at 0x6008-0x600f
> > rnel: hda: ST51080A, 1033MB w/256kB Cache, CHS=525/64/63
> > rnel: hdc: QUANTUM FIREBALL ST6.4A, 6149MB w/81kB Cache,
> > CHS=13328/15/63,
> > UDMA
> > rnel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > rnel: ide1 at 0x170-0x177,0x376 on irq 15
> > rnel: Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
> > rnel: FDC 0 is an 8272A
> > rnel: Partition check:
> > rnel: hda: hda1 hda2 hda3
> > rnel: hdc: [PTBL] [784/255/63] hdc1 hdc2
> >
> > PCI devices found:
> > Bus 0, device 11, function 0:
> > VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 1).
> > Medium devsel. IRQ 255. Master Capable. Latency=32. Min
> > Gnt=4.Max Lat=255.
> > Non-prefetchable 32 bit memory at 0xe0000000.
> > Bus 0, device 9, function 0:
> > Non-VGA device: NCR 53c810 (rev 1).
> > Medium devsel. IRQ 10. Master Capable. Latency=64.
> > I/O at 0x6200.
> > Non-prefetchable 32 bit memory at 0xe4000000.
> > Bus 0, device 7, function 1:
> > IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
> > Medium devsel. Fast back-to-back capable. Master Capable.
> > Latency=32.
> > I/O at 0x6000.
> > Bus 0, device 7, function 0:
> > ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 37).
> > Medium devsel. Master Capable. No bursts.
> > Bus 0, device 0, function 0:
> > Host bridge: VIA Technologies VT 82C585 Apollo VP1/VPX (rev 35).
> ^^^^^^^
I think I got something very similar on my host computer (except a
NCR-scsi?-controller, and everything works fine for me.

dmesg reports me:

BIOS query detected 65536KB RAM. Report errors to lma@varesearch.com
Total RAM size was detected using BIOS function int 15h, ax=e801h.
Detected 233224959 Hz processor.
ide_setup: hdc=635,128,63
... skipping ...
Linux version 2.0.35 (root@captain) (gcc version 2.7.2.3) #2 Thu Sep 3 15:48:37 MET DST 1998
... skipping ...
ISDN subsystem Rev: 1.44/1.41/1.47/1.28/1.8
ide: VIA VT82C586B (split FIFO) UDMA Bus Mastering IDE
Controller on PCI bus 0 function 57
ide: timings == ba09c20b
ide0: BM-DMA at 0x6000-0x6007
ide1: BM-DMA at 0x6008-0x600f
hda: QUANTUM BIGFOOT1280A, 1226MB w/87kB Cache, CHS=623/64/63, DMA
hdb: WEARNES CDD-1020, ATAPI CDROM drive
hdc: FUJITSU MPA3026ATU, 2503MB w/0kB Cache, CHS=635/128/63, UDMA
ide2: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
Floppy drive(s): fd0 is 1.44M
FDC 0 is an 8272A
ne2k-pci.c:v0.99L 2/7/98 D. Becker/P. Gortmaker http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html
ne2k-pci.c: PCI NE2000 clone 'RealTek RTL-8029' at I/O 0x6200, IRQ 11.
eth0: PCI NE2000 found at 0x6200, IRQ 11, 00:00:B4:53:72:47.
Partition check:
hda: hda1 hda2 hda3 hda4
hdc: hdc1 hdc2 hdc3 hdc4

and "/proc/pci":

PCI devices found:
Bus 0, device 10, function 0:
Ethernet controller: Realtek 8029 (rev 0).
Medium devsel. IRQ 11.
I/O at 0x6200.
Bus 0, device 9, function 0:
VGA compatible controller: Cirrus Logic GD 5434 (rev 249).
Fast devsel. IRQ 255.
Non-prefetchable 32 bit memory at 0xe0000000.
Bus 0, device 7, function 1:
IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
Medium devsel. Fast back-to-back capable. Master Capable. Latency=32.
I/O at 0x6000.
Bus 0, device 7, function 0:
ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 37).
Medium devsel. Master Capable. No bursts.
Bus 0, device 0, function 0:
Host bridge: VIA Technologies VT 82C585 Apollo VP1/VPX (rev 35).
Medium devsel. Fast back-to-back capable. Master Capable. Latency=32.


> Is our patch valid only for VP3 and not for VP1/VP2?
these are all 586B south chips => all the same.

> Second, I have discovered the hardware that ide interfaces go only
> as fast as the slowest device. There may be a timing error due to
> device or conflicts or something of this nature.
>
> What do you say?
As you can see upper, I got hda + hdb devices on my first interface. Here
are their speeds:

/dev/hda:
Timing buffer-cache reads: 64 MB in 1.69 seconds =37.87 MB/sec
Timing buffered disk reads: 32 MB in 5.87 seconds = 5.45 MB/sec

/dev/hdb:
Timing buffer-cache reads: 64 MB in 1.70 seconds =37.65 MB/sec
Timing buffered disk reads: 32 MB in 22.93 seconds = 1.40 MB/sec

What do you mean «slowest»?

> This may be a case of individual device tuning of the chipset.

let's us have a look at "/proc/via"!
But could you, Hans, run your kernel with a "hdc=782,255,63" command line?

Cheer,
Michel.

5, rue de la Raillere
65110 Cauterets France.

giovanni@sudfr.com tel.:05 62 92 57 80

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html