** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Needs Info = Fix Released
--
latest feisty kernel does not boot
https://launchpad.net/bugs/84059
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi Miek
Can you confirm that you have not experienced this bug since upgrading
to 2.6.20-8? If so, we can close this bug.
Thanks
--
latest feisty kernel does not boot
https://launchpad.net/bugs/84059
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
[On 14 Mar, @19:25, Phillip Lougher wrote in [Bug 84059] Re: latest feisty
...]
Hi Miek
Can you confirm that you have not experienced this bug since upgrading
to 2.6.20-8? If so, we can close this bug.
I think this is a duplicate of: 75681
regards,
--
latest feisty kernel does not boot
The latest kernel upgrade, 2.6.20-8.x seems to fix to issue.
--
latest feisty kernel does not boot
https://launchpad.net/bugs/84059
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
It is kernel version 2.6.20-6.11.
I've did a apt-get install --reinstall of the kernel and this helped. I
can now boot the laptop... I'm still suspecting a bad block on the disk
or something.
Can I run some tests?
--
latest feisty kernel does not boot
https://launchpad.net/bugs/84059
--
Did a badblocks /dev/hda3 which didn't report any errors. Kernel crashes
again...with the same backtrace as above.
--
latest feisty kernel does not boot
https://launchpad.net/bugs/84059
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The crashing kernel does not write any dmesg/boot logging, so I cannot
give that in this bugreport :(
--
latest feisty kernel does not boot
https://launchpad.net/bugs/84059
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
If is possible that you are being hit by a critical issue we found
resolved between yesterday and today.
A must for this error is you have multiple filesystems -- and,
specifically, /usr/lib is on a different filesystem than /. If this is
the case... then:
If you installed libx86-1 yesterday to
Thanks for your bug report. If you modify the kernel boot options in
grub for the new kernel and remove 'splash' and 'quiet' is there a more
informative error returned?
** Changed in: linux-meta (Ubuntu)
Sourcepackagename: linux-meta = linux-source-2.6.20
Assignee: (unassigned) = Brian
Note: this is on powerpc so there is no grub, only yaboot - using
'nosplash' on the boot prompt doesn't make any difference. And I'm using
only 1 filesystem, /dev/hda3 is / and /dev/hda4 is swap (hda1/hda2 are
used by yaboot - I think).
--
latest feisty kernel does not boot
Ah, found /etc/yaboot.conf via the rescue cd - its a kernel crash...:
Faulting instruction address: 0xc0084a0c
Oops: kernel access of bad area: sig: 11 [#1]
And a lot of other numbers
Is this a kernel bug or a bad disk?
I might be able to make a picture of the dump if that is really
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided = Medium
Assignee: Brian Murray = (unassigned)
--
latest feisty kernel does not boot
https://launchpad.net/bugs/84059
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Yes. It's really needed. Especially the traceback portion.
Cheers,
Kyle
--
latest feisty kernel does not boot
https://launchpad.net/bugs/84059
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sorry for the bad quality, I only have a mobile laying around here. Tomorrow I
will type
the backtrace of the screen.
** Attachment added: loosy backtrace picture 1
http://librarian.launchpad.net/6360667/Afb271.jpg
--
latest feisty kernel does not boot
https://launchpad.net/bugs/84059
--
Need to know exactly what kernel version you are using. First off, you
should be able to boot the old kernel, and yaboot prompt type old
(hitting TAB should show you the available options).
Run this command:
dpkg -l | grep linux-source
Send the output of that command.
** Changed in:
Backtrace:
init-bottom
Done
Unable to handle kernel paging request for data at address 0x004
Faulting instructing address: 0xc0084a0c
Oops: kernel access of bad area: sig: 11 [#1]
Call Trace:
DFFC3E40 C0084AAB free_block+0x160/0x16c (unreliable)
DFFC3E60 C00845B8
On booting the old kernel: I can select 'old' in the yaboot prompt, but
this kernel isn't configured... No vmlinuz.old nor an initramfs.old is
there in the /boot directory.
I can only boot from a rescue CD and then chroot to the root partition. I
should be able to retrieve
the boot.log that way.
17 matches
Mail list logo
