[Expired for linux (Ubuntu Saucy) because there has been no activity for
60 days.]
** Changed in: linux (Ubuntu Saucy)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu Raring) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Raring)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
I don't think so.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1159219
Title:
Ubuntu Raring , IOMMU, fails to boot
Status in “linux” package in Ubuntu:
Incomplete
Status in “linux”
Thanks for testing. I'll investigate the IOMMU patches further.
Was there ever an upstream bug report opened, per the request in comment
#5?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
I have tested it an got the same results. Does not boot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1159219
Title:
Ubuntu Raring , IOMMU, fails to boot
Status in “linux” package in
The 3.12 final kernel is now out. Can you give this kernel a try to see if the
bug still exists in mainline:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-saucy/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
Hi, i have done the testing with the same errors. Does not boot. drops to
Busybox.
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1159219
Title:
Ubuntu Raring , IOMMU, fails to
Can you test the v3.12-rc3 kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc3-saucy/
** Changed in: linux (Ubuntu Saucy)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Raring)
Status: Confirmed => Incomplete
--
You received this bug notification because yo
** Tags added: saucy
** Also affects: linux (Ubuntu Saucy)
Importance: High
Status: Triaged
** Changed in: linux (Ubuntu Raring)
Status: New => Confirmed
** Changed in: linux (Ubuntu Raring)
Importance: Undecided => High
--
You received this bug notification because you are
Also sorry for the delay. :-) I was in vacation.
I have tested it and still no go, same error.
So it is not fixed yet. What's next.
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/11
Sorry for the delay, I was away for a few days. Thanks for testing that
kernel. I'll have to investigate the set of iommu/amd patches further.
The v3.11-rc4 kernel is now out. Can you also test this kernel, just to see if
the bug is already fixed in mainline?
http://kernel.ubuntu.com/~kernel-p
Sorry to say but it still does not boot. I have installed both debs and choose
the .27 version from grub. The same drop to busybox happened.
Do you need me to run some tests?
What's next if there is any?
Thank you for your hard work it's much appreciated.
--
You received this bug notification be
I built a raring test kernel with commit 33f28c59 reverted. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1159219/
Can you test this kernel and confirm that it fixes this bug? Note, you
will need to install both the linux-image and linux-image-extra .deb
packages
33f28c59 was identified as the first bad commit:
33f28c59e18d83fd2aeef258d211be66b9b80eb3 is the first bad commit
commit 33f28c59e18d83fd2aeef258d211be66b9b80eb3
Author: Joerg Roedel
Date: Fri Jun 15 18:03:31 2012 +0200
iommu/amd: Split device table initialization into irq and dma part
I'
15 matches
Mail list logo
