HP ProLiant DL360 G6 has debootstrap errors during install of Precise Alpha 1

[Brendan Donegan]

Trying to install Precise Pangolin Alpha 1 on this HP server, we get debootstrap errors part of the way through the installation. We've tried several times to rerun the install, with no success. This system runs Oneiric flawlessly, so need to consider this a regression.

[Brian Murray (brian-murray)]

It looks to me like there is an issue with the hard disk in this system:

Dec 21 13:54:54 kernel: [ 111.167248] sd 0:0:0:0: [sda] Unhandled error code
Dec 21 13:54:54 kernel: [ 111.167252] sd 0:0:0:0: [sda] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 21 13:54:54 kernel: [ 111.167256] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 06 84 08 00 00 00 08 00
Dec 21 13:54:54 kernel: [ 111.167265] end_request: I/O error, dev sda, sector 109316096
Dec 21 13:54:54 kernel: [ 111.167269] Buffer I/O error on device sda1, logical block 13664256

Could you investigate the health of the disk?

[Brendan Donegan (brendan-donegan)]

Yeah. that is certainly what it look like. I'll test it again with Oneiric (which we certified it for) to see what happens.

[Brendan Donegan (brendan-donegan)]

Ran with Oneiric and it installs perfectly fine and it running tests now. I think the disk is healthy and this is a driver problem.

[Joseph Salisbury (jsalisbury)]

@Brendan,

Would it be possible for you to test the latest upstream kernel? Available at:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc7-precise/

You should be able to install this kernel after booting into Oneiric.

Also, it would be helpful if you could gather some apport logs with:
apport-collect 907377

Thanks in advance

[Brian Murray (brian-murray)]

I opened a linux task since this seems to be a driver issue.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 907377

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Incomplete. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brendan Donegan (brendan-donegan)]

Joe,

If the problem is with the kernel in the installer, how am I supposed to test with the upstream kernel? Maybe there is a way, but I could do with some pointers.

[Joseph Salisbury (jsalisbury)]

Brendan,

I'm going to add this to the kernel team hot-list since it could be an issue with the current development kernel.

[Andy Whitcroft (apw)]

Can we confirm if this issue persists with the latest dalies please. Please report any testing back here.

[Brendan Donegan (brendan-donegan)]

This is still present in the latest dailies, same error.

[Colin Watson (cjwatson)]

The installer kernel is just the same as the normal kernel. Closing the debian-installer task, then - I can't do anything about this from the installer side.

[Tim Gardner (timg-tpi)]

This is where things start to go south: in the syslog attached to comment #3:

Dec 21 13:54:37 kernel: [ 94.417294] NMI: PCI system error (SERR) for reason b1 on CPU 0.
Dec 21 13:54:37 kernel: [ 94.417298] Dazed and confused, but trying to continue
Dec 21 13:54:37 kernel: [ 94.417305] DRHD: handling fault status reg 2
Dec 21 13:54:37 kernel: [ 94.417311] DMAR:[DMA Read] Request device [03:00.0] fault addr ffeec000
Dec 21 13:54:37 kernel: [ 94.417313] DMAR:[fault reason 06] PTE Read access is not set
Dec 21 13:54:54 kernel: [ 111.087385] hpsa 0000:03:00.0: Controller lockup detected: 0xffff0000
Dec 21 13:54:54 kernel: [ 111.087398] hpsa 0000:03:00.0: cp ffff88018ce00000 had hardware error
Dec 21 13:54:54 kernel: [ 111.127427] sd 0:0:0:0: [sda] Unhandled error code
Dec 21 13:54:54 kernel: [ 111.127431] sd 0:0:0:0: [sda] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 21 13:54:54 kernel: [ 111.127436] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 06 84 ef b8 00 00 d0 00
Dec 21 13:54:54 kernel: [ 111.127446] end_request: I/O error, dev sda, sector 109375416
Dec 21 13:54:54 kernel: [ 111.127556] Aborting journal on device sda1-8.
Dec 21 13:54:54 kernel: [ 111.127564] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4501: Journal has aborted
Dec 21 13:54:54 kernel: [ 111.127586] EXT4-fs error (device sda1) in ext4_init_inode_table:1195: Journal has aborted

[Andy Whitcroft (apw)]

DMAR errors, interesting. Can we try booting the installer kernel with the additional kernel command line option: intel_iommu=off

Please report any testing here. Ta.

[Brendan Donegan (brendan-donegan)]

intel_iommu=off worked a charm. What does that mean then?

[Leann Ogasawara (leannogasawara)]

I've commited a patch to disable CONFIG_INTEL_IOMMU_DEFAULT_ON. I plan to upload shortly. This should work around the install issue being seen here. I've also escalated this and similar intel_iommu issues upstream. Thanks.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 3.2.0-10.17

---------------
linux (3.2.0-10.17) precise; urgency=low

  [ Andy Whitcroft ]

  * Revert "SAUCE: overlayfs -- fs: limit filesystem stacking depth"
  * Revert "SAUCE: overlayfs -- overlay: overlay filesystem documentation"
  * Revert "SAUCE: overlayfs -- overlayfs: implement show_options"
  * Revert "SAUCE: overlayfs -- overlayfs: add statfs support"
  * Revert "SAUCE: overlayfs -- overlay filesystem"
  * Revert "SAUCE: overlayfs -- vfs: introduce clone_private_mount()"
  * Revert "SAUCE: overlayfs -- vfs: export do_splice_direct() to modules"
  * Revert "SAUCE: overlayfs -- vfs: add i_op->open()"
  * ensure debian/ is not excluded from git by default
  * add new scripting to handle buglinks in rebases
  * ubuntu: overlayfs -- overlayfs: add statfs support
  * ubuntu: overlayfs -- overlayfs: apply device cgroup and security
    permissions to overlay files
    - LP: #915941, #918212
    - CVE-2012-0055

  [ Erez Zadok ]

  * ubuntu: overlayfs -- overlayfs: implement show_options

  [ Leann Ogasawara ]

  * Revert "SAUCE: dmar: disable if ricoh multifunction detected"
  * [Config] Disable CONFIG_INTEL_IOMMU_DEFAULT_ON
    - LP: #907377, #911236
  * [Config] Enable CONFIG_IRQ_REMAP

  [ Miklos Szeredi ]

  * ubuntu: overlayfs -- vfs: pass struct path to __dentry_open()
  * ubuntu: overlayfs -- vfs: add i_op->open()
  * ubuntu: overlayfs -- vfs: export do_splice_direct() to modules
  * ubuntu: overlayfs -- vfs: introduce clone_private_mount()
  * ubuntu: overlayfs -- overlay filesystem
  * ubuntu: overlayfs -- fs: limit filesystem stacking depth

  [ Neil Brown ]

  * ubuntu: overlayfs -- overlay: overlay filesystem documentation

  [ Upstream Kernel Changes ]

  * (pre-stable) x86/PCI: amd: factor out MMCONFIG discovery
    - LP: #647043
  * (pre-stable) PNP: work around Dell 1536/1546 BIOS MMCONFIG bug that
    breaks USB
    - LP: #647043
 -- Leann Ogasawara <email address hidden> Mon, 16 Jan 2012 07:10:08 -0800