** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776443
Title:
iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
To manage notifications about this bug go to:
https://bug
I installed the 5.0.0-15-generic kernel and removed iwlwifi from the
/etc/modprobe.d/blacklist. The system was stable and ran very well for 4
or 5 hours.
When I booted it (still generic kernel) this morning, it failed after
about 20 minutes. I rebooted and teed journalctl for documentation. The
fa
On 17/5/19 1:14 am, Kai-Heng Feng wrote:
> Sorry for the late reply. Does this happen on generic kernel?
>
It is so good to hear from anyone on this problem, so I welcome your
"late reply"!
My laptop runs ubuntu studio 19.04, but studio stopped including the
linux-generic package many releases
Sorry for the late reply. Does this happen on generic kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776443
Title:
iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
To manage notif
After upgrading to 19.04 disco, the system is still too unstable to be
useful. The current kernel is 5.0.0-13-lowlatency
(buildd@lcy01-amd64-020).
I note the Intel driver has not changed after the upgrade from 18.10
cosmic, i.e. still iwlwifi-7265D-29.ucode, packaged within linux-
firmware version
Is anything happening with this bug report? Are you waiting for me to do
something more, or provide more information.
If it has been passed upstream as I anticipated, could you let me have
details so that I can follow progress there, please?
--
You received this bug notification because you are
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776443
Title:
iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
To manage notifications about this
Thanks for your comment, Kai-Heng, but I did try the latest upstrem
kernel at the weekend. Please refer to my post #8.
Is there a good reason to try a kernel more recent than:-
linux-image-
unsigned-4.17.0-041700-lowlatency_4.17.0-041700.201806041953_amd64.deb
... along with its associated heade
Please give #3 a try...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776443
Title:
iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
To manage notifications about this bug go to:
https:/
** Attachment added: "current bionic lowlatency log when driver hangs"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5155779/+files/bacchus-wifi-hang-log-13-unifi-xb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I installed the latest upstream kernel, headers and modules. As far as I
can tell, it suffers exactly the same failure as the latest released
bionic lowlatency kernel. The stack ttrace seems very similar and the
timeout message looks to be the same. My guess is still the intel
iwlwifi version 29 fi
** Attachment added: "upstream kernel log when driver hang is reported"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5155778/+files/bacchus-wifi-hang-log-14-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Joseph... I also thought I had mentioned this a quite a new machine, so
it doesn't have a lot of history. However, I had a similar wifi failure
quite often with the latest 17.10 kernel before the upgrade to 18.04.
I will look for a 17.10 log if you think it would be helpful, but I'm
not sure I kep
I won't confuse the matter with details, but after I reproduced the
problem (obviously) apport could not reach launchpad because the wifi
adapter was out of action. I connected an ethernet cable, but then
apport failed on three different attempts.
I was under the impression I had attached a "journ
** Attachment added: "Most recent log with firmware register dump and driver
stack trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5152884/+files/bacchus-wifi-hang-log-12-unifi
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
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.17 kernel[
I'm pretty sure the same hardware adapter and firmware is supporting
bluetooth for my logitech mouse.
** Tags added: wifi
** Tags added: intel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776443
T
brian@bacchus:~$ uname -a
Linux bacchus 4.15.0-22-lowlatency #24-Ubuntu SMP PREEMPT Wed May 16 17:09:05
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
brian@bacchus:~$ lsb_release -a
LSB Version:
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distri
18 matches
Mail list logo
