Hi. I've just upgraded my box to 2.4.7 and suse 7.1. I've just
got this messages in dmesg after a bootup:
------------------------------------------------------------
Linux version 2.4.7 (root@pixie) (gcc version 2.95.2 19991024 (release)) #3 Fri
Jul 27 14:49:02 WEST 2001
[...]
CPU: AMD-K6(tm) 3D processor stepping 0c
[...]
VP_IDE: VIA vt82c586b (rev 47) IDE UDMA33 controller on pci00:07.1
ide0: BM-DMA at 0xe400-0xe407, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xe408-0xe40f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 90845U2, ATA DISK drive
hdc: SAMSUNG CD-ROM SC-148F, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 16514064 sectors (8455 MB) w/2048KiB Cache, CHS=1027/255/63, UDMA(33)
hdc: ATAPI 48X CD-ROM drive, 128kB Cache, DMA
[...]
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 184k freed
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Adding Swap: 265064k swap-space (priority -1)
[...]
eth0: using NWAY device table, not 8
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
sb: Creative ViBRA16C PnP detected
[...]
------------------------------------------------------------
The output of hdparm /dev/hda is:
------------------------------------------------------------
/dev/hda:
multcount = 16 (on)
I/O support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 1027/255/63, sectors = 16514064, start = 0
------------------------------------------------------------
and of hdparm -i /dev/hda is:
------------------------------------------------------------
/dev/hda:
Model=Maxtor 90845U2, FwRev=FA550480, SerialNo=E20BW5GC
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=16514064
IORDY=on/off, tPIO={min:120,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
Drive Supports : ATA/ATAPI-4 T13 1153D revision 17 : ATA-1 ATA-2 ATA-3 ATA-4 AT
A-5
Kernel Drive Geometry LogicalCHS=1027/255/63 PhysicalCHS=16383/16/63
------------------------------------------------------------
Any clue of what's happening?
Cheers,
--
*** Rodrigo Martins de Matos Ventura <[email protected]>
*** Web page: http://www.isr.ist.utl.pt/~yoda
*** Teaching Assistant and PhD Student at ISR:
*** Instituto de Sistemas e Robotica, Polo de Lisboa
*** Instituto Superior Tecnico, Lisboa, PORTUGAL
*** PGP fingerprint = 0119 AD13 9EEE 264A 3F10 31D3 89B3 C6C4 60C6 4585
This is sort of a continuation of my last msg. I tried a rpm
-Va on one xterm and a tar cf /dev/null / on another, and I got
another dma error:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
I also have errors from the ethernet devices, e.g.
eth0: Transmit error, Tx status register 82.
Probably a duplex mismatch. See Documentation/networking/vortex.txt
Flags; bus-master 1, dirty 1165(13) current 1165(13)
Transmit list 00000000 vs. c1277540.
0: @c1277200 length 800000aa status 000100aa
1: @c1277240 length 800000aa status 000100aa
2: @c1277280 length 800000aa status 000100aa
3: @c12772c0 length 800000aa status 000100aa
4: @c1277300 length 800000b2 status 000100b2
5: @c1277340 length 8000009e status 0001009e
6: @c1277380 length 800000aa status 000100aa
7: @c12773c0 length 800000aa status 000100aa
8: @c1277400 length 800000aa status 000100aa
9: @c1277440 length 800000aa status 000100aa
10: @c1277480 length 800000b2 status 000100b2
11: @c12774c0 length 8000009e status 0001009e
12: @c1277500 length 800000aa status 800100aa
13: @c1277540 length 800000aa status 000100aa
14: @c1277580 length 800000b2 status 000100b2
15: @c12775c0 length 8000009e status 0001009e
Cheers,
--
*** Rodrigo Martins de Matos Ventura <[email protected]>
*** Web page: http://www.isr.ist.utl.pt/~yoda
*** Teaching Assistant and PhD Student at ISR:
*** Instituto de Sistemas e Robotica, Polo de Lisboa
*** Instituto Superior Tecnico, Lisboa, PORTUGAL
*** PGP fingerprint = 0119 AD13 9EEE 264A 3F10 31D3 89B3 C6C4 60C6 4585
On Sat, Jul 28, 2001 at 04:12:02PM +0100, Rodrigo Ventura wrote:
This is sort of a continuation of my last msg. I tried a rpm
-Va on one xterm and a tar cf /dev/null / on another, and I got
another dma error:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
bad IDE cable?
I also have errors from the ethernet devices, e.g.
eth0: Transmit error, Tx status register 82.
Probably a duplex mismatch. See Documentation/networking/vortex.txt
^^^^^^^^^^^^^^^^^^^^^^^^^^
look |
--cw
> This is sort of a continuation of my last msg. I tried a rpm
> -Va on one xterm and a tar cf /dev/null / on another, and I got
> another dma error:
>
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
BadCRC is normally a cable error, but I'm suspicious that its also one of
the things caused by PCI bus problems on the VIA stuff
On approximately Sat, Jul 28, 2001 at 05:22:09PM +0100, Alan Cox wrote:
> > This is sort of a continuation of my last msg. I tried a rpm
> > -Va on one xterm and a tar cf /dev/null / on another, and I got
> > another dma error:
> >
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> BadCRC is normally a cable error, but I'm suspicious that its also one of
> the things caused by PCI bus problems on the VIA stuff
I am running the same chipset and used to see these sort of problems in
the early 2.3pre and 2.4 days, but have not seen a BadCRC error for a long
time.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
I think I can help verify your suspicions with the PCI problems, since I
get the error with my ethernet device (3C905B), although I do not get
the ide errors. I went from kernel 2.4.7-pre3 to 2.4.8 and started
receiving these errors. I have a WinTV Go board that is notorious for
locking things up which shares an IRQ with the ethernet controller. I
started up my tv viewer program and lost my ethernet connection. If
there is anything I can do that might help further, let me know.
Chris
On 28 Jul 2001 17:22:09 +0100, Alan Cox wrote:
> > This is sort of a continuation of my last msg. I tried a rpm
> > -Va on one xterm and a tar cf /dev/null / on another, and I got
> > another dma error:
> >
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> BadCRC is normally a cable error, but I'm suspicious that its also one of
> the things caused by PCI bus problems on the VIA stuff
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>>>>> "Alan" == Alan Cox <[email protected]> writes:
>> This is sort of a continuation of my last msg. I tried a rpm
>> -Va on one xterm and a tar cf /dev/null / on another, and I got
>> another dma error:
>>
>> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Alan> BadCRC is normally a cable error, but I'm suspicious that
Alan> its also one of the things caused by PCI bus problems on the
Alan> VIA stuff
Bull's eye! I just replaced the cable, which in fact was sort
of long, by a shorter one, and it seems OK now.
Cheers,
--
*** Rodrigo Martins de Matos Ventura <[email protected]>
*** Web page: http://www.isr.ist.utl.pt/~yoda
*** Teaching Assistant and PhD Student at ISR:
*** Instituto de Sistemas e Robotica, Polo de Lisboa
*** Instituto Superior Tecnico, Lisboa, PORTUGAL
*** PGP fingerprint = 0119 AD13 9EEE 264A 3F10 31D3 89B3 C6C4 60C6 4585
>>>>> "Chris" == Chris Wedgwood <[email protected]> writes:
Chris> I also have errors from the ethernet devices,
Chris> e.g.
Chris> eth0: Transmit error, Tx status register 82. Probably
Chris> a duplex mismatch. See Documentation/networking/vortex.txt
Right, I should have read the vortex.txt file before. But now,
let me ask something that is not explained in that file: how can I
track down the misconfigured NIC?
Cheers,
--
*** Rodrigo Martins de Matos Ventura <[email protected]>
*** Web page: http://www.isr.ist.utl.pt/~yoda
*** Teaching Assistant and PhD Student at ISR:
*** Instituto de Sistemas e Robotica, Polo de Lisboa
*** Instituto Superior Tecnico, Lisboa, PORTUGAL
*** PGP fingerprint = 0119 AD13 9EEE 264A 3F10 31D3 89B3 C6C4 60C6 4585