[Kernel-packages] [Bug 1839216] [NEW] xenial VM hangs copying block device
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.bin IN=$(losetup --show -f in.bin) OUT=$(losetup --show -f out.bin) typeset -i i=1 while true; do echo $i $(date) dd if=$IN of=$OUT bs=128k i=i+1 done == The trace (sorry, I don't have the exact kernel version... I found this mid-June 2019) looks like: # cat /proc/5230/stack [<0>] io_schedule+0x16/0x40 [<0>] wbt_wait+0x234/0x390 [<0>] blk_mq_make_request+0x103/0x590 [<0>] generic_make_request+0x122/0x2f0 [<0>] submit_bio+0x73/0x150 [<0>] submit_bh_wbc+0x17a/0x1b0 [<0>] __block_write_full_page+0x15b/0x400 [<0>] block_write_full_page+0x10c/0x130 [<0>] blkdev_writepage+0x18/0x20 [<0>] __writepage+0x1d/0x50 [<0>] write_cache_pages+0x228/0x4b0 [<0>] generic_writepages+0x5c/0x90 [<0>] blkdev_writepages+0x2f/0x40 [<0>] do_writepages+0x1f/0x70 [<0>] __filemap_fdatawrite_range+0xc6/0x100 [<0>] filemap_write_and_wait+0x31/0x90 [<0>] __blkdev_put+0x7a/0x210 [<0>] blkdev_put+0x4c/0xd0 [<0>] blkdev_close+0x34/0x70 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9a/0xc0 [<0>] exit_to_usermode_loop+0xce/0xd0 [<0>] do_syscall_64+0x116/0x150 [<0>] entry_SYSCALL_64_after_hwframe+0x42/0xb7 [<0>] 0x If we have used strace on the process, we find that dd is inside "close(1)" as it closes the output file. I don't know if this would reproduce on actual hardware, as I don't have a machine that large to play with. ** Affects: linux (Ubuntu) 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/1839216 Title: xenial VM hangs copying block device Status in linux package in Ubuntu: New Bug description: 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.bin IN=$(losetup --show -f in.bin) OUT=$(losetup --show -f out.bin) typeset -i i=1 while true; do echo $i $(date) dd if=$IN of=$OUT bs=128k i=i+1 done == The trace (sorry, I don't have the exact kernel version... I found this mid-June 2019) looks like: # cat /proc/5230/stack [<0>] io_schedule+0x16/0x40 [<0>] wbt_wait+0x234/0x390 [<0>] blk_mq_make_request+0x103/0x590 [<0>] generic_make_request+0x122/0x2f0 [<0>] submit_bio+0x73/0x150 [<0>] submit_bh_wbc+0x17a/0x1b0 [<0>] __block_write_full_page+0x15b/0x400 [<0>] block_write_full_page+0x10c/0x130 [<0>] blkdev_writepage+0x18/0x20 [<0>] __writepage+0x1d/0x50 [<0>] write_cache_pages+0x228/0x4b0 [<0>] generic_writepages+0x5c/0x90 [<0>] blkdev_writepages+0x2f/0x40 [<0>] do_writepages+0x1f/0x70 [<0>] __filemap_fdatawrite_range+0xc6/0x100 [<0>] filemap_write_and_wait+0x31/0x90 [<0>] __blkdev_put+0x7a/0x210 [<0>] blkdev_put+0x4c/0xd0 [<0>] blkdev_close+0x34/0x70 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9a/0xc0 [<0>] exit_to_usermode_loop+0xce/0xd0 [<0>] do_syscall_64+0x116/0x150 [<0>] entry_SYSCALL_64_after_hwframe+0x42/0xb7 [<0>] 0x If we have used strace on the process, we find that dd is inside "close(1)" as it closes the output file. I don't know if this would reproduce on actual hardware, as I don't have a machine that large to play with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs
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
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1408106
Title:
attach_disconnected not sufficient for overlayfs
Status in AppArmor:
In Progress
Status in MAAS:
New
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Triaged
Bug description:
With the following use of overlayfs, we get a disconnected path:
$ cat ./profile
#include
profile foo {
#include
capability sys_admin,
capability sys_chroot,
mount,
pivot_root,
}
$ cat ./overlay.c
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char* argv[]) {
int i = 0;
int len = 0;
int ret = 0;
char* options;
if (geteuid())
unshare(CLONE_NEWUSER);
unshare(CLONE_NEWNS);
for (i = 1; i < argc; i++) {
if (i == 1) {
len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
options = alloca(len);
ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
}
else {
len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
options = alloca(len);
ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt",
argv[i]);
}
mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
}
chdir("/mnt");
pivot_root(".", ".");
chroot(".");
chdir("/");
execl("/bin/bash", "/bin/bash", NULL);
}
$ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
[255]
...
Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
With the above, the expectation was for the denial to be /mnt/bin/bash. There
are three ways forward:
1. the correct solution is to patch overlayfs to properly track the loopback,
but this will take a while, may ultimately be unachievable. UPDATE: upstream is
currently working on this and Ubuntu will engage with them
2. we could rely on the fact that overlayfs creates a private unshared
submount, and provide a way to not mediate the path when that is present, and
tagged. This would take a bit of time, and might be the preferred method over 1
longer term
3. we could extend attach_disconnected so that we can define the attach root.
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash'
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs
** 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 in AppArmor:
In Progress
Status in MAAS:
New
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Triaged
Bug description:
With the following use of overlayfs, we get a disconnected path:
$ cat ./profile
#include
profile foo {
#include
capability sys_admin,
capability sys_chroot,
mount,
pivot_root,
}
$ cat ./overlay.c
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char* argv[]) {
int i = 0;
int len = 0;
int ret = 0;
char* options;
if (geteuid())
unshare(CLONE_NEWUSER);
unshare(CLONE_NEWNS);
for (i = 1; i < argc; i++) {
if (i == 1) {
len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
options = alloca(len);
ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
}
else {
len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
options = alloca(len);
ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt",
argv[i]);
}
mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
}
chdir("/mnt");
pivot_root(".", ".");
chroot(".");
chdir("/");
execl("/bin/bash", "/bin/bash", NULL);
}
$ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
[255]
...
Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
With the above, the expectation was for the denial to be /mnt/bin/bash. There
are three ways forward:
1. the correct solution is to patch overlayfs to properly track the loopback,
but this will take a while, may ultimately be unachievable. UPDATE: upstream is
currently working on this and Ubuntu will engage with them
2. we could rely on the fact that overlayfs creates a private unshared
submount, and provide a way to not mediate the path when that is present, and
tagged. This would take a bit of time, and might be the preferred method over 1
longer term
3. we could extend attach_disconnected so that we can define the attach root.
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash'
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597806] Re: ipv6 neighbor discovery broken (on a bridge)
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 notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1597806 Title: ipv6 neighbor discovery broken (on a bridge) Status in linux package in Ubuntu: Confirmed Bug description: 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:8100:3500:24c:40ff:fe1a:c570/64 scope global mngtmpaddr dynamic valid_lft 300sec preferred_lft 120sec The tcpdump trace on against eth0.2 of the broken machine: http://paste.ubuntu.com/18170606/ (fe80::1 is the gateway) http://paste.ubuntu.com/18173670/ is the output of lspci -vvn on one of the (quad) interfaces on the machine. Setting the bridge to promisc and turning it back off works around the issue. Tcpdump on the underlying eth0.2 does not. On another (yakkety) box, running 4-4-0.14-generic, I also see the problem: that interface is also br0, with eth0 (untagged) as its only member. All of the above leads me to believe that the kernel is not managing to correctly set up (at least some?) of the multicast addresses it needs to listen to on the bridge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597806] Re: ipv6 neighbor discovery broken (on a bridge)
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 (Ethernet), capture size 262144 bytes [ fire up ping6 2601:282:8100:3500:641d:9dd0:5b50:46e6 on the gateway.] [ no traffic shows up on the bridge ] [ echo 0 > /sys/devices/virtual/net/br0/bridge/multicast_snooping ] 09:40:49.260756 IP6 fe80::1 > ff02::1:ff50:46e6: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:641d:9dd0:5b50:46e6, length 32 09:40:49.260813 IP6 2601:282:8100:3500:641d:9dd0:5b50:46e6 > fe80::1: ICMP6, neighbor advertisement, tgt is 2601:282:8100:3500:641d:9dd0:5b50:46e6, length 32 Looks like bridge multicast_snooping causes ipv6 neighbor discovery to break. -- 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/1597806 Title: ipv6 neighbor discovery broken (on a bridge) Status in linux package in Ubuntu: Confirmed Bug description: 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:8100:3500:24c:40ff:fe1a:c570/64 scope global mngtmpaddr dynamic valid_lft 300sec preferred_lft 120sec The tcpdump trace on against eth0.2 of the broken machine: http://paste.ubuntu.com/18170606/ (fe80::1 is the gateway) http://paste.ubuntu.com/18173670/ is the output of lspci -vvn on one of the (quad) interfaces on the machine. Setting the bridge to promisc and turning it back off works around the issue. Tcpdump on the underlying eth0.2 does not. On another (yakkety) box, running 4-4-0.14-generic, I also see the problem: that interface is also br0, with eth0 (untagged) as its only member. All of the above leads me to believe that the kernel is not managing to correctly set up (at least some?) of the multicast addresses it needs to listen to on the bridge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597806] [NEW] ipv6 neighbor discovery broken (on a bridge)
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:8100:3500:24c:40ff:fe1a:c570/64 scope global mngtmpaddr dynamic valid_lft 300sec preferred_lft 120sec The tcpdump trace on against eth0.2 of the broken machine: http://paste.ubuntu.com/18170606/ (fe80::1 is the gateway) http://paste.ubuntu.com/18173670/ is the output of lspci -vvn on one of the (quad) interfaces on the machine. Setting the bridge to promisc and turning it back off works around the issue. Tcpdump on the underlying eth0.2 does not. On another (yakkety) box, running 4-4-0.14-generic, I also see the problem: that interface is also br0, with eth0 (untagged) as its only member. All of the above leads me to believe that the kernel is not managing to correctly set up (at least some?) of the multicast addresses it needs to listen to on the bridge. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1597806 Title: ipv6 neighbor discovery broken (on a bridge) Status in linux package in Ubuntu: Incomplete Bug description: 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:8100:3500:24c:40ff:fe1a:c570/64 scope global mngtmpaddr dynamic valid_lft 300sec preferred_lft 120sec The tcpdump trace on against eth0.2 of the broken machine: http://paste.ubuntu.com/18170606/ (fe80::1 is the gateway) http://paste.ubuntu.com/18173670/ is the output of lspci -vvn on one of the (quad) interfaces on the machine. Setting the bridge to promisc and turning it back off works around the issue. Tcpdump on the underlying eth0.2 does not. On another (yakkety) box, running 4-4-0.14-generic, I also see the problem: that interface is also br0, with eth0 (untagged) as its only member. All of the above leads me to believe that the kernel is not managing to correctly set up (at least some?) of the multicast addresses it needs to listen to on the bridge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597806] Re: ipv6 neighbor discovery broken (on a bridge)
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 schedules and the location of the machines. -- 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/1597806 Title: ipv6 neighbor discovery broken (on a bridge) Status in linux package in Ubuntu: Incomplete Bug description: 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:8100:3500:24c:40ff:fe1a:c570/64 scope global mngtmpaddr dynamic valid_lft 300sec preferred_lft 120sec The tcpdump trace on against eth0.2 of the broken machine: http://paste.ubuntu.com/18170606/ (fe80::1 is the gateway) http://paste.ubuntu.com/18173670/ is the output of lspci -vvn on one of the (quad) interfaces on the machine. Setting the bridge to promisc and turning it back off works around the issue. Tcpdump on the underlying eth0.2 does not. On another (yakkety) box, running 4-4-0.14-generic, I also see the problem: that interface is also br0, with eth0 (untagged) as its only member. All of the above leads me to believe that the kernel is not managing to correctly set up (at least some?) of the multicast addresses it needs to listen to on the bridge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1597806] Re: ipv6 neighbor discovery broken (on a bridge)
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/bugs/1597806 Title: ipv6 neighbor discovery broken (on a bridge) Status in linux package in Ubuntu: Incomplete Bug description: 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:8100:3500:24c:40ff:fe1a:c570/64 scope global mngtmpaddr dynamic valid_lft 300sec preferred_lft 120sec The tcpdump trace on against eth0.2 of the broken machine: http://paste.ubuntu.com/18170606/ (fe80::1 is the gateway) http://paste.ubuntu.com/18173670/ is the output of lspci -vvn on one of the (quad) interfaces on the machine. Setting the bridge to promisc and turning it back off works around the issue. Tcpdump on the underlying eth0.2 does not. On another (yakkety) box, running 4-4-0.14-generic, I also see the problem: that interface is also br0, with eth0 (untagged) as its only member. All of the above leads me to believe that the kernel is not managing to correctly set up (at least some?) of the multicast addresses it needs to listen to on the bridge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 detect (second) display Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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: Fails to detect (second) display Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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, 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 (second) display Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 instrument things to produce an audit trail of what queries are hitting the driver about the display, and what it's saying... It's behaving like it only sees 1 display part of the time, while both are actually present. -- 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: Fix Released Status in linux source package in Xenial: Fix Released Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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's likely an interaction between 237ed86c and the fix. If not, that will give us 4.4.0-9+fix as a base good, way ahead of where we would be if we went back to 237ed86c~1. -- 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: Fix Released Status in linux source package in Xenial: Fix Released Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 -14), but not with the trunk prior to 237ed86c, when the OS stops sending video to the displays (in my case after screen locks and there is still no keyboard/mouse activity), then the windows get jumbled around in a manner that is consistent with X deciding that it's single-headed again, and then back to double headed. The kernel in #40 does not exhibit this behavior. It would be interesting to see if 237ed86c with the xenial fix does or does not. If it does, then this remains an open bug. If it does not, then we have a new bug, and a need to bisect again, with 4.4.0-13 (from the archive) being the initial bad, and 237ed86c+fix as the first good. Sadly, every single kernel in that bisect will need to have the fix applied post- bisect, so lets hope it's still this bug. As of right now, initial good is 237ed86c~1(with current fix -- I don't think I tested for this when we were doing the initial bisect.) Thanks -- 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: Fix Released Status in linux source package in Xenial: Fix Released Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 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: Fix Released Status in linux source package in Xenial: Fix Released Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 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: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 (second) display Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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/linux/+bug/1543683/+attachment/4580514/+files/zz -- 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: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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, which shows some screaming from the i915 driver (and some network packet screaming, which I believe is unrelated, though curious.) lamont ** Attachment added: "kern.log from the boot of the 4.4.0-6 (minus the buggy commit)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+attachment/4580286/+files/zz -- 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: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 detect (second) display Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 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: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 belief that the next kernel for me to try is d2e08c0f34438af791482de8abf2c8e4e573b1d3 -- 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: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 detect (second) display Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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: Incomplete Status in linux source package in Xenial: Incomplete Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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: Incomplete Status in linux source package in Xenial: Incomplete Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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: Incomplete Status in linux source package in Xenial: Incomplete Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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/1543683 Title: Fails to detect (second) display Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] [NEW] Fails to detect (second) display
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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: amd64 apport-bug kernel-da-key xenial ** Attachment added: "kernel.log from booting the working (4.3.0-7) kernel." https://bugs.launchpad.net/bugs/1543683/+attachment/4567870/+files/kernel.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: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display
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 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: Confirmed Status in linux source package in Xenial: Confirmed Bug description: 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.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lamont 3923 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 9 10:22:38 2016 HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3 InstallationDate: Installed on 2014-09-22 (505 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc SG41 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FG41 dmi.board.vendor: Shuttle Inc dmi.board.version: V20 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SG41 dmi.product.version: V20 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1502238] Re: bridge does not forward neighbor solicitation packets
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 bridge callouts this week. as for ebtables, I'm going to say there aren't any: sudo: ebtables: command not found -- 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/1502238 Title: bridge does not forward neighbor solicitation packets Status in linux package in Ubuntu: Incomplete Bug description: 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 the e1000e driver (3.13.0-65-generic kernel) (while kailan is doing a ping6 2601:282:8100:3500:82ee:73ff:fe99:368d): +kurrat 324 : sudo tcpdump -eni eth3 ip6 and not tcp and not udp tcpdump: WARNING: eth3: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth3, link-type EN10MB (Ethernet), capture size 65535 bytes 10:39:16.080888 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:16.431484 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:17.077446 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:18.077457 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:19.095034 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:20.093436 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:21.093425 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:21.43 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:22.111042 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 ^C 10 packets captured 11 packets received by filter 0 packets dropped by kernel +kurrat 325 : sudo tcpdump -eni eth1 ip6 and not tcp and not udp tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 10:39:28.201110 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:31.552677 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:38.103919 08:10:78:fc:b3:d2 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 90: fe80::a10:78ff:fefc:b3d2 > ff02::1: HBH ICMP6, multicast listener query v2 [gaddr ::], length 28 10:39:39.663357 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 ^C 4 packets captured 4 packets received by filter 0 packets dropped by kernel 1 packet dropped by interface +kurrat 326 : uname -a Linux kurrat 3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Adding a host route for the 2001:: IP via the link IP on kailan works as a workaround, but the neighbor solicitiation packets are clearly not getting through the bridge. No firewall is configured on kurrat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502238/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1502238] [NEW] bridge does not forward neighbor solicitation packets
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 the e1000e driver (3.13.0-65-generic kernel) (while kailan is doing a ping6 2601:282:8100:3500:82ee:73ff:fe99:368d): +kurrat 324 : sudo tcpdump -eni eth3 ip6 and not tcp and not udp tcpdump: WARNING: eth3: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth3, link-type EN10MB (Ethernet), capture size 65535 bytes 10:39:16.080888 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:16.431484 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:17.077446 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:18.077457 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:19.095034 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:20.093436 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:21.093425 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 10:39:21.43 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:22.111042 00:1c:c0:83:32:40 > 33:33:ff:99:36:8d, ethertype IPv6 (0x86dd), length 86: 2601:282:8100:3500::1 > ff02::1:ff99:368d: ICMP6, neighbor solicitation, who has 2601:282:8100:3500:82ee:73ff:fe99:368d, length 32 ^C 10 packets captured 11 packets received by filter 0 packets dropped by kernel +kurrat 325 : sudo tcpdump -eni eth1 ip6 and not tcp and not udp tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 10:39:28.201110 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:31.552677 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 10:39:38.103919 08:10:78:fc:b3:d2 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 90: fe80::a10:78ff:fefc:b3d2 > ff02::1: HBH ICMP6, multicast listener query v2 [gaddr ::], length 28 10:39:39.663357 00:1c:c0:83:32:40 > 33:33:00:00:00:01, ethertype IPv6 (0x86dd), length 110: fe80::21c:c0ff:fe83:3240 > ff02::1: ICMP6, router advertisement, length 56 ^C 4 packets captured 4 packets received by filter 0 packets dropped by kernel 1 packet dropped by interface +kurrat 326 : uname -a Linux kurrat 3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Adding a host route for the 2001:: IP via the link IP on kailan works as a workaround, but the neighbor solicitiation packets are clearly not getting through the bridge. No firewall is configured on kurrat. ** Affects: linux (Ubuntu) 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/1502238 Title: bridge does not forward neighbor solicitation packets Status in linux package in Ubuntu: New Bug description: 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 the e1000e driver (3.13.0-65-generic kernel) (while kailan is doing a ping6 2601:282:8100:3500:82ee:73ff:fe99:368d): +kurrat 324 : sudo tcpdump -eni eth3 ip6 and not tcp and not udp tcpdump: WARNING: eth3: no IPv4 address assigned tcpdump: verbose output
[Kernel-packages] [Bug 1065974] Re: dmesg full of ICMPv6 RA: ndisc_router_discovery() failed to add default route
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 logged error (1) said what it was trying to add as the default route, and (2) was rate limited, and (3) pointed at accept_ra_defrtr Having ifup turn off accept_ra_defrtr when it adds a default route might be a good thing, too. Just my thoughts. -- 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/1065974 Title: dmesg full of ICMPv6 RA: ndisc_router_discovery() failed to add default route Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu Server 12.04.1 LTS and since IPv6 RAs are enabled on wired connection, the message ICMPv6 RA: ndisc_router_discovery() failed to add default route fills dmesg. The default route is being set nontheless: 2001:638:a000:4104::/64 dev eth0 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 default via fe80::1 dev eth0 metric 1024 /etc/network/interfaces looks like this: # The primary network interface auto eth0 iface eth0 inet static address 131.188.31.189 netmask 255.255.255.0 gateway 131.188.31.1 dns-nameservers 131.188.0.11 131.188.0.10 dns-domain informatik.uni-erlangen.de dns-search informatik.uni-erlangen.de iface eth0 inet6 static address 2001:638:a000:4104::189 netmask 64 gateway fe80::1 dns-nameservers 2001:638:a000:1053:53::1 2001:638:a000:1053:53::2 NetworkManager is not installed, so I don't think its a dublicate of #988183 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-31-virtual 3.2.0-31.50 ProcVersionSignature: Ubuntu 3.2.0-31.50-virtual 3.2.28 Uname: Linux 3.2.0-31-virtual x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Okt 4 23:10 seq crw-rw---T 1 root audio 116, 33 Okt 4 23:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Date: Fri Oct 12 15:12:44 2012 HibernationDevice: RESUME=UUID=f3f34eb5-dc4d-47b9-b67e-6938afa8a07a InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd MachineType: Bochs Bochs PciMultimedia: ProcEnviron: TERM=xterm-256color LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-virtual root=UUID=07c76f05-3330-4c30-b1f5-488a08024a0d ro ProcModules: floppy 70365 0 - Live 0x lp 17799 0 - Live 0x parport 46562 1 lp, Live 0x psmouse 97362 0 - Live 0x serio_raw 13211 0 - Live 0x RelatedPackageVersions: linux-restricted-modules-3.2.0-31-virtual N/A linux-backports-modules-3.2.0-31-virtual N/A linux-firmware1.79.1 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1260431] [NEW] update-grub hangs under 3.11.0-3-generic
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 finishes. The apport gathering is on the new kernel, since apport declined to file a bug with the 3.11.0-3-generic kernel running. filing here for historical purposes, I expect. The problem does not reproduce on a current machine running 3.11.0-14-generic. lamont ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 12 17:45 seq crw-rw 1 root audio 116, 33 Dec 12 17:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 10.105412] init: plymouth-stop pre-start process (1008) terminated with status 1 Date: Thu Dec 12 17:45:40 2013 Ec2AMI: ami-0005 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova MarkForUpload: True PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=25707b7a-3d31-4823-831f-ed5306116706 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.4 dmi.sys.vendor: OpenStack Foundation ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug ec2-images saucy ** Attachment added: ps and strace output at the time of the hang. https://bugs.launchpad.net/bugs/1260431/+attachment/3928207/+files/3.11.0-3 -- 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/1260431 Title: update-grub hangs under 3.11.0-3-generic Status in “linux” package in Ubuntu: Confirmed Bug description: 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 finishes. The apport gathering is on the new kernel, since apport declined to file a bug with the 3.11.0-3-generic kernel running. filing here for historical purposes, I expect. The problem does not reproduce on a current machine running 3.11.0-14-generic. lamont ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 12 17:45 seq crw-rw 1 root audio 116, 33 Dec 12 17:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 10.105412] init: plymouth-stop pre-start process (1008) terminated with status 1 Date: Thu Dec 12 17:45:40 2013 Ec2AMI: ami-0005 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001
