The source package which produces the binary package zfsutils-linux is
called zfs-linux.
https://github.com/openzfs/zfs/pull/13338 is what you'd like to
cherrypick to fix this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
Added the crash file
** Attachment added: "nvidia-dkms-520.0.crash"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/2031973/+attachment/5715183/+files/nvidia-dkms-520.0.crash
--
You received this bug notification because you are a member of Kernel
Packages, which i
Just did a fresh install of 20.04.3 LTS, updated & installed linux-
generic-hwe-20.04 and it booted up just fine. Only difference is
/etc/default/grub on a client's appliance, this is the default/grub on
the machine that freezes:
# If you change this file, run 'update-grub' afterwards to update
#
Same thing, hardware is an Intel NUC NUC10i5FNK. OS: Ubuntu Server
20.04.3 LTS. Kiosk machine, when I select 5.13.0-28 to boot, it just
freezes at loading ramdisk. 5.11.0-46-generic works just fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
(A bit delayed, but just for anyone finding this...)
No, you cannot remove a FAULTED normal data device - device_removal
involves migrating all the data off the old one, which you cannot do if
it's not there.
(logs and caches are different.)
You'll need to recreate the pool.
--
You received th
Public bug reported:
If you do zfs send -D with 0.8.x userland and 2.0.x kernel, it will
actually try to produce a deduplicated send stream (whereas 2.0.x
userland stubs out that flag and prints a "this did nothing, stop trying
to use it" note).
On the system that generated it (20.04 amd64, runni
I lied, it totally happens on 20.04 (w/5.4.0-89-generic) and 21.04
(5.11.0-37-generic), I just had forgotten I hadn't used virtio-scsi on
them, just SATA.
Oh boy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
htt
Public bug reported:
As I often do, I tried running OpenZFS git master's ZFS Test Suite
against the new Ubuntu 21.10 release, to make sure nothing was secretly
broken.
This is on an Ubuntu 21.10 amd64 VM (running 5.13.0-20-generic) inside
VirtualBox 6.1.26 on Windows 10 x64, using virtio-scsi for
My suggestion would be to print a warning unconditionally on first
install that you should test it and not assume it will just work, and/or
to not set crashkernel=... with the default in the first place so people
have to go explicitly set it (and, implicitly, read about the fact that
one size does
I suppose I should have made it clear that just changing the amount of
memory reserved was not sufficient.
Perhaps it would be useful to print a message saying "hey, I know we set
something by default, but we don't expect that to actually work, so you
should probably test and adjust it"?
Because
** Description changed:
I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04
system, installed specifically to try reproducing a bug.
But when I tried, after kdump-config status reported "ready to dump" on
reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed t
Public bug reported:
I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04
system, installed specifically to try reproducing a bug.
But when I tried, after kdump-config status reported "ready to dump" on
reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the panic to
c
I followed the steps above on Linux Mint, and the output of "journalctl
-b | grep i915" no longer had the "GPU HANG or Resetting rcs0 for hang
on rcs0" errors.
I also confirmed that running Zoom no longer has any lags or hangs. It
works as expected.
So confirming this fix worked!
(Sorry, I'm ne
I can also confirm that this problem continues in 5.3.0-51-generic
However, I see it very frequently (not just for 5 seconds... happening
all the time) with two different use cases.
1) When i have a headset (with a mic) plugged into the front audio port.
One of my cores also goes to 100% utilizat
led".
I go thru the usual rfkill stuff and all seems OK. the "new driver from
github" reports it is good now in dmesg.
but I cant find any way to "enable"
any ideas?
thanks
rich
On Fri, May 5, 2017 at 4:00 PM, Cruz Fernandez
wrote:
> Another one, do you have Secure
problem is now worse.
any ideas?
thanks
rich
On Fri, May 5, 2017 at 6:13 AM, Cruz Fernandez
wrote:
> @painterengr have you tried to download the file from somewhere else?
> https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/
> BCM20702A1-0a5c-21e6.hcd
>
> Hope t
Unfortunately this is a linux system and not a windows system. The
references to the procedures to "obtain the windows version file and
convert it to linux" does not work and the links are no good.
I don't understand your reply for a "413c" or "x/y/z". The chip the T530
has is 20702A1. I followed
My Lenovo T530 Bluetooth does not work like so many others that have been
reported. I am running
Ubuntu 14.04.3 LTS 64 bits,
kernel 4.4.0-75-generic,
Broadcom Bluetooth BCM20702A1 (001.002.014) build ,
Latest BIOS: LENOVO 2359CTO/2359CTO, BIOS G4ETA7WW (2.67 ) 08/24/2016
My dmesg error is:
bl
As I previously reported, my SSD is full and cannot build kernels. I
have made several attempts to upgrade to a larger SSD but the grub2
installer refuses to install so I'm still not able to build kernels.
Since you don't care to help you will have to wait until I can find
someone to help correct t
I already read #25 4 or more times and it did not provide sufficient
details to tell me what to do in conjunction with your other direction.
So I provided the details of what I did and asked my questions when you
balked Your reply doesn't help when it doesn't even answer these
follow up questio
I'm not sure how to provide this. You sent me to
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D to obtain the
various kernels to test. This is the kernel releases I bisected...
Note that I do not know "git" and haven't built unix kernels since 1990,
only download prebuilt kernels for at th
Sorry, I don't know how to edit an entry
Previous entry stated "It remains on until manually disabled or when the screen
saver exits."
It should read:
It remains on until manually disabled just the same as when the screen saver
exits.
--
You received this bug notification because you are a
4.5-rc1 and above bug exists
kernel-bug-exists-upstream-4.5-rc1
** 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/1645985
After bisecting the kernel releases I have determined when this bug was
injected.
Release 4.4.39 is OK
Release 4.5-rc1 is BROKEN
64-bit Generic versions were used.
After testing many releases I have discovered one additional aspect of
this bug of the backlight inappropriately coming on following
** Tags added: kernel-fixed-upstream
** Tags removed: kernel-fixed-upstream
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
downloaded into new directory:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-headers-4.9.0-040900_4.9.0-040900.201612111631_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-headers-4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb
http://kernel.ubuntu.com/~kernel-
will do
If I can just install a kernel I think I have room. I dont have space for a
separate partition for a complete and separate installation.
thanks
rich
On Sun, Dec 18, 2016 at 7:01 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> rich painter, in order
Kernel 4.4.0-53, the latest kernel update, flowed in today.
This kernel also exhibits the keyboard and screen-top illuminators bug.
Booting the last 3.x kernel, 3.19.0-77, makes the illuminators to work
correctly.
--
You received this bug notification because you are a member of Kernel
Packages,
Installed "ubuntu 1404_HWE_EOL" update. Other packages updated with it
since nothing has been updating since Aug because ubuntu 1404_HWE_EOL
update was holding it up.
Problem still exists with the keyboard backlight coming on when the
screen saver restores the normal desktop upon hitting the Enter
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1645985/+attachment/4787175/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1645985/+attachment/4787179/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1645985/+attachment/4787185/+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/1645985/+attachment/4787183/+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/1645985
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1645985/+attachment/4787182/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1645985
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1645985/+attachment/4787173/+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/1645985/+attachment/4787184/+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/1645
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1645985/+attachment/4787178/+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/1645985
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1645985/+attachment/4787181/+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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1645985/+attachment/4787176/+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/16
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1645985/+attachment/4787177/+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/1645985
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1645985/+attachment/4787180/+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/1645985/+attachment/4787174/+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/1645985
Ti
apport information
** Tags added: apport-collected
** Description changed:
System: Lenovo Thinkpad T530 laptop
OS: ubuntu 14.04 LTS, kernel 3.19.0-66-generic 64bit
lsb_release -rd
Description: Ubuntu 14.04.5 LTS
Release: 14.04
With the above configuration the keyboard backli
if I let additional update flow in following rerunning
1404_HWE_EOL...
do you have any insight on this risk?
thanks
rich
On Wed, Nov 30, 2016 at 9:19 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Yes, please run apport after installing the update. Also, check to see
&
should the apport command be run AFTER installing the offending
1404_HWE_EOL update?
I/m guessing so.. but please confirm.
thanks
rich
On Tue, Nov 29, 2016 at 10:01 PM, Brad Figg wrote:
> This bug is missing log files that will aid in diagnosing the problem.
> >From a terminal wind
Public bug reported:
System: Lenovo Thinkpad T530 laptop
OS: ubuntu 14.04 LTS, kernel 3.19.0-66-generic 64bit
lsb_release -rd
Description:Ubuntu 14.04.5 LTS
Release:14.04
With the above configuration the keyboard backlights and screen-top
illuminator work as they are supposed to.
In
Public bug reported:
Somehow wouldn't install properly. Only program running at same time was
browser.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_6
Found the issue, was an issue with how the dumps were being transferred
to another machine, not the dumping mechanism itself.
** Changed in: kexec-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
** Description changed:
Ubuntu 15.10 amd64, kernel 4.2.0-19-generic, kexec-tools 2.0.9-1ubuntu1
kexec-tools and crashdumprecipe appear to be configured correctly - on
echo c | sudo tee /proc/sysrq-trigger, it panics, saves a valid
{dump,dmesg}.[datetimestamp] in /var/crash along with a
Public bug reported:
Ubuntu 15.10 amd64, kernel 4.2.0-19-generic, kexec-tools 2.0.9-1ubuntu1
kexec-tools and crashdumprecipe appear to be configured correctly - on
echo c | sudo tee /proc/sysrq-trigger, it panics, saves a valid
{dump,dmesg}.[datetimestamp] in /var/crash along with a
[timestamp].c
so how do I fix whatever the bot changed?
On Fri, Sep 11, 2015 at 8:30 PM, Brad Figg
wrote:
> This change was made by a bot.
>
> ** Changed in: linux (Ubuntu)
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://b
OK, so how do I fix it?
--
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/1494995
Title:
Mousepad Not Working
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have an H
Public bug reported:
I have an HP Chromebook 14 in which I'm running Ubuntu 14.04 from a
Seagate 1TB External Hard Drive. I originally installed 12.04 and
updated to 14.04. At no point since I have done this has the stock
mousepad in the laptop worked, however a wired USB mouse works fine.
Please
** Changed in: linux (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
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/1465322
Title:
regression: "df: `/sys/kernel/debug': Fun
This is the output from LSPCI. There is a mention of NEC USB 3
controller, however I have tried all the USB2 and USB3 ports on the
machine previously without success.
markrich@markys-home-pc:~$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor
DRAM Controller (r
I do not know how to apply the patch mentioned without guidance and
instructions.
--
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/1136110
Title:
USB Audio Codec choppy playback
Status in
I have asked the retailer to take back the card I have purchased. It is
of no use to me if Linux is reporting it as USB3 and not USB2.
--
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/113611
This is the result of the output from dmesg.
[10633.605645] usb 9-2: USB disconnect, device number 2
[10639.410777] usb 9-2: new full-speed USB device number 3 using xhci_hcd
[10640.279483] usb 9-2: New USB device found, idVendor=0c56, idProduct=0003
[10640.279488] usb 9-2: New USB device strings:
This is the result of the output from dmesg.
[10633.605645] usb 9-2: USB disconnect, device number 2
[10639.410777] usb 9-2: new full-speed USB device number 3 using xhci_hcd
[10640.279483] usb 9-2: New USB device found, idVendor=0c56, idProduct=0003
[10640.279488] usb 9-2: New USB device strings:
I have attached a new report according to wishes from the device playing
audio through a separate PCI USB PCIe device. The file is 2.mon.out.
The rice crispies sound is still present through this device too.
** Attachment added: "2.mon.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bu
The device is now plugged into a USB port on the motherboard. I will do
a USBMON trace for you later. I will need to buy another PCI USB card
from eBay or other to provide another set of USB ports, however I'm
using only half of those I presently have so will be overflowing with
them.. :-/
--
Y
[ 3379.830961] usb 3-4: USB disconnect, device number 2
[ 3394.173420] usb 2-1.5: new full-speed USB device number 6 using ehci-pci
[ 3394.973170] usb 2-1.5: New USB device found, idVendor=0c56, idProduct=0003
[ 3394.973176] usb 2-1.5: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 339
I will do so, however the problem is the same for both USB2 and USB3
ports. I have tried them all in the past on the three controllers
(ASMEDIA, NEC and Intel).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
I have no idea if I have done what you desire correctly - given it's my
first attempt to do so, however I hope the following will be helpful.
markrich@markys-home-pc:~$ lsusb
Bus 002 Device 005: ID 18d1:4ee1 Google Inc. Nexus 4
Bus 002 Device 004: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 002 De
Apologies for being vague. I do not know how to get the information you
need to help identify the problem. The comment numbers you suggested do
not help me. I am still uncertain of my way around the lower levels of
Linux.
Please tell me how to get the information you need.
--
You received thi
Your suggestion does not work for me.
I have a USB PCI card installed to my computer alongside my motherboard
USB ports. I have already tried the Arcam device on its ports with the
same results when trying to isolate the cause previously.
--
You received this bug notification because you are a
>>
Mark,
I've just had the same problem on Gentoo with a new (and rather
expensive) DAC. With the 3.13 and 3.14 kernels it sounds like a bowl of
Rice Krispies - snap, crackle and pop.
BUT! After reading this bug report I tried the latest 3.4 kernel (3.4.87) and
that works perfectly. It would be
The homePC/Server I built isn't a year old yet. I cannot justify
replacing motherboard, RAM and CPU just for a single problem. I am
using a 3770K on an ASUS P8Z-77v-Deluxe motherboard. Nothing about my
rig is cheap sadly. :-(
--
You received this bug notification because you are a member of Ke
Does anyone read this anymore or am I yelling at the wind?
--
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/1136110
Title:
USB Audio Codec choppy playback
Status in “linux” package in Ubu
So I patiently waited for weeks until the release of 14.04 with its 3.13
kernel and the problem remains.
Did the patch not get integrated into the final release?
If not, why and how can I do it myself - in easy steps please!
I still cannot use my DAC without the crackles and pops. :-(
--
You r
Has anyone tested with the upcoming 14.04 release to see if the problem is
still there?
I still have an expensive unused DAC waiting for a fix.
--
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
I have the arcam mwave device mentioned above.
I am using 13.10 with kernel 3.11.0-17-generic as part of the normal
update procedure but the problem is still present.
I am uncertain how to apply the fix mentioned above (still very green when it
comes to kernel rebuilds).
How can I resolve?
--
Mainline kernel 3.11.0-031100rc3-generic fixes the suspend/resume
problem for me. (Other late releases may also fix the problem.)
--
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/1088721
Ti
73 matches
Mail list logo
