Public bug reported:
irdma Kernel module will use > 5GB as soon as is loaded. This bug is
present from kernel 5.14.
# free -m
total used free shared buff/cache available
Mem: 15663 5998 8936 155 728 9213
Swap: 0 0 0
Using ps the sum of RSS memory does not adds up: it shows less th
Can I provide something else to help the triage of this 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/1990292
Title:
Mistery memory usage in linux Kernel >= 5.14
Status in linux p
By removing kernel modules one by one I identified the culprit in
"irdma". By removing this module 5.2GiB of RAM is freed
This is the output of "free" without the irdma Kernel module:
free -h
totalusedfree shared buff/cache available
Mem: 15Gi
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1990292/+attachment/5617630/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, whic
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1990292/+attachment/5617629/+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/1990292/+attachment/5617628/+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/1990292
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1990292/+attachment/5617627/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1990292/+attachment/5617626/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1990292/+attachment/5617625/+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: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1990292/+attachment/5617623/+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/1990
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1990292/+attachment/5617622/+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/1990292
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1990292/+attachment/5617624/+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/1990
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1990292/+attachment/5617621/+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 jammy
** Description changed:
My hardware is SuperMicro X11SDV-8C-TP8F with Intel D-2146NT.
I've tested this issue with:
* Ubuntu 22.04 Kernel 5.15
* Ubuntu 22.04 Kernel 5.17
* Ubuntu 20.04 Kernel 5.15
* Ubuntu 20.04 Kernel 5.14
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1990292/+attachment/5617620/+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/1990292
I'm getting the same bug even on Intel(R) Xeon(R) CPU E5-2620 v2 @
2.10GHz, I'm starting to think it's not CPU related.
Am I the only one affected? Are there any logs which can help triage
this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
I've tested (accidentaly) on 4 different servers. Three of them have the
same CPU of the bug report. The fourth one has the cpu attached to this
comment.
** Attachment added: "cpuinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966498/+attachment/5572956/+files/c
Public bug reported:
When updated to kernel 5.13.0-37-generic we get this error and the
server became unresponsive.
I've updated four different servers and all have the same problem. On
kernel 5.13.0-35-generic everything is fine
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-
** Tags added: kernel-bug suspend-resume
--
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/1931105
Title:
Sleep issue on ubuntu 21.04, CPU AMD 5700u
Status in linux package in Ubuntu:
Ne
** Changed in: linux-firmware (Ubuntu)
Status: Triaged => In Progress
--
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/1888647
Title:
Realtek wifi dont work after update
sky2.disable_msi=1 solves my 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/1841304
Title:
sky2 ethernet card don't work after returning from suspension
Status in linux package in
System:
Kernel: 5.8.0-48-generic x86_64 bits: 64 compiler: N/A
Desktop: Gnome 3.36.4 Distro: Ubuntu 20.04.2 LTS (Focal Fossa)
Machine:
Type: Desktop System: Acer product: Aspire E380 v: R01-B4 serial:
Mobo: Acer model: EM61SM/EM61PM serial: BIOS: Phoenix v: R01-B4
date: 12/29/2006
I am experiencing the same issue with an old Acer T180. My kernel version is
5.8.0-48-generic.
My Ethernet card is a Marvell 88E8056. Let me know if you need further
information, I would be willing to help you.
--
You received this bug notification because you are a member of Kernel
Packages, w
I have not had any problem with Nouveau and Wayland so far.
--
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/1901563
Title:
[i915] Kernel crashed in vma_create when running Xorg
Status in
I have successfully switched to Nouveau and Wayland. I have not had any
problem so far (it's been 30 minutes since I switched - maybe it's too
soon to tell). I will test my current setup and report back in a week.
--
You received this bug notification because you are a member of Kernel
Packages,
I am experiencing the same issue. I am using a very old machine: it's an Acer
T180 with a NVIDIA GT710 graphics card (driver nvidia-460) and an AMD Athlon
5600+.
The process causing the crash is /usr/lib/gdm3/gdm-x-session.
I will try to switch to Nouveau and Wayland and report back.
--
You rec
staying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compile
it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7
Distro: Linux Mint 20 Ulyana base:
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
nsion.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
without
staying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits:
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
nsion.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
nsion.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
nsion.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
without
staying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits:
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
spension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v:
taying in suspension.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compil
on.
It's as if an interrupt of some kind or the EC were waking it up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
up immediately
after it entered suspension!
I have 2 identical laptops: same problem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7
Distro: Linux Mint 20 Ulyana base: Ubu
lem.
Thank you,
Federico Tejada
Info:
$ inxi -Fxz
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7
Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal
Machine: Type: Laptop System: TOSHIBA product: Satellite-L845 v:
PSKF6
I have the same machine (Dell XPS 13 9300), came preloaded with Ubuntu
18, then upgraded to 20.04. Running Kernel 5.4.0-48-generic #52.
I have the same problem, only that nothing really helps apart from
restarting until it randomly works ...
--
You received this bug notification because you are
Public bug reported:
Hello!
The webcam of my dell xps isn't been recognized by Linux. I search a lot
on the internet and found that many people is experiencing this. For
example, in the ubuntu page they say regarding the camera:
"Intel Icelake integrated the IPU 4th Generation Gen IPU with on-di
Public bug reported:
Hello!
The touchpad of my "Bangho G05 Zero" laptop is recognized by "xinput
list" as a "ImPS/2 Generic Wheel Mouse".
I been try everything these days, but I do anything about it :(. I had
come to the conclusion that probably is a kernel bug, it shouldn't
recognize it at leas
You-Cheng, i also tried removing pci=nocrs and rebooting and it did not
work either.
I would like to try
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1881322, should I
delete all the grub parameters that i added?
To add further information:
- With the parameters I currently have, and with M
It worked! I added a few parameters to grub before but the did not
worked.
For future reference to others:
- Access the grub configuration file by typing in a terminal: sudo nano
/etc/default/grub
- Find the line "GRUB_CMDLINE_LINUX_DEFAULT" and append i8042.nopnp=1 pci=nocrs
- Save the file and
It worked! I added a few parameters to grub before but the did not
worked.
For future reference to others:
- Access the grub configuration file by typing in a terminal: sudo nano
/etc/default/grub
- Find the line "GRUB_CMDLINE_LINUX_DEFAULT" and append i8042.nopnp=1 pci=nocrs
- Save the file and
Public bug reported:
quiero actualizar al ultimo paquete Ubuntu 20
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.7
Ar
Same here, UX433FN.
Linux asus-ux433fn 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22
03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
--
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/18
Filipe,
as far as I can see you're having issue with usbhid module, not with i8042. But
since you get a very similar issue could be very related to my issue. Good luck!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
I've created a script for lightDM to check the state of the keyboard with
xinput: it starts when X is loaded (tested with display-setup-script and
greeter-setup-script options) and check the state of the internal keyboard then
create a txt in my home.
The keyboard is correctly identified from t
** Tags removed: kernel-bug-exists-mainline-4.11rc1
** Tags added: kernel-bug-exists-mainline-4.12.3
--
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/1599306
Title:
[HP Pavilion dv2910us E
Finally I got the time to test (with a second SSD just to be sure) this
notebook with some quirks.
So far, the quirks I've found and tested are:
i8042.kbdreset
i8042.reset
i8042.nomux
i8042.dumbkbd
i8042.direct
i8042.noaux (irrelevant but tested anyway)
i8042.nokbd (completely kill the keyboard)
I have the same problemi with dell XPS 13 9360.
Here the wifi info
(https://github.com/UbuntuForums/wireless-info/raw/master/wireless-info)
results, hope they are useful: http://paste.ubuntu.com/24848753/
--
You received this bug notification because you are a member of Kernel
Packages, which i
** Tags added: kernel-bug-exists-mainline-4.11rc7 kernel-bug-exists-
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/1637347
Title:
Xubuntu 16.10: drm errors causing slow boot
S
It's not restricted to Xubuntu, but this bug affects all *buntu I've
tested in the last week. Now I'm testing Ubuntu Budgie on a notebook HP
2910us and kernel 4.10.0-19-generic.
** Tags added: zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Yes, the same test is currently passing on rev 55 (edge) [1], the
/dev/ramX files are there after booting [2], and starting with rev 59
that files are missing and the tests fail [3].
[1] https://travis-ci.org/snapcore/spread-cron/builds/216734158
[2] http://paste.ubuntu.com/24306876/
[3] https://t
The oroblem happens on an amd64 ubuntu-core system, no apport-collect in
there, please let me know how can I get the required logs on that
system.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Package
Public bug reported:
While running the snapd suite using the amd64 kernel snap from the beta
channel (rev 59) we got this error running [1]:
2017-03-30 09:36:41 Error preparing
linode:ubuntu-core-16-64:tests/main/snap-auto-mount :
-
[ ... ]
Create a ramdisk with the testrootorg-store.accoun
i8042.kbdreset=1, i8042.reset and i8042.nomux=1 with no luck.
I don't remember if I've tested atkbd, but I can give a new spin of boot
options tomorrow just to be sure.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Yes, the touchpad works just fine (see videos on OP).
--
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/1599306
Title:
[HP Pavilion dv2910us Entertainment Notebook PC] i8042 need to start
Tested (even with broken wifi drivers)
4.11.0-041100rc1-generic #201703051731 SMP Sun Mar 5 22:34:02 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
Issue still present.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-mainline-4.11rc1
--
You recei
Christopher, sorry for the delay but I completely missed your last
messages.
My bios is the latest version:
F.2D 08/26/2008
And the issue is still present with any *buntu I've tried.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Tags removed: bios-outdated-f.2d
** Tags a
Ok, now I test the upstream kernel from here http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.10-rc5/
kernel tested is:
4.10.0-041000rc5-generic
Now with this kernel, going to standby using suspend button in the GUI,
and resuming from standby using the power button, the bug is still NOT
present,
No, this is a new computer and this is a fresh install. I'm really sorry but at
this time I'm unable to try the latest upstream kernel.
But I confirm that this issue is also present in these kernels (they are the
latest kernels present in the official Mint Update Manager):
4.8.0-30
4.8.0-32
4.8.0
Happened after upgrade to 16.04.1, works with kernel 4.4.0-21-generic
works with kernel 4.9.0-040900-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/1654374
Title:
Touchpad and to
** Attachment removed: "dmesg-none.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791714/+files/dmesg-none.txt
** Attachment removed: "dmesg-core.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791713/+files/dmesg-core.txt
**
** Attachment added: "dmesg-none.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791714/+files/dmesg-none.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/bu
** Attachment added: "dmesg-processors.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791712/+files/dmesg-processors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Attachment added: "dmesg-core.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791713/+files/dmesg-core.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/bu
** Attachment added: "dmesg-core.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791718/+files/dmesg-core.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/bu
** Attachment added: "dmesg-freezer.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791709/+files/dmesg-freezer.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
--
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/1649945
Title:
HP 470g3 - not resume from standby
Status in linux package in Ubuntu:
Confirmed
Bug description:
When the power button
** Attachment added: "wakeup.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649945/+attachment/4791708/+files/wakeup.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/16499
1 - 100 of 167 matches
Mail list logo
