Since 16.04.4 LTS with Kernel 4.4.0-128-generic/x86_64 the problems
seems to be fixed. Our VM with more than one VHD are running without
problems for two weeks now. Neither backups nor cluster failovers are
crashing the VM.
--
You received this bug notification because you are a member of Kernel
After a couple of weeks without issues, thanks to changing the v-sync in
compris, it is back and getting progressively worse.
Will try running system monitor and see if this helps.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Running the system monitor as suggested by Jon had no effect.
Doing a cold boot reduced the problem tempoarily.
--
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/1777238
Title:
video lag
S
This is getting really bad. I can't even type without the screen freezing
momentarily!
What information would be most useful to diagnose the problem? How do I
collect it? How do I add it to the ticket?
--
You received this bug notification because you are a member of Kernel
Packages, which i
The lag is everywhere for me, not just in video. Screen scrolling also
has this stutter.
--
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/1777238
Title:
video lag
Status in linux package
After posting the above, I found
https://www.youtube.com/watch?v=cIQZv6MXzno.
The first solution (uncheking v-sync, log out, log in) seems to be
working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Hi Zoltan. This computer (HP Envy 17 Leap Motion SE) is a fresh install
of 18.04. I upgraded my Dell Inspiron from 16.04 and don't have the
issue. Very weird.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
Public bug reported:
Laptop crashes after successfully login with 2nd monitor attached. If I
attach the monitor after login system crashes when changing display
settings , e.g. monitor positions.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-44-generic 4.15.0-44.47
Proc
I can confirm: VMs with more than one disk still crash with out of
memory. We're using Hyper-V on Windows Server 2012 R2 with GEN2 VMs
(Ubuntu 16.04.3 LTS/Xenial, Kernel 4.4.0-104-generic). VMs with just one
disk are running perfectly.
--
You received this bug notification because you are a membe
Sorry I noticed this was still open - problem did disappear after a few
months with newer kernel version
--
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/1168819
Title:
168c:0032 [Asus G75
I have got this bug. If you need some debug information, I can provide
it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth headsets are not wo
PID ACCESS COMMAND
/dev/snd/controlC0: gdm1915 F pulseaudio
boris 2340 F pulseaudio
Date: Thu Oct 6 15:01:24 2016
DpkgHistoryLog:
Start-Date: 2016-10-06 15:01:09
Commandline: apt-get -f install
Requested-By: boris (1000)
Install: linux-image
Public bug reported:
I have a Intel pro wireless 3945 for wifi connection, but it do not
found any network and I can not fix.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-firmware 1.143
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
App
thanks
Regards
Boris
- Messaggio originale -
Da: "Joseph Salisbury"
Inviato: 08/09/2015 18:15
A: "vbori...@gmail.com"
Oggetto: [Bug 1492807] Re: the wi fi network do not work and no networs
werefound
Did this issue start happening after an update/upgrade? Was
Public bug reported:
I've come across the problem that lsblk treats the WWN as SN.
~# lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
~# apt-cache policy util-linux
util-linux:
Installed: 2.34-0.1ubuntu9.1
Candidate: 2.34-0.1ubuntu9.1
Version table:
*** 2.34-0.1ub
As I don't know what kind of data will be sent and this is a production
system with customer data on it, I won't do this.
There is also no need to actuall collect data from the system, as it is
a simple out of the box installation.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confir
Maybe this is the issue: https://github.com/util-linux/util-
linux/commit/b95752ad206222dfaa854a01c6106c89d2c607a2
https://github.com/util-linux/util-linux/issues/1143
Maybe you can backport it?
** Bug watch added: github.com/util-linux/util-linux/issues #1143
https://github.com/util-linux/ut
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 of
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 64
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 during
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 t
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 rec
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] b4
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 linux-image-5.3
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 interruptio
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
cosme
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.
https://bugs.launchpad.net/bugs/1754911
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
m
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 ha
Hi, is there any progress on this bug?
--
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/1728244
Title:
Touchpad stops working after reboot on Apollo Lake
Status in Linux:
Unknown
Status
Hi, I tried Ubuntu 160404 and Ubuntu 1804 beta 2 on Chuwi Lapboo air
with live usb. On both of them touchpad didn't work. I am not very
experienced with linux environment yet. Is there way for me to
contribute in solving this problem&
--
You received this bug notification because you are a member
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
Hi, does anyone know when this bug will be fixed?
I really would love to use Ubuntu on my Chuwi Lapbook Air but I can't
because touchpad doesn't work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
@bbaker6212 Hi, Brad
Thank you for quick answer.
Touchpad model is HID\ALPS0001. Laptop is Chuwi Lapbook Air 14.1.
I tried linux kernel 4.18rc8 with Ubuntu 18.04 today and touchpad didn't
work at all there. Could you please guide me on how to make it work?
--
You received this bug notification
Hi, Kai-Heng @kaihengfeng
Please find attached dmesg file. This is with kernel from comment #187.
Should I file a new bug from it?
@elpraga, thank you. I wil try kernel from comment #162 and write back
my testing results here.
** Attachment added: "Dmesg from Kernel from #187. Touchpad not worki
@elpraga, @kaihengfeng
I can confirm that touchpad works perfectly with kernel from #162 on
Chuwi Lapbook Air, Ubuntu 18.04. Please find attached dmesg for it.
Is there anyhow I can help further to resolve this issue?
** Attachment added: "Dmesg for Kernel from #162. Touchpad is working."
ht
Kai-Heng @kaihengfeng,
Kernel from #187 doesn't work after Suspend on Ubuntu 18.04.
--
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/1728244
Title:
Touchpad stops working after reboot on
Public bug reported:
Hello,
After a few days of troubleshooting a problem with L2TP and IPSec a
fellow from ServerFault pointed out that my problem is a known bug fixed
by 87cdf3148b11 commit which wasn't backported on 4.15 kernel.
Ubuntu 4.15.0-36.39-generic 4.15.18
** Affects: linux (Ubuntu)
Hi Joseph,
Thank you for your fast response.
I will be able to test it only next week as I am out of office until Monday.
Bests,
Boris
--
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
Hello Joseph,
I have checked with lp1795653 build and my problem is solved.
IPSec packets are not translated anymore when passing thru a L2 tunnel.
Thanks,
Boris
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Hi, Hans/Kai-Heng Feng
I tried kernel from comment #187 on Chuwi Lapbook Air 14.1 with touchpad
HID\ALPS0001. It doesn't work for me completely - neither trackpad nor
buttons. Is there anyhow I can help troubleshoot this issue?
BTW. Hans, thank you for your support and answers in my previous
ques
I didn't had time to test again the kernel but a fast fix would be
kernel upgrade to 4.17 or newer version.
--
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/1795653
Title:
87cdf3148b11 was
** Bug watch added: Email to milanovic.boris90@gmail #
mailto:milanovic.bori...@gmail.com
** Also affects: linux via
mailto:milanovic.bori...@gmail.com
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is su
I found a way to trigger the problem fast (within one minute).
On Raspberry Pi 3 B+:
* Enable IPv4 forwarding: sysctl net.ipv4.ip_forward=1
* Enable masquerading: iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
* Start a netcat listening process: sudo nc -l -p 1234 > /dev/null
On another ma
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 PC
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 http://kernel.ubuntu.com/~kernel-ppa/mainl
>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 4.
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
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
I am affected by this bug on dell xps 13 9350 both on FHD and QHD.
Running kernel 4.6rc5 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.6-rc5-wily/ helps as a work-around.
--
You received this bug
t request?
> Yuck. That dies with a divide error. And that looks like XEN is supplying crap
> data in the CPUID.
Joe, do you have
ed6069b xen/apic: Provide Xen-specific version of cpu_present_to_apicid
APIC op
-boris
>
> Does the patch below cure the issue?
>
> Thanks,
>
On 05/06/2016 03:38 PM, Joseph Salisbury wrote:
> On 05/06/2016 03:13 PM, Boris Ostrovsky wrote:
>> On 05/06/2016 02:48 PM, Thomas Gleixner wrote:
>>>
>>> Yuck. That dies with a divide error. And that looks like XEN is supplying
>>> crap
>>> data in
On 05/06/2016 04:51 PM, Joseph Salisbury wrote:
> Thomas' patch does resolve the bug. The cpuid info can be seen here:
> https://launchpadlibrarian.net/258234267/cpuid_full.txt
Any chance you could post it raw (cpuid -1 -r)?
Thanks.
-boris
--
You received this bug notification beca
This bug is fixed for me in http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.4.9-xenial/
--
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/1554613
Title:
Screen flickers on XPS 13 9350/955
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
Update: Now this bug is fixed for me by http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.4.9-xenial/ as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Can you please post:
1. Guest configuration file
2. boot log from dom0 (please boot loglevel=8)
3. xl dmesg and xl info from dom0
4. boot log from guest (also loglevel=8)
5. dmidecode from guest (I am mostly interested in BIOS object)
-boris
--
You received this bug notification because you
So given that you are seeing this on 3.2 guest this would be a different
problem. Having said that, I don't see any errors in dmesg_domu.txt
anyway.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
If you don't specify debug and loglevel boot options I think you won't
see these. Of course, the underlying problem would still be there.
Do you observe this on guests with newer kernels?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Yes, those would be helpful although now I think understanding EC's BIOS
(seabios I assume?) may be more important. Neither I nor Stefan have
been able to reproduce this problem and it seems that EC does something
in BIOS (and possibly qemu) that may not be available in vanilla Xen,
most importantl
Can you attach Xen config file and xen boot options?
--
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/1304001
Title:
xen:balloon errors in 14.04 beta
Status in “linux” package in Ubuntu:
And guest kernel config file please.
--
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/1304001
Title:
xen:balloon errors in 14.04 beta
Status in “linux” package in Ubuntu:
Confirmed
Bu
I would like to reproduce this first and for that I will need at least
config file that is used for launching the guest ('memory' and 'maxmem'
for sure but having the whole file would be better) as well as guest's
kernel config file. Knowing what xen boot options are as well as if
there is anything
This warning implies that SRAT may be wrong. And I just noticed that this may
not be vanilla 4.2:
[0.00] DMI: Xen HVM domU, BIOS 4.2.amazon 01/24/2014
Are we on a custom HVM BIOS? That's where memory is described to domain.
Although NUMA issue may be somewhat orthogonal, it still may be
[14Ah 0330 4] Proximity Domain :
[14Eh 0334 2]Reserved1 :
[150h 0336 8] Base Address :0001
[158h 0344 8] Address Length : 1000<===
This looks wrong
[160h 0352 4]
Matt, can you post config file that you used? I tried a few different
configurations and (again) could not reproduce this.
--
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/1304001
Title:
I am using 4.2 stable tree, configured with default parameters (i.e. no
options to ./configure script):
[root@ovs103 install]# xm info
host : ovs103.us.oracle.com
release: 3.16.0-rc1-pmu-dom0
version: #1 SMP Mon Jul 7 14:09:40 EDT 2014
machine
And this is my guest (14.04 desktop):
Linux version 3.13.0-24-generic (buildd@panlong) (gcc version 4.8.2
(Ubuntu 4.8.2-19ubuntu1) ) #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014
(Ubuntu 3.13.0-24.46-generic 3.13.9)
--
You received this bug notification because you are a member of Kernel
Packages
Hmm, yes, the patch may not work if something (AWS, I guess) keeps
requesting to balloon memory.
Can someone try the attached patch (on top of David's)? I only compile-
tested it.
** Patch added: "cancel_balloon.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4
Actually, this (v2) is a slightly better one to try.
** Patch added: "cancel_balloon_v2.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+attachment/4223585/+files/cancel_balloon_v2.patch
--
You received this bug notification because you are a member of Kernel
Packages, wh
I am not sure the bug should be closed. David's fix made system behavior
tolerable to users (because the error is now only reported once) but the
problem is still there. If possible I'd suggest lowering bug's priority
but keeoping it open.
--
You received this bug notification because you are a m
rg.conf
[Here some driver options could be set, eg. uncomment pageflip and set
it to "True", save any edits and after that reboot]
sudo shutdown -r now
---
Grüße
boris
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Thx for the feedback Lars, I think we can call it on the bug Walter,
so far nobody else has come forward with anything that suggests
otherwise.
Where would we propose to implement those params to be set as default
for the specific systems in future builds/ releases, would a post to the
ppc list b
I believe this is due to incomplete or not at all set up Xorg conf which
for some reason is not done for a long time on certain Radeon systems,
so those are without DRI and all the bells and whistles.
Did you try what I mentioned above?
sudo service lightdm stop
sudo Xorg -configure
sudo mv xorg
known ppc radeon 9000-range AGP-freeze issue, needs radeon.agpmode=-1
yaboot param workaround, additionally combination with video=ofonly is
recommended
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Pack
05:45 schrieb "Lars Noodén" :
> Boris, it's still a bug until the installer adds those boot options and
> the installed system ends up with them in yaboot.conf
>
> ** Changed in: linux (Ubuntu)
>Status: Invalid => Confirmed
>
> --
> You received this bug
Thanks Lars,
still learning the ropes with this, from Walters response I gathered we
could call it, but I'm glad we can work the installer defaults in, makes
more sense that way and I expressed as much in my comments above, was
just not sure if this should be left open all the way, but yeah makes
No fix (from me, that is)
I need to be able to reproduce this and this appears to only be
happening in AWS environment.
--
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/1304001
Title:
xe
I was waiting for this patch to be pulled into the mainline before
posting a pointer/commitID here. It's not there yet.
But yes, you need that commit (on top of 3dcf63677d4e) to make kernel
shut up.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Hello all,
@Walter I did encounter this in 14.04.1 as well
it works if I force PCI mode via yaboot radeon.agpmode=-1 (which I
thought was the expected workaround for an unknown issue with AGP and
the user would be expected to use it)
While on my system with a 9200 based chip under OSX it's list
so I quess the question might be what changed, did AGP work before, was
there no hardware acceleration, was PCI transfer maybe temporarily
forced?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
It is now in mainline, commit fd8b79511349.
--
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/1304001
Title:
xen:balloon errors in 14.04 beta
Status in “linux” package in Ubuntu:
Triage
"System was installed using Boris/Adam's "agpmode=-1"that worked to
clean up the 14.10 GUI . . . and I've tried various flavors of
"radeonfb" boot parameters . . . "
- don't! My understanding was using "radeonfb" conflicts with KMS which
we w
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
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
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. "Wak
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 b
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.
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 tim
@Adam
sadly, yes. But it now should be clear with the existing workarounds
that's not necessary for future releases.
--
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/1377878
Title:
PPC -
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 s
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
** Tags added: verification-done-lunar-linux verification-done-mantic-
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/2042853
Title:
[UBUNTU 23.04] Kernel config option missing for
I re-added the tags "verification-done-lunar-linux
verification-done-mantic-linux" manually as they were deleted by the bridge
(bugproxy) when syncing the target milestone.
This problem of disappearing tags has been seen lately also in other bugs / LP
items. IBM is currently investigating what'
Still a problem on _random_ supermicro hardware: i have 15 identical
nodes, set kernel parameters for `console=ttyS0 console=tty0` and now
_one_ node will not commission or therefore provision with this error.
Maas (snap) is at 3.2.7-12037-g.c688dd446
The maas UI doesn't update the parameters pass
Figured out what made that one node different from the rest: its UEFI network
boot stack had both PXE and HTTP enabled, while the others were PXE only.
After i added the kernel boot parameters, MAAS started to truncate the HTTP URI
by a few characters (and now keeps doing that even if the kernel
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 /etc/default/
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 b4
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
/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_cfg80211_hybrid.c:2394
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.
https://dreamlayers.blogspot.com/20
This is still a problem at least up until kernel 5.10 if not later.
--
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/1851833
Title:
[Sager Clevo notebook model PB50_70RF,RD,RC] Unable to a
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 th
1 - 100 of 117 matches
Mail list logo
