Seeing this on bare metal (Dell R740xd) with Ubuntu 18.04 and linux-
image-generic-hwe-18.04 (5.3.0-62-generic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1820063
Title:
[Hyper-V]
Excellent, thank you. FYI, the actual application I'm using which
requires nbd is snf-image-creator.
I agree it makes sense to remove most modules relating to physical
hardware from the kvm kernel, but loopback and networking modules are
useful.
I did a quick diff. "rbd" might be another one to
Public bug reported:
The "nbd" module is missing from linux-modules-XXX-kvm in bionic
root@ubuntu:~# /sbin/modprobe nbd max_part=16
modprobe: FATAL: Module nbd not found in directory /lib/modules/4.15.0-1021-kvm
root@ubuntu:~# uname -a
Linux ubuntu 4.15.0-1021-kvm #21-Ubuntu SMP Tue Aug 28
BTW, I reproduced the same problem in a different (and arguably more
realistic) scenario:
- install ubuntu 16.04
- configure networking with a bridge interface but a port member that doesn't
exist when you next boot up (e.g. make br0 with a member which is a USB
ethernet adapter, and then
> The user would already have setup in the BIOS menu to either be in
UEFI or BIOS mode prior to installation. This would also be user error.
Really? What's wrong with:
- buy computer
- plug in USB stick
- boot it up
--
You received this bug notification because you are a member of Kernel
Let me try one last time to separate the issues.
** The UEFI issue (a side issue)
The installer works in two completely different ways, depending on
whether the system booted via UEFI or BIOS. But it does not show whether
it is installing in UEFI or BIOS mode. Hence the user has little way,
Not sure about tag "bios-outdated-0055". The latest BIOS for this machine is
0055: see
https://downloadcenter.intel.com/product/85254/Intel-NUC-Kit-NUC5CPYH
As for live CD: no, it can't be reproduced that way. The specific
sequence is:
* Boot from USB in UEFI mode
* Repartition the disk, but
apport information
** Tags added: apport-collected
** Description changed:
Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
machines (with 8GB RAM and Crucial BX200 SSD).
There is a problem running on this machine, but the problem report here
is specifically about how
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735768/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1609475
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735772/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735774/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735779/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735773/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1609475
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735770/+files/Card0.Codecs.codec.2.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735777/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735769/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735775/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735778/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735776/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1609475/+attachment/4735771/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Separate issue #1609715 raised about installer continuing with UEFI
installation even if there is no ESP.
This specific hardware is now working fine.
I would still like recovery mode to be more predictable in the event of
startup problems: after all, the whole point of recovery mode is for
when
The specific problem with NUC seems to have been my fault: I didn't
realise it was installing in UEFI mode, so did not create an ESP (EFI
System Partition).
It was strange that it managed to even start booting the kernel at all;
I can only guess that the hardware was not correctly initialized.
I will happily file a separate bug for NUC5CPYH not booting properly
with 16.04.1, and I will test it with a mainline kernel.
However this bug is to report that "recovery mode" is completely broken
in this situation, which makes it especially hard to debug the problem.
If I cannot open a console
Public bug reported:
Ubuntu 14.04 with linux-generic-lts-xenial kernel (4.4.0), running on
Macmini6,2
Installed package bcmwl-kernel-source, which gives me this module for my
wlan0:
# lsmod | grep wl
wl 6365184 0
cfg80211 557056 1 wl
Machine immediately and
After updating to that kernel (under 14.04), the problem is not fixed.
$ uname -a
Linux kit1 3.19.0-031900rc4-generic #201501112135 SMP Sun Jan 11 21:36:48 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
* The LXC instance still does not start if the memtuneswap_hard_limit
First you need to convince me that this is a kernel bug.
How come libvirt's LXC driver is trying to use a /sys API that doesn't
even exist in the very latest mainline kernel?
I would guess that either libvirt assumes the kernel is built with some
option that the Ubuntu kernel hasn't been built
I got access the the boxes in the data centre (there are two).
The one which was on 3.13 kernel: VGA output was fine
The one which was on 3.2 kernel: VGA output was fine
However when I upgraded the 3.2 to 3.8, the VGA output was still fine :-(
This was using a different VGA monitor than I had
Intermediate update: the machine boots with the linux-
image-3.14.0-031400rc6-generic kernel, it still reports EDID errors,
dmesg info below.
Unfortunately the machine is now in data centre so I can't tell if it is
generating a VGA output or not! I'll update this when I'm next able to
get a
Public bug reported:
Installed Ubuntu 12.04.4 Server 64-bit on Intel D2700MUD motherboard
(Atom D2700), 4GB RAM
Installation process went fine. But after rebooting, after the grub
screen the display was completely blank. This is using a VGA connection
to an external monitor (the board also has a
Forgot to add: in the things I tried, I also did a full apt-get update;
apt-get dist-upgrade, so I was on the latest 3.8.0 kernel version.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have observed this as a more general problem with any sysctl setting
for all interfaces.
For example, try:
sysctl -a | grep '^net\.ipv4\.conf.*send_redirects'
sysctl -w net.ipv4.conf.all.send_redirects=0
sysctl -a | grep '^net\.ipv4\.conf.*send_redirects'
sysctl -w
The answer for IPv4 was figured out here:
http://unix.stackexchange.com/questions/90443/sysctl-proc-sys-net-ipv46-conf-whats-the-difference-between-all-defau
The behaviour is non-obvious. For some settings the interface and 'all'
settings are ANDed together; for others they are OR'd, for others
Same for 12.04.3 LTS. During dist-upgrade:
...
Setting up linux-headers-generic-lts-raring (3.8.0.32.32) ...
Setting up linux-signed-image-3.8.0-32-generic (3.8.0-32.47~precise1) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image
33 matches
Mail list logo
