Public bug reported:
In doing regression testing of the 4.4.0-116 kernel with the server
certification tools, the miscellanea/call-trace-check test failed on one
system. (Maybe more, too; this was the first system to finish the
tests.) This test simply looks for the string "Call Trace" in
/var/log
Joseph, I'm having problems doing that because of the VirtualBox kernel
modules, which don't want to compile for the 4.16 kernel. Here's what I
get why I try to re-install dkms and virtualbox-dkms:
$ sudo apt-get install dkms virtualbox-dkms
Reading package lists... Done
Building dependency tree
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053630/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748901
Title:
Sy
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053627/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/174
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053628/+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/1748901
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053626/+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/1748901
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053624/+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/1748901
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053632/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053625/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053629/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748901
Titl
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053631/+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/1748901
Title:
Sy
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053623/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748901
Title:
Syst
apport information
** Tags added: apport-collected
** Description changed:
Some (maybe all) kernels in the 4.13.0 series are hanging with
Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox
VM, the VM's window appears, clears to black, and then the mouse
freezes. I do
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053620/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748901
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053619/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748901
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053621/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17489
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053618/+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/1748901
Title:
System
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1748901/+attachment/5053622/+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/1748901
Title:
Syst
Public bug reported:
Some (maybe all) kernels in the 4.13.0 series are hanging with
Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox
VM, the VM's window appears, clears to black, and then the mouse
freezes. I do NOT see any BIOS/EFI information or boot loader in the VM;
the
This happened to me on a do-release-upgrade update from Xubuntu 17.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747138
Title:
package resolvconf 1.79ubuntu9 failed to install/upgrade: triggers
A further update: This problem does NOT occur under Artful on the Dell
PowerEdge T610 with the following kernel:
$ uname -a
Linux hogplum 4.13.0-30-generic #33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
I have not yet tested with Xenial or with other kernel series on
This bug also affects hogplum, a Dell PowerEdge T610, running Ubuntu
14.04 with a 3.13.0-140 kernel. Here's the uname data from it:
$ uname -a
Linux hogplum 3.13.0-140-generic #189-Ubuntu SMP Mon Jan 15 16:06:29 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Running "sudo fwts uefirtmisc" causes a rebo
I ran it half a dozen times with your latest kernel and it seemed fine,
aside from the usual "error -19" messages. To be sure it's the right
one, here's the kernel version information:
ubuntu@oil-boldore:~$ uname -a
Linux oil-boldore 4.13.0-25-generic #29~lp1733662PatchInMainline SMP Thu Jan 18
1
That seems to have fixed it! I've run the test script six or seven times
on both kernels, with nary a hiccup (aside from the "error -19" messages
with the 4.13 kernel). Below is the reported kernel information from
both your builds, just to be sure I booted the correct kernels.
$ uname -a
Linux oi
I was unable to reproduce this problem on the Dell T110; however, I did
notice that it failed the test at the point where the T710 rebooted.
("Stress test for UEFI miscellaneous runtime service")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I tried running apport-collect, as requested by the Ubuntu Kernel Bot,
but it didn't work; it tried to open a (text-based) browser, but that
hung on "Opening socket", presumably because the system in question
is behind strict firewalls in 1SS.
** Changed in: linux (Ubuntu)
Status: Triag
I've managed to isolate this to the fwts "uefirtmisc" test:
$ sudo fwts uefirtmisc
Running 1 tests, results appended to results.log
Test: UEFI miscellaneous runtime service interface tests.
Test for UEFI miscellaneous runtime service interfaces. 1 passed, 5 skipped
Timeout,
Joseph,
The first run of your latest kernel completed; however, I noticed the
following in the dmesg output:
[ 426.281083]
==
[ 426.286615] BUG: KASAN: use-after-free in find_first_bit+0x1f/0x80
[ 426.291841] Read of size 8 at ad
Yes, it still exists. To confirm the kernel version:
$ uname -a
Linux oil-boldore 4.15.0-041500rc7-generic #201801072330 SMP Sun Jan 7 23:31:29
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
The system hung bringing CPU 11 back online, with the following dmesg
output:
[ 101.179624] smpboot: Booting N
You're right. (I've got too many kernels installed on that system!) When
I tested again, it got through eight runs without problems, beyond the
"error -19" message. Here's the uname information, just to be sure:
$ uname -a
Linux oil-boldore 4.13.0-21-generic #24~lp1733662Revert SMP Mon Jan 8 15:35
I'm afraid that one fails, too, on the second run when bringing CPU10
back online. Here's the dmesg output:
[ 154.987312] smpboot: Booting Node 1 Processor 10 APIC 0x14
[ 154.992953] BUG: unable to handle kernel paging request at 317865646e69
[ 154.993932] IP: __kmalloc_track_caller+0x97/0x
That one completed two runs, but on the second run, dmesg included the
following message at one point:
[ 240.841694] kernel BUG at
/home/jsalisbury/bugs/lp1733662/ubuntu-artful/mm/slub.c:3878!
[ 240.842765] invalid opcode: [#1] SMP
[ 240.843718] Modules linked in: nls_iso8859_1 intel_rapl
That one completed its first run, but then crashed when bringing CPU 14
back online, with the following dmesg output:
[ 163.176945] [ cut here ]
[ 163.176949] kernel BUG at
/home/jsalisbury/bugs/lp1733662/ubuntu-artful/mm/slub.c:3878!
[ 163.178043] invalid opcode:
Joseph, that one also completed six runs with no problems except the
"error -19" messages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733662
Title:
System hang with Linux kernel 4.13, not with 4
Thanks, Joseph. My break was good; I hope yours was, too!
That latest version you posted completed half a dozen runs of the test
script without incident, aside from the "error -19" messages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Dylan, yes, your description at
https://answers.launchpad.net/ubuntu/+question/662540 is an instance of
this bug.
Your repair was OK, but a bit overkill. Specifically, a chroot was not
really necessary, since the file-juggling could all be done without
that. Of course, as this is a bug in ubiquity
That one ran our test script half a dozen times without failure, albeit
with the "Error -19" messages in the dmesg output.
Note that I'm about to EOD, so I probably won't get to the next one
until next year. Have a good holiday, Joseph!
--
You received this bug notification because you are a mem
That one hung much like the others, with the system responding only to
very basic commands (mostly bash internals), although the dmesg output
continued further after the kernel bug message. Here's the dmesg output:
[ 107.652875] EDAC MC0: Giving out device to module sb_edac.c controller
Haswell
The build from http://kernel.ubuntu.com/~jsalisbury/lp1733662/
successfully completed about six runs of the test script, albeit with
the verbose dmesg output that includes the "EDAC sbridge: Failed to
register device with error -19" messages.
--
You received this bug notification because you are
That one completed one run of the test OK, but then crashed on the
second one, when bringing CPU 15 back online, with the following dmesg
output:
[ 160.596312] EDAC MC0: Giving out device to module sb_edac.c controller
Haswell SrcID#1_Ha#0: DEV :ff:12.0 (INTERRUPT)
[ 160.596537] EDAC MC1: G
OK, I've run tests now. The system did not crash or otherwise misbehave,
but the dmesg output was quite verbose, and included "error -19"
messages. Here's a sample (apparently for just one CPU core; this
sequence was repeated quite a few times):
[ 439.341956] smpboot: Booting Node 1 Processor 31
There's nothing at the URL you posted, Joseph. Do I just need to give it
more time to build, or is something wrong?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733662
Title:
System hang with Linu
That one failed (the script stopped running after taking CPU 9 offline)
with the following dmesg output:
[ 119.360953] [ cut here ]
[ 119.360955] kernel BUG at
/home/jsalisbury/bugs/lp1734327/ac8f82a-revert-test/ubuntu-artful/mm/slub.c:3878!
[ 119.361405] invalid opcode
4.13.0-12 seems to be OK; I ran it seven or eight times without a
failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733662
Title:
System hang with Linux kernel 4.13, not with 4.10
To manage n
4.13.0-14 failed when offlining CPU 9:
[ 104.500965] [ cut here ]
[ 104.500968] kernel BUG at /build/linux-0p6sBa/linux-4.13.0/mm/slub.c:3878!
[ 104.501256] invalid opcode: [#1] SMP
[ 104.501422] Modules linked in: nls_iso8859_1 kvm_intel kvm irqbypass joydev
inpu
The upstream 4.14.0 kernel DOES segfault, but none of the 4.13-series
kernels does. Some of the 4.13-series kernels do have "error -19" or
"error -22" messages in their dmesg output, though.
I've tried the kernel at https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/unstable/+build/1335
Joseph, I've just tested 4.15-rc4, and the script crashed and the system
became responsive to only the simplest commands when bringing CPU 9 back
up, accompanied by this out of dmesg:
[ 166.722460] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L,
BIOS C240M4.2.0.10c.0.032320160820 0
Andres,
I've checked that, and it does *NOT* fix the problem; the system fails
to boot after a deployment in exactly the same way it did before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Lee, I tried http://162.213.35.187/proposed/streams/v1/index.json
earlier, in response to Andres' suggestion, and that stream did not
help. (See comments #24 and #25.) If you think that stream has changed
since I did my testing on November 27, I'm happy to try again; but if
not, it doesn't help.
-
I'd just like to emphasize that, although a change to always install the
linux-signed kernel on AMD64 systems is necessary to fix this bug, it's
not sufficient to fix the bug. As noted in my comment #25 (and
elsewhere), another change is also required -- either a change to Shim
or GRUB (I don't kno
Here are some more test runs on boldore, using different kernels, mostly
from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D. The
attachment is a tarball containing dmesg output associated with runs of
the cpu_offlining script. An overview:
* 4.10.0-38-generic: No hang or misbehavior; verb
I've tried upgrading to the latest development kernel, from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/, and re-
testing. The details of the problem have changed (but they were never
100% consistent), but the problem definitely still exists. I'm attaching
dmesg output from three runs:
Here's the install log, cut-and-pasted from the MAAS web UI, for the
latest installation. Note that after the node shut down, I restarted it
and disabled Secure Boot to get it to complete.
** Attachment added: "install-log.txt"
https://bugs.launchpad.net/maas/+bug/1711203/+attachment/5015350/+
I've tried this and the problem persists. Note that MAAS *IS* installing
the signed kernel, which is necessary but insufficient for a fix; the
problem seems to be that Shim/GRUB is becoming confused by the handoff
from the PXE-boot version of GRUB to the GRUB stored on the hard disk.
If my analysis
Andres, I've downloaded that file, but I have no idea where to put it. I
can't find a file called index.json on my MAAS server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deploymen
I've discovered what may be the same bug on another system -- feebas, a
Cisco UCS C220 M4 (Intel Series v3), with the same CPU type (Intel Xeon
E5-2640 v3). I'm attaching dmesg output from it, but on this particular
run, the computer did not hang indefinitely, although it did become
unresponsive fo
Here's the dmesg output from another run on feebas. In this case, the
system has become unresponsive via SSH, although the console remains
active.
** Attachment added: "Another dmesg output from feebas"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1733662/+attachment/5012438/+files
Public bug reported:
In doing Ubuntu 17.10 regression testing, we've encountered one computer
(boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times
when running our cpu_offlining test. This test attempts to take all the
CPU cores offline except one, then brings them back online
** Attachment added: "dmesg output with a 4.13 kernel"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1733662/+attachment/5012385/+files/dmesg-output-4.13.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
To be clear, although installing the signed kernel package is necessary,
a failure to do this is NOT the source of this bug, which seems to
relate to how Shim and/or GRUB handle the MAAS boot path, which involves
Shim and GRUB being PXE-booted and then chainloaded to (Shim and?) GRUB
on the hard di
Philip, after installation, MAAS configures nodes to PXE-boot, but the
GRUB delivered chainloads a locally-installed GRUB on the hard disk. The
PXE-boot part is a requirement of the MAAS environment. (If systems
booted straight from the hard disk, the MAAS server could not re-deploy
them.) Re-think
Steve, there have been two problems that are feeding into this bug
report, both on MAAS installations to EFI-based nodes, which must
normally PXE-boot so that the MAAS server can maintain control of its
nodes:
* After GRUB package updates, the GRUB package would add GRUB to the start
of the boot
I'm copying my comment #49 from bug #1642298 here
Blake, your proposal makes sense on the surface; however, there are
cases where it would cause problems. For instance, suppose that, outside
of a MAAS environment, somebody installs Ubuntu, then installs Windows
in a dual-boot configuration, th
Blake, your proposal makes sense on the surface; however, there are
cases where it would cause problems. For instance, suppose that, outside
of a MAAS environment, somebody installs Ubuntu, then installs Windows
in a dual-boot configuration, then re-installs Ubuntu because Windows
grabbed the boot
Ooh, lots of activity while I typed my last comment.
This may be beating a dead horse, but concerning comment #42, Andres, I
tried that command and got similar output:
$ ipmitool -H 10.20.30.13 -I lanplus -U user -P pass chassis bootdev pxe
options=persistent,efiboot
Set Boot Device to pxe
$ ipm
Andres, it's perfectly possible to redeploy a system after it's been set
to boot from the local disk by either adjusting the boot order on the
node or by deleting GRUB from the local disk. I don't recall which of
those I did in the procedure noted in my comment #2, but it was likely
one of those th
Andres, fundamentally the problem is that EFI provides no means to
control the boot order via IPMI; it's set via non-IPMI firmware
mechanisms or via the efibootmgr tool in Ubuntu. That is, point #4 in
your first list is incorrect, and everything falls apart after that.
When a GRUB package uses efib
Mathieu, I've tested on all three affected servers in our possession
(jolteon, ostwald, and moltres), and the grubnetx64.efi.signed binary
works on all of them (delivered via the MAAS server, of course). Thanks
for this fix!
I've also tested on three systems that did not have this problem
(wildora
Mathieu, how would I install this? As I understand it, I'd need to
replace /var/lib/maas/boot-resources/current/grubx64.efi on the MAAS
server with a GRUB built for network booting, but it's unclear to me in
which of those packages a suitable file exists.
--
You received this bug notification bec
Another update on this:
I updated jolteon (the Lenovo x3550 M5 that was the original source of
this bug report) with the latest firmware I could find (v.2.21, build
TBE126Q, dated 2016-11-18) and reproduced the original bug. It appears
to be unchanged, with one twist: At one point, the system was
Is there any progress on this? I'm encountering similar problems on at
least two more systems now (moltres and ostwald, which are Quanta S910
X31E and Supermicro SYS-6018R-WTR servers, respectively). I've managed
to find a working firmware setup to get the Quanta booting reliably, but
the Supermicr
This bug is ***NOT FIXED!*** I've just confirmed it still exists on two
systems. Note that the bug is specific to the 3.13 kernel series (it
does not affect 4.4 or other kernel series), and to the EFI stub loader
(it doesn't manifest when using GRUB 2, for instance).
** Changed in: linux (Ubuntu)
Dimitrenko, I'm afraid this bug is NOT FIXED. I've just tested with
3.13.0-123 (installed today via apt-get), and the system still hangs
with it.
Joseph, I'm still willing and able to test more kernels.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: linux (
I'm seeing a regression on this bug, as of 14 June 2017. If it's curtin-
common on the MAAS server that's relevant, here's the version
information:
$ dpkg -s curtin-common | grep Version
Version: 0.1.0~bzr470-0ubuntu1~16.04.1
The suggestion of creating the GRUB/Ubuntu entry but putting it lower i
This problem seems to have disappeared with sbsigntool version
0.6-0ubuntu10.1.
--
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 notifications about th
At the request of Samantha Jian-Pielak, I've run some additional tests.
I installed Ubuntu 16.04.2 desktop on a computer using an ASUS P8-H77I
motherboard with an American Megatrends 2.31 UEFI and a Toshiba 3TB hard
disk, putting a ~700 MB /boot partition at the END of the disk, above
the 2 TiB mar
Joseph,
Do you have more kernels for me to test? It's been a while since you
gave me the last one
--
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
** Merge proposal linked:
https://code.launchpad.net/~rodsmith/checkbox-support/+git/checkbox-support/+merge/320862
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675091
Title:
Mellanox MT27500
** Changed in: checkbox (Ubuntu)
Assignee: (unassigned) => Rod Smith (rodsmith)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Rod Smith (rodsmith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've been looking at this (on and off), and it seems to reach close to
the end of UdevadmParser.run() (in udevadm.py) with the data intact, but
it gets lost in the last line or in transferring control out, in the
main() function of the udev_resource script.
--
You received this bug notification b
** 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 t
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 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
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 3
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 notifi
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
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 3.13.
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 b
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 3.13.0-101-gener
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 3
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 si
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~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 ker
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 not
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 no
The linux-image-3.13.0-031300 kernel boots fine, Joseph.
--
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)
linux-image-3.14.0-031400rc1-generic also 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
linux-image-3.14.0-031400-generic also 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 man
The linux-image-3.16.0-031600-generic 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)
Abalan, you're subscribed to the "linux in Ubuntu" package, which is why
you're receiving bug reports:
https://bugs.launchpad.net/~fyma/+packagebugs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16561
101 - 200 of 281 matches
Mail list logo
