error message while booting dma_intr:error=0x51 ...?

error message while booting dma_intr:error=0x51 ...?

Post by somez7 » Thu, 29 Aug 2002 06:56:31



in the middle of booting message , I got error message as follows.

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 }
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 }

I'd like to know why I get this kind of message.
After booting , the linux works well.
I wondoer if I can ignore it or not?

This is my whole booting message.
==========================
Linux version 2.4.5-3 (gcc version 2.95.3 20010315 (release)) #1 Thu Aug 2
17:18:07 JST 2001
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000006ff0000 (usable)
 BIOS-e820: 0000000006ff0000 - 0000000006ff3000 (ACPI NVS)
 BIOS-e820: 0000000006ff3000 - 0000000007000000 (ACPI data)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 28656
zone(0): 4096 pages.
zone(1): 24560 pages.
zone(2): 0 pages.
Kernel command line: auto BOOT_IMAGE=linux ro root=301
BOOT_FILE=/boot/vmlinuz
Initializing CPU#0
Detected 664.983 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 1327.10 BogoMIPS
Memory: 109720k/114624k available (1464k kernel code, 4520k reserved, 447k
data, 248k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
CPU: Before vendor init, caps: 00803035 80803035 00000000, vendor = 5
CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 64K (32 bytes/line)
CPU: After vendor init, caps: 00803135 80803035 00000000 00000000
CPU:     After generic, caps: 00803135 80803035 00000000 00000000
CPU:             Common caps: 00803135 80803035 00000000 00000000
CPU: Centaur VIA Ezra stepping 08
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX

mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfb560, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 0: assuming transparent
PCI: Using IRQ router VIA [1106/0686] at 00:07.0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.14)
Starting kswapd v1.8
allocated 32 pages and 32 bhs reserved for the highmem bounces
VFS: Diskquotas version dquot_6.5.0 initialized

devfs: boot_options: 0x2
Journalled Block Device driver loaded
vesafb: framebuffer at 0xe0000000, mapped to 0xc7800000, size 15296k
vesafb: mode is 1024x768x16, linelength=2048, pages=8
vesafb: protected mode interface info at c000:76f7
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Serial driver version 5.05b (2001-05-03) with HUB-6 MANY_PORTS MULTIPORT
SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
block: queued sectors max/low 72626kB/24208kB, 256 slots per queue
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
hda: SAMSUNG SV0842D, ATA DISK drive
hdb: SONY CDU4811, ATAPI CD/DVD-ROM drive
hdc: SanDisk SDCFB-256, ATA DISK drive
hdc: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hdc: set_drive_speed_status: error=0x04 { DriveStatusError }
ide1: Drive 0 didn't accept speed setting. Oh, well.
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 16514064 sectors (8455 MB) w/472KiB Cache, CHS=1027/255/63, UDMA(66)
hdc: 501760 sectors (257 MB) w/1KiB Cache, CHS=980/16/32
hdb: ATAPI 48X CD-ROM drive, 120kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
Partition check:
 /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 >
 /dev/ide/host0/bus1/target0/lun0: p1
FDC 0 is a post-1991 82077
Loading I2O Core - (c) Copyright 1999 Red Hat Software
I2O configuration manager v 0.04.
  (C) Copyright 1999 Red Hat Software
loop: loaded (max 8 devices)
Cronyx Ltd, Synchronous PPP and CISCO HDLC (c) 1994
Linux port (c) 1998 Building Number Three Ltd & Jan "Yenya" Kasprzak.
SCSI subsystem driver Revision: 1.00
request_module[scsi_hostadapter]: Root fs not mounted
ACPI: Disabled, if you use ACPI, please add boot option "apm=off acpi=on"
md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md.c: sizeof(mdp_super_t) = 4096
autodetecting RAID arrays
autorun ...
... autorun DONE.
LVM version 0.9.1_beta3  by Heinz Mauelshagen  (25/01/2001)
lvm -- Driver successfully initialized
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 248k freed
================= from here =================
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 }
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 }
================== =================
hdb: DMA disabled
ide0: reset: success
Real Time Clock Driver v1.10d
Adding Swap: 265064k swap-space (priority -1)
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.259 $ time 17:33:00 Aug  2 2001
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 12 for device 00:07.2
PCI: Sharing IRQ 12 with 00:07.3
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
PCI: Enabling device 00:07.3 (0000 -> 0001)
PCI: Found IRQ 12 for device 00:07.3
PCI: Sharing IRQ 12 with 00:07.2
usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 12
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.251:USB Universal Host Controller Interface driver
8139too Fast Ethernet driver 0.9.15c loaded
PCI: Found IRQ 11 for device 00:0b.0
PCI: Sharing IRQ 11 with 00:07.5
eth0: RealTek RTL8139 Fast Ethernet at 0xc872d000, 00:04:5f:00:40:58, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8139C'
eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
eth0: no IPv6 routers present
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability
45e1.
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability
45e1.
eth0: no IPv6 routers present
VFS: Disk change detected on device ide1(22,1)
 /dev/ide/host0/bus1/target0/lun0: p1
VFS: Disk change detected on device ide1(22,1)
 /dev/ide/host0/bus1/target0/lun0: p1
VFS: Disk change detected on device ide1(22,1)
 /dev/ide/host0/bus1/target0/lun0: p1
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

 
 
 

error message while booting dma_intr:error=0x51 ...?

Post by mjt » Wed, 28 Aug 2002 15:12:59


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message


> in the middle of booting message , I got error message as follows.

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

considering you're using a 2.4.xx kernel and the controller seems
to be supported, it might be that the drive is heading out the
door. might want to run badblocks (man badblocks) to see if
anything turns up.  you might want to, at some time, upgrade the
distro.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Michael J. Tobler: motorcyclist, surfer,  #    Black holes result
 skydiver, and author: "Inside Linux",     #   when God divides the  
 "C++ HowTo", "C++ Unleashed"              #     universe by zero

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9axgetTveLPAHcDIRAg+sAJ9fshV+16sMWaorFAuvvOQGHW2v/gCeM6gn
2OfbohZelgwWOfj2esoZhO0=
=K9zR
-----END PGP SIGNATURE-----

 
 
 

error message while booting dma_intr:error=0x51 ...?

Post by Natma » Thu, 29 Aug 2002 13:10:06



Quote:> in the middle of booting message , I got error message as follows.

> 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 }
> 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 }

mjt mentioned that the drive could be failing, but it could also be the
IDE cable too.  I've seen perfectly good drives act weird because
a cable suddenly went 'bad'.  You may try connecting the drive with
a different cable, or to a different computer and see if that fixes it.

Nathan