https://bugzilla.novell.com/show_bug.cgi?id=258433 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |schwab@novell.com |screening@forge.provo.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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=258433 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |psankar@novell.com ------- Comment #2 from gregkh@novell.com 2007-03-29 11:28 MST ------- *** Bug 249255 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=258433 kern@sibbald.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kern@sibbald.com ------- Comment #4 from kern@sibbald.com 2007-04-14 15:15 MST ------- I'm experience the same problem reported here. This is a *critical* problem for a developer like myself. It would be helpful if someone would attach an exact link to this bug report pointing to a kernel that works -- I'll try to find the 10.3 Alpha kernel. In addition to the reported problem, when running gdb in many cases the message SEG FAULT will appear, gdb "exits" and I am back at a command prompt -- note, this is not my program that is getting a seg fault. Both problems happen on kernel-2.6.18.8-0.1-default Example output for problem of no symbols reported by gdb when the program *is* compiled with the same Makefiles used for debugging for years now. gdb bacula-sd GNU gdb 6.5 Copyright (C) 2006 Free Software Foundation, Inc. .. This GDB was configured as "i586-suse-linux"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run -s -f -c stored.conf Starting program: /home/kern/bacula/k/src/stored/bacula-sd -s -f -c stored.conf Failed to read a valid object file image from memory. [Thread debugging using libthread_db enabled] [New Thread -1212569904 (LWP 4867)] [New Thread -1214227568 (LWP 4874)] .. (I type a ctl=c at this point) Program received signal SIGINT, Interrupt. [Switching to Thread -1212569904 (LWP 4867)] 0xb7fc9410 in ?? () (gdb) where #0 0xb7fc9410 in ?? () #1 0xbfab1788 in ?? () #2 0x00000000 in ?? () (gdb) thread apply all bt Thread 3 (Thread -1222620272 (LWP 4875)): #0 0xb7fc9410 in ?? () #1 0xb72043a4 in ?? () #2 0x00000043 in ?? () #3 0x00000000 in ?? () Thread 1 (Thread -1212569904 (LWP 4867)): #0 0xb7fc9410 in ?? () #1 0xbfab1788 in ?? () #2 0x00000000 in ?? () (gdb) -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=258433 ------- Comment #6 from kern@sibbald.com 2007-06-01 03:26 MST ------- This major bug has been outstanding two months now, and it is still marked as NEW. Could you provide an estimate when you will release a new 10.2 kernel with this problem fixed? I saw a comment from someone at SuSE who asked why this was urgent, here is my response. I consider this a major problem, and for me it is not acceptable to be running on a git (10.3) kernel in order to debug my programs for several reasons: 1. The git kerneal is an alpha (or beta) kernel and not made to run on 10.2 2. For the above reason does not load correctly with armour probably because it needs new versions, but there is no procedure for doing this. 3. The kernel I am using 2.6.21-rc5-git13-2-default is not only alpha, but it is broken -- it does not handle opening USB ports correctly, reported in another bug (USB cameras can no longer connect) so I am forced to boot back and forth between kernels, one for debugging, one for accessing my camera. I really like your SuSE distro (switched to SuSE in Jan 2007), however this bug means your released kernel is badly broken for developers. I understand it is a pain for you guys to update kernels when you want to focus on 10.3, but if you don't quickly fix these kinds of major bugs I think you will find that some developers such as myself will move to another distro that gives a higher priority to these kinds of 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=258433#c9 Ryan Partridge changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ryan.partridge@bungeelabs.com --- Comment #9 from Ryan Partridge 2007-07-02 15:53:15 MST --- Still no update on this bug??? -- 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=258433#c11 --- Comment #11 from Petr Vanek 2007-07-04 02:59:08 MST --- hi kernel devs, I agree with Andre Klapper, it's one of the most importatnt issue I'm facing in the development now. Of course I understand there is too much work in different areas etc. etc.... But we are missing any feedback. Ok, you can say: "we will not fix it, wait for 10.3". Good - I'll find some workaround (messing my system and GPU drivers etc.). Anyway - I'd like to hear: "it will be fixed in updates after you return from vacations." cheers petr -- 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=258433#c13 --- Comment #13 from Andi Kleen 2007-07-05 05:42:40 MST --- If the debugger has problems with the vdso you can disable it with echo 0 > /proc/sys/vm/vdso_enabled Re #11: Petr, if you really need bug fixes for old versions in a specific time you'll need a support contract, sorry. For openSUSE the deal is either upgrade or wait. Re #12; USB problems: you likely need to update udev too. Good luck with Fedora, perhaps we'll see you back after their first bug. The zypp (update performance) problem is being worked on bug I agreed it's pretty bad. Hopefully 10.3 will be better though. -- 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=258433#c15 --- Comment #15 from Andi Kleen 2007-07-05 06:49:01 MST --- With disabling the vdso the original 10.2 kernel should actually 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=258433#c17 --- Comment #17 from Andre Klapper 2007-07-05 07:49:44 MST --- andi, i wonder if requesting information from your collegue andreas (who is not in the CC list but came up with the vdso stuff) would not be more sufficient? YES, this issue still exists, even if you cannot reproduce. just take a look at bugzilla.gnome.org. -- 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=258433#c19 --- Comment #19 from Andre Klapper 2007-07-05 11:14:59 MST --- andreas, ignoring bug reports by closing them does not magically make existing issues vanish. if you need more info, feel free to explicitly ask the folks here for more information and describing the steps to gather the requested 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=258433#c21 --- Comment #21 from Andi Kleen 2007-07-05 15:06:47 MST --- So far the bug is not closed yet. Yes I'm asking for a reproducible test case. Please supply one. -- 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=258433#c23 --- Comment #23 from Kern Sibbald 2007-07-05 16:07:43 MST --- I don't know what you need to reproduce it. I am running: Linux rufus 2.6.18.8-0.3-bigsmp #1 SMP Tue Apr 17 08:42:35 UTC 2007 i686 i686 i386 GNU/Linux which as far as I am aware is a perfectly stock released SuSE 10.2. I run my program under the debugger and send it a signal 11, and I get: Program received signal SIGSEGV, Segmentation fault. 0xb7f46410 in ?? () (gdb) where #0 0xb7f46410 in ?? () #1 0xbfdd5298 in ?? () #2 0x00000000 in ?? () (gdb) thread apply all bt Thread 16 (Thread -1214223472 (LWP 8592)): #0 0xb7f46410 in ?? () #1 0xb7a05ec8 in ?? () #2 0x00000013 in ?? () #3 0x00000000 in ?? () Thread 11 (Thread -1240470640 (LWP 8581)): #0 0xb7f46410 in ?? () #1 0xb60fdec8 in ?? () #2 0x00000014 in ?? () #3 0x00000000 in ?? () Thread 10 (Thread -1232077936 (LWP 8580)): #0 0xb7f46410 in ?? () #1 0x00000003 in ?? () #2 0x00000000 in ?? () Thread 8 (Thread -1248863344 (LWP 8573)): #0 0xb7f46410 in ?? () #1 0xb58fced8 in ?? () #2 0x000000de in ?? () #3 0x080bb684 in ?? () #4 0xb7ef0fab in __write_nocancel () from /lib/libpthread.so.0 #5 0x080803a6 in write_nbytes (bsock=0xb69004c0, ptr=0x80bb684 "", nbytes=222) at bnet.c:138 #6 0x080827ee in BSOCK::send (this=0xb69004c0) at bsock.c:292 #7 0x08082dd8 in BSOCK::despool (this=0xb69004c0, update_attr_spool_size=0x80783f0 , tsize=2379278) at bsock.c:518 #8 0x08078aca in commit_attribute_spool (jcr=0x80c76c8) at spool.c:636 #9 0x080530f9 in do_append_data (jcr=0x80c76c8) at append.c:334 #10 0x080674c3 in append_data_cmd (jcr=0x80c76c8) at fd_cmds.c:194 #11 0x080670b1 in do_fd_commands (jcr=0x80c76c8) at fd_cmds.c:165 #12 0x08067612 in run_job (jcr=0x80c76c8) at fd_cmds.c:128 #13 0x08067aa4 in run_cmd (jcr=0x80c76c8) at job.c:192 #14 0x08062314 in handle_connection_request (arg=0xb69004c0) at dircmd.c:224 #15 0x0809bebc in workq_server (arg=0x80b5e60) at workq.c:357 #16 0xb7eea112 in start_thread () from /lib/libpthread.so.0 #17 0xb7be02ee in clone () from /lib/libc.so.6 Thread 3 (Thread -1222616176 (LWP 8531)): #0 0xb7f46410 in ?? () #1 0xb72053a4 in ?? () #2 0x00000049 in ?? () #3 0x00000000 in ?? () Thread 1 (Thread -1213093008 (LWP 8526)): #0 0xb7f46410 in ?? () #1 0xbfdd5298 in ?? () #2 0x00000000 in ?? () (gdb) Now that looks pretty broken to me as it provides no information on where the seg fault happened, and none of my threads are at 0x00000000. If I simply ctl-c the program half of the threads show the nonsense as you see above. If the program seg faults itself, the debugger shows has same problems. With the exception of exactly how one stops the program or how it dies, the broken debugger output is essentially the same as the information I previously sent you in comment #4. I can understand that you may not be able to reproduce it since your hardware or the program you are debugging may be different, but when there are at least 3 developers telling you it is broken, I'd say there is a 99.9% chance it is broken. By the way, the same problem occurs on several different computers loaded with SuSE 10.2. It does not occur on any other OS I have used. -- 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=258433#c25 --- Comment #25 from Kern Sibbald 2007-07-06 03:05:52 MST --- Created an attachment (id=150022) --> (https://bugzilla.novell.com/attachment.cgi?id=150022) Configuration file for bacula-sd executable Configuration file that goes with bacula-sd executable. Instructions on reproducing bug in bug note. -- 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=258433#c29 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com --- Comment #29 from Andreas Jaeger 2007-07-06 08:59:43 MST --- (In reply to comment #13 from Andreas Kleen)

If the debugger has problems with the vdso you can disable it with echo 0 > /proc/sys/vm/vdso_enabled

I think this is a workaround. We should document it nevertheless somewhere.

Re #11: Petr, if you really need bug fixes for old versions in a specific time you'll need a support contract, sorry. For openSUSE the deal is either upgrade or wait.

Which is correct. On the other hand, we do fix really critical bugs. If there's a save and non-intrusive patch for this problem, I would approve to include with the next kernel update. We would not do an extra kernel update for 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=258433#c31 --- Comment #31 from Andi Kleen 2007-07-20 05:41:48 MST --- It will only be active for processes started after the sysctl change -- 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=258433#c33 --- Comment #33 from Sankar P 2007-07-23 06:53:19 MST --- it is not "exported the variable". It should be sysctl change. Sorry. -- 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=258433#c35 Robert Kaiser changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kairo@kairo.at --- Comment #35 from Robert Kaiser 2007-08-03 11:44:25 MST --- I'm seeing this on current FACTORY now, but it was gone with the experimental 2.6.21 kernel that was available from the build service for some time in the past. Should the issue on 10.3 FACTORY be filed as a separate bug from this or is it probably the same issue? It would be helpful if I could get useful stacktraces out of gdb, they somehow tend to help my colleagues in the Mozilla project more than "I crashed somewhere" ;-) -- 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=258433#c37 --- Comment #37 from Kern Sibbald 2007-08-10 04:33:14 MST --- Although the echo 0 > /proc/sys/vm/vdso_enabled kludge does help a bit, I regret to inform you that it is *not* a solution for the production 10.2 kernel. It does seem to fix most of the problems, but quite often when the kludge is applied and things seem to work (i.e. no "Failed to read a valid object file image from memory." when starting the debugger) the debugger simply seg faults while my program is running -- *extemely* frustrating. Given that this problem has been ongoing for well over four months on your "production" kernel and it has now cropped up in 10.3, I for one have decided that my project has suffered way too much on your distro. I have now brought up several CentOS 5 systems to replace my OpenSUSE systems, and once augmented by excellent 3rd party repositories has more up to date software available than OpenSuSE. The best part is that the kernel and the debugger are rock solid under exactly the same conditions where OpenSUSE fails. Except for this, which is a really stupid killer (blocker), and your slow Yast2 installer, which is a royal pain, I liked your distro. IMO you guys and Novell need to seriously rethink your priorities. Good bye. -- 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=258433#c43 Andi Kleen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #43 from Andi Kleen 2007-08-22 09:13:23 MST --- Re #41 I don't see anything useful except some whining in that ubuntu link I tried again the executable posted here and couldn't reproduce it, but a custom test program in beta1 could after some trying. Anyways, that was the problem that was fixed post beta1 with Wed Aug 15 15:16:04 CEST 2007 - ak@suse.de .. - patches.arch/i386-compat-vdso: i386: allow debuggers to access the vsyscall page with compat vDSO. .. In general i must say if you people here had given reproducible test cases I could have told you much earlier about this fix which had been around for a long time. I readded the patch to the 10.2 tree too so it'll be fixed there in the next update (or in kotd in a few hours) ------------------------------------------------------------------- Wed Aug 22 17:12:10 CEST 2007 - ak@suse.de - patches.arch/i386-compat-vdso: i386: allow debuggers to access the vsyscall page with compat vDSO (258433). -- 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=258433#c45 --- Comment #45 from Andreas Jaeger 2007-08-22 11:52:31 MST --- I just tested the beta2 kernel on i686 system and that message does not appear anymore when debugging sleep. Hope that it's fixed for good. -- 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=258433#c47 --- Comment #47 from Andi Kleen 2007-08-22 17:09:11 MST --- well openSUSE is a community project, not a Novell only project. You get great software for free, but you're expected to write good bug reports if you don't contribute patches. Good bug reports involves reproducible cases at least for deterministic bugs. That's how free software works. Besides users of gdb should be developers anyways so we can probably expect some higher standards. -- 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=258433#c49 --- Comment #49 from Andre Klapper 2007-08-22 17:34:17 MST --- Created an attachment (id=159330) --> (https://bugzilla.novell.com/attachment.cgi?id=159330) patch mentioned in comment 43 "i386-compat-vdso", extracted from https://api.opensuse.org/source/openSUSE:Factory/kernel-source/patches.arch.... -- 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=258433#c51 --- Comment #51 from Klaus Wagner 2007-10-24 10:08:41 MST --- Just for the record: Patch: patches.arch/i386-compat-vdso included, enabled, and released in: 10.2 kernel update 2.6.18.8-0.7 dated Oct 03, 2007 & released Oct 10, 2007. -- 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.