This bug was fixed in the package linux - 2.6.32-33.70
---
linux (2.6.32-33.70) lucid-proposed; urgency=low
[Steve Conklin]
* Release Tracking Bug
- LP: #807175
[ Upstream Kernel Changes ]
* Revert "x86: Flush TLB if PGD entry is changed in i386 PAE mode"
- LP: #805
** Tags added: verification-done-lucid
** Tags removed: verification-needed-lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/424142
Title:
Address Collision
To manage notifications about this bu
I've verified the kernel in -proposed includes the working fix for this
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/424142
Title:
Address Collision
To manage notifications about this bug
The verification period for this kernel will close soon, and we have not
received verification that the problem is resolved in Lucid. Please test
and post results to this bug or the fix will be reverted from the
release.
--
You received this bug notification because you are a member of Ubuntu
Bug
** Branch linked: lp:ubuntu/maverick-proposed/linux-mvl-dove
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/424142
Title:
Address Collision
To manage notifications about this bug go to:
https://bugs
** Branch linked: lp:ubuntu/lucid-proposed/linux-mvl-dove
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/424142
Title:
Address Collision
To manage notifications about this bug go to:
https://bugs.la
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag
'verification-needed-lucid' to 'verification-done-lucid'.
If verification is not done by one week from today, thi
** Changed in: linux (Ubuntu Lucid)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/424142
Title:
Address Collision
--
ubuntu-bugs mailing list
ubuntu-bug
Attaching SRU patch.
SRU Justification:
Impact: PCI devices may fail to work due to a resource allocation
failure. When this happens the kernel prints a "address space collision"
message.
Fix: Upstream commit 8c8def26bfaa704db67d515da3eb92cf26067548
Test case: Boot a kernel on an affected machi
I've tested the above Lucid packages and confirmed that it indeed fixes
the problem on two separate boxes and does not cause regressions on a
third that did not exhibit the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
This has long been fixed upstream, so setting the development task to
Fix Released. A test build for Lucid is available at
http://people.canonical.com/~sforshee/lp424142/2.6.32-32.62~lp424142v201105231936/
** Changed in: linux (Ubuntu Lucid)
Importance: Undecided => Medium
** Changed in: linu
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/424142
Title:
Address Collision
--
ubuntu-bugs mailing list
ubuntu-b
This patch from 2.6.33 help to me.
https://patchwork.kernel.org/patch/39988/
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index dbd0f94..89efbb5 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -367,8 +367,12 @@ pci_find_parent_resource(const struct pci_dev *dev,
struct resource
This message also appears with 2.6.32 kernels from Debian:
$ uname -a
Linux jophur 2.6.32-3-amd64 #1 SMP Thu Feb 25 07:33:41 UTC 2010 x86_64 GNU/Linux
$ dmesg | grep BAR
[0.212204] pci :05:04.0: BAR 6: address space collision on of device
[0xfeac-0xfead]
However, it has disappea
After more search on launchpad, I've found many other bug reports that
have been marked as duplicate of Bug #413419 because the message appear
during the boot process.
Bug #413419 has been marked as "fix released" because the message
doesn't appear anymore on the screen during the boot process fro
I've got the same message on dmesg.
My system can boot but it freezes/hangs frequently for many minutes before
coming back alive.
The message dosn't appear on the screen with the latest up to date Karmic
x86_64 (maybe due to usplash).
I try the latest kernel 2.6.32.2 from here :
http://kernel.u
This problem is not specific to Ubuntu. I am also seeing it with linux
2.6.31 on Debian:
$ dmesg | grep collision
[0.257209] pci :05:04.0: BAR 6: address space collision on of device
[0xfeac-0xfead]
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this b
I think this could be a symptom of a problem with 2.6.31 itself. I'm
using a custom kernel on Fedora 8 (x86_64) that's giving a conflict
between two PCI (32-bit) cards:
[0.828847] pci :02:07.0: BAR 6: address space collision on of device
[0xfbfa-0xfbfb]
[0.828929] pci :
The collision error occurs for both the kernels using kubuntu 9.10 AMD64
Desktop version on HP s3220n AMD5000+
BAR 6: address space collision on of device [0xfea0-0xfea1]
2.6.31-11-generic SMP AMD64
2.6.31-14-generic SMP AMD64
I see this in dmesg after every boot.
--
Address Collisio
I just installed a Karmic LTSP server on my Dell 1650 server and got
this error. The install went fine and even the first reboot worked
without a problem. But ever since then it just boots, throws this
error, and dumps to a Busybox shell.
BAR 6: address space collision on of device [0xfea0-0
I have this message during boot on Karmic. Also, today my system stops
booting half-way (right after doing fsck) and I am left with a bunch of
modem-manager messages on the screen. It does this about 9 of every 10
boot attempts. 1 of every 10 it manages to actually boot successfully.
Do you thin
Ah yes I do still have the message just not being shown at boot up:
$ dmesg | grep "BAR 6"
[2.185237] pci :04:05.0: BAR 6: address space collision on of device
[0xdbe0-0xdbe7]
$ uname -a
Linux -- 2.6.31-13-generic #44-Ubuntu SMP Sat Oct 10 15:27:14 UTC 2009
x86_64 GNU/Linux
Exactly Nick B, it is hidden by a new usplash.
Only emergency messages are shown from now on.
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
i have the same message on my packard Bell
but there is no probleme for the boot
** Attachment added: "bug.txt"
http://launchpadlibrarian.net/33416664/bug.txt
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Twig wrote:
> Are you certain it isn't hidden by the new boot process. I have the
> same kernel version yet if I do:
>
> t...@twig-desktop:~$ dmesg | grep BAR [0.140150] pci
> :02:03.0: BAR 6: address space collision on of device
> [0xfe8e000
But I notice that with the new kernel version, the boot time is longer
than with the other version
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Are you certain it isn't hidden by the new boot process. I have the same
kernel version yet if I do:
t...@twig-desktop:~$ dmesg | grep BAR
[0.140150] pci :02:03.0: BAR 6: address space collision on of device
[0xfe8e-0xfe8e]
I still get the same message.
--
Address Collision
htt
I no longer get this message after update...
$ uname -a
Linux -- 2.6.31-13-generic #43-Ubuntu SMP Fri Oct 9 17:41:46 UTC 2009
x86_64 GNU/Linux
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I get the same message and can't boot. :(
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
anything new about this bug???
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinf
Setting affected package as linux. Folks, please do not confirm a bug
without a package assigned.
** Package changed: ubuntu => linux (Ubuntu)
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Cannot boot beta 9.10 i386 on MSI Wind U100
This try froze part way into the boot.
Screen image attached.
** Attachment added: "MSI-Wind_U100"
http://launchpadlibrarian.net/33125972/MSI-Wind-U100.jpg
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notif
This bug is also effecting my Compaq 6715b laptop running the Karmic
beta. I have attached the output from lshw, lspci, and uname. The bug
has the unfortunate side effect of disrupting the new usplash for
Karmic, and that is probably my biggest concern! I found a post from
Linus Torvalds on kernel.
Since its a address collision, with a memory allocation
problemcouldn't someone just try a temporary patch that changes what
things get what address, and memory?
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
I can't even boot the live CD.
I have nearly the same error on both i386 and AMD64 from CD. I also
tried AMD64 from USB and have same error. I am booting from the same
device that wrote the CDs under 9.04.
If I try to "check CD" the system just reboots and I cannot run the
test.
Karmic Beta (
Having this as well, latest Karmic.. Older laptop (2003 Gericom -
company defunct ;)
I also get X hardware freezes I haven't been able to find a bug for
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Ditto for me. Also tried the new kernel option nocrs but no change.
http://groups.google.com/group/linux.kernel/browse_thread/thread/a6fee640edadeeaf/999410b038bab274?lnk=raot
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member
I am having a similar error on my dell dimension 9200. Ubuntu 9.10 beta
AMD64
[1.863478] pci :04:05.0: BAR 6: address space collision on of device
[0xdbe0-0xdbe7]
[3.553122] e1000e :00:19.0: pci_enable_pcie_error_reporting failed
0xfffb
** Attachment added: "picture
I can confirm this as well on a Dell C640.
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
Looks like it's an upstream kernel issue.
http://patchwork.kernel.org/patch/39988/
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Affected. Here my datas.
** Attachment added: "bar6.tgz"
http://launchpadlibrarian.net/32939013/bar6.tgz
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
oops. Forgotten lspci...
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/32939150/lspci.txt
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Affecting me too in Ubuntu Karmic 32bit Beta. Attached dmesg and lshw
outputs.
** Attachment added: "dmesg+lshw.tar.gz"
http://launchpadlibrarian.net/32934478/dmesg%2Blshw.tar.gz
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a
** Changed in: ubuntu
Status: New => Confirmed
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
having same issue on Karmic 64 bits beta
bug attachments :
** Attachment added: "lshw-dmesg.tar.gz"
http://launchpadlibrarian.net/32880002/lshw-dmesg.tar.gz
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs,
Having this also on xubuntu karmic 32bit
--
Address Collision
https://bugs.launchpad.net/bugs/424142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
I can confirm this bug for the karmic alpha 6 live system. The output of
dmesg and lshw is attached.
** Attachment added: "output of dmesg and lshw confirming address space
collision bug"
http://launchpadlibrarian.net/32595971/dmesg_lshw.tar.gz
--
Address Collision
https://bugs.launchpad.net
I'd like to confirm that I also got this issue.
Using latest Karmic x64 with 2.6.31-11-generic kernel.
On same computer I also got Jaunty x64 and this issue is not present there.
I'm attaching the dmesg and lshw (hardware) from Karmic in 1 gzipped
file.
** Attachment added: "dmesg-and-lshw.tar.g
48 matches
Mail list logo
