This problem seems to exist currently on both 15.10 and 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/1085766
Title:
/var/log/upstart/ureadahead.log contains garbage
Status in
Tim, thank you very much for cherry picking this into the 4.3 Xenial
tree!
--
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/1498633
Title:
drivers/net/ethernet/atheros/alx: please add
This change is now in Linus's 4.4rc4 tree:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0208e951d55c435137543e12d7ee795c3784713a
Which means it will make it into Xenial, and could be cherry picked into
the Xenial 4.3 branch in the mean time.
--
You received this
This change is now in linux-next, should be in 4.4rc2:
https://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/commit/?id=6d5b18ae67b32dd4dcf1c91a172f2424e72ae74c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This change has now been accepted into davem's net tree, should
hopefully make its way into Linux 4.4:
https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=0208e951d55c435137543e12d7ee795c3784713a
Big thanks again to the Ubuntu kernel team for carrying this as a sauce
patch in
** Changed in: system76
Status: New => Triaged
** Changed in: system76
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/1413440
Title:
USB stops
** Changed in: system76
Status: Triaged => 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/1498633
Title:
drivers/net/ethernet/atheros/alx: please add device ID for
Public bug reported:
The intel pstate driver is currently quite broken on on Skylake
hardware.
The symptom is that the pstate driver can scale the frequency up, but
wont then scale it back down. So as soon as you hit a decent amount of
CPU load, you get stuck fluctuating in the turbo frequency
Thanks, Tim!
--
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/1499040
Title:
Wily: Skylake: intel_pstate: fix PCT_TO_HWP macro
Status in linux package in Ubuntu:
Fix Committed
Status
** Affects: system76
Importance: Critical
Assignee: Jason Gerard DeRose (jderose)
Status: Triaged
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug wily
** Patch added: "Killer-E2400-device-ID.patch"
https://b
Thanks, Tim!
--
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/1498633
Title:
drivers/net/ethernet/atheros/alx: please add device ID for Killer
E2400
Status in System76:
Triaged
Ah, yes, I meant the lts-wily HWE stack. Thanks!
--
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/1497481
Title:
lts-vivid kernel has IWL8000_UCODE_API_MAX=12, but only iwlwifi-
Seth,
Gotcha, thanks! So is the expectation then that 8260 WiFi cards wont be
usable on Trusty till 14.04.4 (lts-vivid HWE)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Public bug reported:
Intel 8260 WiFi cards currently aren't usable on 14.04.3 (with lts-vivid
HWE, 3.19 kernel).
The problem is that in the kernel, iwl-8000.c defines an
IWL8000_UCODE_API_MAX of 12:
#define IWL8000_UCODE_API_MAX 12
But /lib/firmware/iwlwifi-8000C-13.ucode is the only 8000
Public bug reported:
On Skylake, the skl_dmc firmware is failing to load. From dmesg:
[0.728803] i915 :00:02.0: Direct firmware load for
i915/skl_dmc_ver1.bin failed with error -2
[0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to
load firmware
I spent a lot of time beating on the proposed Trusty nvidia-346
(346.82-0ubuntu0.2) and nvidia-340 (340.76-0ubuntu0.1) packages
yesterday, and things seem solid to me.
Package upgrade/downgrade paths I tested:
331 -- 340
331 -- 346
340 -- 346
346 -- 340
I tested that things work correctly re
@myramenisgone - so the xorg-edgers PPA fixes this for you on 15.04?
I haven't yet filed an upstream bug because I still haven't figured out
whether this is a bug in the kernel vs. xserver-xorg-video-intel, etc.
But if the xorg-edgers PPA fixes this for you on 15.04, that's an
extremely helpful
** Changed in: system76
Status: Triaged = 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/1457369
Title:
kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel
Status
** Changed in: system76
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/1442411
Title:
Intel 3160 wireless card no longer able to connect to
@sforshee - thank you very much for your explanation, I think I'm
starting to understand the issue better.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/1437913
Title:
@sforshee - I'm trying to better understand the consequences of Ubuntu
currently having an an old regulatory database version, as some
System76 customers are having WiFi problems when connecting to AC
routers with an Intel 7265 and `sudo iw reg set US` seems to fix their
issues.
In particular,
Okay, after some more careful testing,
afcee962b09842d0f4191beb4a2d08251b4c7705 does indeed fix the problem.
I was having some unrelated issues when connecting to 2.4GHz N when too
far away from the access point (lots of WiFi interference here at
System76 HQ).
But the important thing is that
I'm not sure what the relevant difference is, but I'm still having
trouble connecting to 2.4GHz N networks with an Intel 3160 when running
3.19.0-20-generic from proposed (when Bluetooth is turned on). In
particular, my 2.4GHz N SSID frequently isn't showing up in the list of
available access
Likewise, I can confirm that 3.19.0-20-genric from proposed does fix
this problem.
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1457369
Title:
kernel 3.19.0-18 breaks HDMI
I can confirm this bug on a System76 Kudu Professional (i7-4900MQ).
Booting with 3.19.0-18-generic, I don't get any HDMI option in the
Output tab in the sound settings UI.
Booting with 3.19.0-16-generic, I get an HDMI option and it works fine.
So this is definitely a regression between
I can confirm this bug on a System76 Kudu Professional (i7-4900MQ).
Booting with 3.19.0-18-generic, I don't get any HDMI option in the
Output tab in the sound settings UI.
Booting with 3.19.0-16-generic, I get an HDMI option and it works fine.
So this is a regression between 3.19.0-16-generic
This bug should also probably be marked as a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457369
--
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/1458922
Title:
No
@boratko - no problem, thanks for figuring out that it was related to
bluetooth being turned on!
--
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/1442411
Title:
Intel 3160 wireless card
Mostly just confirming what @boratko already shared, plus perhaps a few
new details:
The ingredients needed to reproduce this bug on Vivid:
1) Intel 3160 WiFi card
2) Boot with bluetooth enabled (turn on in the bluetooth indicator and
reboot if needed)
3) Connect to a 2.4 GHz N router
In
** Also affects: system76
Importance: Undecided
Status: New
** Changed in: system76
Status: New = Triaged
** Changed in: system76
Assignee: (unassigned) = Jason Gerard DeRose (jderose)
--
You received this bug notification because you are a member of Kernel
Packages
** Changed in: system76
Importance: Undecided = Critical
--
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/1442411
Title:
Intel 3160 wireless card no longer able to connect to wifi
Attaching the patch from:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=afcee962b09842d0f4191beb4a2d08251b4c7705
** Patch added: fix-1442411.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1442411/+attachment/4397772/+files/fix-1442411.patch
** Changed
Okay, afcee962b09842d0f4191beb4a2d08251b4c7705 seems to fix this
problem:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=afcee962b09842d0f4191beb4a2d08251b4c7705
I cherry-picked it into the current ubuntu-vivid.git tree and built a
kernel, and have had no problems so
@boratko - what's the full git commit ID of the of the mainline commit
that fixes this?
--
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/1442411
Title:
Intel 3160 wireless card no longer
** Also affects: system76
Importance: Undecided
Status: New
** Description changed:
- On a 1366x768 Broadwell i3-5010U laptop (System76 Lemur lemu4),
+ On a 1366x768 Broadwell i3-5010U laptop (System76 Lemur lemu5),
sometimes after I logout there is strange horizontal
Public bug reported:
On a 1366x768 Broadwell i3-5010U laptop (System76 Lemur lemu4),
sometimes after I logout there is strange horizontal wrapping/scrolling
corruption at the lightdm login screen plus a fixed vertical wrapping
(see attached video).
After the first time that the screen goes
Colan,
How frequently does this happen, would you say? What percentage of
suspend/resumes encounter this failure?
If you're up for it, the FirmWare Test Suite has a handy way to
repeatedly rest suspend/resume:
https://wiki.ubuntu.com/Kernel/Reference/fwts
Which you can run like this:
sudo
Thanks for the feedback!
System76 has been doing extensive testing internally on Utopic since the
3.16 kernel landed. Thus far we haven't encountered this resume from
suspend issue, but we'll keep a eye out for it!
--
You received this bug notification because you are a member of Kernel
Is this still happening with the 3.16.0-18-generic kernel (current
Utopic kernel)?
--
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/1332398
Title:
[System76, Inc. Galago UltraPro]
I'm not sure whether this can provide any clues, but this Ubiquity oem-
config crash rings a bit similar in that it's only happening when
running under KVM, not when running on hardware:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1374193
Haven't tried it yet on Virtual Box, though.
As far as I can tell, there is no difference between using the proposed
linux-firmware (1.127.5) package vs the stable linux-firmware (1.127.4)
package plus a manually installed /lib/firmware/iwlwifi-7260-8.ucode
file, a combination that has produced favorable results in my previous
testing.
I
Hmm, I guess a verification-needed tag wasn't actually present,
despite the (automated?) comment #69.
Regardless, I added a verification-done tag for good measure :D
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1293569
Title:
iwlwifi-7260-8.ucode causes
I put 3.13.0-32.56 with the iwlwifi-7260-8.ucode through around 32 hours
of continuous testing on a 7260 WiFi card and encountered zero
disconnects.
I tested with a mix of both sustained high network utilization and long
periods of inactivity, both when running on battery and when running on
AC,
I've been testing the proposed trusty kernel (3.13.0-32.56) with the
iwlwifi-7260-8.ucode firmware, and so far so good:
$ dmesg | grep 22.24.8.0
[2.840202] iwlwifi :04:00.0: loaded firmware version 22.24.8.0 op_mode
iwlmvm
Experience is similar to when I was testing Seth's patched
@jasauders: you'll need to download iwlwifi-7260-ucode-22.24.8.0.tgz
from here:
http://wireless.kernel.org/en/users/Drivers/iwlwifi
Extract the tarball, then copy iwlwifi-7260-8.ucode into /lib/firmware,
then reboot, check dmesg to make sure it loaded the correct version:
$ dmesg | grep iwlwifi
Seth, I noticed that the linux-firmware package in proposed (1.127.3)
doesn't have the 7260 -8 firmware, but does have the 3160 -8 firmware?
Is this intentional?
$ dpkg -L linux-firmware | egrep 7260|3160
/lib/firmware/iwlwifi-3160-8.ucode
/lib/firmware/iwlwifi-7260-7.ucode
Public bug reported:
The current linux-firmware package in proposed (1.127.3) added the -8
firmware for the Intel 3160, but not for Intel 7260.
This seems like it was perhaps a mistake, as the -9 firmware has been
added for both.
$ dpkg -L linux-firmware | egrep 7260|3160
Seth,
Progress report from testing your patched 3.13.0-27 build... I made it
through almost 5 days of continuous use without a disconnect. Even
though I did eventually get a disconnect, it seems to happen far less
frequently with the -8 firmware when combined with the disabled beacon
filtering.
Emmanuel, maybe I'm missing something obvious, but isn't wpasupplicant
2.1 already the newest version?
http://w1.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/ChangeLog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Scott,
I've been testing your kernel build with the iwlwifi-7260-8.ucode
firmware (22.24.8.0), and so far so good. Although the particular
problem I've been encountering sometimes takes a day or two to occur, so
I'll let you know how it fairs after a few more days of use.
However, I have
Emmanuel,
I'll test the -9.ucode ASAP. Are there any bits from 3.14 or 3.15 that
should be backported in order for the Ubuntu 3.13 kernel to work best
with the -9.ucode?
System76 customers are experiencing a lot of problems with 7260/3160
cards, and so we're keen on getting -9.ucode in a
Seth,
Just finish building. All I did was bump IWL7260_UCODE_API_MAX,
IWL3160_UCODE_API_MAX to 9.
Loaded -9 firmware correctly, seems to be working fine so far:
[2.936156] iwlwifi :04:00.0: loaded firmware version 23.214.9.0
op_mode
--
You received this bug notification because you
Seth, is this newer 7260 firmware being applied to the Saucy kernel
also?
--
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/1265550
Title:
linux-firmware: iwlwifi: add firmware
** Also affects: system76
Importance: Undecided
Status: New
--
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/1261668
Title:
Intel 7260 firmware causes crashes, needs
Colin,
Thank you very much for this bug report. I've encountered some stability
issues with USB3 hard drives and the 3.11.0-13-generic kernel, but your
report makes it sound like it effects all USB devices (at least when
plugged into USB3 ports, it seems).
I probably wont have a chance to dig
No, this hasn't happened on Raring, but it didn't previously happen in
Saucy either.
One difference is that the 2nd time testing under Saucy I was connected
to a 2560x1600 monitor via DVI, vs a 1920x1080 monitor via HDMI.
Later this week I'll be able to do more testing and to try and narrow
Public bug reported:
This crash occured while running:
sudo fwts s3 --s3-multiple=500
At one point the resume seemed to hang, so I did a hardware reboot, then
got this Apport crash.
We're in the process of doing our final stability testing to see whether
we can use X.M.P 1833MHz when the
58 matches
Mail list logo