Same problem on two identical machines that have dual 1Gb/s ethernet cards on
the motherboard.
This apparently causes booting to stall for about a minute, see this snippet
from syslog after a boot. These timestamps are
while the machine is booting, and hasn't gotten to the point where it presents
Hi Narinder,
Well, that's exactly the problem - sometime during the boot, apparently
biosdev thought it was p2p1, and the OS tried to assign the name p2p1 to
it, which it had already given out. When I run biosdev now, it shows up
as being p2p2 allright - but the interface doesn't get assigned the
Ugh, I also just noticed that this messes up the order of my interfaces
in SNMP - it's swapped the two ones, so now my graphs that used to show
the external interfaces, are showing the internal ones, and v.v.
--
You received this bug notification because you are a member of Kernel
Packages, which
Server configuration:
SuperMicro X9DRi-F mainboard
On-board dual I350 (rev 01) Gigabit Ethernet controller [8086:1521], igb driver
PCI-E X540-AT2 (rev01) 10Gbase-T Ethernet card [8086:1528], ixgbe driver.
bios: Version 2.0a, 03/27/2013
The current situation causes two issues:
1.) The former inte
Kai-Heng Feng: The full dmesg output is already part of the ticket.
However, I've now also included the latest crash as an attachment.
The issue happened again tonight. When the crash happens, the system
loses the ability to write to the filesystem(s). Specifically, if you
type 'sync' in a window,
Public bug reported:
Ubuntu 20.04 system, and a SparkFun RED-V RISC-V devboard attached via
USB. Software used includes SEGGER J-Link (proprietary) and /opt/riscv-
bin/riscv32-unknown-elf-gdb from the riscv github repo.
With a 'gdb remote' connection established, via the JLink software,
pressing
6 matches
Mail list logo
