All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: ide errors in 7-rc1-mm1 and later
Date: Thu, 3 Jun 2004 22:07:25 -0400	[thread overview]
Message-ID: <200406032207.25602.edt@aei.ca> (raw)
In-Reply-To: <200405271928.33451.edt@aei.ca>

Hi,

I am still getting these ide errors with 7-rc2-mm2.  I  get the errors even
if I mount with barrier=0 (or just defaults).  It would seem that something is 
sending my drive commands it does not understand...  

May 27 18:18:05 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
May 27 18:18:05 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }

How can we find out what is wrong?

This does not seem to be an error that corrupts the fs, it just slows things 
down when it hits a group of these.  Note that they keep poping up - they
do stop (I still get them hours after booting).

TIA
Ed Tomlinson

----------------------
7-mm4	ok
7-mm5 	na
7-rc1-mm1 errors
7-rc2	ok
7-rc2-mm2 errors

CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDETAPE=m
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPNP=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y

> Think this is not just a barrier problem (unless barrier is the default).
> One if my two drives gets the error below during operation.
> The drive is the root drive and is mounted with defaults.  2.6.6-mm4
> was the last kernel booted on this box.   The 2.6.7-rc1-mm1 was compiled
> with 2.95 with the following fs options:
> 
> CONFIG_EXT2_FS=y
> # CONFIG_EXT2_FS_XATTR is not set
> CONFIG_EXT3_FS=m
> # CONFIG_EXT3_FS_XATTR is not set
> CONFIG_JBD=m
> # CONFIG_JBD_DEBUG is not set
> CONFIG_REISERFS_FS=y
> # CONFIG_REISERFS_CHECK is not set
> # CONFIG_REISERFS_PROC_INFO is not set
> # CONFIG_REISERFS_FS_XATTR is not set
> # CONFIG_JFS_FS is not set
> # CONFIG_XFS_FS is not set
> # CONFIG_MINIX_FS is not set
> # CONFIG_ROMFS_FS is not set
> # CONFIG_QUOTA is not set
> # CONFIG_AUTOFS_FS is not set
> CONFIG_AUTOFS4_FS=m

Disk /dev/hda: 6448 MB, 6448619520 bytes
240 heads, 63 sectors/track, 833 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1          99      748408+  82  Linux swap
/dev/hda2             100         108       68040   83  Linux
/dev/hda3   *         109         833     5481000   83  Linux

> hda reports:
> root@bert:/usr/src/linux# hdparm -iI /dev/hda
> 
> /dev/hda:
> 
>  Model=WDC AC26400R, FwRev=15.01J15, SerialNo=WD-WM6271600165
>  Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
>  RawCHS=13328/15/63, TrkSize=57600, SectSize=600, ECCbytes=40
>  BuffType=DualPortCache, BuffSize=512kB, MaxMultSect=16, MultSect=16
>  CurCHS=13328/15/63, CurSects=12594960, LBA=yes, LBAsects=12594960
>  IORDY=on/off, tPIO={min:160,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
>  AdvancedPM=no WriteCache=enabled
>  Drive conforms to: device does not report version:  1 2 3 4
> 
>  * signifies the current active mode
> 
> 
> ATA device, with non-removable media
>         Model Number:       WDC AC26400R
>         Serial Number:      WD-WM6271600165
>         Firmware Revision:  15.01J15
> Standards:
>         Supported: 4 3 2 1
>         Likely used: 4
> Configuration:
>         Logical         max     current
>         cylinders       13328   13328
>         heads           15      15
>         sectors/track   63      63
>         --
>         bytes/track: 57600      bytes/sector: 600
>         CHS current addressable sectors:   12594960
>         LBA    user addressable sectors:   12594960
>         device size with M = 1024*1024:        6149 MBytes
>         device size with M = 1000*1000:        6448 MBytes (6 GB)
> Capabilities:
>         LBA, IORDY(can be disabled)
>         Buffer size: 512.0kB    bytes avail on r/w long: 40     Queue depth: 1
>         Standby timer values: spec'd by Standard, no device specific minimum
>         R/W multiple sector transfer: Max = 16  Current = 16
>         DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
>              Cycle time: min=120ns recommended=120ns
>         PIO: pio0 pio1 pio2 pio3 pio4
>              Cycle time: no flow control=160ns  IORDY flow control=120ns
> Commands/features:
>         Enabled Supported:
>            *    READ BUFFER cmd
>            *    WRITE BUFFER cmd
>            *    Look-ahead
>            *    Write cache
>            *    Power Management feature set
>            *    SMART feature set
> 
> root@bert:/usr/src/linux# hdparm -iI /dev/hdb
> 
> /dev/hdb:
> 
>  Model=Maxtor 6E030L0, FwRev=NAR61590, SerialNo=E178CV5E
>  Config={ Fixed }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
>  BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
>  CurCHS=17475/15/63, CurSects=16513875, LBA=yes, LBAsects=60058656
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4
>  DMA modes:  mdma0 mdma1 mdma2
>  UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5 udma6
>  AdvancedPM=yes: disabled (255) WriteCache=enabled
>  Drive conforms to: (null):
> 
>  * signifies the current active mode
> 
> 
> ATA device, with non-removable media
>         Model Number:       Maxtor 6E030L0
>         Serial Number:      E178CV5E
>         Firmware Revision:  NAR61590
> Standards:
>         Supported: 7 6 5 4
>         Likely used: 7
> Configuration:
>         Logical         max     current
>         cylinders       16383   17475
>         heads           16      15
>         sectors/track   63      63
>         --
>         CHS current addressable sectors:   16513875
>         LBA    user addressable sectors:   60058656
>         device size with M = 1024*1024:       29325 MBytes
>         device size with M = 1000*1000:       30750 MBytes (30 GB)
> Capabilities:
>         LBA, IORDY(can be disabled)
>         Queue depth: 1
>         Standby timer values: spec'd by Standard, no device specific minimum
>         R/W multiple sector transfer: Max = 16  Current = 16
>         Advanced power management level: unknown setting (0x0000)
>         Recommended acoustic management value: 192, current value: 254
>         DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5 udma6
>              Cycle time: min=120ns recommended=120ns
>         PIO: pio0 pio1 pio2 pio3 pio4
>              Cycle time: no flow control=120ns  IORDY flow control=120ns
> Commands/features:
>         Enabled Supported:
>            *    NOP cmd
>            *    READ BUFFER cmd
>            *    WRITE BUFFER cmd
>            *    Host Protected Area feature set
>            *    Look-ahead
>            *    Write cache
>            *    Power Management feature set
>                 Security Mode feature set
>            *    SMART feature set
>            *    FLUSH CACHE EXT command
>            *    Mandatory FLUSH CACHE command
>            *    Device Configuration Overlay feature set
>            *    Automatic Acoustic Management feature set
>                 SET MAX security extension
>                 Advanced Power Management feature set
>            *    DOWNLOAD MICROCODE cmd
>            *    SMART self-test
>            *    SMART error logging
> Security:
>         Master password revision code = 65534
>                 supported
>         not     enabled
>         not     locked
>         not     frozen
>         not     expired: security count
>         not     supported: enhanced erase
> HW reset results:
>         CBLID- above Vih
>         Device num = 1 determined by CSEL
> Checksum: correct
> 
> hdb is accessed via dm and evms.   This is what the boot of reports:
> 
> May 27 18:17:39 bert kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> May 27 18:17:39 bert kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> May 27 18:17:39 bert kernel: PIIX4: IDE controller at PCI slot 0000:00:14.1
> May 27 18:17:39 bert kernel: PIIX4: chipset revision 1
> May 27 18:17:39 bert kernel: PIIX4: not 100%% native mode: will probe irqs later
> May 27 18:17:39 bert kernel:     ide0: BM-DMA at 0x10c0-0x10c7, BIOS settings: hda:pio, hdb:DMA
> May 27 18:17:39 bert kernel:     ide1: BM-DMA at 0x10c8-0x10cf, BIOS settings: hdc:DMA, hdd:pio
> May 27 18:17:39 bert kernel: hda: WDC AC26400R, ATA DISK drive
> May 27 18:17:39 bert kernel: hdb: Maxtor 6E030L0, ATA DISK drive
> May 27 18:17:39 bert kernel: Using anticipatory io scheduler
> May 27 18:17:39 bert kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> May 27 18:17:39 bert kernel: hdc: HL-DT-ST RW/DVD GCC-4480B, ATAPI CD/DVD-ROM drive
> May 27 18:17:39 bert kernel: ide1 at 0x170-0x177,0x376 on irq 15
> May 27 18:17:39 bert kernel: pnp: the driver 'ide' has been registered
> May 27 18:17:39 bert kernel: hda: max request size: 128KiB
> May 27 18:17:39 bert kernel: hda: 12594960 sectors (6448 MB) w/512KiB Cache, CHS=13328/15/63, UDMA(33)
> May 27 18:17:39 bert kernel: hda: cache flushes supported
> May 27 18:17:39 bert kernel:  hda: hda1 hda2 hda3
> May 27 18:17:39 bert kernel: hdb: max request size: 128KiB
> May 27 18:17:39 bert kernel: hdb: 60058656 sectors (30750 MB) w/2048KiB Cache, CHS=59582/16/63, UDMA(33)
> May 27 18:17:39 bert kernel: hdb: cache flushes supported
> May 27 18:17:39 bert kernel:  hdb: hdb1 hdb2 hdb3 hdb4 < hdb5 >
>  
> followed later by:
> 
> May 27 18:18:05 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> May 27 18:18:05 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> May 27 18:18:06 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> May 27 18:18:06 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> May 27 18:19:21 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> May 27 18:19:21 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> May 27 18:19:22 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> May 27 18:19:22 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> May 27 18:20:01 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> May 27 18:20:01 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> May 27 18:20:01 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> May 27 18:20:01 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> May 27 18:21:27 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> May 27 18:21:27 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> 
> 
> 
> 
> Hope this help,
> 
> Ed
> 
> On May 27, 2004 04:24 pm, Günther Persoons wrote:
> > Hey,
> > When i mount my reiser partitie with the option barrier=flush i get
> > following message and error:
> > My harddrive is a 2.5 inch Fujitsu 20GB IDE.
> > 
> > mount /dev/hda10 /tmp -o barrier=flush
> > mount: wrong fs type, bad option, bad superblock on /dev/hda10,
> >        or too many mounted file systems
> > Log:
> > ReiserFS: hda10: found reiserfs format "3.6" with standard journal
> > ReiserFS: hda10: using ordered data mode
> > reiserfs: using flush barriers
> > ReiserFS: hda10: journal params: device hda10, size 8192, journal first
> > block 18, max trans len 1024, max batch 900, max commit age 30, max
> > trans age 30
> > ReiserFS: hda10: checking transaction log (hda10)
> > hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > hda: drive_cmd: error=0x04 { DriveStatusError }
> > hda: barrier support doesn't work
> > ReiserFS: hda10: warning: journal-837: IO error during journal replay
> > ReiserFS: hda10: warning: Replay Failure, unable to mount
> > ReiserFS: hda10: warning: sh-2022: reiserfs_fill_super: unable to
> > initialize journal space
> 

  parent reply	other threads:[~2004-06-04  2:07 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 20:24 [2.6.7-rc1-mm1] cant mount reiserfs using -o barrier=flush Günther Persoons
2004-05-27 23:28 ` Ed Tomlinson
2004-05-28 11:54   ` Gunther Persoons
2004-05-28 12:18     ` Jens Axboe
2004-05-28 21:39       ` Ed Tomlinson
2004-05-29  8:30         ` Jens Axboe
2004-06-04  2:07   ` Ed Tomlinson [this message]
2004-06-04  2:31     ` ide errors in 7-rc1-mm1 and later Andrew Morton
2004-06-04  9:42       ` Jens Axboe
2004-06-04 11:22         ` Ed Tomlinson
2004-06-04 11:32           ` Jens Axboe
2004-06-04 11:45             ` Jens Axboe
2004-06-04 11:57             ` Bartlomiej Zolnierkiewicz
2004-06-04 12:01               ` Jens Axboe
2004-06-04 12:38                 ` Bartlomiej Zolnierkiewicz
2004-06-04 12:47                   ` Jens Axboe
2004-06-04 13:34                     ` Bartlomiej Zolnierkiewicz
2004-06-04 15:23                       ` Jens Axboe
2004-06-04 16:14                         ` Bartlomiej Zolnierkiewicz
2004-06-05  9:18                           ` Jens Axboe
2004-06-09 21:52                             ` Bartlomiej Zolnierkiewicz
2004-06-09 22:06                               ` Andrew Morton
2004-06-09 23:38                                 ` Bartlomiej Zolnierkiewicz
2004-06-09 23:50                                   ` Andrew Morton
2004-06-10  0:20                                     ` Bartlomiej Zolnierkiewicz
2004-06-10  0:37                                       ` Andrew Morton
2004-06-10  1:02                                         ` Bartlomiej Zolnierkiewicz
2004-06-10  0:28                                     ` Chris Mason
2004-06-10  0:38                                       ` Andrew Morton
2004-06-10  0:45                                         ` Bartlomiej Zolnierkiewicz
2004-06-10 15:14                                         ` Chris Mason
2004-06-10 15:15                                           ` Jens Axboe
2004-06-10  1:05                                       ` Bartlomiej Zolnierkiewicz
2004-06-10  6:27                                   ` Jens Axboe
2004-06-10  6:26                               ` Jens Axboe
2004-06-04 17:29                         ` Jeff Garzik
2004-06-05  9:24                           ` Jens Axboe
2004-06-06 16:18                             ` Eric D. Mudama
2004-06-06 20:46                               ` Jens Axboe
2004-06-10  0:38                               ` Bartlomiej Zolnierkiewicz
2004-06-10  6:11                                 ` Jens Axboe
2004-06-10 16:41                                   ` Eric D. Mudama
2004-06-10 17:50                                     ` flush cache range proposal (was Re: ide errors in 7-rc1-mm1 and later) Jeff Garzik
2004-06-10 18:02                                       ` Jeff Garzik
2004-06-10 20:33                                         ` Eric D. Mudama
2004-06-11 16:22                                           ` Jeff Garzik
2004-06-11  7:55                                         ` Jens Axboe
2004-06-11 16:17                                           ` Eric D. Mudama
2004-06-11 16:31                                             ` Jeff Garzik
2004-06-11 16:52                                               ` Eric D. Mudama
2004-06-11 16:58                                                 ` Jens Axboe
2004-06-11 16:54                                               ` Jens Axboe
2004-06-11 16:50                                             ` Jens Axboe
2004-06-11 16:24                                           ` Jeff Garzik
2004-06-11  6:10                                       ` Stuart Young
2004-06-26  8:31                                     ` ide errors in 7-rc1-mm1 and later Andre Hedrick
2004-06-26  8:58                                       ` Andre Hedrick
2004-06-28 18:18                                       ` Eric D. Mudama
2004-07-02  8:29                                         ` Jens Axboe
2004-07-07  5:40                                           ` Jeff Garzik
2004-06-04 11:48         ` Bartlomiej Zolnierkiewicz
2004-06-09 23:44     ` Ed Tomlinson
2004-06-09 23:52       ` Andrew Morton
2004-06-10  0:17         ` Ed Tomlinson
2004-06-10  6:29         ` Jens Axboe
2004-06-14 21:42       ` Ed Tomlinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200406032207.25602.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.