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

Bug#394049: marked as done (DriveReady SeekComplete Error)



Your message dated Tue, 14 Aug 2007 22:35:40 +0200
with message-id <20070814203540.GB7247@baikonur.stro.at>
and subject line Bug#394049: Problem identified
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: <debian>
Version: <debian-31r3-i386-netinst>
"Stable" version

Hello:

I want to report the following bug that seems to have been blamed on hardware.


kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }


This is *not* a hardware problem or a CD problem. This problems has been replicated on different hard disks and on another similar computer. Many others have seemed to have experienced it since 2005. (see links below) The common resolution has been to change to another distribution like Fedora or Suse.

So far I have found it in Ubuntu and Debian distributions. Other MS OS's work fine on these computers. (Win95, Win98SE, W3K) I suspect that it may be related to the Debian support of the southbridge PIIX4 chipset and/or the Intel 440BX and 440LX AGPset.

http://groups.google.com/groups?as_q=DriveStatusError+&num=10&scoring=r&hl=en&as_epq=&as_oq=&as_eq=&as_ugroup=linux.debian.bugs.dist&as_usubject=&as_uauthors=&lr=&as_drrb=q&as_qdr=&as_mind=1&as_minm=1&as_miny=1981&as_maxd=18&as_maxm=10&as_maxy=2006&safe=off
http://www.ubuntuforums.org/showthread.php?t=267949&highlight=drivestatuserror
http://www.ubuntuforums.org/showthread.php?t=249447&highlight=drivestatuserror
http://www.ubuntuforums.org/showthread.php?t=273015&highlight=drivestatuserror


#uname -a
Linux server1.example.com 2.4.27-3-386 #1 Thu Sep 14 08:44:58 UTC 2006 i686 GNU/Linux

#dpkg -s libc6 | grep ^Version
Version: 2.3.2.ds1-22sarge4

full dmesg is attached

abbreviated syslog:
Oct 17 01:23:14 localhost termwrap: info: Switching console charset mapping to C
Oct 17 01:36:53 localhost kernel: cdrom: open failed.
Oct 17 01:38:03 localhost dhclient: DHCPREQUEST on eth0 to 192.168.2.2 port 67
Oct 17 01:38:03 localhost dhclient: DHCPACK from 192.168.2.2
Oct 17 01:38:03 localhost dhclient: bound to 192.168.2.22 -- renewal in 900 seconds. Oct 17 01:50:39 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 17 01:50:39 localhost kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 17 01:50:49 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 17 01:50:49 localhost kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 17 01:50:49 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 17 01:50:49 localhost kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 17 01:50:49 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 17 01:50:49 localhost kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 17 01:50:49 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Oct 17 01:50:49 localhost kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Oct 17 01:50:49 localhost kernel: blk: queue d8825b40, I/O limit 4095Mb (mask 0xffffffff)
Oct 17 01:50:49 localhost kernel: hdb: DMA disabled
Oct 17 01:50:49 localhost kernel: ide0: reset: success
Oct 17 01:52:31 localhost lpd[2983]: restarted
Oct 17 01:52:36 localhost rpc.statd[3056]: Version 1.0.6 Starting
Oct 17 01:52:36 localhost rpc.statd[3056]: statd running as root. chown /var/lib/nfs/sm to choose different user Oct 17 01:53:03 localhost dhclient: DHCPREQUEST on eth0 to 192.168.2.2 port 67
Oct 17 01:53:03 localhost dhclient: DHCPACK from 192.168.2.2
Oct 17 01:53:03 localhost dhclient: bound to 192.168.2.22 -- renewal in 900 seconds.

Linux version 2.4.27-3-386 (pbuilder@dl360-g3) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #1 Thu Sep 14 08:44:58 UTC 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000017ffd000 (usable)
 BIOS-e820: 0000000017ffd000 - 0000000017fff000 (ACPI data)
 BIOS-e820: 0000000017fff000 - 0000000018000000 (ACPI NVS)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
383MB LOWMEM available.
On node 0 totalpages: 98301
zone(0): 4096 pages.
zone(1): 94205 pages.
zone(2): 0 pages.
ACPI disabled because your bios is from 99 and too old
You can enable it with acpi=force
Kernel command line: root=/dev/hda1 ro 
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
Detected 334.096 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 666.82 BogoMIPS
Memory: 382952k/393204k available (1070k kernel code, 9868k reserved, 458k data, 96k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU:     After generic, caps: 0183fbff 00000000 00000000 00000000
CPU:             Common caps: 0183fbff 00000000 00000000 00000000
CPU: Intel Celeron (Mendocino) stepping 00
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 334.0776 MHz.
..... host bus clock speed is 66.8153 MHz.
cpu: 0, clocks: 668153, slice: 334076
CPU0<T0:668144,T1:334064,D:4,S:334076,C:668153>
ACPI: Subsystem revision 20040326
ACPI: Interpreter disabled.
PCI: PCI BIOS revision 2.10 entry at 0xf0720, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router PIIX/ICH [8086/7110] at 00:04.0
Limiting direct PCI/PCI transfers.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
COMX: driver version 0.85 (C) 1995-1999 ITConsult-Pro Co. <info@itc.hu>
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 3708 blocks [1 disk] into ram disk... |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\done.
Freeing initrd memory: 3708k freed
VFS: Mounted root (cramfs filesystem).
Freeing unused kernel memory: 96k freed
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide: late registration of driver.
PIIX4: IDE controller at PCI slot 00:04.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
hda: Maxtor 90640D4, ATA DISK drive
hdb: ST3660A, ATA DISK drive
blk: queue d8825b40, I/O limit 4095Mb (mask 0xffffffff)
blk: queue d8825c7c, I/O limit 4095Mb (mask 0xffffffff)
hdc: COMPAQ CDR-8435, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: 12594960 sectors (6449 MB) w/256KiB Cache, CHS=12495/16/63, UDMA(33)
hdb: attached ide-disk driver.
hdb: 1065456 sectors (546 MB) w/120KiB Cache, CHS=1057/16/63, DMA
Partition check:
 /dev/ide/host0/bus0/target0/lun0: [PTBL] [784/255/63] p1
 /dev/ide/host0/bus0/target1/lun0: [PTBL] [66/255/63] p1
Journalled Block Device driver loaded
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding Swap: 530104k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
Real Time Clock Driver v1.10f
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: attached ide-cdrom driver.
hdc: ATAPI 32X CD-ROM drive, 128kB Cache, DMA
Uniform CD-ROM driver Revision: 3.12
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 321M
agpgart: Detected Intel 440BX chipset
agpgart: AGP aperture is 64M @ 0xe4000000
Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
PCI: Found IRQ 10 for device 00:0a.0
tulip0:  MII transceiver #1 config 3100 status 7869 advertising 05e1.
tulip0:  MII transceiver #2 config 1000 status 786d advertising 05e1.
tulip0:  MII transceiver #3 config 1000 status 786d advertising 05e1.
tulip0:  MII transceiver #4 config 1000 status 786d advertising 05e1.
eth0: ADMtek Comet rev 17 at 0xd000, 00:04:5A:6E:8C:F0, IRQ 10.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
SCSI subsystem driver Revision: 1.00
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 }
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
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 }
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 08:57:38 Sep 14 2006
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 12 for device 00:04.2
usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 12
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
uhci.c: USB Universal Host Controller Interface driver v1.1
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x1001
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x1001
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.

--- End Message ---
--- Begin Message ---
On Tue, Aug 14, 2007 at 10:07:15PM +0200, Jan Harnisch wrote:
> Hello again,
> 
> although I was not yet able to do the test with the newest kernel, I 
> have managed to locate the reason for the problem (at least on my 
> machine): While both the mainboard and the harddisk support UDMA5, I 
> originally had connected them with a 40-core cable. Since I replaced 
> this with a 80-core, the machine runs in UDMA5 mode without error 
> messages. So I guess the kernel is not to blame.

citing Documetation/ide.txt
- 40-conductor IDE cables are capable of transferring data in DMA modes
  up to udma2, but no faster.

> Still I think that maybe it would be a good thing to be able to override 
> the kernel-selected DMA mode with a bootprompt parameter...

you seem to want to read that file ;)

closing

-- 
maks

--- End Message ---

Reply to: