October 2006 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 210535] New: 10.2a5: no boot partition found on pmac
by bugzilla_noreply＠novell.com 16 Jul '08

16 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=210535 Summary: 10.2a5: no boot partition found on pmac Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: jplack(a)novell.com ReportedBy: olh(a)novell.com QAContact: jsrain(a)novell.com CC: power-bugs(a)forge.provo.novell.com 10.2a5: using 'whole disk' on apple.suse.de leads to an empty list of bootable partitions. -- 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.

1 9

[Bug 211225] New: hwinfo reports random sysfs shit as driver name
by bugzilla_noreply＠novell.com 16 Jul '08

16 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=211225 Summary: hwinfo reports random sysfs shit as driver name Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Blocker Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: olh(a)novell.com QAContact: qa(a)suse.de unfortunately, random hardware drivers report random driver names via sysfs. Those names have no relationship to the real module names. /sys/bus/pci/drivers/AMD_IDE INITRD_MODULES="qla2xxx AMD_IDE" As a result, the system will not boot because the driver is missing in the initrd. -- 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.

1 12

[Bug 211110] New: blkid prints LABEL= info for FAT filesystems
by bugzilla_noreply＠novell.com 16 Jul '08

16 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=211110 Summary: blkid prints LABEL= info for FAT filesystems Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: mkoenig(a)novell.com ReportedBy: olh(a)novell.com QAContact: qa(a)suse.de I'm almost sure FAT has no LABEL info. current blkid prints unininitialized memory: inst-sys:~ # blkid | xxd 0000000: 2f64 6576 2f68 6461 323a 2053 4543 5f54 /dev/hda2: SEC_T 0000010: 5950 453d 226d 7364 6f73 2220 4c41 4245 YPE="msdos" LABE 0000020: 4c3d 2220 2020 2020 2020 2020 2020 4641 L=" FA 0000030: 5431 3620 2020 0e1f be5b 7cac 22c0 740b T16 ...[|.".t. 0000040: 56b4 0ebb 0722 2055 5549 443d 2234 3437 V...." UUID="447 0000050: 332d 3046 3637 2220 5459 5045 3d22 7666 3-0F67" TYPE="vf 0000060: 6174 2220 0a2f 6465 762f 646d 2d30 3a20 at" ./dev/dm-0: 0000070: 5459 5045 3d22 7377 6170 2220 0a2f 6465 TYPE="swap" ./de 0000080: 762f 646d 2d31 3a20 5555 4944 3d22 3264 v/dm-1: UUID="2d 0000090: 3837 6435 6666 2d37 6161 622d 3435 6538 87d5ff-7aab-45e8 00000a0: 2d39 6562 622d 3634 3339 3662 6162 3662 -9ebb-64396bab6b 00000b0: 6634 2220 4c41 4245 4c3d 2273 6e6f 7762 f4" LABEL="snowb 00000c0: 6572 7279 2d72 6f6f 7422 2054 5950 453d erry-root" TYPE= 00000d0: 2272 6569 7365 7266 7322 200a "reiserfs" . inst-sys:~ # -- 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.

1 5

[Bug 211859] New: oom_adj -17 does not prevent OOM killing a task
by bugzilla_noreply＠novell.com 16 Jul '08

16 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=211859 Summary: oom_adj -17 does not prevent OOM killing a task Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: olh(a)novell.com QAContact: qa(a)suse.de echo -n -17 > /proc/2969/oom_adj this does not prevent the kernel from killing pid 2969 anyway. Out of Memory: Kill process 2401 (YaST2.call) score 1789 and children. Out of memory: Killed process 2969 (Xorg). setting /proc/sys/vm/overcommit_memory from 1 to 0 does not help either. -- 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.

1 11

[Bug 211236] New: /dev/disk/ symlinks not constistent
by bugzilla_noreply＠novell.com 16 Jul '08

16 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=211236 Summary: /dev/disk/ symlinks not constistent Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Blocker Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: olh(a)novell.com QAContact: qa(a)suse.de libata: /dev/disk/by-id/scsi-SATA_TOSHIBA_MK6026G_Y4Q60098T ide: /dev/disk/by-id/ata-TOSHIBA_MK6026GAXB_Y4Q60098T this is clearly broken. -- 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.

1 5

[Bug 211238] New: vim lost UUID syntax for /etc/fstab
by bugzilla_noreply＠novell.com 16 Jul '08

16 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=211238 Summary: vim lost UUID syntax for /etc/fstab Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: olh(a)novell.com QAContact: qa(a)suse.de this is a valid entry for fstab: UUID=41f6db4a-e38f-426e-895d-1b1572e8e1fe /reiserfs acl,user_xattr 1 1 UUID is shown as red when syntax highlighting is enabled. It should be blue, like LABEL= lines. -- 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.

1 4

[Bug 212470] New: uic crashes while loading libqmng.so
by bugzilla_noreply＠novell.com 16 Jul '08

16 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=212470 Summary: uic crashes while loading libqmng.so Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: olh(a)novell.com QAContact: qa(a)suse.de CC: power-bugs(a)forge.provo.novell.com abuild@pomegranate:/usr/src/packages/BUILD/qt-x11-free-3.3.6/tools/qtconfig> rm -fv qmake_image_collection.cpp ; gdb /usr/src/packages/BUILD/qt-x11-free-3.3.6/bin/uic -q --readnow --exec=/usr/src/packages/BUILD/qt-x11-free-3.3.6/bin/uic -ex 'r -L /usr/src/packages/BUILD/qt-x11-free-3.3.6/plugins -embed qtconfig images/appicon.png -o qmake_image_collection.cpp' -ex bt -ex 'info threads' -ex q removed `qmake_image_collection.cpp' Using host libthread_db library "/lib/power4/libthread_db.so.1". Starting program: /usr/src/packages/BUILD/qt-x11-free-3.3.6/bin/uic -L /usr/src/packages/BUILD/qt-x11-free-3.3.6/plugins -embed qtconfig images/appicon.png -o qmake_image_collection.cpp [Thread debugging using libthread_db enabled] [New Thread -134397952 (LWP 2846)] Program received signal SIGABRT, Aborted. [Switching to Thread -134397952 (LWP 2846)] 0x0ef60ff0 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); Current language: auto; currently c #0 0x0ef60ff0 in *__GI_raise (sig=6) at ./nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x0ef62b24 in *__GI_abort () at abort.c:88 #2 0x0efa81fc in malloc_printerr (action=2, str=0xf06d5fc "malloc: top chunk is corrupt", ptr=0x0) at malloc.c:5763 #3 0x0efa943c in top_check () at hooks.c:224 #4 0x0efababc in malloc_check (sz=96, caller=0xb1e) at hooks.c:265 #5 0x0efac5a0 in __libc_calloc (n=<value optimized out>, elem_size=<value optimized out>) at malloc.c:3778 #6 0xf7ff1038 in _dl_check_map_versions (map=0x1006cb58, verbose=0, trace_mode=0) at dl-version.c:299 #7 0x22004422 in ?? () #8 0xf7ff3fac in dl_open_worker (a=<value optimized out>) at dl-open.c:291 #9 0xf7fef18c in _dl_catch_error (objname=0xffde3f7c, errstring=0xffde3f80, mallocedp=0xffde3f78, operate=0xf7ff3b90 <dl_open_worker>, args=0x0) at dl-error.c:178 #10 0xf7ff36e8 in _dl_open (file=0x1006cab8 "/usr/src/packages/BUILD/qt-x11-free-3.3.6/plugins/imageformats/libqmng.so", mode=-2147483647, caller_dlopen=0xfd62e98, nsid=-2, argc=8, argv=0xffde5504, env=0xffde5528) at dl-open.c:543 #11 0x0f315f94 in dlopen_doit (a=<value optimized out>) at dlopen.c:66 #12 0xf7fef18c in _dl_catch_error (objname=0x1006a714, errstring=0x1006a718, mallocedp=0x1006a710, operate=0xf315f00 <dlopen_doit>, args=0x0) at dl-error.c:178 #13 0x0f316600 in _dlerror_run (operate=0xf315f00 <dlopen_doit>, args=0xffde42c8) at dlerror.c:164 #14 0x0f315eb8 in __dlopen (file=<value optimized out>, mode=0) at dlopen.c:87 #15 0x0fd62e98 in QLibraryPrivate::loadLibrary (this=0x10069d50) at tools/qlibrary_unix.cpp:117 #16 0x0fd8dc8c in QLibrary::load (this=<value optimized out>) at tools/qlibrary.cpp:322 #17 0x0fd69684 in QComLibrary::createInstanceInternal (this=0x1006a640) at tools/qcomlibrary.cpp:472 #18 0x44004242 in ?? () #19 0x0fd69a14 in QComLibrary::qtVersion (this=0x0) at tools/qcomlibrary.cpp:516 #20 0x0fd8917c in QGPluginManager::featureList (this=0x10069b60) at tools/qgpluginmanager.cpp:437 #21 0x0fa25d20 in qt_init_image_plugins () at kernel/qimage.cpp:3892 #22 0x0fa26714 in QImageIO::imageFormat (d=0xffde4598) at kernel/qimage.cpp:4302 #23 0x0fa28c64 in QImageIO::read (this=0xffde4e08) at kernel/qimage.cpp:4446 #24 0x0fa29734 in QImage::load (this=0xffde4e70, fileName=<value optimized out>, format=<value optimized out>) at kernel/qimage.cpp:3484 #25 0x1003c400 in Uic::embed (out=@0xffde505c, project=0xffde572a "qtconfig", images=@0xffde4fc4) at embed.cpp:151 #26 0x84002848 in ?? () #27 0x10007404 in main (argc=8, argv=<value optimized out>) at main.cpp:271 * 1 Thread -134397952 (LWP 2846) 0x0ef60ff0 in *__GI_raise (sig=6) at ./nptl/sysdeps/unix/sysv/linux/raise.c:64 The program is running. Exit anyway? (y or n) y -- 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.

1 2

[Bug 211860] New: keep display alive after oom
by bugzilla_noreply＠novell.com 16 Jul '08

16 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=211860 Summary: keep display alive after oom Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: olh(a)novell.com QAContact: jsrain(a)novell.com the kernel tends to kill processes that dont behave and use too much memory. see bug #209424 Unfortunatelty, the kernel kills also Xorg, which can not restore the graphics card state. If Xorg is killed, the system appears to be frozen. echo -n '-17' > /proc/$XORG_PID/oom_adj In theory the line above should keep X alive, bug #211859 talks about the practice. Either way, the yast startup scripts in the inst-sys have to make sure that Xorg is not killed. Documentation/filesystems/proc.txt: ... 2.12 /proc/<pid>/oom_adj - Adjust the oom-killer score ------------------------------------------------------ This file can be used to adjust the score used to select which processes should be killed in an out-of-memory situation. Giving it a high score will increase the likelihood of this process being killed by the oom-killer. Valid values are in the range -16 to +15, plus the special value -17, which disables oom-killing altogether for this process. 2.13 /proc/<pid>/oom_score - Display current oom-killer score ------------------------------------------------------------- ------------------------------------------------------------------------------ This file can be used to check the current score used by the oom-killer is for any given <pid>. Use it together with /proc/<pid>/oom_adj to tune which process should be killed in an out-of-memory situation. .. -- 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.

1 5

[Bug 212548] New: simplify glibc test builds for power4/5
by bugzilla_noreply＠novell.com 16 Jul '08

16 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=212548 Summary: simplify glibc test builds for power4/5 Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: pbaudis(a)novell.com ReportedBy: olh(a)novell.com QAContact: qa(a)suse.de CC: power-bugs(a)forge.provo.novell.com patch to allow power4 or power5 only builds in glibc.spec -- 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.

1 4

[Bug 212580] New: build a power6 optimized glibc
by bugzilla_noreply＠novell.com 16 Jul '08

16 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=212580 Summary: build a power6 optimized glibc Product: openSUSE 10.2 Version: Alpha 5 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: pbaudis(a)novell.com ReportedBy: olh(a)novell.com QAContact: qa(a)suse.de CC: power-bugs(a)forge.provo.novell.com the attached patch builds also a power6 optimized glibc, similar to what we have for power4/970 an power5 -- 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.

1 5