The problem was resolved in #86, not #85
--
David J. Andruczyk
Systems Administrator
University IT - Enterprise Applications
44 Celebration Drive, Suite 3-100
Rochester, NY 14627
E-mail: david.andruc...@rochester.edu
Office: 585-275-9106
-Original Message-
From: boun...@canonical.com
3.13.0-52.86 DOES work and no longer exhibits the crash/oops when
booted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1450442
Title:
Kernel Oops - unable to handle kernel NULL
3.13.0.52-85 still has the same panic related to the audit
subsystem
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1450442
Title:
Kernel Oops - unable to handle kernel NULL
*** This bug is a duplicate of bug 1450442 ***
https://bugs.launchpad.net/bugs/1450442
3.13.0.52.85 STILL exhibits the exact same problem and crash
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Applying 3.13.0-51.84 as per normal update process, reboot of node results in
hard crash. Unfortunately since it's on VMware ESXi it's no possible to catch
scrollback, however a screenshot of hte majority of the crash is linked below:
.http://i.imgur.com/y1531Bl.png
Audit rules trigger this crash. (Strlen)
See http://imgur.com/sWXVpvX,yYMgmOS#0
Linked to bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444141
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Can someone please re-open this bug and mark it as critical.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1444141
Title:
linux: 3.13.0-51.84 -proposed tracker
Status in Kernel SRU
Test scenario: Revert audit config to stock (as installed by vendor
pkgs), boot is clean, system stable, add my rules (which have worked
in all previous relases), restart audit daemon, system still working,
restart Apache, BANG! kernel panic!
BUG: unable to handler kernel NULL pointer
3.13.0-51.84 crashes on every node I've used it on on VMware ESXi 5.5
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450504
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Disabling my audit config and rules seems to present the crash.
** Attachment added: audit rules used when the system crashes hard on boot
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450504/+attachment/4388397/+files/audit.rules
--
You received this bug notification because you
NOTE: Most of these systems that were crashing were Apache Webservers
using php5-fpm with unix domain socket communication between the two of
them, the other's were MySQL, they didn't crash as quickly but did
within minutes of bootup. All packages were ubuntu repo provided,
though the apache and
Disabling the audit rules that were in place eliminates the crash.
More details in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450504
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: auditd.conf used when system crashes on boot
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450504/+attachment/4388398/+files/auditd.conf
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm affected by this bug across 10 production servers, is there a
fix/workaround for trusty, that doesn't involve a manual kernel roll?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Ubuntu 3.2.0-64.97-virtual 3.2.59
One of our Production systems crashed with the following kernel.log
messages (we use a custom syslog setup):
Jun 13 01:06:04 www-node01 kernel: [593611.895631] [ cut here
]
Jun 13 01:06:04 www-node01 kernel:
This was a one time event, and I don't know of a way to replicate it at
this time. Monitors of the box showed it was largely idle at the time
the bug exhibited itself. VMware reported repeated high/low CPU
consumption from the time of the bug until it was forced off and
restarted. The host WAS
16 matches
Mail list logo
