* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
[not found] ` <5WEvy-7az-7@gated-at.bofh.it>
@ 2006-04-01 19:03 ` Robert Hancock
2006-04-01 19:13 ` Kyle Moffett
0 siblings, 1 reply; 17+ messages in thread
From: Robert Hancock @ 2006-04-01 19:03 UTC (permalink / raw)
To: linux-kernel; +Cc: Kyle Moffett
Kyle Moffett wrote:
>>> hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>>> hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
>>
>> Hmm, are these new? Sure you don't have a bad IDE cable?
>
> Oh, those aren't the errors I'm worried about; I've had those for a
> while and they're harmless. Those are due to the kernel running the IDE
> controller at a higher-than-supported speed. It gets errors for a
> couple seconds and automatically drops the bus down to a lower and safer
> speed.
That would be a bug, no? Sounds dangerous to rely on that.
> The cable's aren't bad, I've tried at least 6 different
> 80-conductor cables that all work fine in other systems. The errors I
> _am_ worried about are these:
>
>> Mar 28 03:15:13 penelope kernel: hdi: status timeout: status=0xd0 {
>> Busy }
>> Mar 28 03:15:13 penelope kernel: PDC202XX: Secondary channel reset.
>> Mar 28 03:15:13 penelope kernel: hdi: no DRQ after issuing MULTWRITE_EXT
>> Mar 28 03:15:13 penelope kernel: ide4: reset: success
>> Mar 28 03:30:13 penelope kernel: hdi: status timeout: status=0xd0 {
>> Busy }
>> Mar 28 03:30:13 penelope kernel: PDC202XX: Secondary channel reset.
>> Mar 28 03:30:13 penelope kernel: hdi: no DRQ after issuing MULTWRITE_EXT
>> Mar 28 03:30:13 penelope kernel: ide4: reset: success
That sounds fishy to me. If the controller is having trouble
communicating with the drive causing BadCRC errors, it could easily
cause such errors as the above as well.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
2006-04-01 19:03 ` [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15 Robert Hancock
@ 2006-04-01 19:13 ` Kyle Moffett
0 siblings, 0 replies; 17+ messages in thread
From: Kyle Moffett @ 2006-04-01 19:13 UTC (permalink / raw)
To: Robert Hancock; +Cc: linux-kernel
On Apr 1, 2006, at 14:03:59, Robert Hancock wrote:
> Kyle Moffett wrote:
>>>> hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>>>> hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
>>>
>>> Hmm, are these new? Sure you don't have a bad IDE cable?
>> Oh, those aren't the errors I'm worried about; I've had those for
>> a while and they're harmless. Those are due to the kernel running
>> the IDE controller at a higher-than-supported speed. It gets
>> errors for a couple seconds and automatically drops the bus down
>> to a lower and safer speed.
>
> That would be a bug, no? Sounds dangerous to rely on that.
Well, no one else seems concerned by that behavior (and I recall it
being mentioned previously on this list somewhere). I've tested it
fairly extensively; if I turn up the drive speed with hdparm, it gets
about 4 more CRC errors during data transfer (each badcrc command is
retried, of course), and then does a bus reset and drops to a lower
speed again. I've never had any problems with data corruption on
this system, and it has been a RAID5 fileserver for several years now.
>> The cable's aren't bad, I've tried at least 6 different 80-
>> conductor cables that all work fine in other systems. The errors
>> I _am_ worried about are these:
>>> Mar 28 03:15:13 penelope kernel: hdi: status timeout: status=0xd0
>>> { Busy }
>>> Mar 28 03:15:13 penelope kernel: PDC202XX: Secondary channel reset.
>>> Mar 28 03:15:13 penelope kernel: hdi: no DRQ after issuing
>>> MULTWRITE_EXT
>>> Mar 28 03:15:13 penelope kernel: ide4: reset: success
>>> Mar 28 03:30:13 penelope kernel: hdi: status timeout: status=0xd0
>>> { Busy }
>>> Mar 28 03:30:13 penelope kernel: PDC202XX: Secondary channel reset.
>>> Mar 28 03:30:13 penelope kernel: hdi: no DRQ after issuing
>>> MULTWRITE_EXT
>>> Mar 28 03:30:13 penelope kernel: ide4: reset: success
>
> That sounds fishy to me. If the controller is having trouble
> communicating with the drive causing BadCRC errors, it could easily
> cause such errors as the above as well.
Except you seem to have missed the fact that these errors never
occurred under 2.6.12, and occur regularly on 2.6.15. Besides, after
the initial boot-time lowering of the speed, I never get another
badCRC error from the drive, and I've never had any data corruption.
Cheers,
Kyle Moffett
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
@ 2006-04-03 11:35 Mikael Pettersson
2006-04-03 12:32 ` Kyle Moffett
0 siblings, 1 reply; 17+ messages in thread
From: Mikael Pettersson @ 2006-04-03 11:35 UTC (permalink / raw)
To: alan; +Cc: edmudama, hahn, hancockr, jujutama, linux-kernel, mrmacman_g4
On Mon, 03 Apr 2006 10:29:36 +0100, Alan Cox wrote:
> On Llu, 2006-04-03 at 11:07 +0200, Mikael Pettersson wrote:
> > 20269 PCI controller card. The 20269+cable+disk does udma5
> > just fine in a PC, but throws a few BadCRCs at bootup on
> > the PowerMac, resets and drops to udma4, and then things work
> > OK for me, but I don't stress it very much (no RAID).
>
> Interesting.
>
> > Since the card's bios doesn't get run at powerup, I always
> > suspected that the driver fails to initialize some timing thing.
>
> The BIOS does various bits of PCI bus setup on some systems including
> latency setting. That might be relevant, especially latency to get
> bursting.
>
> > Another possibility is the "data coherency" issue in some
> > G4 CPUs which requires mappings of memory shared with other
> > agents to use some additional magic in the page table.
>
>
> The CRC is computed between the controller as the bits get fired over
> the cable and drive so it shouldn't be caused by any weird bus timings.
>
> More info would be useful although it may be a while before I can look
> at it
Here's the bootup dmesg log, hdparm -i /dev/hde, and lspci -vvvx output
for the machine in question. Let me know if you need anything else.
/Mikael
Total memory = 768MB; using 2048kB for hash table (at cfe00000)
Linux version 2.6.16 (mikpe@eisbock) (gcc version 4.1.0) #1 Mon Mar 20 11:41:36 CET 2006
Found a Heathrow mac-io controller, rev: 1, mapped at 0xfdf80000
PowerMac motherboard: PowerMac G3 (Gossamer)
Found Grackle (MPC106) PCI host bridge at 0x80000000. Firmware bus number: 0->0
nvram: OF partition at 0x1800
nvram: XP partition at 0x1300
nvram: NR partition at 0x1400
Top of RAM: 0x30000000, Total RAM: 0x30000000
Memory hole size: 0MB
On node 0 totalpages: 196608
DMA zone: 196608 pages, LIFO batch:31
DMA32 zone: 0 pages, LIFO batch:0
Normal zone: 0 pages, LIFO batch:0
HighMem zone: 0 pages, LIFO batch:0
Built 1 zonelists
Kernel command line: root=/dev/hde5
irq: Found primary Apple PIC /pci/mac-io for 64 irqs
irq: System has 64 possible interrupts
PID hash table entries: 4096 (order: 12, 65536 bytes)
GMT Delta read from XPRAM: 60 minutes, DST: off
time_init: decrementer frequency = 16.708516 MHz
time_init: processor frequency = 66.820000 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 771840k/786432k available (1960k kernel code, 14340k reserved, 224k data, 94k bss, 152k init)
Calibrating delay loop... 33.38 BogoMIPS (lpj=166912)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
PCI: Probing PCI hardware
PCI: Cannot allocate resource region 2 of device 0000:00:12.0
PCI: Cannot allocate resource region 1 of device 0000:00:12.0
PCI: Enabling device 0000:00:0d.0 (0116 -> 0117)
PCI: Enabling device 0000:00:0e.0 (0004 -> 0007)
Registering pmac pic with sysfs...
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
PCI: Enabling device 0000:00:12.0 (0086 -> 0087)
atyfb: using auxiliary register aperture
atyfb: 3D RAGE II+ (Mach64 GT) [0x4754 rev 0x9a]
atyfb: 2M SGRAM (1:1), 14.31818 MHz XTAL, 200 MHz PLL, 67 Mhz MCLK, 67 MHz XCLK
atyfb: monitor sense=73f, mode 6
Console: switching to colour frame buffer device 80x30
atyfb: fb0: ATY Mach64 frame buffer device on PCI
Generic RTC Driver v1.07
Macintosh non-volatile memory driver v1.1
fd0: SWIM3 floppy controller
MacIO PCI driver attached to Heathrow chipset
input: Macintosh mouse button emulation as /class/input/input0
Macintosh CUDA driver v0.5 for Unified ADB.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PDC20269: IDE controller at PCI slot 0000:00:0e.0
PDC20269: chipset revision 2
PDC20269: ROM enabled at 0x81804000
PDC20269: 100% native mode on irq 24
ide2: BM-DMA at 0x0880-0x0887, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x0888-0x088f, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
adb: starting probe task...
adb devices: [2]: 2 5 [3]: 3 1
ADB keyboard at 2, handler set to 3
Detected ADB keyboard, type ISO, swapping keys.
input: ADB keyboard as /class/input/input1
ADB mouse at 3, handler set to 2
input: ADB mouse as /class/input/input2
adb: finished probe task...
hde: IBM-DTLA-307030, ATA DISK drive
ide2 at 0x8c0-0x8c7,0x8b2 on irq 24
Probing IDE interface ide3...
ide0: Found Apple Heathrow ATA controller, bus ID 0, irq 13
Probing IDE interface ide0...
hda: MATSHITA CR-585, ATAPI CD/DVD-ROM drive
hda: Enabling MultiWord DMA 1
ide0 at 0xf1008000-0xf1008007,0xf1008160 on irq 13
ide1: Found Apple Heathrow ATA controller, bus ID 1, irq 14
Probing IDE interface ide1...
hde: max request size: 128KiB
hde: 60036480 sectors (30738 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)
hde: cache flushes not supported
hde:hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
PDC202XX: Primary channel reset.
ide2: reset: success
hde1 hde2 hde3 hde4 < hde5 hde6 hde7 >
sym0: <875> rev 0x4 at pci 0000:00:0d.0 irq 23
sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.2.2
Vendor: IBM Model: DDRS-34560W Rev: S71D
Type: Direct-Access ANSI SCSI revision: 02
target0:0:0: tagged command queuing enabled, command queue depth 16.
target0:0:0: Beginning Domain Validation
target0:0:0: asynchronous
target0:0:0: wide asynchronous
target0:0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 15)
target0:0:0: Domain Validation skipping write tests
target0:0:0: Ending Domain Validation
SCSI device sda: 8925000 512-byte hdwr sectors (4570 MB)
sda: Write Protect is off
sda: Mode Sense: e5 00 00 08
SCSI device sda: drive cache: write back
SCSI device sda: 8925000 512-byte hdwr sectors (4570 MB)
sda: Write Protect is off
sda: Mode Sense: e5 00 00 08
SCSI device sda: drive cache: write back
sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
sd 0:0:0:0: Attached scsi disk sda
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 152k init
Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Enabling device 0000:00:0f.0 (0014 -> 0017)
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
tulip0: Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) block.
tulip0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
tulip0: Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) block.
tulip0: Index #4 - Media 100baseTx (#3) described by a 21143 reset method (5) block.
eth0: Digital DS21143 Tulip rev 48 at fd731800, 00:00:C5:50:F9:51, IRQ 25.
EXT3 FS on hde5, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on hde3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hde6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1048816k swap on /dev/hde2. Priority:-1 extents:1 across:1048816k
NET: Registered protocol family 17
/dev/hde:
Model=IBM-DTLA-307030, FwRev=TX4OA6AA, SerialNo=YKEYKTTY645
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=60036480
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
UDMA modes: udma0 udma1 udma2 udma3 *udma4 udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1:
* signifies the current active mode
00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort+ <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0, Cache Line Size 08
00: 57 10 02 00 06 00 80 28 40 00 00 06 08 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
00:0d.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 04)
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: 255 (4250ns min, 16000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 23
Region 0: I/O ports at fe000400 [size=256]
Region 1: Memory at 0000000081801000 (32-bit, non-prefetchable) [size=256]
Region 2: Memory at 0000000081802000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 0000000081880000 [disabled] [size=256K]
00: 00 10 0f 00 17 01 00 02 04 00 00 01 08 ff 00 00
10: 01 04 00 00 00 10 80 81 00 20 80 81 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 88 81 00 00 00 00 00 00 00 00 17 01 11 40
00:0e.0 Unknown mass storage controller: Promise Technology, Inc. 20269 (rev 02) (prog-if 85)
Subsystem: Promise Technology, Inc. Ultra133TX2
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (1000ns min, 4500ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 24
Region 0: I/O ports at fe0008c0 [size=8]
Region 1: I/O ports at fe0008b0 [size=4]
Region 2: I/O ports at fe0008a0 [size=8]
Region 3: I/O ports at fe000890 [size=4]
Region 4: I/O ports at fe000880 [size=16]
Region 5: Memory at 0000000081808000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at 0000000081804000 [size=16K]
Capabilities: [60] 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: 5a 10 69 4d 07 00 30 04 02 85 80 01 08 20 00 00
10: c1 08 00 00 b1 08 00 00 a1 08 00 00 91 08 00 00
20: 81 08 00 00 00 80 80 81 00 00 00 00 5a 10 68 4d
30: 01 40 80 81 60 00 00 00 00 00 00 00 18 01 04 12
00:0f.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 30)
Subsystem: Standard Microsystems Corp [SMC]: Unknown device 2401
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: 32 (5000ns min, 10000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 25
Region 0: I/O ports at fe000800 [size=128]
Region 1: Memory at 0000000081800000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at 0000000081840000 [disabled] [size=256K]
00: 11 10 19 00 17 00 80 02 30 00 00 02 08 20 00 00
10: 01 08 00 00 00 00 80 81 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 07 00 00 00 b8 10 01 24
30: 00 00 84 81 00 00 00 00 00 00 00 00 19 01 14 28
00:10.0 Class ff00: Apple Computer Inc. Heathrow Mac I/O (rev 01)
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: 32, Cache Line Size 08
Region 0: Memory at 00000000f3000000 (32-bit, non-prefetchable) [size=512K]
00: 6b 10 10 00 16 00 00 02 01 00 00 ff 08 20 00 00
10: 00 00 00 f3 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
00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 9a) (prog-if 00 [VGA])
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: 32 (2000ns min), Cache Line Size 08
Interrupt: pin A routed to IRQ 22
Region 0: Memory at 0000000082000000 (32-bit, non-prefetchable) [size=16M]
Region 1: I/O ports at fe001000 [size=256]
Region 2: Memory at 0000000080000000 (32-bit, non-prefetchable) [size=4K]
00: 02 10 54 47 87 00 80 02 9a 00 00 03 08 20 00 00
10: 00 00 00 82 01 10 00 00 00 00 00 80 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 16 01 08 00
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
2006-04-03 11:35 Mikael Pettersson
@ 2006-04-03 12:32 ` Kyle Moffett
0 siblings, 0 replies; 17+ messages in thread
From: Kyle Moffett @ 2006-04-03 12:32 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: alan, edmudama, hahn, hancockr, jujutama, linux-kernel
On Apr 3, 2006, at 07:35:01, Mikael Pettersson wrote:
> PDC20269: IDE controller at PCI slot 0000:00:0e.0
> PDC20269: chipset revision 2
> PDC20269: ROM enabled at 0x81804000
> PDC20269: 100% native mode on irq 24
> ide2: BM-DMA at 0x0880-0x0887, BIOS settings: hde:pio, hdf:pio
> ide3: BM-DMA at 0x0888-0x088f, BIOS settings: hdg:pio, hdh:pio
Looks like the controller ends up in the same initial state as mine.
After playing with hdparm a bit, I've determined that my /dev/hdg
(Maxtor disk on the PDC20268) comes up in udma4 and falls back to
udma3 after a few CRC errors. It appears that the /dev/hdi (Samsung
disk on the PDC20268) comes up in an indeterminate udma state and
falls back to a lower DMA state after a few CRC errors. At some
point later the MULTWRITE_EXT problem triggers DMA timeouts and the
kernel falls back to PIO. I can reenable DMA with "hdparm -d1 /dev/
hdi" and it will come back in udma2 mode, but it refuses to go
higher, giving these errors:
hdi: dma_timer_expiry: dma status == 0x21
hdi: DMA timeout error
hdi: dma timeout error: status=0xd0 { Busy }
ide: failed opcode was: unknown
hdi: DMA disabled
PDC202XX: Secondary channel reset.
ide4: reset: success
And at this point it falls back to udma2 again. Both card and drive
should support UDMA4 (ATA100?)
> hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
> ide: failed opcode was: unknown
> PDC202XX: Primary channel reset.
> ide2: reset: success
You get the exact same reset I do on the bad CRCs. When this happens
the udma level is lowered by 1 on my system.
> /dev/hde:
>
> Model=IBM-DTLA-307030, FwRev=TX4OA6AA, SerialNo=YKEYKTTY645
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
> BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=off
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=60036480
> 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
> UDMA modes: udma0 udma1 udma2 udma3 *udma4 udma5
My card and Maxtor drive refuse to run in udma4 mode, although I know
the card and drive support it. The CRC errors on the Maxtor always
trigger a fallback to udma3.
> 00:0e.0 Unknown mass storage controller: Promise Technology, Inc.
> 20269 (rev 02) (prog-if 85)
> Subsystem: Promise Technology, Inc. Ultra133TX2
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32 (1000ns min, 4500ns max), Cache Line Size 08
> Interrupt: pin A routed to IRQ 24
> Region 0: I/O ports at fe0008c0 [size=8]
> Region 1: I/O ports at fe0008b0 [size=4]
> Region 2: I/O ports at fe0008a0 [size=8]
> Region 3: I/O ports at fe000890 [size=4]
> Region 4: I/O ports at fe000880 [size=16]
> Region 5: Memory at 0000000081808000 (32-bit, non-prefetchable)
> [size=16K]
> Expansion ROM at 0000000081804000 [size=16K]
> Capabilities: [60] 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: 5a 10 69 4d 07 00 30 04 02 85 80 01 08 20 00 00
> 10: c1 08 00 00 b1 08 00 00 a1 08 00 00 91 08 00 00
> 20: 81 08 00 00 00 80 80 81 00 00 00 00 5a 10 68 4d
> 30: 01 40 80 81 60 00 00 00 00 00 00 00 18 01 04 12
My controller looks like this:
0001:11:02.0 Mass storage controller: Promise Technology, Inc.
PDC20268 (Ultra100 TX2) (rev 02) (prog-if 85)
Subsystem: Promise Technology, Inc.: Unknown device ad68
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 16 (1000ns min, 4500ns max), Cache Line Size: 0x08
(32 bytes)
Interrupt: pin A routed to IRQ 52
Region 0: I/O ports at f2001440 [size=8]
Region 1: I/O ports at f2001430 [size=4]
Region 2: I/O ports at f2001420 [size=8]
Region 3: I/O ports at f2001410 [size=4]
Region 4: I/O ports at f2001400 [size=16]
Region 5: Memory at 800a0000 (32-bit, non-prefetchable)
[size=64K]
Expansion ROM at 80090000 [disabled] [size=64K]
Capabilities: [60] 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: 5a 10 68 4d 07 00 30 04 02 85 80 01 08 10 00 00
10: 41 14 00 00 31 14 00 00 21 14 00 00 11 14 00 00
20: 01 14 00 00 00 00 0a 80 00 00 00 00 5a 10 68 ad
30: 01 00 09 80 60 00 00 00 00 00 00 00 34 01 04 12
Thanks for the help!
Cheers,
Kyle Moffett
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
@ 2006-04-03 9:07 Mikael Pettersson
2006-04-03 9:29 ` Alan Cox
0 siblings, 1 reply; 17+ messages in thread
From: Mikael Pettersson @ 2006-04-03 9:07 UTC (permalink / raw)
To: alan, mrmacman_g4; +Cc: edmudama, hahn, hancockr, jujutama, linux-kernel
On Sun, 02 Apr 2006 22:24:43 +0100, Alan Cox wrote:
>Unless anyone else is seeing the same problem with the same card variant
>or you have two cards that do it then there isn't much that can be done
>I suspect other than assume the hardware is iffy, rightly or wrongly.
>I'd have expected a lot more reports if it were the controller.
>
>(Having said that if you are reading this and your controller is a
>Promise and does the same, please say so it might be vital to deducing a
>pattern to problems)
I have a Beige G3 PowerMac upgraded with a 1GHz G4 CPU
(a 7455 on a Sonnet board) and a standard (for x86) Promise
20269 PCI controller card. The 20269+cable+disk does udma5
just fine in a PC, but throws a few BadCRCs at bootup on
the PowerMac, resets and drops to udma4, and then things work
OK for me, but I don't stress it very much (no RAID).
Since the card's bios doesn't get run at powerup, I always
suspected that the driver fails to initialize some timing thing.
Another possibility is the "data coherency" issue in some
G4 CPUs which requires mappings of memory shared with other
agents to use some additional magic in the page table.
This issue caused file system corruption when I used
my G4 + 20269 combo under load with 2.4 kernels, until
I found and backported a fix from 2.6 to 2.4.28. It's
supposed to be handled transparently by arch/{ppc,powerpc},
but it's possible the driver is mapping things incorrectly.
(This is just speculation.)
I can provide bootup logs and lspci dumps if you want.
/Mikael
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
2006-04-03 9:07 Mikael Pettersson
@ 2006-04-03 9:29 ` Alan Cox
0 siblings, 0 replies; 17+ messages in thread
From: Alan Cox @ 2006-04-03 9:29 UTC (permalink / raw)
To: Mikael Pettersson
Cc: mrmacman_g4, edmudama, hahn, hancockr, jujutama, linux-kernel
On Llu, 2006-04-03 at 11:07 +0200, Mikael Pettersson wrote:
> 20269 PCI controller card. The 20269+cable+disk does udma5
> just fine in a PC, but throws a few BadCRCs at bootup on
> the PowerMac, resets and drops to udma4, and then things work
> OK for me, but I don't stress it very much (no RAID).
Interesting.
> Since the card's bios doesn't get run at powerup, I always
> suspected that the driver fails to initialize some timing thing.
The BIOS does various bits of PCI bus setup on some systems including
latency setting. That might be relevant, especially latency to get
bursting.
> Another possibility is the "data coherency" issue in some
> G4 CPUs which requires mappings of memory shared with other
> agents to use some additional magic in the page table.
The CRC is computed between the controller as the bits get fired over
the cable and drive so it shouldn't be caused by any weird bus timings.
More info would be useful although it may be a while before I can look
at it
^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <Pine.LNX.4.44.0604021508540.2653-100000@coffee.psychology.mcmaster.ca>]
* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
[not found] <Pine.LNX.4.44.0604021508540.2653-100000@coffee.psychology.mcmaster.ca>
@ 2006-04-02 19:55 ` Kyle Moffett
2006-04-02 21:24 ` Alan Cox
0 siblings, 1 reply; 17+ messages in thread
From: Kyle Moffett @ 2006-04-02 19:55 UTC (permalink / raw)
To: Mark Hahn
Cc: LKML Kernel, John Livingston, Alan Cox, Eric D. Mudama,
Robert Hancock
Due to Mark Hahn's repeated demands that I leave his replies offlist,
I have not included the contents of his message, however as I am
_quite_ sure that my problem is not due to failing or misconfigured
hardware, I am sending my own post to the LKML and a few others in
hopes of receiving additional information that can help me debug the
kernel's confusion.
Like I have tirelessly repeated to you before, Mark:
(1) This same behavior occurs on both controllers regardless of
which drive and cable combination is attached to the controller. I
spent several hours when I first set the system up trying every drive
and cable permutation possible, given the 3 drives I had at the time
and the 5 cables from 4 different manufacturers. Each and every time
it was the PDC controller that gave errors for its two drives until
it reset itself, and from that point in boot on everything was fine.
There is no possible way for it to be a cable or drive specific
problem, I have since replaced 2 of the drives one-by-one with
different drives as they failed due to old age, both times using a
new drive and the shipped cable, in every case it gave the same errors.
(2) It's extremely unlikely that the card itself is faulty; it
exhibits identical symptoms on both drives and has ever since I
originally purchased the card and installed 2.4.X on the system.
(3) It's not possible that it's the power supply. As I said before
I checked the power supply with an oscilliscope _during_boot_. The
levels were correct (12V and 5V), and virtually noise-free. The
hardware was originally designed to reliably support the power load
placed on it, it's a 350W power supply with the 3 drives, a low-power
400MHz CPU, a Rage128 GPU, and 800MB or so of PC-100 RAM.
(4) I'm not an idiot, I've administered a whole lab full of
workstations with a wide variety of IDE hardware from the very old to
the very new; I know what I'm doing and how to properly connect the
cables. It's not like it takes a genius anyways given that the host-
side socket is blue and the drive-side one is black. I know how a
single drive always goes at the end of a cable. Etc. I've even had
to deal with old systems with old-style Y-shaped ATA cables that had
a drive at each end; and I know how to tell the difference between them.
(5) The cables themselves run flat against the grounded metal of the
case, the machine itself has little enough EMI as it is; no wireless
chips and a low-speed CPU and bus, the wires are well away from the
power supply. Even if that were the case, I've rearranged the wire
routing many times and _never_ seen a change in behavior, even
removing the CD-ROM drive and placing a drive there had no effect.
If (as Alan Cox suggested) the problem lies with the kernel
incorrectly detecting IDE settings from the controller or not
noticing a buggy firmware, then I'm hoping that with some help I can
determine where the kernel driver is getting confused and correct the
programmed bus timings (or whatever the hell isn't working). As my
practical knowledge of the ATA and IDE protocols is quite limited I'm
well out of my depth here and unable to debug without further
assistance.
Cheers,
Kyle Moffett
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
2006-04-02 19:55 ` Kyle Moffett
@ 2006-04-02 21:24 ` Alan Cox
2006-04-02 22:00 ` Mark Hahn
2006-04-02 23:17 ` Kyle Moffett
0 siblings, 2 replies; 17+ messages in thread
From: Alan Cox @ 2006-04-02 21:24 UTC (permalink / raw)
To: Kyle Moffett
Cc: Mark Hahn, LKML Kernel, John Livingston, Eric D. Mudama,
Robert Hancock
On Sul, 2006-04-02 at 15:55 -0400, Kyle Moffett wrote:
> (2) It's extremely unlikely that the card itself is faulty; it
> exhibits identical symptoms on both drives and has ever since I
> originally purchased the card and installed 2.4.X on the system.
If it has always shown those symptoms then I'd say its quite likely the
card if the crystals/PLLs on it are out. It looks like the timing is
wrong, which means either the input clocks (eg PCI clock) are wrong (eg
37.5Mhz not 33 due to BIOS overclock settings or just plain out), the
card has a dodgy crystal/PLL or the kernel set it up wrong.
PCI timings won't move between motherboards, PLL faults wont move
between cards.
> (3) It's not possible that it's the power supply. As I said before
> I checked the power supply with an oscilliscope _during_boot_. The
I think you can rule that out. Insufficient power generally causes
drives to offline or spontaneously reset. It can cause weird symptoms as
it ends up back in PIO 0 but not ECC change downs except to PIO
> noticing a buggy firmware, then I'm hoping that with some help I can
> determine where the kernel driver is getting confused and correct the
> programmed bus timings (or whatever the hell isn't working). As my
> practical knowledge of the ATA and IDE protocols is quite limited I'm
> well out of my depth here and unable to debug without further
> assistance.
Unless anyone else is seeing the same problem with the same card variant
or you have two cards that do it then there isn't much that can be done
I suspect other than assume the hardware is iffy, rightly or wrongly.
I'd have expected a lot more reports if it were the controller.
(Having said that if you are reading this and your controller is a
Promise and does the same, please say so it might be vital to deducing a
pattern to problems)
Alan
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
2006-04-02 21:24 ` Alan Cox
@ 2006-04-02 22:00 ` Mark Hahn
2006-04-02 23:17 ` Kyle Moffett
1 sibling, 0 replies; 17+ messages in thread
From: Mark Hahn @ 2006-04-02 22:00 UTC (permalink / raw)
To: Alan Cox
Cc: Kyle Moffett, LKML Kernel, John Livingston, Eric D. Mudama,
Robert Hancock
> > (2) It's extremely unlikely that the card itself is faulty; it
> > exhibits identical symptoms on both drives and has ever since I
> > originally purchased the card and installed 2.4.X on the system.
>
> If it has always shown those symptoms then I'd say its quite likely the
> card if the crystals/PLLs on it are out. It looks like the timing is
> wrong, which means either the input clocks (eg PCI clock) are wrong (eg
> 37.5Mhz not 33 due to BIOS overclock settings or just plain out), the
> card has a dodgy crystal/PLL or the kernel set it up wrong.
I mentioned this to Kyle early on, in connection with the idebus=
kernel parameter. I'm not sure why he wants to believe there's a
software bug causing his problems.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
2006-04-02 21:24 ` Alan Cox
2006-04-02 22:00 ` Mark Hahn
@ 2006-04-02 23:17 ` Kyle Moffett
1 sibling, 0 replies; 17+ messages in thread
From: Kyle Moffett @ 2006-04-02 23:17 UTC (permalink / raw)
To: Alan Cox
Cc: Mark Hahn, LKML Kernel, John Livingston, Eric D. Mudama,
Robert Hancock
On Apr 2, 2006, at 17:24:43, Alan Cox wrote:
> On Sul, 2006-04-02 at 15:55 -0400, Kyle Moffett wrote:
>> (2) It's extremely unlikely that the card itself is faulty; it
>> exhibits identical symptoms on both drives and has ever since I
>> originally purchased the card and installed 2.4.X on the system.
>
> If it has always shown those symptoms then I'd say its quite likely
> the card if the crystals/PLLs on it are out. It looks like the
> timing is wrong, which means either the input clocks (eg PCI clock)
> are wrong (eg 37.5Mhz not 33 due to BIOS overclock settings or just
> plain out), the card has a dodgy crystal/PLL or the kernel set it
> up wrong.
>
> PCI timings won't move between motherboards, PLL faults wont move
> between cards.
>
> Unless anyone else is seeing the same problem with the same card
> variant or you have two cards that do it then there isn't much that
> can be done I suspect other than assume the hardware is iffy,
> rightly or wrongly. I'd have expected a lot more reports if it were
> the controller.
Hmm, okm thanks for the information. If it was possible, I'd be
extremely suspicious that the card's firmware was either buggy or
Linux didn't know how to repsond to the odd hardware variant; I don't
recall them producing that model of card for very long, so it's quite
possible there aren't many of them around and they have some kind of
timing quirk nobody knows about.
CRC issues aside, there is that other MULTWRITE_EXT error that only
occurs on hdi (and if I swap hdi and hdg, the error follows the
drive). The error also is specific to 2.6.15+, it does not occur on
the 2.6.12+patch that I switched from a month ago. I'm assuming that
since the drive/card stop giving BadCRC errors that they're able to
communicate successfully at the extremely low speed.
With a little more tinkering with hdparm I was able to determine that
the drives on the built-in controller and the primary bus of the PCI
controller were both in DMA mode, the former in udma4 and the latter
in udma3. The originally problematic drive (the one giving the
MULTWRITE_EXT errors) was in PIO mode, though "hdparm -d1 /dev/hdi"
"fixed" that problem and resulted in a drastic increase in drive bus
speed as measured by "hdparm -tT". (from 2MB/sec to around 23MB/sec
or so). hdi ended up in udma2 according to "hdparm -i"
Just for clarity, I'm repeating the _new_ error below. This one
recurs about once or twice an hour, but only on the samsung drive.
If the answer is (as it seems likely) "Your drive has bad firmware
but the error is totally harmless", then I'll be perfectly happy,
although I'd kind of prefer if the kernel could detect the buggy
firmware and work around it (maybe by switching back to whatever the
old behavior was, whenever changed). I'd otherwise be happy to git-
bisect except for the fact that a number of people rely on this
system for day-to-day activities.
> Mar 28 03:15:13 penelope kernel: hdi: status timeout: status=0xd0
> { Busy }
> Mar 28 03:15:13 penelope kernel: PDC202XX: Secondary channel reset.
> Mar 28 03:15:13 penelope kernel: hdi: no DRQ after issuing
> MULTWRITE_EXT
> Mar 28 03:15:13 penelope kernel: ide4: reset: success
The drive on the built-in controller is correctly set to udma4 mode,
though if I attempt to bump that up to udma5 (which is listed as
supported in "hdparm -i /dev/hda"), then the drive becomes completely
unresponsive until the next reboot. I'm waiting for the RAID to
finish rebuilding before I try increasing the UDMA speed on the other
drives to see what happens.
Thanks again for the help and consideration!
Cheers,
Kyle Moffett
^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <Pine.LNX.4.44.0604011333160.11853-100000@coffee.psychology.mcmaster.ca>]
* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
[not found] <Pine.LNX.4.44.0604011333160.11853-100000@coffee.psychology.mcmaster.ca>
@ 2006-04-02 0:05 ` Kyle Moffett
0 siblings, 0 replies; 17+ messages in thread
From: Kyle Moffett @ 2006-04-02 0:05 UTC (permalink / raw)
To: Mark Hahn, Alan Cox; +Cc: Robert Hancock, linux-ide, LKML Kernel
Please don't trim CC lists. I re-added LKML and others to the CC.
On Apr 1, 2006, at 13:40:42, Mark Hahn wrote:
>> ide: Assuming 33MHz system bus speed for PIO modes; override with
>> idebus=xx
> is it true that you haven't overridden this?
I leave all drives configured with the settings they have on boot.
At one time while setting the system up I tried playing with hdparm,
but that was long ago and my current /etc/hdparm.conf is empty.
>> PDC20268: IDE controller at PCI slot 0001:11:02.0
>> PDC20268: chipset revision 2
>> PDC20268: ROM enabled at 0x80090000
>> PDC20268: 100%% native mode on irq 52
>> ide3: BM-DMA at 0x1400-0x1407, BIOS settings: hdg:pio, hdh:pio
>> ide4: BM-DMA at 0x1408-0x140f, BIOS settings: hdi:pio, hdj:pio
> hmm, unkind of the bios to leave the ports programmed for PIO.
The problematic card is a FirmTek UltraTek/100 rebranded as a Sonnet
Tempo ATA/100. The chipset on the card is a PDC20268 with a mac-
bootable firmware. The system is an aging 400MHz Mac G4 [AGP
model]. Unfortunately this means that it's using whatever odd
OpenFirmware code it originally shipped with; I've never seen an
updater, and it most likely would require classic MacOS.
>> hda: max request size: 1024KiB
>> hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63,
>> UDMA(66)
>> hda: cache flushes supported
>> hda: [mac] hda1 hda2 hda3 hda4 hda5
> looks good, but that's the builtin disk, right?
The built-in primary (ATA-100?) controller has:
hda: a 80GB Seagate Barracuda 7200.7
The built-in secondary (ATA-66?) controller has:
hdc: a basic no-name brand CDROM
The built-in tertiary (ATA-33?) controller has no drives attached
The primary (IDE0) channel on the PDC20268 has:
hdg: a 80GB Maxtor DiamondMax Plus 9
The secondary (IDE1) channel on the PDC 20268 has:
hdi: a 80GB refurbished Samsung SP0822N
>> hdg: max request size: 128KiB
>> hdg: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63,
>> UDMA(100)
>> hdg: cache flushes supported
>> hdg:hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>> hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
>> ide: failed opcode was: unknown
>
> OK, so the add-in disks are trouble right from the start. have you
> checked your PATA cables? no more than 18" long? both _ends_
> plugged in (no stub if 1 disk/cable)?
All of the PATA cables are perfectly fine. I've tried at _least_ 5
different cables, including the 2 that shipped with the add-in IDE
controller and the 5 that came with the various drives (I've had to
replace 2 of them over the years, they're cheap commodity drives). I
also purchased a generic rounded IDE cable which I'm currently using
as a replacement to connect one of the drives to the add-in
controller due to space restrictions, although it had exactly the
same behavior as all of the other IDE cables I've ever tried. I seem
to recall replacing it with an ordinary ribbon cable on my last
onsite visit as I rearranged some of the internal hardware.
>> PDC202XX: Primary channel reset.
>> ide3: reset: success
> reset to what, I wonder, since the bios only provided programming
> for PIO.
I don't understand what this means, my comprehension of ATA/IDE
extends only as far as what I have read on this list :-\
>> [mac] hdg1 hdg2 hdg3 hdg4 hdg5
>> hdi: max request size: 1024KiB
>> hdi: 156368016 sectors (80060 MB) w/2048KiB Cache,
>> CHS=16383/255/63, UDMA(33)
> hmm, udma33 is a pretty low mode, should certainly avoid CRC errors
> even on quite bad cables.
>
>> hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>> hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
>> ide: failed opcode was: unknown
>
> the BadCRC means that there's definitely a problem with cable,
> power, overclocking or driver-controller-timer-programming.
As I mentioned above, I did check out the cables quite thoroughly,
including swapping them around, but the problem did not change. The
power supply itself was shipped with the case; which has 4 spaces for
mounting internal drives. When I first noticed the problem, I pulled
out an old oscilliscope and saw no problematic power fluctuations
during boot; and removing 2 of the drives and booting from CDROM did
not change the problem at all, the remaining drive on the PDC
controller still had the CRC errors.
On Apr 1, 2006, at 18:23:24, Alan Cox wrote:
> On Gwe, 2006-03-31 at 21:54 -0500, Kyle Moffett wrote:
>> IDE controller at a higher-than-supported speed. It gets errors
>> for a couple seconds and automatically drops the bus down to a
>> lower and safer speed.
>
> This indicates a problem somewhere. The drives and controller
> report their speed capabilities and if they can't meet the ones
> they are reporting something is very wrong somewhere and this is
> most definitely the first thing to debug.
I would not be surprised to find out that the OpenFirmware boot ROM
or the kernel incorrectly programmed PIO or DMA on this card (though
I know next to nothing about IDE, as you have seen). As far as I can
tell the hardware itself is all operating as well as can be expected
given its age and the commodity nature of the parts. If I had a
budget to replace the system I would in a heartbeat, but I'd like to
continue for as long as possible with what I have.
Thanks for all the assistance!
Cheers,
Kyle Moffett
^ permalink raw reply [flat|nested] 17+ messages in thread
[parent not found: <5VqEv-46l-49@gated-at.bofh.it>]
[parent not found: <20060328090211.4D6F34C04A@penelope.moffetthome.net>]
* [2.6.15] New ATA error messages on upgrade to 2.6.15
[not found] <20060328090211.4D6F34C04A@penelope.moffetthome.net>
@ 2006-03-28 17:57 ` Kyle Moffett
2006-03-31 22:16 ` [RESEND][2.6.15] " Kyle Moffett
0 siblings, 1 reply; 17+ messages in thread
From: Kyle Moffett @ 2006-03-28 17:57 UTC (permalink / raw)
To: LKML Kernel; +Cc: Bartlomiej Zolnierkiewicz, Alan Cox, linux-ide
I'm getting the following errors in my syslog on a fairly regular
basis (1 or 2 per hour). They seem to have started when I upgraded
from Debian 2.6.12-1-powerpc (with internal IDE patch) to Debian
2.6.15-1-powerpc. My best guess is for some reason the kernel
started issuing the command MULTWRITE_EXT that it didn't before, and
one of my drives doesn't like it. Two of the drives are attached to
a Promise PDC20268 (Rebranded a couple times by different
manufacturers and with mac-bootable firmware), the third is attached
to the internal ATA66 bus in the 400MHz powermac G4. My apologies if
this problem is known and fixed in 2.6.16; if necessary I'll wait
until Debian testing gets a 2.6.16 kernel and test that too.
Thanks for the help!
Cheers,
Kyle Moffett
Begin forwarded message:
> Security Events
> =-=-=-=-=-=-=-=
> Mar 28 03:15:13 penelope kernel: ide: failed opcode was: unknown
> Mar 28 03:30:13 penelope kernel: ide: failed opcode was: unknown
>
> System Events
> =-=-=-=-=-=-=
> Mar 28 03:15:13 penelope kernel: hdi: status timeout: status=0xd0
> { Busy }
> Mar 28 03:15:13 penelope kernel: PDC202XX: Secondary channel reset.
> Mar 28 03:15:13 penelope kernel: hdi: no DRQ after issuing
> MULTWRITE_EXT
> Mar 28 03:15:13 penelope kernel: ide4: reset: success
> Mar 28 03:30:13 penelope kernel: hdi: status timeout: status=0xd0
> { Busy }
> Mar 28 03:30:13 penelope kernel: PDC202XX: Secondary channel reset.
> Mar 28 03:30:13 penelope kernel: hdi: no DRQ after issuing
> MULTWRITE_EXT
> Mar 28 03:30:13 penelope kernel: ide4: reset: success
smartctl -a:
> smartctl version 5.34 [powerpc-unknown-linux-gnu] Copyright (C)
> 2002-5 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
> === START OF INFORMATION SECTION ===
> Device Model: SAMSUNG SP0822N
> Serial Number: S06QJ10Y946116
> Firmware Version: WA100-32
> User Capacity: 80,060,424,192 bytes
> Device is: In smartctl database [for details use: -P show]
> ATA Version is: 6
> ATA Standard is: ATA/ATAPI-6 T13 1410D revision 1
> Local Time is: Tue Mar 28 12:54:35 2006 EST
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> General SMART Values:
> Offline data collection status: (0x84) Offline data collection
> activity
> was suspended by an
> interrupting command from host.
> Auto Offline Data
> Collection: Enabled.
> Self-test execution status: ( 0) The previous self-test
> routine completed
> without error or no self-
> test has ever
> been run.
> Total time to complete Offline
> data collection: (1980) seconds.
> Offline data collection
> capabilities: (0x5b) SMART execute Offline
> immediate.
> Auto Offline data
> collection on/off support.
> Suspend Offline collection
> upon new
> command.
> Offline surface scan
> supported.
> Self-test supported.
> No Conveyance Self-test
> supported.
> Selective Self-test supported.
> SMART capabilities: (0x0003) Saves SMART data before
> entering
> power-saving mode.
> Supports SMART auto save
> timer.
> Error logging capability: (0x01) Error logging supported.
> No General Purpose Logging
> support.
> Short self-test routine
> recommended polling time: ( 2) minutes.
> Extended self-test routine
> recommended polling time: ( 33) minutes.
>
> SMART Attributes Data Structure revision number: 17
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
> UPDATED WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x000f 100 099 051 Pre-fail
> Always - 0
> 3 Spin_Up_Time 0x0007 252 252 011 Pre-fail
> Always - 0
> 4 Start_Stop_Count 0x0032 252 252 000 Old_age
> Always - 0
> 5 Reallocated_Sector_Ct 0x0033 252 252 011 Pre-fail
> Always - 0
> 7 Seek_Error_Rate 0x000f 252 252 051 Pre-fail
> Always - 0
> 8 Seek_Time_Performance 0x0025 092 092 015 Pre-fail
> Offline - 3665
> 9 Power_On_Half_Minutes 0x0032 099 099 000 Old_age
> Always - 32h+43m
> 10 Spin_Retry_Count 0x0033 252 252 051 Pre-fail
> Always - 0
> 11 Calibration_Retry_Count 0x0012 252 252 000 Old_age
> Always - 0
> 12 Power_Cycle_Count 0x0032 252 252 000 Old_age
> Always - 0
> 190 Unknown_Attribute 0x0022 154 133 000 Old_age
> Always - 33
> 194 Temperature_Celsius 0x0022 151 133 000 Old_age
> Always - 34
> 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age
> Always - 0
> 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age
> Always - 0
> 197 Current_Pending_Sector 0x0012 252 252 000 Old_age
> Always - 0
> 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age
> Offline - 0
> 199 UDMA_CRC_Error_Count 0x003e 199 199 000 Old_age
> Always - 173
> 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age
> Always - 0
> 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age
> Always - 0
>
> Warning! SMART ATA Error Log Structure error: invalid SMART checksum.
> SMART Error Log Version: 1
> No Errors Logged
>
> SMART Self-test log structure revision number 0
> Warning: ATA Specification requires self-test log structure
> revision number = 1
> Num Test_Description Status Remaining LifeTime
> (hours) LBA_of_first_error
> # 1 Short offline Completed without error 00%
> 3918 -
> # 2 Short offline Completed without error 00%
> 3894 -
> # 3 Extended offline Interrupted (host reset) 30%
> 3870 -
> # 4 Short offline Completed without error 00%
> 3846 -
> # 5 Short offline Completed without error 00%
> 3822 -
> # 6 Short offline Completed without error 00%
> 3798 -
> # 7 Short offline Completed without error 00%
> 3774 -
> # 8 Short offline Completed without error 00%
> 3750 -
> # 9 Short offline Completed without error 00%
> 3726 -
> #10 Extended offline Completed without error 00%
> 3703 -
> #11 Short offline Completed without error 00%
> 3678 -
> #12 Short offline Completed without error 00%
> 3654 -
> #13 Short offline Completed without error 00%
> 3630 -
> #14 Short offline Completed without error 00%
> 3606 -
> #15 Short offline Completed without error 00%
> 3582 -
> #16 Short offline Completed without error 00%
> 3558 -
> #17 Extended offline Completed without error 00%
> 3535 -
> #18 Short offline Completed without error 00%
> 3511 -
> #19 Short offline Completed without error 00%
> 3487 -
> #20 Short offline Completed without error 00%
> 3463 -
> #21 Short offline Completed without error 00%
> 3439 -
>
> SMART Selective Self-Test Log Data Structure Revision Number (0)
> should be 1
> SMART Selective self-test log data structure revision number 0
> Warning: ATA Specification requires selective self-test log data
> structure revision number = 1
> SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
> 1 0 0 Not_testing
> 2 0 0 Not_testing
> 3 281479271677952 0 Not_testing
> 4 0 281479271767952 Not_testing
> 5 604800 4 Not_testing
> Selective self-test flags (0x0):
> After scanning selected spans, do NOT read-scan remainder of disk.
> If Selective self-test is pending on power-up, resume after 0
> minute delay.
^ permalink raw reply [flat|nested] 17+ messages in thread* [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
2006-03-28 17:57 ` [2.6.15] " Kyle Moffett
@ 2006-03-31 22:16 ` Kyle Moffett
2006-03-31 22:21 ` Eric D. Mudama
0 siblings, 1 reply; 17+ messages in thread
From: Kyle Moffett @ 2006-03-31 22:16 UTC (permalink / raw)
To: LKML Kernel; +Cc: Bartlomiej Zolnierkiewicz, Alan Cox, linux-ide, Andrew Morton
I haven't received any response to this email over the last several
days, so I'm resending it in hopes that someone can help me track
down the problem. Thanks!
On Mar 28, 2006, at 12:57:29, Kyle Moffett wrote:
> I'm getting the following errors in my syslog on a fairly regular
> basis (1 or 2 per hour). They seem to have started when I upgraded
> from Debian 2.6.12-1-powerpc (with internal IDE patch) to Debian
> 2.6.15-1-powerpc. My best guess is for some reason the kernel
> started issuing the command MULTWRITE_EXT that it didn't before,
> and one of my drives doesn't like it. Two of the drives are
> attached to a Promise PDC20268 (Rebranded a couple times by
> different manufacturers and with mac-bootable firmware), the third
> is attached to the internal ATA66 bus in the 400MHz powermac G4.
> My apologies if this problem is known and fixed in 2.6.16; if
> necessary I'll wait until Debian testing gets a 2.6.16 kernel and
> test that too.
A few extra notes: The system is a Samba fileserver for a collection
of Windows XP clients, but the pattern of errors does not seem to be
triggered by load, including the daily backups. The hourly smart
checks also appear to have nothing to do with the error messages;
sometimes I'll get 10 in the middle of the night, other times almost
a full day of reasonable load will go by without a single message.
> Thanks for the help!
>
> Cheers,
> Kyle Moffett
>
> Begin forwarded message:
>> Security Events
>> =-=-=-=-=-=-=-=
>> Mar 28 03:15:13 penelope kernel: ide: failed opcode was: unknown
>> Mar 28 03:30:13 penelope kernel: ide: failed opcode was: unknown
>>
>> System Events
>> =-=-=-=-=-=-=
>> Mar 28 03:15:13 penelope kernel: hdi: status timeout: status=0xd0
>> { Busy }
>> Mar 28 03:15:13 penelope kernel: PDC202XX: Secondary channel reset.
>> Mar 28 03:15:13 penelope kernel: hdi: no DRQ after issuing
>> MULTWRITE_EXT
>> Mar 28 03:15:13 penelope kernel: ide4: reset: success
>> Mar 28 03:30:13 penelope kernel: hdi: status timeout: status=0xd0
>> { Busy }
>> Mar 28 03:30:13 penelope kernel: PDC202XX: Secondary channel reset.
>> Mar 28 03:30:13 penelope kernel: hdi: no DRQ after issuing
>> MULTWRITE_EXT
>> Mar 28 03:30:13 penelope kernel: ide4: reset: success
>
> smartctl -a:
>> smartctl version 5.34 [powerpc-unknown-linux-gnu] Copyright (C)
>> 2002-5 Bruce Allen
>> Home page is http://smartmontools.sourceforge.net/
>>
>> === START OF INFORMATION SECTION ===
>> Device Model: SAMSUNG SP0822N
>> Serial Number: S06QJ10Y946116
>> Firmware Version: WA100-32
>> User Capacity: 80,060,424,192 bytes
>> Device is: In smartctl database [for details use: -P show]
>> ATA Version is: 6
>> ATA Standard is: ATA/ATAPI-6 T13 1410D revision 1
>> Local Time is: Tue Mar 28 12:54:35 2006 EST
>> SMART support is: Available - device has SMART capability.
>> SMART support is: Enabled
>>
>> === START OF READ SMART DATA SECTION ===
>> SMART overall-health self-assessment test result: PASSED
>>
>> General SMART Values:
>> Offline data collection status: (0x84) Offline data collection
>> activity
>> was suspended by an
>> interrupting command from host.
>> Auto Offline Data
>> Collection: Enabled.
>> Self-test execution status: ( 0) The previous self-test
>> routine completed
>> without error or no self-
>> test has ever
>> been run.
>> Total time to complete Offline
>> data collection: (1980) seconds.
>> Offline data collection
>> capabilities: (0x5b) SMART execute Offline
>> immediate.
>> Auto Offline data
>> collection on/off support.
>> Suspend Offline collection
>> upon new
>> command.
>> Offline surface scan
>> supported.
>> Self-test supported.
>> No Conveyance Self-test
>> supported.
>> Selective Self-test
>> supported.
>> SMART capabilities: (0x0003) Saves SMART data before
>> entering
>> power-saving mode.
>> Supports SMART auto save
>> timer.
>> Error logging capability: (0x01) Error logging supported.
>> No General Purpose Logging
>> support.
>> Short self-test routine
>> recommended polling time: ( 2) minutes.
>> Extended self-test routine
>> recommended polling time: ( 33) minutes.
>>
>> SMART Attributes Data Structure revision number: 17
>> Vendor Specific SMART Attributes with Thresholds:
>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
>> UPDATED WHEN_FAILED RAW_VALUE
>> 1 Raw_Read_Error_Rate 0x000f 100 099 051 Pre-fail
>> Always - 0
>> 3 Spin_Up_Time 0x0007 252 252 011 Pre-fail
>> Always - 0
>> 4 Start_Stop_Count 0x0032 252 252 000 Old_age
>> Always - 0
>> 5 Reallocated_Sector_Ct 0x0033 252 252 011 Pre-fail
>> Always - 0
>> 7 Seek_Error_Rate 0x000f 252 252 051 Pre-fail
>> Always - 0
>> 8 Seek_Time_Performance 0x0025 092 092 015 Pre-fail
>> Offline - 3665
>> 9 Power_On_Half_Minutes 0x0032 099 099 000 Old_age
>> Always - 32h+43m
>> 10 Spin_Retry_Count 0x0033 252 252 051 Pre-fail
>> Always - 0
>> 11 Calibration_Retry_Count 0x0012 252 252 000 Old_age
>> Always - 0
>> 12 Power_Cycle_Count 0x0032 252 252 000 Old_age
>> Always - 0
>> 190 Unknown_Attribute 0x0022 154 133 000 Old_age
>> Always - 33
>> 194 Temperature_Celsius 0x0022 151 133 000 Old_age
>> Always - 34
>> 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age
>> Always - 0
>> 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age
>> Always - 0
>> 197 Current_Pending_Sector 0x0012 252 252 000 Old_age
>> Always - 0
>> 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age
>> Offline - 0
>> 199 UDMA_CRC_Error_Count 0x003e 199 199 000 Old_age
>> Always - 173
>> 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age
>> Always - 0
>> 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age
>> Always - 0
>>
>> Warning! SMART ATA Error Log Structure error: invalid SMART checksum.
>> SMART Error Log Version: 1
>> No Errors Logged
>>
>> SMART Self-test log structure revision number 0
>> Warning: ATA Specification requires self-test log structure
>> revision number = 1
>> Num Test_Description Status Remaining
>> LifeTime(hours) LBA_of_first_error
>> # 1 Short offline Completed without error 00%
>> 3918 -
>> # 2 Short offline Completed without error 00%
>> 3894 -
>> # 3 Extended offline Interrupted (host reset) 30%
>> 3870 -
>> # 4 Short offline Completed without error 00%
>> 3846 -
>> # 5 Short offline Completed without error 00%
>> 3822 -
>> # 6 Short offline Completed without error 00%
>> 3798 -
>> # 7 Short offline Completed without error 00%
>> 3774 -
>> # 8 Short offline Completed without error 00%
>> 3750 -
>> # 9 Short offline Completed without error 00%
>> 3726 -
>> #10 Extended offline Completed without error 00%
>> 3703 -
>> #11 Short offline Completed without error 00%
>> 3678 -
>> #12 Short offline Completed without error 00%
>> 3654 -
>> #13 Short offline Completed without error 00%
>> 3630 -
>> #14 Short offline Completed without error 00%
>> 3606 -
>> #15 Short offline Completed without error 00%
>> 3582 -
>> #16 Short offline Completed without error 00%
>> 3558 -
>> #17 Extended offline Completed without error 00%
>> 3535 -
>> #18 Short offline Completed without error 00%
>> 3511 -
>> #19 Short offline Completed without error 00%
>> 3487 -
>> #20 Short offline Completed without error 00%
>> 3463 -
>> #21 Short offline Completed without error 00%
>> 3439 -
>>
>> SMART Selective Self-Test Log Data Structure Revision Number (0)
>> should be 1
>> SMART Selective self-test log data structure revision number 0
>> Warning: ATA Specification requires selective self-test log data
>> structure revision number = 1
>> SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
>> 1 0 0 Not_testing
>> 2 0 0 Not_testing
>> 3 281479271677952 0 Not_testing
>> 4 0 281479271767952 Not_testing
>> 5 604800 4 Not_testing
>> Selective self-test flags (0x0):
>> After scanning selected spans, do NOT read-scan remainder of disk.
>> If Selective self-test is pending on power-up, resume after 0
>> minute delay.
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
2006-03-31 22:16 ` [RESEND][2.6.15] " Kyle Moffett
@ 2006-03-31 22:21 ` Eric D. Mudama
2006-03-31 23:13 ` Kyle Moffett
0 siblings, 1 reply; 17+ messages in thread
From: Eric D. Mudama @ 2006-03-31 22:21 UTC (permalink / raw)
To: Kyle Moffett
Cc: LKML Kernel, Bartlomiej Zolnierkiewicz, Alan Cox, linux-ide,
Andrew Morton
can you please post your dmesg?
On 3/31/06, Kyle Moffett <mrmacman_g4@mac.com> wrote:
> I haven't received any response to this email over the last several
> days, so I'm resending it in hopes that someone can help me track
> down the problem. Thanks!
>
> On Mar 28, 2006, at 12:57:29, Kyle Moffett wrote:
> > I'm getting the following errors in my syslog on a fairly regular
> > basis (1 or 2 per hour). They seem to have started when I upgraded
> > from Debian 2.6.12-1-powerpc (with internal IDE patch) to Debian
> > 2.6.15-1-powerpc. My best guess is for some reason the kernel
> > started issuing the command MULTWRITE_EXT that it didn't before,
> > and one of my drives doesn't like it. Two of the drives are
> > attached to a Promise PDC20268 (Rebranded a couple times by
> > different manufacturers and with mac-bootable firmware), the third
> > is attached to the internal ATA66 bus in the 400MHz powermac G4.
> > My apologies if this problem is known and fixed in 2.6.16; if
> > necessary I'll wait until Debian testing gets a 2.6.16 kernel and
> > test that too.
>
> A few extra notes: The system is a Samba fileserver for a collection
> of Windows XP clients, but the pattern of errors does not seem to be
> triggered by load, including the daily backups. The hourly smart
> checks also appear to have nothing to do with the error messages;
> sometimes I'll get 10 in the middle of the night, other times almost
> a full day of reasonable load will go by without a single message.
>
> > Thanks for the help!
> >
> > Cheers,
> > Kyle Moffett
> >
> > Begin forwarded message:
> >> Security Events
> >> =-=-=-=-=-=-=-=
> >> Mar 28 03:15:13 penelope kernel: ide: failed opcode was: unknown
> >> Mar 28 03:30:13 penelope kernel: ide: failed opcode was: unknown
> >>
> >> System Events
> >> =-=-=-=-=-=-=
> >> Mar 28 03:15:13 penelope kernel: hdi: status timeout: status=0xd0
> >> { Busy }
> >> Mar 28 03:15:13 penelope kernel: PDC202XX: Secondary channel reset.
> >> Mar 28 03:15:13 penelope kernel: hdi: no DRQ after issuing
> >> MULTWRITE_EXT
> >> Mar 28 03:15:13 penelope kernel: ide4: reset: success
> >> Mar 28 03:30:13 penelope kernel: hdi: status timeout: status=0xd0
> >> { Busy }
> >> Mar 28 03:30:13 penelope kernel: PDC202XX: Secondary channel reset.
> >> Mar 28 03:30:13 penelope kernel: hdi: no DRQ after issuing
> >> MULTWRITE_EXT
> >> Mar 28 03:30:13 penelope kernel: ide4: reset: success
> >
> > smartctl -a:
> >> smartctl version 5.34 [powerpc-unknown-linux-gnu] Copyright (C)
> >> 2002-5 Bruce Allen
> >> Home page is http://smartmontools.sourceforge.net/
> >>
> >> === START OF INFORMATION SECTION ===
> >> Device Model: SAMSUNG SP0822N
> >> Serial Number: S06QJ10Y946116
> >> Firmware Version: WA100-32
> >> User Capacity: 80,060,424,192 bytes
> >> Device is: In smartctl database [for details use: -P show]
> >> ATA Version is: 6
> >> ATA Standard is: ATA/ATAPI-6 T13 1410D revision 1
> >> Local Time is: Tue Mar 28 12:54:35 2006 EST
> >> SMART support is: Available - device has SMART capability.
> >> SMART support is: Enabled
> >>
> >> === START OF READ SMART DATA SECTION ===
> >> SMART overall-health self-assessment test result: PASSED
> >>
> >> General SMART Values:
> >> Offline data collection status: (0x84) Offline data collection
> >> activity
> >> was suspended by an
> >> interrupting command from host.
> >> Auto Offline Data
> >> Collection: Enabled.
> >> Self-test execution status: ( 0) The previous self-test
> >> routine completed
> >> without error or no self-
> >> test has ever
> >> been run.
> >> Total time to complete Offline
> >> data collection: (1980) seconds.
> >> Offline data collection
> >> capabilities: (0x5b) SMART execute Offline
> >> immediate.
> >> Auto Offline data
> >> collection on/off support.
> >> Suspend Offline collection
> >> upon new
> >> command.
> >> Offline surface scan
> >> supported.
> >> Self-test supported.
> >> No Conveyance Self-test
> >> supported.
> >> Selective Self-test
> >> supported.
> >> SMART capabilities: (0x0003) Saves SMART data before
> >> entering
> >> power-saving mode.
> >> Supports SMART auto save
> >> timer.
> >> Error logging capability: (0x01) Error logging supported.
> >> No General Purpose Logging
> >> support.
> >> Short self-test routine
> >> recommended polling time: ( 2) minutes.
> >> Extended self-test routine
> >> recommended polling time: ( 33) minutes.
> >>
> >> SMART Attributes Data Structure revision number: 17
> >> Vendor Specific SMART Attributes with Thresholds:
> >> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
> >> UPDATED WHEN_FAILED RAW_VALUE
> >> 1 Raw_Read_Error_Rate 0x000f 100 099 051 Pre-fail
> >> Always - 0
> >> 3 Spin_Up_Time 0x0007 252 252 011 Pre-fail
> >> Always - 0
> >> 4 Start_Stop_Count 0x0032 252 252 000 Old_age
> >> Always - 0
> >> 5 Reallocated_Sector_Ct 0x0033 252 252 011 Pre-fail
> >> Always - 0
> >> 7 Seek_Error_Rate 0x000f 252 252 051 Pre-fail
> >> Always - 0
> >> 8 Seek_Time_Performance 0x0025 092 092 015 Pre-fail
> >> Offline - 3665
> >> 9 Power_On_Half_Minutes 0x0032 099 099 000 Old_age
> >> Always - 32h+43m
> >> 10 Spin_Retry_Count 0x0033 252 252 051 Pre-fail
> >> Always - 0
> >> 11 Calibration_Retry_Count 0x0012 252 252 000 Old_age
> >> Always - 0
> >> 12 Power_Cycle_Count 0x0032 252 252 000 Old_age
> >> Always - 0
> >> 190 Unknown_Attribute 0x0022 154 133 000 Old_age
> >> Always - 33
> >> 194 Temperature_Celsius 0x0022 151 133 000 Old_age
> >> Always - 34
> >> 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age
> >> Always - 0
> >> 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age
> >> Always - 0
> >> 197 Current_Pending_Sector 0x0012 252 252 000 Old_age
> >> Always - 0
> >> 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age
> >> Offline - 0
> >> 199 UDMA_CRC_Error_Count 0x003e 199 199 000 Old_age
> >> Always - 173
> >> 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age
> >> Always - 0
> >> 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age
> >> Always - 0
> >>
> >> Warning! SMART ATA Error Log Structure error: invalid SMART checksum.
> >> SMART Error Log Version: 1
> >> No Errors Logged
> >>
> >> SMART Self-test log structure revision number 0
> >> Warning: ATA Specification requires self-test log structure
> >> revision number = 1
> >> Num Test_Description Status Remaining
> >> LifeTime(hours) LBA_of_first_error
> >> # 1 Short offline Completed without error 00%
> >> 3918 -
> >> # 2 Short offline Completed without error 00%
> >> 3894 -
> >> # 3 Extended offline Interrupted (host reset) 30%
> >> 3870 -
> >> # 4 Short offline Completed without error 00%
> >> 3846 -
> >> # 5 Short offline Completed without error 00%
> >> 3822 -
> >> # 6 Short offline Completed without error 00%
> >> 3798 -
> >> # 7 Short offline Completed without error 00%
> >> 3774 -
> >> # 8 Short offline Completed without error 00%
> >> 3750 -
> >> # 9 Short offline Completed without error 00%
> >> 3726 -
> >> #10 Extended offline Completed without error 00%
> >> 3703 -
> >> #11 Short offline Completed without error 00%
> >> 3678 -
> >> #12 Short offline Completed without error 00%
> >> 3654 -
> >> #13 Short offline Completed without error 00%
> >> 3630 -
> >> #14 Short offline Completed without error 00%
> >> 3606 -
> >> #15 Short offline Completed without error 00%
> >> 3582 -
> >> #16 Short offline Completed without error 00%
> >> 3558 -
> >> #17 Extended offline Completed without error 00%
> >> 3535 -
> >> #18 Short offline Completed without error 00%
> >> 3511 -
> >> #19 Short offline Completed without error 00%
> >> 3487 -
> >> #20 Short offline Completed without error 00%
> >> 3463 -
> >> #21 Short offline Completed without error 00%
> >> 3439 -
> >>
> >> SMART Selective Self-Test Log Data Structure Revision Number (0)
> >> should be 1
> >> SMART Selective self-test log data structure revision number 0
> >> Warning: ATA Specification requires selective self-test log data
> >> structure revision number = 1
> >> SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
> >> 1 0 0 Not_testing
> >> 2 0 0 Not_testing
> >> 3 281479271677952 0 Not_testing
> >> 4 0 281479271767952 Not_testing
> >> 5 604800 4 Not_testing
> >> Selective self-test flags (0x0):
> >> After scanning selected spans, do NOT read-scan remainder of disk.
> >> If Selective self-test is pending on power-up, resume after 0
> >> minute delay.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
2006-03-31 22:21 ` Eric D. Mudama
@ 2006-03-31 23:13 ` Kyle Moffett
0 siblings, 0 replies; 17+ messages in thread
From: Kyle Moffett @ 2006-03-31 23:13 UTC (permalink / raw)
To: Eric D. Mudama
Cc: LKML Kernel, Bartlomiej Zolnierkiewicz, Alan Cox, linux-ide,
Andrew Morton
On Mar 31, 2006, at 17:21:16, Eric D. Mudama wrote:
> can you please post your dmesg?
Dmesg below. Thanks for taking a look!
Cheers,
Kyle Moffett
Total memory = 832MB; using 2048kB for hash table (at c0400000)
Linux version 2.6.15-1-powerpc (Debian 2.6.15-3) (horms@verge.net.au)
(gcc version 4.0.3 20060115 (prerelease) (Debian 4.0.2-7)) #2 Thu Jan
19 03:51:42 UTC 2006
Found UniNorth memory controller & host bridge, revision: 7
Mapped at 0xfdf00000
Found a Keylargo mac-io controller, rev: 2, mapped at 0xfde80000
Processor NAP mode on idle enabled.
PowerMac motherboard: PowerMac G4 AGP Graphics
Found UniNorth PCI host bridge at 0xf0000000. Firmware bus number: 0->0
Found UniNorth PCI host bridge at 0xf2000000. Firmware bus number: 0->1
Found UniNorth PCI host bridge at 0xf4000000. Firmware bus number: 0->0
via-pmu: Server Mode is disabled
PMU driver 2 initialized for Core99, firmware: 0c
nvram: Checking bank 0...
nvram: gen0=366, gen1=367
nvram: Active bank is: 1
nvram: OF partition at 0x210
nvram: XP partition at 0x1220
nvram: NR partition at 0x1320
On node 0 totalpages: 212992
DMA zone: 196608 pages, LIFO batch:31
DMA32 zone: 0 pages, LIFO batch:0
Normal zone: 0 pages, LIFO batch:0
HighMem zone: 16384 pages, LIFO batch:3
Built 1 zonelists
Kernel command line: root=/dev/mapper/raid-root ro
PowerMac using OpenPIC irq controller at 0x80040000
OpenPIC Version 1.2 (4 CPUs and 64 IRQ sources) at fc62e000
OpenPIC timer frequency is 4.166666 MHz
PID hash table entries: 4096 (order: 12, 65536 bytes)
GMT Delta read from XPRAM: 0 minutes, DST: off
time_init: decrementer frequency = 24.907667 MHz
Console: colour dummy device 80x25
serial8250_console_init: nothing to do on PowerMac
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 835136k available (2172k kernel code, 944k data, 172k init,
65536k highmem)
AGP special page: 0xeffff000
Calibrating delay loop... 794.62 BogoMIPS (lpj=397312)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
device-tree: property "l2-cache" name conflicts with node in /cpus/
PowerPC,G4@0
checking if image is initramfs... it is
Freeing initrd memory: 3260k freed
NET: Registered protocol family 16
PCI: Probing PCI hardware
PCI: Enabling device 0001:11:02.0 (0004 -> 0007)
Registering openpic with sysfs...
Thermal assist unit using timers, shrink_timer: 2000 jiffies
audit: initializing netlink socket (disabled)
audit(1141624084.107:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
PCI: Enabling device 0000:00:10.0 (0086 -> 0087)
aty128fb: Invalid ROM signature 1111 should be 0xaa55
aty128fb: BIOS not located, guessing timings.
aty128fb: Rage128 PF PRO AGP [chip rev 0x1] 16M 128-bit SDR SGRAM (1:1)
Console: switching to colour frame buffer device 128x48
fb0: ATY Rage128 frame buffer device on Rage128 PF PRO AGP
Generic RTC Driver v1.07
Macintosh non-volatile memory driver v1.1
serial8250_init: nothing to do on PowerMac
pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
ttyS0 at MMIO 0x80013020 (irq = 22) is a Z85c30 ESCC - Serial port
ttyS1 at MMIO 0x80013000 (irq = 50) is a Z85c30 ESCC - Serial port
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
MacIO PCI driver attached to Keylargo chipset
input: Macintosh mouse button emulation as /class/input/input0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
adb: starting probe task...
adb: finished probe task...
ide0: Found Apple KeyLargo ATA-4 controller, bus ID 2, irq 19
Probing IDE interface ide0...
hda: ST380011A, ATA DISK drive
hda: Enabling Ultra DMA 4
ide0 at 0xf100e000-0xf100e007,0xf100e160 on irq 19
ide1: Found Apple KeyLargo ATA-3 controller, bus ID 0, irq 20
Probing IDE interface ide1...
hdc: CD-ROM Drive/F5A, ATAPI CD/DVD-ROM drive
hdc: Disabling (U)DMA for CD-ROM Drive/F5A (blacklisted)
ide1 at 0xf1016000-0xf1016007,0xf1016160 on irq 20
ide2: Found Apple KeyLargo ATA-3 controller, bus ID 1, irq 21
Probing IDE interface ide2...
mice: PS/2 mouse device common for all mice
Found KeyWest i2c on "uni-n", 2 channels, stepping: 4 bits
Found KeyWest i2c on "mac-io", 1 channel, stepping: 4 bits
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing unused kernel memory: 172k init
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected Apple UniNorth chipset
agpgart: configuring for size idx: 4
agpgart: AGP aperture is 16M @ 0x0
PDC20268: IDE controller at PCI slot 0001:11:02.0
PDC20268: chipset revision 2
PDC20268: ROM enabled at 0x80090000
PDC20268: 100%% native mode on irq 52
ide3: BM-DMA at 0x1400-0x1407, BIOS settings: hdg:pio, hdh:pio
ide4: BM-DMA at 0x1408-0x140f, BIOS settings: hdi:pio, hdj:pio
Probing IDE interface ide3...
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver
(PCI)
hdg: Maxtor 6Y080P0, ATA DISK drive
ide3 at 0x1440-0x1447,0x1432 on irq 52
Probing IDE interface ide4...
hdi: SAMSUNG SP0822N, ATA DISK drive
ide4 at 0x1420-0x1427,0x1412 on irq 52
r8169 Gigabit Ethernet driver 2.2LK loaded
PCI: Enabling device 0001:11:03.0 (0014 -> 0017)
eth0: Identified chip type is 'RTL8169s/8110s'.
eth0: RTL8169 at 0xf1060000, 00:08:54:d1:af:f9, IRQ 53
sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
PCI: Enabling device 0001:11:08.0 (0000 -> 0002)
ohci_hcd 0001:11:08.0: OHCI Host Controller
ohci_hcd 0001:11:08.0: new USB bus registered, assigned bus number 1
ohci_hcd 0001:11:08.0: irq 27, io mem 0x80083000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PHY ID: 406212, addr: 0
eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:30:65:96:77:a4
eth0: Found BCM5201 PHY
PCI: Enabling device 0001:11:09.0 (0000 -> 0002)
ohci_hcd 0001:11:09.0: OHCI Host Controller
ohci_hcd 0001:11:09.0: new USB bus registered, assigned bus number 2
ohci_hcd 0001:11:09.0: irq 28, io mem 0x80082000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 2-1: new full speed USB device using ohci_hcd and address 2
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 3 ports detected
usb 2-1.1: new full speed USB device using ohci_hcd and address 3
usbcore: registered new driver hiddev
eth_pub: Link is up at 100 Mbps, full-duplex.
drivers/usb/input/hid-core.c: timeout initializing reports
input: Mitsumi Electric Apple Extended USB Keyboard as /class/input/
input1
input: USB HID v1.10 Keyboard [Mitsumi Electric Apple Extended USB
Keyboard] on usb-0001:11:09.0-1.1
input: Mitsumi Electric Apple Extended USB Keyboard as /class/input/
input2
input: USB HID v1.10 Device [Mitsumi Electric Apple Extended USB
Keyboard] on usb-0001:11:09.0-1.1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
usbcore: registered new driver yealink
drivers/usb/input/yealink.c: Yealink phone driver:yld-20050816
hda: max request size: 1024KiB
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63,
UDMA(66)
hda: cache flushes supported
hda: [mac] hda1 hda2 hda3 hda4 hda5
hdg: max request size: 128KiB
hdg: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=65535/16/63,
UDMA(100)
hdg: cache flushes supported
hdg:hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
PDC202XX: Primary channel reset.
ide3: reset: success
[mac] hdg1 hdg2 hdg3 hdg4 hdg5
hdi: max request size: 1024KiB
hdi: 156368016 sectors (80060 MB) w/2048KiB Cache, CHS=16383/255/63,
UDMA(33)
hdi: cache flushes supported
hdi: [mac] hdi1 hdi2 hdi3 hdi4 hdi5
hdc: ATAPI 48X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.20
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
md: raid1 personality registered as nr 3
raid5: measuring checksumming speed
8regs : 488.000 MB/sec
8regs_prefetch: 408.000 MB/sec
32regs : 448.000 MB/sec
32regs_prefetch: 392.000 MB/sec
raid5: using function: 8regs (488.000 MB/sec)
md: raid5 personality registered as nr 4
md: md0 stopped.
md: bind<hda3>
md: bind<hdi3>
md: bind<hdg3>
raid1: raid set md0 active with 3 out of 3 mirrors
md: md1 stopped.
md: bind<hda4>
md: bind<hdi4>
md: bind<hdg4>
raid5: device hdg4 operational as raid disk 0
raid5: device hdi4 operational as raid disk 2
raid5: device hda4 operational as raid disk 1
raid5: allocated 3168kB for md1
raid5: raid level 5 set md1 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
--- rd:3 wd:3 fd:0
disk 0, o:1, dev:hdg4
disk 1, o:1, dev:hda4
disk 2, o:1, dev:hdi4
md: md2 stopped.
md: bind<hda5>
md: bind<hdi5>
md: bind<hdg5>
raid5: device hdg5 operational as raid disk 0
raid5: device hdi5 operational as raid disk 2
raid5: device hda5 operational as raid disk 1
raid5: allocated 3168kB for md2
raid5: raid level 5 set md2 active with 3 out of 3 devices, algorithm 2
RAID5 conf printout:
--- rd:3 wd:3 fd:0
disk 0, o:1, dev:hdg5
disk 1, o:1, dev:hda5
disk 2, o:1, dev:hdi5
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
cdrom: open failed.
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
PDC202XX: Primary channel reset.
ide3: reset: success
Adding 1048440k swap on /dev/md1. Priority:-1 extents:1 across:1048440k
EXT3-fs warning: maximal mount count reached, running e2fsck is
recommended
EXT3 FS on dm-0, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
input: PowerMac Beep as /class/input/input3
NET: Registered protocol family 15
eth_pub: Link is up at 100 Mbps, full-duplex.
eth_pub: Pause is disabled
r8169: eth_lan: link up
ip_tables: (C) 2000-2002 Netfilter core team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (6656 buckets, 53248 max) - 232 bytes per
conntrack
ClusterIP Version 0.8 loaded successfully
ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. http://
snowman.net/projects/ipt_recent/
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery
directory
NFSD: recovery directory /var/lib/nfs/v4recovery doesn't exist
NFSD: starting 90-second grace period
Initializing IPsec netlink socket
eth_pub: no IPv6 routers present
eth_lan: no IPv6 routers present
eth_pub: Link is up at 100 Mbps, full-duplex.
eth_pub: Pause is disabled
tun_624: Disabled Privacy Extensions
GRE over IPv4 tunneling driver
hdi: dma_timer_expiry: dma status == 0x21
hdi: DMA timeout error
hdi: dma timeout error: status=0xd0 { Busy }
ide: failed opcode was: unknown
hdi: DMA disabled
PDC202XX: Secondary channel reset.
ide4: reset: success
[... ad nauseum ...]
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2006-04-03 12:33 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <5WD6n-5fR-9@gated-at.bofh.it>
[not found] ` <5WD6n-5fR-11@gated-at.bofh.it>
[not found] ` <5WD6n-5fR-13@gated-at.bofh.it>
[not found] ` <5WD6n-5fR-15@gated-at.bofh.it>
[not found] ` <5WD6n-5fR-17@gated-at.bofh.it>
[not found] ` <5WD6n-5fR-7@gated-at.bofh.it>
[not found] ` <5WEvy-7az-7@gated-at.bofh.it>
2006-04-01 19:03 ` [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15 Robert Hancock
2006-04-01 19:13 ` Kyle Moffett
2006-04-03 11:35 Mikael Pettersson
2006-04-03 12:32 ` Kyle Moffett
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 9:07 Mikael Pettersson
2006-04-03 9:29 ` Alan Cox
[not found] <Pine.LNX.4.44.0604021508540.2653-100000@coffee.psychology.mcmaster.ca>
2006-04-02 19:55 ` Kyle Moffett
2006-04-02 21:24 ` Alan Cox
2006-04-02 22:00 ` Mark Hahn
2006-04-02 23:17 ` Kyle Moffett
[not found] <Pine.LNX.4.44.0604011333160.11853-100000@coffee.psychology.mcmaster.ca>
2006-04-02 0:05 ` Kyle Moffett
[not found] <5VqEv-46l-49@gated-at.bofh.it>
[not found] ` <5VqEv-46l-47@gated-at.bofh.it>
[not found] ` <5WA8u-X3-5@gated-at.bofh.it>
[not found] ` <5WAi6-19q-13@gated-at.bofh.it>
[not found] ` <5WB4M-2kX-29@gated-at.bofh.it>
2006-04-01 1:21 ` Robert Hancock
2006-04-01 2:54 ` Kyle Moffett
2006-04-01 23:23 ` Alan Cox
[not found] <20060328090211.4D6F34C04A@penelope.moffetthome.net>
2006-03-28 17:57 ` [2.6.15] " Kyle Moffett
2006-03-31 22:16 ` [RESEND][2.6.15] " Kyle Moffett
2006-03-31 22:21 ` Eric D. Mudama
2006-03-31 23:13 ` Kyle Moffett
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.