kernel fails to boot: pci: 0000:00:09.0: address space collision: [mem 0x00007800-0x000078ff] conflicts with reserved [mem 0x00000000-0x0000ffff] since 2.6.32-2.2

Bug #893269 reported by André Carvalho
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

When booting, the system hangs and not even REISUB-ing works, making a force shutdown the only way to turn off the laptop.

The problem seems to be an "address space collision":
[0.282266] pci: 0000:00:09.0: address space collision: [mem 0x00007800-0x000078ff] conflicts with reserved [mem 0x00000000-0x0000ffff]

(No logs available for this boot, apparently, so it had to be written by hand)

1) I am currently running Oneiric, but the problem started on Lucid;
2) I am currently running 2.6.31-23-generic-pae (Karmic).

Additional testing from other distributions (and Ubuntu itself):
1) Debian-testing kernels boot, but the nVidia drivers fail to compile for it (meaning X doesn't work);
2) Fedora 14 works fine, but 15 had some problems (it still booted);
3) ANY x86 Ubuntu derivative fails to boot if it was based on Lucid or later;
4) openSUSE works fine;
5) Any x64 package of the Kernel in Ubuntu works, but has wi-fi and sound problems (ndiswrapper is not an alternative since it crashes the kernel);
6) The problem starts on 2.6.32-2.2 x86 and is still replicable on today's builds of the Kernel on Ubuntu.
7) Karmic and older versions have no problems.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.20.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SIS966 [HDA SIS966], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andre 4009 F.... pulseaudio
 /dev/snd/pcmC0D0p: andre 4009 F...m pulseaudio
CRDA: Error: [Errno 2] Ficheiro ou directoria inexistente
Card0.Amixer.info:
 Card hw:0 'SIS966'/'HDA SIS966 at 0xd3200000 irq 18'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,15580802,00100101'
   Controls : 22
   Simple ctrls : 13
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: clevo M7X0SU
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=pt_PT:en
 PATH=(custom, no user)
 LANG=pt_PT.UTF-8
 LC_MESSAGES=pt_PT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-23-generic-pae root=UUID=a5b7e233-9e13-43cb-995a-d72e11a07eb0 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.31-23.75-generic-pae
RelatedPackageVersions:
 linux-restricted-modules-2.6.31-23-generic-pae N/A
 linux-backports-modules-2.6.31-23-generic-pae N/A
 linux-firmware 1.60
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: oneiric running-unity
Uname: Linux 2.6.31-23-generic-pae i686
UpgradeStatus: Upgraded to oneiric on 2011-11-09 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/07/0892
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.asset.tag: 1234567890
dmi.board.name: M7X0SU
dmi.board.vendor: clevo
dmi.board.version: Bottom
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: SiS
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/07/0892:svnclevo:pnM7X0SU:pvrRev.A1:rvnclevo:rnM7X0SU:rvrBottom:cvnSiS:ct1:cvrN/A:
dmi.product.name: M7X0SU
dmi.product.version: Rev. A1
dmi.sys.vendor: clevo

Revision history for this message
André Carvalho (andrecarvalhopt) wrote :
Revision history for this message
André Carvalho (andrecarvalhopt) wrote :
Revision history for this message
André Carvalho (andrecarvalhopt) wrote :
summary: kernel fails to boot: pci: 0000:00:09.0: address space collision: [mem
0x00007800-0x000078ff] conflicts with reserved [mem
- 0x00000000-0x0000ffff] since 2.6.32-2
+ 0x00000000-0x0000ffff] since 2.6.32-2.2
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 893269

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.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: karmic
Revision history for this message
André Carvalho (andrecarvalhopt) wrote : AcpiTables.txt

apport information

tags: added: apport-collected oneiric running-unity
description: updated
Revision history for this message
André Carvalho (andrecarvalhopt) wrote : AlsaDevices.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : AplayDevices.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : BootDmesg.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : CurrentDmesg.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : IwConfig.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : Lspci.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : Lsusb.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : PciMultimedia.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : ProcInterrupts.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : ProcModules.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : PulseSinks.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : PulseSources.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : UdevDb.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : UdevLog.txt

apport information

Revision history for this message
André Carvalho (andrecarvalhopt) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
André Carvalho (andrecarvalhopt) wrote :

Additional information added, but not from the buggy kernels (they dont' boot as posted before)

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Thanks in advance.

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Revision history for this message
André Carvalho (andrecarvalhopt) wrote :

It's in upstream (v3.2-rc2-oneiric). One thing is that with this particular kernel it stayed on the purple-ish screen, while 3.2.0.999 (In daily?) actually tried to show something (both with same boot flags as described in the Wiki).

Revision history for this message
André Carvalho (andrecarvalhopt) wrote :

Update: I tried again today with the same kernel and boot flags and this time it showed some actual text.

The error's still the same.

Also, I picked up some extra messages, don't know how relevant they can be:
(the actual error)
(netLabel)
(appArmor)
pnp: pnp ACPI disabled
PnP BIOS: scanning for PnP BIOS
PnP BIOS: found at 0xc00f8074
PnP BIOS: version 1.0, entry 0xf0000: 0xbc4d, dseg 0x400

That's the last messages before it hangs.

Revision history for this message
André Carvalho (andrecarvalhopt) wrote :

I talked to someone who is more into Ubuntu than me, and happens to have the exact same computer, and he told me I had to use the following combination of flags at boot:
acpi=force
noapic
nohz=off

With those, Oneiric boots fine, but that doesn't dismiss the fact it's still a regression from 2.6.31.

I also attach the dmesg log from this boot from a live usb of Oneiric with those flags. It may help.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
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.