May 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 908454] get_kernel_version does not support zImage
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.novell.com/show_bug.cgi?id=908454 --- Comment #35 from Andreas Schwab <schwab(a)suse.com> --- > ... with the file command you can not do this That's why we have get_kernel_version. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 908454] get_kernel_version does not support zImage
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.suse.com/show_bug.cgi?id=908454 --- Comment #34 from Dr. Werner Fink <werner(a)suse.com> --- (In reply to Andreas Faerber from comment #31) There is nothing to fix as if you have a look into the code of get_kernel_version you will see a brut force method which search for the string "Linux version " for both little and big endian case in the binary which is ... if required ... uncompressed with "/bin/gzip -dc %s 2>/dev/null" ... with the file command you can not do this, as file was not written to dump symbols from an elf binary nor symbols from a compressed elf binary. I've done an strace get_kernel_version /boot/vmlinux | & grep ^read | wc -l on PowerPC64 and this reports 351 reads with each of 32768 bytes to find the final "Linux version " ... this has nothing todo with magic headers of magic marks for elf binaries. The PowerPC64 kernel probed with the file command shows ELF 64-bit MSB shared object, 64-bit PowerPC or cisco 7500, version 1 (SYSV), statically linked, BuildID[sha1]=0x88bcd91b88298c500c6127aae9a4756811267a47, stripped -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 908454] get_kernel_version does not support zImage
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.novell.com/show_bug.cgi?id=908454 --- Comment #33 from Andreas Schwab <schwab(a)suse.com> --- get_kernel_version can uncompress the file, it just needs to find the signature. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 910675] kernel of opensuse13.2 does not mount a USB storage card which is mounted by kernel of 13.1 without problems
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.suse.com/show_bug.cgi?id=910675 Hannes Reinecke <hare(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(hare(a)suse.com) | --- Comment #16 from Hannes Reinecke <hare(a)suse.com> --- Not that I'm aware of. However, the error is classified as 'critical target error', so it might be that the SCSI midlayer does less retries here (as the hardware is affected). But needless to say, the number of retries won't influence the behaviour, as the hardware will always respond with the same sense code. I'd rather suspect that the command itself isn't handled properly. Can you check what's so special with the 'READ' command? I would think the READ is going beyond the capacity of the disk ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 872102] blkid cannot detect backing store of a bcache device
by bugzilla_noreply＠novell.com 12 May '15

12 May '15

http://bugzilla.suse.com/show_bug.cgi?id=872102 Hannes Reinecke <hare(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|hare(a)suse.com |jthumshirn(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 913996] Applying Critical Updates Causes System to no longer boot (ucode-intel / ucode-amd problem?)
by bugzilla_noreply＠novell.com 11 May '15

11 May '15

http://bugzilla.suse.com/show_bug.cgi?id=913996 --- Comment #92 from James Moe <jimoe(a)sohnen-moe.com> --- $ setpci -s 18.3 0x188.l 00400000 $ cat /proc/cpuinfo ((See attachment)) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 913996] Applying Critical Updates Causes System to no longer boot (ucode-intel / ucode-amd problem?)
by bugzilla_noreply＠novell.com 11 May '15

11 May '15

http://bugzilla.suse.com/show_bug.cgi?id=913996 James Moe <jimoe(a)sohnen-moe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jimoe@sohnen-moe. | |com) | --- Comment #91 from James Moe <jimoe(a)sohnen-moe.com> --- Created attachment 633876 --> http://bugzilla.suse.com/attachment.cgi?id=633876&action=edit /proc/cpuinfo CPU info for asus m3a78-em + AMD CPU. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 913996] Applying Critical Updates Causes System to no longer boot (ucode-intel / ucode-amd problem?)
by bugzilla_noreply＠novell.com 11 May '15

11 May '15

http://bugzilla.suse.com/show_bug.cgi?id=913996 --- Comment #90 from Borislav Petkov <bpetkov(a)suse.com> --- (In reply to James Moe from comment #89) > On 2015-05-03 I upgraded our main server. It has the same motherboard as the > other systems (asus m3a78-em) with the AMD CPU 630 4-core. Can get me /proc/cpuinfo from that box and do the setpci command on it too? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 908454] New: get_kernel_version does not support zImage
by bugzilla_noreply＠novell.com 11 May '15

11 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=908454 Bug ID: 908454 Summary: get_kernel_version does not support zImage Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: armv7 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: josua.m(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- /usr/bin/get_kernel_version program can not extract the version from zImages. This prevents mkinitrd from detecting a kernel and creating a ramdisk when run without arguments, on ARM. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 913996] Applying Critical Updates Causes System to no longer boot (ucode-intel / ucode-amd problem?)
by bugzilla_noreply＠novell.com 11 May '15

11 May '15

http://bugzilla.suse.com/show_bug.cgi?id=913996 --- Comment #89 from James Moe <jimoe(a)sohnen-moe.com> --- On 2015-05-03 I upgraded our main server. It has the same motherboard as the other systems (asus m3a78-em) with the AMD CPU 630 4-core. It has exhibited the same microcode issue as the other systems but with a more restrictive twist. Disabling the modules ucode-intel and ucode-amd in the Software Manager was not sufficient to prevent a catatonic system. It is a necessary requirement to include "dis_ucode_ldr" in the kernel parameters at boot time (GRUB2). -- You are receiving this mail because: You are on the CC list for the bug.

1 0