* ide taskfile and cdrom hang
@ 2004-01-30 22:36 Mark Haverkamp
2004-02-01 20:48 ` Bartlomiej Zolnierkiewicz
0 siblings, 1 reply; 13+ messages in thread
From: Mark Haverkamp @ 2004-01-30 22:36 UTC (permalink / raw)
To: linux-kernel; +Cc: Cliff White
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
We have some test machines here at OSDL that have a problem with the ide
cdrom driver hanging when we cat the /proc/ide/hda/identify file. After
30 seconds the console displays: "hda: lost interrupt" which reoccurs
every 30 seconds forever. We noticed it on 2.6.2-rc2-mm1 but It looks
like this has been a problem for a while. Our test machines just changed
their configuration to use make defconfig. I found that if
CONFIG_IDE_TASKFILE_IO is N then the hang doesn't occur. Is this a
common problem or are there just certain drives that won't work with
taskfile i/o enabled? I've included my .config, lspci as attachments.
The cdrom model is CD-224E.
--
Mark Haverkamp <markh@osdl.org>
[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 20804 bytes --]
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
# CONFIG_STANDALONE is not set
#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
#
# Processor support
#
#
# Select all processors your kernel should support
#
# CONFIG_CPU_386 is not set
CONFIG_CPU_486=y
CONFIG_CPU_586=y
CONFIG_CPU_586TSC=y
CONFIG_CPU_586MMX=y
CONFIG_CPU_686=y
CONFIG_CPU_PENTIUMII=y
CONFIG_CPU_PENTIUMIII=y
CONFIG_CPU_PENTIUMM=y
CONFIG_CPU_PENTIUM4=y
CONFIG_CPU_K6=y
CONFIG_CPU_K7=y
CONFIG_CPU_K8=y
CONFIG_CPU_CRUSOE=y
CONFIG_CPU_WINCHIPC6=y
CONFIG_CPU_WINCHIP2=y
CONFIG_CPU_WINCHIP3D=y
CONFIG_CPU_CYRIXIII=y
CONFIG_CPU_VIAC3_2=y
CONFIG_CPU_INTEL=y
CONFIG_CPU_WINCHIP=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_F00F_BUG=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_BAD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set
# CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC is not set
CONFIG_SMP=y
CONFIG_NR_CPUS=8
# CONFIG_SCHED_SMT is not set
CONFIG_PREEMPT=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
CONFIG_X86_MCE_P4THERMAL=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_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BOOT=y
#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
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_PCI_USE_VECTOR is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_PCMCIA_PROBE=y
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
#
# Device Drivers
#
#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set
#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
# CONFIG_ISAPNP is not set
# CONFIG_PNPBIOS is not set
#
# 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_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_LBD=y
#
# ATA/ATAPI/MFM/RLL support
#
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=y
# 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
CONFIG_IDE_TASKFILE_IO=y
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_RZ1000=y
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_IDEDMA_PCI_WIP 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_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_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_MAX_SD_DISKS=256
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_REPORT_LUNS is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
CONFIG_SCSI_AACRAID=m
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
CONFIG_SCSI_MEGARAID=y
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
CONFIG_SCSI_QLOGIC_FC=y
CONFIG_SCSI_QLOGIC_FC_FIRMWARE=y
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX_CONFIG=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA23XX is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_DM=y
CONFIG_DM_IOCTL_V4=y
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=y
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
#
# Device Drivers
#
#
# Texas Instruments PCILynx requires I2C
#
CONFIG_IEEE1394_OHCI1394=y
#
# Protocol Drivers
#
# CONFIG_IEEE1394_VIDEO1394 is not set
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
# CONFIG_IEEE1394_RAWIO is not set
# CONFIG_IEEE1394_CMP is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Macintosh device drivers
#
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# 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 is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB 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
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP 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_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
CONFIG_E100=y
# CONFIG_E100_NAPI is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=y
# 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_8139_RXBUF_IDX=2
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE 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_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP 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
# CONFIG_NETCONSOLE 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
#
# Bluetooth support
#
# CONFIG_BT is not set
# CONFIG_KGDBOE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
# CONFIG_NET_POLL_CONTROLLER is not set
#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=y
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
CONFIG_SOFT_WATCHDOG=y
# CONFIG_WDT is not set
CONFIG_WDTPCI=y
# CONFIG_WDT_501_PCI is not set
# CONFIG_PCWATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
CONFIG_I810_TCO=m
# CONFIG_MIXCOMWD is not set
# CONFIG_SCx200_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_AMD7XX_TCO is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_HW_RANDOM 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_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
# CONFIG_HANGCHECK_TIMER is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
# CONFIG_USB is not set
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_GADGET is not set
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_JFS_FS=m
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
CONFIG_XFS_FS=m
# CONFIG_XFS_RT is not set
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_POSIX_ACL 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=y
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_GSS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# 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=y
# 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
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_STACKOVERFLOW 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_DEBUG_PAGEALLOC is not set
# CONFIG_SPINLINE is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_LOCKMETER is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_KGDB is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
CONFIG_CRC32=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_PC=y
[-- Attachment #3: lspci --]
[-- Type: text/plain, Size: 968 bytes --]
00:00.0 Host bridge: Intel Corp. 82860 860 (Wombat) Chipset Host Bridge (MCH) (rev 04)
00:01.0 PCI bridge: Intel Corp. 82850 850 (Tehama) Chipset AGP Bridge (rev 04)
00:02.0 PCI bridge: Intel Corp. 82860 860 (Wombat) Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 04)
00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 04)
00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 04)
00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 04)
00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 04)
00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio (rev 04)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 85)
02:1f.0 PCI bridge: Intel Corp. 82806AA PCI64 Hub PCI Bridge (rev 03)
03:00.0 PIC: Intel Corp. 82806AA PCI64 Hub Advanced Programmable Interrupt Controller (rev 01)
04:04.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0c)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
[not found] <1075502193.26342.61.camel@markh1.pdx.osdl.net.suse.lists.linux.kernel>
@ 2004-01-31 0:46 ` Andi Kleen
0 siblings, 0 replies; 13+ messages in thread
From: Andi Kleen @ 2004-01-31 0:46 UTC (permalink / raw)
To: Mark Haverkamp; +Cc: B.Zolnierkiewicz, linux-kernel
Mark Haverkamp <markh@osdl.org> writes:
> We have some test machines here at OSDL that have a problem with the ide
> cdrom driver hanging when we cat the /proc/ide/hda/identify file. After
> 30 seconds the console displays: "hda: lost interrupt" which reoccurs
> every 30 seconds forever. We noticed it on 2.6.2-rc2-mm1 but It looks
> like this has been a problem for a while. Our test machines just changed
> their configuration to use make defconfig. I found that if
> CONFIG_IDE_TASKFILE_IO is N then the hang doesn't occur. Is this a
> common problem or are there just certain drives that won't work with
> taskfile i/o enabled? I've included my .config, lspci as attachments.
> The cdrom model is CD-224E.
I looked at this some time ago together with BenH and Bart. The problem
seems to be that the taskfile statemachine for identify is quite broken.
(even when it didn't hang it usually returned only garbage on other
CD ROMs).
The CD ROM doesn't answer the request for some reason and then the
Linux taskfile code goes into an endless loop sending retries.
Bart had a patch to at least cure the hang by erroring out.
-Andi
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-01-30 22:36 Mark Haverkamp
@ 2004-02-01 20:48 ` Bartlomiej Zolnierkiewicz
2004-02-02 18:46 ` Mark Haverkamp
0 siblings, 1 reply; 13+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2004-02-01 20:48 UTC (permalink / raw)
To: Mark Haverkamp; +Cc: linux-kernel, Cliff White
Hi,
On Friday 30 of January 2004 23:36, Mark Haverkamp wrote:
> We have some test machines here at OSDL that have a problem with the ide
> cdrom driver hanging when we cat the /proc/ide/hda/identify file. After
> 30 seconds the console displays: "hda: lost interrupt" which reoccurs
> every 30 seconds forever. We noticed it on 2.6.2-rc2-mm1 but It looks
> like this has been a problem for a while. Our test machines just changed
> their configuration to use make defconfig. I found that if
> CONFIG_IDE_TASKFILE_IO is N then the hang doesn't occur. Is this a
> common problem or are there just certain drives that won't work with
> taskfile i/o enabled? I've included my .config, lspci as attachments.
> The cdrom model is CD-224E.
Does 'hdparm -I /dev/hda" work? If so can you try this patch?
It reverts taskfile code to use old (non-taskfile) order of accessing
port registers for ATAPI identify command. This is a good starting point.
If CONFIG_IDE_TASKFILE_IO is N code just ignores BUSY status of a drive
and reads some random data. I would like to have this problem solved
at least instead of adding the same workaround to CONFIG_IDE_TASKFILE_IO.
Cheers,
--bart
linux-2.6.2-rc2-root/drivers/ide/ide-taskfile.c | 14 ++++++++++++++
1 files changed, 14 insertions(+)
diff -puN drivers/ide/ide-taskfile.c~ide_tf_identify_debug drivers/ide/ide-taskfile.c
--- linux-2.6.2-rc2/drivers/ide/ide-taskfile.c~ide_tf_identify_debug 2004-02-01 21:06:58.494873136 +0100
+++ linux-2.6.2-rc2-root/drivers/ide/ide-taskfile.c 2004-02-01 21:15:06.268720240 +0100
@@ -142,6 +142,20 @@ ide_startstop_t do_rw_taskfile (ide_driv
void debug_taskfile(drive, task);
#endif /* CONFIG_IDE_TASK_IOCTL_DEBUG */
+ if (taskfile->command == WIN_PIDENTIFY) {
+ hwif->OUTB(taskfile->feature, IDE_FEATURE_REG);
+
+ if (IDE_CONTROL_REG)
+ hwif->OUTB(drive->ctl, IDE_CONTROL_REG);
+ SELECT_MASK(drive, 0);
+
+ hwif->OUTB(taskfile->sector_count, IDE_NSECTOR_REG);
+
+ ide_execute_command(drive, taskfile->command, task->handler,
+ WAIT_WORSTCASE, NULL);
+ return ide_started;
+ }
+
/* ALL Command Block Executions SHALL clear nIEN, unless otherwise */
if (IDE_CONTROL_REG) {
/* clear nIEN */
_
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-02-01 20:48 ` Bartlomiej Zolnierkiewicz
@ 2004-02-02 18:46 ` Mark Haverkamp
2004-02-02 19:45 ` Bartlomiej Zolnierkiewicz
0 siblings, 1 reply; 13+ messages in thread
From: Mark Haverkamp @ 2004-02-02 18:46 UTC (permalink / raw)
To: Bartlomiej Zolnierkiewicz; +Cc: linux-kernel, Cliff White
On Sun, 2004-02-01 at 12:48, Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> On Friday 30 of January 2004 23:36, Mark Haverkamp wrote:
> > We have some test machines here at OSDL that have a problem with the ide
> > cdrom driver hanging when we cat the /proc/ide/hda/identify file. After
> > 30 seconds the console displays: "hda: lost interrupt" which reoccurs
> > every 30 seconds forever. We noticed it on 2.6.2-rc2-mm1 but It looks
> > like this has been a problem for a while. Our test machines just changed
> > their configuration to use make defconfig. I found that if
> > CONFIG_IDE_TASKFILE_IO is N then the hang doesn't occur. Is this a
> > common problem or are there just certain drives that won't work with
> > taskfile i/o enabled? I've included my .config, lspci as attachments.
> > The cdrom model is CD-224E.
>
> Does 'hdparm -I /dev/hda" work? If so can you try this patch?
> It reverts taskfile code to use old (non-taskfile) order of accessing
> port registers for ATAPI identify command. This is a good starting point.
>
> If CONFIG_IDE_TASKFILE_IO is N code just ignores BUSY status of a drive
> and reads some random data. I would like to have this problem solved
> at least instead of adding the same workaround to CONFIG_IDE_TASKFILE_IO.
>
> Cheers,
> --bart
Thanks,
hdparm -I /dev/hda didn't hang. I got this on the console:
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04Aborted Command
I added the patch that you provided and I still get the hang when I cat
/proc/ide/hda/identify. I put a printk In the code to make sure that it
was going through the added code, and it is.
Mark.
--
Mark Haverkamp <markh@osdl.org>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-02-02 18:46 ` Mark Haverkamp
@ 2004-02-02 19:45 ` Bartlomiej Zolnierkiewicz
2004-02-02 20:45 ` Mark Haverkamp
0 siblings, 1 reply; 13+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2004-02-02 19:45 UTC (permalink / raw)
To: Mark Haverkamp; +Cc: linux-kernel, Cliff White
On Monday 02 of February 2004 19:46, Mark Haverkamp wrote:
> On Sun, 2004-02-01 at 12:48, Bartlomiej Zolnierkiewicz wrote:
> > Hi,
> >
> > On Friday 30 of January 2004 23:36, Mark Haverkamp wrote:
> > > We have some test machines here at OSDL that have a problem with the
> > > ide cdrom driver hanging when we cat the /proc/ide/hda/identify file.
> > > After 30 seconds the console displays: "hda: lost interrupt" which
> > > reoccurs every 30 seconds forever. We noticed it on 2.6.2-rc2-mm1 but
> > > It looks like this has been a problem for a while. Our test machines
> > > just changed their configuration to use make defconfig. I found that
> > > if
> > > CONFIG_IDE_TASKFILE_IO is N then the hang doesn't occur. Is this a
> > > common problem or are there just certain drives that won't work with
> > > taskfile i/o enabled? I've included my .config, lspci as attachments.
> > > The cdrom model is CD-224E.
> >
> > Does 'hdparm -I /dev/hda" work? If so can you try this patch?
> > It reverts taskfile code to use old (non-taskfile) order of accessing
> > port registers for ATAPI identify command. This is a good starting
> > point.
> >
> > If CONFIG_IDE_TASKFILE_IO is N code just ignores BUSY status of a drive
> > and reads some random data. I would like to have this problem solved
> > at least instead of adding the same workaround to CONFIG_IDE_TASKFILE_IO.
> >
> > Cheers,
> > --bart
>
> Thanks,
>
> hdparm -I /dev/hda didn't hang. I got this on the console:
>
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04Aborted Command
That's okay.
hdparm first tries WIN_IDENTIFY which can fail on ATAPI devices.
> I added the patch that you provided and I still get the hang when I cat
> /proc/ide/hda/identify. I put a printk In the code to make sure that it
> was going through the added code, and it is.
So it is something different. Can you give this patch a go?
We will know more about what's going on.
Thanks,
--bart
linux-2.6.2-rc2-root/drivers/ide/ide-taskfile.c | 3 +++
1 files changed, 3 insertions(+)
diff -puN drivers/ide/ide-taskfile.c~ide_tf_identify_debug1 drivers/ide/ide-taskfile.c
--- linux-2.6.2-rc2/drivers/ide/ide-taskfile.c~ide_tf_identify_debug1 2004-02-02 20:30:16.435636072 +0100
+++ linux-2.6.2-rc2-root/drivers/ide/ide-taskfile.c 2004-02-02 20:40:25.604028400 +0100
@@ -794,6 +794,7 @@ static u8 wait_drive_not_busy(ide_drive_
*/
while (((stat = hwif->INB(IDE_STATUS_REG)) & BUSY_STAT) && retries--)
udelay(10);
+ printk("%s: (WAIT_NOT_BUSY) status=0x%02x\n", drive->name, stat);
return stat;
}
@@ -811,6 +812,7 @@ check_status:
if (!OK_STAT(stat, good_stat, BAD_R_STAT)) {
if (stat & (ERR_STAT | DRQ_STAT))
return DRIVER(drive)->error(drive, __FUNCTION__, stat);
+ printk("%s: (BUSY) status=0x%02x\n", drive->name, stat);
/* BUSY_STAT: No data yet, so wait for another IRQ. */
ide_set_handler(drive, &task_in_intr, WAIT_WORSTCASE, NULL);
return ide_started;
@@ -836,6 +838,7 @@ check_status:
if (!rq->nr_sectors) {
good_stat = 0;
stat = wait_drive_not_busy(drive);
+ printk("%s: (CHECK_STATUS) status=0x%02x\n", drive->name, stat);
goto check_status;
}
_
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-02-02 19:45 ` Bartlomiej Zolnierkiewicz
@ 2004-02-02 20:45 ` Mark Haverkamp
2004-02-02 21:35 ` Bartlomiej Zolnierkiewicz
0 siblings, 1 reply; 13+ messages in thread
From: Mark Haverkamp @ 2004-02-02 20:45 UTC (permalink / raw)
To: Bartlomiej Zolnierkiewicz; +Cc: linux-kernel, Cliff White
On Mon, 2004-02-02 at 11:45, Bartlomiej Zolnierkiewicz wrote:
> On Monday 02 of February 2004 19:46, Mark Haverkamp wrote:
> > On Sun, 2004-02-01 at 12:48, Bartlomiej Zolnierkiewicz wrote:
[ .... ]
> >
> > Thanks,
> >
> > hdparm -I /dev/hda didn't hang. I got this on the console:
> >
> > hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > hda: drive_cmd: error=0x04Aborted Command
>
> That's okay.
> hdparm first tries WIN_IDENTIFY which can fail on ATAPI devices.
>
> > I added the patch that you provided and I still get the hang when I cat
> > /proc/ide/hda/identify. I put a printk In the code to make sure that it
> > was going through the added code, and it is.
>
> So it is something different. Can you give this patch a go?
> We will know more about what's going on.
>
> Thanks,
> --bart
OK, Here it is:
hda: (WAIT_NOT_BUSY) status=0xd0
hda: (CHECK_STATUS) status=0xd0
hda: (BUSY) status=0xd0
hda: lost interrupt
hda: (BUSY) status=0x50
hda: lost interrupt
hda: (BUSY) status=0x50
hda: lost interrupt
hda: (BUSY) status=0x50
hda: lost interrupt
hda: (BUSY) status=0x50
--
Mark Haverkamp <markh@osdl.org>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-02-02 20:45 ` Mark Haverkamp
@ 2004-02-02 21:35 ` Bartlomiej Zolnierkiewicz
2004-02-02 21:44 ` Mark Haverkamp
0 siblings, 1 reply; 13+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2004-02-02 21:35 UTC (permalink / raw)
To: Mark Haverkamp; +Cc: linux-kernel, Cliff White
On Monday 02 of February 2004 21:45, Mark Haverkamp wrote:
> On Mon, 2004-02-02 at 11:45, Bartlomiej Zolnierkiewicz wrote:
> > On Monday 02 of February 2004 19:46, Mark Haverkamp wrote:
> > > On Sun, 2004-02-01 at 12:48, Bartlomiej Zolnierkiewicz wrote:
>
> [ .... ]
>
> > > Thanks,
> > >
> > > hdparm -I /dev/hda didn't hang. I got this on the console:
> > >
> > > hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > > hda: drive_cmd: error=0x04Aborted Command
> >
> > That's okay.
> > hdparm first tries WIN_IDENTIFY which can fail on ATAPI devices.
> >
> > > I added the patch that you provided and I still get the hang when I cat
> > > /proc/ide/hda/identify. I put a printk In the code to make sure that
> > > it was going through the added code, and it is.
> >
> > So it is something different. Can you give this patch a go?
> > We will know more about what's going on.
> >
> > Thanks,
> > --bart
>
> OK, Here it is:
>
> hda: (WAIT_NOT_BUSY) status=0xd0
> hda: (CHECK_STATUS) status=0xd0
> hda: (BUSY) status=0xd0
> hda: lost interrupt
> hda: (BUSY) status=0x50
> hda: lost interrupt
> hda: (BUSY) status=0x50
> hda: lost interrupt
> hda: (BUSY) status=0x50
> hda: lost interrupt
> hda: (BUSY) status=0x50
Here we go with next (incremental) patch...
linux-2.6.2-rc2-root/drivers/ide/ide-taskfile.c | 12 ++++++++----
1 files changed, 8 insertions(+), 4 deletions(-)
diff -puN drivers/ide/ide-taskfile.c~ide_tf_identify_debug2 drivers/ide/ide-taskfile.c
--- linux-2.6.2-rc2/drivers/ide/ide-taskfile.c~ide_tf_identify_debug2 2004-02-02 22:24:31.802461904 +0100
+++ linux-2.6.2-rc2-root/drivers/ide/ide-taskfile.c 2004-02-02 22:33:54.987844712 +0100
@@ -786,14 +786,18 @@ EXPORT_SYMBOL(task_mulout_intr);
static u8 wait_drive_not_busy(ide_drive_t *drive)
{
ide_hwif_t *hwif = HWIF(drive);
- int retries = 5;
+ int retries = 100;
u8 stat;
+
/*
- * (ks) Last sector was transfered, wait until drive is ready.
- * This can take up to 10 usec. We willl wait max 50 us.
+ * Last sector was transfered, wait until drive is ready.
+ * This can take up to 10 usec, but we will wait max 1 ms
+ * (drive_cmd_intr() waits that long).
*/
- while (((stat = hwif->INB(IDE_STATUS_REG)) & BUSY_STAT) && retries--)
+ while (((stat = hwif->INB(IDE_STATUS_REG)) & BUSY_STAT) && retries--) {
+ printk("%s: (UDELAY(10)) status=0x%02x\n", drive->name, stat);
udelay(10);
+ }
printk("%s: (WAIT_NOT_BUSY) status=0x%02x\n", drive->name, stat);
return stat;
}
_
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-02-02 21:35 ` Bartlomiej Zolnierkiewicz
@ 2004-02-02 21:44 ` Mark Haverkamp
2004-02-02 23:37 ` Bartlomiej Zolnierkiewicz
0 siblings, 1 reply; 13+ messages in thread
From: Mark Haverkamp @ 2004-02-02 21:44 UTC (permalink / raw)
To: Bartlomiej Zolnierkiewicz; +Cc: linux-kernel, Cliff White
On Mon, 2004-02-02 at 13:35, Bartlomiej Zolnierkiewicz wrote:
> On Monday 02 of February 2004 21:45, Mark Haverkamp wrote:
> > On Mon, 2004-02-02 at 11:45, Bartlomiej Zolnierkiewicz wrote:
> > > On Monday 02 of February 2004 19:46, Mark Haverkamp wrote:
> > > > On Sun, 2004-02-01 at 12:48, Bartlomiej Zolnierkiewicz wrote:
> >
> > [ .... ]
> >
> > > > Thanks,
> > > >
> > > > hdparm -I /dev/hda didn't hang. I got this on the console:
> > > >
> > > > hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > > > hda: drive_cmd: error=0x04Aborted Command
> > >
> > > That's okay.
> > > hdparm first tries WIN_IDENTIFY which can fail on ATAPI devices.
> > >
> > > > I added the patch that you provided and I still get the hang when I cat
> > > > /proc/ide/hda/identify. I put a printk In the code to make sure that
> > > > it was going through the added code, and it is.
> > >
> > > So it is something different. Can you give this patch a go?
> > > We will know more about what's going on.
> > >
> > > Thanks,
> > > --bart
> >
> > OK, Here it is:
> >
> > hda: (WAIT_NOT_BUSY) status=0xd0
> > hda: (CHECK_STATUS) status=0xd0
> > hda: (BUSY) status=0xd0
> > hda: lost interrupt
> > hda: (BUSY) status=0x50
> > hda: lost interrupt
> > hda: (BUSY) status=0x50
> > hda: lost interrupt
> > hda: (BUSY) status=0x50
> > hda: lost interrupt
> > hda: (BUSY) status=0x50
>
> Here we go with next (incremental) patch...
>
> linux-2.6.2-rc2-root/drivers/ide/ide-taskfile.c | 12 ++++++++----
> 1 files changed, 8 insertions(+), 4 deletions(-)
>
> diff -puN drivers/ide/ide-taskfile.c~ide_tf_identify_debug2 drivers/ide/ide-taskfile.c
> --- linux-2.6.2-rc2/drivers/ide/ide-taskfile.c~ide_tf_identify_debug2 2004-02-02 22:24:31.802461904 +0100
> +++ linux-2.6.2-rc2-root/drivers/ide/ide-taskfile.c 2004-02-02 22:33:54.987844712 +0100
> @@ -786,14 +786,18 @@ EXPORT_SYMBOL(task_mulout_intr);
> static u8 wait_drive_not_busy(ide_drive_t *drive)
> {
> ide_hwif_t *hwif = HWIF(drive);
> - int retries = 5;
> + int retries = 100;
> u8 stat;
> +
> /*
> - * (ks) Last sector was transfered, wait until drive is ready.
> - * This can take up to 10 usec. We willl wait max 50 us.
> + * Last sector was transfered, wait until drive is ready.
> + * This can take up to 10 usec, but we will wait max 1 ms
> + * (drive_cmd_intr() waits that long).
> */
> - while (((stat = hwif->INB(IDE_STATUS_REG)) & BUSY_STAT) && retries--)
> + while (((stat = hwif->INB(IDE_STATUS_REG)) & BUSY_STAT) && retries--) {
> + printk("%s: (UDELAY(10)) status=0x%02x\n", drive->name, stat);
> udelay(10);
> + }
> printk("%s: (WAIT_NOT_BUSY) status=0x%02x\n", drive->name, stat);
> return stat;
> }
>
> _
No hang this time. Saw this on the console:
hda: (UDELAY(10)) status=0xd8
hda: (WAIT_NOT_BUSY) status=0x50
hda: (CHECK_STATUS) status=0x50
hda: (UDELAY(10)) status=0xd8
hda: (WAIT_NOT_BUSY) status=0x50
hda: (CHECK_STATUS) status=0x50
--
Mark Haverkamp <markh@osdl.org>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-02-02 21:44 ` Mark Haverkamp
@ 2004-02-02 23:37 ` Bartlomiej Zolnierkiewicz
2004-02-02 23:52 ` Mark Haverkamp
0 siblings, 1 reply; 13+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2004-02-02 23:37 UTC (permalink / raw)
To: Mark Haverkamp; +Cc: linux-kernel, Cliff White
On Monday 02 of February 2004 22:44, Mark Haverkamp wrote:
> On Mon, 2004-02-02 at 13:35, Bartlomiej Zolnierkiewicz wrote:
> > On Monday 02 of February 2004 21:45, Mark Haverkamp wrote:
> > > On Mon, 2004-02-02 at 11:45, Bartlomiej Zolnierkiewicz wrote:
> > > > On Monday 02 of February 2004 19:46, Mark Haverkamp wrote:
> > > > > On Sun, 2004-02-01 at 12:48, Bartlomiej Zolnierkiewicz wrote:
> > >
> > > [ .... ]
> > >
> > > > > Thanks,
> > > > >
> > > > > hdparm -I /dev/hda didn't hang. I got this on the console:
> > > > >
> > > > > hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > > > > hda: drive_cmd: error=0x04Aborted Command
> > > >
> > > > That's okay.
> > > > hdparm first tries WIN_IDENTIFY which can fail on ATAPI devices.
> > > >
> > > > > I added the patch that you provided and I still get the hang when I
> > > > > cat /proc/ide/hda/identify. I put a printk In the code to make
> > > > > sure that it was going through the added code, and it is.
> > > >
> > > > So it is something different. Can you give this patch a go?
> > > > We will know more about what's going on.
> > > >
> > > > Thanks,
> > > > --bart
> > >
> > > OK, Here it is:
> > >
> > > hda: (WAIT_NOT_BUSY) status=0xd0
> > > hda: (CHECK_STATUS) status=0xd0
> > > hda: (BUSY) status=0xd0
> > > hda: lost interrupt
> > > hda: (BUSY) status=0x50
> > > hda: lost interrupt
> > > hda: (BUSY) status=0x50
> > > hda: lost interrupt
> > > hda: (BUSY) status=0x50
> > > hda: lost interrupt
> > > hda: (BUSY) status=0x50
> >
> > Here we go with next (incremental) patch...
> >
> > linux-2.6.2-rc2-root/drivers/ide/ide-taskfile.c | 12 ++++++++----
> > 1 files changed, 8 insertions(+), 4 deletions(-)
> >
> > diff -puN drivers/ide/ide-taskfile.c~ide_tf_identify_debug2
> > drivers/ide/ide-taskfile.c ---
> > linux-2.6.2-rc2/drivers/ide/ide-taskfile.c~ide_tf_identify_debug2 2004-02
> >-02 22:24:31.802461904 +0100 +++
> > linux-2.6.2-rc2-root/drivers/ide/ide-taskfile.c 2004-02-02
> > 22:33:54.987844712 +0100 @@ -786,14 +786,18 @@
> > EXPORT_SYMBOL(task_mulout_intr);
> > static u8 wait_drive_not_busy(ide_drive_t *drive)
> > {
> > ide_hwif_t *hwif = HWIF(drive);
> > - int retries = 5;
> > + int retries = 100;
> > u8 stat;
> > +
> > /*
> > - * (ks) Last sector was transfered, wait until drive is ready.
> > - * This can take up to 10 usec. We willl wait max 50 us.
> > + * Last sector was transfered, wait until drive is ready.
> > + * This can take up to 10 usec, but we will wait max 1 ms
> > + * (drive_cmd_intr() waits that long).
> > */
> > - while (((stat = hwif->INB(IDE_STATUS_REG)) & BUSY_STAT) && retries--)
> > + while (((stat = hwif->INB(IDE_STATUS_REG)) & BUSY_STAT) && retries--) {
> > + printk("%s: (UDELAY(10)) status=0x%02x\n", drive->name, stat);
> > udelay(10);
> > + }
> > printk("%s: (WAIT_NOT_BUSY) status=0x%02x\n", drive->name, stat);
> > return stat;
> > }
> >
> > _
>
> No hang this time. Saw this on the console:
>
> hda: (UDELAY(10)) status=0xd8
> hda: (WAIT_NOT_BUSY) status=0x50
> hda: (CHECK_STATUS) status=0x50
> hda: (UDELAY(10)) status=0xd8
> hda: (WAIT_NOT_BUSY) status=0x50
> hda: (CHECK_STATUS) status=0x50
Now, can you comment out "(UDELAY(10))" printk and add printk for "retries"
variable after while {} loop. I thought there will be more "(UDELAY(10))"
messages - but I forgot about delay introduced by printk() call :-).
--bart
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-02-02 23:37 ` Bartlomiej Zolnierkiewicz
@ 2004-02-02 23:52 ` Mark Haverkamp
2004-02-03 0:13 ` Bartlomiej Zolnierkiewicz
0 siblings, 1 reply; 13+ messages in thread
From: Mark Haverkamp @ 2004-02-02 23:52 UTC (permalink / raw)
To: Bartlomiej Zolnierkiewicz; +Cc: linux-kernel, Cliff White
On Mon, 2004-02-02 at 15:37, Bartlomiej Zolnierkiewicz wrote:
> On Monday 02 of February 2004 22:44, Mark Haverkamp wrote:
> > On Mon, 2004-02-02 at 13:35, Bartlomiej Zolnierkiewicz wrote:
> > > On Monday 02 of February 2004 21:45, Mark Haverkamp wrote:
> > > > On Mon, 2004-02-02 at 11:45, Bartlomiej Zolnierkiewicz wrote:
> > > > > On Monday 02 of February 2004 19:46, Mark Haverkamp wrote:
> > > > > > On Sun, 2004-02-01 at 12:48, Bartlomiej Zolnierkiewicz wrote:
> > > >
[ ... ]
> Now, can you comment out "(UDELAY(10))" printk and add printk for "retries"
> variable after while {} loop. I thought there will be more "(UDELAY(10))"
> messages - but I forgot about delay introduced by printk() call :-).
>
> --bart
I ran twice, got the same results:
1)
hda: (WAIT_NOT_BUSY) status=0x50 retry 94
hda: (CHECK_STATUS) status=0x50
hda: (WAIT_NOT_BUSY) status=0x50 retry 94
hda: (CHECK_STATUS) status=0x50
2)
hda: (WAIT_NOT_BUSY) status=0x50 retry 94
hda: (CHECK_STATUS) status=0x50
hda: (WAIT_NOT_BUSY) status=0x50 retry 94
hda: (CHECK_STATUS) status=0x50
--
Mark Haverkamp <markh@osdl.org>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-02-02 23:52 ` Mark Haverkamp
@ 2004-02-03 0:13 ` Bartlomiej Zolnierkiewicz
2004-02-03 0:16 ` Mark Haverkamp
0 siblings, 1 reply; 13+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2004-02-03 0:13 UTC (permalink / raw)
To: Mark Haverkamp; +Cc: linux-kernel, Cliff White
On Tuesday 03 of February 2004 00:52, Mark Haverkamp wrote:
> On Mon, 2004-02-02 at 15:37, Bartlomiej Zolnierkiewicz wrote:
> > On Monday 02 of February 2004 22:44, Mark Haverkamp wrote:
> > > On Mon, 2004-02-02 at 13:35, Bartlomiej Zolnierkiewicz wrote:
> > > > On Monday 02 of February 2004 21:45, Mark Haverkamp wrote:
> > > > > On Mon, 2004-02-02 at 11:45, Bartlomiej Zolnierkiewicz wrote:
> > > > > > On Monday 02 of February 2004 19:46, Mark Haverkamp wrote:
> > > > > > > On Sun, 2004-02-01 at 12:48, Bartlomiej Zolnierkiewicz wrote:
>
> [ ... ]
>
> > Now, can you comment out "(UDELAY(10))" printk and add printk for
> > "retries" variable after while {} loop. I thought there will be more
> > "(UDELAY(10))" messages - but I forgot about delay introduced by printk()
> > call :-).
> >
> > --bart
>
> I ran twice, got the same results:
>
> 1)
> hda: (WAIT_NOT_BUSY) status=0x50 retry 94
> hda: (CHECK_STATUS) status=0x50
> hda: (WAIT_NOT_BUSY) status=0x50 retry 94
> hda: (CHECK_STATUS) status=0x50
Is this output for single 'cat /proc/ide/hda/identify' run?
There should be only one WAIT_NOT_BUSY and one CHECK_STATUS.
> 2)
> hda: (WAIT_NOT_BUSY) status=0x50 retry 94
> hda: (CHECK_STATUS) status=0x50
> hda: (WAIT_NOT_BUSY) status=0x50 retry 94
> hda: (CHECK_STATUS) status=0x50
Wow, 94 retries vs. limit of 5 previously.
Please also check if 'hdparm -Istdin</proc/ide/hda/identify'
returns correct information now.
Thanks,
--bart
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-02-03 0:13 ` Bartlomiej Zolnierkiewicz
@ 2004-02-03 0:16 ` Mark Haverkamp
2004-02-03 1:09 ` Bartlomiej Zolnierkiewicz
0 siblings, 1 reply; 13+ messages in thread
From: Mark Haverkamp @ 2004-02-03 0:16 UTC (permalink / raw)
To: Bartlomiej Zolnierkiewicz; +Cc: linux-kernel, Cliff White
On Mon, 2004-02-02 at 16:13, Bartlomiej Zolnierkiewicz wrote:
> On Tuesday 03 of February 2004 00:52, Mark Haverkamp wrote:
> > On Mon, 2004-02-02 at 15:37, Bartlomiej Zolnierkiewicz wrote:
> > > On Monday 02 of February 2004 22:44, Mark Haverkamp wrote:
> > > > On Mon, 2004-02-02 at 13:35, Bartlomiej Zolnierkiewicz wrote:
> > > > > On Monday 02 of February 2004 21:45, Mark Haverkamp wrote:
> > > > > > On Mon, 2004-02-02 at 11:45, Bartlomiej Zolnierkiewicz wrote:
> > > > > > > On Monday 02 of February 2004 19:46, Mark Haverkamp wrote:
> > > > > > > > On Sun, 2004-02-01 at 12:48, Bartlomiej Zolnierkiewicz wrote:
> >
> > [ ... ]
> >
> > > Now, can you comment out "(UDELAY(10))" printk and add printk for
> > > "retries" variable after while {} loop. I thought there will be more
> > > "(UDELAY(10))" messages - but I forgot about delay introduced by printk()
> > > call :-).
> > >
> > > --bart
> >
> > I ran twice, got the same results:
> >
> > 1)
> > hda: (WAIT_NOT_BUSY) status=0x50 retry 94
> > hda: (CHECK_STATUS) status=0x50
> > hda: (WAIT_NOT_BUSY) status=0x50 retry 94
> > hda: (CHECK_STATUS) status=0x50
>
> Is this output for single 'cat /proc/ide/hda/identify' run?
> There should be only one WAIT_NOT_BUSY and one CHECK_STATUS.
I see two for each cat. Also, the 94 is the leftover number. So there
were probably about 6 retries.
>
> > 2)
> > hda: (WAIT_NOT_BUSY) status=0x50 retry 94
> > hda: (CHECK_STATUS) status=0x50
> > hda: (WAIT_NOT_BUSY) status=0x50 retry 94
> > hda: (CHECK_STATUS) status=0x50
>
> Wow, 94 retries vs. limit of 5 previously.
The 94 is the leftover number. Retry started at 100 and was decremented
in the status check loop. So there were probably about 6 retries.
>
> Please also check if 'hdparm -Istdin</proc/ide/hda/identify'
> returns correct information now.
# hdparm -Istdin</proc/ide/hda/identify
ATAPI CD-ROM, with removable media
Model Number: CD-224E
Serial Number:
Firmware Revision: 1.5A
Standards:
Likely used CD-ROM ATAPI-1
Configuration:
DRQ response: 50us.
Packet size: 12 bytes
Capabilities:
Cmd overlap, LBA, IORDY(can be disabled)
Buffer size: 128.0kB
Overlap support: 896us to release bus. 115us to clear BSY after SERVICE
cmd.
DMA: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Plus:
hda: (WAIT_NOT_BUSY) status=0x50 retry 94
hda: (CHECK_STATUS) status=0x50
on the console.
>
> Thanks,
> --bart
I see two for each cat. Also, the 94 is the leftover number. So there
were probably about 6 retries.
Mark.
--
Mark Haverkamp <markh@osdl.org>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: ide taskfile and cdrom hang
2004-02-03 0:16 ` Mark Haverkamp
@ 2004-02-03 1:09 ` Bartlomiej Zolnierkiewicz
0 siblings, 0 replies; 13+ messages in thread
From: Bartlomiej Zolnierkiewicz @ 2004-02-03 1:09 UTC (permalink / raw)
To: Mark Haverkamp; +Cc: linux-kernel, Cliff White
On Tuesday 03 of February 2004 01:16, Mark Haverkamp wrote:
> On Mon, 2004-02-02 at 16:13, Bartlomiej Zolnierkiewicz wrote:
> > On Tuesday 03 of February 2004 00:52, Mark Haverkamp wrote:
> > > On Mon, 2004-02-02 at 15:37, Bartlomiej Zolnierkiewicz wrote:
> > > > On Monday 02 of February 2004 22:44, Mark Haverkamp wrote:
> > > > > On Mon, 2004-02-02 at 13:35, Bartlomiej Zolnierkiewicz wrote:
> > > > > > On Monday 02 of February 2004 21:45, Mark Haverkamp wrote:
> > > > > > > On Mon, 2004-02-02 at 11:45, Bartlomiej Zolnierkiewicz wrote:
> > > > > > > > On Monday 02 of February 2004 19:46, Mark Haverkamp wrote:
> > > > > > > > > On Sun, 2004-02-01 at 12:48, Bartlomiej Zolnierkiewicz
> > > > > > > > > wrote:
> > >
> > > [ ... ]
> > >
> > > > Now, can you comment out "(UDELAY(10))" printk and add printk for
> > > > "retries" variable after while {} loop. I thought there will be more
> > > > "(UDELAY(10))" messages - but I forgot about delay introduced by
> > > > printk() call :-).
> > > >
> > > > --bart
> > >
> > > I ran twice, got the same results:
> > >
> > > 1)
> > > hda: (WAIT_NOT_BUSY) status=0x50 retry 94
> > > hda: (CHECK_STATUS) status=0x50
> > > hda: (WAIT_NOT_BUSY) status=0x50 retry 94
> > > hda: (CHECK_STATUS) status=0x50
> >
> > Is this output for single 'cat /proc/ide/hda/identify' run?
> > There should be only one WAIT_NOT_BUSY and one CHECK_STATUS.
>
> I see two for each cat. Also, the 94 is the leftover number. So there
> were probably about 6 retries.
Yep, I need some caffeine or sleep :-).
Okay, so 6 retries were needed and the limit was 5.
Thanks,
--bart
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2004-02-03 1:08 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1075502193.26342.61.camel@markh1.pdx.osdl.net.suse.lists.linux.kernel>
2004-01-31 0:46 ` ide taskfile and cdrom hang Andi Kleen
2004-01-30 22:36 Mark Haverkamp
2004-02-01 20:48 ` Bartlomiej Zolnierkiewicz
2004-02-02 18:46 ` Mark Haverkamp
2004-02-02 19:45 ` Bartlomiej Zolnierkiewicz
2004-02-02 20:45 ` Mark Haverkamp
2004-02-02 21:35 ` Bartlomiej Zolnierkiewicz
2004-02-02 21:44 ` Mark Haverkamp
2004-02-02 23:37 ` Bartlomiej Zolnierkiewicz
2004-02-02 23:52 ` Mark Haverkamp
2004-02-03 0:13 ` Bartlomiej Zolnierkiewicz
2004-02-03 0:16 ` Mark Haverkamp
2004-02-03 1:09 ` Bartlomiej Zolnierkiewicz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox