Public bug reported:
[GFX1-]: vaapitest: ERROR
[GFX1-]: vaapitest: VA-API test failed: failed to open renderDeviceFD.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ProblemType: Bug
DistroRel
Public bug reported:
touchpad showed as device in windows 10 but in fresh install of ubuntu
the touchpad does not show up at all. does not show in xinput or
devices.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1
ProcVersionSignature: Ubu
It seems like my problem may have been a different underlying cause with
similar symptoms.
In my case, the entry in /etc/crypttab didn't match the location of the
encrypted partition. Partition is on sda3, but /etc/crypttab read:
sda6_crypt UUID={uuid} none luks,discard
It appears that when the
(Correction: previously it asked to decrypt sda3_crypt, not /dev/sda3.)
--
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/1986623
Title:
cryptsetup fails to decrypt root partion during boot
Success?
Based only on the error message, I tried defining tmpData in
/etc/crypttab. Previously, the file consisted of one line:
sda6_crypt UUID={uuid} none luks,discard
I added a second line:
tmpData UUID={uuid} none luks,discard
and re-ran update-initramfs. It still produced the other mess
I'm getting a bit over my head, but it is seeming like there's a problem
with creating a new initrd.
When I decrypt (using unmkinitramfs) the initrd.img file, I see that the
"good" version has a /main/cryptroot/crypttab file which appears
identical to /etc/crypttab. The "bad" version has an empty
Correction: It is not the kernel itself I was talking about, above.
It's the initrd.img file associated with the kernel.
Note also that replacing that file with the old version eliminates the
problem (at least until some update changes it again).
--
You received this bug notification because you
I am able to reproduce the error when I install the new 5.19.0-32
kernel.
Also, when I install the package "Firmware for Linux kernel drivers," it
modifies the files for the older kernels (5.15.0-60 and 5.15.0-43),
making them have the same problem. The 5.15.0-60 file goes from
111,616,247 bytes
Fresh install worked until I did today's recommended updates, then the
problem recurred. Not sure exactly what was updated; I thought
/var/log/dpkg.log was supposed to be human-readable, but mine isn't.
--
You received this bug notification because you are a member of Kernel
Packages, which is s
I have an Intel Core i5-4590.
Also just tried a fresh install (Ubuntu 22.04) on a spare hard drive,
and it boots fine using kernel 5.15.0-60-generic. Note that spare is a
traditional hard drive and main drive is an SSD; next I'll try
reinstalling on the SSD.
--
You received this bug notificatio
I am still experiencing this issue:
$ uname -a
Linux dev 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64
x86_64 x86_64 GNU/Linux
$ lspci -k | grep Network
04:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev ff)
$ md5sum /lib/firmware/iwlwifi-9260-th-b0-jf-b
I've tested on the test kernel, and it's working perfectly - Thanks!
# uname -a
Linux GAU23LD12 5.13.0-47-generic #52~20.04.1+lp1967493 SMP Mon Jun 6
06:43:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is
A patch for this has been merged into Linus's tree and it has been back
ported to the LTS kernels.
https://github.com/torvalds/linux/commit/e82e7c6dde91acd6748d672a44dc1980ce239f86
Please can this patch be included into the Ubuntu kernels.
--
You received this bug notification because you are
> If the issue still exist, please report this issue to linux-
u...@vger.kernel.org, indicating the kernel version and attach the lsusb
-v output for this device.
Done: https://lore.kernel.org/linux-
usb/cajixrzqf4a9-zkzdgwxicc_bpfdzve9qqgmkio7xestoxub...@mail.gmail.com/T/#u
--
You received this
Hi @cypressyew. Sorry to take so long to get back to you.
> Maybe your PL2303 is using another chip,
> can you please upload the dmesg output with this device attached?
> Also the output of the following command with it connected:
>
> lsusb -v
I've attached a file with the output.
> And in case
/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
InstallationDate
Public bug reported:
Hi
After upgrading the Linux kernel from 5.11.0-27 to 5.13.0-37 a device
that uses a pl2303 usb serial chip no longer works.
This seems very similar to bug 1959110, and according to that it should
be fixed, but somehow it's not.
# uname -a
Linux GAU23LD04 5.13.0-37-gene
*** This bug is a duplicate of bug 1959110 ***
https://bugs.launchpad.net/bugs/1959110
** This bug has been marked a duplicate of bug 1959110
pl2303 serial adapter no longer recognized
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
vicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUI
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: R
chitecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ub
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: R
vicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUI
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: R
vicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUI
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevi
vicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=4cc
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
Hiberna
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gary 12435 F pulseaudio
/dev/snd/controlC2: gary 12435 F pulseaudio
/dev/snd/controlC0: gary 12435 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: R
with the GPU would go away!
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.27
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: gary 12435 F pulseaudio
+ /dev/snd/controlC2: gary 12435 F pulseaudio
+ /dev/snd/controlC0
Public bug reported:
Tracker says mesa-vulkan-drivers is not in Ubuntu!?
mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed]
Ubuntu 18.04.6 LTS
AMD Ryzen 7 2700x eight-core processor x 16
AMD Radeon rx 5700 xt
apt-cache show says that vulkan-mesa-drivers provides vul
Similar to or possibly the same as
https://gitlab.freedesktop.org/drm/intel/-/issues/4150
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4150
https://gitlab.freedesktop.org/drm/intel/-/issues/4150
--
You received this bug notification because you are a member of Kernel
Package
Ok, so I went back and re-read some of the most recent comments here -
especially #226 and #229.
This is what works for me:
$ alias vmware="xmodmap -e 'remove control = Caps_Lock ' &&
/usr/lib/vmware/bin/vmplayer"
If I start vmware with this alias, the keyboard on the host does not get
corrupt
Ok I see this issue is closed as its quite old. Is this particular
issue tracked somewhere else?
I just upgraded my Ubuntu 16.04 system to Ubuntu 18.04.5 and this issue
still exists for me.
what I'd like to be able to do is:
1. configure my keyboard on the host laptop to map "Caps Lock as an ext
Public bug reported:
SoI need instructions on what to do now. Any chance?
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-headers-4.4.0-150-generic 4.4.0-150.176
ProcVersionSignature: Ubuntu 4.4.0-197.229-generic 4.4.241
Uname: Linux 4.4.0-197-generic x86_64
ApportVersion: 2.20.1
Sorry, more info... looking at kern.log, the context is as follows. Note
that this occurred when the machine had auto-suspended with the laptop
open, and the black screen with text was already visible when I came
into the room. It did not suddenly appear as a result of my triggering a
return from s
Following up, I have made the following changes to my system recently.
Two occurred within the week prior to this problem appearing, but not
immediately before to my knowledge, so it's not certain that any of them
are applicable. They are listed in order of first use.
- Added a 4K monitor on HDMI
This problem just appeared on my Spectre x360 for the first time
yesterday. When laptop auto-suspends form lack of activity, the screen
goes black with three messages with this error. It is unresponsive so
only solution is power off and reboot by pressing and holding the power
button to shut down,
Public bug reported:
fresh install of ubuntu 20.04 touch screen works but touchpad not working at all
make is acer
model V3-112P
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-31-generic 5.4.0-31.35
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4
I fixed it by adding a few lines in my /etc/default/grub file! (not sure which
exactly which one of the 3 fixed it)
In the line (GRUB_CMDLINE_LINUX_DEFAULT=) I added to the quotes: iommu=soft
processor.max_cstate=5 idle=nomwait
If anyone can explain what they each do/which ones are necessary that
I started to experience this same issue with Ubuntu 16.04. I performed an apt
upgrade and after rebooting I did not have any sound from my HDMI port.
I did some research and I think I figured out why my Ubuntu 16.04 machine would
not output audio on an HDMI port. I believe this is the same iss
Tested bionic-proposed with both original VM that exhibited the problem
on upgrade and a separate VM used to test the work-around (uncommenting
WaylandEnable=false in /etc/gdm3/custom.conf).
Both VMs upgraded and ran successfully using
https://wiki.ubuntu.com/Testing/EnableProposed.
-
Additional confirmation...
Working under VMware Workstation v12.5.7 running kernel 4.15.0.52:
Having performed the workaround of uncommenting the
WaylandEnable=false...
- Re-commented the line & rebooted to experience the hang with the
Ubuntu logo before the login screen
- Using your ppa,
By the way, I connected back up the sound on my machine before that most
recent crash. So, it is not the cause (for anyone who may have
considered that possibility).
Also, you will find this possibly relevant thread regarding
smp_call_function_ (single or many):
https://lkml.org/lkml/2016/1/30/2
at 8:35:51 am.
I restarted it at 9:14:04 am.
It crashed again.
I checked /var/crash, and it had the following (I've inserted the file
contents below listed files):
[ gary@Quasar | Tue 02 A
It hung again yesterday (S 23 Mar 2019). It used to hang multiple times
daily.
Anyhow, the laptop was unresponsive. The disk activity light continued
as normal, though.
However, it did allow me to SSH into it, but hung completely when I
tried to open gnome-control-center. That suggests that th
Err, the issue sounds a lot like Bug #1743094. Maybe one should be
marked as a duplicate of the 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/1757445
Title:
Suspend does not alw
This issue sounds a lot like Bug #1757445. Maybe one should be marked
as a duplicate of the 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/1757445
Title:
Suspend does not always
I forgot to mention that before demonstrating that "Night Light" and
"Dim screen when inactive", I upgraded to the latest BIOS from Lenovo on
20 March (a day prior to posting #16 and before turning off the dimming
features). It is the Lenovo 85UJ25US (1.46) BIOS, which is an upgrade
from 8BET55WW
By the way, this issue appeared on my machine, which is a Lenovo W520.
I have turned off automatic suspend while plugged in. I need it to run
financial calculations overnight. And, I have increased the battery
power delay to 30m. Though that is neither here nor there.
With "Night Light" and "D
I've found that I can make the system stable with the following
settings:
System Settings:
Privacy>Screen Lock:On
Power>Dim screen when inactive: Off
Power>Blank screen: 10m
Power>Automatic suspend
Yes, this worked, thank you. OFB communication also still works as
documented in comment #9
--
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/1787898
Title:
[18.10 FEAT] Add kernel config o
Our product includes a linux module. In order to build with lp1787898 I
had to modify linux-headers-4.15.0-34-generic (exportroot tree) to copy
(older) s390x built tools in place of the incorrect x86 versions in
linux-headers-4.15.0-34-generic_4.15.0-34.37~lp1787898_s390x.deb:
scripts/sign-file
sc
http://kernel.ubuntu.com/~ksouza/lp1787898/linux-
headers-4.15.0-34-generic_4.15.0-34.37~lp1787898_s390x.deb
does not contain s390 builds of tools:
$ arch
s390x
$ usr/src/linux-headers-4.15.0-34-generic/scripts/basic/fixdep
warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
Public bug reported:
it just crashed
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-kvm-tools-4.15.0-1008 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_gen
So if this is the solution, how long before it gets into the standard
update to folks?
Thanks in advance,
Gary
--
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/1752772
Title:
r8169
If you don't see specific messages like:
HcDoneHead not written back; disabled
HC died; cleaning up
Then it's unlikely to be the same bug. This one has been fixed anyway.
If you have a particular USB device that disconnects, it's likely to be
either a hardware problem (check it on a different O
Here's a new bug: There doesn't seem to be a way to mark comments as
spam.
--
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/344878
Title:
file name too long when creating new file (ecryptf
@baltic (bugsgenerator) You're right, but the powers that be have for
years refused to see the distinction between changing the way filenames
are handled (which they have, I think, adequately explained the
technical reasons for not doing) and providing adequate documentation
and error handling (whi
** Changed in: linux (Ubuntu)
Status: Expired => 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/1514821
Title:
SD card reader on Dell E7250 doesn't work in Ubuntu 15.10
I also had this problem, and found a different fix in 4.9 that fixed it
(my original bug #1641052):
commit a8006bd915095c40098bfcb684cc2bdfb414dc0d
Merge: 965c4b7 6bad6bc
Author: Linus Torvalds
Date: Fri Oct 28 11:26:01 2016 -0700
Merge branch 'timers-urgent-for-linus' of
git://git.kernel.or
Public bug reported:
Dropping wifi when coming out of suspend
** Affects: linux (Ubuntu)
Importance: Undecided
Status: 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/163
Is it not complete now?
** 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/1636625
Title:
Syntax error extra parenthesis linux
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1636625/+attachment/4767523/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1636625/+attachment/4767521/+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: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1636625/+attachment/4767517/+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: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1636625/+attachment/4767525/+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/1636
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1636625/+attachment/4767518/+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.txt"
https://bugs.launchpad.net/bugs/1636625/+attachment/4767519/+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/1636625
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1636625/+attachment/4767522/+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/1636625/+attachment/4767520/+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/1636625
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1636625/+attachment/4767524/+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/1636625
apport information
** Tags added: apport-collected
** Description changed:
Recommended change: remove incorrect extra ) character
root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile
615c615
< -fstack-protector not supported by compiler)
---
>
Kernel (and kernel headers) linux-headers-3.13.0-100-generic was released
in response to CVE 2016-5195
It is then unfortunate that customers upgrading urgently to kernel
3.13.0-100-generic in Ubuntu 14.04.1 LTS can not rebuild some customer-
specific drivers because of the syntax error in this Ma
The warning statement parenthesis is not balanced
ifdef CONFIG_CC_STACKPROTECTOR_REGULAR
stackp-flag := -fstack-protector
ifeq ($(call cc-option, $(stackp-flag)),)
$(warning Cannot use CONFIG_CC_STACKPROTECTOR: \
-fstack-protector not supported by compiler))
endif
else ifd
Public bug reported:
Recommended change: remove incorrect extra ) character
root@nereid:/usr/src/linux-headers-3.13.0-100# diff Makefile old2.Makefile
615c615
< -fstack-protector not supported by compiler)
---
> -fstack-protector not supported by compiler))
This bug cause
I apologize, I should have included that to begin with.
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.1 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.1 LTS"
VERSION_ID="16.04"
$ uname -a
Linux localhost 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
x
I'd also like to add to the above comment that I'm using WPA2 for the
wireless encryption.
--
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/1520343
Title:
Qualcomm Atheros wireles
OK -- I have no clue what my issue could be and am starting to get a bit
frustrated with this WiFi chip because it seems like there's nothing I
can do about it. I'm using the Ath10k QCA6174 chipset on a Acer Aspire V
Nitro laptop. Every other device I have connects at a much faster rate
to my Asus
** Package changed: kernel-package (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/1606786
Title:
in Ubuntu16.10: Hit on Call traces and system goes down when
** Package changed: 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/1584828
Title:
s390/pci: fix use after free in dma_init
Status in linux package in Ubuntu:
** Package changed: 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/1584827
Title:
s390/mm: fix asce_bits handling with dynamic pagetable levels
Status in linux
** Package changed: ubuntu => makedumpfile (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1564475
Title:
128M is not enough for kdump on s390 LPARs
Status in makedumpfil
** Package changed: 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/1562004
Title:
S390: glibc does not use direct socket-syscalls, but the multiplexer-
socket-
FYI -- the author forgot to mention that these files need to be marked
executable...
sudo chmod +x /lib/firmware/ath10k/QCA6174/hw3.0/*.bin
--
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/1
** Package changed: 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/1556141
Title:
s390/mm: four page table levels vs. fork
Status in linux package in Ubuntu:
#7 - Gary M. Gaydos - 2016-03-08 14:45:49 ==
From /var/log/kern.log
Mar 7 15:27:36 s83lp62 kernel: [0.340487] Linux version
4.4.0-10-generic (buildd@z13-027) (gcc version 5.3.1 20160225 (Ubuntu
5.3.1-10ubuntu2) ) #25-Ubuntu SMP Wed Mar 2 14:56:49 UTC 2016 (Ubuntu
4.4.0-10.25-generic 4.
** Package changed: 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/1548414
Title:
Floating-point exception handler receives empty Data-Exception Code in
Floati
** Package changed: 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/1543165
Title:
kernel: update kernel configuration
Status in linux package in Ubuntu:
New
** Package changed: 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/1539642
Title:
Integrate zfcp HBA API library 2.1.1
Status in linux package in Ubuntu:
New
** Package changed: ubuntu => linux-lts-utopic (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1533351
Title:
DLPAR operation fails on Bell adapter with Ubuntu 14.04.3
While it's wonderful that a patch has been created, could someone out
there PLEASE wrap it up in a nice and simple .DEB package so the rest of
us idiots can install it without having to manually recompile the
kernel?
After all, most of us *buntu users are simpletons who can't work a BASH
shell if
** Package changed: 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/1522071
Title:
EEH recovery fails for shinner T on firestone
Status in linux package in Ubunt
** Package changed: 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/1517942
Title:
Backport upstream commit to Ubuntu 15.10 (Wily) SRU stream
Status in linux pac
This is seriously disheartening ...
Bug #1189721 reported by Graeme Pietersz on 2013-06-11
That was 2 years and 5 months ago!!
No disrespect to Alexandre but his report of a working solution seems to
be a bit shaky in that we don't have any specifics of the circumstances
under which it is operati
-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gary 1329 F pulseaudio
CurrentDesktop: Unity
Date: Fri Nov 6 12:29:09 2015
HibernationDevice: RESUME=UUID=24230065-3837-4659-ac98-167ff163207f
InstallationDate: Installed on
-generic 4.2.0-16.19 [modified:
boot/vmlinuz-4.2.0-16-generic]
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gary
ric x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gary 1329 F pulseaudio
CurrentDesktop: Unity
Date: Fri Nov 6 12:29:09 2015
HibernationDevice: RESUME=UUID=24230065-3837-4659-ac98-167ff163207f
Instal
-generic 4.2.0-16.19 [modified:
boot/vmlinuz-4.2.0-16-generic]
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gary
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gary 1329 F pulseaudio
CurrentDesktop: Unity
Date: Fri Nov 6 12:29:09 2015
HibernationDevice: RESUME=UUID=24230065
1 - 100 of 145 matches
Mail list logo
