this bug still happens on my machine in karmic. i've all but given up
hope for it to be fixed and usually just build a kernal with my custom
kernal config after each upgrade.
--
Kernel Crash [Debian or Kernel.org kernels OK]
https://bugs.launchpad.net/bugs/48264
You received this bug notification
I'm afraid there isn't much we can do without further information.
Thank you for reporting this issue. I will close it now, but please
feel free to reopen with more information.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux-source-2.6.15 (Ubuntu)
The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains
Hi Mike, Are you able to test with latest intrepid and Jaunty Alpha?
Also would it be possible for you to attach a diff between the Ubuntu
kernel config file and the one you're using?
thanks
--
Kernel Crash [Debian or Kernel.org kernels OK]
https://bugs.launchpad.net/bugs/48264
You received thi
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
** Attachment added: "the 2.6.25 kernel config based on
config-2.6.24-16-generic (also crashes)"
http://launchpadlibrarian.net/14020616/config-2.6.25-from-2.6.24-16-generic
--
Kernel Crash [Debian or Kernel.org kernels OK]
https://bugs.launchpad.net/bugs/48264
You received this bug notificat
** Attachment added: "my working 2.6.23.12 kernel config"
http://launchpadlibrarian.net/14020542/config-2.6.23.12-custom
--
Kernel Crash [Debian or Kernel.org kernels OK]
https://bugs.launchpad.net/bugs/48264
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "crash 2 screenshot"
http://launchpadlibrarian.net/14020516/IMGP1263.JPG
--
Kernel Crash [Debian or Kernel.org kernels OK]
https://bugs.launchpad.net/bugs/48264
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
** Attachment added: "crash 1 screenshot"
http://launchpadlibrarian.net/14020498/IMGP1253.JPG
--
Kernel Crash [Debian or Kernel.org kernels OK]
https://bugs.launchpad.net/bugs/48264
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Leann:
Looks like you were right. I tried an upstream kernel (2.6.25 from
kernel.org) with the hardy kernel config and it also crashes. I took two
pictures of the crashes that occur with the 2.6.24-16-generic kernel (i
couldn't get anything from kern.log.0) and I will attach them after this
messag
Hi Mike,
Care to take a peek at /var/log/kern.log.0 and see if anything is logged
there regarding the panic.
I'd also be interested to know if you'd be willing to test the upstream
kernel from kernel.org with a more recent Ubuntu Hardy Heron kernel
config. For example 'cp /boot/config-2.6.24-16-
Leann:
What I usually do is download the latest kernel from kernel.org, then
make oldconfig, then run make-kpkg to make the packages. So at one point
the oldconfig was probably based on the ubuntu kernel config but I may
have changed a few settings here and there over the years.
How can I get the
Also, if you do use the Ubuntu kernel config it would be nice to know
which specific kernel config you are using, for ex
config-2.6.24-16-generic.
--
Kernel Crash [Debian or Kernel.org kernels OK]
https://bugs.launchpad.net/bugs/48264
You received this bug notification because you are a member of
Hi Mike,
You mention that you are able to run the upstream kernels and do not
experience this issue. Do you use the ubuntu kernel config when you
build the upstream kernel? Also, would you be able to attach the same
stack trace output as in your bug description but with the 2.6.24 Hardy
kernel?
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (kernel-team) => Ubuntu Kernel Team
(ubuntu-kernel-team)
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: Ubuntu Kernel Team (kernel-team) => Ubuntu Kernel Team
(ubuntu-kernel-team)
** Changed in: linux-source-2.6.22 (Ubu
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Sourcepackagename: linux-source-2.6.24 => linux
Assignee: (unassigned) => Ubuntu Kernel Team (kernel-team)
Status: New => Confirmed
** Changed in: linux-source-2.6.2
i just tried the 8.04 beta and the kernel still exhibits the problem.
the attached dmesg shows some of the strange behavior just prior to the
machine locking up.
** Attachment added: "dmesg_4.txt"
http://launchpadlibrarian.net/13418161/dmesg_4.txt
--
Kernel Crash [Debian or Kernel.org kernels
Ok.
Updating effected packages to include Gutsy.
If you are able to access 8.04 pre-release this may be a useful test (it would
get noticed).
A Gutsy (& if possible 8.04beta) dmesg of error situation would also be useful
(and required for proper analysis by kernel team).
** Changed in: linux-s
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
Kernel Crash?
https://bugs.launchpad.net/bugs/48264
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
this is still an issue with the latest gutsy kernel on my desktop
machine. every time i do an update i need to download the kernel source
from kernel.org and build a custom kernel (which can be difficult with
the instability). there is something different about the ubuntu kernel
that is causing thi
This bug has had no activity for a considerable period. This is a check
to see if there is still interest in investigating this bug report.
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: New => Incomplete
--
Kernel Crash?
https://bugs.launchpad.net/bugs/48264
You received this bug no
21 matches
Mail list logo
