Hi,
I am facing aic7xxx driver initialization failure over a kdump reboot.
kdump is basically kexec based crash dumping mechanism.
I get a stack dump and kernel booting operation simply hangs. Pasted
below are relevant details. Any idea what might be going wrong??
In my machine Adaptec SCSI controller is not managing any devices. It is
a lonely controller.
Thanks
Vivek
TEST KERNEL:
------------
2.6.10-mm1
Machine Configuration:
----------------------
Intel(R) Xeon(TM) CPU 2.40GHz, SMT, 2 logical cpus.
lspci output:
00:00.0 Host bridge: ServerWorks CMIC-LE (rev 13)
00:00.1 Host bridge: ServerWorks CMIC-LE
00:00.2 Host bridge: ServerWorks: Unknown device 0000
00:01.0 Bridge: IBM Remote Supervisor Adapter (RSA)
00:09.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:0f.0 Host bridge: ServerWorks CSB5 South Bridge (rev 93)
00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93)
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev
05)
00:0f.3 ISA bridge: ServerWorks GCLE Host Bridge
00:10.0 Host bridge: ServerWorks: Unknown device 0101 (rev 05)
00:10.2 Host bridge: ServerWorks: Unknown device 0101 (rev 05)
00:11.0 Host bridge: ServerWorks: Unknown device 0101 (rev 05)
00:11.2 Host bridge: ServerWorks: Unknown device 0101 (rev 05)
02:01.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 0c)
02:02.0 Ethernet controller: Intel Corp.: Unknown device 1079 (rev 03)
02:02.1 Ethernet controller: Intel Corp.: Unknown device 1079 (rev 03)
02:08.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703
Gigabit Ethernet (rev 02)
05:03.0 Ethernet controller: Intel Corp.: Unknown device 1079 (rev 03)
05:03.1 Ethernet controller: Intel Corp.: Unknown device 1079 (rev 03)
05:07.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 (rev
07)
05:07.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 (rev
07)
07:05.0 SCSI storage controller: Adaptec AIC-7892A U160/m (rev 02)
09:06.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
Kernel Boot Message:
--------------------
<0>kexec: opening parachute
Linux version 2.6.10-mm1 ([email protected]) (gcc version 3.2.2
20030222 (Re
d Hat Linux 3.2.2-5)) #4 SMP Tue Jan 4 20:15BIOS-provided physical RAM
map:
BIOS-e820: 0000000000000000 - 000000000009d400 (usable)
BIOS-e820: 000000000009d400 - 00000000000a0000 (reserved)
BIOS-e820: 0000000000100000 - 00000000effe7f80 (usable)
BIOS-e820: 00000000effe7f80 - 00000000effef800 (ACPI data)
BIOS-e820: 00000000effef800 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Warning only 896MB will be used.
Use a HIGHMEM enabled kernel.
user-defined physical RAM map:
user: 0000000000000000 - 00000000000a0000 (usable)
user: 0000000001000000 - 0000000003000000 (usable)
ignoring highmem size on non-highmem kernel!
48MB LOWMEM available.
DMI 2.3 present.
__iounmap: bad address c00f0000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
Processor #6 15:2 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
Built 1 zonelists
Found and enabled local APIC!
Initializing CPU#0
Kernel command line: root=/dev/sda5 dump init 1 memmap=exactmap
memmap=640k@0 memmap=32M@16M console=tty0 console=ttyS0,384lkernel
profiling enabled (shift: 0)
using polling idle threads.
PID hash table entries: 256 (order: 8, 4096 bytes)
Detected 2396.667 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 18404k/49152k available (2557k kernel code, 14936k reserved,
999k data, 204k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Hyper-Threading is disabled
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
CPU0: Intel(R) Xeon(TM) CPU 2.40GHz stepping 07
per-CPU timeslice cutoff: 1462.95 usecs.
task migration cache decay timeout: 2 msecs.
Booting processor 1/6 eip 2000
Initializing CPU#1
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Hyper-Threading is disabled
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel P4/Xeon Extended MCE MSRs (12) available
CPU1: Intel(R) Xeon(TM) CPU 2.40GHz stepping 07
Total of 2 processors activated (9486.33 BogoMIPS).
checking TSC synchronization across 2 CPUs: passed.
Brought up 2 CPUs
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfd7cc, last bus=10
PCI: Using configuration type 1
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
PCI: Discovered peer bus 02
PCI: Discovered peer bus 05
PCI: Discovered peer bus 07
PCI: Discovered peer bus 09
Installing knfsd (copyright (C) 1996 [email protected]).
Initializing Cryptographic API
Real Time Clock Driver v1.12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing
disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
elevator: using anticipatory as default io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
e100: Intel(R) PRO/100 Network Driver, 3.2.3-k2-NAPI
e100: Copyright(c) 1999-2004 Intel Corporation
e100: eth0: e100_probe: addr 0xfbfff000, irq 10, MAC addr
00:03:47:E0:67:78
e100: eth1: e100_probe: addr 0xf53ff000, irq 11, MAC addr
00:02:55:50:04:D6
tg3.c:v3.14 (November 15, 2004)
eth2: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCI:33MHz:64-bit)
10/100/1000BaseT Ethernet 00:09:6b:25:58:a1
eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[1]
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
hda: LTN486S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: ATAPI 48X CD-ROM drive, 120kB Cache
Uniform CD-ROM driver Revision: 3.20
PCI: Enabling device 0000:07:05.0 (0156 -> 0157)
irq 9: nobody cared!
[<c10360aa>] __report_bad_irq+0x2a/0xa0
[<c1035960>] handle_IRQ_event+0x30/0x70
[<c10361b0>] note_interrupt+0x70/0xb0
[<c1035ad1>] __do_IRQ+0x131/0x140
[<c1004c79>] do_IRQ+0x19/0x30
[<c10031f2>] common_interrupt+0x1a/0x20
[<c101ddab>] __do_softirq+0x4b/0xe0
[<c101de6d>] do_softirq+0x2d/0x30
[<c1004c7e>] do_IRQ+0x1e/0x30
[<c10031f2>] common_interrupt+0x1a/0x20
[<c127e2f7>] _spin_unlock_irqrestore+0x17/0x20
[<c1035da1>] setup_irq+0xa1/0x100
[<c11d8ef0>] ahc_linux_isr+0x0/0x2a0
[<c1036057>] request_irq+0x97/0xc0
[<c11dc19b>] ahc_pci_map_int+0x3b/0x70
[<c11d8ef0>] ahc_linux_isr+0x0/0x2a0
[<c11d09aa>] ahc_pci_config+0x6fa/0x9e0
[<c1153c0b>] pci_set_master+0x4b/0x80
[<c11dbd83>] ahc_linux_pci_dev_probe+0x153/0x1b0
[<c114ccff>] kobject_hotplug+0x2af/0x300
[<c11554e2>] pci_device_probe_static+0x52/0x70
[<c115553c>] __pci_device_probe+0x3c/0x50
[<c115557c>] pci_device_probe+0x2c/0x50
[<c117192f>] driver_probe_device+0x2f/0x80
[<c1171a7c>] driver_attach+0x5c/0x90
[<c1171ff2>] bus_add_driver+0xb2/0xe0
[<c1155824>] pci_register_driver+0x84/0xb0
[<c11dbdef>] ahc_linux_pci_init+0xf/0x20
[<c11d4749>] ahc_linux_detect+0x39/0x90
[<c139824f>] ahc_linux_init+0xf/0x30
[<c137ca2b>] do_initcalls+0x2b/0xc0
[<c1399d54>] sock_init+0x44/0x50
[<c10003c4>] init+0xb4/0x190
[<c1000310>] init+0x0/0x190
[<c10009e5>] kernel_thread_helper+0x5/0x10
handlers:
[<c11d8ef0>] (ahc_linux_isr+0x0/0x2a0)
Disabling IRQ #9
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec 29160B Ultra160 SCSI adapter>
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
SYSTEM HANGS AFTER THIS.
CONFIGURATION FILE:
-------------------
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.10-mm1
# Wed Jan 5 01:00:17 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_LOCK_KERNEL=y
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=15
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
# CONFIG_IKCONFIG_PROC is not set
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CPUSETS is not set
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM 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=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=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
# 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_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
CONFIG_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON 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_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
CONFIG_SMP=y
CONFIG_NR_CPUS=8
# CONFIG_SCHED_SMT is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_X86_MCE_P4THERMAL is not set
# 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
#
# Firmware Drivers
#
# 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 is not set
CONFIG_IRQBALANCE=y
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set
#
# Performance-monitoring counters support
#
# CONFIG_PERFCTR is not set
CONFIG_KERN_PHYS_OFFSET=16
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_BACKUP_BASE=16
CONFIG_BACKUP_SIZE=32
#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_BLACKLIST_YEAR=0
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_TABLE is not set
#
# CPUFreq processor drivers
#
# CONFIG_X86_GX_SUSPMOD is not set
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
#
# shared options
#
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_MSI is not set
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_HOTPLUG_CPU is not set
#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set
#
# PC-card bridges
#
CONFIG_PCMCIA_PROBE=y
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
# CONFIG_PNP is not set
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD 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=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_LBD=y
# CONFIG_CDROM_PKTCDVD is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=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_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED 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_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# 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_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
#
# SCSI low-level drivers
#
CONFIG_BLK_DEV_3W_XXXX_RAID=y
# CONFIG_SCSI_3W_9XXX 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 is not set
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=253
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA 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_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_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR 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 is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 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 is not set
#
# Fusion MPT device support
#
CONFIG_FUSION=y
CONFIG_FUSION_MAX_SGE=40
# CONFIG_FUSION_CTL is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# 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_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IP_TCPDIAG=y
# CONFIG_IP_TCPDIAG_IPV6 is not set
# CONFIG_IPV6 is not set
# CONFIG_NETFILTER is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET 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
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN 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
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# ARCnet devices
#
# CONFIG_ARCNET 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 is not set
# 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_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_TIGON3=y
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
#
# ISDN subsystem
#
# CONFIG_ISDN 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 is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD 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 is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA 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 is not set
# 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=y
# CONFIG_SERIAL_8250_MANY_PORTS is not set
# CONFIG_SERIAL_8250_SHARE_IRQ is not set
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_MULTIPORT is not set
# CONFIG_SERIAL_8250_RSA is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG 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 is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Misc devices
#
# CONFIG_IBM_ASM 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
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
# CONFIG_USB is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be
needed; see USB_STORAGE Help for more information
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# MMC/SD Card support
#
# CONFIG_MMC is not set
#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISER4_FS is not set
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
CONFIG_MINIX_FS=y
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
#
# Caches
#
# CONFIG_FSCACHE is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# 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_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_XATTR is not set
# 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_HFSPLUS_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=y
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_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_ASCII 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=y
CONFIG_OPROFILE=y
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_BUGVERBOSE is not set
CONFIG_DEBUG_INFO=y
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
# CONFIG_KGDB is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_TEST is not set
#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set
#
# Library routines
#
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC32 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
On Thu, 2005-01-06 at 18:05 +0530, Vivek Goyal wrote:
>
> In my machine Adaptec SCSI controller is not managing any devices. It
> is
> a lonely controller.
>
looks like the following is happening:
the controller wants to send an irq (probably from previous life)
then suddenly the driver gets loaded
* which registers an irq handler
* which does pci_enable_device()
and .. the irq goes through.
the irq handler just is not yet expecting this irq, so
returns "uh dunno not mine"
the kernel then decides to disable the irq on the apic level
and then the driver DOES need an irq during init
... which never happens.
Arjan van de Ven <[email protected]> wrote:
>
> On Thu, 2005-01-06 at 18:05 +0530, Vivek Goyal wrote:
> >
> > In my machine Adaptec SCSI controller is not managing any devices. It
> > is
> > a lonely controller.
> >
>
> looks like the following is happening:
> the controller wants to send an irq (probably from previous life)
> then suddenly the driver gets loaded
> * which registers an irq handler
> * which does pci_enable_device()
> and .. the irq goes through.
> the irq handler just is not yet expecting this irq, so
> returns "uh dunno not mine"
> the kernel then decides to disable the irq on the apic level
> and then the driver DOES need an irq during init
> ... which never happens.
>
yes, that's exactly what e100 was doing on my laptop last month. Fixed
that by arranging for the NIC to be reset before the call to
pci_set_master().
I expect the adaptec driver could be fixed by calling ahc_reset() from a
strategic place in either ahc_linux_pci_dev_probe() or in the shutdown
handler. (Does the crashdump code call shutdown handlers? Sounds like a
bad idea...)
Andrew Morton wrote:
>> looks like the following is happening:
>> the controller wants to send an irq (probably from previous life)
>> then suddenly the driver gets loaded
>> * which registers an irq handler
>> * which does pci_enable_device()
>> and .. the irq goes through.
>> the irq handler just is not yet expecting this irq, so
>> returns "uh dunno not mine"
>> the kernel then decides to disable the irq on the apic level
>> and then the driver DOES need an irq during init
>> ... which never happens.
>>
>
>
> yes, that's exactly what e100 was doing on my laptop last month. Fixed
> that by arranging for the NIC to be reset before the call to
> pci_set_master().
I noticed the exact same thing with a usb-uhci hub on a VIA MicroATX
board a month back. I rewrote the init sequence of the driver so that
it resets all of the hubs in the system first, and THEN registers their
interrupts.
This seems like a problem that CAN happen with level-triggered
interrupts. Us fixing it in individual drivers is not the solution; we
need a general solution.
I have an idea of something I might do for 2.6.11, but I doubt anyone
will actually agree with it. Say we keep a counter of how many times
interrupt x has been fired off since the last timer interrupt
(obviously, a timer interrupt resets the counter). Then we can pick an
arbitrary threshold for masking out this interrupt until another device
actually pines for it.
Or something. The point is, we need a general solution to the problem,
not poking about in every single driver trying to tie it down.
Luke Kosewski
Human Cannonball
Net Integration Technologies
On Thu, Jan 06, 2005 at 11:53:27PM -0500, Lukasz Kosewski wrote:
> I have an idea of something I might do for 2.6.11, but I doubt anyone
> will actually agree with it. Say we keep a counter of how many times
> interrupt x has been fired off since the last timer interrupt
> (obviously, a timer interrupt resets the counter). Then we can pick an
> arbitrary threshold for masking out this interrupt until another device
> actually pines for it.
>
> Or something. The point is, we need a general solution to the problem,
> not poking about in every single driver trying to tie it down.
Something like note_interrupt() in kernel/irq/spurious.c?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
Hi,
> yes, that's exactly what e100 was doing on my laptop last month. Fixed
> that by arranging for the NIC to be reset before the call to
> pci_set_master().
>
> I expect the adaptec driver could be fixed by calling ahc_reset() from a
> strategic place in either ahc_linux_pci_dev_probe() or in the shutdown
> handler.
> (Does the crashdump code call shutdown handlers? Sounds like a
> bad idea...)
>
No. Crash dump code does not call shutdown handlers...
Thanks
Vivek
Few questions/observations on this.
1. What can be the reason that a lonely SCSI storage controller will
continuously interrupt the cpu. Little different from network card.
2. In a normal boot, irq 24 is requested for aic7xxx. But over a kdump
boot, it is trying to request for irq 9. I have no idea if it is normal
behavior??
3. I changed following existing code a little to force ahc_reset() and i
get panic. May be called ahc_reset() at wrong place.
ahc_linux_pci_dev_probe()
{
.........
pci_enable_device();
pci_set_master();
............
ahc_pci_config() {
ahc_reset(ahc, FALSE);
}
}
I changed FALSE to TRUE, got following panic.
Oops: 0002 [#1]
SMP
Modules linked in:
CPU: 0
EIP: 0060:[<c0257163>] Not tainted VLI
EFLAGS: 00010246 (2.6.10-rc3-mm1-1M)
EIP is at ahc_chip_init+0x2e6/0xaa8
eax: 00000000 ebx: 00000000 ecx: 0000000f edx: f880402f
esi: 00000000 edi: 00000000 ebp: f7d61c00 esp: c5211df4
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=c5210000 task=c51e6a80)
Stack: f7d61c00 00000f00 00000100 00000100 ffffffe8 f7d61c00 000003e7
00000001
c025616e f7d61c00 00000000 00000000 00000000 f7d61c00 00000000
00000000
c025dacd f7d61c00 00000001 00000004 00000156 c5211e4f 40d61c00
00000001
Call Trace:
[<c025616e>] ahc_reset+0x269/0x3df
[<c025dacd>] ahc_pci_config+0x2a3/0x9f4
[<c01c78fa>] pci_set_master+0x4b/0x80
[<c026c82f>] ahc_linux_pci_dev_probe+0x155/0x1af
[<c01c9070>] pci_device_probe_static+0x52/0x61
[<c01c90ba>] __pci_device_probe+0x3b/0x4e
[<c01c90f9>] pci_device_probe+0x2c/0x4a
[<c01f7657>] driver_probe_device+0x2f/0x6e
[<c01f777d>] driver_attach+0x56/0x80
[<c01f7bf7>] bus_add_driver+0x99/0xc7
[<c01c934b>] pci_register_driver+0x72/0x90
[<c026c898>] ahc_linux_pci_init+0xf/0x1b
[<c0264148>] ahc_linux_detect+0x43/0x94
[<c040fd8c>] ahc_linux_init+0xf/0x23
[<c03f093d>] do_initcalls+0x28/0xb5
[<c0411f6c>] sock_init+0x40/0x4d
[<c01003a6>] init+0xab/0x185
[<c01002fb>] init+0x0/0x185
[<c010093d>] kernel_thread_helper+0x5/0xb
Code: 01 09 f0 89 44 24 04 e8 8d 15 00 00 83 fb 3f 7e e8 83 c7 01 83 44
24 0c 1
<0>Kernel panic - not syncing: Attempted to kill init!
Thanks
Vivek
On Fri, 2005-01-07 at 10:23, Lukasz Kosewski wrote:
> Andrew Morton wrote:
> >> looks like the following is happening:
> >> the controller wants to send an irq (probably from previous life)
> >> then suddenly the driver gets loaded
> >> * which registers an irq handler
> >> * which does pci_enable_device()
> >> and .. the irq goes through.
> >> the irq handler just is not yet expecting this irq, so
> >> returns "uh dunno not mine"
> >> the kernel then decides to disable the irq on the apic level
> >> and then the driver DOES need an irq during init
> >> ... which never happens.
> >>
> >
> >
> > yes, that's exactly what e100 was doing on my laptop last month. Fixed
> > that by arranging for the NIC to be reset before the call to
> > pci_set_master().
>
> I noticed the exact same thing with a usb-uhci hub on a VIA MicroATX
> board a month back. I rewrote the init sequence of the driver so that
> it resets all of the hubs in the system first, and THEN registers their
> interrupts.
>
> This seems like a problem that CAN happen with level-triggered
> interrupts. Us fixing it in individual drivers is not the solution; we
> need a general solution.
>
> I have an idea of something I might do for 2.6.11, but I doubt anyone
> will actually agree with it. Say we keep a counter of how many times
> interrupt x has been fired off since the last timer interrupt
> (obviously, a timer interrupt resets the counter). Then we can pick an
> arbitrary threshold for masking out this interrupt until another device
> actually pines for it.
>
> Or something. The point is, we need a general solution to the problem,
> not poking about in every single driver trying to tie it down.
>
> Luke Kosewski
> Human Cannonball
> Net Integration Technologies
>
Lukasz Kosewski wrote:
> Andrew Morton wrote:
>
>>> looks like the following is happening:
>>> the controller wants to send an irq (probably from previous life)
>>> then suddenly the driver gets loaded
>>> * which registers an irq handler
>>> * which does pci_enable_device()
>>> and .. the irq goes through. the irq handler just is not yet
>>> expecting this irq, so
>>> returns "uh dunno not mine"
>>> the kernel then decides to disable the irq on the apic level
>>> and then the driver DOES need an irq during init
>>> ... which never happens.
>>>
>>
>>
>> yes, that's exactly what e100 was doing on my laptop last month. Fixed
>> that by arranging for the NIC to be reset before the call to
>> pci_set_master().
After reading this again when I /wasn't/ semi-comatose, I retract my
statement insofar as it wouldn't help you (but I think it's still rather
necessary) :)
The system did exactly what I'm talking about (which it didn't do for
me, possibly because the board/processor didn't support APIC). I guess
my question to you is: do you have other devices sharing this
interrupt? In other words, are you /sure/ that it's the adaptec
controller which is setting the interrupt line high?
Luke Kosewski
Human Cannonball
Net Integration Technologies
On Fri, 7 Jan 2005, Lukasz Kosewski wrote:
> Lukasz Kosewski wrote:
>> Andrew Morton wrote:
>>
>>>> looks like the following is happening:
>>>> the controller wants to send an irq (probably from previous life)
>>>> then suddenly the driver gets loaded
>>>> * which registers an irq handler
>>>> * which does pci_enable_device()
>>>> and .. the irq goes through. the irq handler just is not yet expecting
>>>> this irq, so
>>>> returns "uh dunno not mine"
>>>> the kernel then decides to disable the irq on the apic level
>>>> and then the driver DOES need an irq during init
>>>> ... which never happens.
>>>>
>>>
>>>
>>> yes, that's exactly what e100 was doing on my laptop last month. Fixed
>>> that by arranging for the NIC to be reset before the call to
>>> pci_set_master().
>
> After reading this again when I /wasn't/ semi-comatose, I retract my
> statement insofar as it wouldn't help you (but I think it's still rather
> necessary) :)
>
> The system did exactly what I'm talking about (which it didn't do for me,
> possibly because the board/processor didn't support APIC). I guess my
> question to you is: do you have other devices sharing this interrupt? In
> other words, are you /sure/ that it's the adaptec controller which is setting
> the interrupt line high?
>
> Luke Kosewski
> Human Cannonball
> Net Integration Technologies
Note that Linux-2.6.10 PCI code will report the __wrong__ IRQ
unless pci_enable_device() is executed first! Hopefully, there
may be an additional callable procedure in the future that
sets up the IRQ routing independent of actually enabling the
device. In the meantime, enable the device before you believe
dev->irq.
Cheers,
Dick Johnson
Penguin : Linux version 2.6.10 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached for review by Dictator Bush.
98.36% of all statistics are fiction.
On Fri, 2005-01-07 at 20:20, linux-os wrote:
> On Fri, 7 Jan 2005, Lukasz Kosewski wrote:
>
> > Lukasz Kosewski wrote:
> >> Andrew Morton wrote:
> >>
> >>>> looks like the following is happening:
> >>>> the controller wants to send an irq (probably from previous life)
> >>>> then suddenly the driver gets loaded
> >>>> * which registers an irq handler
> >>>> * which does pci_enable_device()
> >>>> and .. the irq goes through. the irq handler just is not yet expecting
> >>>> this irq, so
> >>>> returns "uh dunno not mine"
> >>>> the kernel then decides to disable the irq on the apic level
> >>>> and then the driver DOES need an irq during init
> >>>> ... which never happens.
> >>>>
> >>>
> >>>
> >>> yes, that's exactly what e100 was doing on my laptop last month. Fixed
> >>> that by arranging for the NIC to be reset before the call to
> >>> pci_set_master().
> >
> > After reading this again when I /wasn't/ semi-comatose, I retract my
> > statement insofar as it wouldn't help you (but I think it's still rather
> > necessary) :)
> >
> > The system did exactly what I'm talking about (which it didn't do for me,
> > possibly because the board/processor didn't support APIC). I guess my
> > question to you is: do you have other devices sharing this interrupt? In
> > other words, are you /sure/ that it's the adaptec controller which is setting
> > the interrupt line high?
> >
> > Luke Kosewski
> > Human Cannonball
> > Net Integration Technologies
>
>
> Note that Linux-2.6.10 PCI code will report the __wrong__ IRQ
> unless pci_enable_device() is executed first! Hopefully, there
> may be an additional callable procedure in the future that
> sets up the IRQ routing independent of actually enabling the
> device. In the meantime, enable the device before you believe
> dev->irq.
pci_enable_device() has already executed by the time i check for what
irq line aic7xxx adapter is requesting for. So i hope that irq 9
information is right.
>
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.10 on an i686 machine (5537.79 BogoMips).
> Notice : All mail here is now cached for review by Dictator Bush.
> 98.36% of all statistics are fiction.
>
On Fri, 2005-01-07 at 20:25, Lukasz Kosewski wrote:
> Lukasz Kosewski wrote:
> > Andrew Morton wrote:
> >
> >>> looks like the following is happening:
> >>> the controller wants to send an irq (probably from previous life)
> >>> then suddenly the driver gets loaded
> >>> * which registers an irq handler
> >>> * which does pci_enable_device()
> >>> and .. the irq goes through. the irq handler just is not yet
> >>> expecting this irq, so
> >>> returns "uh dunno not mine"
> >>> the kernel then decides to disable the irq on the apic level
> >>> and then the driver DOES need an irq during init
> >>> ... which never happens.
> >>>
Well, in last 4-5 trials I did not see this problem. Everything is same
except we had just opened the box once to checkout few things.
Probably "noirqdebug" boot time parameter can be a stop gap solution
over a kdump boot, which will make sure irq is not disabled even if
unhandled interrupts are there. Assuming driver will be able to
initialize after this and hence undesired interrupt generation shall be
stopped.
> >>
> >>
> >> yes, that's exactly what e100 was doing on my laptop last month. Fixed
> >> that by arranging for the NIC to be reset before the call to
> >> pci_set_master().
>
> After reading this again when I /wasn't/ semi-comatose, I retract my
> statement insofar as it wouldn't help you (but I think it's still rather
> necessary) :)
>
> The system did exactly what I'm talking about (which it didn't do for
> me, possibly because the board/processor didn't support APIC). I guess
> my question to you is: do you have other devices sharing this
> interrupt? In other words, are you /sure/ that it's the adaptec
> controller which is setting the interrupt line high?
I am not sure about this. Following are two contradictory observations.
1. Remove the adaptec controller support and everything works fine. It
might mean that it was adapted controller only which was generating
spurious interrupts.
2. There are two more SCSI Controllers in the system and first one is
managing all the six hard disks in the system.
05:07.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 (rev
07)
05:07.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 (rev
07)
These also could be potential source of interrupts as after a successful
reboot with kdump, these also are sharing irq 9.
Following is a snapshot of /proc/interrupts over a kdump boot with
"noirqdebug"
CPU0 CPU1
0: 109474 0 XT-PIC timer
1: 8 0 XT-PIC i8042
2: 0 0 XT-PIC cascade
4: 385 0 XT-PIC serial
8: 1 0 XT-PIC rtc
9: 25588 0 XT-PIC aic7xxx, ioc0, ioc1
12: 100 0 XT-PIC i8042
14: 19 0 XT-PIC ide0
In normal boot, I don't see any other device connected to irq 9. (I am
not sure if this irq number can change over reboot)
Following is a snapshot of /proc/interrupts over a normal boot.
CPU0 CPU1
0: 95314 0 IO-APIC-edge timer
1: 9 0 IO-APIC-edge i8042
2: 0 0 XT-PIC cascade
4: 498 0 IO-APIC-edge serial
8: 2 0 IO-APIC-edge rtc
12: 100 0 IO-APIC-edge i8042
14: 20 0 IO-APIC-edge ide0
18: 1155 0 IO-APIC-level eth0
24: 30 0 IO-APIC-level aic7xxx
27: 1946 0 IO-APIC-level ioc0
28: 29 0 IO-APIC-level ioc1
NMI: 0 0
LOC: 94835 96567
ERR: 0
MIS: 0
Does that conclude anything that who is/was the potential source?
Vivek
On Friday 07 January 2005 06:53, Lukasz Kosewski wrote:
> Andrew Morton wrote:
> >> looks like the following is happening:
> >> the controller wants to send an irq (probably from previous life)
> >> then suddenly the driver gets loaded
> >> * which registers an irq handler
> >> * which does pci_enable_device()
> >> and .. the irq goes through.
> >> the irq handler just is not yet expecting this irq, so
> >> returns "uh dunno not mine"
> >> the kernel then decides to disable the irq on the apic level
> >> and then the driver DOES need an irq during init
> >> ... which never happens.
> >>
> >
> >
> > yes, that's exactly what e100 was doing on my laptop last month. Fixed
> > that by arranging for the NIC to be reset before the call to
> > pci_set_master().
>
> I noticed the exact same thing with a usb-uhci hub on a VIA MicroATX
> board a month back. I rewrote the init sequence of the driver so that
> it resets all of the hubs in the system first, and THEN registers their
> interrupts.
"Me too".
prism54 had similar bug long ago.
--
vda
On Fri, Jan 07, 2005 at 04:38:32AM +0000, Matthew Wilcox wrote:
> On Thu, Jan 06, 2005 at 11:53:27PM -0500, Lukasz Kosewski wrote:
> > I have an idea of something I might do for 2.6.11, but I doubt anyone
> > will actually agree with it. Say we keep a counter of how many times
> > interrupt x has been fired off since the last timer interrupt
> > (obviously, a timer interrupt resets the counter). Then we can pick an
> > arbitrary threshold for masking out this interrupt until another device
> > actually pines for it.
> >
> > Or something. The point is, we need a general solution to the problem,
> > not poking about in every single driver trying to tie it down.
>
> Something like note_interrupt() in kernel/irq/spurious.c?
BTW I wonder if its feasible to add an interface on top of kernel/irq/spurious.c for
notifying drivers about interrupts storms, so they can take appropriate action
(try to reset the device).
For example I've seen a 8390 based pcnet_cs driven (Linksys EtherFast 10/100+ + 56K Modem) PCMCIA
card go nuts and trigger infinite interrupt storms on custom PowerPC hardware under certain situations,
and resetting the device after a high limit of bogus interrupts "brought the hardware back", stabilizing
the system.
Would be nice to be able to change the current hardcoded nr-of-interrupt limits, and
have a notification mechanism.
Not sure if this kind of problem is common enough that adding a generic API
is worth it, though ?
On Sun, 2005-01-30 at 13:27 -0200, Marcelo Tosatti wrote:
> On Fri, Jan 07, 2005 at 04:38:32AM +0000, Matthew Wilcox wrote:
> > On Thu, Jan 06, 2005 at 11:53:27PM -0500, Lukasz Kosewski wrote:
> > > I have an idea of something I might do for 2.6.11, but I doubt anyone
> > > will actually agree with it. Say we keep a counter of how many times
> > > interrupt x has been fired off since the last timer interrupt
> > > (obviously, a timer interrupt resets the counter). Then we can pick an
> > > arbitrary threshold for masking out this interrupt until another device
> > > actually pines for it.
> > >
> > > Or something. The point is, we need a general solution to the problem,
> > > not poking about in every single driver trying to tie it down.
> >
> > Something like note_interrupt() in kernel/irq/spurious.c?
>
> BTW I wonder if its feasible to add an interface on top of kernel/irq/spurious.c for
> notifying drivers about interrupts storms, so they can take appropriate action
> (try to reset the device).
the problem is... the driver just denied it was their irq (at least in
all the common cases)...
On Sun, Jan 30, 2005 at 07:27:26PM +0100, Arjan van de Ven wrote:
> On Sun, 2005-01-30 at 13:27 -0200, Marcelo Tosatti wrote:
> > On Fri, Jan 07, 2005 at 04:38:32AM +0000, Matthew Wilcox wrote:
> > > On Thu, Jan 06, 2005 at 11:53:27PM -0500, Lukasz Kosewski wrote:
> > > > I have an idea of something I might do for 2.6.11, but I doubt anyone
> > > > will actually agree with it. Say we keep a counter of how many times
> > > > interrupt x has been fired off since the last timer interrupt
> > > > (obviously, a timer interrupt resets the counter). Then we can pick an
> > > > arbitrary threshold for masking out this interrupt until another device
> > > > actually pines for it.
> > > >
> > > > Or something. The point is, we need a general solution to the problem,
> > > > not poking about in every single driver trying to tie it down.
> > >
> > > Something like note_interrupt() in kernel/irq/spurious.c?
> >
> > BTW I wonder if its feasible to add an interface on top of kernel/irq/spurious.c for
> > notifying drivers about interrupts storms, so they can take appropriate action
> > (try to reset the device).
>
> the problem is... the driver just denied it was their irq (at least in
> all the common cases)...
Hum, drivers should, at least in theory, be able to return IRQ_NONE if interrupts
can't be handled.
So is 8390 a special case?
drivers/net/8390.c
irqreturn_t ei_interrupt(int irq, void *dev_id, struct pt_regs * regs)
{
...
}
spin_unlock(&ei_local->page_lock);
return IRQ_RETVAL(nr_serviced > 0);
}
The "workaround" looks like (at the end of ei_interrupt):
if (!nr_serviced)
interrupt_cnt++;
else
interrupt_cnt = 0;
if (interrupt_cnt > 256) {
ei_status.reset_8390(dev);
interrupt_cnt = 0;
}
One could argue that it is a hardware problem...