Public bug reported:
Seen on intel Wireless-N 2230 BGN (rev c4).
After the update to said linux firmware version I had issues in connecting to
the WPA enterprise wifi networks EDUROAM and ALMAWIFI. EDUROAM is the European
universities Wi-Fi network. Ability to connect to non enterprise network i
Yes, that is probably the case and it was probably just by chance that
after downgrading the firmware I managed connecting for a couple of
times consecutively. Now, I cannot connect again and the only reliable
way of connecting seems to be by letting the mobile phone connect and
using cable or blue
I have investigated a bit further.
- Using a USB wifi adapter (took me some time to force one to use only
the 2.4 GHz band as my laptop wifi adapter) I can always connect
properly, so the issue is restricted to the intel card I have in my
laptop. This should exclude wpasupplicant and network-manag
Cannot test daily builds right now, but 6.3.0 beta 1 still has the issue.
Launching impress reports:
bluetoothd[1386]: RFCOMM server failed for LibreOffice Impress Remote:
rfcomm_bind: Address already in use (98)
in the system logs and then the remote app cannot contact the host.
--
You received
The premise is that my ignorance on BT is complete. After some
investigation, it is my understanding that RFCOMM channels are to RFCOMM
communication a bit like ports in TCP and UDP, with the main difference
that while there are really a lot of TCP/UDP ports and some of them are
reserved as "well k
Thanks for the analysis!
>From it, I still wonder whether this is a pulseaudio bug, though. Why is
pulseaudio ever binding to RFCOMM channel 3 *before* there is any need
to do so? That is, until I am not connected to any device using channel
3, why is pulseaudio already using it up?
In other word
@John Poole
Can you please indicate that you are also experiencing the issue in the
issue tracker at the document foundation at
https://bugs.documentfoundation.org/show_bug.cgi?id=120663 ?
The issue is still "unconfirmed" there, and until it is "confirmed" by
multiple reporters, there is little c
Issue still present in LibO 6.4.3.1.
I see the bug as still unconfirmed after more than one year. I wonder if
it could be confirmed, given that the same issue has also been reported
for redhat (https://bugzilla.redhat.com/show_bug.cgi?id=1581879)
--
You received this bug notification because you
The bug is also confirmed in the ubuntu launchpad at
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400.
Users there are reporting that they are experiencing the issue in ubuntu
(from bionic, I think) and gentoo. This adds to the reports in fedora
and to the confirmation here on arch lin
Andrzej, I am CC-ing you on this, because I believe that you were one of
the original corder of the BT code for the impress remote on linux. I
hope that you may able to provide some advice on this. If I'm wrong,
please take my apology for the noise.
--
You received this bug notification because y
Wonder if it could be useful to kindly ask Andrzej Hunt if he can look
into the issue. If I am not wrong he is the author of the current bluez
5 code in Impress.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs
Issue persists with current LibO 6.3.1.2 and most likely due to the fact
that the bluetooth stack on linux (bluez) has changed in the past years
and impress has not cought up.
Problem is now more visible due to the startup tooltips in Impress 6.3.x
which explicitly introduce the impress remote fun
I only use the internet key rarely, so it is hard for me to give any
precise indication about when the issue was introduced. I would say that
at the release of artful the issue was not there.
Tested mainline 2.16 and it is OK. Correctly reports "setup of pktcdvd
device failed" rather than oopsing.
In general, it is hard to test modern kernels on artful because of the header
dependence on libssl1.1 (is it really a hard requirement?)
In any case, the fact that 2.16 is OK makes me hope that on the upgrade to
bionic, the issue will automatically be over.
--
You received this bug notification
Public bug reported:
On insertion of a Huawei E173 mobile internet USB stick the artful
kernel now oopses:
BUG: unable to handle kernel NULL pointer dereference at 03d0
[ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd]
Issue seems to be related to the setup of the cdrom-like dev
Public bug reported:
Trying to use the impress remote
(https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with
libreoffice over ubuntu bionic fails.
The handset errors out that it cannot connect with Libreoffice on the
computer even if the bluetooth adapter on the handset and on t
See https://bugzilla.redhat.com/show_bug.cgi?id=1581879
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1798400
Title:
Regression: cannot use impress remote over bluetooth with ubuntu
b
I have stayed a long time without trying impress remote, so I do not
know exactly when the issue started. However, I am sure that last year
at this time (aka on 16.04) the issue did not exist.
Just tried latest non-RC kernel from mainline 4.18.x and the issue is
still there.
** Changed in: linux
I think that the issue can be either a bug in the bluetooth stack or
merely something that has /changed/ in the bluetooth stack, that
libreoffice has not tracked properly. Hence, I have also opened a bug
upstream for LibO, mentioning this one.
--
You received this bug notification because you are
Still present in 6.2.0 RC 1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1798400
Title:
Regression: cannot use impress remote over bluetooth with ubuntu
bionic
Status in LibreOffice
I have occasionally seen this too, in kubuntu 17.04. What is weird is
that it happens only sometimes, and I cannot recognize what triggers the
issue. Last time it went away with a reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to blu
Unable to provide the logs, because when the bug hits, I cannot get to a login
prompt.
If there is a way to get some logs, I'd like to try to help, but I need further
instructions.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification becaus
Public bug reported:
In order to resolve some bugs, to workaround some hardware quirk, or to
help developers test some bug-fixing patch it would be able to:
- Get the sources of the *current* (non mainline) ubuntu kernel
- Apply some patch
- Rebuild the kernel in a PPA (so that it can be made ava
Question expired. Can we reopen the bug as an enhancement request?
--
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/1738761
Title:
Please document how to build a patched version of the cur
Hi, I forgot to report:
the Wily kernel does not have the issue. Only the Vivid kernel has it.
As a matter of fact, according to conversation I had with one of the
kernel developers, the issue may be due to a race. The more modern
kernels do not seem to trigger the problem.
I cannot test the mo
Since it is anyway easy to install the driver in http://www.tp-
link.us/res/down/soft/TL-WN725N_V2_150911.zip, please ignore
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Description changed:
After update to wily, I have continuous disconnections with a tplink
725N wifi usb dongle that uses the r8188eu driver to the point that the
dongle is completely useless.
In vivid, the driver driver shipped with the kernel was problematic but
working a bit bet
Same issue here: DELL Precision T5400 with nvidia graphics cannot
suspend anymore after upgrade to 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/1566302
Title:
Ubuntu 16.04: Sus
*** This bug is a duplicate of bug 1566302 ***
https://bugs.launchpad.net/bugs/1566302
Same issue here: DELL Precision T5400 with nvidia graphics cannot
suspend anymore after upgrade to xenial.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
I see this in kubuntu 14.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/778236
Title:
bluetooth adapter not found after wakeup
Status in “bluez” package in Ubuntu:
Confirmed
Bug d
Same issue here with a Schenker S413, identical to clevo W740SU, Sager
NP240 and System 76 Galago ultrapro.
Probem is worse than described, though.
If you attach an external monitor and
xrandr --ouptput HDMI2 --auto --output eDP1 --off
(i.e. switch on external monitor, off internal one)
then g
Bug is also present in 3.16.x
See also https://bugzilla.kernel.org/show_bug.cgi?id=59321
Please assure that the relevant patches are applied on the trusty (lts)
and utopic (current) kernels.
IMHO this issue is particularly serious because in most cases the system
appears to resume from hibernati
To Jussi...
as the original reporter of this bug, I think it has no hope of being fixed
even if you provide all the relevant kernel commits.
Which is bad, because the crash is serious and happens 'late' when may kernel
data structures may have been written over, with potential data loss.
I trie
Same issue in trusty.
This is in fact a kernel bug: see https://lkml.org/lkml/2014/2/9/316.
Tried mainline (e.g. 3.15.6) and works fine.
There is also another bug in modemmanager/networkmanager. This keeps
rfcomm0 open when the connection is dropped and causes modemmanager to
keep asking the blu
apport information
** Tags added: apport-collected trusty
** Description changed:
Working on kubuntu saucy 64bit. Trying to connect to the internet via an
UMTS phone that is DUN capable over bluetooth (Samsung galaxy)
Setting up things manually, i.e.
bring up rfcomm via rfcomm comm
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175737/+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: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175728/+files/BootDmesg.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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175739/+files/RfKill.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/1300386
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175738/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175729/+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/1300386
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175740/+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/1300386
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175736/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175733/+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/1300386
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175730/+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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175731/+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/13
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175734/+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: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175741/+files/UdevLog.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/1300
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175742/+files/WifiSyslog.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/bug
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175732/+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/1300386
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1300386/+attachment/4175735/+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
Started to see this on an eeepc after upgrade to utopic, that basically
made the wifi so fragile that the laptop cannot be used.
--
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/1318837
Titl
Actually happens with queue 2
--
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/1318837
Title:
1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0
failed to flush
Status
Public bug reported:
During a normal
sudo apt-get dist-upgrade
my "utopic" system reported the need to upgrade the kernel package.
During the process, I saw
Setting up linux-image-3.16.0-24-generic (3.16.0-24.32) ...
Running depmod.
update-initramfs: deferring update (hook will be called later
After tons of testing, I strongly suspect that the issue was with a
failing SATA cable, passing next to the IDE cable of the ZIP disk.
Whenever detaching the ZIP, I was probably bending the SATA cable in
such a way that made it work more reliably. Now the cable has failed
altogether and, after repl
Please disregard my previous message.
The bug is definitely there.
In some cases it does not manifest immediately. Conversely, it is quite
frequent to see the IOWAIT close to zero at system startup. Then after a
while the system is up, the IOWAIT jumps for no reason at about 50% and
stays there.
3.16.7-031607-generic seems to have no issue.
3.19.0-18-generic has the issue
4.0.4-040004-generic cannot be tested because it is impossible for me to use X
with it (the nvidia proprietary driver 304 does not work with it and Kwin does
not work on my hardware without it).
This is already good ne
3.18.14-031814-generic seems to have the 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/1451277
Title:
Extremely high IOWait and processes hungs after utopic->vivid upgrade
Status
Bug is still present as of utopic. Now also verified trying the same
USB3 pci card on an DELL Precision T5400 Server.
Unable to test upstream kernel, but it is extremely likely that the bug
is also present there.
Please, propagate to Sarah Sharp (who said me once "Ubuntu doesn't forward me
bugs
Hack in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/522998/comments/61
seems to work around the 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/1058725
Title:
XHCI (USB 3
Marking the bug as confirmed, since there is a known working workaround,
proving that the bug exists.
** 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://b
After more research, I can confirm the bug and I hope I have also
determined the cause...
1) Bug also happens when booting from the vivid iso image... so it is
not dependent from leftovers due to the utopic->vivid upgrade.
2) Bug stops manifesting if I detach the IOMEGA ZIP drive (with ide
connec
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1451277
Title:
Extremely high IOWait and processes hungs after utopic->vivid
Brad, I cannot provide log files:
- If I boot with the zip disk the machine goes to 60% iowait and processes
dealing with I/O start hunging. I do not want to risk my data just to try
running apport (that would likely fail anyway).
- If I boot without the zip disk, the log files cannot report any
apport-collect 1451277
ERROR: Could not import module, is a package upgrade in progress? Error: No
module named PyQt5.QtCore
Please do not ask things that are clearly beyond the possibilities of
kubuntu vivid after the plasma 5 transition.
** Changed in: linux (Ubuntu)
Status: Incomplete
** Summary changed:
- Extremely high IOWait and processes hungs after utopic->vivid upgrade
+ Extremely high IOWait and processes hungs after utopic->vivid upgrade with
Iomega Zip drive (IDE)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Installed python-pyqt5 as reported in bug 1439784 to make apport-collect
work.
Still getting error apport-collect crashing though.
dpkg-query: no packages found matching linux
Traceback (most recent call last):
File "/usr/share/apport/apport-kde", line 530, in
sys.exit(UserInterface.run_ar
Given that apport collect fails, can the incomplete tag be removed
anyway?
--
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/1451277
Title:
Extremely high IOWait and processes hungs after u
Bug present with 3.17.8 mainline
--
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/1451277
Title:
Extremely high IOWait and processes hungs after utopic->vivid upgrade
with Iomega Zip dri
3.17.0 impossible to test because, for some reason, it fails to boot to
X with the nvidia proprietary driver, so it is hard to test in realistic
conditions.
In any case, I would say that the issue has been introduced in the 3.16
-> 3.17 transition.
Can this be reported upstream?
--
You received
I would also rise priority, since the issue
- makes it often impossible to shut down the machine cleanly, requiring a hard
reset which may result in data loss;
- I imagine that it can make it quite hard to install security updates from
ubuntu as any update of the kernel package tends to result i
Also
hdparm -i /dev/sda
hangs when the iowait goes high.
Note that the issue happens with the drive unmounted.
--
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/1451277
Title:
Extremely
I see it on a laptop that does not connect automatically to the wireless
network after wakeup. But I have the same issue also with a desktop with
wired ethernet. So a more appropriate title would be 'network manager
fails to reconnect after resume', because the issue is not wifi
specific.
After a
As a further note, the script by aztecjoe works around the issue just
fine.
I would recommend delivering it via an updated network manager package
and not waiting for network manager to have the issue fixed. If and when
the issue is fixed in network manager, the redundant restart should not
be a b
Apparently the patches do not include the cc tag for
sta...@vger.kernel.org in the sign-off area which assures that when
applied to the stable tree they are applied also to the stable kernels
without anything else needing to be done by the author or subsystem
maintainer.
Should Gianluca Anzolin or
If the patch series is not applied, after 6 months of raring there will
be 6 more months of saucy without the possibility to use the bluetooth
tethering facility (bluetooth DUN) offered by mobile phones. Sounds bad.
In any case if this patch set is too extensive to apply, the obvious
conclusion is
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189998 and this
bug duplicate each other.
--
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/1165433
Title:
Kernel 3.8.x panics on bluet
Public bug reported:
Attaching the Maxwell (in fact Pioneer) blueray usb drive and trying to
write a blueray disk invariably results in a writing error.
This has been tried both with the ubuntu raring 3.8 kernel and the ppa
mainline 3.10.5 kernel and the result is just the same.
Please report up
Tried 3.10.5 from the mainline ppa.
The situation if possible is even worse.
At boot I get tons of I/O errors on the usb3 disks that make up the raid
components.
In dmesg I find
[ 32.202815] sd 8:0:0:0: [sdf] No Caching mode page present
[ 32.202831] sd 8:0:0:0: [sdf] Assuming drive cache:
Actually, there should be no need to ask for the ubuntu-bug report to
users that are merely confirming a bug for which everything is already
known and everyone is merely waiting for Gianluca Anzolin's patches to
land on the stable update kernel channels.
BTW, ubuntu-bug is quite buggy itself. I gu
I was forgetting...
this on a DELL E6500 using intel Ultimate N wifi 5300 and kubuntu raring
64bit
--
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/1129661
Title:
[8086:4238]: frequents d
I also have an issue with a 5ghz network, where the system keeps
disconnecting and in dmesg I see continuous updates to the crda domain.
Weird enough, loading iwlwifi with the 5ghz_disable does not disable the
5ghz band at all. I still see the APs on the 5ghz band in iwlist wlan0
scan.
--
You re
Dared to test 3.10.2 from ppa mainline. This works without any of the issues of
3.9.8 from the ppa mainline on raring.
So the issue with 3.9.8 seems specific to this kernel. Now I wonder if the
issue is specific to 3.9.8 mainline itself or to the ubuntu ppa build of 3.9.8
mainline. Finding out
Tested 3.10.2 from the mainline ppa (in spite of the bad experience with
3.9.8 that is broken).
The linux bluetooth screen of death is still there, 127 days since first
notification on the LKML for a fully reproducible regression that
completely impairs a subsystem and causes a hard kernel crash w
Isn't this just fixing a leak? Namely, that an object is not destroyed when it
should so memory is wasted?
>From previous messages on LKML the issue causing the crash seemed to be the
>opposite... that an object is destroyed and then its data is used again
>causing memory corruption...
--
You
Thanks for the notice about the Linux-BT ML... I was looking at the
latest posts by Gianluca Anzolin on LKML and that is why I was confused.
This ones look really quite promising.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
Public bug reported:
Hi,
I have a system with a Nec PCI USB 3 adapter (Renesas Technology Corp.
uPD720201 USB 3.0 Host Controller) with a Lindy USB3 disk case for 2
disks attached to it (JMicron Technology Corp. chipset) and two 1TB
disks inside. The Lindy disk case is configured to show the 2 d
In the best case where there is no freeze, the system logs get full of
entries like
Buffer I/O error on device dm-8, logical block 11595768
literally tons of them. And at the end
[ 2472.637908] Buffer I/O error on device dm-8, logical block 11595769
[ 2472.637909] Buffer I/O error on device dm-8
Machine with the raid is not in the same place I usually work, hence it will
take me some time to test.
Unfortunately, every failing test is a >8 hours rebuild time for the array.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Ubuntu bug is buggy and hangs all the time with "You are already logged
in You are already logged in as Sergio Callegari. If this is not you,
please log out now." To make it work, you need to log-out and rerun
apport-collect, not nice. Plus, I am now trying 3.10.3 and obviously
apport
Is it in today 3.8.0-27.40? From the changelogs it doesn't look like.
Can anyone confirm if there is a SRU process in progress for 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/12001
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- Kernel 3.8.x panics on bluetooth DUN disconnect
+ Kernels from 3.8.x to 3.11.x panic on bluetooth DUN disconnect
--
You received this bug notification because you are a member of Kernel
Packages, which is
Fixed the bug title (so that the window of affected kernels is clear and
it is clear that this is an issue both for raring and for saucy.
Also marked as confirmed, since the incomplete label was a bit weird at
this point.
If I understand correctly the situation now is this
1) All kernels from 3.
For the 10th time, tried. Hangs. Apport-collect is buggy and needs
inconvenient workarounds to be used. Please push to have it fixed,
otherwise it won't be used. If it worked fine, it would have been used
it since the first time.
In any case I cannot see how a bug for which there are kernel patche
** Tags removed: kernel-bug-exists-upstream-v3.9-rc7 needs-apport-collect
needs-bisect needs-crash-log needs-upstream-testing regression-potential
** Tags added: kernel-bug-exists-upstream-v3.11.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
There is no activity from me because I have unsubscribed from the bug...
it is just by chance that I am reading this now.
This bug has been investigated and fixed in recent linux ages ago and
Jussi, eccerr0r and I have provided all the relevant information and
pointers in this thread. It has also
I have tried to look into the issue, but I am encountering a situation
that is extremely weird. Hence I hope that someone might be able to
help.
The latest kernel that works from the ubuntu mainline ppa repo is
3.16.7-031607_3.16.7-031607.201410301735
Kernel 3.17.0-031700_3.17.0-031700.2014100606
Please ignore my previous message. Did not wait enough. Bug is present
in 3.17 upstream
--
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/1451277
Title:
Extremely high IOWait and processes
Bisected.
Bug seen after commit 045065d8a300a37218c548e9aa7becd581c6a0e8 [SCSI]
fix qemu boot hang problem.
Actually, the problem is not with that commit that is perfectly fine.
That commit merely lets the real bug be triggered.
Real bug is with scsi host lock and likely to be triggered by mixin
>From LKML conversation, fix https://lkml.org/lkml/2014/11/20/581 is not
likely to be applied upstream, because it probably just papers over the
real bug.
The real issue appears with the patch series "scsi: convert host_busy to
atomic_t" that causes regressions on some hardware configurations. Mig
Public bug reported:
Hi,
In the process of working around an issue that has appeared in the linux
kernel after the patch series "convert host_busy to atomic_t" (see bug
1451277), I would like to compile kernel deb packages that work around
the issue in a PPA, using patches that appeared on the L
1 - 100 of 123 matches
Mail list logo
