This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on
the current status under the
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Hardy Heron 8.04 was recently released. It would be helpful if you
could test the new release and verify if this is still an issue -
http://www.ubuntu.com/getubuntu/download . You should be able to test
your bug using the LiveCD. Please let us know your results. Thanks.
** Changed in: linux (U
The 18 month support period for Edgy Eft 6.10 has reached it's end of
life. As a result, we are closing the linux-source-2.6.17 Edgy Eft
kernel task.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Confirmed => Invalid
** Tags added: edgy-close
** Also affects: linux (Ubuntu)
Impo
** Tags added: kernel-oops
** Changed in: linux-source-2.6.17 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Kernel Team
Status: Needs Info => Confirmed
--
Edgy amd64 kernel lockup
https://bugs.launchpad.net/bugs/82987
You received this bug notification
Had another lockup. It seemed to be pretty stable for several days. I
had upgraded to:
$ uname -a
Linux stargate 2.6.17-11-generic #2 SMP Thu Feb 1 18:03:05 UTC 2007 x86_64
GNU/Linux
I was hoping this had caused the issue to vanish. Unfortunately, not the
case. Attached is the segment from /var/
0. Please update BIOS.
> Need clearer direction why this is necessary.
1. Please include the output of the command "uname -a" in your next response.
It should be one, long line of text which includes the exact kernel version
you're running, as well as the CPU architecture.
> Already did that ea
** Attachment added: "lspci"
http://librarian.launchpad.net/6488811/lspci.log
--
Edgy amd64 kernel lockup
https://launchpad.net/bugs/82987
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "dmidecode"
http://librarian.launchpad.net/6488802/dmidecode.log
--
Edgy amd64 kernel lockup
https://launchpad.net/bugs/82987
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "dmesg"
http://librarian.launchpad.net/6488801/dmesg.log
--
Edgy amd64 kernel lockup
https://launchpad.net/bugs/82987
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Change Status of Unconfirmed to Needs Info.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Unconfirmed => Needs Info
--
Edgy amd64 kernel lockup
https://launchpad.net/bugs/82987
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubun
Thanks for taking the time to report this bug. Unfortunately we can't
fix it, because your description didn't include enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional options), as required by
the
** Attachment added: "Another kernel crash"
http://librarian.launchpad.net/6268308/crash_kern3.log
--
Edgy amd64 kernel lockup
https://launchpad.net/bugs/82987
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "Lines from /var/log/kern.log when problem occurred until
lockup."
http://librarian.launchpad.net/6155803/crash_kern.log
--
Edgy amd64 kernel lockup
https://launchpad.net/bugs/82987
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
14 matches
Mail list logo
