IDE Hard disk geometry problem in 2.4.19 / 2.4.20pre7

IDE Hard disk geometry problem in 2.4.19 / 2.4.20pre7

Post by James Finni » Sat, 21 Sep 2002 23:10:06



Hi,

I have a large number of IDE hard disks here where I work.  Since moving to
2.4.19 from 2.4.17, several of these disks have stopped working, resulting
in a kernel panic after the drive has declared itself to have 0 cylinders!
All the disks that have broken are the following:

Seagate 80GB U6 ST380020ACE with Firmware version 4.65

We have lots of these same drives, with FW v 3.34, that all work fine.  I do
not have a single drive with the 4.65 firmware working.  

My problem is that these drives used to work fine, with 2.4.17.  They are
not obsolete hardware, I think they are all less than 6 months old.

I have seen this on CS5530 with the standard kernel PCI IDE, and on SIS630
with the SIS Kernel IDE driver.  

Setting ide=nodma makes no difference.

Here is an excerpt from the kernel console booting:

....
hda: ST380020ACE, ATA DISK drive
....
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04  { DriveStatusError }
hda: setmax_ext LBA 1, native 0
hda: 0 sectors (0 MB) w/2048KiB Cache, CHS 0/255/63, (U)DMA
....
hda2: bad access: block=2, count=2
end_request: I/O error, dev 03:02 (hda), sector 2
EXT3-fs: unable to read superblock
hda2: bad access: block=2, count=2
end_request: I/O error, dev 03:02 (hda), sector 2
EXT3-fs: unable to read superblock
Kernel panic: VFS: Unable to mount root fs on 03:02

Is this a result of all the new IDE stuff that went in in 2.4.19???

Cheers for any help,

James Finnie
Imerge Ltd.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Imerge Limited                          Tel :- +44 (0)1954 783600
Unit 6 Bar Hill Business Park           Fax :- +44 (0)1954 783601
Saxon Way                               Web :- http://www.imerge.co.uk
Bar Hill
Cambridge
CB3 8SL
United Kingdom
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

IDE Hard disk geometry problem in 2.4.19 / 2.4.20pre7

Post by Jeff Garzi » Sat, 21 Sep 2002 23:30:08



> Hi,

> I have a large number of IDE hard disks here where I work.  Since moving to
> 2.4.19 from 2.4.17, several of these disks have stopped working, resulting
> in a kernel panic after the drive has declared itself to have 0 cylinders!
> All the disks that have broken are the following:

> Seagate 80GB U6 ST380020ACE with Firmware version 4.65

> We have lots of these same drives, with FW v 3.34, that all work fine.  I do
> not have a single drive with the 4.65 firmware working.  

> My problem is that these drives used to work fine, with 2.4.17.  They are
> not obsolete hardware, I think they are all less than 6 months old.

> I have seen this on CS5530 with the standard kernel PCI IDE, and on SIS630
> with the SIS Kernel IDE driver.  

> Setting ide=nodma makes no difference.

> Here is an excerpt from the kernel console booting:

> ....
> hda: ST380020ACE, ATA DISK drive
> ....
> hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: task_no_data_intr: error=0x04  { DriveStatusError }
> hda: setmax_ext LBA 1, native 0
> hda: 0 sectors (0 MB) w/2048KiB Cache, CHS 0/255/63, (U)DMA
> ....
> hda2: bad access: block=2, count=2
> end_request: I/O error, dev 03:02 (hda), sector 2
> EXT3-fs: unable to read superblock
> hda2: bad access: block=2, count=2
> end_request: I/O error, dev 03:02 (hda), sector 2
> EXT3-fs: unable to read superblock
> Kernel panic: VFS: Unable to mount root fs on 03:02

> Is this a result of all the new IDE stuff that went in in 2.4.19???

"All the new IDE stuff" hasn't really hit 2.4.x yet...

Do you have CONFIG_IDEDISK_STROKE set?  If yes, do things start working
if you disable it?

Can you post the other IDE options you have set in your kernel config?

        Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

IDE Hard disk geometry problem in 2.4.19 / 2.4.20pre7

Post by James Finni » Sun, 22 Sep 2002 00:00:08


> -----Original Message-----

> Sent: 20 September 2002 15:19
> To: James Finnie

> Subject: Re: IDE Hard disk geometry problem in 2.4.19 / 2.4.20pre7


> > Hi,

> > I have a large number of IDE hard disks here where I work.  
> Since moving to
> > 2.4.19 from 2.4.17, several of these disks have stopped
> working, resulting
> > in a kernel panic after the drive has declared itself to
> have 0 cylinders!
> > All the disks that have broken are the following:

> > Seagate 80GB U6 ST380020ACE with Firmware version 4.65

> > We have lots of these same drives, with FW v 3.34, that all
> work fine.  I do
> > not have a single drive with the 4.65 firmware working.  

> > My problem is that these drives used to work fine, with
> 2.4.17.  They are
> > not obsolete hardware, I think they are all less than 6 months old.

> > I have seen this on CS5530 with the standard kernel PCI
> IDE, and on SIS630
> > with the SIS Kernel IDE driver.  

> > Setting ide=nodma makes no difference.

> > Here is an excerpt from the kernel console booting:

> > ....
> > hda: ST380020ACE, ATA DISK drive
> > ....
> > hda: task_no_data_intr: status=0x51 { DriveReady
> SeekComplete Error }
> > hda: task_no_data_intr: error=0x04  { DriveStatusError }
> > hda: setmax_ext LBA 1, native 0
> > hda: 0 sectors (0 MB) w/2048KiB Cache, CHS 0/255/63, (U)DMA
> > ....
> > hda2: bad access: block=2, count=2
> > end_request: I/O error, dev 03:02 (hda), sector 2
> > EXT3-fs: unable to read superblock
> > hda2: bad access: block=2, count=2
> > end_request: I/O error, dev 03:02 (hda), sector 2
> > EXT3-fs: unable to read superblock
> > Kernel panic: VFS: Unable to mount root fs on 03:02

> > Is this a result of all the new IDE stuff that went in in 2.4.19???

> "All the new IDE stuff" hasn't really hit 2.4.x yet...

> Do you have CONFIG_IDEDISK_STROKE set?  If yes, do things
> start working
> if you disable it?

> Can you post the other IDE options you have set in your kernel config?

>    Jeff

Hi Jeff,

we do not have CONFIG_IDEDISK_STROKE set; I just tried setting it and get
the same result.

Here are the IDE bits that we are setting:

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set
# CONFIG_BLK_DEV_IDEDISK_IBM is not set
# CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set
# CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set
# CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set
# CONFIG_BLK_DEV_IDEDISK_WD is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
# CONFIG_BLK_DEV_TIVO is not set
# CONFIG_BLK_DEV_IDECS is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_IDEDMA_TIMEOUT is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_AEC62XX_TUNING is not set
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_AMD74XX_OVERRIDE is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CMD680 is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_PIIX_TUNING is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_PDC202XX=y
CONFIG_PDC202XX_BURST=y
# CONFIG_PDC202XX_FORCE is not set
# CONFIG_BLK_DEV_SVWKS is not set
CONFIG_BLK_DEV_SIS5513=y
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y
# CONFIG_BLK_DEV_ATARAID is not set
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Imerge Limited                          Tel :- +44 (0)1954 783600
Unit 6 Bar Hill Business Park           Fax :- +44 (0)1954 783601
Saxon Way                               Web :- http://www.imerge.co.uk
Bar Hill
Cambridge
CB3 8SL
United Kingdom
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. NFS/UDP/IP performance - 2.4.19 v/s 2.4.20, 2.4.20-pre3

Greetings.

There seem to be a remarkable performance difference
between 2.4.19 and 2.4.20/2.4.21-pre3 in regards to
NFS writes/reads. I am not sure, but the problem may not
in NFS but somewhere lower (UDP/IP or core).

For example, in my kernel and network configuration a
write to a new file over NFS on 2.4.19 for 5MB takes 2.5
seconds or so. With everything same (including kernel
configuration) 2.4.20 and 2.4.21-pre3 the same takes
11 or more seconds.

Also, when this file write is in progress, the system
time goes up to 15% on 2.4.19, whereas on 2.4.20/21-pre3,
it is about 4%. (I use sar/sysstat for this).

Memory accesses dont seem to be the issue either. Test
program to check this show same times and are ok (as I
expect on the board I use).

"netstat -s" or ifconfig or tcpdump traces dont seem to
point to dropped messages, collisions, retransmissions
etc.

The hardware configuration is PowerPC based, and there
are no changes in the board specific IO subsystem between
2.4.19 and 2.4.20/21-pre3. The same compiler is used for
building both the kernels, and have tried this even with
GCC 3.2, with same results.

So, I dont suspect this is either board or compiler
related issue.

Also, I see some differences in handling of the bottom
halves in net/core/dev.c between 2.4.19 and 2.4.20/21-pre3.
Although, I have not gone through these in details to
assert that this is indeed the problem area.

Questions:

  - Has anyone seen this? Perhaps on other platforms (x86 etc)?
    Is there some tunable that has been added (or is different)
    after 2.4.19, and which needs to be tuned?

  - I have tried to enable kernel profiling to find any
    potential problem code areas. But given the low cpu
    utilization during these copies, I am not sure if this
    can give any useful info.

    Could anyone offer any ideas to debug this?

I would appreciate if you copy me on any responses to this post, I
dont subscribe to this list.

Best regards,
-Arun.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Shared memory.

3. Process hangs in 2.4.19, RH7.latest, and 2.4.20-pre7-ac2

4. resolving problems

5. Oops in usb_submit_urb with US_FL_MODE_XLATE (2.4.19 and 2.4.20-pre7)

6. basic firewall/NAT setup

7. PROBLEM: ide-related kernel panic in 2.4.19 and 2.4.20-pre11

8. Restricted (or Captive) Account/Shell

9. IDE problem in 2.4.19 & 2.4.20 on Compaq Armada 1130T

10. Intel ICH4 ide not working for 2.4.19 and 2.4.20

11. 2.4.20-pre2-ac3 IDE better than 2.4.19-pre10

12. Hangs in 2.4.19 and 2.4.20-pre5 (IDE-related?)