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.
> Chances are the r8169
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
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
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
@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
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
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 S1:
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
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
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),
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 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
12 matches
Mail list logo
