Weber
// This test program generates a Bus error core dump after reading or writing
a specific number
// of unique locations from/to a shared memory pool. It does not matter if
the pool memory locations
// are accessed starting at the base of the pool, incrementing up through the
addresses
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing
a specific number
est program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing
a specific number
// of unique locations from/to a shared memory pool. It does not mat
: Dell Inspiron 5558
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing a
specific number
Public bug reported:
The system does not shut down completely. The display goes black, but the power
LED stays on (ThinkPad E460). Trying to boot the system in that state is not
successful. Only way out is a hard reset.
Interestingly, rebooting works (very slowly).
Normal boot takes to long.
Public bug reported:
Closing the notebook results in the system going to sleep/hibernate.
Since upgrading to 22.04, the system is unable to wake up. No buttons pressed
register, even the power button does not work as a wake-up call.
Only way out seems to be a hard reset.
I am not alone with this
Public bug reported:
I got this e-mail that debsums found a symlink loop and am filing a bug
as instructed:
/etc/cron.daily/debsums:
debsums: Error: symlink loop detected in path
'usr/share/doc/libnvpair1linux/COPYRIGHT'. Please file a bug again
libnvpair1linux.
Additional info:
~$ apt-cache
Same here on a XPS 13 7390, 5.4.0-14-generic also.
--
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/1858844
Title:
[Dell XPS 15 9575] Screen brightness stopped working with linux-
I didn’t need to remove GDM3, but installing LightDM (and switching to
it) fixed it for me. Well, I should say it was a workaround, anyway...
> On Oct 24, 2018, at 11:56 PM, ccdisle wrote:
>
> Uncommenting "WaylandEnable=false " worked.
>
> Removing gdm3 did not work, I just got redirected to
Why is it incomplete again?
--
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/1508510
Title:
Something in the Kernel crashes when I try to mount via NFS
Status in linux package in Ubuntu:
Public bug reported:
I have a vagrant virtual machine that mounts a directory on my computer
via NFS, this does not work and the reason seems to be this. My System
is using SMP, reverting to the kernel before solves the problem.
Broken: Linux paul-ThinkPad-T430s 3.13.0-66-generic
Working:
Nope ... did not work
uname -a
Linux paul-ThinkPad-T430s 3.13.11-031311ckt27-generic #201509251131 SMP Fri Sep
25 15:34:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[ 133.141688] BUG: unable to handle kernel NULL pointer dereference at
0008
[ 133.141734] IP: []
** 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/1508510
Title:
Something in the Kernel crashes when I try to mount
Will try.
--
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/1508510
Title:
Something in the Kernel crashes when I try to mount via NFS
Status in linux package in Ubuntu:
Incomplete
Bug
Installing Xubuntu 15.04 to boot in UEFI non-secure mode has some
challenges of it's own. But once I got the system working, it doesn't
freeze anymore.
If you want to use legacy BIOS mode, you'll have to compile a kernel.
However, it is not necessary to apply the patch above. Just disable the
USB
The cause of the freeze seems to be a BIOS problem, as Alan suggested on
the linux-usb mailing list. When booting in UEFI mode (from a Xubuntu
15.04 installation medium), three of the devices listed by lspci are
missing, compared to legacy BIOS mode. One of those is the device that
caused the
** Attachment added: "output of lspci when booting in legacy BIOS mode"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4474852/+files/lspci-legacy.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
contents of /sys/kernel/debug/usb/ehci/:00:1d.0/registers before unbinding:
bus pci, device :00:1d.0
EHCI Host Controller
EHCI 1.00, rh state running
ownership 0001
SMI sts/enable 0xc008
structural params 0x0028
capability params 0x00036881
status 6008 Periodic Recl FLR
command
contents of /sys/kernel/debug/usb/ehci/:00:1d.0/registers before unbinding
the bus which triggers the freeze:
bus pci, device :00:1d.0
EHCI Host Controller
EHCI 1.00, rh state suspended
ownership 0101 linux
SMI sts/enable 0xe000
structural params 0x0028
capability params
I removed the bios-outdated tag. The guy who wrote about his BIOS update
in comment #9 has a completely different problem and commented off-
topic.
** Tags removed: bios-outdated-1.13
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Current state of things: I've tracked down the code line where the
freeze happens. It's in function ehci_halt within file ehci-hcd.c. The
function is executed on shutdown as well as when the usb devices on the
bus are about to be probed again. The latter is triggered by "lsusb -v"
as root.
** Attachment added: "photo of the virtual terminal after the freeze"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4458832/+files/screenshot-freeze.JPG
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
For the records, here's a screenshot (photo) of the system after a freeze.
Series of actions to get there:
1. enable kernel debug output
2. detach external mouse, to verify that messages appear
3. hit enter to get a new prompt line
4. trigger the freeze with "lsusb -v"
lsusb prints the name of
The previous log for the "bad" kernel was incomplete, due to kernel
buffer overflows caused by systemd output. I've switched that off as
explained here: https://bugs.freedesktop.org/show_bug.cgi?id=76935#c1
** Bug watch added: freedesktop.org Bugzilla #76935
As suggested by Alan Stone on the linux-usb mailing list, I've verified
that the "USB cable is bad" messages are caused by the order in which
the USB devices are initialized.
I've also found a new way of triggering the freeze on a bad kernel:
https://bugs.freedesktop.org/show_bug.cgi?id=76935#c1
Sorry, the link in comment #14 is nonsense, a paste error.
The new way to trigger a freeze is:
echo :00:1d.0 >/sys/bus/pci/drivers/ehci-pci/unbind
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sorry, the link in comment #14 is nonsense, a paste error.
The new way to trigger a freeze is:
echo :00:1d.0 >/sys/bus/pci/drivers/ehci-pci/unbind
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "last good kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4456919/+files/dmesg.good.full.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Valentine, your problem is almost certainly not related to the one I reported
here.
You should seek advice in forums or on mailing lists for your computer and/or
distribution.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
As suggested on the linux.usb mailing list, I've added some additional debug
print statements to the first bad kernel. They are not triggered by "lsusb -v"
though. I'm attaching kernel debug output from the boot sequence of two kernels:
- the bad one, with additional print statements
- the last
I've verified that the freeze on shutdown is caused by the same commit.
Contrary to my initial report here, the freeze on shutdown happens late in the
sequence, not early.
I'm used to much longer shutdown times from my desktop :-)
** Summary changed:
- lsusb -v as root freezes the kernel on
As requested on the linux-usb mailing list, I've bisected the problem in
the mainline git repository.
638139eb95d2d241781330a321e88c8dafe46078 is the first bad commit
commit 638139eb95d2d241781330a321e88c8dafe46078
Author: Petr Mladek pmla...@suse.cz
Date: Fri Sep 19 17:32:24 2014 +0200
** Attachment added: output of git bisect log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4451330/+files/bisect.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for your advice!
I've posted a bug report upstream:
http://permalink.gmane.org/gmane.linux.usb.general/129790
I also checked out some older kernels.
The problem is present since 3.18, while 3.17.x was OK.
Or rather, had other, less dramatic problems on the machine.
** Tags added:
Public bug reported:
reproducible: always
Steps to reproduce:
- open a terminal
- sudo bash
- lsusb -v
In a virtual terminal, the command prints the name of the first device
it finds, then the system freezes completely. In a terminal of the
desktop, I don't even get the name of the device, the
** Attachment added: output of lsusb -t
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/865/+files/lsusb-t.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Joseph, your kernel in comment #52 does work on my 2 affected laptops
--
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/1440724
Title:
linux-image 3.19.0.12.11 will not boot - Intel mobile
Same here, on two laptops, one the same Dell D630 as the OP, as well as
a basically identical D830. However, editing the boot parameters from
the grub menu does not allow me to get to a login screen, and I am
unable to even get to a vt to run any sort of commands.
--
You received this bug
same here on Acer TravelMate B113 on 3.8.0-29-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/1140716
Title:
[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on
39 matches
Mail list logo
