[Bug 326376] New: DNS hangs/errors with e1000
https://bugzilla.novell.com/show_bug.cgi?id=326376 Summary: DNS hangs/errors with e1000 Product: openSUSE 10.3 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: adrian@novell.com QAContact: qa@suse.de Found By: --- I have still serious trouble with DNS using the latest kernel ("* Di Sep 18 2007" latest changelog entry). Please note that the same notebook has no trouble in 10.x network, but it has in 149.44.x network. We have seen the same problem with a workstation which got installed 10.3 snapshot from yesterday here in the 149.44. network. All 10.2 systems work still fine. -- 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=326376#c2 Karsten Keil <kkeil@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Karsten Keil <kkeil@novell.com> 2007-09-19 08:27:57 MST --- Hmm, no problems in the 10.X network but problems in 149.44 do not sound like a driver problem, but I will try to build a KMP with the old e1000 code to verify if it makes a difference. -- 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=326376 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com Status|ASSIGNED |NEEDINFO Info Provider| |adrian@novell.com Flag| |SHIP_STOPPER- -- 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=326376#c4 --- Comment #4 from Christopher Stender <cstender@novell.com> 2007-09-19 16:05:20 MST --- We also had some trouble with a Lenovo T61 and RC1 today. Ping on a IP works, but dns doesn't (same network as every day and correct dns settings in /etc/resolv.conf). -- 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=326376#c5 --- Comment #5 from Adrian Schröter <adrian@novell.com> 2007-09-20 02:20:30 MST --- Sorry, I told you some crap. It seems only one of the broken systems is using e1000 (the workstation), my notebook uses the tg3 kernel module, but it has the same problems .... (maybe this is more a glibc problem ?) I will check if I can test your module with the workstation, if makes a difference. -- 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=326376#c6 --- Comment #6 from Karsten Keil <kkeil@novell.com> 2007-09-20 03:59:38 MST --- Not needed I think. Hmm, I had a similar issue with my notebook during installing Beta3 (sky2 driver). The install was direct from a burned DVD and then the network test didn't work. All test on the console shows, that networking itself works (e.g. ssh), but DNS not, /etc/resolv.conf was OK and the request reached the nameserver machine, but didn't generate a response. Then I did a reboot and the issue was not longer reproducible. So I would say it has nothing todo with the card driver. Does a machine still show this behavior, maybe the DNS packets are somehow corrupted. -- 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=326376#c7 Christoph Thiel <cthiel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cthiel@novell.com --- Comment #7 from Christoph Thiel <cthiel@novell.com> 2007-09-20 06:24:08 MST --- Were you guys using x86_64 or i386 maschines? This problem could well be related to the RC1 glibc, which is different from i386. Please test with the latests gblic from full-x86_64. It should include: Sun Sep 16 14:04:30 CEST 2007 - aj@suse.de - Install gai.conf on all archs. -- 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=326376 Christoph Thiel <cthiel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|SHIP_STOPPER- |SHIP_STOPPER+ -- 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=326376#c8 --- Comment #8 from Karsten Keil <kkeil@novell.com> 2007-09-20 06:44:07 MST --- My issue with Beta3 was on i386. -- 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=326376#c9 Adrian Schröter <adrian@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|adrian@novell.com | Summary|DNS hangs/errors with e1000 |DNS hangs/errors --- Comment #9 from Adrian Schröter <adrian@novell.com> 2007-09-20 07:18:24 MST --- I tried with Beta3 kernel on x86_64 again and it did not change the behaviour. I made some straces of ping, but they do not look helpfull to me. Any idea what else could get checked ? -- 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=326376#c10 --- Comment #10 from Karsten Keil <kkeil@novell.com> 2007-09-20 07:50:59 MST --- OK. 1. ping <ip-address> works and ping <name> not ? If yes then you could use tcpdump to look if here is any DNS activity on the interface: tcpdump -vvvv -n -i eth0 If this shows that here is a DNS request going out, but no response, it would be great if you find sombody with root access to the name server, who can run tcpdump or wireshark on it, to see if the request go to this machine and generate a response. -- 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=326376#c11 Adrian Schröter <adrian@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wwilde@novell.com, deckel@novell.com, | |snagel@novell.com, ro@novell.com --- Comment #11 from Adrian Schröter <adrian@novell.com> 2007-09-20 07:53:35 MST --- Another observation, I had two ping processes running, one to the 10.10.x network and one to the 149.x.x.x network. Only the 10.10.x ping did hang when I have the problems and continued later. So this points to a general network problem. But the question is why are only the two 10.3 system affected but non of the 10.2 systems in the room ? /etc/nsswitch.conf got configured to use only files and dns resolvements. avahi was not running (in fact both daemons do crash anyway on boot, so they have no effect). Vacation-Deckel, do you have any hint ? -- 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=326376#c13 --- Comment #13 from Adrian Schröter <adrian@novell.com> 2007-09-20 08:24:55 MST --- The problem seems to be more low level. I observed meanwhile also hanging of pings to both networks (to 149.44.170.254 and 10.10.0.10). In general, I would say it is a generic broken network, but only 10.3 hosts seems to be affected and I hear about similar problems from other people in other networks (ro and thoenig both in 10.10.x network, but all with different hardware). The hanging DNS is most likely only a following problem, because no traffic wents over the wire at all. -- 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=326376#c14 --- Comment #14 from Christian Deckelmann <deckel@novell.com> 2007-09-20 08:42:50 MST --- Unlikely for being a general network problem when only 10.3 hosts are affected. To rule out the network you could try to ping another host which is as well connected to the same local switch in your office. Keep also in mind that ping tries to resolve the name when using an IP address as ping target. Does "ping -n" 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=326376#c15 Karsten Keil <kkeil@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kkeil@novell.com |kernel-maintainers@forge.provo.novell.com Status|ASSIGNED |NEW --- Comment #15 from Karsten Keil <kkeil@novell.com> 2007-09-20 09:55:03 MST --- So I installed now RC1 and run into this problem again, HW is i386 with sky2. This time the network test works, it also downloads the release notes, but after install was done (without additional reboot) ping <name> doesn't work, but ping -n <IP> does. nslookup runs into a timeout. Running tcpdump on the nameserver shows, that the packets have a wrong UDP checksum: 17:21:36.905845 arp who-has 10.23.200.9 tell 10.23.200.111 17:21:36.905933 arp reply 10.23.200.9 is-at 0:50:ba:fb:71:36 17:22:24.415433 arp who-has 10.23.200.9 tell 10.23.200.111 17:22:24.415493 arp reply 10.23.200.9 is-at 0:50:ba:fb:71:36 17:22:43.774113 10.23.200.111.32776 > 10.23.200.9.53: [bad udp cksum cd54!] 55913+ A? nb-tosh.kke.suse.de. (37) (DF) (ttl 64, id 38702, len 65) 17:22:48.770692 10.23.200.111.32776 > 10.23.200.9.53: [bad udp cksum cd54!] 55913+ A? nb-tosh.kke.suse.de. (37) (DF) (ttl 64, id 38703, len 65) 17:22:48.771890 10.23.200.111.32777 > 10.23.200.9.53: [bad udp cksum 7d09!] 9657+ A? nb-tosh.kke.suse.de. (37) (DF) (ttl 64, id 39952, len 65) 17:22:53.770563 10.23.200.111.32777 > 10.23.200.9.53: [bad udp cksum 7d09!] 9657+ A? nb-tosh.kke.suse.de. (37) (DF) (ttl 64, id 39953, len 65) 17:23:34.103527 10.23.200.111.32777 > 10.23.200.9.53: [bad udp cksum 4cdc!] 52762+ A? pingi.kke.suse.de. (35) (DF) (ttl 64, id 0, len 63) 17:23:39.101547 arp who-has 10.23.200.9 tell 10.23.200.111 17:23:39.101627 arp reply 10.23.200.9 is-at 0:50:ba:fb:71:36 17:23:39.105677 10.23.200.111.32777 > 10.23.200.9.53: [bad udp cksum 4cdc!] 52762+ A? pingi.kke.suse.de. (35) (DF) (ttl 64, id 0, len 63) 17:23:44.105783 10.23.200.111.32777 > 10.23.200.9.53: [bad udp cksum 4cdc!] 52762+ A? pingi.kke.suse.de. (35) (DF) (ttl 64, id 0, len 63) A tcpdump on the notebook also shows UDP checksum errors 17:36:40.008472 arp who-has 10.23.200.9 tell 10.23.200.111 17:36:40.008785 arp reply 10.23.200.9 is-at 00:50:ba:fb:71:36 17:36:40.008798 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 63) 10.23.200.111.32777 > 10.23.200.9.53: [bad udp cksum e3b3!] 63107+ A? pingi.kke.suse.de. (35) 17:36:45.008919 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 63) 10.23.200.111.32777 > 10.23.200.9.53: [bad udp cksum e3b3!] 63107+ A? pingi.kke.suse.de. (35) 17:36:50.009197 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 63) 10.23.200.111.32777 > 10.23.200.9.53: [bad udp cksum e3b3!] 63107+ A? pingi.kke.suse.de. (35) Strange: After some minutes (writing this down), it works, without any problems, I cannot reproduce it any longer. I do not have any idea. I'm on vacation and traveling without network until Tuesday. -- 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=326376#c17 --- Comment #17 from Jiri Kosina <jkosina@novell.com> 2007-09-20 10:05:06 MST --- Is this problem also observable when using kernel-vanilla? It can be obtained from the same place as KOTD - ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/ -- 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=326376#c18 --- Comment #18 from Stephan Kulow <coolo@novell.com> 2007-09-21 02:42:52 MST --- I think this is not a ship stopper as online updates still run. No idea how they get their DNS information -- 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=326376#c19 --- Comment #19 from Adrian Schröter <adrian@novell.com> 2007-09-21 04:21:51 MST --- Well, even installation was not possible or did hang forever on one host, if you add the remote repositories. Yes, you can install also without remote repos, but I doubt that the updater would work in that case. -- 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=326376#c20 Stanislav Visnovsky <visnov@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |visnov@novell.com --- Comment #20 from Stanislav Visnovsky <visnov@novell.com> 2007-09-24 03:34:28 MST --- I was running into the problem with kernel-default-2.6.22.5-18.i586. Today morning I've updated the system via booting RC1, selecting 'Update'. Now, the network works fine. This is ThinkPad x60s (i386), e1000 driver. -- 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=326376#c21 --- Comment #21 from Stephan Kulow <coolo@novell.com> 2007-09-24 04:25:55 MST --- damn. so far this was x86_64 only -- 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=326376#c22 --- Comment #22 from Stephan Kulow <coolo@novell.com> 2007-09-24 07:59:00 MST --- OK, adrian tested vanilla kernel -> same problem. This makes it quite unlikely that it's caused by a kernel problem. But I wonder how userland can corrupt UDP packages (#15) -- 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=326376#c23 --- Comment #23 from Jiri Kosina <jkosina@novell.com> 2007-09-24 08:04:03 MST --- Adrian, did you test the kernel-vanilla package from our repositories, or did you test the snapshot from kernel.org? As you seem to be able to reproduce the problem quite well, it might be very interesting if you could try to grab the kernel.org kernel, and if the problem is not present there, we should just find and backport the proper fix, otherwise we should report the problem upstream. Thanks. -- 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=326376#c24 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|SHIP_STOPPER+ |SHIP_STOPPER- --- Comment #24 from Stephan Kulow <coolo@novell.com> 2007-09-24 09:07:39 MST --- as discussed in the exit criteria meeting: there is not enough information to mark it as SHIP_STOPPER -- 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=326376#c25 --- Comment #25 from Adrian Schröter <adrian@novell.com> 2007-09-24 09:37:24 MST --- kernel-vanilla package shows the same problems. -- 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=326376#c26 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn@novell.com, bwalle@novell.com --- Comment #26 from Thomas Renninger <trenn@novell.com> 2007-09-24 11:12:59 MST --- I also saw this with the kernel from a week ago. I now tried latest CVS snapshot with and without e1000 enhancements (v. 7.6.5) and it works with both. Maybe this already got fixed by this (the others look even more unrelated): Thu Sep 20 16:23:32 CEST 2007 - bwalle@suse.de - Update config files. Revert RTC transition for 10.3 due to problems that cannot be fixed quickly (#326490). -- 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=326376#c27 --- Comment #27 from Jiri Bohac <jbohac@novell.com> 2007-09-25 12:18:40 MST --- Can anyone experiencing this problem (Adrian, ...) please try and see (using tcpdump) what packets arrive at the nameserver, just as Karsten did? The bad UDP checksums seem to be the problem. If you don't have a nameserver where you have root access, just specify any other machine (where you do have root access) as nameserver in /etc/resolv.conf. The packets will arrive anyway, even though there will not be any chance of getting a reply ;-) I suspect some kind of checksum offloading to cause the problem. So if you see the checksum errors on the [pseudo]nameserver, please try to change the checksum offloading settings with ethtool -K ... -- 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=326376#c28 Adrian Schröter <adrian@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |cschum@novell.com --- Comment #28 from Adrian Schröter <adrian@novell.com> 2007-09-26 02:05:53 MST --- I was not able to produce broken udp packages with a different workstation in that room. I think we to check this on the real dns server. Additionally, Cornelius reported that he has the same problem also with a 10.2 installation in that room on his apple notebook on LAN. Cornelius, which netcard driver do you use ? -- 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=326376#c29 --- Comment #29 from Karsten Keil <kkeil@novell.com> 2007-09-26 05:33:39 MST --- Created an attachment (id=174823) --> (https://bugzilla.novell.com/attachment.cgi?id=174823) tcpdump dump file I installed RC1 again on my notebook and run into the issue again. This is a tcpdump file (you can process it with tcpdump -r) from the nameserver. The issue was directly after installation, also downloading the release notes doesn't work. The issue went away after I connected via ssh from a third machine. If I look at the tcpdump messages at the notebook, I always get UDP checksum errors also after the issue went away, I think because packets are captured before checksums are written. In the error case, the checksum bytes on both sides are the same, so it seems that until I connected via the ssh, the checksum was not written at all. -- 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=326376#c30 Karsten Keil <kkeil@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkeil@novell.com --- Comment #30 from Karsten Keil <kkeil@novell.com> 2007-09-27 10:26:19 MST --- I can now reproduce the issue in 75% with rcnetwork restart. Also switching TX checksum offload off with ethtool solve the problem, so it seems that this issue is specific to sky2. I opened a mainline bug for this issue now: http://bugzilla.kernel.org/show_bug.cgi?id=9089 -- 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=326376#c31 --- Comment #31 from Andreas Jaeger <aj@novell.com> 2007-09-28 02:30:36 MST --- Mainline has a bugfix at http://bugzilla.kernel.org/show_bug.cgi?id=8667 But that one is sky2 - what hardware are others are using? I only heard e1000 mentioned (note I use e1000 as well and never had such a problem) -- 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=326376#c32 --- Comment #32 from Ruediger Oertel <ro@novell.com> 2007-09-28 02:57:06 MST --- e1000 was mentioned several times comment#5 talks about tg3 -- 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=326376#c33 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|cschum@novell.com | --- Comment #33 from Stephan Kulow <coolo@novell.com> 2007-10-21 07:27:20 MST --- I don't think Cornelius can help mere, removing NEEDINFO -- 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=326376 User kkeil@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=326376#c35 Karsten Keil <kkeil@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #35 from Karsten Keil <kkeil@novell.com> 2008-01-24 06:42:43 MST --- OK, the issue which I could reproduce was fixed, but this do not explain the issues with the other drivers. Meanwhile I installed several 10.3 nodes and never run into this problem (at least 3 times the node had a e1000). So does the problem still exist (even with openSuse 11.0) ? -- 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=326376 Karsten Keil <kkeil@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |adrian@novell.com -- 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=326376 User adrian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=326376#c36 --- Comment #36 from Adrian Schröter <adrian@novell.com> 2008-01-29 22:18:34 MST --- The room where this was reproducable does not exist anymore. So I can not reproduce this anymore easily. I have also not seen the issues in our floor anymore. Dunno what changed, but I think we can close this. -- 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=326376 User kkeil@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=326376#c37 Karsten Keil <kkeil@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|adrian@novell.com | Resolution| |WORKSFORME --- Comment #37 from Karsten Keil <kkeil@novell.com> 2008-01-30 03:21:08 MST --- Yes, I think something of the network infrastructure was flaky in this room, so we cannot do so much here anymore. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com