[Bug 666211] Re: maverick on ec2 64bit ext4 deadlock
As a matter of practicality, given this and other problematic bugs w/ EC2 on the stock Maverick and Lucid kernels (there are several that range from annoying to flat-out unreliable or un-(re)-bootable), I had been running my Maverick-based instances with the Karmic kernels pretty successfully for a long time (by adding Karmic repos to sources.list and installing linux-image-2.6.31-307-ec2 from them and deleting the Maverick kernel as part of my cloud-init script on first boot). I'd recommend that to you now (and you still can if you must, using the old-releases.ubuntu.com mirror), but Karmic has now been dropped from support some months back. This leaves basically no stable, supported option for an Ubuntu-based distribution with a reasonably-decent quality kernel for EC2. I'd recommend switching distros; these problems have been simmering far too long to expect a sudden fix to come your way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666211 Title: maverick on ec2 64bit ext4 deadlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/666211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 666348] Re: Reboot notification should not require X
Auto-closing bugs without reading them because you never got around to fixing them is an *awesome* QA plan. The bug isn't missing any data :P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666348 Title: Reboot notification should not require X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/666348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 636474] Re: xtables-addons-source will not compile
Maverick still doesn't have this commit released, any plans to do so? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/636474 Title: xtables-addons-source will not compile -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727814] Re: [Maverick] Reboot of linux-virtual hangs on EC2
Stefan, your workaround would almost be acceptable if this were the only bug in play. However, for those of us booting Maverick AMIs for PV- grub, and then using cloud-init to auto-downgrade the kernel to Karmic's or auto-upgrade to Natty's (because let's face it, so far Lucid and Maverick have yet to have a production-capable kernel for EC2 use), lack of a reboot method that works from a shellscript inside the instance itself without sensitive keys is a no-go for even initially booting from Maverick AMIs with this bug in them. Luckily the older Maverick AMIs from before this bug was introduced are still available... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727814 Title: [Maverick] Reboot of linux-virtual hangs on EC2 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727814] Re: [Maverick] Reboot of linux-virtual hangs on EC2
Anyone have a userland workaround (other than ec2-reboot-instances of own instance-id, which requires auth keys on the node...) for getting an ec2 node on these kernels to reboot itself successfully? Also: note that once we have a release kernel w/ the fix, new Maverick AMIs will have to go out before the problem is really solved (or else you can't really reboot to the fixed kernel from a fresh image after update). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727814 Title: [Maverick] Reboot of linux-virtual hangs on EC2 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 669096] Re: Kernel divide by zero panic in sched.c:update_sd_lb_stats
This looks very likely to be related upstream: https://bugzilla.kernel.org/show_bug.cgi?id=16991 ** Bug watch added: Linux Kernel Bug Tracker #16991 http://bugzilla.kernel.org/show_bug.cgi?id=16991 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669096 Title: Kernel divide by zero panic in sched.c:update_sd_lb_stats -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 669096] Re: Kernel divide by zero panic in sched.c:update_sd_lb_stats
Ah, and from there I see a link to a different LP bug which has more details as well, should probably close this as a dupe of that one: https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/614853 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669096 Title: Kernel divide by zero panic in sched.c:update_sd_lb_stats -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666348] Re: Reboot notification should not require X
If you haven't fixed it, then yes, it's still an issue. The bug was found in Maverick. I don't have the time or inclination to test later versions of the distribution, but either way you need to fix it in Maverick, and perhaps look at your other kernel packages to see if they need fixing as well. FWIW, this bug doesn't need kernel logs or anything else, it's a pretty straightforward and simple issue once you look at it, and the problem lies solely in the kernel package scripts (the postinst script), it's not a runtime problem with the kernel itself. I'll restate the original description in simpler terms if that would help: How Things Work Today: --- The kernel postinst script executes /usr/share/update-notifier/notify- reboot-required if it exists, to notify that a reboot is required due to kernel upgrade. That script comes from the package update-notifier. update-notifier (among perhaps other things) creates the file /var/run/reboot-required, which is the documented hook by which other services and scripts detect that a reboot is required (such as the dynamic /etc/motd stuff, or any kind of administrative scripts the systems admin might write). The Problem: --- update-notifier is a graphical X-windows package, and is not normally installed on headless servers. Thus on headless servers, /var/run /reboot-required is never created when kernels are installed/upgraded. The simple fix is to have the kernel postinst script create the /var/run /reboot-required file itself, in addition to launching the update- notifier hook. ** Changed in: linux (Ubuntu) Status: Incomplete = New ** Tags removed: needs-kernel-logs needs-upstream-testing -- Reboot notification should not require X https://bugs.launchpad.net/bugs/666348 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/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
Stefan: the ~32 vs ~64GB memory issue is very likely orthogonal and has a separate bug now (bug 667796). This issue is solely about intel_idle vs certain CPU types under Amazon's EC2 (Xen) environment. m2.4xlarge in us-east reproduces the crash on boot readily (and also happens to exhibit the memory limit issue), and c1.xlarge reproduces it some of the time (depending which hardware you are randomly assigned). -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 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/mailman/listinfo/ubuntu-bugs
[Bug 667796] Re: kernel only recognizes 32G of memory
My experience so far has been that the Lucid kernels do not have this memory size bug, only the Maverick ones. -- kernel only recognizes 32G of memory https://bugs.launchpad.net/bugs/667796 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/mailman/listinfo/ubuntu-bugs
[Bug 669096] [NEW] Kernel divide by zero panic in sched.c:update_sd_lb_stats
Public bug reported: host was an m2.2xlarge instance in us-east-1 (with EBS root and data volumes) running stock lucid and serving primarily as a MySQL server. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-308-ec2 2.6.32-308.16 ProcVersionSignature: Ubuntu 2.6.32-308.16-ec2 2.6.32.15+drm33.5 Uname: Linux 2.6.32-308-ec2 x86_64 Architecture: amd64 Date: Sun Oct 31 09:58:32 2010 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-ec2 ** Affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Kernel divide by zero panic in sched.c:update_sd_lb_stats https://bugs.launchpad.net/bugs/669096 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/mailman/listinfo/ubuntu-bugs
[Bug 669096] Re: Kernel divide by zero panic in sched.c:update_sd_lb_stats
** Attachment added: crash output from ec2-get-console-output https://bugs.launchpad.net/bugs/669096/+attachment/1718175/+files/Console.txt -- Kernel divide by zero panic in sched.c:update_sd_lb_stats https://bugs.launchpad.net/bugs/669096 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/mailman/listinfo/ubuntu-bugs
[Bug 669096] Re: Kernel divide by zero panic in sched.c:update_sd_lb_stats
The part we crashed in is the code that calculates cpu scheduler stats, with a divide by zero. I've done some searching around on git.kernel.org and lxr.linux.no, and I don't see where any similar existing problem has been caught and fixed yet upstream through 2.6.32, but it could be non-obvious. Looking at linux_2.6.32-25.45.diff.gz from the relevant apt source for -virtual, I see a lot of patches to sched.c, some of which introduce new division operations. It wouldn't surprise me if the bug was in there somewhere. -- Kernel divide by zero panic in sched.c:update_sd_lb_stats https://bugs.launchpad.net/bugs/669096 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/mailman/listinfo/ubuntu-bugs
[Bug 668434] [NEW] ec2-bundle-vol should copy filesystem label
Public bug reported: Binary package hint: ec2-ami-tools ec2-bundle-vol needs to copy the filesystem label from the source system's rootfs to the rootfs image, so that things like LABEL=euc- rootfs in /etc/fstab work (which is used in Maverick, which makes ec2 -bundle-vol fail to create bootable images for Maverick by default). ** Affects: ec2-ami-tools (Ubuntu) Importance: Undecided Status: New -- ec2-bundle-vol should copy filesystem label https://bugs.launchpad.net/bugs/668434 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-ami-tools in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 668434] [NEW] ec2-bundle-vol should copy filesystem label
Public bug reported: Binary package hint: ec2-ami-tools ec2-bundle-vol needs to copy the filesystem label from the source system's rootfs to the rootfs image, so that things like LABEL=euc- rootfs in /etc/fstab work (which is used in Maverick, which makes ec2 -bundle-vol fail to create bootable images for Maverick by default). ** Affects: ec2-ami-tools (Ubuntu) Importance: Undecided Status: New -- ec2-bundle-vol should copy filesystem label https://bugs.launchpad.net/bugs/668434 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/mailman/listinfo/ubuntu-bugs
[Bug 667793] Re: euca-bundle-vol should copy filesystem label
Did you check on this bug in euca-bundle-vol? The broken AMI I referenced in the other thread was actually made with ec2-bundle-vol. -- euca-bundle-vol should copy filesystem label https://bugs.launchpad.net/bugs/667793 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667793] Re: euca-bundle-vol should copy filesystem label
Did you mean here or with Amazon? I've opened a feature-request case with Amazon as a customer in any case. BTW, the simple commandline way to get the label is: /sbin/blkid -s LABEL -o value /dev/sda1 -- euca-bundle-vol should copy filesystem label https://bugs.launchpad.net/bugs/667793 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667793] Re: euca-bundle-vol should copy filesystem label
Did you check on this bug in euca-bundle-vol? The broken AMI I referenced in the other thread was actually made with ec2-bundle-vol. -- euca-bundle-vol should copy filesystem label https://bugs.launchpad.net/bugs/667793 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/mailman/listinfo/ubuntu-bugs
[Bug 667793] Re: euca-bundle-vol should copy filesystem label
Did you mean here or with Amazon? I've opened a feature-request case with Amazon as a customer in any case. BTW, the simple commandline way to get the label is: /sbin/blkid -s LABEL -o value /dev/sda1 -- euca-bundle-vol should copy filesystem label https://bugs.launchpad.net/bugs/667793 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/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
I wasn't able to boot on ami-d258acbb on m2.4xlarge. It seemed to come up without the special kernel options: [0.00] Linux version 2.6.35-22-virtual (bui...@allspice) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu4) ) #33-Ubuntu SMP Sun Sep 19 21:05:42 UTC 2010 (Ubuntu 2.6.35-22.33-virtual 2.6.35.4) [0.00] Command line: root=LABEL=uec-rootfs ro console=hvc0 And then hung in intel_idle as expected. Also, confirmed apparent 32GB memory limit on this kernel + machine type. -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 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/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
What's the method for making the S3 AMIs by the way? When I tried before, I tried just doing standard ec2-bundle-vol stuff inside of a fixed Maverick, but my first attempts failed because of the root device not having LABEL=euc-rootfs in the newly-launched instances, and the second generation I manually switched the root to /dev/sda1, but had other mysterious boot failures. Is there some standard tool or script used to package the official AMIs that we can use to produce identical results (with small changes)? -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 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/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
Well, I had a hunch this morning that perhaps my test AMI was faulty (perhaps some stupid issue related to block-device mapping, etc, which varies between the variations on c1.xlarge), since it wasn't packaged by the same methods/tools as the official one. It seems this may be the case. Going off the hint from Mikael that m2.4xlarge may exhibit the problems more reliably, I did the following experiment this morning using EBS root persistence to make the change, rather than custom instance-store AMIs: 1) Booted ami-548c783d (Maverick 64-bit EBS official) on m1.large in us-east-1. 2) Logged into this machine and edited /boot/grub/menu.lst manually to add intel_idle.max_cstate=0 idle=nomwait to the kernel bootflags. 3) Rebooted, instance came up fine with messages showing intel_idle disabled. 4) Stopped the instance, used ec2-modify-instance-attributes to move it to type m2.4xlarge 5) Booted on m2.4xlarge successfully, no crash (cpuinfo shows Xeon X5550, which is also model 26 like the failing c1.xlarges) 6) Edited menu.lst to remove the added bootflags and rebooted the instance again, (staying on same m2.4xlarge hardware) 7) Instance crashed on boot in intel_idle code as always Given these results, I think the kernel flags will workaround this issue, I just built a bad test AMI during my first tests yesterday. Could someone rebuild a set of Maverick AMIs with these flags added from the get-go using whatever the official method of packaging Maverick AMIs is, for public testing among those of us experiencing the bug? -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 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/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
I tried to look in more detail at the crash this evening, because it's really causing me a lot of headache now. The most recent time I tried to boot a new c1.xlarge in us-east-1 this evening, I had to cycle through the crash/terminate/relaunch cycle 7 times before I got a working instance. I don't have a patch or answer yet, but I have a lot of hints: 1) c1.xlarge seems to be going through some changes of underlying CPU/hardware, which could explain the randomness. It probably depends which hardware you land on. The older ones are Xeon E5410 and the newer ones are Xeon E5506. So far the only times I've gotten non-crashed launches and thought to check, they've all been the E5410's. 2) The exact instruction throwing invalid opcode is MONITOR (0f 01 c8). The instructions MONITOR and MWAIT are used for efficient idling on newer CPUs, which I guess is the whole point of the intel_idle code we're crashing in. 3) These are not the sorts of instructions that can be executed in a VM environment like Xen without special support. Googling reveals discussions/patches to Xen for supporting these instructions in various ways (either as a hypercall encapsulating the whole monitor/wait pair, or masking the capability in CPUID so that Linux doesn't detect support and doesn't try to use it all). Various related links: http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00043.html http://markmail.org/thread/terab63w744x3m2r http://www.sfr-fresh.com/unix/misc/xen-4.0.1.tar.gz:a/xen-4.0.1/docs/misc/cpuid-config-for-guest.txt 4) intel_idle can be effectively disabled from the kernel commandline with intel_idle.max_cstate=0 ( http://kerneltrap.org/mailarchive/git- commits-head/2010/5/28/40718 ), which will fall back on acpi_idle behavior. If it still crashes, there's also a commandline flag idle=nomwait which might prevent acpi_idle from using mwait as well. I don't know at this point where the true bug lies. It could be that the intel_idle code needs to make an exception to its detection routines under Xen. It could be that some of Amazon's Xen hosts are configured differently (wrt CPUID masking for mwait) than others. It could be any of a number of related things. However, I suspect new AMIs for Maverick on EC2 that disable mwait from the commandline in grub.conf/menu.lst per above might fix this. I'll try making my own AMIs with this change in the morning and see how it goes. -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 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/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
I forgot to add above: on the E5410 c1.xlarge's that do boot successfully, the kernel output contains: Oct 26 07:37:55 ip-10-243-51-207 kernel: [0.210255] intel_idle: MWAIT substates: 0x2220 Oct 26 07:37:55 ip-10-243-51-207 kernel: [0.210257] intel_idle: does not run on family 6 model 23 Which I believe means that intel_idle figured out that it needs to disable itself on these. The E5506's are model 26 rather than 23. The intel_idle code has a case statement that switches on this model number. Model 23 (0x17) is commented out for FUTURE_USE and thus falls through to the does not run condition with the output above. Model 26 (0x1A) has a case statement and will attempt to use intel_idle support. -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 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/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
So far my test instances with one or both of the MWAIT-related kernel flags have given even worse results than the original: They boot showing intel_idle disabled on E5410 nodes only, but the (assumed) E5506 nodes just terminate themselves quickly with no console log output at all (even after waiting a while). I've opened a web support ticket with Amazon referencing my test AMI and this bug report to ask for their input. -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 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/mailman/listinfo/ubuntu-bugs
[Bug 666348] [NEW] Reboot notification should not require X
Public bug reported: The postinst script for Maverick (and probably other releases') kernels ultimately signal that a reboot is required by checking for and executing (if exists) /usr/share/update-notifier/notify-reboot- required. That script in turn generates /var/run/reboot-required, which then other scripts (unattended-upgrade, for example) look for to indicate that a package update requires a reboot. For that matter, /var/run/reboot-required is what any other scripts would want to look for (sysadmin's own scripts on a remote headless server? EC2?). The meta-problem here is that update-notifier is not normally installed in a headless server environment like EC2, and depends on the whole mess of X dependencies since it's related to graphical notifications as well. Thus the notify-reboot-required script does not exist, thus /var/run /reboot-required does not get generated. The best fix would probably be to have the kernel postinst script create /var/run/reboot-required directly itself, in addition to executing update-notifier hooks if that package happens to be installed. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Reboot notification should not require X https://bugs.launchpad.net/bugs/666348 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/mailman/listinfo/ubuntu-bugs
[Bug 666348] Re: Reboot notification should not require X
[ s/exit/exist/ in near the end of the second paragraph above, typo ] Also, as a temporary workaround, I've found that the kernel postinst script *does* directly create /var/run/do-not-hibernate when a kernel is upgraded, so that can be used to determine needs reboot as well for now. ** Description changed: - - The postinst script for Maverick (and probably other releases') kernels ultimately signal that a reboot is required by checking for and executing (if exists) /usr/share/update-notifier/notify-reboot-required. That script in turn generates /var/run/reboot-required, which then other scripts (unattended-upgrade, for example) look for to indicate that a package update requires a reboot. For that matter, /var/run/reboot-required is what any other scripts would want to look for (sysadmin's own scripts on a remote headless server? EC2?). + The postinst script for Maverick (and probably other releases') kernels + ultimately signal that a reboot is required by checking for and + executing (if exists) /usr/share/update-notifier/notify-reboot- + required. That script in turn generates /var/run/reboot-required, + which then other scripts (unattended-upgrade, for example) look for to + indicate that a package update requires a reboot. For that matter, + /var/run/reboot-required is what any other scripts would want to look + for (sysadmin's own scripts on a remote headless server? EC2?). The meta-problem here is that update-notifier is not normally installed in a headless server environment like EC2, and depends on the whole mess of X dependencies since it's related to graphical notifications as well. - Thus the notify-reboot-required script does not exit, thus /var/run + Thus the notify-reboot-required script does not exist, thus /var/run /reboot-required does not get generated. The best fix would probably be to have the kernel postinst script create /var/run/reboot-required directly itself, in addition to executing update-notifier hooks if that package happens to be installed. -- Reboot notification should not require X https://bugs.launchpad.net/bugs/666348 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/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
Having the same issue on c1.xlarge in us-east-1 (kernel crash on boot related to intel_idle). I've booted the Maverick release AMI several times on m1.large instances fine, but I seem to have a 50%+ failure rate getting it to initially boot without crashing on c1.xlarge. You're going to need to roll new AMIs when/if this bug is fixed, because the failure means inability boot far enough to get the kernel upgraded in the first place. FWIW, I'm only even trying Maverick because of the unresolved kernel issues with Lucid on EC2 that have been hard to pin down (divide by zero panics in network-related areas of the kernel, apparent disk i/o lockups triggered by runaway CPU load triggered by apt somehow, etc...). What's going on with kernels on EC2? Is anyone at Ubuntu actually testing them? ** Attachment added: console.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/651370/+attachment/1710799/+files/console.txt -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 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/mailman/listinfo/ubuntu-bugs
[Bug 289087] Re: Missing linux-image-debug packages and metapackages since Intrepid
As above, the ddebs link is useless for me. I'm running the current latest release of Ubuntu server, fully updated. My kernel is 2.6.31-17-server. There is no vmlinux shipped, there doesn't appear to be one available via apt, and even the ddebs link noted above only contains packages for kernel 2.6.32-11. This is pretty simple stuff guys. When a user decides to break out oprofile to solve problems, there should be *some* mechanism by which they can obtain a valid vmlinux for the vendor-built kernel. One that doesn't involve jumping through the hoops of figure out the vendor's kernel build process and rebuild a new kernel exactly like the one they shipped you, pointlessly, just to get a corresponding copy of vmlinux. Given the current situation, I don't see why you even bothered putting the oprofile tools in apt or enabling oprofile in your kernel builds... -- Missing linux-image-debug packages and metapackages since Intrepid https://bugs.launchpad.net/bugs/289087 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/mailman/listinfo/ubuntu-bugs
