Hello Guys
I just compiled 4.11 final without AMD PINCTRL this morning. Could
someone please test it?
http://www.nextized.net/repo/linux/ubuntu-
linux-4.11.rc8_ryzen01_amd64_generic.tar.gz
Thanks.
Marc
--
You received this bug notification because you are a member of Kernel
Packages, which is
I can confirm the problem with kernel 4.4.0-75-generic.
Removing the virtual dvd drive does not resolve the problem.
I have two virtual machines with attached pysical hard drives - perhaps this is
another cause for the problem?
It is not possible for me to remove the physical drives.
Interesting e
I wanted to detail that I had the DVD drive on a separate SCSI controller
so I just removed the controller not just the DVD drive.
Maybe this is different.
On May 1, 2017 9:50 AM, "Werner Reinersmann" <1679...@bugs.launchpad.net>
wrote:
> I can confirm the problem with kernel 4.4.0-75-generic.
>
Yes, it is odd. I think the post-installation scripts will be run
because the depending linux-image- package might not get
removed (and is present at the time anyway), thus initramfs-tools is
used to create /boot/initrd.img- without the extra kernel
modules provided by linux-image-extra-. I guess t
I also had a crash with the #22~lp1674838 kernel. This happend after 2-3
days, over night when the machine was supposedly mainly idle.
** Attachment added: "syslog.bug2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+attachment/4870237/+files/syslog.bug2
--
You received this b
Looks like I ran into the same bug. Constantly having to restart the
entire system:
[53368.776850] [ cut here ]
[53368.776895] kernel BUG at
/build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!
[53368.776915] invalid opcode: [#1] SMP
[53368.776928] Modules li
Public bug reported:
Extract of system log (Oops part)
Apr 30 12:01:25 salon kernel: [ 8273.281441] Oops: [#1] SMP
Apr 30 12:01:25 salon kernel: [ 8273.281447] Modules linked in: ccm gpio_ich
snd_hda_codec_hdmi joydev input_leds arc4 ath9k ath9k_common coretemp kvm_intel
ath9k_hw ath kvm ir
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1687383
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 commen
Public bug reported:
When plugging in/out my external monitor (Acer B286HK) via an USB-C ->
DP Adapter, there is a great chance, that the computer completely
freezes. SysReq-Keys are also not working.
I added a kernel.log where you can see the boot-up after one crash, than
plugging In/Out the m
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/1687397
Title:
Kernel freeze when plugging in
** Changed in: linux
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/1572901
Title:
i915: No HDMI output with 4.4
Status in Linux:
Confirmed
Stat
After that my system crash. Grub does not start the system. I used grub-
recovery solution.
Solved.
Thank You.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1669071
Title:
pac
I've got the same problem from a number of Ubuntu 16.04 machines.
They're running on Hyper-V and so they've got the following installed as
per Microsoft recommendations:
linux-virtual-lts-xenial linux-tools-virtual-lts-xenial linux-cloud-
tools-virtual-lts-xenial
It happens a few minutes after mo
As a workaround, I've added a cron job that does a directory listing on
the share every minute. It has not stopped the flood but it seems to be
allowing the cifs client to stay connected for a longer period of time
(a major annoyance when the application relies on that share being
available.)
--
I failed to mention my kernel version: 4.4.0-75-generic #96-Ubuntu SMP
--
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/1686099
Title:
connection flood to port 445 on mounting cifs volume
Hi. The same problem here. Release 16.04.2 LTS, iptables 1.6.0-2ubuntu3
etc. I noticed this one in dmesg entry:
$ sudo dmesg |grep iptables
[ 1168.282586] nf_conntrack: automatic helper assignment is deprecated and it
will be removed soon. Use the iptables CT target to attach helpers instead.
I
apport information
** Tags added: apport-collected zesty
** Description changed:
Extract of system log (Oops part)
Apr 30 12:01:25 salon kernel: [ 8273.281441] Oops: [#1] SMP
Apr 30 12:01:25 salon kernel: [ 8273.281447] Modules linked in: ccm gpio_ich
snd_hda_codec_hdmi joydev input_
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870347/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870357/+files/PulseList.txt
--
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/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870354/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870352/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870350/+files/Lspci.txt
--
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/1687383
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870346/+files/CRDA.txt
--
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/1687383
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870358/+files/UdevDb.txt
--
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/1687383
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870351/+files/Lsusb.txt
--
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/1687383
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870353/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870356/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870349/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870355/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870348/+files/IwConfig.txt
--
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/16
Did as requested and changed the status to 'Confirmed'. Let me know if I
can do anything else that could help to solve it.
--
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/1687383
Title:
C
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1687383/+attachment/4870359/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
My workaround may have added some time, but eventually the share
dismounted :(
--
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/1686099
Title:
connection flood to port 445 on mounting cifs
Can folks affected by this bug see if it is fixed with the kernel posted
in comment #12? To test that kernel you would need to install both the
linux-image and linux-image-extra .deb packages. You should see this
bug number in the output of uname -a if it the kernel is installed and
booted.
--
I think I encountered the same thing. The screen would not wake up
though I could still ssh to the system, a lot of commands were not
working, they would just hang or do nothing. Had to resort to a hard
reset. The crash just continued to loop over and over again in the logs
4/30/17 11:11 PM
You have been subscribed to a public bug:
I encountered a problem when trying to install Ubuntu Desktop 17.04 on a
HP Pavilion g7 Notebook with 8 Gigs of memory, on a disk that had been
completely wiped clean. Basically, the installation CD could not connect
to the Internet. I tried both a wired E
** Package changed: ubiquity (Ubuntu) => linux (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/1687113
Title:
Ubuntu 17.04 install cannot connect to internet
Status in linux pac
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1687113
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 commen
@jsalisbury: I can still reproduce this issue with the kernel in #12...
$ uname -a
Linux cola 4.8.0-49-generic #52~lp1679823 SMP Tue Apr 25 17:29:26 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ dmesg | grep enp4s0
[1.194350] e1000e :04:00.0 enp4s0: renamed from eth0
[ 53.469795] enp4s0: In
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
** This bug has been marked a duplicate of bug 1674838
kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
--
You received this bug notification because you are a member of Kernel
It seems I can reproduce this bug now. I'm in the process of "Reverse"
bisecting now, which will identify the commit(s) in mainline that fix
this and are needed in Zesty.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
I did try to install the upstream kernel linux-
image-4.11.0-041100rc8-generic_4.11.0-041100rc8.201704232131_amd64.deb
and linux-
headers-4.11.0-041100rc8-generic_4.11.0-041100rc8.201704232131_amd64.deb
but unfortunately the system barely boots and the networking is messed
up after the change. I c
If you reboot (or unmount/remount) with the "ls every minute" cron job
active, it should prevent the timeout on the share and not reach the
keep-alive echo that starts the flood. I think it is about the
15-minute mark (of inactivity) where the client starts the echo flood.
--
You received this b
Can folks affected by this bug test the 4.10.0-21 kernel? It can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1674838/
--
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/1674838
any news about kernel 4.10.0-20 to fix also openvswitch interfaces (bug
1685742) ?
--
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/1679823
Title:
bond0: Invalid MTU 9000 requested, hw max
This is a quick respin and no need for Cert. testing
** Tags added: regression-testing-passed
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Change
Respin, no need for Cert. testing
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Invalid
** Tags added: regression-testing-passed
** Changed in: kernel-sru-wo
Cannot run:
apport-collect 1687113
As described in the initial bug report, Ubuntu Desktop 17.04 is no
longer installed on the subject machine.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
Needs to be copied to the yakkety security pocket.
** Changed in: kernel-sru-workflow/security-signoff
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/
Does not need to be copied to security pocket.
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Invalid
--
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/1686
@Joseph Salisbury, I'm running the 4.10.0-21 kernel now. Let's see what
happens.
--
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/1674838
Title:
kernel BUG at /build/linux-
7LGLH_/linux
Sorry, I mis-read the git commit history for this kernel, it does NOT
need to go to the yakkety-security pocket. I am unable to change the
status of the security-signoff task to Invalid.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
*** This bug is a duplicate of bug 1679823 ***
https://bugs.launchpad.net/bugs/1679823
** This bug has been marked a duplicate of bug 1679823
bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
--
You received this bug notification because you are a member of Ker
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Invalid
** 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 (ubunt
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Invalid
--
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/1686040
Title:
linux: 4.4.0-77.98 -proposed trac
*** This bug is a duplicate of bug 1686070 ***
https://bugs.launchpad.net/bugs/1686070
This bug was fixed in the package linux - 4.8.0-51.54
---
linux (4.8.0-51.54) yakkety; urgency=low
* linux: 4.8.0-51.54 -proposed tracker (LP: #1686070)
* [Hyper-V][SAUCE] pci-hyperv: Use
This bug was fixed in the package linux - 4.4.0-77.98
---
linux (4.4.0-77.98) xenial; urgency=low
* linux: 4.4.0-77.98 -proposed tracker (LP: #1686040)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 bi
** 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) => Steve
Langasek (vorlon)
--
You received this bug notification because you are a
This bug was fixed in the package linux - 4.4.0-77.98
---
linux (4.4.0-77.98) xenial; urgency=low
* linux: 4.4.0-77.98 -proposed tracker (LP: #1686040)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 bi
This bug was fixed in the package linux - 4.8.0-51.54
---
linux (4.8.0-51.54) yakkety; urgency=low
* linux: 4.8.0-51.54 -proposed tracker (LP: #1686070)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 b
This bug was fixed in the package linux - 4.8.0-51.54
---
linux (4.8.0-51.54) yakkety; urgency=low
* linux: 4.8.0-51.54 -proposed tracker (LP: #1686070)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 b
This bug was fixed in the package linux - 4.4.0-77.98
---
linux (4.4.0-77.98) xenial; urgency=low
* linux: 4.4.0-77.98 -proposed tracker (LP: #1686040)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 bi
This bug was fixed in the package linux - 4.8.0-51.54
---
linux (4.8.0-51.54) yakkety; urgency=low
* linux: 4.8.0-51.54 -proposed tracker (LP: #1686070)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 b
This bug was fixed in the package linux - 4.4.0-77.98
---
linux (4.4.0-77.98) xenial; urgency=low
* linux: 4.4.0-77.98 -proposed tracker (LP: #1686040)
* [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain
(LP: #1684971)
- SAUCE: pci-hyperv: Use only 16 bi
FYI, I switched to the mainline build of 4.10.11 and did *not*
experience this issue. Today I tried to switch back to linux-
image-4.10.0-20-generic (4.10.0-20.22) to see if it had been fixed, and
hit the bug again within a few minutes. Trying out jsalisbury's -21
build now.
Running the mainline
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
Yes, the bisect reported commit da2ba564a6dcf46df4f828624ff55531ff11d5b0
as the culprit. To see if that is the case, I built a kernel with that
commit reverted.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1685865/
Can you test that kernel and report back if it
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tra
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.11 kernel[
Do you have a way to reproduce the bug, or was it a one time event?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1687383
T
Can you see if this bug still exists if you install the latest 17.04
kernel, which can be downloaded from:
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/12451317
To test this kernel, you need to install both the linux-image and linux-
image-extra .deb packages.
** Chan
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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 t
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** 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/1680904
Title:
zesty unable to handle kernel
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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 t
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Ch
Do you have a way to reproduce the oops, or was it a one time event?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
You have been subscribed to a public bug:
On ASRock QC5000M-ITX/PH P1.10 and BIOSTAR Group A68N-2100 4.6.5 the
mouse cursor is displayed distorted since we upgraded to kernel linux-
image-4.4.0-75-generic:amd64
We use 32bit Xubuntu 14.04.5 with 64bit Kernel on about 150 machines.
Core2Duo, Celero
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Zesty)
Status: New => Triaged
** Changed in: linux (Ubuntu Zesty)
Importance: Undecided => Medium
--
You re
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.11 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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 t
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.11 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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 t
This kernel seems to fix the issue. I am able to login via the login
screen.
This is the output of "uname -a"
tisch@tisch-XPS-15-9560:~$ uname -a
Linux tisch-XPS-15-9560 4.11.0-041100-generic #201705010951 SMP Mon May 1
13:53:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
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/1686838
Title:
** Changed in: linux (Ubuntu)
Status: New => Triaged
** 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.
https://bugs.launchpad.net/bugs/1686836
Title:
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** 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.
https://bugs.launchpad.net/bugs/1686828
T
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.11 kernel[
I downgraded to linux-image-4.4.0-66-generic and no longer have the
flooding issue.
--
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/1686099
Title:
connection flood to port 445 on mounting
I finally got time to get access to the computer again. I tried the
4.4.0-62 kernel from xenial-proposed and received "host adapter dead".
Since I last tested I see that 4.4.0-75 is available, so I tried that.
The system booted. It gave me some messages about scsi adapter reset and
a messag about
Thanks for testing. I'll ping upstream and the patch author for
feedback.
--
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/1685865
Title:
Can't login after boot with Kernel 4.11.0-rc7, so
Thanks for extracting the commit. And thanks for caring for this 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/1685865
Title:
Can't login after boot with Kernel 4.11.0-rc7,
** Description changed:
- When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised
correctly and shows with xinput --list as BYDPS/2 BYD Touchpad.
+ When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised
correctly and shows with xinput --list as BYDPS/2 BYD Touchpad.
kernel-bug-exists-upstream
** 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/1687256
Title:
byd touchpad no longer dete
Of the kernels in the mainline ppa i can at the moment confirm that none above
v4.8.17 works (ie 4.8.17-040817-generic), and all of
- v4.9.24
- v4.9.25
- v4.10-rc1
- v4.10.8
- v4.10.12
- v4.10.13
have the bug present.
I'll come back with an update after I've tested the proposed v4.11-rc8 (
http:
Thanks for the testing feedback on my test kernel. I suspect more than
just commit 3331aa378e9bcbd0d16de9034b0c20f4050e26b4 is needed.
dev->max_mtu being set to ETH_MAX_MTU must be needed in other spots.
I'll investigate and post another test kernel shortly.
--
You received this bug notification
It appears commit 3331aa378e9 fixes commit 91572088e3fd. However,
commit 91572088e3fd was introduced in v4.10-rc1 and not cc'd to stable.
The Yakkety 4.8 kernel never had commit 91572088e3fd applied. That
explains why my test kernel did not fix this bug.
Comment #6 says that this same issue happ
The issue started happening as soon as I started using the bluetooth
dongle on this laptop some days ago.
I have tested with latest upstream kernel, both lowlatency and generic,
and the issue is still there: it even happens sooner, just after I
reboot the laptop, no need to enter sleep mode.
So,
Using Joseph's kernel, I'm still running into the same issue.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+attachment/4870532/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
1 - 100 of 132 matches
Mail list logo
