I can reproduce this on Fedora 40, which likely indicates that it's an
upstream bug.
Workaround: disable c-states in BIOS.
--
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/1978133
Title:
Hello Brothers!
Shouldn't Quanta or Acer accurately propose a patch to make your device
work natively on recent kernels?
Or do they do this but the team that maintains the kernel takes a while to
accept the changes?
[]s
Em sex., 29 de set. de 2023 às 09:00, Giuliano Lotta <
2000...@bugs.launchp
I just found many similar reports.
1. https://github.com/QubesOS/qubes-issues/issues/6923
2. https://gitlab.freedesktop.org/drm/amd/-/issues/2266
3. https://gitlab.freedesktop.org/drm/amd/-/issues/822
They all have the same amdgpu errors:
```
mar 01 23:01:25 workstation1 kernel: [drm:psp_load_no
It happened again. Notice the same amdgpu errors near the end.
** Attachment added: "second_freeze.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+attachment/5650838/+files/second_freeze.log
--
You received this bug notification because you are a member of Kernel
Packages,
** Tags added: kubuntu
--
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/2008118
Title:
Freeze on resume from suspend (amdgpu errors)
Status in linux package in Ubuntu:
Confirmed
Bug de
This only affects automatic suspension (activated by idle time).
Manually suspending the system works as expected.
--
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/2008118
Title:
Freeze on
This contains the logs from the resume attempt that failed.
** Attachment added: "logs from the relevant boot (sudo journalctl -b -1)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+attachment/5649176/+files/journalctl.log
--
You received this bug notification because you are
Public bug reported:
I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
resuming from suspend-to-RAM, the system will freeze. Sometimes the
screen is all black, while other times it is showing the lock screen; in
both cases it's completely unresponsive.
The only way out is to fo
Thanks for your support @giuliano69
With a broken heart, I ended up deciding to kiss Linux goodbye. At least for a
while.
This process of compiling and searching for solutions does not fit into my
day-to-day life.
In addition to the webcam problem, the headset microphone does not work, the
vide
I'm having the same problem with one of my systems. Same family of GPU, Tahiti.
This bug https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953249
is very similar to what is happening. However, I'm able to get all the way to
an X session, but functionality of the card is affected (can
Same problema here!
I bougth a new Acer Nitro 5, and this problem is very boring.
--
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/2000947
Title:
UVC Quanta 0408:4035 camera PROBLEM
St
I thought it was a bug in the kernel, but I just found out it is
reproducible on Windows too. Closing.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
** Description changed:
I have an Xbox One controller plugged in to the computer via USB. Every
time I resume from suspend (to RAM), the controller doesn't turn itself
- back on. Its lights are off, and it doesn't respond in any way.
+ back on. Its lights are off, and it doesn't respond in any
Public bug reported:
I have an Xbox One controller plugged in to the computer via USB. Every
time I resume from suspend (to RAM), the controller doesn't turn itself
back on. Its lights are off, and it doesn't respond in any way. It still
appears in `lsusb` output, though.
```
Bus 001 Device 007:
I can no longer reproduce. Running Xubuntu 22.10.
** Changed in: linux (Ubuntu)
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/1978133
Title:
System
** Bug watch added: Debian Bug tracker #1013211
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013211
** Also affects: linux via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013211
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1978133 ***
https://bugs.launchpad.net/bugs/1978133
** This bug has been marked a duplicate of bug 1978133
System freeze followed by kernel panic or blank screen
--
You received this bug notification because you are a member of Kernel
Packages, which is
It happens more often when the laptop is idle.
In the logs I see a pattern of messages like:
"systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
and they intensify right before the system hangs.
Secure boot is enabled, and hibernation is disabled by default. I only
use suspen
** Attachment added: "journalctl blank screen"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978133/+attachment/5595973/+files/journalctl-blank-screen.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Public bug reported:
System keeps freezing in many different circumstances. I don't know how
to reproduce this.
Only happens on Ubuntu 22.04. Earlier versions were fine - tested Ubuntu
impish and Debian bullseye.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-37-generic
It happened again, with the laptop idle same as before.
This time the screen went dark (backlight off) and the fans were
spinning fast. I could feel the laptop was a bit hot.
I had Transmission, LibreOffice Writer and GNOME Files running at the
time.
** Attachment added: "journalctl log of the s
** Description changed:
I had LibreOffice Writer open at the time, but it was idle. The system
- was completely unresponsive and a power reset was the only way to shut
- it down. The "REISUB" command didn't work.
+ became completely unresponsive and a power reset was the only way to
+ shut it do
** Attachment added: "dmesg log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+attachment/5592340/+files/dmesg.log
--
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/1975516
Public bug reported:
I had LibreOffice Writer open at the time, but it was idle. The system
was completely unresponsive and a power reset was the only way to shut
it down. The "REISUB" command didn't work.
I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible
with them.
ProblemT
I've tried to change /etc/pulse/daemon.conf (default-sample-rate =
48000) but did not work for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio fro
I have the same issue, but with another USB sound device: Yamaha Thr10x
amp (which is also an audio interface).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title
I'm now using Ubuntu 21.04 hirsute, and this bug can no longer be
reproduced :) Kernel 5.11.0-25-generic.
I've done 3 tests. No crashes so far.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.8 in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479070/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux-hwe-5.8 (Ubuntu)
Status: New => Confirmed
--
You received
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479069/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479068/+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/1917674
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479066/+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: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479062/+files/Lsusb-v.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/1917
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479065/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479056/+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/1917674
Ti
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479058/+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/19
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479059/+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/1917674
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479063/+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: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479061/+files/Lsusb-t.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/1917
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479064/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479057/+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: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1917674/+attachment/5479060/+files/Lspci-vt.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/19
apport information
** Tags added: apport-collected
** Description changed:
Automatic suspension causes the system to freeze on resume. This doesn't
happen if I suspend it manually by opening the system menu and pressing
the suspend button. Suspension works flawlessly when it is triggered
Kernel 5.6.19: OK
If I'm not mistaken, this was the last version before 5.7, so the bug
must have been introduced in 5.7.0.
--
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/1917674
Title:
I've finished the tests, here are the results:
5.0.0: OK
5.4.0: OK
5.6.0: OK
5.7.0: BUG
5.8.0: BUG
--
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/1917674
Title:
[amdgpu] kernel crash wh
Nevermind, I was running 5.8, not 5.0.0. I forgot to select 5.0.0 in the
boot menu.
--
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/1917674
Title:
[amdgpu] kernel crash when resuming from
I was able to reproduce this with kernel 5.0.0 too. Isn't it possible
that this is not caused by the kernel? I don't think I had this issue
back then - it's something more recent.
** Attachment added: "Logs from a previous session that crashed with kernel
5.0.0"
https://bugs.launchpad.net/ubu
Can report today the same issue - this happened on my Asrock x300
running popos 20.04 LTS
--
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/1908894
Title:
USB controllers disconnects after
My Notebook is a Acer Aspire E5-573G-72UF
With headset pluged or not:
sudo hdajacksensetest -a
Pin 0x05 ( Digital Out, HDMI): present = No
Pin 0x06 ( Digital Out, HDMI): present = No
Pin 0x07 ( Digital Out, HDMI): present = No
My headset is an Hyper-X Cloud Stinger.
** Attachment ad
My Notebook is a Acer Aspire E5-573G-72UF
With headset pluged or not:
sudo hdajacksensetest -a
Pin 0x05 ( Digital Out, HDMI): present = No
Pin 0x06 ( Digital Out, HDMI): present = No
Pin 0x07 ( Digital Out, HDMI): present = No
My headset is an Hyper-X Cloud Stinger.
** Attachment ad
Hello!
I have the same problem as my friend! I tried to follow the steps, but I
believe that something I did on other tests may be causing the problem.
Can anyone help me check what may be wrong?
Note: My primary system is Mint 19.3, but I just ran the test on Ubuntu 20.04
live and the latest ub
You mean I should try an older version? Then I think I should try v5.0.x
first. As you can see, it takes time to reproduce it again. I don't know
how to intentionally reproduce it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Perhaps even more problematic is that the .430 driver does not have
support for the new T4 cards, whereas .418 does.
I am not an expert on Nvidia drivers, but it is very surprising to me
that the older version of the driver has support for a new piece of
hardware where the new driver does not, but
Tested kernel 5.2-rc2. The issue is still reproducible.
To clarify it a bit more, let me explain that this happens when the
screen turns off by inactivity (screen locks) and also when you suspend
to RAM and then resume. The monitor will not turn back on when you press
any key.
I can continue pres
I can no longer reproduce this with kernel 5.1.5.
--
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/1830652
Title:
On shutdown, peripherals turn off, but fans keep spinning, power LED
is
Public bug reported:
After the screen turns off (for inactivity, screen lock, etc.), mouse or
keyboard input won't bring it back. When I come back to the computer to
resume my work, I have to wake the system up, and press the power button
on the monitor. If I don't manually bring the monitor back
** Description changed:
On shutdown, peripherals turn off (keyboard, mouse), but fans keep
spinning, motherboard LEDs are lit and screen is frozen at the Ubuntu
plymouth screen (no animations, frozen frame). The keyboard is turned
off at this point, so the only way to properly shut down th
Public bug reported:
On shutdown, peripherals turn off (keyboard, mouse), but fans keep
spinning, motherboard LEDs are lit and screen is frozen at the Ubuntu
plymouth screen (no animations, frozen frame). The keyboard is turned
off at this point, so the only way to properly shut down the computer
OK, installing old kernels seems to be beyond me at the moment, trying
to install 4.20 & 4.19 following https://seagullbird.xyz/posts/how-to-
install-an-older-kernel/ or some askubuntu results so far leaves me with
non-booting kernels. Is there a reliable beginners guide somewhere I
can follow?
-
Using Gnome 3.32.1 on Xorg, (vanilla Ubuntu).
Current kernel 5.0.0-15-generic, same behaviour in 5.0.0-13-generic
--
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/1825499
Title:
Touchpad v
Re: #7 - I'm running vanilla Ubuntu on Xorg / Gnome shell.
--
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/1825499
Title:
Touchpad vertical sensitivity is much higher than horizontal
se
HP Pavilion model G6-2264sa
--
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/1825499
Title:
Touchpad vertical sensitivity is much higher than horizontal
sensitivity [HP Pavilion g6]
Sta
Also have same symptoms following 19.04 upgrade.
--
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/1825499
Title:
Touchpad vertical sensitivity is much higher than horizontal
sensitivity
teresaejunior, could you try that:
"Can you try 4.20-rc2 and boot with kernel parameter `pcie_aspm=off`?"
I suggest first trying 4.20-rcX and seeing if it freezes at least once.
If it does, try booting for a few days with pcie_aspm=off in the kernel
parameters. Post back results.
I can't do that
** Attachment added: "output of journalctl -b -1 -k"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+attachment/5212302/+files/journal2.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
It happened again.
See the attachment of the output of journalctl -b -1 -k
This time I was just editing the position of widgets on the xfce4-panel.
I think it was around 11:45 on the clock.
And I do not have a .cache/thumbnails/fail folder.
** Also affects: linux (Arch Linux)
Importance: Unde
I have updated to A16 and so far no freezes, although it's still not
uncommon for these to stop happening for a while and then return.
--
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/1798961
The problem is, it could take days before the system freezes. I don't
know how to reproduce, it simply happens. I don't even know where to
start. Maybe 4.17-rc1 and so on. But that's a huge task and one needs a
lot of patience to do it. I'm not sure I'll be able to.
--
You received this bug notif
** Description changed:
First thing I notice is that the mouse cursor freezes as I'm using it,
then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then
I try the "REISUB" command, but it doesn't do anything either. Only a
hard reset works, pressing down the power button for
Affects the latest mainline build 4.19-rc8 as well.
Still cannot identify one way to reproduce it intentionally, although
most of the time it happens when I have a video playing and/or multiple
images being displayed with the image viewer.
** Changed in: linux (Ubuntu)
Status: Incomplete =
I am failing to boot from this new kernel. Downloaded the amd64 build
files, 'sudo dpkg -i ' on each of them, but upon trying to boot
from the new entries, it stops with "you need to load the kernel first".
I really need some help figuring out my mistake here. I did my homework
but no solutions yet
This is the bug report opened for Arch Linux [TASK FS#59483]:
https://bugs.archlinux.org/task/59483?string=freeze&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&cha
Public bug reported:
First thing I notice is that the mouse cursor freezes as I'm using it,
then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then
I try the "REISUB" command, but it doesn't do anything either. Only a
hard reset works, pressing down the power button for a few seco
I can verify from IBM's standpoint, that we were able to use Volta gpu's
with POWER9. The Nvidia driver enabled correctly.
--
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/1772991
Title:
Tested kernel 4.13.4-200.fc26.x86_64, and is still reproducible. Arch is
free from this bug, but Fedora and Debian are not.
** Tags removed: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Tested kernel 4.13 in Arch Linux. Cannot reproduce the bug with it.
Fedora is in 4.12.14-300.fc26 and is still reproducible there.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Sorry, can you tell me how to install the 4.13 kernel in Debian? It's
useless to do it in Ubuntu. As I said, Ubuntu is not affected. I might
have reported in the wrong place.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Fedora's kernel version: 4.12.13-300.fc26.x86_64
Debian's kernel version: 4.9.0-3-amd64
Both are affected. Ubuntu LTS is not, though. I don't remember 17.04.
I can install the mainline 4.13 kernel for Fedora. If Ubuntu is really
needed, I don't mind installing it here.
--
You received this bug
Public bug reported:
Symptoms:
The computer begins its boot process, then the root decryption password
prompt appears (via Plymouth) and I start typing. The first letters are
caught, but some letters are not captured. It's as if the keyboard shut
down during a few seconds and then returned, and I
vice
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: douglas1966 F pulseaudio
lightdm 22384 F pulseaudio
Date: Wed
ector talpa_pedevice
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: douglas1966 F pulseaudio
lightdm 22384 F pulseaudi
vice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: douglas1966 F pulseaudio
lightdm 22384 F pulseaudio
Date: Wed Aug
/controlC0: douglas1966 F pulseaudio
lightdm 22384 F pulseaudio
Date: Wed Aug 9 08:10:00 2017
DuplicateSignature:
package:linux-image-4.4.0-89-generic:(not installed)
Unpacking linux-image-4.4.0-89-generic (4.4.0-89.112) ...
dpkg: error processing arc
talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: douglas1966 F pulseaudio
lightdm 22384 F pulseaudio
Date: Wed Aug 9 08:10:00 2017
DuplicateSignature
happened at any cause.
With regards,
Naveed
- Forwarded by Naveed Us Ahmed/India/IBM on 03/30/2016 11:10 AM -
> From: Douglas Miller1/Rochester/IBM
> To: Naveed Us Ahmed/India/IBM
> Date: 03/29/2016 07:46 AM
> Subject: Re: dkms driver
>
> It would app
Public bug reported:
The system keep show me this problem everytime i try to update the
System.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-22-generic 4.10.0-22.24
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
Appo
I fixed it with `sudo systemctl enable bluetooth` followed by a reboot.
It will print something to the terminal when you enable. Something else
must have disabled bluetooth.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Carsten, I am currently thinking there are two possibilities here.
Maybe three.
1) The fix I submitted is not in the kernel(s) you are running.
2) The s390 compiler does not produce the necessary code to implicitly convert
long int to bool.
3) You are hitting a different bug that just happens to
I'm confused about the release mechanics, I guess. Looking at the git
repository, I see tag "Ubuntu-4.4.0-65.86" (for example) and that tag
commit does contain the fix. Is it then possible for a kernel labeled
"4.4.0-65-generic #86" to NOT contain that patch? Am I making a gross
assumption that the
This looks a lot like the problem in LP #1662673, but that fix is
supposed to be in kernel 4.4.0-65-generic. Might be worth confirming
though. Or perhaps confirming that the fix actually works on the Z
architecture (depends on how the architecture/compiler handles 'bool').
--
You received this bu
Christopher,
That's a tougher question than you might think. :)
The full system is a rack-scale product developed by Dell's Data Center
Solutions division called DSS9000. This is not a generally-available
system, but is produced only for hyperscale and other large-volume
clients. However, the moth
I'm seeing my logs spammed with "dell_laptop: Keyboard brightness level
control not supported" too. Have you reported the bug upstream already?
--
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
I have modified the description and status to Incomplete, as I cannot
provide an adequate test (that doesn't contain proprietary code) to
reproduce the issue at this time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
Unfortunately, I was able to reproduce my segfault with a kernel version
before the parent's bug was introduced. This implies my issue lies
somewhere else. I'm pretty sure its something to do with threading in
the kernel, but the referenced issue is not this one.
** Changed in: linux (Ubuntu)
Chris: My test case unfortunately depends on an internal application
that I am not able to share the code of. At the moment, I am building an
older kernel version to test whether the test works properly on it. I
will respond once I've determined that the bug I referenced is indeed
the same one i'm
Public bug reported:
This bug appears to be due to a regression of the fix for:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450584
Specifically, the edit history for
https://github.com/torvalds/linux/commits/master/arch/x86/kernel/pvclock.c
(one of the files that the parent mentioned ne
Specifically, the edit history for
https://github.com/torvalds/linux/commits/master/arch/x86/kernel/pvclock.c
(one of the files that the parent mentioned needed patching for the fix)
shows that the changes added for the fix were removed one month later.
--
You received this bug notification becau
I believe that this issue has reappeared in 3.13.0-62-generic, i'm
getting an extremely similar problem on that kernel version.
--
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/1450584
Title
> I'll try to find out what my VM actually is, beyond "openstack".
KVM 2.0.0+dfsg-2ubuntu1.11
The processor (per attached files above) is "Intel Xeon E312xx (Sandy
Bridge)".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
hi Colin,
I first met on a 3.19.0-20 build:
Linux samba-build-i386-32bit 3.19.0-20-generic #20-Ubuntu SMP Fri May 29
10:06:53 UTC 2015 i686 i686 i686 GNU/Linux
and as far as I can tell (taking into account Joseph's 3.16 and upstream
4.2rc3), that a87938b/b51621a commit is neither the cure or cul
Thanks Joseph!
It's no better with 3.16.0-44-generic #59~lp1471029. Perhaps even slightly
worse -- in my sample of 2 I've seen the heap at b8d- and b94-, while I think
stock Vivid 3.19 was most often in the b7's.
$ uname -a
Linux samba-build-i386-4-32bit 3.16.0-44-generic #59~lp1471029 SMP Wed
1 - 100 of 117 matches
Mail list logo
