We just got bit by this.
It looks like there *WAS* a fix in the Lucid package at one point, but
then it was removed because:
debian/patches/96_fix_daylight-saving.dpatch: Already upstream.
Well, it is NOT upstream in 3.2.0. =/
--
You received this bug notification because you are a member of
We just got bit by this.
It looks like there *WAS* a fix in the Lucid package at one point, but
then it was removed because:
debian/patches/96_fix_daylight-saving.dpatch: Already upstream.
Well, it is NOT upstream in 3.2.0. =/
--
You received this bug notification because you are a member of
It looks like everything has been qualified in the bug for the proposed
package, and everyone has signed off on it. As of the 27th of October.
I wonder if there's anything else preventing it from being promoted?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
See:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/871899
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/614853
Title:
kernel panic divide error: [#1] SMP
To manage notifications about
Can I be pointed to the commit with the diff where the fix went into
linux generic (server, etc.) and what package rev it will go into
testing on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/614853
Thanks Tim. If we can at least keep the div by zero from happening and
keep the kernel from dying, if the underlying problem occurs again we
can at least gather more information to determine what happened to put
it the situation in the first place. In the meantime, at least we don't
have to keep a
I wound up opening a separate bug for the generic/server packages over
at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/824304?comments=all
... There didn't seem to be a way for me to add those packages to this
ticket (just other projects).
--
You received this bug notification because
Due to the nature of the crash, logs cannot be obtained. Screenshots in
the referenced ec2 bug are relevant, however, and the problem is already
described in that bug, but because it was only reported for ec2 package,
fixes were not applied to the generic/server kernel packages.
I am setting bug
Quick hardware description of systems that this is occuring on:
SuperMicro X8-series motherboards, various models equipped with Xeon
Westmeres, various models.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This is relevant to Lucid 10.04.2, but it seems to affect all 2.6.32
builds (and possibly others). Symptoms are very frustrating divide by
zero kernel panics/hangs after roughly 200 days uptime.
Currently using:
Ubuntu 2.6.32-32.62-server 2.6.32.38+drm33.16 -- image
10 matches
Mail list logo
