June 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 786318] New: mkinitrd inefficiently called multiple times per updates session
by bugzilla_noreply＠novell.com 06 Jun '14

06 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=786318 https://bugzilla.novell.com/show_bug.cgi?id=786318#c0 Summary: mkinitrd inefficiently called multiple times per updates session Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: PC OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=510522) --> (http://bugzilla.novell.com/attachment.cgi?id=510522) 12.2 zypp history mailing list thread starter: http://lists.opensuse.org/opensuse-kernel/2012-10/msg00048.html Each of the following packages triggered mkinitrd to build a new initrd for each installed kernel: mkinitrd udev mdadm lvm2 multipath-tools to reproduce: 1-zypper up or zypper dup where more than a few basesystem packages are updated actual behavior: 1-mkinitrd is called to product a new initrd for each installed kernel each time a package is installed that affects what goes into an initrd expected behavior: 1-mkinitrd is called no more than once per zypper dup or zypper up -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 30

[Bug 881383] New: plasma-mediacenter draws in nepomuk again when in KDE 13.1 and with baloo running.
by bugzilla_noreply＠novell.com 06 Jun '14

06 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881383 https://bugzilla.novell.com/show_bug.cgi?id=881383#c0 Summary: plasma-mediacenter draws in nepomuk again when in KDE 13.1 and with baloo running. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: stakanov(a)freenet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 When you try to install plasma-mediacenter it draws the nepomuk packages. For the newest KDE it should instead depend on baloo. This may be because the support of baloo is yet not done. Reproducible: Always Steps to Reproduce: 1.go to yast 2.install plasma-mediacenter 3.nepomuk-base package is drawn in although you have 4.13.1 without nepomuk installed. Actual Results: nepomuck package installs as dependency Expected Results: package should for 4.13.1 depend on baloo. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 872560] New: sdb reports error "WARN: Servant for pcmk has terminated" every six seconds
by bugzilla_noreply＠novell.com 06 Jun '14

06 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=872560 https://bugzilla.novell.com/show_bug.cgi?id=872560#c0 Summary: sdb reports error "WARN: Servant for pcmk has terminated" every six seconds Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: High Availability AssignedTo: lmb(a)suse.com ReportedBy: chapan(a)milwaukee.gov QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.154 Safari/537.36 We are using a resource 'external/sbd' on our cluster. Every six seconds the following error messages are logged: 2014-04-08T09:11:22.539122-05:00 ftp1 sbd: [7779]: info: Monitoring Pacemaker health 2014-04-08T09:11:22.551392-05:00 ftp1 sbd: [1925]: WARN: Servant for pcmk (pid: 7779) has terminated 2014-04-08T09:11:28.569978-05:00 ftp1 sbd: [7922]: info: Monitoring Pacemaker health 2014-04-08T09:11:28.582381-05:00 ftp1 sbd: [1925]: WARN: Servant for pcmk (pid: 7922) has terminated 2014-04-08T09:11:34.601031-05:00 ftp1 sbd: [7944]: info: Monitoring Pacemaker health 2014-04-08T09:11:34.612901-05:00 ftp1 sbd: [1925]: WARN: Servant for pcmk (pid: 7944) has terminated 2 Reproducible: Always Steps to Reproduce: 1.Define a primitive stonith->external/sbd 2.Start the cluster and the errors start appearing. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 779434] New: On shutdown/reboot "Could not unmount /var: Device or resource busy"
by bugzilla_noreply＠novell.com 06 Jun '14

06 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=779434 https://bugzilla.novell.com/show_bug.cgi?id=779434#c0 Summary: On shutdown/reboot "Could not unmount /var: Device or resource busy" Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alessandro.sturniolo(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=504959) --> (http://bugzilla.novell.com/attachment.cgi?id=504959) Shutdown on workstation User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 If the system have a separate /var on another partition/disk, on shutdown it was unable to clean umount /var (because, I suppose, /var/run take it busy). I've this behaviour in my workstation and I've replicated it on a VirtualBox virtual machine. On my workstation, as side effects of the more complex partition layout (2 RAID 1 SSD disk as /, 3 RAID 5 HDD with LVM with /home /root /var /tmp dirs binded in /), this cause filesystem corruption at every reboot/shutdown. Actually, as a workaround to not corrupt more over my filesystem, I logout from desktop environment, init 1, stop manually as more service as I can, remount all filesystems read-only and then poweroff. My workstation fstab: UUID=3d1d8188-7413-4f89-8dce-47b9c38ab328 swap swap defaults 0 0 UUID=46bf26d8-ffe7-44c8-ad3b-90269d194bd3 / ext4 acl,user_xattr,relatime,discard 1 1 UUID=9a0cc638-83d7-43da-9b38-8d0f4e5af01a /mnt/VolGroup00-LogVol01 ext4 acl,user_xattr,relatime 1 2 /mnt/VolGroup00-LogVol01/var /var bind defaults,bind 0 0 /mnt/VolGroup00-LogVol01/tmp /tmp bind defaults,bind 0 0 /mnt/VolGroup00-LogVol01/root /root bind defaults,bind 0 0 /mnt/VolGroup00-LogVol01/home /home bind defaults,bind 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 The fstab of the fresh installed virtual machine: UUID=76f63653-7371-4b84-b7f6-ce88097da2a5 swap swap defaults 0 0 UUID=784906ae-2c06-4fc6-86fa-0b4702181c0a / ext4 acl,user_xattr 1 1 UUID=0187604f-2470-41be-be9b-2de2763ca984 /boot ext4 acl,user_xattr 1 2 UUID=6de41ea6-489e-48cd-9b3c-a007ac33d860 /home ext4 acl,user_xattr 1 2 UUID=9871a843-2fea-4909-b4d3-be61ccc8a785 /var ext4 acl,user_xattr 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 Reproducible: Always Steps to Reproduce: 1. Install a fresh machine/virtual machine. 2. Restart/Shutdown and watch the system messages. Actual Results: On shutdown/reboot: On Workstation (/var /tmp /home /root binded to /): Could not unmount /var: Device or resource busy Not all file systems unmounted, 1 left. Detaching DM devices. Could not delete dm /dv/dm-0: Device or resource busy Not all DM devices detached, 1 left. Too many iterations, giving up. On Virtual Machine (slightly different file systems layout): Could not unmount /var: Device or resource busy Expected Results: Clean unmounting and clean shutdown/reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 13

[Bug 880633] New: xdm update restarts gdm and X session
by bugzilla_noreply＠novell.com 06 Jun '14

06 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=880633 https://bugzilla.novell.com/show_bug.cgi?id=880633#c0 Summary: xdm update restarts gdm and X session Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lchiquitto(a)suse.com QAContact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com, werner(a)suse.com Found By: --- Blocker: --- X session restarted during 'zypper up' today on my Factory installation. How to reproduce: zypper in -f xdm. And I'm not even using xdm. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 881722] New: Kaffeine dvb-t support broken. Seems to be connected to intel i965 video driver
by bugzilla_noreply＠novell.com 06 Jun '14

06 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881722 https://bugzilla.novell.com/show_bug.cgi?id=881722#c0 Summary: Kaffeine dvb-t support broken. Seems to be connected to intel i965 video driver Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: stakanov(a)freenet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) konqueror/4.13.1 Safari/537.21 This is a Lenovo X201 with 64 bit opensuse and kde 13.1. DVB-t device tried are Zaapa Realtek based dvb-t stick and a Hauppauge Nova-TD (diversity is working, senders are captured and reconginzed, video description of the running programm is charged. But.... Launching kaffeine with whatever dvb-t usb key (like hauppauge - broadcom based or Realtek based ones) does result in a short picture only of the tv-programme, the sound goes on for about 30 sec or so. Then all blocks. Previously the function worked. I haven't seen an update of the intel video driver but maybe this is related to it because when launching from terminal you get: kaffeine Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) Failed to open VDPAU backend libvdpau_nvidia.so: impossibile aprire il file oggetto condiviso: File o directory non esistente vo_vdpau: Can't create vdp device : No vdpau implementation. libva info: VA-API version 0.34.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_34 libva info: va_openDriver() returns 0 user@mypc:~> X Error: BadValue (integer parameter out of range for operation) 2 Major opcode: 12 (X_ConfigureWindow) Resource id: 0x0 net_buf_ctrl: dvbspeed mode net_buf_ctrl: prebuffering... net_buf_ctrl: dvbspeed OFF net_buf_ctrl: dvbspeed mode net_buf_ctrl: dvbspeed OFF net_buf_ctrl: dvbspeed mode net_buf_ctrl: prebuffering... net_buf_ctrl: dvbspeed 100% @ video 2040 ms 116 buffers libva info: VA-API version 0.34.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_34 libva info: va_openDriver() returns 0 net_buf_ctrl: dvbspeed 100.5% @ video 3080 ms 173 buffers Reproducible: Always Steps to Reproduce: 1. open kaffeine 2. select dvt-t device 3. program is shown as one picture only, sound goes 30 secs. Then all is blocked. Actual Results: kaffeine freezes with dvb-t. You have to get out of kaffeine, wait a sec and get in again to be able to open it again. Expected Results: I know that the developpement of KDE has been discontinued (I do not comment on the modalities) but as I haven't found any substitute application working for dvb-t: kaffeine should still be able to work with mainstream functions as long as a kde substitute has not been developped (means completely working developped). on the very system xbmc from packman does not start either with following error in terminal: xbmc sh: xdpyinfo: command not found Traceback (most recent call last): File "/usr/share/xbmc/FEH.py", line 175, in <module> if (badColorDepth()): File "/usr/share/xbmc/FEH.py", line 154, in badColorDepth return bitDepth UnboundLocalError: local variable 'bitDepth' referenced before assignment Maybe this is connected, maybe not. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 881679] New: sysfs group ffffffff81eaba60 not found for kobject 'parport0'
by bugzilla_noreply＠novell.com 06 Jun '14

06 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881679 https://bugzilla.novell.com/show_bug.cgi?id=881679#c0 Summary: sysfs group ffffffff81eaba60 not found for kobject 'parport0' Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: mpluskal(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- When running hwinfo on recent factory, following appears in dmesg: [ 480.868613] ------------[ cut here ]------------ [ 480.868625] WARNING: CPU: 0 PID: 1764 at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.15.rc7/linux-3.15-rc7/fs/sysfs/group.c:219 device_del+0x40/0x1b0() [ 480.868627] sysfs group ffffffff81eaba60 not found for kobject 'parport0' [ 480.868629] Modules linked in: parport_pc(-) rpcsec_gss_krb5 auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd sunrpc fscache bridge stp llc iscsi_ibft iscsi_boot_sysfs af_packet gpio_ich iTCO_wdt iTCO_vendor_support ppdev snd_hda_codec_idt snd_hda_codec_generic coretemp pcspkr serio_raw i2c_i801 lpc_ich mfd_core snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer tpm_tis tpm snd parport soundcore mei_me shpchp mei acpi_cpufreq processor btrfs xor raid6_pq ata_generic sr_mod cdrom firewire_ohci firewire_core crc_itu_t nouveau pata_marvell video mxm_wmi wmi i2c_algo_bit drm_kms_helper ttm e1000e drm ptp pps_core button dm_mirror dm_region_hash dm_log dm_mod sg [last unloaded: lp] [ 480.868689] CPU: 0 PID: 1764 Comm: rmmod Not tainted 3.15.0-rc7-1-desktop #1 [ 480.868691] Hardware name: /DG965WH, BIOS MQ96510J.86A.1754.2008.1117.0002 11/17/2008 [ 480.868693] 0000000000000009 ffffffff81603600 ffff8800c2213de8 ffffffff810582f7 [ 480.868696] ffff8800c624bc00 ffff8800c2213e38 ffff88021dc9ea00 ffff88021e7e2810 [ 480.868699] 00000000024081d0 ffffffff8105835c ffffffff81a2fe68 0000000000000028 [ 480.868702] Call Trace: [ 480.868716] [<ffffffff81004b7e>] dump_trace+0x8e/0x350 [ 480.868720] [<ffffffff81004ee6>] show_stack_log_lvl+0xa6/0x190 [ 480.868724] [<ffffffff81006371>] show_stack+0x21/0x50 [ 480.868729] [<ffffffff81603600>] dump_stack+0x49/0x6a [ 480.868735] [<ffffffff810582f7>] warn_slowpath_common+0x77/0x90 [ 480.868739] [<ffffffff8105835c>] warn_slowpath_fmt+0x4c/0x50 [ 480.868743] [<ffffffff81403200>] device_del+0x40/0x1b0 [ 480.868747] [<ffffffff8140338a>] device_unregister+0x1a/0x60 [ 480.868750] [<ffffffff8140343a>] device_destroy+0x3a/0x40 [ 480.868758] [<ffffffffa0414546>] parport_remove_port+0x36/0x180 [parport] [ 480.868770] [<ffffffffa06d0bc5>] parport_pc_unregister_port+0x25/0x1a0 [parport_pc] [ 480.868782] [<ffffffffa06d407e>] parport_pc_exit+0x71/0xff3 [parport_pc] [ 480.868790] [<ffffffff810d0fa4>] SyS_delete_module+0x154/0x1f0 [ 480.868796] [<ffffffff816116ed>] system_call_fastpath+0x1a/0x1f [ 480.868802] [<00007f3d8d937047>] 0x7f3d8d937046 [ 480.868804] ---[ end trace 9f24dc682fb2d1b9 ]--- [ 480.887650] parport_pc 00:07: activated [ 480.887657] parport_pc 00:07: reported by Plug and Play ACPI [ 480.887714] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [ 480.977933] lp0: using parport0 (interrupt-driven). [ 481.004338] ppa: Version 2.07 (for Linux 2.4.x) [ 481.034148] st: Version 20101219, fixed bufsize 32768, s/g segs 256 [ 481.210758] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 481.210762] EDD information not available. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 858840] New: Kernel update complexity (excess use of mkinitrd); extended "unsafe" period
by bugzilla_noreply＠novell.com 06 Jun '14

06 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=858840 https://bugzilla.novell.com/show_bug.cgi?id=858840#c0 Summary: Kernel update complexity (excess use of mkinitrd); extended "unsafe" period Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:26.0) Gecko/20100101 Firefox/26.0 For systems where more than one kernel (n kernels) is installed (e.g. multiple versions or flavors), mkinitrd creates an initrd for each. So far, so good. Unfortunately a single "kernel" consists of two or more packages which are installed in a somewhat loose order. Each %post script of a kernel package calls mkinitrd, which in turn, re-creates the initrds for each kernel found. Despite the fact that the "useless temporary" initrd updates waste time and CPU cycles, there is a danger associated with this: If you update your kernel (say from 2.6.x to 3.0.y), the first mkinitrd of the first kernel package created an initrd that does not fit to the rest of the kernel. If the system crashes or the power goes out (or a cluster node fences the server), the system may be unbootable (modules in initrd not matching the kernel image). Reproducible: Always Steps to Reproduce: 1. Watch kernel updates Actual Results: Multiple mkinitd calls are observerd Expected Results: mkinitrd should be deferred until all the kernel-related updates are on disk. For example: I installed updates for kernel and multipath. multipath-update alone built the initrd several times: 2014-01-15 10:41:51 <1> pc(10330) [zypp] RpmDb.cc(doInstallPackage):1849 RpmDb::installPackage(/var/cache/zypp/packages/repo-update/i586/multipath-tools-0.4.9-7.5.1.i586.rpm,0x0000000c) [...] 2014-01-15 10:52:46 <1> pc(10330) [zypp] RpmDb.cc(doInstallPackage):1849 RpmDb::installPackage(/var/cache/zypp/packages/repo-update/i586/parted-2.4-30.4.1.i586.rpm,0x0000000c) That is 11 minutes to wait just for the update of multipath-tools! Each of my 3 kernels got its initrd build at least two times during that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11

[Bug 861608] New: Dovecot error on deleting mail
by bugzilla_noreply＠novell.com 06 Jun '14

06 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=861608 https://bugzilla.novell.com/show_bug.cgi?id=861608#c0 Summary: Dovecot error on deleting mail Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: james.knott(a)rogers.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 I recently did a fresh install of openSUSE 13.1 on my main computer, where I have been running Dovecot for years. Since then, I have been getting occasional errors when deleting messages. After clearing the error message, the message I had deleted reappears. I did not experience this on this computer when I had updated 12.3 to 13.1. Here's the error message. "Alert The current operation on 'Inbox' did not succeed. The mail server for account Rogers responded: [SERVERBUG] internal error occurred. Refer to server log for more information." According to a Google search, this appears to be a server related problem. I normally read my email with Seamonkey, on the same computer as the server. I have not seen this problem on other computers or devices, but I do almost all my email on this one computer. Reproducible: Sometimes Steps to Reproduce: 1.Delete a message 2.Error message pops up, clear message 3.Deleted message reappears. Actual Results: On occasion, a deleted message will reappear. Expected Results: Message should always be deleted without issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 849749] New: 13.1/post-RC2 (via dup) x64 network devices on pcie bus not persistently named: enp3s0 becomes enp6s0 with adding another pcie card?
by bugzilla_noreply＠novell.com 06 Jun '14

06 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=849749 https://bugzilla.novell.com/show_bug.cgi?id=849749#c0 Summary: 13.1/post-RC2 (via dup) x64 network devices on pcie bus not persistently named: enp3s0 becomes enp6s0 with adding another pcie card? Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: abittner(a)abittner.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 I am not sure about these new namings of ethernet cards any more with the new kernel or systemd or whoever is in charge here, but an onboard realtek ethernet port was intially already configured as dhcp just fine. then i added another realtek pcie network card later on, and the system then had no working ethernet configuration any more suddenly and the initial onboard chip that used to be named enp3s0 is now being listed as enp6s0 and needed to be set new as dhcp, and the additional pcie slot card (dual nic) is being named as enp4s0 and enp5s0 (no configs set yet) this is odd. am I misunderstand the new naming scheme? Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: current situation with onboard nic and pcie-dualnic from dmesg: [ 5.654437] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 5.655012] r8169 0000:04:00.0 eth0: RTL8168evl/8111evl at 0xffffc90001948000, 00:0a:cd:21:e3:e5, XID 0c900800 IRQ 57 [ 5.655014] r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [ 5.655035] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 5.655360] r8169 0000:05:00.0 eth1: RTL8168evl/8111evl at 0xffffc9000194a000, 00:0a:cd:21:e3:e6, XID 0c900800 IRQ 58 [ 5.655361] r8169 0000:05:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko] [ 5.655368] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 5.657199] r8169 0000:06:00.0 eth2: RTL8168g/8111g at 0xffffc90001974000, d8:50:e6:4c:08:d4, XID 0c000800 IRQ 59 [ 5.657202] r8169 0000:06:00.0 eth2: jumbo features [frames: 9200 bytes, tx checksumming: ko] [ 5.706037] systemd-udevd[309]: renamed network interface eth2 to enp6s0 [ 6.409314] systemd-udevd[306]: renamed network interface eth0 to enp4s0 [ 6.415252] systemd-udevd[307]: renamed network interface eth1 to enp5s0 but my sysconfig/network/ directory shows the old config file and the new config file for actually the same onboard nic device, which is odd. My understand and the documentation said that these same physical network devices and chips and ports should retain their names and not get confused and mixed and renamed back and forth any more. so what is wrong here? the onboard nic config file that got created and named initially until there was no additional pcie dual-nic card installed: -rw------- 1 root root 200 Nov 10 00:43 ifcfg-enp3s0 content: OOTPROTO='dhcp' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='RTL8111/8168B PCI Express Gigabit Ethernet controller' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' ifcfg-enp3s0 lines 1-11/11 (END) the newer config file now for the same onboard nic but now under a different name and needing to be set again: -rw-r--r-- 1 root root 200 Nov 10 12:17 ifcfg-enp6s0 content: BOOTPROTO='dhcp' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='RTL8111/8168B PCI Express Gigabit Ethernet controller' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' ifcfg-enp6s0 lines 1-11/11 (END) The pcie dual-nic card is constructed via a pci bridge as far as I understand and see on the PCB of that card: lspci: 02:00.0 PCI bridge: PLX Technology, Inc. Device 8603 (rev aa) 03:01.0 PCI bridge: PLX Technology, Inc. Device 8603 (rev aa) 03:02.0 PCI bridge: PLX Technology, Inc. Device 8603 (rev aa) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) 02:00.0 PCI bridge [0604]: PLX Technology, Inc. Device [10b5:8603] (rev aa) 03:01.0 PCI bridge [0604]: PLX Technology, Inc. Device [10b5:8603] (rev aa) 03:02.0 PCI bridge [0604]: PLX Technology, Inc. Device [10b5:8603] (rev aa) 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) 05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) 06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) +-15.0-[02-05]----00.0-[03-05]--+-01.0-[04]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller | \-02.0-[05]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller +-15.1-[06]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 17