Merged for 4.8
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1579984
Title:
Dell dock MAC Address pass through
Verified working with both -33 and -34 kernels
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1603719
mainline kernel 4.7 failed.
** Attachment added: "kern.log from 4.7 testing failure"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4708871/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Output of 4.7 mainline kernel testing failure
** Attachment added: "4.7.0-040700-generic-201607241632.log from 4.7 testing
failure"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4708872/+files/4.7.0-040700-generic-201607241632.log
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1416659
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1362180
tests ran: 23, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-34.53/kernel01__4.4.0-34.53__2016-07-28_16-36-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 1, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp3__4.4.0-30.49__2016-07-28_16-33-00/results-index.html
--
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/1606960
tests ran: 19, failed: 17;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp3__4.4.0-30.49__2016-07-28_16-27-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 1, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-31.50/s2lp6g001__4.4.0-31.50__2016-07-28_16-35-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 19, failed: 17;
http://kernel.ubuntu.com/testing/4.4.0-31.50/s2lp6g001__4.4.0-31.50__2016-07-28_16-27-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 5, failed: 4;
http://kernel.ubuntu.com/testing/4.4.0-34.53/kernel01__4.4.0-34.53__2016-07-28_16-21-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Acknowledged, we will verify and revert.
--
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/1590655
Title:
[Hyper-V] storvsc messages for CD-ROM medium not present tray closed
Status in
I just tested the suspend to ram (sorry I misunderstood this option in my own
language), it works.
The tip is that if the laptop is on the dockstation and I suspend it to ram,
after wakeup I have to unplug and replug it, to bypass the black screen.
--
You received this bug notification because
Acknowledged, we will verify and revert.
--
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/1583357
Title:
[Hyper-V] Rebase Hyper-V to 4.6 kernel
Status in linux package in Ubuntu:
Fix
** Tags added: patch
--
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/1605344
Title:
Regression caused by `fuse: Add support for pid namespaces` in
4.4.0-6.21
Status in linux package
** Tags added: patch
--
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/1607374
Title:
Cannot mount proc in unprivileged containers if /proc/xen is mounted
Status in linux package in
Debdiff for Xenial (16.04)
** Patch added: "Debdiff for Xenial (16.04)"
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1574342/+attachment/4708833/+files/lp574342_xenial.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is
tests ran: 5, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp3__4.4.0-30.49__2016-07-28_16-15-00/results-index.html
--
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/1606960
tests ran: 10, failed: 10;
http://kernel.ubuntu.com/testing/4.4.0-31.50/s2lp6g001__4.4.0-31.50__2016-07-28_16-09-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 23, failed: 23;
http://kernel.ubuntu.com/testing/4.4.0-31.50/s2lp6g001__4.4.0-31.50__2016-07-28_16-21-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 10;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp3__4.4.0-30.49__2016-07-28_16-10-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 5, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-31.50/s2lp6g001__4.4.0-31.50__2016-07-28_16-15-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 23, failed: 23;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp3__4.4.0-30.49__2016-07-28_16-21-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.4.0-34.53/kernel01__4.4.0-34.53__2016-07-28_16-10-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The netboot image is regenerated whenever debian-installer changes,
i.e., when the kernel is updated.
--
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/1572712
Title:
console hung during
Debdiff for Yakkety (16.10)
** Patch added: "Debdiff for Yakkety (16.10)"
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1574342/+attachment/4708820/+files/lp1574342_yakkety.debdiff
** Tags added: patch sts
--
You received this bug notification because you are a member of
This bug was fixed in the package dkms - 2.2.0.3-1.1ubuntu5.14.04.7
---
dkms (2.2.0.3-1.1ubuntu5.14.04.7) trusty; urgency=medium
* Build Linux modules in a specific order (LP: #1491729)
- Add POST_BUILD directive, and implement a BUILD_DEPENDS directive that
instructs
The (1) onexec test problem is tracked in bug #1528230. Please use this
bug to track the (2) exec_qual test failure or problem.
--
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/1543461
This fix was released in yakkety via 2.10.95-4ubuntu2.
** Changed in: apparmor (Ubuntu)
Status: New => Fix Released
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Medium
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
** Changed in:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Released
** Changed in:
I think this was likely a problem (race condition) in the upstream test
itself. I think I've been able to eliminate any races in the test with
upstream commits r3488 and r3489.
** Also affects: apparmor
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu)
Importance:
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Could /usr/lib/zfs-linux/scrub not just give the full path to zpool
instead? Then PATH wouldn't need modifying at all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548009
Title:
FYI, this is a requirement for snapd, but it was deprioritized in favor
of namespace stacking in support of LXD, upstreaming and other work in
support of snappy (eg, gsettings mediation). A lot of work was done to
support this, but the soonest it would be delivered given current
priorities is
Maybe this will help, Bugzilla Gnome-Shell memory leak bugs:
Bug 735705 Summary -Memory usage of gnome-shell increasing to X GiB (heap)
https://bugzilla.gnome.org/show_bug.cgi?id=735705
Bug 709451 -gnome-shell memory leaks
https://bugzilla.gnome.org/show_bug.cgi?id=709451
Bug 701230 - Summary:
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
*** This bug is a duplicate of bug 1588946 ***
https://bugs.launchpad.net/bugs/1588946
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
Hello Richard, or anyone else affected,
Accepted zfs-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.6.5.6-0ubuntu11 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
Ok, comparing this to other users of /etc/cron.d it does seem to be a
common idiom used there. To update the path to exactly the above form.
So this is not making things any worse. I am inclined to let this go on
that basis given it is already in yakkety.
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of
I get not wanting unnecessary PATHs... But is /usr/local really
considered a security issue? It's in /usr...
It's part of the standard PATH for the root user. And if an admin has
installed tools in /usr/local, wouldn't they expect them to be used?
--
You received this bug notification
Would it not make more sense to have /usr/lib/zfs-linux/scrub set the
PATH that it requires in order to find the zpool command?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548009
/usr/local/bin and /usr/local/sbin are not required for anything zfs
specific, so given that they are redundant they should not be added to
the PATH. Plus the security issue as mentioned above.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Just happened two days ago on Trusty 14.04.4 with Linux 4.4.0-31 on one
of Ceph Jewel OSD server. It ran fine for 8 days though and suddenly the
CPU load spiked to 600.
The server is from SuperMicro SuperStorage Server SSG-6048R-E1CR36L with these
following specs:
2x Intel Xeon E5-2630 v3 @
This should be rejected for Xenial and reverted for Yakkety and a more
minimal path used.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548009
Title:
ZFS pools should be
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Kamil,
For your issue, this is potentially a bug specific to the 4.5 driver. We
used to poll once a second, which would hide legacy irq issues during
initialization, but 4.5 removed it. A patch[*] to 4.6 removed all use of
legacy interrupts, and should have been applied to 4.5 stable (they were
This patch adds /usr/local/bin and /usr/local/sbin to the path. Given
the utilities in use are all official binaries this seems unexpected and
a potential security risk.
** Changed in: zfs-linux (Ubuntu Xenial)
Status: New => Incomplete
--
You received this bug notification because you
Hi Kamil,
It looks like the kernel issue is resolved. Your drive just appears to
be in a bad state and the driver reacts accordingly.
I think this launchpad's issue is resolved and should request the fix go
forward.
--
You received this bug notification because you are a member of Kernel
Public bug reported:
I've recently installed ubuntu 16.04 LTS twice -and i discovered that
the problem was from the tool katoolin so i didn't install it- after i
installed ubuntu the bluetooth didn't work for me.
P.S:the bluetooth was working when my laptop was ubuntu 15.04
when i turn
I've uploaded the patch to xenial-proposed too. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548009
Title:
ZFS pools should be automatically scrubbed
Status in
** Summary changed:
- [LTCTest][Opal][FW860] Ubuntu: lm-sensors is throwing "ERROR: Can't get value
of subfeature temp1_input: I/O error" for be2net driver
+ lm-sensors is throwing "ERROR: Can't get value of subfeature temp1_input: I/O
error" for be2net driver
--
You received this bug
Original report of the exact same issue:
https://lkml.org/lkml/2016/5/13/327
--
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/1605843
Title:
Kernel crashes from time to time when using
** Patch added:
"0001-UBUNTU-SAUCE-xenbus-Use-proc_create_mount_point-to-c.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607374/+attachment/4708767/+files/0001-UBUNTU-SAUCE-xenbus-Use-proc_create_mount_point-to-c.patch
** Changed in: linux (Ubuntu Xenial)
Importance:
Public bug reported:
== Comment: #17 - Guilherme Guaglianoni Piccoli - 2016-07-27 18:49:08 ==
Temperature and fan information from hardware are normally available to
userspace through hwmon sysfs abstraction. In case of be2net driver, all PCI
devices "managed" by this driver have hwmon entries,
You have been subscribed to a public bug:
== Comment: #17 - Guilherme Guaglianoni Piccoli - 2016-07-27 18:49:08 ==
Temperature and fan information from hardware are normally available to
userspace through hwmon sysfs abstraction. In case of be2net driver, all PCI
devices "managed" by this
** Description changed:
+ SRU Justification
+
+ Impact: The pid namespace support in fuse refuses requests from any
+ process whose pid does not map into the pid namespace of the fuse
+ userspace process. This has caused a regression for at least one user.
+
+ Fix: Permit requests from
** Patch added:
"0001-UBUNTU-SAUCE-namespace-fuse-Permit-requests-from-oth.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605344/+attachment/4708792/+files/0001-UBUNTU-SAUCE-namespace-fuse-Permit-requests-from-oth.patch
--
You received this bug notification because you are a
Hi,
I have the Lenovo T440p with integrated intel and nvidia, and I encounter the
same symptoms than deb2014.
The log is also with symbols.
It's ramdomly crashed with a black screen or works after hibernating no more
than 2-3 times.
Moreover, it crashs every time I plug in to the
Public bug reported:
SRU Justification
Impact: The xenfs filesystem is traditionally mounted at /proc/xen in
xen guests. This directory doesn't use the special "create proc
mountpoint" interface and thus fails the permanently empty test in
fs_fully_visible(). This causes mounting of proc to fail
I think the fix for this crash is this upstream commit:
8329e818f14926a6040df86b2668568bde342ebf
--
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/1605843
Title:
Kernel crashes from time
Thanks for the help. After a while modprobe btrfs hangs again,
specifically on "insmod
/lib/modules/3.13.0-88-generic/kernel/lib/raid6/raid6_pq.ko" and "insmod
/lib/modules/3.13.0-88-generic/kernel/fs/btrfs/btrfs.ko". Even after
installing btrfs-tools.
--
You received this bug notification
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1607355
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1607356
Title:
package linux-image-3.5.0-54-generic 3.5.0-54.81~precise1 failed to
install/upgrade:
Using my simpler testing I found that the problem first started
occurring in 15.10
I also noticed this is also when the "Disable while typing" option was
removed.
I hope this helps, I will be able to test any new upstream releases pretty
quickly
(Now that I have done it once :) )
** Tags
101 - 200 of 228 matches
Mail list logo
