What instance type saw this kernel panic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787258
Title:
3.13.0-155.205 Kernel Panic - divide by zero
To manage notifications about this bug go to:
Public bug reported:
I keep trying to set up external SSH access using openssh server on my
18.04 system and it throws back this error
sudo service ssh status
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
enabled)
I imagine CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is set for the Ubuntu
kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668129
Title:
Amazon I3 Instance Buffer I/O error on dev nvme0n1
To manage
Yes, ballooning has been a constant source of problems which is why it
is disabled in Amazon Linux AMI.
We do not currently support DMA to/from guest physical addresses outside
of the E820 map for ENA networking or NVMe storage interfaces. This
effectively means that ballooning needs to be
Dan,
It appears that the requests that are being submitted refer to DMA
addresses that exceed the guest physical memory range, and this is why
the requests are being failed. The address seen is outside the E820 map:
[ 0.00] e820: BIOS-provided physical RAM map:
[ 0.00] BIOS-e820: [mem
Dan,
This BUG_ON has been demoted to only trigger when DEBUG_VM is set in
upstream:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=97ee4ba7cbd30f1858f0d16911e042737c53f2ef
I'm looking into why there's a one page difference between the E820
tables and SRAT. You're
Hi Stefan,
I looked at this a long time back (circa 2011), and things may have
changed since then. See:
https://forums.aws.amazon.com/thread.jspa?threadID=59753
When I looked at this last, we weren't emulating TSC and the CPUID flags
that advertise invariant TSC came through. This was making the
Not precisely. What toolstack are you using? I can try to reproduce
outside of our control plane with a config file that would work on your
toolstack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Boris, all:
We did a test with disabling the SRAT entirely, but the balloon messages
persisted.
ami-af8d9ac6 (ubuntu/images-milestone/hvm/ubuntu-
trusty-14.04-beta2-amd64-server-20140326)
$ dmesg | grep -i 'srat\|node\|numa\|balloon' |grep -iv inode
[0.00] No NUMA configuration found
[
I have a very similar setup, and had the same issue.
Samsung NP535U3C-B01US
AMD A6-4455M APU with Radeon(tm) HD 7500G Graphics
3.5.0-17-generic
Ubuntu 12.10
Suspend ok, resume with blank screen, no backlight, but system was fully
function
*Not an expert; actually, I have no idea what I'm doing*
See my post here: http://lists.xen.org/archives/html/xen-
devel/2013-01/msg00941.html
The correct values should be returned already via rdmsr if
cpureq=dom0-kernel is specified on the Xen command line. Looking at
the LP report, it doesn't seem that this option was used.
Likely you will also need
For what it's worth, I started running this test case on the Amazon
Linux AMI (ami-aecd60c7) yesterday. It hasn't crashed. The DB is now 96
GiB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011792
Public bug reported:
After running for some time, several m1.large 64-bit instances started
repeatedly hitting this BUG_ON()
[525758.322281] BUG: Bad page state in process pdnsd pfn:1d1a6f
[525758.322290] page:88000b26f848 flags:887c count:2 mapcount:0
mapping:8800d2da0860
** Attachment added: i-af57f6d4.txt
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/1052275/+attachment/3321705/+files/i-af57f6d4.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052275
** Attachment added: i-b557f6ce.txt
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/1052275/+attachment/3321706/+files/i-b557f6ce.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052275
@Matt, when you produce those cpu stacktraces, how do you do that? Is
that from a dump or somehow tapping into the still running instance?
@smb, these are traces from running, but unresponsive, instances. I pull
the traces from the vCPU context in the hypervisor, then resolve symbols
from the
We've observed this on another instance running 12.04, ami-3c994355,
with a read-heavy postgresql load.
CPU0
rip: 8105e51a try_to_wake_up+0xca
flags: 1202 i nz
rsp: 880f22deb7d0
rax: 0004 rcx: 880f22deb900 rdx: 0082
rbx: 880c633196e0 rsi:
CPU stack traces from a hi1.4xlarge PV instance running ami-8baa73e2:
CPU 0 is the only running CPU. The others are blocked.
CPU0
rip: 8105711a try_to_wake_up+0xca
flags: 1202 i nz
rsp: 880f22dfc870
rax: 0008 rcx: rdx: 0002
rbx:
Stack traces from a second hi1.4xlarge running ami-8baa73e2:
CPU0
rip: 8105711a try_to_wake_up+0xca
flags: 1202 i nz
rsp: 880f22dfc740
rax: 0006 rcx: 880f22dfc870 rdx: 0082
rbx: 880b13d9 rsi: rdi: 0001
rbp:
This has been observed on https://launchpad.net/ubuntu/oneiric/+package
/linux-image-3.0.0-17-virtual
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: oneiric
** Summary changed:
- Scheduler deadlock running 3.0.0-20-virtual on c1.xlarge EC2 instance
+
Due to the nature of the issue encountered, we cannot run this command.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011792
Public bug reported:
Scheduler deadlocks have been observed on c1.xlarge EC2 instances
running 10.04.3 LTS with the 3.0.0-20-virtual Oneiric backport kernel.
The symptoms appear similar to bug 929941, where multiple CPUs are
waiting on scheduler runqueue locks. But in this case, only a few CPUs
vCPUs 0, 2 and 3 are stuck waiting on a spinlock. vCPU 1 is running with
the EIP showing various values inside try_to_wake_up()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011792
Title:
We've had a customer report a very similar looking lockup on
3.0.0-20-virtual. Full version info, 3.0.0-20-virtual (buildd@yellow)
(gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1) ) #34~lucid1-Ubuntu SMP Wed
May 2 17:24:41 UTC 2012 (Ubuntu 3.0.0-20.34~lucid1-virtual 3.0.30)
--
You received this bug
I've never been able to reproduce the problem with synthetic workloads.
I've asked customers that experience the lockup regularly to test the v3
builds in an environment that won't cause production problems, but
haven't received results.
--
You received this bug notification because you are a
This has also been observed on c1.xlarge, adjusting the summary
** Summary changed:
- Kernel deadlock in scheduler on m2.{2,4}xlarge EC2 instance
+ Kernel deadlock in scheduler on multiple EC2 instance types
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The required CONFIG_XEN_COMPAT value for ec2 is documented here:
http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/AdvancedUsers.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
$ git clone git://kernel.ubuntu.com/smb/ubuntu-lucid.git
Cloning into ubuntu-lucid...
remote: error: Could not read b43f7c4d8d293aa9f47a7094852ebd5355e4f38f
remote: fatal: Failed to traverse parents of commit
3becab1d2df01d54a4e889cf2d69ccb902cd43c3
remote: aborting due to possible repository
Stefan,
Which commit has the race condition comment? I'm aware of a problem with
SUSE's kernel with regard to PV ticketlocks and HYPERVISOR_poll(), but I
don't see any mention in upstream 3.2.x or XenLinux 2.6.18.
Your 10.04 2.6.32-era kernel doesn't have ticketlocks, so the underlying
I also suspect something going sideways in the PV spinlock code, but
nothing has changed in the underlying hardware or hypervisor in this
area. There have been bugs in the PV spinlock code in the past,
including using mb() instead of barrier() in the unlock path, which
could cause the VCPU holding
** Attachment added: /proc/interrupts as an attachment
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/929941/+attachment/2736482/+files/proc-interrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Overnight an instance running 2.6.32-316 locked up. The stack traces are
attached.
** Attachment added: stack traces from instance running 2.6.32-316
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/929941/+attachment/2730182/+files/i-804475e2.txt
--
You received this bug
Private bug reported:
After running for some indeterminate period of time, the 2.6.32-341-ec2
and 2.6.32-342-ec2 kernels stop responding when running on m2.2xlarge
EC2 instances. No console output is emitted. Stack dumps gathered by
examining CPU context information show that all VCPUs are stuck
** Attachment added: stack traces from instance running 2.6.32-341 (1/2)
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/929941/+attachment/2728701/+files/ubuntu-deadlock-2.6.32-341-1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/929941
Title:
Kernel deadlock in scheduler on m2.2xlarge EC2 instance
To manage notifications about this bug go to:
** Attachment added: stack traces from instance running 2.6.32-341 (2/2)
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/929941/+attachment/2728702/+files/ubuntu-deadlock-2.6.32-341-2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: stack traces from instance running 2.6.32-342 (1/1)
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/929941/+attachment/2728703/+files/ubuntu-deadlock-2.6.32-342-1.txt
** Visibility changed to: Private
--
You received this bug notification because you are a
Stefan,
The ec2 kernels already have xen-netfront and xen-blkfront compiled in.
If xen-platform-pci was also compiled in, or included in the initramfs,
then the HW emulation will be unplugged properly and you'll switch over
to the PV drivers. The following results in PV drivers for the root
Public bug reported:
The following soft lockup is seen randomly on m2.2xlarge instances in
EC2:
[1284451.875485] BUG: soft lockup - CPU#3 stuck for 61s! [identify:24060]
[1284451.875485] Modules linked in: ipv6 ipt_REJECT ipt_LOG xt_limit
nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919431
Title:
CPU soft lockup in Xen PTE allocation on m2.2xlarge instances
To manage notifications about this bug go to:
The hypercall fails due to invalid write permissions on the page that's
attempting to be pinned. Perhaps the page that's being pinned for PTEs
was reused?
One fix that was applied to the upstream kernel for such problems was
this:
I think that the root cause is a corrupted p2m_host[] list via a PV-GRUB
bug. Updated PV-GRUB AKIs are now available. These can be used in us-
east-1 to verify the fix:
32-bit: aki-805ea7e9
64-bit: aki-825ea7eb
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The permanent fix for this is likely in PV-GRUB. See:
https://patchwork.kernel.org/patch/727511/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686692
Title:
natty kernel does not boot on ec2
The permanent fix for this is likely in PV-GRUB. See:
https://patchwork.kernel.org/patch/727511/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710754
Title:
natty kernel does not boot on t1.micro
I just installed natty narwhal on my dell 1420 and as soon as I punched
my sudo password to unlock my key to get on the wireless, my touchpad
stopped working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Mike,
You bring up a good point about CFS' need for good process time
accounting. I think that this upstream patch may fix a lot of problems:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8a22b9996b001c88f2bfb54c6de6a05fc39e177a
This patch is in 2.6.34.7, may
Are you using CONFIG_RELOCATABLE=y for your kernels? If so,
CONFIG_PHYSICAL_START should not be a factor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710754
Title:
natty kernel does not boot on
What is CONFIG_PHYSICAL_ALIGN?
-- Sent from my Palm Pre
On Feb 1, 2011 12:16 PM, Scott Moser smo...@canonical.com wrote:
On Tue, 1 Feb 2011, Matt Wilson wrote:
Are you using CONFIG_RELOCATABLE=y for your kernels? If so,
CONFIG_PHYSICAL_START should
We use:
CONFIG_PHYSICAL_START=0x100
CONFIG_PHYSICAL_ALIGN=0x100
It sounds like that works for you too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710754
Title:
natty kernel does not
I've done a lot of looking at this today. It feels like the problem may
lie in the process scheduler. When I pin the CPU burning process to CPU0
(through taskset -pc 0 $pid_printed_by_a_out), and pin a bash shell
also to CPU0, I see failure of the bash process to wake after sleeping
(i.e., it's
Alec,
Do any hung task kernel stack traces get emitted during your hangs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/708920
Title:
Strange 'fork/clone' blocking behavior under high cpu usage on
Jordan,
Do you see this behavior at boot, or only after your instance has been
up and running for a while?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/708920
Title:
Strange 'fork/clone' blocking
Alec,
Do you have instance IDs from your hanging instances?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/708920
Title:
Strange 'fork/clone' blocking behavior under high cpu usage on EC2
--
If anyone has a machine that they can get into the hanging state (with
fork() blocking), can you run run echo w /proc/sysrq-trigger as root
and post the results?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
Hi Mike,
Let's focus on the fork() hangs in this bug. It's true that the two
could be related, but the symptoms don't quite line up.
You say you can reproduce the behavior on 2.3.32-311. Do you have a
procedure for getting an instance into the broken state, so you can then
cause fork() hangs
If you have an instance in a state where fork() will hang if you spin a
CPU, it would be a good experiment to see if irqbalance helps at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/708920
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708920
Title:
Strange 'fork/clone' blocking behavior under high cpu usage on EC2
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This is a transcription of the test program from the youtube video:
#include unistd.h
#include stdlib.h
#include stdio.h
int main(int argc, char **argv) {
int children = 0;
int status;
int i = 0;
if (argc 2) {
printf(Usage: %s children\n, argv[0]);
return 1;
}
children =
On a system in this condition, sometimes hung task traces are seen:
kernel: [65098.694112] echo 0 /proc/sys/kernel/hung_task_timeout_secs
disables this message.
kernel: [65098.694117] cron D 880001885380 0 21248 569 0x
kernel: [65098.694121] 880772e25d20 0282
Private bug reported:
There have been reports of fork() hangs on Lucid when running on EC2.
See this YouTube video for an example:
http://www.youtube.com/watch?v=rbURfuAmtXw
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-305-ec2 2.6.32-305.9
ProcVersionSignature: User
It seems that this reproduction case only happens after the system has
been used for some unknown amount of time. At that point, fork() hangs
can be triggered at will. If the instance is rebooted, the test case no
longer causes hangs.
--
You received this bug notification because you are a
Attaching /proc/slabinfo from a system that can be used to cause fork()
hangs.
** Attachment added: /proc/slabinfo from a sick instance
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/708920/+attachment/1811279/+files/slabinfo.txt
--
You received this bug notification because you
Some discussions on this are at http://twitter.com/#!/mjmalone
Video posted by
http://twitter.com/#!/jordansissel/status/30421571315175425
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/708920
Title:
The following kernel stack was captured on a system in fork() hangs
state via echo t /proc/sysrq-trigger. The code for libctest is here:
https://gist.github.com/2d2b78987ea451c2edd6
6[853486.204130] libctest R running task0 13658 1417
0x
4[853486.204132]
Gavin,
Can you reproduce the issue at will? I'm struggling to find a way to
reproduce the issue on a freshly booted instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/708920
Title:
Strange
Mike, can you click on the affects me for this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/708920
Title:
Strange 'fork/clone' blocking behavior under high cpu usage on EC2
--
ubuntu-bugs
*** This bug is a duplicate of bug 664645 ***
https://bugs.launchpad.net/bugs/664645
Public bug reported:
Binary package hint: alsa-utils
trying to install guarddog firewall from software centre
ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: alsa-utils 1.0.23-2ubuntu3.3
*** This bug is a duplicate of bug 664645 ***
https://bugs.launchpad.net/bugs/664645
--
package alsa-utils 1.0.23-2ubuntu3.3 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/664708
You received this bug
I can confim that this still exists in Karmic Koala.
--
libx11-data: compose ellipsis problem
https://bugs.launchpad.net/bugs/415667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm seeing this too, after upgrading 8.10 to 9.04. It happens in Pidgin,
Firefox and gnome-terminal, but NOT for some reason in xterm or urxvt.
My locale is en_NZ.UTF-8. I'll attach the requested logs.
--
libx11-data: compose ellipsis problem
https://bugs.launchpad.net/bugs/415667
You received
** Attachment added: lspci -vvnn output
http://launchpadlibrarian.net/32971888/lspci-vvnn.log
--
libx11-data: compose ellipsis problem
https://bugs.launchpad.net/bugs/415667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Xorg log
http://launchpadlibrarian.net/32971969/Xorg.0.log
--
libx11-data: compose ellipsis problem
https://bugs.launchpad.net/bugs/415667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: Xorg old
http://launchpadlibrarian.net/32972005/Xorg.0.log.old
--
libx11-data: compose ellipsis problem
https://bugs.launchpad.net/bugs/415667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm not sure where this should go either, but I agree that it would be
really nice to have nagios3 packaged up.
Maybe I should take a try at it.
--
Package Nagios3 and plugins
https://bugs.launchpad.net/bugs/227595
You received this bug notification because you are a member of Ubuntu
Bugs,
I just discovered this bug when I read the man page for mkfifo and then
tried to read the info for mkfifo.
I followed foolishchild's advice:
cd /usr/share/info
sudo gunzip coreutils.info.gz
sudo vim coreutils.info
comment out (delete?) the first END-INFO-DIR-ENTRY and
Yeah, I think my way will work fine. And if not, we'll hear about it
quickly!
:)
--
/etc/init.d/kannel depends on nonexistant /var/run/kannel directory
https://bugs.launchpad.net/bugs/187356
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Hi David,
Do we need to fix your problems before we fix my problem?
By the way, I've been poking around to see how other init scripts deal
with the fact that /var/run is flushed after every reboot.
This is how /etc/init.d/klogd makes sure that it has a subdirectory in
/var/run:
case $1 in
Public bug reported:
Binary package hint: kannel
The /etc/init.d/kannel script tries to put files inside /var/run/kannel.
That directory doesn't exist and gets erased every time.
I suggest adding something sort of like this into the /etc/init.d/kannel
script:
# Create the PIDFILES dir if it
78 matches
Mail list logo
