Public bug reported:
With a Xenial kernel running in a VM (32 cores and 65536 MB RAM), the
following script hangs in the dd command:
==
#!/bin/bash
dd if=/dev/zero of=in.bin bs=1 seek=6442506751 count=1
cp in.bin out.
This bug causes maas testing to fail (at least the ntp test, because of
overlayfs and apparmor and ntp having a profile.) See
https://bugs.launchpad.net/maas/+bug/1677336
Hardware testing is a requirement for MAAS 2.2.
--
You received this bug notification because you are a member of Kernel
Pack
** Also affects: maas
Importance: Undecided
Status: New
--
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/1408106
Title:
attach_disconnected not sufficient for overlayfs
Status i
apport-collect is not really an option on the machine, nor should any of
that really provide any additional information that's not already in the
bug report. holler at me if I missed anything relevant.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
Following apw's excellent advice pointing to
https://www.v13.gr/blog/?p=378 and abusing another ipv6 address on the
afflicted host:
tcpdump -npi br0 ip6 and not port 22 | grep -i neigh
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br0, link-type EN10MB (Et
Public bug reported:
I have a xenial (4.4.0-24-generic) machine that loses ipv6 connectivity
every time I reboot the gateway it uses.
br0 is a bridge which has eth0.2 as its only member, with (currently) 6 "scope
global temporary deprecated dynamic" (privacy) addresses, and:
inet6 2601:282:8
However, given that eth0.2 is seeing the solicitation, and br0 isn't,
I'm leaning strongly toward the bridge code being slightly buggy.
My next test will be to do a non-promisc tcpdump on eth0.2 and see if
_THAT_ sees the traffic. That may take me a week before I can do it
though, due to schedule
One other tidbit: The gateway in question is using eth0.2 on a trunked
port to a Cisco WS-C2960G-24TC-L running
c2960-lanbasek9-mz.150-2.SE9.bin.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
4.6 test kernel (2dcd0af568b0cf583645c8a317dd12e344b1c72a would seem to
be the base) does not exhibit the bug.
--
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/1543683
Title:
Fails to dete
based on discussion, more work is needed.
** Changed in: linux (Ubuntu Xenial)
Status: Fix Released => In Progress
--
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/1543683
Title:
F
Said kernel appears to be good. The reshuffling of windows does not
occur (and I get two displays!!) In the worst case, I'd recommend
shipping xenial with 237ed86c reverted, if they can't get a fixed
version before our deadline.
Holler at me if there's another kernel for me to test.
thanks,
lam
The kernel in #45:
1) exhibits the window shuffling issue.
2) if I lock the screen, and sit back for a few seconds, the display blanks,
and then (almost immediately) unblanks. I would expect it to remain blanked
until there was mouse or keyboard activity.
I suspect that the next step is to inst
The kernel in comment #40 exhibits neither the original bug, nor the
window-shuffling bug. On a lark, I'd like tip 4.4.0-9 with the
"original" fix added (and 237ed86c NOT reverted). All of which assumes
that 237ed86c was not reverted as part of landing the fix.
Something about this feels like it
And I completely misstated myself. :(
What I think I want is: 237ed86c with the current patch for this bug
applied.
Here is what I'm seeing, and trying to isolate it to these two patches,
or if it's something yet newer that we'll need to bisect all over again:
With current xenial (4.4.0-13 and
Rereading #40, what exactly was that kernel? On rereading, it sounds
like it was top-of-tree (ish), with 237ed86c reverted and the fix added
-- or was it bonafide 237ed86c~1 + the fix? (on which hinges what the
kernel to try next is, but the last 2 paragraphs in #41 are still valid)
--
You rece
On the other hand, for the "completely unacceptable" part of the diff:
locking the screen results in the display going away or something, such
that X randomly moves windows from the right hand to the left and vice
versa. Just... No.
--
You received this bug notification because you are a member
4.4.0-9.24~lp1543683Commit8d409cb is a good kernel. (with the now
expected lag of ~1/2 second between the two displays refreshing during
boot at driver cutover.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Interestingly, while two displays show up in the lspci output, only the
one was detected and used.
lamont
--
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/1543683
Title:
Fails to detect (
Here is the boot... Interestingly, it shows 2 displays in lspci. I'm
not in front of the computer, so I can't exactly say if it found it or
not, but ISTR that it didn't show the device at all (in lspci) in the
bad kernels.
** Attachment added: "zz"
https://bugs.launchpad.net/ubuntu/+source/li
Works. Note that during boot, when it flashes (presumably over to the
kernel's i915 driver?) there is a noticible delay between the first
(00:02.0) display and the second (failing, 00:02.1) display coming up -
on the order of "under a second or two". I'm attaching the kernel log
from the boot, wh
d2e0 is good 74fc bad 237e bad. We have a winner: 237ed86c is the first
failing commit.
--
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/1543683
Title:
Fails to detect (second) display
S
23eafea6a9d1faac0588a5275d0c755cb261346e is good (with complaints from
the monitor about refreshrate out of range)
--
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/1543683
Title:
Fails to
That is, if it's convenient to just loop through and build all 7, then
throw them into ~jsalisubury/lp1543683/$REF, then I can smash through
the reboots in minimal time. (Getting tired of rebuilding my
workspace...)
--
You received this bug notification because you are a member of Kernel
Package
9eca6832f7254d49d25494da7d47c0f8a24f7862 is bad. In the interest of
letting me do the rest in one interruption of my primary worksurface,
would it be possible for you to build all 7 remaining versions (or throw
me a script..), and then I can just reboot a few times for completion.
I'm of the belie
e8cb8d69d125f56fa3ba5239b215a56718e2ca44 is bad.
--
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/1543683
Title:
Fails to detect (second) display
Status in linux package in Ubuntu:
Conf
40a4a5727f21a0e439d317aa99953e24467605eb fails.
--
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/1543683
Title:
Fails to detect (second) display
Status in linux package in Ubuntu:
Confi
717d84d67e3a95f440c37c7482681b3535fdc7e2 is bad.
--
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/1543683
Title:
Fails to detect (second) display
Status in linux package in Ubuntu:
Conf
c0f3f90cf454dd845dcc443afa4f0e312a8eaee0 is bad. (201602161109
timestamp on the kernel build, for confirmation)
--
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/1543683
Title:
Fails to det
b44a3d2a85c64208a57362a1728efb58a6556cd6 is bad.
--
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/1543683
Title:
Fails to detect (second) display
Status in linux package in Ubuntu:
Inco
e6604ecb70d4b1dbc0372c6518b51c25c4b135a1 is good.
--
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/1543683
Title:
Fails to detect (second) display
Status in linux package in Ubuntu:
Inc
118c216e16c5ccb028cd03a0dcd56d17a07ff8d7 is good.
--
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/1543683
Title:
Fails to detect (second) display
Status in linux package in Ubuntu:
Inc
I went the route of bisecting the RCs...
rc2: no kernel present in page, which makes rc6 the obvious bisect point
rc6: bad.
rc4: bad.
FIN.
--
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/1
As requested, here is the output of lspci -vvvnn on the good kernel.
** Attachment added: "lspci -vvvnn from 4.3.0-7"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+attachment/4567889/+files/lspci.good
--
You received this bug notification because you are a member of Kernel
Pa
Public bug reported:
With the upgrade to 4.4.0-2, only one of the two displays in the machine
is detected. With 4.3.0-7 (and earlier) both are detected.
In this case, both display connectors are on the MB.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-2-generic 4
the "2001::" IP would be the 2601:... IP address used throughout. Once
it is specifically routed to the fe80: IP for the host, then ipv6
connectivity works just fine to the 2601 IP (since no neighbor discovery
is involved -- it's a link address for nexthop.
I'll make some time to disable the brid
Public bug reported:
3 hosts involved here:
kailan is connected to a cisco switch, which is also connected to kurrat
(eth3), which is running a bridge with tigernut connected to eth1.
kurrat's controllers are 06:00.0 Ethernet controller: Intel Corporation
82574L Gigabit Network Connection, using
I believe that this happens because the config
(/proc/sys/net/ipv6/conf/all/accept_ra_defrtr) says to accept a default
route, and you have one specified in /etc/network/interfaces, and
therefore the advertised default route fails to get added to the routing
table.
It would be a good thing if the l
Attaching the apt history.log (files).
** Attachment added: "apt history.log (concatenated through all of time)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1260431/+attachment/3928217/+files/history.log
--
You received this bug notification because you are a member of Kernel
Packag
Public bug reported:
I have a saucy/amd64 instance that was booted using the 20130822 image
(checksum c19841cd672d6fcb3d4e78f0f918f8e1) and last updated on
2013-08-29, which I finally updated today. During the upgrade, modprobe
btrfs hung in init_module(). If I kill modprobe, the upgrade finishe
39 matches
Mail list logo
