[Bug 982991] New: biosdevname fails to set interface name in dom0
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=982991
Bug ID: 982991
Summary: biosdevname fails to set interface name in dom0
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-maintainers@forge.provo.novell.com
Reporter: ohering@suse.com
QA Contact: qa-bugs@suse.de
Found By: ---
Blocker: ---
Dell Optiplex 980.
Since a few weeks biosdevname fails to name the interface 'em1'. Instead the
onboard network is named 'eno1'. As a result the bridge does not start and the
system is unreachable.
dom0:
root@optiplex:~ # ip a
1: lo:
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=982991
http://bugzilla.suse.com/show_bug.cgi?id=982991#c1
--- Comment #1 from Olaf Hering
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=982991
http://bugzilla.suse.com/show_bug.cgi?id=982991#c3
--- Comment #3 from Dr. Werner Fink
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=982991
http://bugzilla.suse.com/show_bug.cgi?id=982991#c4
--- Comment #4 from Olaf Hering
Created attachment 679526 [details] bug982991.tar.xz
With modified udev rule to run biosdevname via strace. Not sure where em1 is actually coming from.
In dom0 the included dmidecode can not read from /dev/mem, and as a result there is no info about onboard devices. Since this worked with xenlinux based kernels its a regression. Its also reported as bug#974257 -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=982991
http://bugzilla.suse.com/show_bug.cgi?id=982991#c5
Takashi Iwai
(In reply to Olaf Hering from comment #1)
Created attachment 679526 [details] bug982991.tar.xz
With modified udev rule to run biosdevname via strace. Not sure where em1 is actually coming from.
In dom0 the included dmidecode can not read from /dev/mem, and as a result there is no info about onboard devices. Since this worked with xenlinux based kernels its a regression. Its also reported as bug#974257
Ah, I see. Then this is due to your patch patches.suse/xen-pv-devmem_is_allowed.patch, isn't it? Don't you have a kernel message indicating the invalid /dev/mem access? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=982991
http://bugzilla.suse.com/show_bug.cgi?id=982991#c6
--- Comment #6 from Olaf Hering
Ah, I see. Then this is due to your patch patches.suse/xen-pv-devmem_is_allowed.patch, isn't it?
This change is only for domU, at least its supposed to affect only domU.
Don't you have a kernel message indicating the invalid /dev/mem access?
I have to check, likely not. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=982991
http://bugzilla.suse.com/show_bug.cgi?id=982991#c7
Olaf Hering
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=982991
http://bugzilla.suse.com/show_bug.cgi?id=982991#c8
Olaf Hering
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=982991
http://bugzilla.suse.com/show_bug.cgi?id=982991#c9
--- Comment #9 from Olaf Hering
participants (1)
-
bugzilla_noreply@novell.com