https://bugzilla.novell.com/show_bug.cgi?id=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c1 --- Comment #1 from Elmar Stellnberger 2013-10-15 13:19:07 UTC --- Created an attachment (id=563509) --> (http://bugzilla.novell.com/attachment.cgi?id=563509) yast2 log package as produced by save_y2logs -- 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=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c3 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com --- Comment #3 from Arvin Schnell 2013-10-15 14:46:48 UTC --- Some commands for probing need very long, e.g. "blkid" needs 2451s, "btrfs filesystem show" needs 39s and "mdadm --examine --scan" 184s. I suspect a kernel driver problem when accessing a certain device. -- 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=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c5 --- Comment #5 from Elmar Stellnberger 2013-10-15 20:42:31 UTC --- Arvin, it would be really nice if we could do something about it. What shall I do? -- 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=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c7 --- Comment #7 from Elmar Stellnberger 2013-10-16 14:12:18 UTC --- Unfortunately this way I could not reproduce any hang. There must either have been used some other command line parameters or it was a totally different command that hung. -- 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=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c9 --- Comment #9 from Elmar Stellnberger 2013-10-16 15:18:37 UTC --- Unfortunately this did not do the trick (at least not by executing it normally under the console at runlevel 3). Even grub-install - the bootloader installation was known to cause another hang - did not cause a hang no more. The third hang was somewhere during normal package isntallation (you may also see for these issues in the final log). However I guess we can not reproduce it unless I boot into the installation system again. Too bad that we won`t even have an strace utility there. Arvin; can we still do something about it? -- 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=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c11 Alex Armstrong changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |AlexRArmstrong@gmail.com --- Comment #11 from Alex Armstrong 2013-10-23 18:01:05 UTC --- I also noticed that detecting other Linux partitions took longer than I expected. Though in my case it only took several minutes and not an hour. At the time I attributed this to my setup of two SATA HDDs in a RAID 0 (stripping) configuration. -A -- 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=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c13 --- Comment #13 from Elmar Stellnberger 2013-11-10 18:06:24 UTC --- Created an attachment (id=566799) --> (http://bugzilla.novell.com/attachment.cgi?id=566799) stderr messages on stracing blkid -- 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=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c Elmar Stellnberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|estellnb@elstel.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=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c16 Elmar Stellnberger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |jeffm@suse.com |ovo.novell.com | --- Comment #16 from Elmar Stellnberger 2014-01-04 11:27:28 UTC --- Jeff, would you have a look at the mdadm.log and why the command invocation lasts for so long? Any other information I could provide? -- 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=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c18 --- Comment #18 from Elmar Stellnberger 2014-01-12 14:21:21 UTC --- In deed fd0 is only at installation time in /proc/partitions; when normally booting into kernel 3.11.6-4-desktop it is not there (Perhaps I should also test it with the -default variant). -- 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=846001 https://bugzilla.novell.com/show_bug.cgi?id=846001#c20 --- Comment #20 from Scott Couston 2014-03-19 09:52:59 EST --- With 13.1 I have several problems I'll summarise specially in regard to X_64 architecture and BIOS recognition. 1. The suggested default partitioning made by 13.1 cannot determine if the BIOS has or has not /boot/efi demands. It treats all X_64 BIOS the same. On my X_64 which has no BIOS UEFI mode the partitioner cant tell if the BIOS has or nas not an extended UEFI mode. 2. The partitioner once overridden with a user defined partition setup issues warnings and almost demands /boot/efi regardless. 3. Further warnings that when the user makes sound decision to use a particular drive which has not the correct label based on the non presence of a NTFS label being present issues warning after warning based solely on the Drives Label. These are all reproducible and I have previously summarised in great deal. The time delay is a reflection on the base on the rated FLOPS of the CPU which could be anything from 5 mins in my experience to over an hour on I586/686 CPU as is this and other bug duplicates. Once installed any disparity that exists based on the user accepting the auto proposed partitioning yields an unusable O/S based on the auto bootloader info. Once installed with sound reasoning in partitioning the drives based of BIOS and X_64 architecture the auto bootloader yields an unusable stable O/S. Other issues of a 13.1 fully online updated, given that the user can get that far are SHOWSTOPPER and I wont use 13.1 period and my humble un-emotive conclusion is that 13.1 should be simply expunged. It should not have never got past alpha testing on just 1 X_64 PC there is just way way too many things wrong with the O/S after default install to even gain access to online updates...Just expunge it...and I have never in my life recommend to the same conclusion...Im really 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.