I solved the problem. This was wake on LAN. When I ran sudo ethtool eth0 the
output included:
Supports Wake-on: pumbg
Wake-on: ug
From the ethtool man page:
u Wake on unicast messages
g Wake on MagicPacket™
This was wake on unicast messages.
I can reproduce this with v4.1-rc1-vivid. I had to uninstall
nvidia-340-updates because the DKMS module failed to build and boot hung
while it was installed. So, I was using nouveau for my GeForce 8600GT
PCI express graphics card.
I can't reproduce it if not running X, or running X, twm and xterm
Public bug reported:
I'm running 64-bit Ubuntu 15.04 on a Gigabyte GA-P35-DS3R rev 1.0
motherboard with BIOS F13. I also have 32-bit Windows 7 SP1. If power
was fully cut, including standby power, and Windows has not been run
since then, Ubuntu will quickly wake from S3 sleep without any apparent
This keeps happening to me occasionally, less than one out of ten times.
Over the last several Ubuntu releases, sudo ifconfig eth0 down
followed by sudo ifconfig eth0 up has always been enough to re-
establish connectivity. A long time ago, I sometimes had to unload and
reload the r8169 module.
Public bug reported:
Occasionally the onboard gigabit Ethernet on this Gigabyte GA-P35-DS3R
rev 1.0 motherboard doesn't work after suspend. This happens less than
one out of ten times. Over the last several Ubuntu releases, sudo
ifconfig eth0 down followed by sudo ifconfig eth0 up has always been
I refuse to test this with the latest upstream kernel. That is because
the bug happens rarely and the upstream kernel breaks other stuff. I
would have to use Ubuntu for a prolonged period with the upstream
kernel, putting up with that brokenness, or I would have to go into
suspend and wake many
After upgrading to Ubuntu 16.10 I removed the r8168-dkms package so I
could see if this bug still exists in 4.8.0 kernels. I upgraded on
October 13th, and everything worked fine until today, October 24th.
After waking from sleep eth0 appeared up according to ifconfig, but I
had no connectivity and
I wonder if this is the same bug which I am seeing on my Dell Inspiron
6400 laptop with Radeon X1400 video. Occasionally I get white lines
which are very similar to the
https://www.youtube.com/watch?v=nx2-Fvihzxg video posted at the
beginning. The only difference is that more lines are present at
Public bug reported:
I'm opening a raw disk device (like /dev/sdb) with O_DIRECT and then
doing write() calls. The device is actually USB mass storage. Looking at
the USB packets with Wireshark, I see that the write() calls are being
split into multiple SCSI writes. That part is okay I guess. The
rmmod b43 works in 4.15.0-21-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/1763967
Title:
rmmod b43 hangs
Status in linux package in Ubuntu:
Confirmed
Status in linux source
>From http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.9/ I installed:
linux-headers-4.15.9-041509_4.15.9-041509.201803111231_all.deb
linux-headers-4.15.9-041509-generic_4.15.9-041509.201803111231_amd64.deb
linux-image-4.15.9-041509-generic_4.15.9-041509.201803111231_amd64.deb
And booted into
Public bug reported:
When I boot linux-image-4.13.0-36-generic then I get an eth0 interface
and dmesg output includes:
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x42
43)
b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100
After installing
linux-headers-4.16.0-041600rc4_4.16.0-041600rc4.201803041930_all.deb ,
linux-headers-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb
and
linux-image-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb
from
Public bug reported:
I'm running Ubuntu on a Dell Inspiron 6400 with a 14e4:4328 "Dell
Wireless 1500 Draft 802.11n WLAN Mini-Card". Running "rmmod b43" always
hangs. So far I have only tried it while connected to a wireless
network. I immediately disconnect from the wireless network, so it seems
In 4.15.0-13-generic, BCM4321 WiFi works via b43 and BCM4401-B0 b44
Ethernet eth0 exists. So, it seems this has been fixed. Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Bug does not exist in 4.16.2-041602-generic. I did rmmod b43 4 times and
it always succeeded immediately. It never worked properly in
4.15.0-13-generic so I am confident this isn't just random success, and
it means the bug is fixed in upstream.
What older version should I try? Currently I don't
Public bug reported:
This problem started after upgrading to Ubuntu 19.04. It was not present
with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic
kernel. Ever time during boot there is a null pointer dereference in the
b44 driver for the on-board Ethernet on this Dell Inspiron
linux-image-
unsigned-4.20.0-042000-generic_4.20.0-042000.201812232030_amd64.deb is
good but linux-image-
unsigned-5.0.0-05rc1-generic_5.0.0-05rc1.201901062130_amd64.deb
is bad. I'm not sure I'll have time for a git bisect.
--
You received this bug notification because you are a member
Sorry, I mean bug is not present in 4.18.0-16-generic and present in
5.0.0-7-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/1821564
Title:
b44 Ethernet driver null pointer
Public bug reported:
On my Dell Inspiron 6400 laptop with Mobility Radeon X1400 and built in
Intel HDA audio with STAC9200 codec, audio is normally perfect. Even
with 100% load on both CPU cores audio is perfect. However, while
playing high resolution video, audio has many tiny regular
Public bug reported:
My Inspiron 6400 laptop has a Dell Wireless 1500 Draft 802.11n WLAN
Mini-Card with BCM4321 chip. I was using airmon-ng from aircrack-ng to
enter monitor mode. It claims the chipset is "non-mac80211 device?
(report this!)" but I think that's incorrect information and only
I don't normally use Ethernet on my laptop, and for some reason the b44
module for Ethernet doesn't get loaded normally. So I didn't notice
this. But I'm getting the same problem reported in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/comments/8
in Ubuntu 19.10 with
iommu=soft does not help, and I don't understand why it would help
theoretically when the Core 2 Duo T7400 CPU doesn't have a hardware
IOMMU. The problem seems to be that the 64 MB buffer is allocated beyond
1 GB.
One theoretical good workaround would be to boot up with only 1 GB and
then enable
This problem still exists in Ubuntu Focal Fossa (development branch)
20.04 with linux-image-5.4.0-21-generic. It also exists in linux-image-
unsigned-5.6.2-050602-generic_5.6.2-050602.202004020822_amd64.deb
With linux-image-5.4.0-21-generic I didn't get any error messages after
"insmod b44" in
I don't see a null pointer message but the b44 driver is still broken in
5.4.0-33-generic on my Dell Inspiron 6400:
[ 3148.539194] ssb: Found chip with id 0x4401, rev 0x02 and package 0x00
[ 3148.599317] b44 :03:00.0: Sonics Silicon Backplane found on PCI device
:03:00.0
[ 3148.599414]
Wake worked with kernel 5.11.0-16-generic. So, I guess this is fixed.
--
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/1922439
Title:
X hangs after wake on Mobility Radeon x1400
Status
Public bug reported:
I have a Dell Inspiron 6400 with Mobility Radeon x1400. In Ubuntu 20.10
and earlier, wake from sleep worked properly. In Ubuntu 21.04, X does
not work after wake from sleep. It fails in Plasma, Xfce, Openbox and
Twm. With both Plasma and Xfce the screen is totally black. In
Wake from sleep works in Xfce and Plasma in Ubuntu 21.04 when using
kernel 5.12.0-051200rc5-generic from https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.12-rc5/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I got upgraded back to 470 because new 460 transitional dummy packages
were released, which caused the upgrade. I could have prevented that via
apt-mark hold.
When I was getting these problems with 470 I had
nvidia.NVreg_PreserveVideoMemoryAllocations=1 in my kernel command line,
via
Public bug reported:
Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake
from suspend. It does start running again, but there is no video output. I'm
attaching text for two crashes from kernel log output. First is:
/var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967
In Ubuntu 21.10 with 5.13.0-16-generic kernel, I don't get any dmesg
errors after I "modprobe b44" and Ethernet works initially at reasonable
speed, but the whole system freezes totally after a few minutes. I
suppose this means the b44 driver still doesn't work properly, because I
don't get such
No, "pcie_aspm=off" does not help.
I also tried uninstalling broadcom-sta-dkms. It blacklists the b44
module via /etc/modprobe.d/broadcom-sta-dkms.conf and also
https://wiki.debian.org/wl says that b44 is incompatible with wl. This
did not help either.
My laptop seems fine with just having the
Public bug reported:
I kept getting occasional hangs. Usually, the mouse would still move,
but I couldn't do anything other than use Magic SysRq. These seemed to
happen more after resume from suspend, but I also saw them happen if the
computer hadn't been suspended since booting. They probably
I applied the patch to files in /usr/src/broadcom-sta-6.30.223.271/ and then
reinstalled linux-image-6.5.0-7-generic to make DKMS rebuild the module. It
made this error go away:
UBSAN: array-index-out-of-bounds in
After putting nvidia.NVreg_PreserveVideoMemoryAllocations=0 in the
kernel command line I don't remember any black screens after wake from
suspend. They certainly haven't happened in Ubuntu 22.04. The computer
is always usable immediately after waking.
However, I have gotten lockups some time
I see lots of these errors on my Dell Inspiron 6400 when booting. They
started after upgrading to Ubuntu 20.10. Everything still seems to work.
** Attachment added: "Errors from dmesg"
After adding mitigations=off to the kernel command line,
5.4.0-132-generic boots successfully every time. This workaround
satisfies me. I don't need those mitigations on that old PC, and turning
them off probably speeds it up a bit.
--
You received this bug notification because you are a member
Public bug reported:
I am running Ubuntu 18.04.6 LTS on an old PC with a Pentium 3 and Soltek
SL-65KVB motherboard. The 5.4.0 generic kernels work fine up to and
including release 126. Attempts to boot 128, 131 and 132 quickly lead to
a panic every time. The error seems to be "Attempted to kill
I'm not sure that this error message causes problems. My card had
firmware in its non-volatile memory, and worked without this. After I
updated its firmware to 2.0.2.6 with the chip vendor's Windows tool, I
didn't have problems with the card itself after suspend.
39 matches
Mail list logo
