[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261596
Christopher, unfortunately I'm no longer able to reproduce the crash
reliably enough to complete the bisect. If anything changes, I'll
update this bug, but for now I'll most likely just run 12.04 which
doesn't appear to have the issue.
--
You received this bug notification because you are a
Christopher, I have not experienced the crash in 12.04.3 which is
running kernel 3.8.0-29-generic. I'm pretty confident in saying it is
not present in this version as the other kernels crash within 10
minutes. I'll report back if the situation changes, but consider it not
a bug in 12.04 at this
Mark Shirley, thank you for testing Precise. Assuming the issue is not
reproducible in Precise, could you please test for this in Raring via
http://releases.ubuntu.com/raring/ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Christopher, I did not experience the crash in Raring either. As with
Precise, I left the system running for a couple hours and did different
tasks to load the system (that's the best method I have for reproducing
the crash). To be sure, I then reinstalled 13.10 and got the crash
within 5
Mark Shirley, thank you for testing Raring. The next step would be to
fully commit bisect from Raring to Saucy, in order to identify the
offending commit. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?
--
You received this bug notification because you are a
Christopher, I'm trying several different mainline kernels, but all seem
to hang at Loading initial ramdisk. Once I fix that issue, I can
proceed with testing for the kernel panic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261596
Title:
[Intel S2600GZ] System crash at thread_group_cputime_adjusted
To manage notifications about this bug go
OK, I've been running v3.12-saucy, from http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.12-saucy/. I have not yet experienced the
kernel panic. With the 3.11.0-14 it usually crashed within an hour.
I'll wait a few more hours before adding the fixed upstream tags.
Assuming everything looks
Mark Shirley, thank you for testing the mainline kernel. Once a mainline
kernel has been identified to not have the bug, the next step would be
to reverse bisect mainline kernel versions until the earliest fix kernel
has been identified, and subsequently the fix commit.
--
You received this bug
Christopher, I was only able to boot the mainline kernel by doing a
(recovery mode) boot and then resuming a normal boot from there. When
doing this (even with the 3.11.0-14 kernel) I'm not experiencing a
crash. I don't think I can reliably diagnose the problem unless I can
get past the Loading
Mark Shirley, darn. Well, we could approach this a different way, in
that was this issue reproducible with a prior server release of Ubuntu
(ex. Precise or Lucid)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, good (?) news. I was able to load the v3.12-saucy kernel without
using recovery mode by adding the nomodeset boot parameter (not sure
why that gets past the Loading initial ramdisk hang). I almost
immediately got the same kernel panic as seen in 3.11.0-14. Therefore
it is not fixed
Mark Shirley, nice troubleshooting on the kernel boot parameter. Would
this allow you to make a test of the latest mainline kernel
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/ and see
if anything changes with it?
** Tags removed: kernel-bug-exists-upstream
** Tags added:
OK, I tried booting again and this time got the original crash. So it
looks like it is present in v3.13-rc3 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261596
Title:
[Intel S2600GZ]
Unfortunately the v3.13-rc3 kernel is crashing on boot with a different
stack trace ending with __purge_vmap_area_lazy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261596
Title:
[Intel S2600GZ]
Mark Shirley, thank you for testing the latest mainline kernel. Did this
problem not occur in a prior kernel version or prior Ubuntu server
release?
** Tags removed: kernel-bug-exists-upstream-v3.12 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-v3.13-rc3
--
You received this
This is the only Ubuntu server release I've run on this system. I can
try 12.04 and see if the problem exists there if that would be helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261596
Mark Shirley, that would be most helpful to test 12.04 via
http://releases.ubuntu.com/precise/ . If reproducible, for regression
testing purposes, could you also please test Lucid via
http://releases.ubuntu.com/lucid/ ?
--
You received this bug notification because you are a member of Ubuntu
19 matches
Mail list logo
