I am seeing this bug on buster, currently udev 241-7~deb10u4. Somehow I
wound up with /etc/systemd/network/*.link files that I did not create
(maybe a postinst migration script did?).
To get my old working config working again I did:
* rm /etc/systemd/network/*
* rm /etc/udev/rules.d/70-*
*
Is this still reproducible with v244?
In case you are using stable, there is a v244 backport for buster available.
On Fri, 24 Jan 2020 21:23:17 -0500 Dragan Tubic
wrote:
> I have the same problem
>
> Failed to rename network interface 2 from 'enxXXX to 'wan':
> Device or resource busy
I have the same problem
Failed to rename network interface 2 from 'enxXXX to 'wan':
Device or resource busy
I noticed the following line in the journal that before udevd fails,
systemd-networkd[293]: enxXXX : IPv6 successfully enabled
so I tried to disable ipv6 in
Hello,
It looks like, I have the same problem and it is still present in 240-4.
For more detail :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917128#40
Regards,
--
Emmanuel DECAEN
* Wolfgang Walter [Fri Jan 18, 2019 at 11:56:28AM +0100]:
> On Fri, 11 Jan 2019 17:44:48 +0100 Michael Biebl wrote:
> > On Wed, 9 Jan 2019 22:41:24 +0100 Michael Biebl wrote:
> > > I've pulled this patch and applied it to 240-3.
> > As I'm pretty sure this is fixed in 240-3, I'm going to close
On Fri, 11 Jan 2019 17:44:48 +0100 Michael Biebl wrote:
> Version: 240-3
>
> On Wed, 9 Jan 2019 22:41:24 +0100 Michael Biebl wrote:
> > On Fri, 28 Dec 2018 15:24:03 +0100 Wolfgang Walter
> > wrote:
> > > On Friday, 28 December 2018 15:05:06 CET Michael Biebl wrote:
> > > > On Sun, 23 Dec 2018
Hello,
I've tried with 240-4, the VLAN problem is still present.
File /etc/systemd/network/00-xgbe1.link :
[Match]
MACAddress=00:50:56:96:0d:d7
[Link]
Name=xgbe1
File /etc/network/interfaces :
iface xgbe1.40 inet static
address 192.168.40.218/24
$ sudo ifup xgbe1.40
Cannot find device
On Fri, 28 Dec 2018 15:24:03 +0100 Wolfgang Walter
wrote:
> On Friday, 28 December 2018 15:05:06 CET Michael Biebl wrote:
> > On Sun, 23 Dec 2018 01:51:00 +0100 Wolfgang Walter
> >
> > wrote:
> > > systemd-networkd from 240-1 though crashes with
> > >
> > > Assertion 'IN_SET(link->state,
> On Sun, 23 Dec 2018 01:51:00 +0100 Wolfgang Walter
>
> wrote:
> > Package: udev
> > Version: 240-1
> > Severity: important
> >
> > After upgrading from 239-15 to 240-1 or higher my network setup breaks.
> >
> > The breakage is similar to the last one I reported (bug #904198) though
> >
On Friday, 28 December 2018 15:05:06 CET Michael Biebl wrote:
> On Sun, 23 Dec 2018 01:51:00 +0100 Wolfgang Walter
>
> wrote:
> > systemd-networkd from 240-1 though crashes with
> >
> > Assertion 'IN_SET(link->state, LINK_STATE_CONFIGURING,
> > LINK_STATE_CONFIGURING, LINK_STATE_FAILED,
On Sun, 23 Dec 2018 01:51:00 +0100 Wolfgang Walter
wrote:
> systemd-networkd from 240-1 though crashes with
>
> Assertion 'IN_SET(link->state, LINK_STATE_CONFIGURING,
> LINK_STATE_CONFIGURING, LINK_STATE_FAILED, LINK_STATE_LINGER)' failed at
> ../src/network/network/networkd-link.c:934,
On Sun, 23 Dec 2018 01:51:00 +0100 Wolfgang Walter
wrote:
> Package: udev
> Version: 240-1
> Severity: important
>
> After upgrading from 239-15 to 240-1 or higher my network setup breaks.
>
> The breakage is similar to the last one I reported (bug #904198) though
> different in detail.
>
>
Package: udev
Version: 240-1
Severity: important
After upgrading from 239-15 to 240-1 or higher my network setup breaks.
The breakage is similar to the last one I reported (bug #904198) though
different in detail.
This times all my vlan-devices on a physical device netint are first renamed to
13 matches
Mail list logo
