Ubuntu 5.10 installer crashes with kernel BUG on Adaptec AHA-2940U2/U2W controller

Bug #46420 reported by AleksanderAdamowski
12
Affects Status Importance Assigned to Milestone
base-installer (Ubuntu)
Invalid
Medium
Unassigned
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: base-installer

The machine in question doesn't have any IDE hard drives, onle an IDE CD-ROM drive and 3 SCSI drives connected to a
Adaptec AHA-2940U2/U2W in hardware RAID5 configuration.

Debian 3.1 has installed and runs fine on this machine.

When trying to install Ubuntu, the initial installer kernel panics with the following error:

[4294682.735000] SCSI subsystem initialized
[4294683.071000] scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
[4294683.071000] <Adaptec aic7890/91 Ultra2 SCSI adapter>
[4294683.071000] aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs
[4294683.071000]
[4294698.968000] Vendor: HP Model: C5683A Rev: C005
[4294699.052000] Type: Sequential-Access ANSI SCSI revision: 02
[4294699.150000] target0:0:3: Beginning Domain Validation
[4294699.258000] WIDTH IS 1
[4294699.292000] (scsi0:A:3): 6.600MB/s transfers (16bit)
[4294699.362000] target0:0:3: Domain Validation skipping write tests
[4294699.444000] (scsi0:A:3): 40.000MB/s transfers (20.000MHz, offset 32, 16bit)
[4294699.540000] target0:0:3: Ending Domain Validation
[4294699.802000] st: Version 20050312, fixed bufsize 32768, s/g segs 256
[4294700.005000] Attached scsi tape st0 at scsi0, channel 0, id 3, lun 0
[4294700.090000] st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575
     aic7xxx: loaded successfully
[4294703.416000] I2O subsystem v$Rev$
[4294703.461000] i2o: max drivers = 8
[4294703.535000] i2o: Checking for PCI I2O controllers...
[4294703.603000] i2o: I2O controller found on bus 0 at 81.
[4294703.671000] iop0: PCI I2O controller at E4000000 size=1048576
[4294703.750000] iop0: using write combining MTRR
[4294703.809000] iop0: MTRR workaround for Intel i960 processor
[4294703.884000] iop0: Installed at IRQ 10
[4294703.935000] iop0: Activating I2O controller...
[4294703.996000] iop0: This may take a few minutes if there are many devices
[4294705.437000] iop0: HRT has 1 entries of 16 bytes each.
[4294705.506000] Adapter 00000012: <7>TID 0000:[<7>H<7>P<7>C<7>*<7>]:<7>PCI 1: Bus 1 Device 22 Function 0<7>
[4294715.748000] iop0: Controller added
     i2o_core: loaded successfully
[4294716.376000] Loading Adaptec I2O RAID: Version 2.4 Build 5go
[4294716.452000] Detecting Adaptec I2O RAID controllers...
[4294716.520000] Adaptec I2O RAID controller 0 at e0b00000 size=100000 irq=10
[4294717.970000] ------------[ cut here ]------------
[4294717.970000] kernel BUG at <bad filename>:55433!
[4294717.970000] invalid operand: 0000 [#1]
[4294717.970000] Modules linked in: dpt_i2o i2o_core st aic7xxx scsi_transport_spi scsi_mod uhci_hcd usbcore piix ide_core evdev unix
[4294717.970000] CPU: 0
[4294717.970000] EIP: 0060:[<e0875bbf>] Not tainted VLI
[4294717.970000] EFLAGS: 00010206 (2.6.12-9-386)
[4294717.970000] EIP is at i2o_pci_interrupt+0x3e/0x88 [i2o_core]
[4294717.970000] eax: 1e8e0000 ebx: 1ec18000 ecx: df989aa0 edx: 1e8d0000
[4294717.970000] esi: def5b000 edi: 00000000 ebp: 0000000a esp: c0323f74
[4294717.970000] ds: 007b es: 007b ss: 0068
[4294717.970000] Process swapper (pid: 0, threadinfo=c0322000 task=c0299b80)
[4294717.970000] Stack: df989aa0 00000000 c012d95f 0000000a def5b000 c0323fbc c0323fbc c0319f80
[4294717.970000] 0000000a df989aa0 c0323fbc c012d9fe 00000000 00039100 c035e120 003b2007
[4294717.970000] c0104ca5 c01038b6 00000000 df6e5a20 c010101c 00039100 c035e120 003b2007
[4294717.970000] Call Trace:
[4294717.970000] [<c012d95f>] handle_IRQ_event+0x20/0x4c
[4294717.970000] [<c012d9fe>] __do_IRQ+0x73/0xb1
[4294717.970000] [<c0104ca5>] do_IRQ+0x19/0x24
[4294717.970000] [<c01038b6>] common_interrupt+0x1a/0x20
[4294717.970000] [<c010101c>] default_idle+0x0/0x29
[4294717.970000] [<c010103f>] default_idle+0x23/0x29
[4294717.970000] [<c01010a1>] cpu_idle+0x2d/0x42
[4294717.970000] [<c0324665>] start_kernel+0x176/0x178
[4294717.970000] Code: ff 75 12 f0 83 44 24 00 00 8b 46 44 8b 18 31 c0 83 fb ff 74 5d 8b 96 ac 00 00 00 39 d3 72 0c 89 d0 03 86 b0 00 00 00 39 c3 72 02 <0f> 0b 89 d8 29 d0 03 86 a8 00 00 00 50 53 56 e8 ea e5 ff ff 83
[4294717.970000] <0>Kernel panic - not syncing: Fatal exception in interrupt
[4294717.970000]

On the PCI bus, the controller is visible as this (output from lspci -vv):

0000:00:06.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891
        Subsystem: Adaptec 2940U2W SCSI Controller
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 40 (9750ns min, 6250ns max), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 5
        BIST result: 00
        Region 0: I/O ports at d000 [disabled] [size=256]
        Region 1: Memory at db800000 (64-bit, non-prefetchable) [size=4K]
        Expansion ROM at <unassigned> [disabled] [size=128K]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:0a.0 PCI bridge: Adaptec (formerly DPT) PCI Bridge (rev 02) (prog-if 00 [Normal decode])
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 40, Cache Line Size: 0x08 (32 bytes)
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=40
        BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
        Capabilities: [68] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:0a.1 I2O: Adaptec (formerly DPT) SmartRAID V Controller (rev 02) (prog-if 01)
        Subsystem: Adaptec (formerly DPT) 2000S Ultra3 Single Channel
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (250ns min, 250ns max), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 10
        BIST result: 00
        Region 0: Memory at e4000000 (32-bit, prefetchable) [size=32M]
        Expansion ROM at <unassigned> [disabled] [size=32K]
        Capabilities: [80] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Revision history for this message
AleksanderAdamowski (aadamowski) wrote : more detailed log from kernel bootup

This is a detailed log from Ubuntu installer, during the kernel bootup phase.

Extracted through serial console (I've booted from Ubuntu install cd with the command line: "server-expert console=0") on another machine, using "cu" utility from "uucp" package to connect with a null modem cable.

Revision history for this message
AleksanderAdamowski (aadamowski) wrote :

BTW, Ubuntu 6.06 RC installation CD works fine with this adapter, and uses I2O to support it.

Revision history for this message
AleksanderAdamowski (aadamowski) wrote :

However, Ubuntu 6.06 has a problem with device naming inconsistency between 2 kernel modules that support this adapter.

This causes the installed system to fail upon bootup in the initrd stage. See Bug #46420.

Both Ubuntu 5.10 installer and 6.06 instelled system seem to use the dpt_i2o module for this adapter, but the 6.06 installer uses a different module - i2o_block.

That module works fine, but it names the devices differently (i2o_block creates /dev/i2o/hda while dpt_i2o creates a /dev/sda device).

Revision history for this message
AleksanderAdamowski (aadamowski) wrote :

I think that this bug could be marked as confirmed, and IMHO it's severity should be risen.

Revision history for this message
AleksanderAdamowski (aadamowski) wrote :

Oops, I've meant "See bug #37639..."

#46420 is this bug.

My sillyness...

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report.

Changed in linux-source-2.6.15:
status: New → Incomplete
Changed in base-installer:
status: New → Incomplete
Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

We are closing this bug report (no response to previous request for expressions of interest in this report). To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-source-2.6.15:
status: Incomplete → Invalid
Changed in base-installer:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.