n_sectors mismatch, boot hang in 2.6.20-14 not 2.6.20-12

Bug #106086 reported by Matthew Kennel on 2007-04-13
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

I have a problem which may be related to other reported SATA problems
but I haven't seen a direct match.

Basic facts: Fresh installation of 7.04 beta, on a Dell Dimension E521,
AMD Dual Core 3800 CPU. One hard drive, one DVD/ROM drive and
one DVD/RW drive, all SATA. There is no IDE connector on the motherboard.

Kernel package 2.6.20-14 fails and results in odd boot messages and a hang (sometimes) in
a USB detection/selection phase, but I suspect the problem is earlier in the SATA section.
(I removed 'quiet' and 'splash' from the GRUB command line before attempting
to boot)

Kernel package 2.6.20-12 works and boots to the GUI.

Unfortunately, the hang happens at a time AFTER the apparent
error messages from SATA stuff and that text has scrolled off the screen.
I did manage to briefly see a mention of a "n_sectors mismatch" and
then some reasonable number "!=" to something immensely huge.

When the system came up having used the -12 kernel and I typed
"dmesg" I only got the bootup messages from the current (working)
kernel and not the ones for the failure. I do not know how to
retrieve those.

I do not see a link to upload the results of 'lspci -vv' as I was instructed
to do in a kernel-bug link in a Wiki:

https://wiki.ubuntu.com/KernelTeamBugPolicies

This is my first time attempting to report a kernel bug so try not to bite
my head off too soon. :)

Matthew Kennel (mbkennel) wrote :

Sorry, I now see the link for uploading lspci output.

Matthew Kennel (mbkennel) wrote :

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 all these symptoms come from SATA problems
earlier in the boot process as many others seem to have had them.

I just confirmed that looking through /var/log/messages
did not show any messages from the boots with the bad
kernel to help you. :(

David Symons (bimberi) wrote :

Tagged as a possible duplicate of https://bugs.launchpad.net/ubuntu/+bug/106063

Matthew, thankyou for your detailed report. Cheers, Dave.

Looks like this kernel version is completely busted. No more boot with AMD64 feisty after upgrade. :(

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 Symons <email address hidden> wrote:
> 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 notification because you are a direct subscriber
> of the bug.
>

Matthew Kennel (mbkennel) wrote :

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 address hidden> wrote:
> 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 notification because you are a direct subscriber
> of the bug.
>

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers