FWIW, this still seems to be a problem with Ubuntu Minimal cloud images
for bionic? I'm using them in a slightly non-standard configuration
(ripping the root file system image out and handing it to qemu), but
this does seem to be a problem with the image itself - the modules are
included on the roo
Earlier problems seem to have been caused by the packages not all
arriving in the archive together, and apt-get/aptitude and myself
getting very confused - apologies for noise. Can now confirm that
4.15.0-35.38 seems to solve the issue; tags adjusted.
** Tags removed: verification-needed-bionic
**
OK, this looks like a mismatched set of package landed in the archives
at some point? I have apt-get updated and reinstalled and everything is
now sorted..
** Summary changed:
- 4.15.0-35.38 missing many modules
+ 4.15.0-35.38 some packages in archive are out-of-date
** Changed in: linux (Ubuntu
Argh, linux-modules-extra didn't install for some reason...
--
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/1792635
Title:
4.15.0-35.38 some packages in archive are out-of-date
Status in
This seems to be caused by a bad build? Many modules missing:
$ ls /lib/modules/4.15.0-34-generic/kernel/drivers/ | wc -l
91
$ ls /lib/modules/4.15.0-35-generic/kernel/drivers/ | wc -l
39
No sdhci, r8169, or usb hub driver (wherever that lives) made this a fun
one to try to debug :(
** Summary c
New bug report opened:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792635
On 14 September 2018 at 21:29, Steve Dodd wrote:
> Well 4.15.0-35.38 doesn't even finish booting on my machine. Doesn't
> find the root volume and the USB keyboard doesn't finish booting.
&g
Public bug reported:
Trying to test the fix for https://bugs.launchpad.net/bugs/1779817.
I get dropped into initramfs because the root fs is not found - rootfs
is on LVM on MMC storage on this machine (Apollo Lake-based 'media
centre' type box.)
Unfortunately USB keyboard doesn't work either so
Well 4.15.0-35.38 doesn't even finish booting on my machine. Doesn't
find the root volume and the USB keyboard doesn't finish booting.
Chances are the r8169 fix is fine but I can't test.
On 14 September 2018 at 18:02, Brad Figg wrote:
> This bug is awaiting verification that the kernel in -propos
Yup, this kernel finally fixes things for me too (I did remember to
disable my other workaround) - thanks Kai, look forward to seeing it
SRU'd.
On 24 August 2018 at 09:39, Jan Rathmann wrote:
> Kai-Heng, the bug seems to be gone on my system with your newest kernel
> in #63 and I don't experience
Attached is a work-around for the in-kernel driver that is as unhacky as
I can make it.
Drop it in /etc/initramfs-tools/scripts/init-top and chmod a+x it. Add
'r8169_disable_msi' to your kernel command line (/etc/default/grub,
usually.) Remember to update-initramfs and update-grub as necessary.
F
Can we cherry-pick
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=7c53a722459c1d6ffb0f5b2058c06ca8980b8600
for bionic?
On 10 August 2018 at 12:49, Heiner Kallweit <1779...@bugs.launchpad.net>
wrote:
> @Steve, there's some resistance amongst kernel maintainers agains
@Heiner, I know a number of other modules have a "use_msi_x" option - I
guess that would be too much to ask given I'm the only one who seems to
need it so far? :)
On 9 August 2018 at 16:54, David Jordan wrote:
> I can reproduce the issue with ethernet failing on the r8169 on resume
> from suspen
It's was only Kai's kernel from comment #39 that didn't boot - I've not had
any other problems on that front.
On 9 August 2018 at 12:05, Heiner Kallweit <1779...@bugs.launchpad.net>
wrote:
> Whether other systems suffer from the same MSI-X incompatability we'll
> know only once I get more such bu
Yup, afraid so, Beelink S1: https://www.amazon.co.uk/dp/B077HKCT78 - I'm
basically using it as an old-fashioned X Terminal. They promised a BIOS
update to "make it work with Linux" but I never got it to install and they
stopped answering my emails :( Happy to put it down to broken hardware so
long
Just double-checked with lspci -vvv and indeed the Realtek NIC is the only
MSI-X capable device. Is there anyway to disable MSI-X globally but leave
MSI on? All I can find is pci=nomsi which seems a bit heavy handed..
On 9 August 2018 at 10:08, Steve Dodd wrote:
> Yup, afraid so, Beelink
@kalle1
Your one liner seems to fix things - thank you! Also discovered I can
work around by writing 0 to /sys/devices/pci//msi_bus, which will
at least mean I can run unpatched Ubuntu kernels until we figure this
out :)
Anybody still having problems and wanting to test if this is their issue
is
Hmm, no "IOMMU" messages in dmesg, and the CPU is supposed to support it,
so I guess it is disabled,
however this machine really doesn't have a BIOS to speak of, in terms of
configurable settings anyway :(
On 8 August 2018 at 14:42, Heiner Kallweit <1779...@bugs.launchpad.net>
wrote:
> One more h
I'm about to dash out, but will try the above change later. Meanwhile,
relevant bits of dmesg:
[4.440185] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[4.445120] r8169 :01:00.0: enabling device ( -> 0003)
[4.458178] r8169 :01:00.0 eth0: RTL8168g/8111g at 0x
(ptrval), 84:
Progress!
I have built ubuntu-bionic.git myself and discovered the only commit I
have to revert to get things working again is this one:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=41450d46ba126887b9548cfcdf99957da5418ca5
@Kai, does that help you at all? If nothing else mig
I can't even boot Kai's latest kernel! The system hard locks early in the
boot process, I have tried blacklisting r8169 and rebuilding the initramfs,
pretty sure it is not loaded by the point at which it hangs. My hardware is
cursed...
On 7 August 2018 at 21:13, Jan Rathmann wrote:
> @Kai-Heng
>
I've just built net-next direct from git and still have the same issue -
the NIC doesn't come back after suspend, even with rmmod / modprobe.
Is there any upstream awareness of this? Bug tracker and/or mailing list
discussion?
--
You received this bug notification because you are a member of Ker
I still think there are multiple bugs here. Some of us have a network that
absolutely will not come back up after suspend with kernel version
>4.15.0-23, even after reloading the driver. So there is a very clear
regression that I would really like see resolved / rolled back. Breaking
stuff in an LT
Is this even from a cold boot? Similar issues being discussed at bug
#1779817 and bug #1752772 but that is only after suspension.
--
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/1784542
Tit
A bit off-topic but: on a third machine of mine, booting into into
Bionic leaves the network card in a state where WoL won't work at all,
even after rebooting back into Trusty (3.13.0.) Have to power cycle the
machine, then WoL is fine.. (r8169 driver again, obviously)
--
You received this bug no
lp1779817 kernel from #19 doesn't help me, last working kernel is
4.15.0-23.
--
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/1779817
Title:
r8169 no internet after suspending
Status in l
Actually, I take that back - my testing (on a different machine) with
image-generic-hwe-16.04-edge in xenial is giving inconsistent results.
--
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/1
Also affects linux-image-generic-hwe-16.04-edge in xenial.
** Also affects: linux-signed-hwe (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-signed-hwe (Ubuntu)
** No longer affects: linux-signed-hwe (Ubuntu Bionic)
--
You received this bug notification because
I'm not sure if I'm in the right bug thread, 4.15.0-24 stopped my
r8168/9 NIC working after suspend, was fine in prior versions. I have
tested Kai's lp1779817-2 kernel above but it does not help.
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Eth
I'm a bit lost in this bug thread already, but the fix here seems to
have caused a regression for me.
I had no problems up until -24, with -24 I can't get the network up
after resume, even with module reload.
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Expre
On Wed, Jan 22, 2014 at 04:13:19PM -, Max wrote:
> Steve Dodd:
> > Last time I did, my own problems were caused by dhclient and ureadahead..
>
> It is not an ureadahead issue, it is an extra fork in upstart to launch
> shell for ureadahead if more than one partition mounted
This does seem to be getting kind of embarassing. With modern journalled
filesystems on relatively straightforward hardware configs an unclean
shutdown shouldn't be the end of the world (after all, power failures
can happen), but it's not "nice" either.
Unfortunately we also seem to have a hell o
The version currently in proposed (3.2.0-57.87) seems to fix the issue
here. If someone else seconds that, let's mark this as verified.
--
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/124666
That sounds plausible - I would guess wireless connections are usually torn
down at the end of the user session (i.e. logout) whereas I assume wired
connections persist right to system shutdown??
On Oct 21, 2013 3:01 PM, "Christian Niemeyer"
wrote:
> It occurs that the problem did *not* exist aft
Hence why I said I/O errors on *write*. If the block dev layer reports
an error to the VM on page-out, it knows the data hasn't been correctly
written.
I'm not sure zram actually allocates the whole amount of memory it's
configured to use, initially:
steved@xubuntu:~$ free
total
Been a long time since I looked at the relevant bits of the kernel
source, but errors when _writing_ to swap devices should be quite
manageble, I would have thought - simply mark the block/page as bad and
go looking for another free location. It'll be _read_ errors that cause
problems!
Some info h
I've lost track of which bugs cause what here, but *not* looking good on
precise so far:
steved@xubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.3 LTS
Release:12.04
Codename: precise
steved@xubuntu:~$ uname -a
Linux xubuntu 3
Ah, I didn't know about apport-collect, I've added my data as Bug
#1223273, and marked it as a duplicate ..
** 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 Ubun
*** This bug is a duplicate of bug 1217189 ***
https://bugs.launchpad.net/bugs/1217189
Public bug reported:
I'm seeing errors such as these:
Sep 9 08:41:26 xubuntu kernel: [ 20.641594] Buffer I/O error on device
zram0, logical block 256349
Sep 9 08:41:26 xubuntu kernel: [ 20.641599] B
Like Hans, I'm seeing this on 12.04 LTS. linux-image-3.2.0-53-generic-
pae seems to enable zram by default, which results in lots of
"scheduling while atomic" errors in syslog and occasional lockups
(machine still responds to ping, but not ssh, desktop frozen.)
This seems like a pretty critical pr
39 matches
Mail list logo
