Promise IDE controller crashes 2.4.22

Promise IDE controller crashes 2.4.22

[John Goerzen]

Hi,

I have a Promise 20269-based UDMA 133 IDE controller.  If I have DMA
enabled on this controller, then when it is seeing heavy write activity,
the system freezes.  No messages on the console, ctrl-alt-del does
nothing, magic sysrq does nothing.

Reads do not appear to cause this problem, and the problem also
disappears if I disable DMA on the drive connected to the controller by
using hdparm.

System information:
Linux pi 2.4.22 #3 Sat Oct 25 15:45:50 CDT 2003 i586 GNU/Linux
AMD K6 400MHz processor

lspci:
00:08.0 Unknown mass storage controller: Promise Technology, Inc. 20269
(rev 02)

Drive: Maxtor 6Y160P0 150GB UDMA 133

I have, in my .config:

CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_BLK_DEV_PDC202XX=y

Thanks for any insight.

-- John Goerzen

Re: Promise IDE controller crashes 2.4.22

[Bartlomiej Zolnierkiewicz]

[ linux-kernel@ replaced by linux-ide@ ]

Can you try setting drive to use UDMA100 instead of UDMA133
(by something like 'hdparm -Xudma100 /dev/hda')?

Also please send full dmesg and config.

--bart

On Thursday 27 of November 2003 19:43, John Goerzen wrote:
> Hi,
>
> I have a Promise 20269-based UDMA 133 IDE controller.  If I have DMA
> enabled on this controller, then when it is seeing heavy write activity,
> the system freezes.  No messages on the console, ctrl-alt-del does
> nothing, magic sysrq does nothing.
>
> Reads do not appear to cause this problem, and the problem also
> disappears if I disable DMA on the drive connected to the controller by
> using hdparm.
>
> System information:
> Linux pi 2.4.22 #3 Sat Oct 25 15:45:50 CDT 2003 i586 GNU/Linux
> AMD K6 400MHz processor
>
> lspci:
> 00:08.0 Unknown mass storage controller: Promise Technology, Inc. 20269
> (rev 02)
>
> Drive: Maxtor 6Y160P0 150GB UDMA 133
>
> I have, in my .config:
>
> CONFIG_BLK_DEV_PDC202XX_NEW=y
> CONFIG_BLK_DEV_PDC202XX=y
>
> Thanks for any insight.
>
> -- John Goerzen

Re: Promise IDE controller crashes 2.4.22

[John Goerzen]

[-- Attachment #1: Type: text/plain, Size: 406 bytes --]

On Thu, Nov 27, 2003 at 08:42:19PM +0100, Bartlomiej Zolnierkiewicz wrote:
> [ linux-kernel@ replaced by linux-ide@ ]

OK (please continue to CC me on replies)

> Can you try setting drive to use UDMA100 instead of UDMA133
> (by something like 'hdparm -Xudma100 /dev/hda')?

I will give it a whirl and see if I can repeat the problem and let you
know.

> Also please send full dmesg and config.

Attached.

[-- Attachment #2: config-2.4.22 --]
[-- Type: text/plain, Size: 16614 bytes --]

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
CONFIG_MK6=y
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_HAS_TSC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_MCE=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_HIGHMEM is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_UP_IOAPIC is not set
# CONFIG_X86_TSC_DISABLE is not set
CONFIG_X86_TSC=y

#
# General setup
#
CONFIG_NET=y
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_ISA=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
# CONFIG_HOTPLUG_PCI_COMPAQ is not set
# CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_PM is not set
# CONFIG_APM is not set

#
# ACPI Support
#
# CONFIG_ACPI is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_CISS_SCSI_TAPE is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
# CONFIG_BLK_STATS is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK_DEV=y
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_NAT=y
# CONFIG_IP_ROUTE_MULTIPATH is not set
# CONFIG_IP_ROUTE_TOS is not set
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set

#
#  
#
# CONFIG_IPX is not set
# CONFIG_ATALK is not set

#
# Appletalk devices
#
# CONFIG_DEV_APPLETALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set
# CONFIG_PHONE_IXJ_PCMCIA is not set

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

#
# IDE, ATA and ATAPI Block devices
#
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_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
# 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_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=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 is not set
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_ADMA100 is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_AMD74XX_OVERRIDE 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_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_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
# CONFIG_PDC202XX_FORCE is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_SC1200 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=y
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_PDC202XX=y
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
# CONFIG_BLK_DEV_ATARAID_SII is not set

#
# SCSI support
#
# CONFIG_SCSI is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_BOOT is not set
# CONFIG_FUSION_ISENSE is not set
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LAN is not set

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
CONFIG_BONDING=m
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_SUNLANCE is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
# CONFIG_EL3 is not set
# CONFIG_3C515 is not set
# CONFIG_ELMC is not set
# CONFIG_ELMC_II is not set
CONFIG_VORTEX=m
# CONFIG_TYPHOON is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_CS89x0 is not set
# CONFIG_TULIP is not set
# CONFIG_DE4X5 is not set
# CONFIG_DGRS is not set
# CONFIG_DM9102 is not set
# CONFIG_EEPRO100 is not set
# CONFIG_EEPRO100_PIO is not set
# CONFIG_E100 is not set
# CONFIG_LNE390 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_NE3210 is not set
# CONFIG_ES3210 is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_SUNDANCE_MMIO is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_RHINE_MMIO is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_MYRI_SBUS is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
# CONFIG_PPP_FILTER is not set
# CONFIG_PPP_ASYNC is not set
# CONFIG_PPP_SYNC_TTY is not set
# CONFIG_PPP_DEFLATE is not set
# CONFIG_PPP_BSDCOMP is not set
# CONFIG_PPPOE is not set
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
# CONFIG_SLIP_SMART is not set
# CONFIG_SLIP_MODE_SLIP6 is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Input core support
#
# CONFIG_INPUT is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_MOUSE is not set

#
# Joysticks
#
# CONFIG_INPUT_GAMEPORT is not set

#
# Input core support is needed for gameports
#

#
# Input core support is needed for joysticks
#
# CONFIG_QIC02_TAPE is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_IPMI_PANIC_EVENT is not set
# CONFIG_IPMI_DEVICE_INTERFACE is not set
# CONFIG_IPMI_KCS is not set
# CONFIG_IPMI_WATCHDOG is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_SCx200_GPIO is not set
# CONFIG_AMD_RNG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_AMD_PM768 is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_QFMT_V2 is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_REISERFS_FS is not set
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BEFS_DEBUG is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=m
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_JFFS2_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_JFS_FS is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_DIRECTIO is not set
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_TCP is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
# CONFIG_ZISOFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_SMB_NLS=y
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="cp437"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VIDEO_SELECT is not set
# CONFIG_MDA_CONSOLE is not set

#
# Frame-buffer support
#
# CONFIG_FB is not set

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set

#
# Bluetooth support
#
# CONFIG_BLUEZ is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_FRAME_POINTER is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
# CONFIG_CRC32 is not set
# CONFIG_ZLIB_INFLATE is not set
# CONFIG_ZLIB_DEFLATE is not set

[-- Attachment #3: dmesg --]
[-- Type: text/plain, Size: 5564 bytes --]

Linux version 2.4.22 (jgoerzen@heinrich) (gcc version 3.3.2 (Debian)) #3 Sat Oct 25 15:45:50 CDT 2003
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000018000000 (usable)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
384MB LOWMEM available.
On node 0 totalpages: 98304
zone(0): 4096 pages.
zone(1): 94208 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hdc1 ro rootfstype=ext3
Initializing CPU#0
Detected 400.919 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 799.53 BogoMIPS
Memory: 386700k/393216k available (1137k kernel code, 6132k reserved, 465k data, 76k 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: 32K (32 bytes/line), D cache 32K (32 bytes/line)
CPU: L2 Cache: 256K (32 bytes/line)
CPU:     After generic, caps: 008021bf 808029bf 00000000 00000002
CPU:             Common caps: 008021bf 808029bf 00000000 00000002
CPU: AMD-K6(tm) 3D+ Processor stepping 01
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: AMD K6
PCI: PCI BIOS revision 2.10 entry at 0xfb420, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router VIA [1106/0596] at 00:07.0
Activating ISA DMA hang workarounds.
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
Starting kswapd
Journalled Block Device driver loaded
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 00:07.1
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 vt82c596b (rev 12) IDE UDMA66 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:DMA, hdd:DMA
PDC20269: IDE controller at PCI slot 00:08.0
PCI: Found IRQ 11 for device 00:08.0
PDC20269: chipset revision 2
PDC20269: not 100% native mode: will probe irqs later
PDC20269: ROM enabled at 0xe4000000
    ide2: BM-DMA at 0xe800-0xe807, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xe808-0xe80f, BIOS settings: hdg:pio, hdh:pio
hda: FUJITSU MPE3084AE, ATA DISK drive
hdc: IBM-DTLA-305040, ATA DISK drive
hde: Maxtor 6Y160P0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xd800-0xd807,0xdc02 on irq 11
hda: attached ide-disk driver.
hda: 16514064 sectors (8455 MB) w/512KiB Cache, CHS=1027/255/63
hdc: attached ide-disk driver.
hdc: host protected area => 1
hdc: 80418240 sectors (41174 MB) w/380KiB Cache, CHS=79780/16/63
hde: attached ide-disk driver.
hde: host protected area => 1
hde: 320173056 sectors (163929 MB) w/7936KiB Cache, CHS=19929/255/63
Partition check:
 hda: hda1 hda2 < hda5 hda6 >
 hdc: [PTBL] [5005/255/63] hdc1
 hde: hde1
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 76k freed
Adding Swap: 248968k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,1), internal journal
PCI: Found IRQ 12 for device 00:0a.0
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
See Documentation/networking/vortex.txt
00:0a.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xec00. Vers LK1.1.18-ac
 00:01:02:43:b1:69, IRQ 12
  product code 4347 rev 00.12 date 03-28-00
  Internal config register is 1800000, transceivers 0xa.
  8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
  MII transceiver found at address 24, status 786d.
  Enabling bus-master transmits and whole-frame receives.
00:0a.0: scatter/gather enabled. h/w checksums enabled
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide2(33,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
blk: queue c02cc320, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c02cc774, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c02ccbc8, I/O limit 4095Mb (mask 0xffffffff)
hde: DMA disabled

Re: Promise IDE controller crashes 2.4.22

[Bartlomiej Zolnierkiewicz]

Can you first try booting with "ide2=autodma" kernel parameter
instead of downgrading to UDMA100?

--bart

On Thursday 27 of November 2003 23:55, John Goerzen wrote:
> On Thu, Nov 27, 2003 at 08:42:19PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > [ linux-kernel@ replaced by linux-ide@ ]
>
> OK (please continue to CC me on replies)
>
> > Can you try setting drive to use UDMA100 instead of UDMA133
> > (by something like 'hdparm -Xudma100 /dev/hda')?
>
> I will give it a whirl and see if I can repeat the problem and let you
> know.
>
> > Also please send full dmesg and config.
>
> Attached.

Re: Promise IDE controller crashes 2.4.22

[John Goerzen]

On Fri, Nov 28, 2003 at 12:16:48AM +0100, Bartlomiej Zolnierkiewicz wrote:
> 
> Can you first try booting with "ide2=autodma" kernel parameter
> instead of downgrading to UDMA100?

This caused the system to boot up with DMA disabled for the relevant
drive.  (Note: that may also be how it was working before.)  Here is a
diff from the previous dmesg to this one:

--- dmesg       2003-11-27 17:51:54.000000000 -0500
+++ dmesg2      2003-11-27 21:04:14.000000000 -0500
@@ -9,9 +9,10 @@
 zone(0): 4096 pages.
 zone(1): 94208 pages.
 zone(2): 0 pages.
-Kernel command line: root=/dev/hdc1 ro rootfstype=ext3
+Kernel command line: root=/dev/hdc1 ro rootfstype=ext3 ide2=autodma
+ide_setup: ide2=autodma -- BAD OPTION
 Initializing CPU#0
-Detected 400.919 MHz processor.
+Detected 400.923 MHz processor.
 Console: colour VGA+ 80x25
 Calibrating delay loop... 799.53 BogoMIPS
 Memory: 386700k/393216k available (1137k kernel code, 6132k reserved,
465k data, 76k init, 0k highmem)
@@ -55,7 +56,6 @@
 VP_IDE: IDE controller at PCI slot 00:07.1
 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 vt82c596b (rev 12) IDE UDMA66 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:DMA, hdd:DMA
@@ -113,7 +113,3 @@
 EXT3 FS 2.4-0.9.19, 19 August 2002 on ide2(33,1), internal journal
 EXT3-fs: mounted filesystem with ordered data mode.
 Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
-blk: queue c02cc320, I/O limit 4095Mb (mask 0xffffffff)
-blk: queue c02cc774, I/O limit 4095Mb (mask 0xffffffff)
-blk: queue c02ccbc8, I/O limit 4095Mb (mask 0xffffffff)
-hde: DMA disabled

Also, here's some hdparm info:

# hdparm -i /dev/hde

/dev/hde:

 Model=Maxtor 6Y160P0, FwRev=YAR41VW0, SerialNo=xxxxxxxx
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
 BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
 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):  1 2 3 4 5 6 7

Re: Promise IDE controller crashes 2.4.22

[John Goerzen]

On Fri, Nov 28, 2003 at 12:16:48AM +0100, Bartlomiej Zolnierkiewicz wrote:
> > > Can you try setting drive to use UDMA100 instead of UDMA133
> > > (by something like 'hdparm -Xudma100 /dev/hda')?

Tried that too, but I got: 

pi:~# hdparm -Xudma100 /dev/hde
-X: missing value

Re: Promise IDE controller crashes 2.4.22

[Stefan Smietanowski]

Hi John.

>>>>Can you try setting drive to use UDMA100 instead of UDMA133
>>>>(by something like 'hdparm -Xudma100 /dev/hda')?
> 
> 
> Tried that too, but I got: 
> 
> pi:~# hdparm -Xudma100 /dev/hde
> -X: missing value

Try -X69 (69 means udma100)

Formula is simple. UDMA mode you want + 64, ie UDMA5 = 5+64.

// Stefan

Re: Promise IDE controller crashes 2.4.22

[Bartlomiej Zolnierkiewicz]

My mistake, it should have been -Xudma5 :-).

On Friday 28 of November 2003 04:22, Stefan Smietanowski wrote:
> Hi John.
>
> >>>>Can you try setting drive to use UDMA100 instead of UDMA133
> >>>>(by something like 'hdparm -Xudma100 /dev/hda')?
> >
> > Tried that too, but I got:
> >
> > pi:~# hdparm -Xudma100 /dev/hde
> > -X: missing value
>
> Try -X69 (69 means udma100)
>
> Formula is simple. UDMA mode you want + 64, ie UDMA5 = 5+64.
>
> // Stefan

Re: Promise IDE controller crashes 2.4.22

[Bartlomiej Zolnierkiewicz]

Sorry, it should have been "ide2=dma"...

On Friday 28 of November 2003 03:12, John Goerzen wrote:
> On Fri, Nov 28, 2003 at 12:16:48AM +0100, Bartlomiej Zolnierkiewicz wrote:
> > Can you first try booting with "ide2=autodma" kernel parameter
> > instead of downgrading to UDMA100?
>
> This caused the system to boot up with DMA disabled for the relevant
> drive.  (Note: that may also be how it was working before.)  Here is a
> diff from the previous dmesg to this one:
>
> --- dmesg       2003-11-27 17:51:54.000000000 -0500
> +++ dmesg2      2003-11-27 21:04:14.000000000 -0500
> @@ -9,9 +9,10 @@
>  zone(0): 4096 pages.
>  zone(1): 94208 pages.
>  zone(2): 0 pages.
> -Kernel command line: root=/dev/hdc1 ro rootfstype=ext3
> +Kernel command line: root=/dev/hdc1 ro rootfstype=ext3 ide2=autodma
> +ide_setup: ide2=autodma -- BAD OPTION
>  Initializing CPU#0
> -Detected 400.919 MHz processor.
> +Detected 400.923 MHz processor.
>  Console: colour VGA+ 80x25
>  Calibrating delay loop... 799.53 BogoMIPS
>  Memory: 386700k/393216k available (1137k kernel code, 6132k reserved,
> 465k data, 76k init, 0k highmem)
> @@ -55,7 +56,6 @@
>  VP_IDE: IDE controller at PCI slot 00:07.1
>  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 vt82c596b (rev 12) IDE UDMA66 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:DMA, hdd:DMA
> @@ -113,7 +113,3 @@
>  EXT3 FS 2.4-0.9.19, 19 August 2002 on ide2(33,1), internal journal
>  EXT3-fs: mounted filesystem with ordered data mode.
>  Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> -blk: queue c02cc320, I/O limit 4095Mb (mask 0xffffffff)
> -blk: queue c02cc774, I/O limit 4095Mb (mask 0xffffffff)
> -blk: queue c02ccbc8, I/O limit 4095Mb (mask 0xffffffff)
> -hde: DMA disabled
>
> Also, here's some hdparm info:
>
> # hdparm -i /dev/hde
>
> /dev/hde:
>
>  Model=Maxtor 6Y160P0, FwRev=YAR41VW0, SerialNo=xxxxxxxx
>  Config={ Fixed }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
>  BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=16
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
>  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):  1 2 3 4 5 6 7

Re: Promise IDE controller crashes 2.4.22

[Wes Janzen]

Hi,

I'd suspect some sort of PCI problem, especially since you're running a 
K6.  What chipset is your motherboard based on?

I'm running a K6-2 400 on an FIC PA2013 with two PDC20269 controllers 
and my primary drive is a 6Y060L0.  I've had no problem with writes in 
DMA mode locking the system in 2.4.22 or any of the test kernels.  I 
have a 92048D8 that doesn't like UDMA-2 writes, but that won't hang the 
system; it just causes Linux to continually reset the interface until 
the kernel finally disables DMA on the drive.  Oddly, UDMA-1 works fine 
but this is a drive to controller hardware issue and not the drivers 
fault. 

Anyway, since the kernel seems to handle a DMA write gone bad, that 
leads me to believe that this issue is caused by the increased data 
flowing over the PCI bus when using DMA vs using PIO.  I'm not an expert 
though, maybe someone else has an opinion on this?

You might try putting the card in another slot too.  My cards are 
installed in slots 1 & 2 with 2 other PCI cards and an ISA device.  This 
particular motherboard seems to handle a full complement of expansion 
cards without problem, but I remember hearing nightmares about such a 
configuration back when these things were new.

-Wes-

John Goerzen wrote:

>Hi,
>
>I have a Promise 20269-based UDMA 133 IDE controller.  If I have DMA
>enabled on this controller, then when it is seeing heavy write activity,
>the system freezes.  No messages on the console, ctrl-alt-del does
>nothing, magic sysrq does nothing.
>
>Reads do not appear to cause this problem, and the problem also
>disappears if I disable DMA on the drive connected to the controller by
>using hdparm.
>
>System information:
>Linux pi 2.4.22 #3 Sat Oct 25 15:45:50 CDT 2003 i586 GNU/Linux
>AMD K6 400MHz processor
>
>lspci:
>00:08.0 Unknown mass storage controller: Promise Technology, Inc. 20269
>(rev 02)
>
>Drive: Maxtor 6Y160P0 150GB UDMA 133
>
>I have, in my .config:
>
>CONFIG_BLK_DEV_PDC202XX_NEW=y
>CONFIG_BLK_DEV_PDC202XX=y
>
>Thanks for any insight.
>
>-- John Goerzen
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>

Re: Promise IDE controller crashes 2.4.22

[John Goerzen]

On Fri, Nov 28, 2003 at 02:01:32PM +0100, Bartlomiej Zolnierkiewicz wrote:
> 
> Sorry, it should have been "ide2=dma"...

That doesn't seem to have made much of a difference.  hdparm /dev/hde
still reports DMA being off by default.  Here's the complete dmesg
again:


Linux version 2.4.22 (jgoerzen@heinrich) (gcc version 3.3.2 (Debian)) #3 Sat Oct 25 15:45:50 CDT 2003
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000018000000 (usable)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
384MB LOWMEM available.
On node 0 totalpages: 98304
zone(0): 4096 pages.
zone(1): 94208 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hdc1 ro rootfstype=ext3 ide2=dma
ide_setup: ide2=dma
Initializing CPU#0
Detected 400.919 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 799.53 BogoMIPS
Memory: 386700k/393216k available (1137k kernel code, 6132k reserved, 465k data, 76k 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: 32K (32 bytes/line), D cache 32K (32 bytes/line)
CPU: L2 Cache: 256K (32 bytes/line)
CPU:     After generic, caps: 008021bf 808029bf 00000000 00000002
CPU:             Common caps: 008021bf 808029bf 00000000 00000002
CPU: AMD-K6(tm) 3D+ Processor stepping 01
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: AMD K6
PCI: PCI BIOS revision 2.10 entry at 0xfb420, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router VIA [1106/0596] at 00:07.0
Activating ISA DMA hang workarounds.
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
Starting kswapd
Journalled Block Device driver loaded
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c596b (rev 12) IDE UDMA66 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:DMA, hdd:DMA
PDC20269: IDE controller at PCI slot 00:08.0
PCI: Found IRQ 11 for device 00:08.0
PDC20269: chipset revision 2
PDC20269: not 100% native mode: will probe irqs later
PDC20269: ROM enabled at 0xe4000000
    ide2: BM-DMA at 0xe800-0xe807, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xe808-0xe80f, BIOS settings: hdg:pio, hdh:pio
hda: FUJITSU MPE3084AE, ATA DISK drive
hdc: IBM-DTLA-305040, ATA DISK drive
hde: Maxtor 6Y160P0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xd800-0xd807,0xdc02 on irq 11
hda: attached ide-disk driver.
hda: 16514064 sectors (8455 MB) w/512KiB Cache, CHS=1027/255/63
hdc: attached ide-disk driver.
hdc: host protected area => 1
hdc: 80418240 sectors (41174 MB) w/380KiB Cache, CHS=79780/16/63
hde: attached ide-disk driver.
hde: host protected area => 1
hde: 320173056 sectors (163929 MB) w/7936KiB Cache, CHS=19929/255/63
Partition check:
 hda: hda1 hda2 < hda5 hda6 >
 hdc: [PTBL] [5005/255/63] hdc1
 hde: hde1
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 76k freed
Adding Swap: 248968k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,1), internal journal
PCI: Found IRQ 12 for device 00:0a.0
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
See Documentation/networking/vortex.txt
00:0a.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xec00. Vers LK1.1.18-ac
 00:01:02:43:b1:69, IRQ 12
  product code 4347 rev 00.12 date 03-28-00
  Internal config register is 1800000, transceivers 0xa.
  8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
  MII transceiver found at address 24, status 786d.
  Enabling bus-master transmits and whole-frame receives.
00:0a.0: scatter/gather enabled. h/w checksums enabled
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide2(33,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).

Re: Promise IDE controller crashes 2.4.22

[John Goerzen]

On Fri, Nov 28, 2003 at 01:36:57PM -0600, Wes Janzen wrote:
> I'd suspect some sort of PCI problem, especially since you're running a 

Do you happen to have a URL where I can read up on PCI problems with
K6s?  Are the problems unique to Linux?  Note that it's a K6-3, so it's
not really first generation PCI.

> K6.  What chipset is your motherboard based on?

I haven't looked at the motherboard in quite awhile...  it's got a lot
of VIA hardware: the PCI bridge is a VT82C598/694x (Apollo MVP3/Pro133x
AGP).  I also see VT82C596 and VT82C586 in the lspci output.  The box
was used as a server for a couple of years with no obvious hardware
problems.

The motherboard was, if memory serves, manufactured by Epox.  But it's
been ages since I've looked at that, so my memory may be failing.  If it
would help with the diagnosis, though, I could go open it up and find
out.

> have a 92048D8 that doesn't like UDMA-2 writes, but that won't hang the 

Can you translate UDMA-2 into something like UDMA/133?  I'm having
trouble mapping the two in my head (I'm not terribly familiar with IDE
internals)

> Anyway, since the kernel seems to handle a DMA write gone bad, that 
> leads me to believe that this issue is caused by the increased data 
> flowing over the PCI bus when using DMA vs using PIO.  I'm not an expert 
> though, maybe someone else has an opinion on this?

The other thing is that the drives hooked to the on-board IDE channels
work fine.  I don't know if that is important; but I figured I'd mention
it.

> You might try putting the card in another slot too.  My cards are 

Hmm, I could give that a try.

Thanks,
John

Re: Promise IDE controller crashes 2.4.22

[John Goerzen]

On Fri, Nov 28, 2003 at 02:00:55PM +0100, Bartlomiej Zolnierkiewicz wrote:
> 
> My mistake, it should have been -Xudma5 :-).

I tried the ide2=dma in the kernel and then:

hdparm -d 1 -u 1 -X 69 /dev/hde

That did seem to solve the problem.  Output of hdparm after that
command:

pi:~# hdparm /dev/hde

/dev/hde:
 multcount    = 16 (on)
 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    =  8 (on)
 geometry     = 19929/255/63, sectors = 320173056, start = 0

What does that mean?

Re: Promise IDE controller crashes 2.4.22

[Andrew Herdman]

to determine the UDMA mode the drive is currently operating in perform a
hdparm -i /dev/hde

an example from my system, Promise TX133 Card

hdparm -i /dev/hde

/dev/hde:

 Model=WDC WD800JB-00DUA3, FwRev=75.13B75, SerialNo=WD-WMACM1696962
 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
 RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=74
 BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=156301488
 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
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: device does not report version:

 * signifies the current active mode

As you can see, my drive is currently operating using udam4 (i turned off
udma5 on the drives themselves because of dma errors, bad cabling).

Andrew

----- Original Message ----- 
From: "John Goerzen" <jgoerzen@complete.org>
To: "Bartlomiej Zolnierkiewicz" <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: "Stefan Smietanowski" <stesmi@stesmi.com>; <linux-ide@vger.kernel.org>
Sent: Friday, November 28, 2003 8:52 PM
Subject: Re: Promise IDE controller crashes 2.4.22


> On Fri, Nov 28, 2003 at 02:00:55PM +0100, Bartlomiej Zolnierkiewicz wrote:
> >
> > My mistake, it should have been -Xudma5 :-).
>
> I tried the ide2=dma in the kernel and then:
>
> hdparm -d 1 -u 1 -X 69 /dev/hde
>
> That did seem to solve the problem.  Output of hdparm after that
> command:
>
> pi:~# hdparm /dev/hde
>
> /dev/hde:
>  multcount    = 16 (on)
>  IO_support   =  0 (default 16-bit)
>  unmaskirq    =  0 (off)
>  using_dma    =  1 (on)
>  keepsettings =  0 (off)
>  readonly     =  0 (off)
>  readahead    =  8 (on)
>  geometry     = 19929/255/63, sectors = 320173056, start = 0
>
> What does that mean?
>
>
> -
> 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
>

Re: Promise IDE controller crashes 2.4.22

[Wes Janzen]

John Goerzen wrote:

>On Fri, Nov 28, 2003 at 01:36:57PM -0600, Wes Janzen wrote:
>  
>
>>I'd suspect some sort of PCI problem, especially since you're running a 
>>    
>>
>
>Do you happen to have a URL where I can read up on PCI problems with
>K6s?
>
Well, I know of the assorted problems with the KT133 & newer from VIA 
and SoundBlaster Live sound cards.  I think changing the latency greatly 
reduced the problems but didn't eradicate it completely, IIRC.  You can 
search on Google for "via soundblaster live" to get some more information.

I know when I posted to the list due to problems with the onboard IDE on 
my board, several people responded that they had problems with their VIA 
boards randomly corrupting data during PCI busmaster transfers.  That 
problem doesn't seem to afflict my board.  Most of those were on newer 
boards (KT/KX133) but some involved the MVP3 which both of us are 
running.  I compared notes with someone with the same motherboard 
revision who didn't have the problems I have, so perhaps some silicon or 
boards were defective in a way that was never detected by VIA or the 
board manufacturer respectively. 

Anyway, if VIA had problems with the later chipset I wouldn't be at all 
surprised if an older version suffered from similar defects.

>  Are the problems unique to Linux? 
>
These problems are not unique to Linux.  Windows configures PCI devices 
differently though and that could have an effect.

> Note that it's a K6-3, so it's
>not really first generation PCI.
>  
>
Well, it was a first-generation chipset in many regards ;-)  Seriously 
though, especially back then VIA was several notches below Intel when it 
came to product quality.  The K6 in any form was a bargain chip and the 
chipsets for it were targetting that market; I doubt they went through 
any qualification program remotely resembling those of Intel.  In other 
words, it may not be first generation for VIA but it wasn't top quality 
either.

I'm not bashing VIA, that's just the reality of it.  My system was flaky 
until I replaced the onboard IDE with the Promise cards.  It became 
solid when I replaced the 3dfx Banshee with an ATI 9000 Pro.  Still I 
don't expect to get the kind of performance out of the cards as I would 
if they were in a comparable PII system.  For example, I seriously doubt 
the 3COM diagnostics complain about PCI bus performance on an Intel system.

> ...
>
>Can you translate UDMA-2 into something like UDMA/133?  I'm having
>trouble mapping the two in my head (I'm not terribly familiar with IDE
>internals)
>
>  
>
UDMA-2 = UDMA/33

It's not really important, I'm just pointing out that if the drive 
stopped responding due to a communication problem between the drive and 
card, the drive would be reset and the system would become responsive 
even if it paused for several seconds.

I should also clarify that the drive communicated fine with the VIA IDE 
in UDMA-2, just not with the Promise controllers.  I have to back the 
drive down to UDMA-1 before writing data or it will reset and fallback 
to PIO.

> ...
>
>The other thing is that the drives hooked to the on-board IDE channels
>work fine.  I don't know if that is important; but I figured I'd mention
>it.
>
>  
>
It may not stress the PCI bus as much, it was designed specifically for 
the chipset, and it's attached to the PCI bus in a significantly 
different manner.  It's just that the fact that using PIO transfers 
implies a large reduction in the PCI bandwidth utilized by the card.  
That and my experience with card to drive communication failure only 
leaves some other cause.  Depending on the type of transfer, it's likely 
that the PCI bus is being completely saturated when bursting write data 
to the drive's cache or even a sustained write.  So going from a high 
PCI load to a lower PCI load solves the problem.

It's possible that the driver is doing something wrong, but I'm using a 
similar hardware configuration and not experiencing the problem.  Many 
more people are using the driver and card with a different board, also 
apparently without problems.  So, add the history of VIA and PCI 
problems and a PCI communication failure looks like a prime candidate.  
You'd be wise to run an extensive memory test though to eliminate that 
cause.  Other possible suspects would be the power supply or a hot cpu.

>>You might try putting the card in another slot too.  My cards are 
>>    
>>
>
>Hmm, I could give that a try.
>  
>
Could be a BIOS setting causing the problem too, but I don't know enough 
about the PCI bus to know which settings you'd want to adjust ;-)  If it 
was me, I'd try the PCI settings first though since my machine is so 
full of cards and cables.

Perhaps someone else can speak up and let us know if another misbehaving 
PCI device could be causing this problem?  For example when the drive is 
hogging the bus during a DMA transfer maybe another card could interrupt 
it and lock up the PCI bus; is it possible and if so, likely?  Maybe 
it's not the bandwidth but a long transfer that's the problem...?  I'd 
rather not try to dig up the PCI specs to answer this question (mainly 
because I don't have the time).

Good luck,
Wes

>Thanks,
>John
>  
>

Re: Promise IDE controller crashes 2.4.22

[Bartlomiej Zolnierkiewicz]

It means two things:

(a) There is a bug in drivers/ide/pci/pdc202xx_new.c:init_hwif_pdc202new(),
    hwif->autodma shouldn't be set to 0 or "idex=dma" parameter won't work.

(b) If you don't use autodma you have to tune desired mode _explicitly_ first,
    because most of ->ide_dma_check() implementations (for pdc202xx_new.c
    it is pdcnew_config_drive_xfer_rate()) check for hwif->autodma.

--bart

On Saturday 29 of November 2003 02:52, John Goerzen wrote:
> On Fri, Nov 28, 2003 at 02:00:55PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > My mistake, it should have been -Xudma5 :-).
>
> I tried the ide2=dma in the kernel and then:
>
> hdparm -d 1 -u 1 -X 69 /dev/hde
>
> That did seem to solve the problem.  Output of hdparm after that
> command:
>
> pi:~# hdparm /dev/hde
>
> /dev/hde:
>  multcount    = 16 (on)
>  IO_support   =  0 (default 16-bit)
>  unmaskirq    =  0 (off)
>  using_dma    =  1 (on)
>  keepsettings =  0 (off)
>  readonly     =  0 (off)
>  readahead    =  8 (on)
>  geometry     = 19929/255/63, sectors = 320173056, start = 0
>
> What does that mean?

Re: Promise IDE controller crashes 2.4.22

[beolach]

I recently had a very similar problem to this on my computer with a
Promise Ultra133TX2 (PDC20269) addon card.  In my case I had a Western
Digital drive attached to the PDC20269 that would have major filesystem
corruption when DMA was enabled during the boot process.  Interestingly,
if I disabled DMA during boot, and then enabled it after boot with
hdparm, the drive worked OK.  Also, if I moved the drive to my
mainboard's IDE controller, it would work.  It seemed to be a
combination of my drive & IDE controller, because the IDE controller
works fine with other drives, and the WD hard drive worked fine with
another IDE controller.  I replaced the drive (20 GB) with a 120 GB
Maxtor drive, and haven't had any problem since.

Just something similar that happened to me,
Conway S. Smith


-- John Goerzen <jgoerzen@complete.org> wrote:
On Fri, Nov 28, 2003 at 12:16:48AM +0100, Bartlomiej Zolnierkiewicz wrote:
> 
> Can you first try booting with "ide2=autodma" kernel parameter
> instead of downgrading to UDMA100?

This caused the system to boot up with DMA disabled for the relevant
drive.  (Note: that may also be how it was working before.)  Here is a
diff from the previous dmesg to this one:

--- dmesg       2003-11-27 17:51:54.000000000 -0500
+++ dmesg2      2003-11-27 21:04:14.000000000 -0500
@@ -9,9 +9,10 @@
 zone(0): 4096 pages.
 zone(1): 94208 pages.
 zone(2): 0 pages.
-Kernel command line: root=/dev/hdc1 ro rootfstype=ext3
+Kernel command line: root=/dev/hdc1 ro rootfstype=ext3 ide2=autodma
+ide_setup: ide2=autodma -- BAD OPTION
 Initializing CPU#0
-Detected 400.919 MHz processor.
+Detected 400.923 MHz processor.
 Console: colour VGA+ 80x25
 Calibrating delay loop... 799.53 BogoMIPS
 Memory: 386700k/393216k available (1137k kernel code, 6132k reserved,
465k data, 76k init, 0k highmem)
@@ -55,7 +56,6 @@
 VP_IDE: IDE controller at PCI slot 00:07.1
 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 vt82c596b (rev 12) IDE UDMA66 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:DMA, hdd:DMA
@@ -113,7 +113,3 @@
 EXT3 FS 2.4-0.9.19, 19 August 2002 on ide2(33,1), internal journal
 EXT3-fs: mounted filesystem with ordered data mode.
 Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
-blk: queue c02cc320, I/O limit 4095Mb (mask 0xffffffff)
-blk: queue c02cc774, I/O limit 4095Mb (mask 0xffffffff)
-blk: queue c02ccbc8, I/O limit 4095Mb (mask 0xffffffff)
-hde: DMA disabled

Also, here's some hdparm info:

# hdparm -i /dev/hde

/dev/hde:

 Model=Maxtor 6Y160P0, FwRev=YAR41VW0, SerialNo=xxxxxxxx
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
 BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
 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):  1 2 3 4 5 6 7




________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!

Re: Promise IDE controller crashes 2.4.22

[Benjamin Herrenschmidt]

On Sun, 2003-11-30 at 09:07, beolach@juno.com wrote:
> I recently had a very similar problem to this on my computer with a
> Promise Ultra133TX2 (PDC20269) addon card.  In my case I had a Western
> Digital drive attached to the PDC20269 that would have major filesystem
> corruption when DMA was enabled during the boot process.  Interestingly,
> if I disabled DMA during boot, and then enabled it after boot with
> hdparm, the drive worked OK.  Also, if I moved the drive to my
> mainboard's IDE controller, it would work.  It seemed to be a
> combination of my drive & IDE controller, because the IDE controller
> works fine with other drives, and the WD hard drive worked fine with
> another IDE controller.  I replaced the drive (20 GB) with a 120 GB
> Maxtor drive, and haven't had any problem since.

Did you have something on the "other" channel ?

Andre seems to imply that the Promise chip may trigger interesting
bugs if you do things like SET_FEATURE on one channel while another
is doing DMA, kind of things that may well happen during boot

Ben.