Seeing the same on Ubuntu 18.04.3 with the HWE kernel, 5.0.0-25-generic
AMD A6-9225 RADEON R4
This appears to be tied in to the problems resuming the laptop from
suspended (black screen, flashing cursor)
--
You received this bug notification because you are a member of Kernel
Packages, which is
I'm confused. Do you need verification or not? Cosmic is not
specifically supported on our platform, and there are no plans at the
moment to support non-LTS releases that I know of. I can certainly test
this if needs be, though.
--
You received this bug notification because you are a member of
Patch submitted to netdev: https://marc.info/?l=linux-
netdev&m=153695411427176&w=2
--
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/1790652
Title:
Oracle cosmic image does not find broadc
I've been able to replicate the situation with a few different
distributions. It seems to only occur with VMs. When I tried 4.18.7 on
a bare metal instance, there was no problem.
We believe we've isolated the kernel commit that is introducing the
problem to 707e7e96602675beb5e09bb994195663da6eb5
I haven't specifically seen that one, but I'll check in with both the
Oracle Linux team and our Hypervisor team.
--
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/1790652
Title:
Oracle cosm
I took a step back from doing bisecting and focussed on creating a
replication scenario, which I've done successfully.
ipconfig is struggling to handle things when two interfaces are present
and sending out DHCP requests, even if one interface doesn't get a
response.
Here's what I've done:
Using
I'm continuing to bisect the mainline linux kernel, and also trying to
see if I can create a straightforward reproducible example.
First focus on bisecting was between 4.5 and 4.6, to figure out what
changed to suddenly have ipconfig working. I've tracked it down to this
using bisect, and validat
I've tried every version in the v4 series, and a few in v3. None prior
to (and including) v4.0.0 will boot, none output anything on the screen
to give me a clue why they're not booting.
So far:
v4.0 = won't boot
v4.1 = ipconfig bug
v4.2 = ipconfig bug
v4.3 = ipconfig bug
v4.4 = ipconfig bug
v4.5
The more I look at this, the more I'm convinced *most* of the real
problem lies in that ipconfig tool. Yes, various kernel changes seem to
make it alter between working & not working under the circumstances
(which is bizarre), but unless something is specifically interfering
with the inter-process
My apologies for any lack of clarity.
I tested against the head of ubuntu-xenial, reverting just that commit
and it fixed it.
I tested against the head of the mainstream kernel and it didn't (last
night I tried 4.9, 4.8, 4.5, 4.4, 4.2 tags of the mainstream kernel and
in every place I find the ge
I tried reverting that specific commit from upstream, but that didn't
resolve the issue. Time for a new round of bisecting the kernel, this
time using mainline.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
This seems to make no sense to me, as a layman anyway.
I checked out the 4.4.0-58.79 tag, reverted that one commit and
confirmed I have a booting 4.4.0-58-generic that'll happily DHCP in the
initrd environment on multiple boots. It really does seem like,
somehow, that commit is the source of the
I bisected again, and again it came back to that mount point change.
This seems so bizarre.
$ git bisect log
# bad: [6d4f0a79e5a307b6fd3ee3cc5bbb2fcb701b09db] UBUNTU: Ubuntu-4.4.0-57.78
# good: [db5f146d309e70067dae57798c9ea679af835aa7] UBUNTU: Ubuntu-4.4.0-53.74
git bisect start 'Ubuntu-4.4.0-57.
I see where I messed up.. I'll try the bisect again.
--
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/1652348
Title:
initrd dhcp fails / ignores valid response
Status in linux package in
Okay... I can't help but think I made a mistake somewhere in the
bisecting process, but it seems to have isolated
fd4b5fa6e3487d15ede746f92601af008b2abbc0 as the bad commit
$ git bisect log
# bad: [6d4f0a79e5a307b6fd3ee3cc5bbb2fcb701b09db] UBUNTU: Ubuntu-4.4.0-57.78
# good: [40a98f0e91bcc062babd0
I'll take a fresh look in the morning, but ran into this:
make[1]: Leaving directory
'/home/ubuntu/storage/ubuntu-xenial/debian/build/build-generic/zfs/module'
Debug: module-check-generic
install -d
/home/ubuntu/storage/ubuntu-xenial/debian.master/abi/4.4.0-54.76/amd64
find /home/ubuntu/storage/
I can give that a shot, following the instructions here:
https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions
--
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/16523
I should clarify, I know for certain that 4.4.0-51 is stable and
reliable (and doesn't exhibit the bug). As part of our attempt to
verify everything was correct with the installation we had a system run
from Wednesday before Thanksgiving, all the way through to the following
Monday, during which t
Okay.. this is interesting. It seems like the Ubuntu dev version of
4.10 is actually intermittently failing (?!) I guess the next thing to
do here is keep rebooting on this version of the kernel and see how
often the bug occurs vs doesn't occur, so I can get a feel for a
reasonable number of time
Rolling that command against master fails too:
ubuntu@Beta:~/linux$ mainline-build-one
afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc xenial
*** BUILDING: commit:afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc series:xenial
abinum: ...
full_version<4.4.0>
version<4.4.0>
long
abinum<040400>
fatal: 'xenial' do
Gah.. okay https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
--
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/1652348
Title:
initrd dhcp fails / ignores valid response
Status in linux pac
Ahh, I see where the kteam tools stuff is supposed to come from.
It's not clear if I'm supposed to go down that route and use the
mainline-build-one script or not when trying to build the kernel in this
case. If I use the mainline-build-one tool:
$ mainline-build-one afd2ff9b7e1b367172f18ba7f693
I'll get started on it. This might take a while to do.
A couple of quick observations:
1) we haven't validated that mainline 4.4.0 actually works. I only know
certain Ubuntu versions of the 4.4.0 kernel work. Given how much seems
to be changing between Ubuntu releases of it, that seems a risky
Tried and tested (the current up-to-date kernels at the time of
posting):
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/linux-
headers-4.10.0-041000rc1-generic_4.10.0-041000rc1.201612252031_amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/linux-
image-4.10.0-041000rc1-g
I've also confirmed the bug is present all the way back in
4.4.0-21-generic, and is present in 4.8.0-34-generic from yakkety-
proposed.
--
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/165234
I've worked my way back through the kernels. The bug, as it was
(avoided by ip=dhcp in the kernel command line), was in effect in
version 4.4.0-38-generic. It was fixed in 4.4.0-42-generic. This is
the state of play so far with kernels I've tested:
linux-image-4.4.0-38-generic - Affected
linux-
apport-collect doesn't exist in initrd. I'm unable to supply the
requested information.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Attachment added: "pcap from dhcp server side of 'ipconfig -t "dhcp" -d
"ens2f0" '"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795819/+files/worked.pcap
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The checksum invalid mentioned in the pcap is interesting, but happens
in both failed and successful, so I'm not sure it's relevant.
--
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/1652348
** Attachment added: "pcap from dhcp server side of inird startup doing dhcp"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795820/+files/failed.pcap
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Attachment added: "Working 4.4.0-53 initrd"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795794/+files/initrd.img-4.4.0-53-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
** Attachment added: "4.4.0-57 "broken" initrd"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795793/+files/initrd.img-4.4.0-57-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Public bug reported:
Between kernel versions 4.4.0-53 and 4.4.0-57 a bug has been
(re?)introduced that is breaking dhcp booting in the initrd environment.
This is stopping instances that use iscsi storage from being able to
connect.
Over serial console it outputs:
IP-Config: no response after 2
There isn't a kernel in proposed at the moment, but I've tested using
the latest in yakkety and it seems to be working fine.
I don't have a simple replication case for the bug, unfortunately. It
just seems to happen for (hand-wavey guess) 50% of boots.
So far I've got this 4.8.0-19-generic kerne
gzip'd copy of the kern.log showing the error.
** Attachment added: "kern.log.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626679/+attachment/4746377/+files/kern.log.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Public bug reported:
On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger
off a kernel panic against somepart of the NVMe driver it looks like,
after which the logs get filled with entries over and over again of:
"bad: scheduling from the idle thread!"
Here's the initial stack
36 matches
Mail list logo
