I worked with shankao through private emails to bisect to the first
commit that causes issues for him. Here's the output of the bisection
(note that the tree is the ubuntu-lucid git tree hosted at
kernel.ubuntu.com):
1369d982cea341524032a248b1f31832bb8c3eb6 is first bad commit
commit
** Bug watch added: freedesktop.org Bugzilla #25408
https://bugs.freedesktop.org/show_bug.cgi?id=25408
** Also affects: linux via
https://bugs.freedesktop.org/show_bug.cgi?id=25408
Importance: Unknown
Status: Unknown
--
Can't boot with last linux kernels from 2.6.32.10 to
** Changed in: linux
Status: Unknown = Confirmed
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
@shankao:
Can you test the latest kernel I've built:
http://people.canonical.com/~cndougla/505808/vram_cocktail/linux-
image-2.6.32-13-generic_2.6.32-13.19_i386.deb. It contains three new
patches:
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@chase: em... I think that's not me...
Yes, I'm still interested in having the last kernel working. I can make some
test as you suggest, but I need some guidance. Can you please point to the info
or procedures that I should follow?
Maybe this bug report is not the better place to continue this
I am working with shankao through email to proceed with a git bisect
run. When we have results they will get posted here.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Chase Douglas (chasedouglas)
** Changed in: linux (Ubuntu)
Status: New = Triaged
--
Can't boot with last
@shankao:
Your issue seems to be related to bug 510524. Can you try upgrading your
plymouth package to see if it helps?
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You
@Hew,
I don't think your issue is related.
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Upgraded to 0.8.0~-9ubuntu1 and still no change. I'm stuck with the .9
kernel :(
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you
@shankao:
Can you try removing plymouth and seeing if that helps?
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member
Done, and nothing changes... but some extra complains about the missing
plymouth.
We can put plymouth out of the possible causes.
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
@shankao:
The 2.6.32-9 kernel is based on upstream 2.6.32.1. The -10 kernel is
based on upstream 2.6.32.2. Can you try out the upstream kernels? You
can find prebuilt kernel packages at:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.1/
I can boot with upstream 2.6.32.2
$ uname -a
Linux clotilde 2.6.32-02063202-generic #02063202 SMP Sat Dec 19 11:00:49 UTC
2009 i686 GNU/Linux
$
Do this mean that the problem is in the ubuntu changes? Should I also
test with the 2.6.32.1 one (that I can boot if ubuntu's .9 is based on
it) or
@shankao:
I think this is enough information for now. I will look into things a
bit further.
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Tags removed: needs-upstream-testing
** Tags removed: i386
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
@shankao:
There's 173 changes between the -9 and the -10 kernels. Are you able to
build and git bisect your way through a few ubuntu test kernels to
determine what change is giving you issues?
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@shankao:
I think I just received an email from you saying your hardware has
changed and that may be making a difference for you. If this is the
case, are you still interested in following up on this issue with the
same hardware?
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
My problem turned out to be bug 507881
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can't boot with 2.6.32-9-generic either. I get the following error
message which may or may not be related:
mount: mount point /proc/bus/usb does not exist
mountall: mount /proc/bus/usb [703] terminated with status 32
mountall: Filesystem could not be mounted: /proc/bus/usb
--
Can't boot
20 matches
Mail list logo
