I've confirmed Simos's observation. I've identified two variants of the
problem, doing a test installation under VirtualBox:
1) The disk is unpartitioned (either with no partition table or with a GPT in
which no partitions are defined) when ubiquity is launched. In this case, the
error message
FWIW, this is fixed upstream (in GPT fdisk 1.0.1), and bug 1514400 now
requests an update to that version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285197
Title:
growpart failed in ppc64el
FWIW, this is fixed upstream (in GPT fdisk 1.0.1), and bug 1514400 now
requests an update to that version.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/1285197
Title:
growpart
I'm the upstream author of GPT fdisk. This bug will be fixed in version
1.0.1, which I hope to release later today.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/924028
Title:
I'm the upstream author of GPT fdisk. This bug will be fixed in version
1.0.1, which I hope to release later today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924028
Title:
sgdisk 0.8.1-1build1:
I've released GPT fdisk 1.0.1. I know it's way too late to get it into
Wily, so either 1.0.1 can be SRU'd or I can provide a patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924028
Title:
I've released GPT fdisk 1.0.1. I know it's way too late to get it into
Wily, so either 1.0.1 can be SRU'd or I can provide a patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/924028
I've released gdisk 1.0.1 this weekend, which addresses this
documentation issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/1445456
Title:
Manpage documentation for exit status
I've released gdisk 1.0.1 this weekend, which addresses this
documentation issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445456
Title:
Manpage documentation for exit status 3 is not clear
What does this have to do with gdisk? It sounds like it's describing a
GRUB issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/941089
Title:
Force /etc/crypttab entry for
What does this have to do with gdisk? It sounds like it's describing a
GRUB issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941089
Title:
Force /etc/crypttab entry for inclusion in initrd.
To
The upstream GPT fdisk project provides separate "gdisk" (containing
gdisk, cgdisk, and sgdisk binaries) and "fixparts" (containing the
fixparts binary) packages, since FixParts is intended to manipulate MBR
partition tables and the other binaries work on GPT disks. The Ubuntu
"gdisk" package,
The upstream GPT fdisk project provides separate "gdisk" (containing
gdisk, cgdisk, and sgdisk binaries) and "fixparts" (containing the
fixparts binary) packages, since FixParts is intended to manipulate MBR
partition tables and the other binaries work on GPT disks. The Ubuntu
"gdisk" package,
Public bug reported:
As per my e-mail with Steve Langasek, the "debian" directory for the
shim package contains some material that is Canonical's property, but
the debian/copyright file does not reflect this fact and so should be
updated.
** Affects: shim (Ubuntu)
Importance: Undecided
This is a conflict between the Ubuntu-provided gdisk 0.8.8 package and
the upstream-provided fixparts-1.0.1 package. Upstream (that's me)
provides separate gdisk and fixparts packages, whereas Ubuntu provides a
single gdisk package that includes both gdisk and fixparts binaries.
To overcome the
This is a conflict between the Ubuntu-provided gdisk 0.8.8 package and
the upstream-provided fixparts-1.0.1 package. Upstream (that's me)
provides separate gdisk and fixparts packages, whereas Ubuntu provides a
single gdisk package that includes both gdisk and fixparts binaries.
To overcome the
I'm not sure, Brian. I've done installs both on real hardware with 4GiB
of RAM and under VirtualBox with less than that, and I don't recall
which installation triggered this bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I agree with Jarno; these three bugs are related, but this one (at
least) is not an exact duplicate of the other two. This one is
explicitly and exclusively about mkinitramfs, whereas the other two are
more general and can be triggered in other ways. (Those two might be
duplicates of each other,
I've tested with both v4.7-rc1 and v4.7-rc3 and saw the same results as
with the stock 14.04, 14.04.4, and 16.04 kernels. If it ever worked
properly, I'm not sure when it was. (We initially misinterpreted the
problem as a mis-labeled USB port, so I'm not sure how far back the
problem goes.)
**
Public bug reported:
On a Lenovo x3650 M5 server running Ubuntu 14.04 GA, mapping of USB
flash drives to USB2 or USB3 busses is irregular. For instance, with two
USB3 ADATA USB flash drives plugged into the system, one on an external
port that's marked with the blue USB3 color and the other
** Attachment added: ""sudo lshw" output from the affected system"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1593291/+attachment/4685024/+files/lshw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: ""sudo lsusb -v" output from the affected system"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1593291/+attachment/4685025/+files/lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm unable to complete the requested apport-collect run. The system in
question is in 1SS, and I suspect the 1SS firewalls are blocking access
to required sites; when I run it, after getting some prompts, it hangs
with "Opening socket..." displayed at the bottom of my Terminal window.
** Changed
I'm attaching a tarball with additional information. This includes runs
that generate these errors on three systems in the certification lab in
1SS: rollinia, wildorange, and hogplum. I'm providing both sample runs
and CPU information ("lscpu" and "cat /proc/cpuinfo" output) for each
system. I've
I've re-run my original test script and your command on the three
servers whose results I posted yesterday, and the error messages have
disappeared, so this looks good from my end. Thanks for the quick fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm having this problem with a mirror (using Trusty) of Xenial files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/368419
Title:
apt-mirror i18n files
To manage notifications about this bug go
Here's some version information, taken from the machine's iLO:
Product NameProLiant DL385p Gen8
UUID37303137-3332-584D-5134-303830335450
Server Serial NumberMXQ40803TP
Product ID 710723-001
System ROM A28 02/06/2014
Backup System ROM 11/02/2013
Integrated Remote
An update: After re-deploying with Ubuntu 14.04.3, the error logged in
the iLO and shown in the screen shot disappears; the hardware now
registers as OK. Thus, I think this error is simply another symptom of
the kernel panic.
--
You received this bug notification because you are a member of
Note that the same problem occurs with the 4.2 kernel in 16.04 (a pre-
release from a week or two ago). I haven't yet tested the firmware
workaround with 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Disabling IOMMU did indeed enable us to boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550481
Title:
hpsa driver causing kernel panics on HP ProLiant DL385p Gen8
To manage notifications
** Attachment added: "dmesg output from successful boot of 14.04.1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550481/+attachment/4582024/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Doing regression testing on Ubuntu 14.04.4, we've found a big one: An HP
ProLiant DL385p Gen8 kernel panics on startup with the default kernel
for that version (4.2.0-27-generic). The server's display (see screen
shot taken via its BMC's remote KVM) shows a kernel panic that
** Attachment added: "output of "lspci -vnvn" after successful boot of 14.04.1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550481/+attachment/4582025/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: blocks-hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550481
Title:
hpsa driver causing kernel panics on HP ProLiant DL385p Gen8
To manage notifications about this bug
The bug may or may not still exist, but I've been unable to reproduce it
since deleting and re-creating the "maas" user on the affected system,
as noted in comment #3, above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The bug may or may not still exist, but I've been unable to reproduce it
since deleting and re-creating the "maas" user on the affected system,
as noted in comment #3, above.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
Public bug reported:
After an update to my openjdk-7-jre (to 7u95-2.6.4-0ubuntu0.14.04.1) and
openjdk-7-jre-headless (to 7u95-2.6.4-0ubuntu0.14.04.1), javaws has
begun producing "Network connect error" messages when I try to connect
to my Avocent 2020 KVM's remote-viewing console. Attached is a
I see something similar, but in my case it's an external USB drive
that's causing the problem; if I unplug the external disk, gsmartcontrol
launches normally. My output is slightly different from what's reported
earlier, so I'm presenting it here:
$ sudo gsmartcontrol
(gsmartcontrol:7931):
It's possible to customize the size of the /boot partition on a Desktop
system by using the (poorly-named, IMHO) "Something Else" partitioning
option; however, this also requires explicitly setting up all other
partitions. This can be a rather high hurdle for inexperienced users. Of
course, such
I've just reproduced the problem with 14.04 GA and a 3.13.0-24-generic
kernel:
$ for x in `seq 0 9`; do start=`date +"%s"`; sleep 60; stop=`date +"%s"`; echo
"$stop - $start"|bc; done
63
60
60
60
61
60
60
60
60
61
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
In doing certification testing on an HP DL385p Gen8 server with an AMD
Opteron(tm) Processor 6320 CPU, we've run into some clock issues, as
illustrated by the following:
$ for x in `seq 0 9`; do start=`date +"%s"`; sleep 60; stop=`date +"%s"`; echo
"$stop - $start"|bc; done
Public bug reported:
On an EFI-based computer, the GRUB binary (grubx64.efi) will normally
reside on the EFI System Partition (ESP); however, this binary relies on
a configuration file (grub.cfg) that resides in Ubuntu's /boot/grub
directory. This split is a result of history -- on BIOS-based
Public bug reported:
I'm trying to perform 16.04 server certification work on a Lenovo x3550
M5 server (jolteon in OIL). Part of this task involves ensuring that the
server boots with Secure Boot active. Unfortunately, this has eluded me.
Using MAAS, the server enlists, commissions, and (mostly)
Public bug reported:
A small but increasing number of disks use 4KiB native ("4Kn") sectors
-- that is, they use 4096-byte physical sectors (which is now common)
*AND* 4096-byte LOGICAL sectors (which is uncommon, "translation" to
512-byte sectors being the norm). Today, most 4Kn disks are
I've tried to reproduce Alexander's report of an EFI-mode GRUB failure
without success:
I first created a VirtualBox BIOS-mode Ubuntu 15.10 installation in a
4TiB virtual disk. To "stack the deck" in favor of a failure, I created
a separate /boot partition at the END of the disk, ensuring that
This is fixed upstream somewhere between 0.8.8 (included in Ubuntu
14.04) and 1.01 (to be included in Ubuntu 16.04).
** Summary changed:
- sgdisk only saves 11 characters with change-name option
+ sgdisk only saves 35 characters with change-name option
--
You received this bug notification
** Attachment added: "Automated crash dump"
https://bugs.launchpad.net/ubuntu/+source/sbsigntool/+bug/1574372/+attachment/4645831/+files/_usr_bin_sbsign.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The sbsign program in Ubuntu 16.04 is segfaulting randomly:
root@gil:/home/ubuntu# /usr/bin/sbsign --key
//etc/refind.d/keys/refind_local.key --cert
//etc/refind.d/keys/refind_local.crt --output /tmp/refind_local/refind_x64.efi
/usr/share/refind/refind/refind_x64.efi
s/it did not occur with Ubuntu 16.04/it did not occur with Ubuntu 14.04/
Sorry for the typo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574372
Title:
sbsign crashes randomly
To manage
Note that memory_stress_ng is a script in the Checkbox certification
suite. The actual stress-ng command line should be:
timeout -s 9 $end_time stress-ng --aggressive --verify --timeout
$runtime --brk 0
The exact values of $end_time and $runtime vary with the amount of
memory in the system --
Firmware updated to "A28 03/07/2016". This does not help; the system is
still showing clock skew.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564949
Title:
Severe latency/skew on AMD Opetron
*** This bug is a duplicate of bug 1564949 ***
https://bugs.launchpad.net/bugs/1564949
** This bug has been marked a duplicate of bug 1564949
Severe latency/skew on AMD Opetron processor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It should be run as root.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
To manage notifications about this bug go
Public bug reported:
When doing certification testing of Ubuntu 16.04 on a Lenovo x3550 M5,
we've found a Secure Boot failure. After installing via MAAS with Secure
Boot DISABLED, we've enabled Secure Boot. The following appears on the
screen (SOL session):
No key pressed. Preparing to boot
I've done some more experiments. After booting in the normal MAAS way
with Secure Boot disabled, I created an entry with efibootmgr to boot
directly from the local hard disk, bypassing MAAS and its PXE boot. The
system booted fine with this configuration, even after enabling Secure
Boot. Thus,
I find that I get crashes until ~/.nedit is populated. I've gotten in
the habit of copying that directory from a working system when
installing a new one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Contents of MAAS clusterd.log file showing activity
involved in failed boot."
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1578837/+attachment/4657252/+files/clusterd.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm attaching the contents of the /var/lib/maas/boot-
resources/snapshot-20160426-183112 directory on the MAAS server (minus
the ubuntu and custom directories, which contain OS images and are
therefore huge). This tarball includes the shim and GRUB images used in
this process. I'm also including
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578837
Title:
Secure Boot failure on Lenovo x3550 M5
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1466367 ***
https://bugs.launchpad.net/bugs/1466367
** This bug has been marked a duplicate of bug 1466367
Installer ask where to install boot loader during uefi installation
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
When installing Ubuntu in EFI mode to removable disks, Ubiquity installs
GRUB to EFI/ubuntu/grubx64.efi and Shim to EFI/ubuntu/shimx64.efi on the
first EFI System Partition (ESP) detected -- often an ESP on an internal
disk. This creates several problems:
1) If the ESP
Public bug reported:
I'm trying to script a change to the automatic updating of servers, and
tried the following:
echo "debconf unattended-upgrades/enable_auto_updates boolean false" |
debconf-set-selections -
dpkg-reconfigure -fnoninteractive unattended-upgrades
The result, however, is a
fierabras66, please see comment #7 in this bug report for a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550481
Title:
hpsa driver causing kernel panics on HP ProLiant DL385p Gen8
To
linux-image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit6edf523
boots fine for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader broken in kernel
The linux-image-3.16.0-23-generic_3.16.0-23.31_amd64.deb kernel (with
its associated "extra" package) boots fine for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader
Joseph, I don't see the usual linux-image-* files at that URL. Could you
please double-check that and fix as necessary?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader
The linux-image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commitdaa829d
kernel boots fine for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader broken in kernel
Joseph,
I think there was a typo in your URL, since it was the same as from the
previous test. Since you noted a different commit number, I adjusted and
pulled the kernel from:
http://kernel.ubuntu.com/~jsalisbury/lp1649326/59ed4b6/
This kernel fails to boot, with the "failed to get file info
Joseph, the linux-
image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit74bdcac_amd64.deb
kernel also boots correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader
The linux-
image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commitf162bc9_amd64.deb
kernel boots fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader broken in kernel
I just did an "apt-get dist-upgrade", and I see there's now a 3.13.0-110
kernel, too. It also crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader broken in kernel
The kernel in linux-
image-3.13.0-9-generic_3.13.0-9.29~lp1649326_amd64.deb boots fine for
me.
Also, the newly-release 3.13.0-108 kernel in the regular repos does NOT
boot; it crashes like everything else since 3.13.0-101.
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "boot-failure-2.png screen shot mentioned in previous
comment."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+attachment/4826242/+files/boot-failure-2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The kernel in linux-
image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit3f049ea_amd64.deb
fails to boot, but in different ways that seem to be somewhat random:
* Sometimes the warnings "Failed to get file info size" and
"Failed to alloc highmem for files" appear.
* Sometimes, when launching
The 3.15.0-0.1 kernel boots fine for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
series)
To manage
Joseph, the 3.13.11-ckt39 kernel boots fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
series)
To manage
Joseph, the 3.19.0-79.87 kernel boots fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
series)
To manage
The linux-
image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit528f2d2_amd64.deb
kernel boots correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader broken in
Matthew, note that the change I was trying to make did not take effect.
This might be independent of the warning message, but it's the real
problem being reported. As noted, omitting "-fnoninteractive" enables it
to work, but as I'm trying to do this in a script, that omission is not
a reasonable
Public bug reported:
In Ubuntu 16.10, but not in 16.04, apt-key leaves /dev/null and
/dev/urandom open after exiting. Here's a procedure to replicate the
problem:
1. Install Ubuntu 16.10. (I used MAAS for this task.)
2. Install the "lsof" package (which is not installed by default).
3. Type
** Attachment added: ""lsof | grep dev" output from after running apt-key"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1634234/+attachment/4762666/+files/after.txt
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The lp1649326 version failed to boot for me, but in a different way from
the others on SOME launches -- rather than crashing VirtualBox with a
"guru meditation" dialog box, it displayed the following messages within
the emulated environment:
failed to get file info size
failed to alloc highmem
More kernels in that range:
* 3.13.0-91: OK
* 3.13.0-92: Bad
* 3.13.0-93: OK
* 3.13.0-95: OK
* 3.13.0-96: OK
* 3.13.0-98: OK
I installed all of these via "sudo apt-get install linux-image-
extra-{version}-generic". Versions not noted between 3.13.0-90 and
3.13.0-99 were reported by apt-get as
The plot thickens; it seems that this bug, or at least a variant of it,
may have existed as far back as 3.13.0-92. See this post in the Kubuntu
forums thread:
https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
kernels=396273=1#post396273
I've tested the 3.13.0-92 kernel and
Yes, I installed both linux-image and linux-image-extra for all the
kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI stub loader broken in kernel 3.13.0-101-generic (&
Thanks for the work on this so far, Colin. One point:
> I'm still not happy about the /usr/lib/plainbox-provider-
checkbox/bin/disk_stress_ng using timeout with a -9 (SIGKILL) to
terminate stress-ng stressors. Stress-ng stressors can be *cleanly*
terminated with a SIGALRM signal, this triggers
Public bug reported:
The EFI stub loader produces consistent boot errors when booting Trusty
starting with version 3.13.0-101-generic. This bug can be reproduced in
many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach
is:
1) Install an EFI shell on the computer and set it as
apport information
** Tags added: apport-collected
** Description changed:
The EFI stub loader produces consistent boot errors when booting Trusty
starting with version 3.13.0-101-generic. This bug can be reproduced in
many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790874/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790870/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790875/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790871/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790876/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790872/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790879/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790881/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I've tried with 3.13.0-100 and it worked. I tried with 3.13.0-106 and it
failed.
I've attached the requested apport-collect information from a 3.13.0-106
kernel; however, because of the nature of the bug, I had to boot that
kernel via GRUB 2, not via the EFI stub loader. The apport-collect
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790880/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790877/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1649326/+attachment/4790873/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649326
Title:
EFI
1 - 100 of 288 matches
Mail list logo
