Bug#684766: persistent-net-generator broken on s390(x)

2012-08-14 Thread Philipp Kern
On Mon, Aug 13, 2012 at 06:49:41PM +0200, Marco d'Itri wrote: > On Aug 13, Philipp Kern wrote: > > Marco, could you come up with a fix that rearranges the dev_id properly so > > that > > it's not added to the matching rules for ccwgroup devices? The only > > "solution" > Setting ENV{MATCHDEVID}=

Bug#684766: persistent-net-generator broken on s390(x)

2012-08-13 Thread Philipp Kern
On Mon, Aug 13, 2012 at 06:49:41PM +0200, Marco d'Itri wrote: > On Aug 13, Philipp Kern wrote: > > Marco, could you come up with a fix that rearranges the dev_id properly so > > that > > it's not added to the matching rules for ccwgroup devices? The only > > "solution" > Setting ENV{MATCHDEVID}=

Bug#684766: persistent-net-generator broken on s390(x)

2012-08-13 Thread Marco d'Itri
On Aug 13, Philipp Kern wrote: > Marco, could you come up with a fix that rearranges the dev_id properly so > that > it's not added to the matching rules for ccwgroup devices? The only "solution" Setting ENV{MATCHDEVID}="" in the rule should be enough. > so far for squeeze and wheezy is to dele

Bug#684766: persistent-net-generator broken on s390(x)

2012-08-13 Thread Philipp Kern
Package: udev Version: 175-3.1 Severity: important The network devices on s390(x) seem to increase their dev_id by one on every reboot. Hence we get something like this with a new device coming up whenever the VM is rebooted: | # S/390 device at 0.0.0300 (qeth) | SUBSYSTEM=="net", ACTION=="add"