.
[73792.544263] mmc0: Timeout waiting for hardware interrupt.
Using a Lexar 16 GB SDHC.
Regards,
Nils
--
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/1327764
Title:
[Acer Aspire V5-131] Broadcom
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631753/+attachment/4758123/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631753/+attachment/4758124/+files/dmesg
--
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/1631753
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631753/+attachment/4758125/+files/Xorg.0.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "devices"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631753/+attachment/4758126/+files/devices
** Description changed:
- After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped working
(meaning it even worked for some hours put then stopped). Now
Public bug reported:
After upgrade from kubuntu 14.04 to 16.04 the touchpad soon stopped
working (meaning it even worked for some hours put then stopped). Now it
is not detected anymore. It isn't listed when typing cat
/proc/bus/input/devices.
sudo apt-get install xserver-xorg-input-synaptics +
Thanks for the assistance!
I tested kernel v4.8.0-040800-generic and it didn't fix the bug.
Regarding tags assigned.
Further two things for info (nothing new, just for the sake of completeness):
- I've a dualboot and the touchpad works on windows.
- System Settings -> Input Devices -> Touchpad
With nvme_core.default_ps_max_latency_us=2000 the problem persists.
However, everything seems fine with nvme_core.default_ps_max_latency_us=0.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm having the exact same problem (drive dying with filesystem read
errors and system becoming unusable after using it for a while)
However, my nvme SSD is not from Samsung, but from Toshiba:
nvme list
Node SN Model
Namespace
No, it's a Lenovo ThinkPad X270. Do you need any other information?
--
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/1678184
Title:
APST quirk needed for Samsung 512GB NVMe drive
Status
I have to admit that I'm not sure how or where to set 'nvme-
core.nvme_core.default_ps_max_latency_us=2000'.
I assumed that it's a kernel boot parameter that I can add in grub? But
when I do nothing changes and "sysctl -a", which I assumed should list
the changed parameter does not show anything
Thanks Chris.
I have tried 'nvme-core.nvme_core.default_ps_max_latency_us=2000' (though I
have been unable to verify that the parameter actually changed) and the problem
persisted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Hm, ok I seem to be unable to disable APST. :(
In '/etc/default/grub', I have
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme-
core.nvme_core.default_ps_max_latency_us=0"
and I get
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed
Hm, thanks. That's copied verbatim from your comment above. ;)
I did not notice the inconsistency with the rest of the comments.
In the meantime I DID manage to disable APST with
sudo nvme set-feature -f 0x0c -v=0 /dev/nvme0
and that seems to have helped (no crash for 9 hours). I'll retry with
I'm sorry, for taking so long to respond.
I do not have any logs, since they cannot be written to my hard drive in
the event of failure. (The SSD is my only hard drive and it can no
longer be accessed.)
But the error messages are something like:
EXT4-fs error (device nvme0n1p2):
I really don't understand what's going on here and what I'm expected to
do.
After enabling -proposed, my system boots with kernel
4.12.0-041200rc5-generic
and APST is enabled again (and my system crashed after about 10 Minutes with
exactly the same behaviour as before). Should that kernel
Sorry, you are indeed correct, apparently I forgot to update-grub.
Nevertheless, I get the same results
$ dmesg | grep -i apst
$ dmesg | grep -i nvme
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc5-generic
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
$ dmesg | grep -i apst
still does not return anything
$ dmesg | grep -i nvme
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc5-generic
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 nvme_core.dyndbg=+p vt.handoff=7
[
Public bug reported:
I have a Lenovo ThinkPad X270 with a Toshiba nvme SSD
$ sudo nvme list
Node SN Model
Namespace Usage Format FW Rev
Now I get the following:
$ dmesg | grep -i apst
[2.232133] nvme nvme0: apsta = 0, no APST
[2.448134] nvme :04:00.0: NVME_QUIRK_NO_APST
[2.448135] nvme :04:00.0: disabling APST.
[2.448137] nvme nvme0: apsta = 0, no APST
It seems like those messages are telling me that apst
I get
$ cat /sys/module/nvme_core/parameters/default_ps_max_latency_us
0
which kind of surprises me.
$ sudo find /sys -name '*latency*' | grep nvme0 | xargs cat
does not return anything.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I installed the kernel you linked to and set the kernel parameter.
On first boot the system immediately crashed with I/O errors upon login.
After reboot I could run the commands:
$ dmesg | grep -i nvme
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc5-generic
$ dmesg | grep -i apst
does not return anything.
--
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/1699004
Title:
APST gets enabled against explicit kernel option
Status in linux package
It is indeed very odd.
dmesg | grep dyndbg
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc5-generic
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 nvme_core.dyndbg=+p vt.handoff=7
[0.00] Kernel command line:
I have not upgraded the BIOS or the firmware, no.
This is really weird.
I tried the new kernel, however my system does not boot up with it.
It also does not show me an error that i can interpret, and the boot messages
do not seem to be logged anywhere. I'm assuming that the system has problems
With the new kernel the system boots up.
I get the following:
$ dmesg | grep -i nvme
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-rc6+
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.dyndbg=+p vt.handoff=7
[0.00] Kernel command line:
In that case it's enabled again:
$ dmesg | grep -i nvme
[0.00] Command line:
BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 nvme_core.dyndbg=+p vt.handoff=7
[0.00] Kernel
I'm not sure what exactly you're asking. The kernel above that does not
boot? The boot seems to fail before the drive is mounted, so I have no
logfiles whatsoever. The only thing I have is a photo of the last
messages on screen.
Or are you talking about something else?
--
You received this bug
Kai-Heng,
I tested it with 4.20 from Ubuntu mainline at the time and it still had the
issue. I think all ubuntu 4.x kernels ship with 3.2.6-k version of the e1000e
module.
I haven't tested the 5.0 release yet though.
As an addition, my lenovo ThinkCentre M720q hasn't had any issues since
I've
I had the same symptoms as in #58 on my Lenovo ThinkCentre M720q but
running 18.04.2 desktop.
Built the latest Intel driver, signed and installed it and updated initramfs.
I've been running for half a day now without problems, when previously the
symptoms would arise very quickly after boot.
Are there going to be further upgrade to xenial? I'm thinking of just
rolling a PPA since I tend to run more current vanilla kernels.
--
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/1588632
Pavel Selivanov solution #3 worked for me as well, but I purged my old
drivers first with:
sudo apt-get remove --purge bcmwl-kernel-source
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
*** This bug is a duplicate of bug 1291365 ***
https://bugs.launchpad.net/bugs/1291365
I would not mark this as a duplicate as this does not happen when
locking, only when suspending.
Funny thing is that I first get the old lock screen I was used to from
12.04 and when unlocked there's about
*** This bug is a duplicate of bug 1040943 ***
https://bugs.launchpad.net/bugs/1040943
Public bug reported:
Using Ubuntu 14.04
wireless is unstable, and cannot connect to some networks (which other
devices work flawlessly with)
iwconfig for nonworking network:(can connect using win7 on
Was this bug ever moved to a ubuntu bug as Christopher M suggested?
I have the same (or at least similar) problem on a Acer V5-171 with Atheros
AR9462.
I didn't know what the best practice was so I made a new bug reported and made
it a duplicate for the time being.
** This bug is no longer a duplicate of bug 1040943
Wireless -very- frequent disconnects in LinuxMint13 - Atheros AR9462
--
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/1324353
Title:
Sorry, my mistake.
I can confirm that Atheros AR9462 in Acer V5-171 is working in Ubuntu 14.04
(it was a DHCP server 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/1040943
Title:
found the error, nvm me..
How do I delete this bug?
for the curious the problem was with the local network DHCP IPv4
assignment.
** Changed in: linux (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Bug can be confirmed present in 14.04 with standard LTS kernel and
3.15rc2 kernel from ubuntu mainline kernel-ppa, daily build for april
24th (latest marked trusty at the time, now nonexistent, should I try a
newer kernel even if marked utopic?)
I tried upgrading to bios version 2.21, but there
will do, as soon as I get it booting into ubuntu again.
Apparently update-grub (or rather grub-probe) doesn't work when chrooting into
a root partition if it's btrfs, so I'm gonna try booting through a efi booter
from another computer running the same kernelversion of 14.04..
I'm quite pissed
*** This bug is a duplicate of bug 1173725 ***
https://bugs.launchpad.net/bugs/1173725
Public bug reported:
changing the backlight slider has no affect of actual screen brightness
in Ubuntu 14.04 using the 3.13.0-27-generic #50-Ubuntu kernel, also
exist on latest daily 3.15 kernel marked for
added a duplicate bug generated by ubuntu-bug.
is there a way to make it upload the information to a specific bug and not make
a new bug entry? or is it fine to just make duplicates? should I also make one
using the newest kernel?
--
You received this bug notification because you are a member
I can confirm successful booting using a Acer v5-171 with bios version 2.21
tested media is 14.04 liveUSB and installed ubuntu 14.04
All with secure boot enabled.
If you update to V2.21, this needs to be done from win8 and the
EFI/ubuntu folder was removed for me, so please make sure to back up
might this be a duplicate of this bug?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280020
it's a different acer device, but using the same SD controller from what
I can find, according to that bugs comment thread the SD card reader
works in 14.04 with 3.13.0-8-generic #28-Ubuntu SMP
this seems to be worked around in 14.04 since resizing is live by default.
But problem persists if a user changes to rectangle instead of normal in ccsm
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1173725 ***
https://bugs.launchpad.net/bugs/1173725
On the acer webspace the newest version of the bios is V2.21 how can I
find a version 2.25?
** Attachment added: newestBIOS.png
*** This bug is a duplicate of bug 1173725 ***
https://bugs.launchpad.net/bugs/1173725
well, the only thing google can find about a bios 2.25 for v5-171 is
this page, so I'm rather sure I'm on the newest bios version..
--
You received this bug notification because you are a member of Kernel
I just noticed that while secureboot works for ubuntu from grub-efi,
grub-efi cannot boot a windows bootloader with secureboot enabled. Which
affects people that dual boot AND want to have secureboot enabled.
Is this a bug or a feature?
--
You received this bug notification because you are a
Hi,
I have the same problem using 3.12.9-031209-generic 64bit mode.
Nickolay, is it too much to ask if you could provide a deb package for
this specifications?
Thanks,
Marcos.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in
Public bug reported:
Tested card was a 64GB SDXC from supertalent and Lexar 16GB SDHC.
In both cases nothing happens when cards are inserted, and after
10seconds dmesg shows: mmc0: Timeout waiting for hardware interrupt.
This seems to be a common problem in ubuntu with the Broadcom
Corporation
** Tags added: kernel-bug-exists-upstream-3.16
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/1353808
Title:
[ACER
Also downloaded and installed same version (4.1.0-040100rc1-generic) as
suggested on an older MacBook (plastic, late 2007 - 64-bit). Boots up
all fine here! So, for me the bug is fixed, but - as stated by
monochromec - not for the newer MacBook 8.1 series.
--
You received this bug notification
Sorry, I mixed up kernel versions in my first comment above. Before
15.04, I used only the official kernel coming with the Ubuntu releases.
So these were:
Ubuntu | Kernel
14.04| 3.13
14.10| 3.16
15.04| 3.19
As written above, both kernels 3.13 and 3.16 had occasional hangs
Agree'd. With this patch, screen turns off (not only black).
--
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/1455852
Title:
15.04 will not boot on MacBook 2,1
Status in linux package in
Hey Guys,
I also experienced this bug and was unable to boot completely with 3.19
kernel. Thus I gave the current upstream linux kernel (4.1-rc2) a try
and it works like a charm on every single boot. Couldn't be better.
Some more background:
I started with Lubuntu 14.10 (3.13 kernel) on my good
Also tried - also boots without issues. Nice work!
--
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/1455852
Title:
15.04 will not boot on MacBook 2,1
Status in linux package in Ubuntu:
Joseph Salisbury, I installed the test kernel and booted several times.
Still hangs after the Initial RamDisk loaded message is shown and the
fan speeds up. The screen however does stay alive and doesn't switch off
or turn black (messages stay visible).
Hope this helps. If you tell me where to
Just installed the official 3.19-18 kernel as well. Behaviour is exactly
the same.
Concerning the message: I have a German system while intuitively writing
English :). I guess it's exactly the same point.
--
You received this bug notification because you are a member of Kernel
Packages, which
** Attachment added: "screeshot of output with linux-image-3.13.0-63-generic in
recovery mode (first screen I can get)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492331/+attachment/4457366/+files/3_13_0_63_recovery0.png
--
You received this bug notification because you are a
** Attachment added: "screeshot of output with linux-image-3.13.0-63-generic in
recovery mode (early screen in between)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492331/+attachment/4457367/+files/3_13_0_63_recovery1.png
--
You received this bug notification because you are a
Public bug reported:
My Ubuntu 14.04 VM (Hyper-V / Windows Server 2008 R2) crashes directly
after the grub boot loader screen. Kernel packages linux-
image-3.13.0-62-generic and linux-image-3.13.0-63-generic are affected
while linux-image-3.13.0-61-generic works like all previous versions
did.
** Attachment added: "screeshot of output with linux-image-3.13.0-63-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492331/+attachment/4457365/+files/3_13_0_63.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Attachment added: "screeshot of output with linux-image-3.13.0-63-generic in
recovery mode (final screen)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492331/+attachment/4457369/+files/3_13_0_63_recovery3.png
--
You received this bug notification because you are a member of
** Attachment added: "screeshot of output with linux-image-3.13.0-63-generic in
recovery mode (late screen in between)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492331/+attachment/4457368/+files/3_13_0_63_recovery2.png
--
You received this bug notification because you are a
As stated in the desciption and shown in my screenshots I am not able to
run apport-collect. Please feel free to request further data.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
Thank you very much for your help! Unfortunately the VM is installed as
i386. I can't remember why, but maybe I hoped it whould use less RAM
with this arch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks again!
The Kernel you build does not work. The screen is nealy the same.
** Attachment added: "3_13_0_60_1.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492331/+attachment/4457498/+files/3_13_0_60_1.png
--
You received this bug notification because you are a member of
This one does not work too. It's nearly the same except for the recovery
mode crashing exactly like the standard mode.
--
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/1492331
Title:
The newest one is affected aswell.
--
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/1492331
Title:
kernel crashes on boot (ubuntu as a Hyper-V guest)
Status in linux package in Ubuntu:
The newest one is affected aswell.
Can you exclude that the problem is toolchain related?
--
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/1492331
Title:
kernel crashes on boot (ubuntu
This one is working fine.
--
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/1492331
Title:
kernel crashes on boot (ubuntu as a Hyper-V guest)
Status in linux package in Ubuntu:
In
This one is working.
--
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/1492331
Title:
kernel crashes on boot (ubuntu as a Hyper-V guest)
Status in linux package in Ubuntu:
In Progress
This one is working aswell.
--
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/1492331
Title:
kernel crashes on boot (ubuntu as a Hyper-V guest)
Status in linux package in Ubuntu:
In
This is the first working one.
--
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/1492331
Title:
kernel crashes on boot (ubuntu as a Hyper-V guest)
Status in linux package in Ubuntu:
In
Either Chris is wrong or 1492331 is not a duplicate of this. Is
be0cf6ca301c61458dc4aa1a37acf4f58d2ed3d6 of Vivid not the same as
97b2591fbecaa0366939bb5fdfecd79fe914de22 of Trusty? The commit-msg is
the same.
--
You received this bug notification because you are a member of Kernel
Packages,
Yes, that kernel works!
--
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/1492331
Title:
kernel crashes on boot (ubuntu as a Hyper-V guest)
Status in linux package in Ubuntu:
In
Public bug reported:
Version 0.6.5.7 was released 21 ago, this is the changelog:
https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.7
Since Ubuntu is now shipping ZFS we can't rely on the ppa anymore to
provide up to date packages. This point release also fixes a few minor
bugs and
I noticed that using the wily PPA will build correct kernel modules so
this is my workaround for now (doesn't require me to backport).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have the latest BIOS running on this machine and also getting ACPI
errors (not running ubuntu but manjaro ( 5.1.15-1-MANJARO #1 SMP
PREEMPT)
[0.932573] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [CAP1] at bit
offset/length 64/32 exceeds size of target Buffer (64 bits)
Currently using 5.1.15-1-MANJARO #1 SMP PREEMPT. Had the same error on
arch 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/1813496
Title:
powertop does not accurately determine
The bug was fixed in nvidia-settings 418.56, but I am using the nvidia
1650 gpu and the 418.56 driver doesn't support my gpu. Will the fix be
released for the 430 driver as well?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Might not be related, but check if you have a high file descriptor limit
configured (1048576). In my case that caused a delay in the pkexec cmd
used to change the brightness. See https://forum.manjaro.org/t/very-
slow-response-of-brightness-controls-in-gnome/74891/18 and
Thanks Kai-Heng - Manjaro doesn't have a 5.0 kernel (only offers me
realtime and that does not boot for me) but i can confirm on both 5.1
and 5.2.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Same error on HP zBook 15 G5, with a discharge rate between 300-400 mW.
Running arch linux though. Would the log files still help?
--
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/1813496
Confirm this is still an issue on Kernel 5.6.6-1-MANJARO #1 SMP PREEMPT
--
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/1813496
Title:
powertop does not accurately determine battery
*** This bug is a duplicate of bug 1861837 ***
https://bugs.launchpad.net/bugs/1861837
I am also seeing exactly this bug on older hardware (Lenovo G560) using up to
date kernel, so this can not be a duplicate of #1861837.
Workaround as proposed does also not work.
Can I provide any more
@Mohamed: Thanks for your great work! It's running now on my ASUS
Zenbook UX433FAC 14 with Fedora 34 installed.
--
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/1810183
Title:
numpad on
Same Problem here with Focusrite Scarlett 2i2 and 5.13.0-37.
The test kernel works for me: uname -a gives 'Linux
5.13.0-37-generic #42~20.04.1+lp1966066 SMP Tue Mar 29 06:12:21 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux' and sound is ok again.
Thanks for resolving this so fast!
--
You
I've had two systems taken down by what seems to be this bug now in the
last few weeks. This, together with the mismatched kernel and userspace
version of the ZFS tooling is really, really bad.
I do get that a ZFS root and the HWE kernel together is a rather
esoteric setup but it's all
I just installed a fresh Xubuntu 14.04 on an iMac with Fusion drive. I
split the Fusion drive to install the ubuntu on the SSD. I now get a lot
of very similar errors:
[332951.343902] ata5: irq_stat 0x0040, PHY RDY changed
[332951.343908] ata5: SError: { PHYRdyChg }
[332951.343916] ata5: hard
I found the following workaround:
as root:
echo min_power
/sys/class/scsi_host/host4/link_power_management_policy
where host4 correspnds to my ata5 in the error message. Now the error
messages have stopped. I hope this helps with debugging
--
You received this bug notification because you
Public bug reported:
Did not go into suspend. This happens from time to time, but usually it
works.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic 3.11.0-15.23
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic
For future reference, kolasa has a repository that have the patches required to
make the driver work on 3.17 (and 3.18).
https://github.com/kolasa/bcmwl-6.30.223.141
Personally I used dpkg-deb to edit the official deb file and add his
patches in (specifically 0011 and 0012), got it installed and
Hi Matt,
did you try the workaround that I suggested in the bugreport? Does it work? I
still need to do it on my machine, but it mitigates the problem.
Cheers,
Nils
Gesendet: Dienstag, 13. Januar 2015 um 08:50 Uhr
Von: Matt Hanyok 1318...@bugs.launchpad.net
An: nol...@gmx.de
Betreff: [Bug
94 matches
Mail list logo
