I'm experiencing quite similar problems on Ubuntu 12.04.1 LTS running on
brand new Fujitsu servers :(
** Attachment added: "messages.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/614853/+attachment/3432126/+files/messages.tar.gz
--
You received this bug notification becaus
** Changed in: linux
Status: Confirmed => Fix Released
--
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 this
This is also affecting Maverick, on physical hardware.
--
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 this bug go
Has there been an AKI released for this new patch?
--
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 this bug go to:
This bug was fixed in the package linux - 2.6.32-35.78
---
linux (2.6.32-35.78) lucid-proposed; urgency=low
[Herton R. Krzesinski]
* Release Tracking Bug
- LP: #871899
[ Andrew Dickinson ]
* SAUCE: sched: Prevent divide by zero when cpu_power is 0
- LP: #614853
[
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
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, which
Any ETA on promoting the 2.6.32-35.78 kernel package from -proposed to
-updates?
--
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 notif
** Branch linked: lp:ubuntu/lucid-proposed/linux-mvl-dove
** Branch linked: lp:ubuntu/maverick-proposed/linux-mvl-dove
--
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 divid
Since this bug is hard to verify, looking to require more than 1 week
with the pristine kernel, and the same patch is already for some time in
lucid-ec2 without issues, I'm marking verified for lucid update.
** Tags removed: verification-needed-lucid
** Tags added: verification-done-lucid
--
You
The patch is now in -proposed 2.6.32-35.78 kernel for Lucid (it is
already included in current ec2 flavour, just main kernel for lucid
didn't have it).
Just noted that on master, the debugging patch "UBUNTU: SAUCE: sched:
Try tp catch cpu_power being set to 0" isn't included, not sure this was
int
mine has been running for 212 days when it crashed
after what i can read on the internet, it _seems_ this bug happens when the
server's uptime is 200+ days
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
That syslog is from a 2.6.32 kernel (and a quite old one 2.6.32-29.58).
However the current 2.6.32-34.77 would not have the work-around patch,
yet. It is staged for the next round of updates. Was that the correct
syslog (because crashes with 2.6.35 were mentioned).
--
You received this bug notifi
It was 244 days actually. Syslog output attached.
** Attachment added: "syslog output"
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/614853/+attachment/2512258/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Yes, the scheduler code changed since 2.6.32 and so the syslog is
valuable. Also, was this actually 200+ day uptime or quicker?
--
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 pan
Ok we just got hit again by this bug is there still need to attach the
output from syslog to this bug?
--
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
Hi.
today, on my filer, running debian squeeze with kernel 2.6.32-5-amd64, i had
the same bug in "find_busiest_group"
see the screen here :
http://pic.twitter.com/sAih9DlN
after rebooting, my server runs fine... but i'm affraid it can happen again :(
--
You received this bug notification because
It seems like a regression to me or introduced by a new feature. We
still have some karmic KVM hosts that are running 2.6.31-20-server
kernel but they are definitely not affected by this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Whether using 2.6.35 or 2.6.38 would make no difference if the patch
which is upstream helps. There was a patch claimed to cause the problem
sooner in the upstream discussion but it did not seem to work for me
when I tried it. So unfortunately I know of now way to speed up testing.
--
You receive
Since the latest kvm machine is running 2.6.35-30-server
#59~lucid1-Ubuntu and has an uptime of 13 days, 22:03. Will report back
in 206 days from now to see if that fix is working as intended. Is there
any other workaround available? Like upgrading to another backports
kernel, 2.6.38 perhaps?
Or
This is currently only committed to the repository and will be included
in the next proposed kernel update. There will be a message to this
report, asking for verification when the package is prepared. Note this
is 2.6.32. For 2.6.35 see comment #39: Ubuntu-2.6.35-29.51 had a fix
that was said to f
As James Sellman I'm quite curious if someone could point me to the
changelog of the 2.6.35.xx kernel version where this was fixed as I'm
unable to find it. I just want to make sure that this issue is fixed or
has a workaround so that we don't get this oops again. So far 20 KVM
servers have been hi
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
This bug will be next to impossible to verify given its 219 day cycle.
** Changed in: linux (Ubuntu Lucid)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Lucid)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: linux-ec2 (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: linux-ec2 (Ubuntu Lucid)
Statu
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 you
This looks like the work-around used for the ec2 kernels. So it sounds like the
same problem can in fact happen on real hardware (which was not really clear).
That, the fact that it is clearly only papering over some other issue and no
reports about this happening on other kernels prevented any
Apparently a patch will be included in Debian to fix the 219 days issue,
as per http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636797
It's for 2.6.32, but would you think it could be ported to the 2.6.35 on
Maverick? Should I file a different bug?
Thanks,
** Bug watch added: Debian Bug tracker
No, as this report was only observed on ec2 kernels and also quicker.
There has been some upstream stable discussion about crashes after 219
days of uptime (in 2.6.32 based kernels). One of the patches mentioned
commit 305e6835e05513406fa12820e40e4a8ecb63743c
Author: Venkatesh Pallipadi
Date: M
Hi all.
This happened to me with 2.6.35-24-server, it is a MySQL (Percona,
5.1.54) machine running not so heavy load but slightly heavier IO.
Please find attached the crash log.
The uptime of the server was ~219 days, which is relevant according to
the original bug at the kernel.
Was the patch o
Scott,
you're right! I think what happened is, that we were running 312 and had
a crash after which we rebooted the machine and installed the newest
kernel (314 at that time). But we didn't reboot the machine after the
upgrade, so 312 was still running.
Please ignore comment #36!
Let's see how 31
Rudolf,
your console log shows:
[0.00] Linux version 2.6.32-312-ec2 (buildd@yellow) (gcc version
4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #24-Ubuntu SMP Fri Jan 7 18:30:50 UTC 2011
(Ubuntu 2.6.32-312.24-ec2 2.6.32.27+drm33.12)
That definitely indicates that you've either collected the wrong
I can confirm, that this bug is still happening in (see attached log):
Ubuntu 10.04.2 LTS, kernel 2.6.32-314-ec2
We're running a Postgres server on AWS with linux software raid10. After the
crash we upgraded to:
Linux db6.i.bluereport.net 2.6.32-316-ec2 #31-Ubuntu SMP Wed May 18 14:10:36
UTC 201
This bug was fixed in the package linux-ec2 - 2.6.32-313.26
---
linux-ec2 (2.6.32-313.26) lucid-proposed; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #716657
[ Brad Figg ]
* Release Tracking Bug
- LP: #712864
[ Brad Figg ]
* Rebased to 2.6.32-29.58
** Tags added: verification-needed-lucid
--
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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
** Branch linked: lp:ubuntu/lucid-proposed/linux-ec2
--
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
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Patch is in 2.6.32-313.25
** Changed in: linux-ec2 (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: linux-ec2 (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: linux
Status: Unknown => Confirmed
--
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
--
ubuntu-bugs mailing list
ubuntu-bug
SRU Justification:
Impact: When trying to find the busiest group for the scheduler, there
are rare (but it seems more likely in EC2) cases where cpu_power is zero
when the code tries to divide by that variable.
Fix: There is no real fix yet (and therefor both patches are not upstream) but
users
Not yet, but in the end maybe the pragmatic approach will have to do
until there is something better. I tried to reproduce this with the
other patch from the upstream bug (to possible catch setting the value
to zero) but have not been able to get anything. I have packages with
those kernels at http
Has this been merged into 10.04? If not, the "paper over" patch should
really get included in my opinion and then be replaced when the correct
fix is available. Myself and others have been running the custom kernel
that includes the fix for a while now with success. I guess I am a bit
more pragmati
We had at least 4 crashes related to this bug (all within 2 months).
Attached the messages of the latest two panics.
It's a DB server running postgres and a linux software raid10 setup for
storage. On all occasions the machine had a higher load than normal ~20
- 30 (normally ~15), on the latest cr
There was more action on the linux bug
(https://bugzilla.kernel.org/show_bug.cgi?id=16991#c17), and a paper-
over patch sent upstream
http://lkml.indiana.edu/hypermail/linux/kernel/1010.2/02058.html . The
upstream post got the expected response (no... fix it right).
--
You received this bug noti
It has been reported that Bug #671001 was encountered before the ran the
test kernel with the above patch.
--
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:
The patch posted above may be causing Bug #671001. The patch "fixes"
this bug by simply checking for 0 before doing the division it does not
address the underlying issue causing group->cpu_power to be 0 in the
first place. So instead of oopsing at the divide by zero, the kernel
continues until th
This patch seems solid, the panics don't seem to happen any longer on my
machines.
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Tags added: patch
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
** Changed in: linux-ec2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-ec2 (Ubuntu)
Status: New => Confirmed
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a member of Ubuntu
Bugs, wh
ubuntu-kernels-sandbox/ubuntu-lucid-amd64-linux-
image-2.6.32-310-ec2_2.6.32-310.190-lp614853-kernel.img.manifest.xml
I uploaded to each region john's kernel from
http://kernel.ubuntu.com/~jj/linux-image-2.6.32-310-ec2_2.6.32-310.19~lp614853_amd64.deb
us-west-1 aki-3e23737b x86_64
us-east-1
I have been running this patch in production for a couple days and it
seems solid thus far. I'm going to wait a few more days before I call it
fixed though.
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a memb
This is the patch from comment #17 backported to Lucid.
** Patch added: "lp614853.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/614853/+attachment/1729278/+files/lp614853.patch
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received t
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=16991
Importance: Unknown
Status: Unknown
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
@Scott I do not believe its the same bug, see the discussion at
https://bugzilla.kernel.org/show_bug.cgi?id=16991
I have gotten a patched kernel from canonical support and applied it to
some of my machines this morning, we'll see if it will fix the panics.
--
kernel panic divide error: [#1]
@Joe,
Do you think that this bug is a duplicate (or vice versa) of bug 651370 ?
The thing that makes me think it might be is that your console log and all
linked images show massive timestamps in the kernel at the time of the failure.
Ie, "3229228" is ~ 897 hours uptime. Was your system up
I believe I have found this bug reported in the kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=16991
Anything that can be done to expedite a fix is appreciated.
** Bug watch added: Linux Kernel Bug Tracker #16991
http://bugzilla.kernel.org/show_bug.cgi?id=16991
--
kernel panic
I doubt they are related but figured it was worth mentioning last night
we got soft lockups (not the divide by zero panics we've seen in the
past) on a machine. Our hosting provider's KVM software didnt allow me
to get the text but i got some screenshots.
http://img.skitch.com/20100914-nkskuxfcucg
Verified my disks are not CFQ, so it seems to effect all schedulers.
$ cat /sys/block/*/queue/scheduler | grep -v none
noop anticipatory [deadline] cfq
noop anticipatory [deadline] cfq
noop anticipatory [deadline] cfq
noop anticipatory [deadline] cfq
noop anticipatory [deadline] cfq
noop ant
apport information
** Description changed:
I have seen this both on EC2 and physical hardware. I installed linux-
crashdump on these machines to see if I can get more information but I
will have to wait for another crash.
divide error: [#1] SMP
[1449293.452514] last sysfs fil
Got it again ...
** Attachment added: "panic.log"
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/614853/+attachment/1545147/+files/panic.log
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a membe
** Attachment added: "lsmod"
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/614853/+attachment/1543562/+files/lsmod
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I ran "apport-collect 614853" on the aformentioned EC2 node and all it
seemed to produce was the above dependency list. I have attached uname
and lsmod should they be helpful.
** Attachment added: "uname"
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/614853/+attachment/1543561/+file
apport information
** Description changed:
I have seen this both on EC2 and physical hardware. I installed linux-
crashdump on these machines to see if I can get more information but I
will have to wait for another crash.
divide error: [#1] SMP
[1449293.452514] last sysfs fil
Not sure if it's related but I noticed the following on boot up of the
EC2 machine:
Checking for running unattended-upgrades: [ 132.079264] BUG: soft
lockup - CPU#0 stuck for 61s! [udevd:219]
[ 197.577155] BUG: soft lockup - CPU#0 stuck for 61s! [udevd:219]
[ 240.073502] INFO: task mount:609
Here's another panic screenshot (physical hardware) and console output
(EC2).
http://img.skitch.com/20100904-bitg4476jipband75g38g5wjcb.jpg
** Attachment added: "panic.log"
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/614853/+attachment/1543483/+files/panic.log
--
kernel panic d
I have confirmed this happens with the deadline IO scheduler. Today an
EC2 node of ours running deadline on all the disks got the same "divide
error: [#1] SMP" panic.
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because
In an attempt to figure out the issue I decided to change the IO
scheduler thinking it might help considering the contents of the trace.
I set one group of nodes to noop and another to deadline. I have seen
panics on both groups of machines since doing so. From the (partial)
traces I've gotten from
apport information
** Tags added: apport-collected
** Description changed:
I have seen this both on EC2 and physical hardware. I installed linux-
crashdump on these machines to see if I can get more information but I
will have to wait for another crash.
divide error: [#1] SMP
All of these servers are doing high throughput database work,
specifically CouchDB.
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
Joe,
what kind of work loads are you running to trigger this?
also after you hit this bug again could you run
apport-collect 614853
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I have been unable to collect a core using linux-crashdump on my
physical machines, it doesn't seem dump it and reboot automatically.
However it does seem to load the crash kernel (kdump init script).
I did collect another stack trace from one of my EC2 machines:
[2498228.006101] divide error: 00
On the physical hardware I am running 2.6.32-24-generic, without any
virtualization of any sort.
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Joe,
can you elaborate on which kernel and the setup you were using when you
saw this on physical hardware, ie. were you running lucid's generic
kernel on physical hardware, or where you running the ec2 kernel under a
Xen dom0, etc.
--
kernel panic divide error: [#1] SMP
https://bugs.launch
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/53250006/Dependencies.txt
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
74 matches
Mail list logo
