*** This bug is a duplicate of bug 106063 ***
https://bugs.launchpad.net/bugs/106063
** Branch unlinked: lp:~openerp-dev/openobject-server/7.0-opw-598942-acl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
*** This bug is a duplicate of bug 106063 ***
https://bugs.launchpad.net/bugs/106063
** Branch linked: lp:~openerp-dev/openobject-server/7.0-opw-598942-acl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
*** This bug is a duplicate of bug 106063 ***
https://bugs.launchpad.net/bugs/106063
** This bug has been marked a duplicate of bug 106063
Computer will not boot after 2.6.20-14.24 kernel upgrade
--
n_sectors mismatch, boot hang in 2.6.20-14 not 2.6.20-12
https://bugs.launchpad.net/bugs/1
By the way, recent commenters on bug 82314 seem to now
be coming up with the same error message as mine.
On 4/12/07, David Symons <[EMAIL PROTECTED]> wrote:
> Tagged as a possible duplicate of
> https://bugs.launchpad.net/ubuntu/+bug/106063
>
> Matthew, thankyou for your detailed report. Cheers,
yes, it does seem "inconsistently" (in terms of where it craps out) consistent
and coincidental with the version & error message.
I'm relieved. Is there a way to merge all the bugs so we can all see
the progress on the central issue no matter how we found it?
cheers
Matt
On 4/12/07, David Symo
Looks like this kernel version is completely busted. No more boot with
AMD64 feisty after upgrade. :(
--
n_sectors mismatch, boot hang in 2.6.20-14 not 2.6.20-12
https://bugs.launchpad.net/bugs/106086
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
Tagged as a possible duplicate of
https://bugs.launchpad.net/ubuntu/+bug/106063
Matthew, thankyou for your detailed report. Cheers, Dave.
** Tags added: likely-dup
--
n_sectors mismatch, boot hang in 2.6.20-14 not 2.6.20-12
https://bugs.launchpad.net/bugs/106086
You received this bug notificat
Let me clarify the comment about the hang. It seems to hang all the time,
but where it is in the boot process is occasionally unpredictable.
Sometimes I have also seen errors in that it doesn't seem to be able
to find the god-awful long UUID string for the root file system.
My guess is that a
Sorry, I now see the link for uploading lspci output.
** Attachment added: "lspci -vv output under working kernel"
http://librarian.launchpad.net/7315843/lspci.log
--
n_sectors mismatch, boot hang in 2.6.20-14 not 2.6.20-12
https://bugs.launchpad.net/bugs/106086
You received this bug notifi
