[Bug 17897] New: 2.6.12-9-686 and SMP kernel and Ubuntu Live CD Panic During Boot with DPT/Adaptec I2O Controller - Cause: Loads both dpt_i20 and the i2o drivers.

Sun Oct 16 12:10:22 UTC 2005

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=17897
Ubuntu | kernel-package

           Summary: 2.6.12-9-686 and SMP kernel and Ubuntu Live CD Panic
                    During Boot with DPT/Adaptec I2O Controller - Cause:
                    Loads both dpt_i20 and the i2o drivers.
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: kernel-package
        AssignedTo: ben.collins at ubuntu.com
        ReportedBy: chris at csamuel.org
         QAContact: kernel-bugs at lists.ubuntu.com

Having successfully upgrade my laptop to the Breezy RC via apt-get from Hoary I
did the same with my desktop, a 2.4GHz Intel P4 with 1GB RAM and an Adaptec
2100S RAID card which is normally driven by the dpt_i2o driver, after the Breezy
release.

Rebooting after the upgrade I found the SMP version of 2.6.12-9-686 panic'd (see
end of report) whilst initialising my SCSI controller, Googling around seems to
show this this as being a known problem caused when you mistakenly load both the
dpt_i2o driver and the I2O subsystem, which is a Bad Thing(tm).

This same panic happens with the SMP, uniprocessor and KUbuntu Live CD!

See this posting to the Linux-SCSI list with a very similar panic to mine at:

http://www.spinics.net/lists/linux-scsi/msg02497.html

The response saying that you should never load them both is at:

http://www.spinics.net/lists/linux-scsi/msg02503.html

IMPORTANT: The I2O on linux FAQ says:

Note: One user have reported that moving from dpt_i2o to i2o_block has caused
lockups and kernel panics if he uses LVM and XFS on top of it. Other filesystems
on top of LVM and XFS directly on the partition worked fine.

I'm using XFS on LVM, so I'd much rather see dpt_i2o be used (as it was in
Hoary) than I2O!

After posting this I'm going to try and boot from a rescue CD and see if I can
rebuild the initrd to not use the I2O subsystem..

This is the most of the boot I can see and copy by hand using vga=773.

scsi0: Vendor: Adaptec  Model: 2100S      FW: 370F
   Vendor: ADAPTEC  Model: RAID-5    Rev: 370f
   Type: Direct-Access               ANSI SCSI revision: 02
I2O subsystem v$Rev$
i2o: max drivers = 8
i20: Checking for PCI I2O controllers...
ACPI: PCI Interrupt 0000:02:01.1[A] -> GSI 21 (level, low) -> IRQ 21
i2o: I2O controller found on bus 2 at 9.
iop0: PCI I2O controller at DC000000 size=1048576
iop0: isomg write combined MTRR
iop0: MTRR workaround for Intel i960 processor
iop0: Installed at IRQ 21
iop0: Activating I2O controller...
iop0: This may take a few minutes if there are many devices
Unable to handle kernel paging request at virtual address 8000002c
 printing eip:
f8a389ad3
*pde = 00000000
Oops: 0000 [#1]
Modules linked in: i20_core dpt_i2o scsi_mod ehci_hcd usbcore ide_disk ide_cd
cdrom ide_generic piix ide_core unix  fbcon tileblit font bitblit vesafb
cfbcopyarea cfbimgblt cfbfillrect softcursor capability commoncap
CPU:     0
EIP:     0060:[<f8a39ad3>]    Not tainted VLI
EFLAGS:  00010086   (2.6.12-9-686)
EIP is at adpt_isr+0xde/0x201 [dpt_i20]
eax: 80000000   ebx: f7910000   exc: 00000000   edx: f7879000
esi: f7879000   edi: c034ffa4   ebp: 37910000   esp: c034ff28
ds: 007b   es: 007b   ss: 0068
Process swapper (pid: 0, threadinfo=c034e000 task=c02cdb80)
Stack: 00000292 00000100 c0120d10 c034ff48 00000000 00000286 00000000 f7871ec0
       00000000 c034ffa4 00000015 c0136594 00000015 f7879000 c034ffa4 00000000
       f7871ec0 00000015 c034ace0 c034ffa4 c013666b 00000015 000f41ff f7d13de4
Call Trace:
 [<c0120d10>] process_timeout+0x0/0x9
 [<c0136594>] handle_IRQ_event+0x39/0x6d
 [<c013666b>] __do_IRQ+0xa3/0xfc
 [<c02940b9>] schedule+0x303/0x5a5
 [<c01051fd>] do_IRQ+0x19/0x24
 [<c010380e>] common_interrupt+0x1a/0x20
 [<c010101e>] default_idle+0x0/0x29
 [<c0101041>] default_idle+0x23/0x29
 [<c01010b2>] cpu_idle+0x3c/0x51
 [<c03507ab>] start_kernel+0x171/0x1ad
 [<c0350346>] unknown_bootoption+0x0/0x1da
Code: 00 40 89 44 24 18 74 10 8b 7b 0c 85 ff 74 09 b9 11 00 00 00 89 de f3 a5 8b
4c 24 18 85 c9 0f 88 a6 00 00 00 8b 43 0c 85 c0 74 0b <8b> 50 2c 85 d2 0f 85 f4
00 00 00 8b 54 24 34 8b 82 84 00 00 00
<0>Kernel panic - not syncing: Fatal exception in interrupt

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.