** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Zesty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Zesty)
Status: New => Fix Committed
**
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Zesty)
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.
Public bug reported:
The ubuntu/xr-usb-serial is expected to be built for i386 and x86_64,
and in ubuntu/Makefile it says:
ifneq ($(filter $(ARCH), i386 x86_64),)
obj-y += xr-usb-serial/
endif
Since ARCH is x86 for both i386 and x86_64, this condition will never be
true thus the module will
These three commits should be included in next (or next one after that)
for 4.13 kernel:
f6c7b8031d7e177c837c23d1065204b697fb54b7 platform/x86: peaq-wmi: Remove
unnecessary checks from peaq_wmi_exit
d6fa71f1c003fb2bc824276bb424a4171f9a717f platform/x86: peaq_wmi: Fix missing
terminating entry
Dave,
Please try this kernel,
http://people.canonical.com/~khfeng/lp1729674/
The temporary workaround is what we can get before chip vendors solve
the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
cat /sys/power/mem_sleep
[s2idle]
--
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/1732424
Title:
Surface Pro 4. System hangs when suspended or hibernated
Status in linux package in
This is the dmesg output before a crash. I'll add another dmesg output
when I get the next crash.
** Attachment added: "dmesg-output.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729030/+attachment/5011563/+files/dmesg-output.log
--
You received this bug notification because
--- Comment From sikri...@in.ibm.com 2017-11-20 04:13 EDT---
Hi Daniel,
When one enables largesend offload in AIX, MTU still stays at 1500 (when
Jumbo frames are disabled) and 9000 (when Jumbo frames are enabled). So,
when a workload pushes data > MTU sizes, AIX LPAR will send the bigger
Somebody can tell where to follow the input maintainers?
Thank's!
--
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/1400463
Title:
[Medion Akoya P2214T] Touchpad not properly recognized
At Sun, 19 Nov 2017 20:13:35 -, Christopher M. Penalver wrote:
> ...would you like this report to remain open for when your schedule
> opens up, or would you like to close this report as Status Invalid?...
Dear Christopher M. Penalver
as far as I am concerned, I fear I will not be able to
Possible upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=197147
** Bug watch added: Linux Kernel Bug Tracker #197147
https://bugzilla.kernel.org/show_bug.cgi?id=197147
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Can you try the daily kernel? It has some new commits on hid-asus.
--
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/1732686
Title:
Asus Fx553VD - Keyboard LED backlight controls are not
--- Comment From vaish...@in.ibm.com 2017-11-20 04:01 EDT---
*** This bug has been marked as a duplicate of bug 142747 ***
--
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/1658968
--- Comment From chand...@in.ibm.com 2017-11-20 04:10 EDT---
(In reply to comment #18)
> (In reply to comment #16)
> > Noticed that the offset for crashkernel is set to 32MB in
> > /etc/default/grub.d/kdump-tools..ppc64el file . Any specific reason
> > why this value is chosen? With the
(IBM Bugzilla duplicate)
--
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/1658968
Title:
ubuntu 16.04.2: crashed at deactivate_slab+0x18c/0x640 when testing
dlpar
Status in The
Since on 8th Nov you wrote "in 5 days or it will be dropped" (I verified
and it was good) I expected a fix to be released already.
Not super important, but can you share an ETA on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
As far as I know, it's impossible to follow them and it looks as though
they have not been doing anything anymore to fix the issue. Kai-Heng
Feng did his best and sent them an e-mail, but I never got a response
from them. He suggested to ask ITE Tech to debug the issue, but I've
given up and have
My guess is that it doesn't support S3 at all.
Does suspend work on v4.14?
--
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/1520965
Title:
Lenovo Helix does not wake up from suspend
Public bug reported:
I'm encountering many random kernel panic after enabling fsc with NFS.
Then I see a number of following err msgs right before it crashed.
Nov 20 12:04:26 g2 kernel: [170689.549374] FS-Cache:
Nov 20 12:04:26 g2 kernel: [170689.549381] FS-Cache: Assertion failed
Nov 20
** 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/1729337
Title:
CIFS errors on 4.4.0-98, but not on
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
**
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Artful)
Status: New => Fix Committed
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/verification-testing
Status: Invalid => Confirmed
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => 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/1728927
Title:
linux: 4.13.0-17.20
This change was made by a bot.
** Changed in: linux (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/1733306
Title:
FS-Cache: Assertion failed
Hi cking,
I rarely use it, but for me (on Xenial) the following worked.
$ sudo apt install vagrant virtualbox
$ vagrant init ubuntu/artful64
# note that you have to elminate all KVMs before you can do the next step
$ vagrant up
$ vagrant ssh
vagrant@ubuntu-artful:~$ df -h /
Filesystem Size
With the above in comment #17 I see the limited size after boot and the crash
in dmesg.
But then a repro with
$ sudo resize2fs /dev/sda1
doesn't work - well it works, but that is the problem it works to resize
without triggering the issue "again".
--
You received this bug notification
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Zesty)
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => High
** Changed in: linux (Ubuntu Artful)
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 one:
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/linux-
image-4.14.0-999-generic_4.14.0-999.201711192100_amd64.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1. Verified on both Ubuntu Linux 17.10 and Windows 10
2. The official ubuntu/artful64 box:
https://app.vagrantup.com/ubuntu/boxes/artful64. The problem is verified with
the currently latest version (v20171115.1.0)
3. Verified with the minimal vagrant configuration (see attached Vagrantfile).
This bug was fixed in the package linux - 4.10.0-40.44
---
linux (4.10.0-40.44) zesty; urgency=low
* linux: 4.10.0-40.44 -proposed tracker (LP: #1731269)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in gup_huge_pmd()
This bug was fixed in the package linux - 4.10.0-40.44
---
linux (4.10.0-40.44) zesty; urgency=low
* linux: 4.10.0-40.44 -proposed tracker (LP: #1731269)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in gup_huge_pmd()
This bug was fixed in the package linux - 4.10.0-40.44
---
linux (4.10.0-40.44) zesty; urgency=low
* linux: 4.10.0-40.44 -proposed tracker (LP: #1731269)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in gup_huge_pmd()
This bug was fixed in the package linux - 4.10.0-40.44
---
linux (4.10.0-40.44) zesty; urgency=low
* linux: 4.10.0-40.44 -proposed tracker (LP: #1731269)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in gup_huge_pmd()
*** This bug is a duplicate of bug 1731269 ***
https://bugs.launchpad.net/bugs/1731269
This bug was fixed in the package linux - 4.10.0-40.44
---
linux (4.10.0-40.44) zesty; urgency=low
* linux: 4.10.0-40.44 -proposed tracker (LP: #1731269)
* s390/mm: fix write access check
This bug was fixed in the package linux - 4.10.0-40.44
---
linux (4.10.0-40.44) zesty; urgency=low
* linux: 4.10.0-40.44 -proposed tracker (LP: #1731269)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in gup_huge_pmd()
This bug was fixed in the package linux - 4.10.0-40.44
---
linux (4.10.0-40.44) zesty; urgency=low
* linux: 4.10.0-40.44 -proposed tracker (LP: #1731269)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in gup_huge_pmd()
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux - 4.10.0-40.44
---
linux (4.10.0-40.44) zesty; urgency=low
* linux: 4.10.0-40.44 -proposed tracker (LP: #1731269)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in gup_huge_pmd()
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-aws - 4.4.0-1041.50
---
linux-aws (4.4.0-1041.50) xenial; urgency=low
* linux-aws: 4.4.0-1041.50 -proposed tracker (LP: #1732535)
* xen hibernation support for linux-aws (LP: #1732512)
- aws: [Config] disable SUSPEND
- aws:
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
*** This bug is a duplicate of bug 1732535 ***
https://bugs.launchpad.net/bugs/1732535
This bug was fixed in the package linux-aws - 4.4.0-1041.50
---
linux-aws (4.4.0-1041.50) xenial; urgency=low
* linux-aws: 4.4.0-1041.50 -proposed tracker (LP: #1732535)
* xen hibernation
This bug was fixed in the package linux-meta-aws - 4.4.0.1041.43
---
linux-meta-aws (4.4.0.1041.43) xenial; urgency=medium
* Bump ABI 4.4.0-1041
* Switch Vcs-Git: url to fully expanded form (LP: #1730648)
- [Config] Change Vcs-Git: URL to point to correct package
-- Kamal
This bug was fixed in the package linux-aws - 4.4.0-1041.50
---
linux-aws (4.4.0-1041.50) xenial; urgency=low
* linux-aws: 4.4.0-1041.50 -proposed tracker (LP: #1732535)
* xen hibernation support for linux-aws (LP: #1732512)
- aws: [Config] disable SUSPEND
- aws:
This bug was fixed in the package linux-aws - 4.4.0-1041.50
---
linux-aws (4.4.0-1041.50) xenial; urgency=low
* linux-aws: 4.4.0-1041.50 -proposed tracker (LP: #1732535)
* xen hibernation support for linux-aws (LP: #1732512)
- aws: [Config] disable SUSPEND
- aws:
*** This bug is a duplicate of bug 1731264 ***
https://bugs.launchpad.net/bugs/1731264
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access
This bug was fixed in the package linux-aws - 4.4.0-1041.50
---
linux-aws (4.4.0-1041.50) xenial; urgency=low
* linux-aws: 4.4.0-1041.50 -proposed tracker (LP: #1732535)
* xen hibernation support for linux-aws (LP: #1732512)
- aws: [Config] disable SUSPEND
- aws:
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
Thanks, can reproduce the issue now, will debug
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Status in cloud-images:
This bug was fixed in the package linux-aws - 4.4.0-1041.50
---
linux-aws (4.4.0-1041.50) xenial; urgency=low
* linux-aws: 4.4.0-1041.50 -proposed tracker (LP: #1732535)
* xen hibernation support for linux-aws (LP: #1732512)
- aws: [Config] disable SUSPEND
- aws:
*** This bug is a duplicate of bug 1731264 ***
https://bugs.launchpad.net/bugs/1731264
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access
I can confirm @paelzer's comment above, resize2fs after vagrant up
works. In fact this helps me in the short term, as adding `resize2fs
/dev/sda1` to the beginning of my provision script resolves my issue.
But this is just a workaround and not a real solution.
--
You received this bug
This bug was fixed in the package linux-aws - 4.4.0-1041.50
---
linux-aws (4.4.0-1041.50) xenial; urgency=low
* linux-aws: 4.4.0-1041.50 -proposed tracker (LP: #1732535)
* xen hibernation support for linux-aws (LP: #1732512)
- aws: [Config] disable SUSPEND
- aws:
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
This bug was fixed in the package linux-aws - 4.4.0-1041.50
---
linux-aws (4.4.0-1041.50) xenial; urgency=low
* linux-aws: 4.4.0-1041.50 -proposed tracker (LP: #1732535)
* xen hibernation support for linux-aws (LP: #1732512)
- aws: [Config] disable SUSPEND
- aws:
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
This bug was fixed in the package linux-aws - 4.4.0-1041.50
---
linux-aws (4.4.0-1041.50) xenial; urgency=low
* linux-aws: 4.4.0-1041.50 -proposed tracker (LP: #1732535)
* xen hibernation support for linux-aws (LP: #1732512)
- aws: [Config] disable SUSPEND
- aws:
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
This bug was fixed in the package linux - 4.4.0-101.124
---
linux (4.4.0-101.124) xenial; urgency=low
* linux: 4.4.0-101.124 -proposed tracker (LP: #1731264)
* s390/mm: fix write access check in gup_huge_pmd() (LP: #1730596)
- s390/mm: fix write access check in
** Package changed: linux (Ubuntu) => linux-oem (Ubuntu)
--
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/1731822
Title:
system can't detect external microphone with the codec alc274
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => Medium
**
** Tags removed: bugnameltc-161493 kernel-da-key severity-high triage-g
--
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/1732978
Title:
Ubuntu 17.10: Include patch "crypto: vmx - Use
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14
** Tags added: triage-g
--
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/1732978
Title:
Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
fallback"
Status in The
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14
** Package changed: linux (Ubuntu) => apparmor (Ubuntu)
** Changed in: apparmor (Ubuntu)
Status: Confirmed => 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/1733070
Title:
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14
** Tags removed: kernel-key
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1730596
Title:
s390/mm: fix write access check in gup_huge_pmd()
Status in
311ac00deff520820d198cda141109f2a5655d4a 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/1724911
Title:
text VTs are unavailable on desktop after upgrade to Ubuntu 17.10
Status
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1733357
and then change the status of the bug to 'Confirmed'.
If, due to the
This is an image of the line that is visible in the sequence between the Grub
menu and the Recovery Menu.
Hope that helps.
** Attachment added: "Image of line with ERROR in it"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+attachment/5011745/+files/20171120_152818.jpg
--
I built a 17.10 test kernel with a pick of commit e666d4e9ceec94. The
test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1732978/
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of Kernel
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Artful)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Yo!
Have you read that nice article already, it's so interesting, please
read it here http://www.triathloncoach-
ted.com/donate.php?UE80Mzc3NjBAYnVncy5sYXVuY2hwYWQubmV0
See you around, Danielle Trotter
--
You received this bug notification because you are a member of Kernel
Packages,
Validated the test kernel in the PPA by installing it onto a QDF2400
device running 16.04.3
Used JTAG to trigger multiple concurrent errors, and observed that all
errors were parsed, instead of just the first one:
root@ubuntu:/home/ubuntu# cat /sys/kernel/debug/tracing/trace
# tracer: nop
#
#
I reviewed your patch, and it appears as if it only turns off receive
checksumming. The internets are saying that transmit needs to be turned off
as well. Have you checked to see if transmit is affected as well?
I will try to do some transmit tests. I'll also "test" your kernel when I
get a
Public bug reported:
Since the following updates installed on Friday Nov 17 my system will no
longer go into suspend or hibernate via the keybord or the logout screen
when Suspend is selected. It will, however, suspend via the command
line with pm-syspend or pm-suspend-hybrid.
As a temp
** Changed in: xserver-xorg-video-intel
Status: Confirmed => Won't 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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR:
I've tested all the following 64bit versions:
version before 3.13 were not starting
version 3.14 and 3.15 were starting only with x.org
for 3.16 and above start with wayland or xorg.
That said, all the 64 bit version fail in managing the suspend resume.
Using the old 14.04.1 32 bit from CD
apport-collect 1733357 is sticks me at a blank launchpad 'Already logged
in' page with no way to indicate any decision.
@jsalsbury, sorry, I don't recall a kernel update for 17.10 and there is
only one option in my boot menu. This problem seems to have fixed
itself though. After todays updates
My current hunch is that this is due to blk optimization functionality
that landed in the kernel and perhaps the virt blk device on VirtualBox
does not support it yet.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => In
** Summary changed:
- [HP ProBook 4530s] Intel Powerclamp is Slowing CPU
+ [HP ProBook 4530s / Lenovo G580] Intel Powerclamp is Slowing CPU
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Kai , thank you so much!
That one works nicely , i can adjust the brightness of keyboard and turn
on and off my keyboard light.
Thanks again.
One last question though ; what can i do for ACPI errors?
--
You received this bug notification because you are a member of Kernel
Packages, which is
git bisect'd to:
c20cfc27a47307e811346f85959cf3cc07ae42f9 is the first bad commit
commit c20cfc27a47307e811346f85959cf3cc07ae42f9
Author: Christoph Hellwig
Date: Wed Apr 5 19:21:07 2017 +0200
block: stop using blkdev_issue_write_same for zeroing
We'll always use the
Good to know, thank you for your support. The issue is fixed in
4.13.0-16-generic of Ubuntu 17.10 as stated in #16.
--
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/1721856
Title:
Suspend
Does the bug go away if you boot back into the prior kernel version?
** Tags added: artful needs-bisect
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'll try and figure out *why* this patch is causing the kernel grief
tomorrow.
--
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/1726818
Title:
vagrant artful64 box filesystem too small
Whilst one cannot revert this for 4.13, I did remove the offending code,
rebuilt and now one can boot without the kernel failure and the hdd is
resized correctly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 196 matches
Mail list logo