tests ran: 16, failed: 4;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/kernel01__4.4.0-57.78__2016-12-15_13-08-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: 36, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/dwalin__4.4.0-57.78__2016-12-15_08-56-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: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/kernel01__4.4.0-57.78__2016-12-15_13-32-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: 35, failed: 6;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-15_08-56-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: 141, failed: 140;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/kernel01__4.4.0-57.78__2016-12-15_13-20-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 d_automount is the callback into the filesystem to mount a sub-
filesystem upon access to a directory. autofs does use it, but nfs uses
it too for subshares even without autofs.
So far I'm not seeing any connection between my patch and the crash, I'm
wondering if you've encountered another
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/kernel01__4.4.0-57.78__2016-12-15_13-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: 33, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/kernel01__4.4.0-57.78__2016-12-15_09-11-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: 1;
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/modoc__3.19.0-78.86__2016-12-15_13-06-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: 33, failed: 5;
http://kernel.ubuntu.com/testing/3.19.0-78.86~14.04.1-generic/dwalin__3.19.0-78.86~14.04.1__2016-12-15_15-09-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
Public bug reported:
On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
crash on boot when in /etc/fstab a nfsv4 entry is active
When comment the line or set to noauto the kernel boot with no error and
mounting the nfs shares (after uncomment ) is also possible without
error
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1650336
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
This does not sound like a QEMU bug, so let's remove it from the QEMU
bug tracker
** No longer affects: qemu
--
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/712416
Title:
kvm_intel
I see this has been changed to expired because of lacking activity, so I
just wanted to say hi and that it affects me, too. And I got pretty
annoyed by it by now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ok,
your kernel 4.4.0.54.75... boots and works with no permission error :)
For the kernel crash i will create a new bug report.
--
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/1649292
** Changed in: linux (Ubuntu)
Status: Expired => 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/1082418
Title:
[Fujitsu Lifebook AH532] UEFI firmware locks itself after
Thanks. Here's the new test build.
http://people.canonical.com/~sforshee/lp1649292/linux-4.4.0-54.75+lp1649292v201612150908/
--
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/1649292
Title:
No changing since 4.9-RC8 ... the kernel boots ... mounting shares from
fstab ... but i got permission denied at the second subshare
--
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/1649292
tests ran: 7, failed: 4;
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/modoc__3.19.0-78.86__2016-12-15_14-49-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: 4;
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/modoc__3.19.0-78.86__2016-12-15_16-01-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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: Fix Committed => Fix Released
** Changed in:
tests ran: 16, failed: 3;
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/modoc__3.19.0-78.86__2016-12-15_17-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.
This ticket is a replacement to LP 1578232 which was a bit screwed up
...
** Package changed: linux (Ubuntu) => parted (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in:
It appears this bug has stalled until someone can pinpoint the commit
that broke this? I would love to do this, but lack resources. Is there
anyone that can do this bisect between 15.10 and 16.04?
This was originally requested in #40.
https://wiki.ubuntu.com/Kernel/KernelBisection
--
You
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/3.13.0-106.153-generic/ms10-34-mcdivittB0-kernel__3.13.0-106.153__2016-12-15_18-23-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: 36, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-15_18-29-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: 35, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onibi__4.4.0-57.78__2016-12-15_13-37-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: 141, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-78.86~14.04.1-generic/modoc__3.19.0-78.86~14.04.1__2016-12-15_17-57-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
Do you have time to install a test kernel before the system hangs up?
If so, it might be good to test the latest mainline kernel to see if
this bug is already fixed:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/
** Tags added: kernel-da-key xenial
** Also affects: linux (Ubuntu)
Are there any call traces or errors in the logs after the installation?
Once on the the other vt, does the system appear to function properly?
If so, it might be good to test some other kernels to see if this is a
regression, and test the latest mainline kernel to see if this is
already fixed:
tests ran: 33, failed: 5;
http://kernel.ubuntu.com/testing/3.19.0-78.86-generic/dwalin__3.19.0-78.86__2016-12-15_17-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: 1;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-15_14-02-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I built the next test kernel, up to the following commit:
866ae696e26ee2b1fa0d04e67d6dafc477543fd6
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1642739
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/modoc__4.4.0-57.78__2016-12-16_00-03-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi
After update mainline kernel ,has fixed this problem
linux-headers-4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb
linux-image-4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is
So..this issue, kernel team will release next Ubuntu 16.04.2 version
with fix?
--
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/1646277
Title:
Xenial desktop 16.04.x will have a black
After update the latest v4.9 kernel ,the issue still exist.
Below as error messages
===
INFO: task systemd-shutdow:1 blocked for more than 120 seconds.
Not tainted 4.9.0-040900rc8-generic #201612051443
"echo 0 >
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: crda (Ubuntu)
Status: New => 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/1280636
This kernel did not have 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/1642739
Title:
Kernel panic on shutdown
Status in linux package in Ubuntu:
Confirmed
Status in linux
tests ran: 18, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/modoc__4.4.0-57.78__2016-12-16_01-32-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: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-15_22-28-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: 1;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onibi__4.4.0-57.78__2016-12-15_18-38-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: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-15_23-44-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: 33, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onibi__4.4.0-57.78__2016-12-15_23-20-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/modoc__4.4.0-57.78__2016-12-15_23-31-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
I had the issue since the first installation of ubuntu 16.04 lts, same after
upgrade to non lts.
Just tested with mainstream kernel and the issue is still there.
thanks
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You
** Also affects: apmd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to apmd in Ubuntu.
https://bugs.launchpad.net/bugs/1650074
Title:
Default on battery APM level causes SSD runing
tests ran: 23, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-15_20-34-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/3.19.0-78.86~14.04.1-generic/ms10-34-mcdivittB0-kernel__3.19.0-78.86~14.04.1__2016-12-15_19-50-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** 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/1650058
Title:
[Hyper-V/Azure] Please include Mellanox OFED drivers
** 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/1650059
Title:
[Hyper-V] Rebase Hyper-V in 16.04 and 16.10 to the the
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I haven't been able to reproduce the problem after running fsck on
/dev/sda5.
I'm attaching an excerpt from my syslog which includes the errors I was
getting (I guess they didn't show up in the logs sent by apport).
I still intend to test newer kernels and run other checks to see if it's
a
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onibi__4.4.0-57.78__2016-12-16_04-50-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Changed in: hwe-next
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
tests ran: 33, failed: 5;
http://kernel.ubuntu.com/testing/3.19.0-78.86~14.04.1-generic/onibi__3.19.0-78.86~14.04.1__2016-12-16_06-09-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 9, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/modoc__4.4.0-57.78__2016-12-16_03-44-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Yes,
in fact it is not possible to execute the apoort-collect command when the
kernel crashed.
If someone need information about the hardware, i can boot the computer
without the nfs stab entry and execute then the command.
But i can also report the same problem from other computers ( for
OTA14 does not changed anything here.
I can also upload videos to show the different behaviors on MX4 and Pro5.
If you need any help i can do, let me know.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: hwe-next
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or
UEFI mode.
System hangs while rebooting
Not found the issue in RAID0
No issue on Ubuntu14.04
Driver-OS inbox support
tests ran: 3, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-78.86~14.04.1-generic/modoc__3.19.0-78.86~14.04.1__2016-12-16_02-32-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onibi__4.4.0-57.78__2016-12-16_03-18-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Summary changed:
- Fix channel data parsing in ST Mirco sensor IIO drivers
+ Fix channel data parsing in ST Micro sensor IIO drivers
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I create a new bug report Bug #1650336 for the crash with the nfs
/etc/fstab entry
--
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/1649292
Title:
NFS client : permission denied when
> 4.4.0-38 contains a patch (backported from 4.8)
Hmm, when i remember correctly, after the first time the permission
problem occurs a lot of kernel updates comes in quick succession ... and
when i test this updates i had similar crashes on boot time and booting
without fstab entries works and
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Committed
--
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/1634964
Title:
Allow fuse user namespace mounts by default
You have been subscribed to a public bug:
I installed Ubuntu 16.04.1 on an FBA device. When the partman menu appeared, I
created a new partition table on DASD 0.0.ede0 (FBA), and then I created two
partitions: 0.7G ext4 for /boot and 10G ext4 for /.
Installation proceeded ok, and the system
I'll have another kernel for you to test soon with a very simple fix. In
the mean time could you test the 4.9 mainline build from the link below
just to confirm that the problem hasn't been fixed upstream?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/
--
You received this bug notification
Default Comment by Bridge
** Attachment added: "/var/log/syslog"
https://bugs.launchpad.net/bugs/1650300/+attachment/4791999/+files/syslog
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You
Strange about the crash, there are no changes between 4.4.0-54 and
4.4.0-57 that look to be related at all. I suggest you open another bug
for that issue (let me know the bug number).
I'll make the new test build based on 4.4.0-54.
--
You received this bug notification because you are a member
tests ran: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/s2lp3__4.4.0-57.78__2016-12-15_09-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.
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/trusty/3.19.0-78.86~14.04.1/trusty-3.19-proposed-frozen.html
** Tags added: certification-testing-passed
** Changed in:
tests ran: 20, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/onibi__4.4.0-57.78__2016-12-15_08-28-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ok,
after further googling it turned out these up-right and bottom-right top
shortcuts for middle and right button are default in Ubuntu (and not specific
of our trackpad).
So the new driver is working as expected.
For those finding very annoying the accidental middle button click when
tapping
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/s2lp3__4.4.0-57.78__2016-12-15_09-39-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: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/s2lp3__4.4.0-57.78__2016-12-15_09-41-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1649821
Title:
Boot crash in xen_send_IPI_one
Status in
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1633321 ***
https://bugs.launchpad.net/bugs/1633321
Verified with 201611-25212 on Yakkety, this issue will gone with proposed
Yakkety kernel 4.8.0-32
Thanks
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-15_08-31-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: 16, failed: 4;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/s2lp3__4.4.0-57.78__2016-12-15_09-02-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
looks good :)
In this kernel the problem is fixed.
Thank you very much !!!
But for my personal interest, could you explain me in a few words in
which part of the kernel this fix works ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
tests ran: 33, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/onibi__4.4.0-57.78__2016-12-15_03-48-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: 0;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/onza__4.4.0-57.78__2016-12-15_08-06-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ok, i can boot without the /etc/fstab entries and mount then the NFS
shares without errors ...
I added the logs as an attachment ...
** Attachment added: "kernel_crash.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649292/+attachment/4791915/+files/kernel_crash.txt
--
You
Public bug reported:
Use correct read length when reading from ST Micro sensors on i2c/spi
bus.
This bug is used for tracking purposes, please do not triage.
** Affects: hwe-next
Importance: Critical
Assignee: Shrirang Bagul (shrirang-bagul)
Status: Confirmed
** Affects:
tests ran: 5, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/kernel01__4.4.0-57.78__2016-12-15_05-40-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ah ... to early :(
In the patch i saw "automount" and in fact i configured autofs to mount
the nfs shares.
Now i disabled autofs and uncomment the appropriate entries in
/etc/fstab and the kernel crash on boot time.
--
You received this bug notification because you are a member of Kernel
tests ran: 35, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-57.78-lowlatency/dwalin__4.4.0-57.78__2016-12-15_03-17-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: 3;
http://kernel.ubuntu.com/testing/4.4.0-57.78-generic/s2lp3__4.4.0-57.78__2016-12-15_05-12-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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/1632786
Title:
[Hyper-V] do not lose pending heartbeat
Public bug reported:
As I visited to many website seeking for solution , I get the message to
upgrade your kernel to start using multi-touch, but is there any hack so
I can use multi touch in e450.
* 2 fingers scrolling not working.
* Double click not so much efficient, even I have to make
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1650257
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
You have been subscribed to a public bug:
This is a Ubuntu 16.04.2 feature to track the inclusions of POWER9
patches on top of kernel 4.8.
Ubuntu 16.04.2 is based on kernel 4.8[1], and we want to add support for
POWER9 on this kernel. In order to do so, we will need to cherry-pick
important
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1650257/+attachment/4791960/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected trusty
** Description changed:
As I visited to many website seeking for solution , I get the message to
upgrade your kernel to start using multi-touch, but is there any hack so
I can use multi touch in e450.
* 2 fingers scrolling not
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1650257/+attachment/4791959/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 121 matches
Mail list logo
