https://bugzilla.novell.com/show_bug.cgi?id=415034 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c2 --- Comment #2 from Thomas Renninger 2008-08-06 07:10:58 MDT --- Created an attachment (id=232041) --> (https://bugzilla.novell.com/attachment.cgi?id=232041) Yast2 logs after doing "ethtool eth0" and "ethtool eth1", entering yast network module then showed that one device has a link (correct) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c4 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|trenn@novell.com | --- Comment #4 from Thomas Renninger 2008-08-06 08:13:08 MDT --- yast2-network-2.17.14-2 Something still seems to not work. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c6 --- Comment #6 from Michal Zugec 2008-08-14 04:22:03 MDT --- trying to reproduce -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c8 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|trenn@novell.com | --- Comment #8 from Thomas Renninger 2008-08-14 09:06:19 MDT --- This was not Alpha1, but a test build afterwards coolo asked us to test. Let's see if things change in Alpha2, if not we have to increase severity again as we have to set up every machine by hand. The tested built is: /mounts/dist/machcd2/CDs/openSUSE-11.1-Alpha1plus-DVD-x86_64-Build0016/DVD1/ I'll attach some screenshots. You still may want to log into *adalid*. It's freshly installed -> therefore network is broken and you have to log in via serial console: ssh root@sconsole1 cscreen -> choose adalid -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c10 --- Comment #10 from Thomas Renninger 2008-08-14 09:09:47 MDT --- Created an attachment (id=233489) --> (https://bugzilla.novell.com/attachment.cgi?id=233489) Extra packages needed for installation cannot be installed -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c12 --- Comment #12 from Thomas Renninger 2008-08-14 09:11:35 MDT --- Created an attachment (id=233491) --> (https://bugzilla.novell.com/attachment.cgi?id=233491) And here we have to break our automated installation... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c14 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Blocker Status|NEEDINFO |NEW Info Provider|trenn@novell.com | --- Comment #14 from Thomas Renninger 2008-08-20 11:30:35 MDT --- This can still be reproduced on Alpha2. Adalid's network now got set up by hand. This might not be a Yast, but a ethtool problem. This should be found out first... How does Yast find out whether a network cable is plugged in and the link is active? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c16 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bgeuken@novell.com, kkeil@novell.com --- Comment #16 from Thomas Renninger 2008-09-01 08:14:09 MDT --- Hi Karsten, this is the bug where I expect that network link detection does not work. Machines that should for now be affected: *adalid*, *field*. According to Karsten one cannot really trust /sys/class/net/*/carrier or there may be delay issues (let the network driver give some more time to detect a link?). Bjorn is playing a bit with it on adalid (go ahead and double check on *field* -> same driver? same problem? ...) BTW: We also saw problems with ethtool and therefore are now activating network devices via ifup and then use ethtool to detect the link. I could imagine ethtool and /sys/../carrier link detection are rather similar/same? Then yast problaby also needs a workaround like activate network cards first? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User kkeil@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c18 Karsten Keil changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|kkeil@novell.com | --- Comment #18 from Karsten Keil 2008-09-01 09:16:09 MDT --- This seems to be normal as long the interface was not brought in up state: gw:/usr/src/linux # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:08:54:53:FD:03 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:221 Base address:0xa000 gw:/usr/src/linux # cat /sys/class/net/eth0/carrier cat: /sys/class/net/eth0/carrier: Invalid argument gw:/usr/src/linux # ifconfig eth0 up gw:/usr/src/linux # cat /sys/class/net/eth0/carrier 0 ifconfig eth0 down gw:/usr/src/linux # cat /sys/class/net/eth0/carrier cat: /sys/class/net/eth0/carrier: Invalid argument -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c20 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |okir@novell.com, ksievers@novell.com Info Provider|mzugec@novell.com |okir@novell.com --- Comment #20 from Thomas Renninger 2008-09-02 05:38:24 MDT --- Hmm, I mean how long should Yast wait... IMO this should still be solved properly in the kernel. IMO the sysfs file access on carrier should block if there is a detection in progress, something like: 1. I do not know anything about network layer 2. I didn't find and search for the real carrier sysfs method But could something like this be the real solution?: static ssize_t carrier_show(struct class *cls, char *buf) { unsigned long timeout = jiffies + HZ * 5; /* 5s */ while (netif_carrier_check(cxy->dev)) && timeout > jiffies) { /* I found netif_carrier_ok, netif_carrier_on and netif_carrier_off... NIC link detection in progress... /* cond_resched(); } return sprintf(buf, "%d", netif_carrier_ok(xy->dev)); } Two problems I am not sure: - Is this allowed in a sysfs read at all, Kay? - The netif_carrier_check(xy->dev) is probably hard to impelement? Maybe it could be done for the tg3 only for now? Just an idea, but solving/workarounding this in Yast is probably really ugly: Michal just confirmed: Waiting longer would block the whole application, not a real solution. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User kkeil@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c22 --- Comment #22 from Karsten Keil 2008-09-02 06:21:08 MDT --- No that would be a bad idea. The driver cannot make a difference between "no connection" and "carrier detection in progress", so it would wait forever, if no cable is connected. And the testloop from comment #19 is wrong, it restarts carrier detection in every loop, note "ifconfig down" is the same like pulling the cable. The important things are: YaST should not access /sys/class/net/ethX/carrier before ifconfig up was done, this would cause an error, note on some devices a ifconfig up does not happen immediately in the driver, it maybe delayed until the driver thread is running again. You can examine /sys/class/net/ethX/flags, Bit0 shows up/down status. If it read 0 for carrier it should retry, at least 3 seconds, but some cards (and switches) maybe need more time. One idea would be to do ifconfig up on all found interfaces early as possible, do something else and then test carrier state. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c24 --- Comment #24 from Thomas Renninger 2008-09-02 06:40:03 MDT ---

You can examine /sys/class/net/ethX/flags, Bit0 shows up/down status One second.., It's says connected :)

cat /sys/class/net/eth1/flags 0x1003 linux:~ # cat /sys/class/net/eth0/flags 0x1002 So they should use /sys/class/net/ethX/flags instead of carrier? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c26 --- Comment #26 from Thomas Renninger 2008-09-02 07:39:10 MDT --- Some workaround ideas: 1) ifup all the network interfaces by another program ealier on 2nd stage install/setup boot. Is not nice, because the yast lan module will still be broken stand alone 2) Wait the same amount as currently if one or more carrier files show 1 -> link detected. It is then expect that: a) We have something to use for installation -> not that bad if another link is not detected. Also cards of the same type should be ready. b) If no link is detected at all, at least wait 5 secs (should not be that often). 3) Re-evaluate carrier link after Yast lan is fully started and adjust things to the user -> Probably very hard to implement in Yast? Best would be 2+3, this would be fully satisfactoring, but 3 may not be possible as Yast could make assumptions displaying things on the result of the detection? I am off from discussion. I do not know enough in this area..., just some ideas. But it seems, beside that our auto-installation does not work on several systems, we hit a sever bug here (especially Karsten's power saving assumptions make me nervous, that would mean that link detection time could take even longer in cards upcoming in the future if they take more care about power consumption?) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=415034 User okir@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=415034#c29 --- Comment #29 from Olaf Kirch 2008-09-03 09:46:05 MDT --- Is this documented in some prominent place in the autoyast documentation? -- 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.