Public bug reported:
My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.
When I don't have headphones plugged in, the system thinks headphones
If I save the ALSA state with the headphones unplugged to a file:
sudo alsactl --file=settings-out.txt store
And then plug in the headphones and restore it:
sudo alsactl --file=settings-out.txt restore
I still get no sound. But then diffing the final state against the
unplugged state did find t
This may be a kernel driver bug, and a regression from 4.12. See
http://www.lattepanda.com/topic-p24689.html?sid=1fa88916eb19dd9d65e0abd3ecbf6210#p24689
This may be a missing piece of platform data in the kernel that would
tell it to invert jack detection on this particular board. I will try
testi
This is actually a kernel bug, in Linux. The issue is the absence of
platform data for this particular board in the snd_soc_rt5645 module.
The issue can be worked around by creating
/etc/modprobe.d/hacksound.conf with the following contents:
# Invert jack detection (1) and use detection mode 2 (2
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255465/+files/PulseList.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/
I set the bug to Confirmed, despite being the original reporter, because
the bot told me to.
The Apport logs I posted are form the system with my workaround enabled.
I also blacklisted the HDMI audio module, since I don't use HDMI audio,
and I thought it might help. It didn't seem to, but I never
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255467/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255464/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255458/+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/1824259
Ti
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255460/+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/18
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255462/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255463/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255461/+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/1824259
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255466/+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/1824259
apport information
** Tags added: apport-collected
** Description changed:
My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.
When
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1824259/+attachment/5255459/+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
Do I have to downgrade my system from Dingo to Cosmic in order to test
this in Cosmic, to keep my bug from being closed?
May 20, 2019 7:02 AM, "Ubuntu Kernel Bot" wrote:
> This bug is awaiting verification that the kernel in -proposed solves
> the problem. Please test the kernel and update this
Hello,
Thank you for looking into this.
I installed the DKMS module deb (which built itself against kernel
5.0.0-13, which is what the system is now updated to), commented out the
quirk-setting line in my module config file, and rebooted.
I now have no sound; list-cards in pacmd shows me that it
Here's the whole `sudo dmidecode` output (attached).
** Attachment added: "Output of sudo dmidecode for the LattePanda"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+attachment/5258402/+files/dmidecode.txt
--
You received this bug notification because you are a member of Kern
OK, this second deb seems to solve my problem! The headphone jack state
is detected correctly without the quirk! Thanks!
--
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/1824259
Title:
Hea
Public bug reported:
The `perf` profiling tool, and a few other tools, are part of the Linux
project. Ubuntu gets them from a package specific to the running kernel
version, and uses wrapper scripts installed as e.g. /usr/bin/perf to
dispatch to the appropriate version for the running kernel. This
I reported this bug from this container running on an Ubuntu-based host
where I built it. When I tried to run ubuntu-bug in the container on the
host where I actually encountered the problem, it refused to report the
bug due to... a non-Ubuntu kernel!
--
You received this bug notification because
There's not really an applicable Ubuntu kernel to collect logs for; the
problem is only apparent in a container on top of a host that doesn't
run a recognized kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a memb
Public bug reported:
I went to boot my computer today and it wouldn't boot.
I get an "Unable to handle kernel NULL pointer dereference" message
during the boot process, and, a bit after that, a message from the
kernel watchdog about CPU #0 being stuck. Then the boot process stops
completely.
I w
The drive that was giving me this problem failed. I got a replacement
(which is notionally the same model, with the same USB ID 0781:5581),
and, on kernel 4.15-22, under Xen, the new drive seems to work fine in
USB 3 ports.
However, I also tested with the latest v4.17 kernel from the given link
(4
This also affects the mainline kernel build 4.17.0-041700.201806041953
that I was testing for another bug.
I've attached a photo of the screen with the issue occurring, in that
version.
Booting not under Xen seems to work around the issue, and the system
comes up, but that's not useful for me bec
I updated my BIOS and tested the -24 kernel, as was recommended. It
definitely doesn't work any better. It still has the null dereference
problem, and then it prints a bunch of smp_call_function_too_many errors,
apparently forever.
On Tue, Jun 19, 2018, 08:11 Joseph Salisbury
wrote:
> Can you se
Hello,
Thanks for putting this together. I tried to get the kernels you
built, but I'm having trouble establishing a secure (https) connection
to kernel.ubuntu.com. It looks like the server might not offer https.
Can you give me the expected hashes of the files so I can verify the
downloads?
Tha
I don't seem to have access to change the tag, but I can confirm that
4.15.0-34-generic from -proposed solves the problem. So the tag should
be verification-done-bionic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
Nope, my speculation is definitely wrong. The disk shows up in lsscsi:
[anovak@octagon ~]$ lsscsi
...
[9:0:0:0]diskSeagate Backup+ Hub BK D781 /dev/sdb
Also, it shows up in lsusb -t with a "uas" driver.
Maybe the problem is the uas driver itself?
Here's the full description of the U
Even after rebooting with the drive for the zpool physically removed
from the system, I still had a zpool I couldn't destroy, export, or
otherwise remove from the listing.
Using "sudo zpool status -Pv" I worked out that my ZFS was actually
expecting to find the data on partition 1 of the drive:
e
I pulled the hdparm binary from Artful, and it can't spin down the drive
with -y either.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774569
Title:
gsmartcontrol, hdparm, and ZFS
It looks like the drive is replying with an ILLEGAL REQUEST/INVALID
FIELD IN CDB error to all the interesting SCSI commands, and to pretty
much anything hdparm sends it.
I've also tried throwing sdparm at it. The only page sdparm can get out
of it is the basic identification page:
[anovak@octagon
Public bug reported:
I have a 128 GB Sandisk Ultra USB Flash Drive. It works when I plug it
into a USB 2.0 port, or if I partially insert it into a USB 3.0 port (so
the USB 3 pins don't make contact).
Here's what lsusb says about it:
Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra
And dmes
OK, I've tested this kernel, and it works just fine under Xen, from
what I can tell. The system comes up just fine:
Linux octagon 4.15.0-23-generic #26~lp1777338Commit8eca6add0 SMP Wed
Jun 27 15:50:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
The offending commit must be later.
On Thu, Jul 5, 2018
Thanks!
I have tested this kernel; it doesn't work, so the problem is between
fc8704280f2ada9f61f08a2d5adc0dab169cc207 and
8eca6add0defde203282476d7969a7c13bbd7d91.
I've gotten set up with a kernel build environment; I think I can
finish the git bisect myself, but looking at the commits in that
r
OK, I tried that one and it still exhibited the issue. I'm going to
try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next.
On Fri, Jul 20, 2018 at 9:08 PM, Adam Novak wrote:
> Thanks!
>
> I have tested this kernel; it doesn't work, so the problem is between
> fc8704280f2ada9f61
That one works. On to 5856293c78e552c012835e667d66775bba20b4f7.
I suspect 3f6a3b035f91 and abd39ac1da07 may be the real problem, since
the CPU I am using is an AMD Ryzen chip, and those are tinkering
specifically with how the kernel handles those.
On Fri, Jul 20, 2018 at 10:23 PM, Adam Novak
OK, I have finished the bisect.
3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c is the first bad commit. I
tested it and it displays the problem, and I tested
abd39ac1da07b433fc570332ee9ad938b5071760 right before it and that one
boots fine.
On Sat, Jul 21, 2018 at 9:42 AM, Adam Novak wrote:
> That
I'm not finding any kernel packages in bionic-proposed; maybe they were
released already?
I've installed and tested 4.15.0-29 from the normal repos; it has the same
null pointer dereference at address 8 issue.
On Tue, Jul 24, 2018, 09:17 Joseph Salisbury
wrote:
> Thanks for finishing up the bis
I've been advised by Juergen Gross that not having "x86/xen: Add call of
speculative_store_bypass_ht_init() to PV paths" from the mainline kernel
might contribute to this problem. I am trying to pull that in now.
--
You received this bug notification because you are a member of Kernel
Packages, w
OK, I grabbed commit 74899d92e3dc7671a8017b3146dcd4735f3b "x86/xen:
Add call of speculative_store_bypass_ht_init() to PV paths" from
g...@github.com:torvalds/linux.git and cherry-picked it on top of the tag
Ubuntu-4.15.0-29.31, and built the kernel, and now it boots fine as
dom0! I think that t
Thanks for preparing this kernel; I am downloading it now. What are
the expected hashes of the files, so that I can verify the insecure
downloads?
On Tue, Aug 7, 2018 at 8:49 AM, Joseph Salisbury
wrote:
> I built a test kernel with commit 74899d92e3dc7671a8017b3146dcd4735f3b.
> The test ke
OK, I have tested the provided kernel and it works for me under Xen.
Thank you for fixing the bug! I look forward to seeing this in the
real releases.
[anovak@octagon ~]$ uname -a
Linux octagon 4.15.0-31-generic #34~lp1777338 SMP Tue Aug 7 14:57:12
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
On Mon,
Public bug reported:
The r8152 Ethernet device in my Lattepanda board just disconnected from
my network while I was uploading some files over the LAN.
dmesg reported this:
[1036155.155084] [ cut here ]
[1036155.155099] NETDEV WATCHDOG: enx00e04c368b17 (r8152): transmit qu
45 matches
Mail list logo
