[Bug 832737] New: zypper [in,dup,rm,se] segmentation fault
https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c0 Summary: zypper [in,dup,rm,se] segmentation fault Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: i686 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mrmazda@earthlink.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- With repos changed manually to factory-snapshot, I did zypper -v dup on a multiboot Athlon 13.1M2 system running kernel-desktop-3.10.0-rc4 but with kernel-desktop locked. The dup completed without any apparent errors. Afterward I did zypper rl kernel-desktop; zypper -v dup. That resulted in a segfault. I tried again without -v, then tried zypper -v in kernel-desktop, and repeated without -v, then zypper rm zypper-aptitude, then zypper se -s zypp. All segfaulted. I used rpm to upgrade to the Factory zypp Head packages, but it helped none for zypper se -s zypp and zypper -v dup. dmesg tail: zypper[1290]: segfault at 2 ip b75dc49a sp bff35ef0 error 4 in libzypp.so.1302.1.0[b7253000+470000] zypper[1294]: segfault at 2 ip b75ef49a sp bf81fb70 error 4 in libzypp.so.1302.1.0[b7266000+470000] zypper[1298]: segfault at 2 ip b762549a sp bfbc54b0 error 4 in libzypp.so.1302.1.0[b729c000+470000] zypper[1302]: segfault at 2 ip b76c449a sp bfac09c0 error 4 in libzypp.so.1302.1.0[b733b000+470000] zypper[1450]: segfault at 2 ip b76ae49a sp bfca9490 error 4 in libzypp.so.1302.1.0[b7325000+470000] zypper[1476]: segfault at 2 ip b760749a sp bfa036a0 error 4 in libzypp.so.1302.1.0[b727e000+470000] zypper[1503]: segfault at fff1063d ip b76788ca sp bf9f8ef0 error 5 in libzypp.so.1304.0.0[b72ee000+472000] libzypp-13.3.0-1.2.i586 rpm-4.10.3.1-8.3.i586 rpm-python-4.10.3.1-8.2.i586 zypper-1.9.0-2.3.i586 zypper-aptitude-1.9.0-2.3.noarch zypper-log-1.9.0-2.3.noarch Linux kt880 3.10.0-rc4-1-desktop #1 SMP PREEMPT Wed Jun 5 15:55:02 UTC 2013 (fc06ef7) i686 athlon i386 GNU/Linux vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) XP 2400+ stepping : 1 cpu MHz : 2000.098 cpuid level : 1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow clflush size : 32 cache_alignment : 32 address sizes : 34 bits physical, 32 bits virtual power management: ts -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c1 --- Comment #1 from Felix Miata <mrmazda@earthlink.net> 2013-08-01 08:41:54 UTC --- After doing zypper up on the same system's 12.3, its zypper too is segfaulting. zypper[2403]: segfault at ffffff86 ip b48234a1 sp bff55630 error 5 zypper[3764] general protection ip:b48a2086 sp:bfbb2000 error:0 libzypp-11.11.1-2.23.2.i586 zypper-1.7.14-1.24.1.i586 -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c2 --- Comment #2 from Felix Miata <mrmazda@earthlink.net> 2013-08-01 09:28:38 UTC --- Comment 1 should have been written for 12.2, but 12.3 has the same problem. zypper[3492]: segfault at 0 ip b76b2631 sp bff7de10 error 4 in libzypp.so.1200.13.3[b733c000+471000] kernel-default-3.7.10-1.16.1.i586 libzypp-12.13.3-1.11.1.i586 zypper-1.8.16-1.10.1.i586 zypper-log-1.8.16-1.10.1.noarch -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |zypp-maintainers@forge.prov |ovo.novell.com |o.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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c3 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #3 from Michael Andres <ma@suse.com> 2013-08-01 18:38:42 CEST --- Is zypper the only tool no longer working? Could you attach the systems zypper.log (12.2, 12.3, 13.1). May they contain a 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c4 --- Comment #4 from Felix Miata <mrmazda@earthlink.net> 2013-08-01 21:45:56 UTC --- Created an attachment (id=550787) --> (http://bugzilla.novell.com/attachment.cgi?id=550787) zypper.log from 13.1 M2 -> M3 (In reply to comment #3)
Is zypper the only tool no longer working?
All 3 OS installations got all the way through zypper up/dup of 100 or more packages. I did have it completely lock up while in MC after this started to happen, so I tried to reproduce in two other socket A/462 systems, without any failing evident in either.
Could you attach the systems zypper.log (12.2, 12.3, 13.1). May they contain a hint.
As I now suspect hardware may be the issue after finding bad PS caps and replacing them, I'm running memtest now, and if successful after a couple of hours, will try some other things (e.g. fresh factory-snapshot installation) to try to confirm or deny hardware issue before considering whether to attach those from 12.2 & 12.3 or close invalid. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c5 --- Comment #5 from Felix Miata <mrmazda@earthlink.net> 2013-08-02 02:51:27 UTC --- Created an attachment (id=550802) --> (http://bugzilla.novell.com/attachment.cgi?id=550802) manually collected installation logs: /var/log/YaST2/ and /var/log/zypp/ I'm still not entirely convinced this is 100% a hardware problem. I ran memtest 4.10 192 minutes with 0 errors on the repaired power supply. Then I did a HTTP factory-snapshot E17 installation. Everything went apparently well until the last package was installed, then the installation GUI spontaneously exited and the ncurses failure message appeared. I then rebooted to 12.3 and mounted the aborted 13.1 /. No logs were written to /root/inst-sys. No X log was written anywhere I've found. Last week I found a bad cap on another motherboard. I replaced 10 of the 13 it had of that brand and type, which was all I had in stock. This motherboard has more than a dozen of that same brand and type, and most likely same vintage. None are obviously bad, but I'm going to buy more and then replace these before doing any more follow-up on this bug, unless someone from the zypp team has suggestions for other things to do first. All that said, I do have one idea. This has never happened to me in all the years of using openSUSE and SuSE before it, but I wonder if something related to https://bugzilla.redhat.com/show_bug.cgi?id=680508 is happening here. I also had the same trouble with Mandriva and likely Mandrake before it, but its bug DB is no longer available. Such trouble appeared only on certain combinations of hardware and software, and was far far short of ubiquitous. Virtually all my / partitions, as here, are smallish, usually 4.8G, and use a 1024 blocksize to minimize sector overhang waste. Has there been a compiler change for building zypper, libzypp and/or rpm in recent weeks? -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c6 --- Comment #6 from Felix Miata <mrmazda@earthlink.net> 2013-08-02 03:55:22 UTC --- Created an attachment (id=550805) --> (http://bugzilla.novell.com/attachment.cgi?id=550805) zypper.log from comment 5 installation To see if I successfully could, I manually finished the comment 5 installation. On first try, login failed. On second, network failed. Third was a charm, but it seems to work only as well as the previous 13.1 on that host. Zypper ref, al & ll work, but se -s segfaults. zypper[2528]: segfault at 2 ip b768649a sp bf9776e0 error 4 in libzypp.so.1302.1.0[b72fd000+470000] kernel-default-3.10.0-2.3.gc5ad3f9.i586 libzypp-13.3.0-1.2.i586 zypper-1.9.0-2.3.i586 -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|mrmazda@earthlink.net |ma@suse.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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c7 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ma@suse.com | --- Comment #7 from Michael Andres <ma@suse.com> 2013-08-02 13:35:15 CEST --- The logs from c#5 are empty (no zypper.log or y2log). The ones form c#4 and c#6 both use libzypp: 13.3.0 built Jul 6 2013 08:54:24 libsolv: 0.3.0 SystemArchitecture: 'i686' (i686) and both crash in 2013-08-01 23:46:20 <1> kt880(2528) [zypp] PoolImpl.h(setHardLockQueries):246 Apply 51 HardLockQueries Error: signal 11 [bt]: (1) /usr/lib/libzypp.so.1302 : +0x2fc99b [0xb75f999b] [bt]: (2) linux-gate.so.1 : __kernel_sigreturn+0 [0xb7789400] [bt]: (3) /usr/lib/libzypp.so.1302 : +0x38949a [0xb768649a] [bt]: (4) /usr/lib/libzypp.so.1302 : zypp::sat::LookupAttr::iterator::increment()+0x23 [0xb7613d23] [bt]: (5) /usr/lib/libzypp.so.1302 : zypp::sat::LookupAttr::iterator::iterator(zypp::sat::detail::DIWrap&) [bt]: (6) /usr/lib/libzypp.so.1302 : zypp::sat::LookupAttr::begin() ... Well, I'm running almost all zypp versions on my VMs for developing, testing and we also have the hudson build nodes for each distro. No one has this problem. OTOH, the crash seems to happen at a point where libzypp calls into libsolv and where we applied some fixes a few weeks ago, because libsolvs dataiterator was returning random data. On 12.3 we had libsolv-tools-0.2.3 which had the dataiterator bug, and it was fixed in version 0.3.0. You said your 12.3 started to crash after updating. Maybe you can check whether a fresh 12.3 fails after updating to the latest libzypp/ibsolv-tools-0.3.0. If so, please attach the zypper log, so we can check whether it's again the dataiterator. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c8 --- Comment #8 from Felix Miata <mrmazda@earthlink.net> 2013-08-02 19:00:00 UTC --- Created an attachment (id=551027) --> (http://bugzilla.novell.com/attachment.cgi?id=551027) zypper.log from fresh customized minimal X 12.3 HTTP installation to host kt880 I run openSUSE only on hardware solver.onlyRequires = true on all my openSUSE installations download.use_deltarpm = false on most of my openSUSE installations (In reply to comment #7)
Maybe you can check whether a fresh 12.3 fails after updating to the latest libzypp/ibsolv-tools-0.3.0. If so, please attach the zypper log, so we can check whether it's again the dataiterator.
From second boot (to 'runlevel 3') following uneventful installation of 12.3:
# bash_history tail #1375466729 zypper clean -a #1375466799 zypper al zypper libzypp rpm #1375466809 zypper al kernel-desktop #1375466815 zypper ref #1375467415 zypper -v in mc-4.8.9 #1375467516 zypper -v in seamonkey-irc seamonkey-dom-inspector #1375467550 zypper -v in seamonkey-irc-2.17 seamonkey-dom-inspector-2.17 #1375467977 zypper -v in MozillaFirefox-21.0 #1375468261 zypper al MozillaFirefox seamonkey-irc seamonkey-dom-inspector #1375468268 zypper up # dmesg tail portion [ 1601.745021] zypper[2000]: segfault at 70596b4 ip b4ccd00b sp bf89bf40 error 4 # from rpm querying glibc-2.17-4.4.1.i586 kernel-default-3.7.10-1.1.1.i586 libsolv-tools-0.2.4-2.1.1.i586 libudev1-195-13.11.1.i586 libzypp-12.9.0-1.1.1.i586 python-satsolver-0.45.0-4.1.1.i586 udev-195-13.11.1.i586 zypper-1.8.11-1.1.1.i586 zypper-log-1.8.11-1.1.1.noarch A subsequent 'zypper -v in -f prctl' succeeded. Let me know if you want the new zypper.log tail, 229929 more bytes. Motherboard caps are on order, due in 3-7 days. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c9 --- Comment #9 from Felix Miata <mrmazda@earthlink.net> 2013-08-03 06:37:48 UTC --- FWIW, I just spent well over an hour doing urpmi --auto-update on Mageia 3 and yum upgrade on Fedora 19 on the same comment 0 kt880 host, with no hiccups, lockups or crashes observed. -- 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.
From original 12.3: cpuinfo: model name : AMD Athlon(tm) XP 2400+ flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat
https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c10 --- Comment #10 from Felix Miata <mrmazda@earthlink.net> 2013-08-08 04:07:36 UTC --- After replacing 18 1000uf 6.3v caps on the motherboard, and 3.2 hours doing 3 full memtest86+ 4.10 passes with no errors, zypper se -s still segfaults in both 13.1m3 (desktop kernel) and the original 12.3 installation (default kernel), but not in the newer 12.3 (default kernel). pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow last dmesg line: zypper[1154]: segfault at f6349840 ip b63583f2 sp bff68350 error 7 cmdline: root=LABEL=wd80suse123 ipv6.disable=1 noresume splash=verbose vga=794 video=1152x864@60 3 noapic nolapic (normally neither noapic nor nolapic, but I was testing to see if they helped) uname -a: Linux kt880.ij.net 3.7.10-1.16-default #1 SMP Fri May 31 20:21:23 UTC 2013 (97c14ba) i686 athlon i386 GNU/Linux -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c11 --- Comment #11 from Felix Miata <mrmazda@earthlink.net> 2013-08-10 08:23:50 UTC --- Same host's dmesg tail after fresh 13.1M4 installation and "zypper se -s SUSE": 625.413627] NFS: Registering the id_resolver key type [ 625.413672] Key type id_resolver registered [ 625.413675] Key type id_legacy registered [ 971.499672] zypper[20937]: segfault at 1 ip 09843fd8 sp bfd78f00 error 6 [ 986.044431] zypper[20942]: segfault at 2 ip b765348a sp bf9a7d70 error 4 in libzypp.so.1302.1.0[b72ca000+470000] [ 991.373552] zypper[20947]: segfault at 2 ip b760748a sp bf891f30 error 4 in libzypp.so.1302.1.0[b727e000+470000] uname -a: Linux kt880 3.10.1-3.g0cd5432-default #1 SMP Fri Jul 19 14:39:31 UTC 2013 (0cd5432) i686 athlon i386 GNU/Linux /proc/cmdline: root=LABEL=s131test ipv6.disable=1 noresume splash=verbose video=1152x864@60 vga=794 noapic libzypp-13.3.0-1.3.i586 zypper-1.9.0-2.4.i586 -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c12 --- Comment #12 from Felix Miata <mrmazda@earthlink.net> 2013-08-10 08:34:50 UTC --- Created an attachment (id=552095) --> (http://bugzilla.novell.com/attachment.cgi?id=552095) /var/log/zypp/history following fresh 13.1M4 installation Previous comment forgot to mention the installation failed to complete while I wasn't looking. It booted successfully after the abort, but I could not login until after copying passwd/shadow files from another installation and rebooting. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c13 --- Comment #13 from Felix Miata <mrmazda@earthlink.net> 2013-08-10 08:35:01 UTC --- Created an attachment (id=552096) --> (http://bugzilla.novell.com/attachment.cgi?id=552096) zypper.log from fresh 13.1M4 installation, following segfaulted 'zypper se -s SUSE' -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c14 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mls@suse.com --- Comment #14 from Michael Andres <ma@suse.com> 2013-08-27 13:06:15 CEST --- (Sorry for the late response, I've been on vacation) @mls: Any idea? The crash in zypp::sat::LookupAttr::iterator::increment is the location we had to touch after the libsolv dataiterator fixes (added the ::dataiterator_strdup call). void LookupAttr::iterator::increment() { if ( _dip ) { if ( ! ::dataiterator_step( _dip.get() ) ) { _dip.reset(); base_reference() = 0; } else { ::dataiterator_strdup( _dip.get() ); } } } -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c15 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|zypper [in,dup,rm,se] |zypper [in,dup,rm,se,ve] |segmentation fault |segmentation fault --- Comment #15 from Felix Miata <mrmazda@earthlink.net> 2013-09-01 05:56:26 UTC --- On the 13.1M3 host kt880 installation (sda15) I upgraded using rpm to: libzypp-13.5.0-1.1 rpm-4.11.1-3.3 zypper-1.9.1-1.1 It didn't stop the segfaulting. 12.3 updates has nothing newer than already installed to try. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c16 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|mls@suse.com |mrmazda@earthlink.net --- Comment #16 from Michael Andres <ma@suse.com> 2013-09-02 11:51:46 CEST --- This problem still seems to be unique to your machine. We debugged into libsolv using the information provided so far, but this did not reveal anything. We'd need a core file to get more information. Maybe you can install on your 12.3 libzypp and zypper from the zypp:Code12_3-Branch repo as the packages there are not stripped. (http://download.opensuse.org/repositories/zypp:/Code12_3-Branch/openSUSE_12....). Execute 'ulimit -c unlimited' to enable core file creation. If zypper crashes, attach the core file and the zypper.log. (please keep/backup /usr/bin/zypper and /usr/lib/libzypp.so.1200.15.0 in case we need additional info) -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c17 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|mrmazda@earthlink.net |ma@suse.com --- Comment #17 from Felix Miata <mrmazda@earthlink.net> 2013-09-02 18:39:33 UTC --- bz2 of core file is 150% of upload size limit. What now? -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c18 --- Comment #18 from Michael Andres <ma@suse.com> 2013-09-03 11:18:32 CEST --- Found it in my mailbox, thanks. (you can use 'split' to divide the file into smaller pieces...) -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c19 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ma@suse.com | --- Comment #19 from Felix Miata <mrmazda@earthlink.net> 2013-09-03 09:39:44 UTC --- I got to thinking about this and looked at the roots of the 13.1 system. It started as a clone of the 12.3 system, which was originally installed last November 15 from one of the milestones, 12.3-1.13. /root/inst-sys/ and the oldest files in /var/log/YaST2/ are identical on the two systems. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c20 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #20 from Michael Andres <ma@suse.com> 2013-09-03 18:40:36 CEST --- All crashes so far seem to happen, when applying the hardlocks. I'd like to know if this is just a coincidence or if other query or non query actions fail as well. Could you please - on the 12.3 system - move away the /etc/zypp/locks file (containing your locked packages); if it still crashes also move away the /var/lib/zypp/SoftLocks file. If it still crashes, please attach the zypper.log. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c21 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mrmazda@earthlink.net | --- Comment #21 from Felix Miata <mrmazda@earthlink.net> 2013-09-03 18:23:50 UTC --- Created an attachment (id=555574) --> (http://bugzilla.novell.com/attachment.cgi?id=555574) 3443 byte locks file from host kt880's 12.3 # mv /etc/zypp/locks /etc/zypp/.locks # 3443 bytes last written 7 Aug # zypper se -s GL no segfault # zypper al MozillaFirefox seamonkey # zypper up still no segfault -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c22 --- Comment #22 from Michael Andres <ma@suse.com> 2013-09-04 16:39:35 CEST --- That's strange. There's nothing in the lock file that could explain the crash. And also after an excessive debugging session we're not sure what actually happens on your system. We'd recommend to call 'zypper clean -m', so all cached data files are recreated. It would be interesting to know if you can recreate all the packages locks again, and if the same procedure also helps on the 13.1 system. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c23 --- Comment #23 from Felix Miata <mrmazda@earthlink.net> 2013-09-04 16:13:20 UTC --- Created an attachment (id=555793) --> (http://bugzilla.novell.com/attachment.cgi?id=555793) 3361 byte locks file from kt880's 13.1m4 -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c24 --- Comment #24 from Felix Miata <mrmazda@earthlink.net> 2013-09-04 16:13:44 UTC --- Created an attachment (id=555794) --> (http://bugzilla.novell.com/attachment.cgi?id=555794) /etc/zypp/zypp.conf from kt880's 13.1m4 12.3: # zypper clean -m # mv /etc/zypp/locks /etc/zypp/locks-new # cp -a /etc/zypp/.locks /etc/zypp/locks # zypper se -s GL # zypper -v up no segfault 13.1: # zypper clean -m # mv /etc/zypp/locks /etc/zypp/locks-new # cp -a /etc/zypp/.locks /etc/zypp/locks # zypper se -s GL segfault # cp -a /etc/zypp/locks-new /etc/zypp/locks # zypper se -s GL no segfault # zypper clean -a # zypper ref # zypper ll # cp -a /etc/zypp/.locks /etc/zypp/locks # zypper ll # zypper se -s GL segfault Any more suggestions? -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c25 --- Comment #25 from Michael Andres <ma@suse.com> 2013-09-04 18:55:46 CEST --- We need to build a special libzypp without optimisation for your 13.1 first. If you like to install it then, and it still crashes and we get a core file we hopefully find the reason. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c26 --- Comment #26 from Felix Miata <mrmazda@earthlink.net> 2013-09-04 17:04:32 UTC --- 13.1: # zypper clean -m # cp -a /etc/zypp/locks-new /etc/zypp/locks # zypper se -s GL no segfault # zypper al kernel-default # zypper al kernel-desktop # zypper se -s GL segfault # zypper ll # | Name | Type | Repository --+----------------+---------+----------- 1 | MozillaFirefox | package | (any) 2 | seamonkey | package | (any) 3 | kernel-default | package | (any) 4 | kernel-desktop | package | (any) # uname -a Linux kt880 3.11.0-rc7-1.g99e1318-default #1 SMP Tue Aug 27 13:32:27 UTC 2013 (99e1318) i686 athlon i386 GNU/Linux # cat /proc/cmdline root=/dev/disk/by-label/wd80suse131 ipv6.disable=1 apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=794 3 (reboot) #cat /proc/cmdline root=LABEL=wd80suse131 ipv6.disable=1 noresume splash=verbose vga=794 video=1152x864@70 3 noapic nolapic # zypper clean -m # cp -a /etc/zypp/locks-new /etc/zypp/locks # zypper se -s GL # zypper al kdm # zypper se -s GL # zypper al kernel-default # zypper se -s GL segfault # zypper rl kernel-default # zypper se -s GL # zypper al kernel-desktop # zypper se -s GL segfault # zypper rl kdm # zypper se -s GL no segfault Looks like it can handle 3 locks or less without segfaulting, but no more. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c27 --- Comment #27 from Michael Andres <ma@suse.com> 2013-09-05 11:45:29 CEST --- Could you please install valgrind and run valgrind zypper se -s GL That way we can check if valgrind detects some corruption before the segfault. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c28 --- Comment #28 from Felix Miata <mrmazda@earthlink.net> 2013-09-05 15:31:21 UTC --- # zypper ll # 3 items # zypper ref # zypper -v in valgrind # zypper al kernel-default # valgrind zypper se -s GL .. in use at exit: 6,618,521 bytes in 253,096 blocks total heap usage: 435,978 allocs, 182,882 frees, 942,946,588 bytes allocated .. definitely lost: 6,480 bytes in 39 blocks indirectly lost: 0 possibly lost: 645,389 bytes in 21,986 blocks suppressed: 0 Rerun with --leak-check=full to see details of leaked memory For counts of detected and suppressed errors, rerun with: -v ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) no segfault # mv /etc/zypp/locks /etc/zypp/locks-4 # cp -a /etc/zypp/.locks /etc/zypp/locks # zypper ll # 40 items # valgrind zypper se -s GL (valgrind output) similar to with 4 locks as above, aka no segfault # zypper se -s GL segfault -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c29 --- Comment #29 from Michael Andres <ma@suse.com> 2013-09-05 18:51:43 CEST --- No segfault with valgrind, that's a pity. With enough locks added, 12.3 crashes as well? I'm just asking because it's easier for me to build a nonoptimized-debug-libzypp for 12.3 then for 13.1. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c30 --- Comment #30 from Felix Miata <mrmazda@earthlink.net> 2013-09-05 18:56:12 UTC --- 12.3: # zypper ll (41 locks) # zypper ref # zypper se -s GL # zypper lu # zypper se -s kern | grep def | grep -v src returned nothing # zypper se -s kern segfault # zypper se -s GL segfault # zypper clean -m # zypper se -s GL segfault # cp -a /etc/zypp/locks-OK /etc/zypp/locks # 2 locks # zypper se -s GL No segfault, so build it for 12.3 if you please. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c31 --- Comment #31 from Michael Andres <ma@suse.com> 2013-09-06 13:15:35 CEST --- Created an attachment (id=556192) --> (http://bugzilla.novell.com/attachment.cgi?id=556192) nonoptimized-debug-libzypp for 12.3 Attached is the nonoptimized-debug-libzypp for 12.3. Hope you able to reproduce the crash with it. Simply unpack and install it in /usr/lib: bunzip2 libzypp.so.1200.15.0.bz2 cp libzypp.so.1200.15.0 /usr/lib ldconfig Enable core file creation: ulimit -c unlimited Splitting the core file into uploadable pieces: bzip2 core split -b 9M --additional-suffix=-libzypp-core.bz2 core.bz2 -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c32 --- Comment #32 from Felix Miata <mrmazda@earthlink.net> 2013-09-06 18:20:41 UTC --- Created an attachment (id=556260) --> (http://bugzilla.novell.com/attachment.cgi?id=556260) zypper se -s GL segfault core using comment 31 attachment, part 1 of split bz2 (In reply to comment #31)
Simply unpack and install it in /usr/lib:
Would "simply" have done it? Permissions as unpacked were 664 or 644, 755 as I installed it, to match perms of the original file. Core size: 55388K What clears "ulimit -c unlimited" when done? -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c33 --- Comment #33 from Felix Miata <mrmazda@earthlink.net> 2013-09-06 18:21:38 UTC --- Created an attachment (id=556261) --> (http://bugzilla.novell.com/attachment.cgi?id=556261) zypper se -s GL segfault core using comment 31 attachment, part 2 of split bz2 -- 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.
What clears "ulimit -c unlimited" when done?
https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c34 --- Comment #34 from Michael Andres <ma@suse.com> 2013-09-09 18:52:14 CEST --- ulimit -c 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c35 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #556192|0 |1 is obsolete| | Attachment #556260|0 |1 is obsolete| | Attachment #556261|0 |1 is obsolete| | --- Comment #35 from Michael Andres <ma@suse.com> 2013-09-17 18:11:00 CEST --- Created an attachment (id=558691) --> (http://bugzilla.novell.com/attachment.cgi?id=558691) nonoptimized-debug-libzypp for 12.3 (v2) (sorry for the delay, but I've been offline last week) It's a brainteaser. Please try out the attached debug-libzypp (v2) for 12.3 and attach a core file in case it crashes. 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mrmazda@earthlink.net -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c36 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mrmazda@earthlink.net | --- Comment #36 from Felix Miata <mrmazda@earthlink.net> 2013-09-18 07:10:01 UTC --- No segfault using comment 35 lib for se -s and -v up on 12.3. Upgrade installed newer libzypp package version, after which segfaulting did not return with se -s. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c37 --- Comment #37 from Michael Andres <ma@suse.com> 2013-09-18 13:13:32 CEST --- We were afraid this would happen. The libzypp you installed from the zypp:Code12_3-Branch repo and the two libzypp versions I attached were all compiled from the same code; just compiler optimization is different. This could hint to a misscompilation. The core files we saw could also hint to a misscompilation. But then the crashes should not be limited to your system. It would be great it you could stay with the libzypp from comment 35 for a while, 'hoping' it will crash an produce a core which reveals a bug. --- The lib has BuildID[sha1]=0xc29dca57f0993572283073455f20964658e7dc0e. You can easily check whether zypper actually uses the right one: $ ldd /usr/bin/zypper | grep libzypp libzypp.so.1200 => /usr/lib/libzypp.so.1200 VVVVVVVVVVVVVVVVVVVVVVVV $ file --dereference /usr/lib/libzypp.so.1200 .....BuildID[sha1]=0xc29dca57f0993572283073455f20964658e7dc0e -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c38 --- Comment #38 from Felix Miata <mrmazda@earthlink.net> 2013-09-18 15:20:31 UTC --- # ldd /usr/bin/zypper | grep libzypp libzypp.so.1200 => /usr/lib/libzypp.so.1200 (0xb71ac000) # file --dereference /usr/lib/libzypp.so.1200 /usr/lib/libzypp.so.1200: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=0xc29dca57f0993572283073455f20964658e7dc0e, not stripped # zypper al libzypp zypper -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c Alberto Planas Dominguez <aplanas@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| | GOLD -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c39 --- Comment #39 from Felix Miata <mrmazda@earthlink.net> 2013-12-04 03:10:48 UTC --- No luck today acquiring a segfault with the special 1790928 byte binary to do some searching, remove MozillaFirefox and seamonkey, install firefox-esr and branding, and up 86 non-zypper-related packages on 12.3. With the M4 binary on 13.1 I got segfaults on every up attempt until I used rpm to upgrade 13.1's zypper, libzypp & libsolv-tools, after which no more segfaults. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c40 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #40 from Michael Andres <ma@suse.com> 2013-12-04 08:58:23 CET --- Thanks for the feedback. I'm going to close this report for now. Please reopen, if the problem shows up again. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c41 --- Comment #41 from Felix Miata <mrmazda@earthlink.net> 2013-12-04 09:09:30 UTC --- On 12.3 I went ahead and unlocked zypper and libzypp, then did zypper -v up, then zypper se -s GL, only the latter of which produced a segfault. I repeated zypper se -s GL after removing the 3kb+ /etc/zypp/locks file, without getting a segfault. Any chance this could be a "mutex"-like thing like in https://bugzilla.redhat.com/show_bug.cgi?id=680508 and https://qa.mandriva.com/show_bug.cgi?id=32547 ? On the same machine over the past ~36 hours I did updates to 6 installations: Mageia 4 (urpmi), Fedora 19 (yum), Fedora 20 (yum), openSUSE 12.2 (zypper), openSUSE 12.3 (zypper) and openSUSE 13.1 (zypper). Only 12.3's zypper produced observable bad behavior of any kind, 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c42 --- Comment #42 from Felix Miata <mrmazda@earthlink.net> 2013-12-14 02:05:00 UTC --- FWIW, on same I host I HTTP installed 13.2 from Factory repos last night. Zypper seems perfectly happy running with well in excess of 40 locks set and kernel-default. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c43 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | --- Comment #43 from Felix Miata <mrmazda@earthlink.net> 2014-02-27 00:53:28 UTC --- (In reply to comment #42)
FWIW, on same I host I HTTP installed 13.2 from Factory repos last night. Zypper seems perfectly happy running with well in excess of 40 locks set and kernel-default.
That happiness disappeared on 13.2 after upgrading to zypper-1.10.7-1.1/libzypp-14.14.0-1.1. I have to reduce locks file size again, to be able to dup. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c44 --- Comment #44 from Felix Miata <mrmazda@earthlink.net> 2014-04-25 03:58:06 EDT --- using 32 bit 12.3 running kernel-default-3.7.10-1.16 with libzypp-12.16.4-1.33.1 zypper-1.8.24-1.26.1 zypper -v up with more than 3 locks set segfaulted after refreshing but before beginning to list packages it wants an answer y to (while "reading installed packages"?), but works as expected with only 3 locks set. using 32 bit 13.1 running kernel-default-3.11.10-7 with libzypp-13.9.0-13.1 zypper-1.9.12-16.1 zypper -v up with a 3433 byte locks file (41 entries, including kernel* as #40, with firefox-esr as #41) worked as expected. Just afterward, zypper rl kernel*; zypper -v up segfaulted after "Reading installed packages..." appeared on screen. Removing the locks file, then zypper al seamonkey; zypper se -s kernel-default; zypper ll; zypper -v up succeeded to upgrade kernel-firmware. using 32 bit Factory running kernel-default-3.14.rc7 with libzypp-14.17.5-1.1 zypper-1.11.4-1.1 zypper -v dup with a 3726 byte locks file (45 locks, including kernel* as #45), followed by zypper rl kernel*; zypper -v dup all worked as expected. 8 days ago on same machine, urpmi --auto-select on Cauldron and yum upgrade on Rawhide again worked fine too. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c45 --- Comment #45 from Michael Andres <ma@suse.com> 2014-04-28 12:41:21 CEST --- Sorry Felix, but I currently don't know how to hunt this without being able to reproduce it on one of our machines. But I still don't know a second machine suffering from this 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c46 Michael Matz <matz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #46 from Michael Matz <matz@suse.com> 2014-04-28 12:27:20 UTC --- Does valgrind say anything now (and does the segfault still happen with it)? If that doesn't reveal anything: run zypper under gdb (install libzypp-debuginfo and -debugsource, as well as zypper-debuginfo/debugsource): % gdb --args /usr/bin/zypper <your arguments> ... (gdb) r ... wait until it crashes ... (gdb) backtrace Show us the output of that backtrace. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c47 --- Comment #47 from Felix Miata <mrmazda@earthlink.net> 2014-04-28 18:32:55 EDT --- (In reply to comment #45)
Sorry Felix, but I currently don't know how to hunt this without being able to reproduce it on one of our machines. But I still don't know a second machine suffering from this problem.
Sad thing is I have a near twin to the errant host kt880, kt400, with all but identical data in /proc/cpuinfo, CPU speed being the notable difference, and the 16% slower CPU host kt400 has not suffered this. Motherboard and gfxcard are very different 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c48 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|mrmazda@earthlink.net | --- Comment #48 from Felix Miata <mrmazda@earthlink.net> 2014-04-28 18:33:06 EDT --- Created an attachment (id=588015) --> (http://bugzilla.novell.com/attachment.cgi?id=588015) copy & paste from Konsole gdb attempt Is this attachment from 13.1 host kt880 useful? valgrind --leak-check=yes zypper se -s n-page failed to produce a segfault. Process tail: ==3509== LEAK SUMMARY: ==3509== definitely lost: 0 bytes in 0 blocks ==3509== indirectly lost: 0 bytes in 0 blocks ==3509== possibly lost: 1,044,588 bytes in 33,654 blocks ==3509== still reachable: 10,250,326 bytes in 394,738 blocks ==3509== suppressed: 0 bytes in 0 blocks ==3509== Reachable blocks (those to which a pointer was found) are not shown. ==3509== To see them, rerun with: --leak-check=full --show-reachable=yes ==3509== ==3509== For counts of detected and suppressed errors, rerun with: -v ==3509== ERROR SUMMARY: 52 errors from 52 contexts (suppressed: 0 from 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c49 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |matz@suse.com --- Comment #49 from Michael Andres <ma@suse.com> 2014-04-29 09:47:02 CEST --- @Michael Matz: It's like comment #27 ff. No segfault with valgrind nor with an un-optimized libzypp/libsolv. Mls and I spent quite some time to debug the core files and read the libsolv code in parallel. But they did not fit together. We're almost sure that the state we found in the core file is not reachable by the code, but it's hard to figure out more debugging the optimized code. But unoptimized it did not segfault. -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c50 --- Comment #50 from Felix Miata <mrmazda@earthlink.net> 2014-07-03 00:18:27 EDT --- Factory (1.11.8-1.1/14.24.0-1.2) seems to be OK with lots of locks currently, but not 13.1 (1.9.16-22.2/13.10.2-19.6). -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c51 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|matz@suse.com | Resolution| |INVALID Status Whiteboard| GOLD | --- Comment #51 from Felix Miata <mrmazda@earthlink.net> 2014-09-06 05:00:01 EDT --- Comment 0 system would no longer even POST every try. I moved the HDs to a slightly older, very similar Socket A system, requiring all same drivers. No fault found with 12.3, 13.1 or Factory using 3kb+ /etc/zypp/lock files. -> hardware failure -> invalid -- 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=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c52 --- Comment #52 from Michael Andres <ma@suse.com> 2014-09-08 09:32:31 CEST --- Thanks for the update. -- 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