[parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17

[parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17

[Steve Bromwich]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1496 bytes --]

Hi,

I installed 2.4.22-pa17 on my machine over the weekend, and I'm getting
processes stuck in D state. The machine usually runs for several hours
without any problem, but then processes start dying, apparently fairly
randomly, the load goes up, and vmstat shows CPU as near 100% idle. I
*think* it's something to do with writing to the drive, since one of the
first things to die is syslogging. Anything that doesn't touch the drive
(eg, IRC clients) seem to run forever. One thing that really kills it
seems to be daily maintenance around 6am; I can see mail being delivered
until then, and after that it queues on my backup MX. The only way to get
the machine back is to pull the power - shutdown -r now hangs, presing the
power button gets shutdown started but still hangs, and the TOC doesn't
seem to produce any output on my serial console. I've only seen a process
die in ffront of me once, when I was exiting from a bash session; the
machine just sat there with no i/o, ps aux showed the bash session stuck
in D state, and I couldn't ctrl-c or ctrl-z out of it at all.

Prior to this I was running 2.4.18 with no problem with the machine
running for months at a time. Has anyone seen this problem and/or got any
tips on how to figure out what's going wrong? I can't find any error
output anywhere that's hinting what could be wrong, so I'm really stuck on
this one.

I've attached my .config, dmesg and cpuinfo in case anyone can see
anything obvious. Thanks for any help!

Cheers, Steve

[-- Attachment #2: config_2422pa17 --]
[-- Type: TEXT/PLAIN, Size: 13534 bytes --]

#
# Automatically generated make config: don't edit
#
CONFIG_PARISC=y
# CONFIG_UID16 is not set
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

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

#
# Processor type
#
# CONFIG_PA7100 is not set
# CONFIG_PA7200 is not set
CONFIG_PA7100LC=y
# CONFIG_PA8X00 is not set
CONFIG_PA11=y

#
# General options
#
# CONFIG_SMP is not set
CONFIG_CHASSIS_LCD_LED=y
# CONFIG_PDC_CHASSIS is not set
CONFIG_IOMMU_CCIO=y
CONFIG_GSC=y
CONFIG_GSC_LASI=y
CONFIG_GSC_WAX=y
CONFIG_EISA=y
CONFIG_ISA=y
# CONFIG_PCI is not set

#
# General setup
#
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
# CONFIG_HOTPLUG_PCI is not set
CONFIG_NET=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_SOM is not set
CONFIG_BINFMT_MISC=m
# CONFIG_PM 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 is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
CONFIG_PARPORT_GSC=m
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# 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=y
CONFIG_BLK_DEV_NBD=m
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=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=m
CONFIG_MD_RAID5=m
# CONFIG_MD_MULTIPATH is not set
CONFIG_BLK_DEV_LVM=m

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=m
# CONFIG_NETFILTER is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
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_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

#
# SCSI support
#
CONFIG_SCSI=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
CONFIG_CHR_DEV_ST=m
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_SR_EXTRA_DEVS=2
CONFIG_CHR_DEV_SG=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_DEBUG_QUEUES is not set
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# 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_AHA1740 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA 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_INITIO 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_LASI700=y
CONFIG_53C700_MEM_MAPPED=y
CONFIG_53C700_LE_ON_BE=y
CONFIG_53C700_USE_CONSISTENT=y
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_ASK_ZALON is not set
# CONFIG_ASK_NCR53C8XX is not set
# CONFIG_ASK_SYM53C8XX is not set
# CONFIG_SCSI_ZALON is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

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

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_LASI_82596=y
# CONFIG_SUNLANCE is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE 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
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_PCI 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=m
# CONFIG_PPP_SYNC_TTY is not set
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
# CONFIG_PPPOE is not set
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
# 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

#
# 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_GSC_PS2 is not set
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
CONFIG_SERIAL_GSC=y
# CONFIG_HP_DIVA is not set
# 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=y
CONFIG_WATCHDOG_NOWAYOUT=y
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_PCWATCHDOG is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I810_TCO is not set
# CONFIG_MIXCOMWD is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_SCx200_WDT is not set
CONFIG_SOFT_WATCHDOG=m
# CONFIG_W83877F_WDT is not set
# CONFIG_WDT is not set
# CONFIG_WDTPCI is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_AMD7XX_TCO is not set
# CONFIG_GEN_RTC is not set
# CONFIG_SCx200_GPIO is not set
# CONFIG_AMD_PM768 is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

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

#
# HIL support
#

#
# Input support needed for HIL support
#

#
# 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 is not set
CONFIG_REISERFS_FS=y
# 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=y
# CONFIG_JFS_FS is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_MINIX_FS=m
# 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=m
CONFIG_INTERMEZZO_FS=m
CONFIG_NFS_FS=m
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=m
CONFIG_LOCKD=m
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=m

#
# 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="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# 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=m

#
# Console drivers
#

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

#
# Sound
#
# CONFIG_SOUND is not set

#
# Kernel hacking
#
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=m
CONFIG_ZLIB_DEFLATE=m

[-- Attachment #3: dmesg --]
[-- Type: TEXT/PLAIN, Size: 9183 bytes --]

Linux version 2.4.22-pa17 (root@brain) (gcc version 3.0.4) #1 Sat Nov 15 23:25:26 AST 2003
FP[0] enabled: Rev 1 Model 13
The 32-bit Kernel has started...
Determining PDC firmware type: Snake.
model 000060c0 00000481 00000000 00000000 77566b4e 00000000 00000004 00000072 00000072
vers  0000000c
model 9000/715
Total Memory: 256 Mb
pagetable_init
On node 0 totalpages: 65536
zone(0): 65536 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 palo_kernel=2/vmlinux
Calibrating delay loop... 99.73 BogoMIPS
Memory: 256804k available
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
Searching for devices...
Found devices:
1. Mirage 100+ GSC Builtin Graphics (10) at 0xf8000000 [1], versions 0x11, 0x0, 0x85
2. Mirage 100+ Core BA (11) at 0xf0100000 [2], versions 0x2c, 0x0, 0x81
3. Mirage 100+ Core SCSI (10) at 0xf0106000 [2/0/1], versions 0x2c, 0x0, 0x82
4. Mirage 100+ Core LAN (802.3) (10) at 0xf0107000 [2/0/2], versions 0x2c, 0x0, 0x8a
5. Mirage 100+ Core RS-232 (10) at 0xf0105000 [2/0/4], versions 0x2c, 0x0, 0x8c
6. Mirage 100+ Core Centronics (10) at 0xf0102000 [2/0/6], versions 0x2c, 0x0, 0x74
7. Mirage 100+ Audio (10) at 0xf0104000 [2/0/8], versions 0x2c, 0x0, 0x7b
8. Mirage 100+ Core PC Floppy (10) at 0xf010a000 [2/0/10], versions 0x2c, 0x0, 0x83
9. Mirage 100+ Core PS/2 Port (10) at 0xf0108000 [2/0/11], versions 0x2c, 0x0, 0x84
10. Mirage 100+ Core PS/2 Port (10) at 0xf0108100 [2/0/12], versions 0x2c, 0x0, 0x84
11. Mirage 100+ Wax EISA BA (11) at 0xfc000000 [4], versions 0x2c, 0x0, 0x90
12. Mirage 100+ Wax BA (11) at 0xf0200000 [5], versions 0x2c, 0x0, 0x8e
13. Mirage 100+ Wax HIL (10) at 0xf0201000 [5/0/1], versions 0x2c, 0x0, 0x73
14. Gecko Core RS-232 (10) at 0xf0202000 [5/0/2], versions 0x16, 0x0, 0x8c
15. Mirage 100+ (0) at 0xfffbe000 [8], versions 0x60c, 0x0, 0x4
16. Memory (1) at 0xfffbf000 [9], versions 0x4c, 0x0, 0x9
CPU(s): 1 x PA7100LC (PCX-L) at 100.000000 MHz
Lasi version 0 at 0xf0100000 found.
LED display at f00e0000 registered
Wax at 0xf0200000 found.
Wax EISA Adapter found at 0xfc000000
EISA EEPROM at 0xf00c0400
Enumerating EISA bus
EISA slot 1 a configured board was not detected ( expected INT1060)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Gecko-style soft power switch enabled.
Starting kswapd
Journalled Block Device driver loaded
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with no serial options enabled
ttyS00 at iomem 0xf0105800 (irq = 90) is a 16550A
ttyS01 at iomem 0xf0202800 (irq = 121) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Found i82596 at 0xf0107000, IRQ 87
eth0: 82596 at 0xf0107000, 08 00 09 E4 7D 02 IRQ 87.
82596.c $Revision: 1.32 $
SCSI subsystem driver Revision: 1.00
53c700: Version 2.8 By James.Bottomley@HansenPartnership.com
scsi0: 53c710 rev 2 
scsi0 : LASI SCSI 53c700
scsi0: (1:0) Synchronous at offset 8, period 100ns
  Vendor: SEAGATE   Model: ST15150N          Rev: 9107
  Type:   Direct-Access                      ANSI SCSI revision: 02
scsi0: (6:0) Synchronous at offset 8, period 100ns
  Vendor: QUANTUM   Model: FIREBALL-ST2      Rev: HP0J
  Type:   Direct-Access                      ANSI SCSI revision: 02
Attached scsi disk sda at scsi0, channel 0, id 1, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 6, lun 0
scsi0: (1:0) Enabling Tag Command Queuing
SCSI device sda: 8388315 512-byte hdwr sectors (4295 MB)
Partition check:
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 >
scsi0: (6:0) Enabling Tag Command Queuing
SCSI device sdb: 4194685 512-byte hdwr sectors (2148 MB)
 sdb: sdb1 sdb2 sdb3 < sdb5 sdb6 sdb7 sdb8 sdb9 >
md: raid0 personality registered as nr 2
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 161k freed
Adding Swap: 132888k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,3), internal journal
parport_init_chip: initialize bidirectional-mode.
parport0: PC-style at 0xf0102800, irq 88 [PCSPP,TRISTATE]
 [events: 00000040]
md: bind<sdb6,1>
 [events: 00000040]
md: bind<sda7,2>
md: sda7's event counter: 00000040
md: sdb6's event counter: 00000040
md0: max total readahead window set to 512k
md0: 2 data-disks, max readahead per data-disk: 256k
raid0: looking at sda7
raid0:   comparing sda7(206016) with sda7(206016)
raid0:   END
raid0:   ==> UNIQUE
raid0: 1 zones
raid0: looking at sdb6
raid0:   comparing sdb6(205504) with sda7(206016)
raid0:   NOT EQUAL
raid0:   comparing sdb6(205504) with sdb6(205504)
raid0:   END
raid0:   ==> UNIQUE
raid0: 2 zones
raid0: FINAL 2 zones
raid0: zone 0
raid0: checking sda7 ... contained as device 0
  (206016) is smallest!.
raid0: checking sdb6 ... contained as device 1
  (205504) is smallest!.
raid0: zone->nb_dev: 2, size: 411008
raid0: current zone offset: 205504
raid0: zone 1
raid0: checking sda7 ... contained as device 0
  (206016) is smallest!.
raid0: checking sdb6 ... nope.
raid0: zone->nb_dev: 1, size: 512
raid0: current zone offset: 206016
raid0: done.
raid0 : md_size is 411520 blocks.
raid0 : conf->smallest->size is 512 blocks.
raid0 : nb_zone is 804.
raid0 : Allocating 6432 bytes for hash.
md: updating md0 RAID superblock on device
md: sda7 [events: 00000041]<6>(write) sda7's sb offset: 206016
md: sdb6 [events: 00000041]<6>(write) sdb6's sb offset: 205504
 [events: 0000002a]
md: bind<sdb7,1>
 [events: 0000002a]
md: bind<sda8,2>
md: sda8's event counter: 0000002a
md: sdb7's event counter: 0000002a
md1: max total readahead window set to 496k
md1: 2 data-disks, max readahead per data-disk: 248k
raid0: looking at sda8
raid0:   comparing sda8(206016) with sda8(206016)
raid0:   END
raid0:   ==> UNIQUE
raid0: 1 zones
raid0: looking at sdb7
raid0:   comparing sdb7(205504) with sda8(206016)
raid0:   NOT EQUAL
raid0:   comparing sdb7(205504) with sdb7(205504)
raid0:   END
raid0:   ==> UNIQUE
raid0: 2 zones
raid0: FINAL 2 zones
raid0: zone 0
raid0: checking sda8 ... contained as device 0
  (206016) is smallest!.
raid0: checking sdb7 ... contained as device 1
  (205504) is smallest!.
raid0: zone->nb_dev: 2, size: 411008
raid0: current zone offset: 205504
raid0: zone 1
raid0: checking sda8 ... contained as device 0
  (206016) is smallest!.
raid0: checking sdb7 ... nope.
raid0: zone->nb_dev: 1, size: 512
raid0: current zone offset: 206016
raid0: done.
raid0 : md_size is 411520 blocks.
raid0 : conf->smallest->size is 512 blocks.
raid0 : nb_zone is 804.
raid0 : Allocating 6432 bytes for hash.
md: updating md1 RAID superblock on device
md: sda8 [events: 0000002b]<6>(write) sda8's sb offset: 206016
md: sdb7 [events: 0000002b]<6>(write) sdb7's sb offset: 205504
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device sd(8,18)) ...
for (sd(8,18))
sd(8,18):Using r5 hash to sort names
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device sd(8,5)) ...
for (sd(8,5))
reiserfs: replayed 1 transactions in 0 seconds
sd(8,5):Using r5 hash to sort names
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device sd(8,24)) ...
for (sd(8,24))
reiserfs: replayed 16 transactions in 1 seconds
sd(8,24):Using r5 hash to sort names
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device sd(8,6)) ...
for (sd(8,6))
sd(8,6):Using r5 hash to sort names
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device md(9,0)) ...
for (md(9,0))
reiserfs: replayed 1 transactions in 1 seconds
md(9,0):Using r5 hash to sort names
md(9,0):Removing [2 9 0x0 SD]..done
md(9,0):Removing [2 8 0x0 SD]..done
md(9,0):There were 2 uncompleted unlinks/truncates. Completed
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device md(9,1)) ...
for (md(9,1))
md(9,1):Using r5 hash to sort names
eth0: link ok.
lp0: using parport0 (interrupt-driven).
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).

[-- Attachment #4: cpuinfo --]
[-- Type: TEXT/PLAIN, Size: 486 bytes --]

processor	: 0
cpu family	: PA-RISC 1.1d
cpu		: PA7100LC (PCX-L)
cpu MHz		: 100.000000
model		: 9000/715
model name	: Mirage 100+
hversion	: 0x000060c0
sversion	: 0x00000481
I-cache		: 512 KB
D-cache		: 512 KB (WB)
ITLB entries	: 64
DTLB entries	: 64 - shared with ITLB
BTLB fixed	: max. 16384 pages, pagesize=4096 (64MB)
BTLB fix-entr.	: 0 instruction, 0 data (8 combined)
BTLB var-entr.	: 0 instruction, 0 data (0 combined)
bogomips	: 99.73
software id	: 2002152270

RE: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17

[Joel Soete]

Hi Steve,

The toc 'process' don't display anything (excepted may be on lcd). To see
'piminfo', you should interupt the boot and collect the 'piminfo' (iirc >
ser pim).

hth,
    Joel

PS: btw which glibc is installed on your system?

>-- Original Message --
>From: Steve Bromwich <lists@fop.ns.ca>
>To: parisc-linux@parisc-linux.org
>Date: Tue, 18 Nov 2003 10:24:56 -0400 (AST)
>Subject: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17
>
>
>Hi,

I installed 2.4.22-pa17 on my machine over the weekend, and I'm getting
processes stuck in D state. The machine usually runs for several hours
without any problem, but then processes start dying, apparently fairly
randomly, the load goes up, 
>nd vmstat shows CPU as near 100% idle. I
*think* it's something to do with writing to the drive, since one of the
first things to die is syslogging. Anything that doesn't touch the drive
(eg, IRC clients) seem to run forever. One thing that really k
>lls it
seems to be daily maintenance around 6am; I can see mail being delivered
until then, and after that it queues on my backup MX. The only way to get
the machine back is to pull the power - shutdown -r now hangs, presing the
power button gets s
>utdown started but still hangs, and the TOC doesn't
seem to produce any output on my serial console. I've only seen a process
die in ffront of me once, when I was exiting from a bash session; the
machine just sat there with no i/o, ps aux showed the
>bash session stuck
in D state, and I couldn't ctrl-c or ctrl-z out of it at all.

Prior to this I was running 2.4.18 with no problem with the machine
running for months at a time. Has anyone seen this problem and/or got any
tips on how to figure o
>t what's going wrong? I can't find any error
output anywhere that's hinting what could be wrong, so I'm really stuck on
this one.

I've attached my .config, dmesg and cpuinfo in case anyone can see
anything obvious. Thanks for any help!

Cheers,
>Steve
>
>Attachment: config_2422pa17
>
>
>Attachment: dmesg
>
>
>Attachment: cpuinfo
>


-------------------------------------------------------------------------
Tiscali ADSL: 3 mois GRATUITS! L'Internet rapide, c'est pour tout le monde.

http://reg.tiscali.be/default.asp?lg=fr

RE: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17

[Steve Bromwich]

Hi Joel,

Just to clarify, this is happening during operation, not bootup. Next time
it happens (probably tomorrow morning) I'll break on serial and try
piminfo - is there anything else useful in there that might be worth
looking at?

I'm using Debian stable, with the 2.2.5-11.5 libc package installed.

Cheers, Steve

On Tue, 18 Nov 2003, Joel Soete wrote:

> Hi Steve,
>
> The toc 'process' don't display anything (excepted may be on lcd). To see
> 'piminfo', you should interupt the boot and collect the 'piminfo' (iirc >
> ser pim).
>
> hth,
>     Joel
>
> PS: btw which glibc is installed on your system?

RE: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17

[Joel Soete]

>-- Original Message --
>From: Steve Bromwich <lists@fop.ns.ca>
>To: Joel Soete <soete.joel@tiscali.be>
>Cc: parisc-linux@parisc-linux.org
>Date: Tue, 18 Nov 2003 14:34:49 -0400 (AST)
>Subject: RE: [parisc-linux] Processes stuck in D state on 715/100XC with
> 2.4.22-pa17
>
>
>Hi Joel,
>
>Just to clarify, this is happening during operation, not bootup. Next time
>it happens (probably tomorrow morning) I'll break on serial and try
>piminfo - is there anything else useful in there that might be worth
>looking at?
>
May be if you can, run hp diag tools?

(I have no clue about 715 model but well running 2.4.22 (and above) on various
b180, b2k, c110, N4000 and i have never encounter such pb?)

>I'm using Debian stable, with the 2.2.5-11.5 libc package installed.

Hmm, may be Carlos could help here, I know that glibc 2.3 need a kernel >
2.4.18  iirc but what is about a kernel 2.4.22? (does 2.4.22 need then glibc
2.3 for user space prgm operate correctly?)

Joel

-------------------------------------------------------------------------
Tiscali ADSL: 3 mois GRATUITS! L'Internet rapide, c'est pour tout le monde.

http://reg.tiscali.be/default.asp?lg=fr

Re: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17

[Matthew Wilcox]

On Wed, Nov 19, 2003 at 09:21:29AM +0100, Joel Soete wrote:
> Hmm, may be Carlos could help here, I know that glibc 2.3 need a kernel >
> 2.4.18  iirc but what is about a kernel 2.4.22? (does 2.4.22 need then glibc
> 2.3 for user space prgm operate correctly?)

No.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

RE: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17

[Steve Bromwich]

> >Just to clarify, this is happening during operation, not bootup. Next time
> >it happens (probably tomorrow morning) I'll break on serial and try
> >piminfo

So much for that idea - I forgot I had magic sysrq on, so break just gave
me the usual sysrq options. I'll recompile without sysrq over the weekend
and see what happens, but in the meantime I've reverted to 2.4.18 to see
if I get the same problem, just to make sure it's not faulty hardware. I
checked ps, and all the processes in D state were ones that touch the
drive (eg, find, exim, apache).

I've got a J class at work that's not in production, so if I get time I'll
try it out with the same config (or at least, the closest I can get) just
to make sure it's not something obviously wonky in my config.

> May be if you can, run hp diag tools?

I don't have a CD in that machine - do you know if there's any netbootable
images I can use? I have an HPUX 11.0 CD set, so if there's something I
can pull off there I'll be good to go.

> (I have no clue about 715 model but well running 2.4.22 (and above) on various
> b180, b2k, c110, N4000 and i have never encounter such pb?)

Well, the frustrating thing is is that there's no debug output anywhere
that I can find that's showing anything obviously wrong. I had a skim
through lasi700.c/.h and couldn't see anything that'd help, do you know if
there's any debug/printks I can scatter anywhere to give me some pointers?

Cheers, Steve

Re: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17

[Joel Soete]

Hi Steve,

Steve Bromwich wrote:
>>>Just to clarify, this is happening during operation, not bootup. Next time
>>>it happens (probably tomorrow morning) I'll break on serial and try
>>>piminfo
> 
> 
> So much for that idea - I forgot I had magic sysrq on, so break just gave
> me the usual sysrq options. I'll recompile without sysrq over the weekend
> and see what happens, but in the meantime I've reverted to 2.4.18 to see
> if I get the same problem, just to make sure it's not faulty hardware. I
> checked ps, and all the processes in D state were ones that touch the
> drive (eg, find, exim, apache).
> 
> I've got a J class at work that's not in production, so if I get time I'll
> try it out with the same config (or at least, the closest I can get) just
> to make sure it's not something obviously wonky in my config.
> 
well, but those system are widly different (cpu, architecture, ...).
> 
>>May be if you can, run hp diag tools?
> 
> 
> I don't have a CD in that machine - do you know if there's any netbootable
> images I can use? I have an HPUX 11.0 CD set, so if there's something I
> can pull off there I'll be good to go.
> 
Good question? never have to test it but it is a bootable cd (I don't 
remember if it is available via internet?) so if you copy it's image 
(with dd) on a system, i think that following the faq how-to netboot 
<http://parisc-linux.org/faq/index.html#netboot> , it would works?
> 
>>(I have no clue about 715 model but well running 2.4.22 (and above) on various
>>b180, b2k, c110, N4000 and i have never encounter such pb?)
> 
> 
> Well, the frustrating thing is is that there's no debug output anywhere
> that I can find that's showing anything obviously wrong.
Don't feel alone, during severall month (2, 3, 4, ... I don't want to 
remember) I try to get just a panic message from a smp kernel on a N4k 
: no success :_(
...

> I had a skim
> through lasi700.c/.h and couldn't see anything that'd help, do you know if
> there's any debug/printks I can scatter anywhere to give me some pointers?
>
Sorry, I couldn't help here.

hmm, what kind of disk have you on your D: hot-swapable or fixed?
(with fixed disk, I already encounter a pb of flat cable and with 
hot-swap disk a pb with dust on disks' support)

Cheers,
	Joel

Re: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17

[Steve Bromwich]

Hi Joel,

On Fri, 21 Nov 2003, Joel Soete wrote:

> Hi Steve,
>
> Steve Bromwich wrote:
> >
> > I've got a J class at work that's not in production...

> well, but those system are widly different (cpu, architecture, ...).

Well, my plan was something like this:

1. Install Linux on the J200, replicate my 715, and then compile the
kernel as closely as possible to how it is in the 715. Run the J200 like
that for a day or two and see if I can duplicate the problem. If so, diag
further on there.

2. If the problem does not appear on the J200, resync with the 715 and put
the J200 in place of the 715 while I tinker with the 715 to nail down the
problem. Then I should be able to regress through the kernels from cvs
until I find the one where it stopped working, and hopefully I should be
able to find a resolution from there.

Unfortunately, I was caught out right at the start - after lugging all 60
kilos of it home and downstairs into my basement server room, I discovered
that someone had borrowed the drives out of it, so I'll have to bring home
an enclosure next week to continue my testing.

In the meantime, I tried a net install which ultimately failed trying to
extract debs to the nfs root (which, incidentally, took about 5 minutes to
mount - is this to be expected on the install disks? It usually only takes
a couple of seconds for my 715 to mount an nfs partition off my
workstation). Unfortunately I was on serial console so couldn't get much
in the way of diags, I'll have to move a monitor into my server room to
hook up to it (the J200 doesn't like my 15" SVGA test monitor,
unfortunately).

> Good question? never have to test it but it is a bootable cd (I don't
> remember if it is available via internet?) so if you copy it's image
> (with dd) on a system, i think that following the faq how-to netboot
> <http://parisc-linux.org/faq/index.html#netboot> , it would works?

Hmmm... you mean like dd if=/dev/scd0 of=lifimage.testing? I guess that'll
be my next try :-)

> > Well, the frustrating thing is is that there's no debug output anywhere
> > that I can find that's showing anything obviously wrong.
> Don't feel alone, during severall month (2, 3, 4, ... I don't want to
> remember) I try to get just a panic message from a smp kernel on a N4k
> : no success :_(

Ah well... misery loves company, I guess! :-)

> hmm, what kind of disk have you on your D: hot-swapable or fixed?
> (with fixed disk, I already encounter a pb of flat cable and with
> hot-swap disk a pb with dust on disks' support)

Fixed. I don't *think* it's a problem with the cable, since (a) I reseated
all the cables after the first couple of times it died, and (b) after the
last time it reset, I rebooted back to 2.4.18 to make sure it wasn't a
flat-out hardware error (as opposed to possibly a hardware bug being
tickled by 2.4.22).

Thanks for the help :-)

Cheers, Steve

Re: [parisc-linux] Processes stuck in D state on 715/100XC with 2.4.22-pa17

[Michael Wood]

Hi

Been going through old mail and saw this thread.

One thing I noticed that the others did not seem to is that you seem to
be under the impression that the TOC and "ser pim" thing have to be done
while the machine is having the problem.  I have never used the TOC
button or "ser pim" before, but I believe how it works is that when the
machine is running (or when you press the TOC button or something) it
writes stuff to some sort of flash area.  The next time you boot, you
can interrupt the boot sequence and type "ser pim" and get the debugging
output.

I hope that helps.

-- 
Michael Wood <mwood@its.uct.ac.za>