[Bug 750798] New: installation: final restart does not work
https://bugzilla.novell.com/show_bug.cgi?id=750798 https://bugzilla.novell.com/show_bug.cgi?id=750798#c0 Summary: installation: final restart does not work Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bluedzins@wp.pl QAContact: jsrain@suse.com Found By: --- Blocker: --- installation: final restart does not work At the end of the installation process, if I am not mistaken, there is restart performed. Tested on MacBook Pro (OS 64-bit) and Dell Latitude D610 (OS 32-bit) -- it does not work. For Mac, there is black screen and nothing, for Dell there is "white noise" (ok, it is not technically speaking), static, and nothing. I can tell, then in case of Dell something works, because if I press keys, the pattern of "noise" changes. However, bottom line is -- it does not 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=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c
kk zhang
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c1
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c2
Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c3
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c4
Tony Jones
I am unable to perform regular power off, because computer is not operational, so I have to make cold power down.
Then I power it on and second stage installation kicks in. I can say, that both installation after that point were successful.
Are you able to perform kexec on this hardware outside of the install system ... I think this is going to be the best chance of finding the problem, most likely using a serial console. Obviously for most the installer/kexec case is working fine. -- 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=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c5
Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c6
--- Comment #6 from Tony Jones
With what arguments I should run kexec to mimic the installer restart?
looking at yast2.installer, it does: cmd = sformat("kexec -l --command-line='%1' --initrd='%2' '%3'", String::Quote (kernel_args), String::Quote (initrd), String::Quote (vmlinuz)); y2milestone("Calling kexec via command: %1", cmd); So I would try the following two commands: # kexec -l --command-line="`cat /proc/cmdline`" --initrd=/boot/initrd-`uname -r` /boot/vmlinuz-`uname -r` # kexec -e The above succeeds on my test system. If it fails on your system without any obvious diagnostic then I will probably want you to repeat it with a serial console. If it succeeds on your system then it would be interesting to know what the command was that y2milestone logged, assuming you still have or can recreate the logfile. -- 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=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c
Tony Jones
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c7
Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c8
--- Comment #8 from Tony Jones
From the manpage:
It's also possible to invoke kexec without an option parameter. In that case, kexec loads the specified kernel and then invokes shutdown(1). If the shutdown scripts of your Linux distribution support kexec-based rebooting, they then call kexec -e just before actually rebooting the machine. I expect if you try it from the booted system it will yield better results, i.e kexec --command-line="`cat /proc/cmdline`" --initrd=/boot/initrd-`uname -r` /boot/vmlinuz-`uname -r` I wonder if the installation system isn't set up for this option, I will have to check. -- 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=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c9
--- Comment #9 from Maciej Pilichowski
kexec -l/-e makes no attempt to clean up hardware before transitioning to the new kernel
So it is not suitable for installation then, because there is no way for interacting with the process of booting, if anything goes bad, for example entering the password -- how am I to enter anything if my display is broken.
I expect if you try it from the booted system
I did -- see above. If I may -- "premature optimization is root of evil". This is textbook case. Seconds saved on booting up computer, and it does not even work for old hardware (Mac is mid 2009, Dell is around 2004), "troubles" with incoming computers are simple middle name of entire concept, for this report we already lost more time than bunch of seconds. So why installer does not use plain and simple restart, without all this "optimization"? There is enough problems with OS, why bringing more? After all, installation is done once, I would understand speeding up booting up installed system, but installer... My 2 cents for consideration. -- 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=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c10
--- Comment #10 from Tony Jones
kexec -l/-e makes no attempt to clean up hardware before transitioning to the new kernel ..... I expect if you try it from the booted system
I did -- see above.
Re-read xomment #8. That second command was different. Look closely. No -l option. I would expect that since it runs through the shutdown sequence that it should work correctly on your hardware. Obviously it's not what the installation system uses.
If I may -- "premature optimization is root of evil". This is textbook case. Seconds saved on booting up computer, and it does not even work for old hardware (Mac is mid 2009, Dell is around 2004), "troubles" with incoming computers are simple middle name of entire concept, for this report we already lost more time than bunch of seconds.
As I said, I will check. I was not responsible for the package when the decision was made. -- 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=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c11
--- Comment #11 from Maciej Pilichowski
Re-read xomment #8. That second command was different.
Indeed, ok, this time for Mac it worked. Now, for Mac it was installation. For Dell it was an update of the system. Because of this bug: https://bugzilla.novell.com/show_bug.cgi?id=750796 even with the changed arguments, I suspect in case of update of the system, such quick restart might won't 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=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c12
Tony Jones
Ok, so restart was done.
BUT -- what happened is, immediately after "kexec -e" the display "crashed", instead of anything meaningful top of the monitor was filled with "noise". Then I pressed some keys, and "noise" changed. So I waited a bit, and after few seconds desktop loaded.
To confirm. This is therefore different than your install experience? From the initial comment it appears that the system never "reboots" after the install, no matter how long you waited? (In reply to comment #11)
Re-read xomment #8. That second command was different.
Indeed, ok, this time for Mac it worked.
Thanks for the reply. I'm looking at the issue. I'll try and come up with some better steps for us to gather useful data. I'm thinking it would be useful to get your system temporarily using the same graphics setup as the installer and to then capture dmesg output for a normal boot vs a kexec. See if there is any difference.
Now, for Mac it was installation. For Dell it was an update of the system. Because of this bug: https://bugzilla.novell.com/show_bug.cgi?id=750796
This seems a totally different issue. -- 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=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c13
--- Comment #13 from Tony Jones
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c14
--- Comment #14 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750796 This seems a totally different issue.
It just explain why I could wait till death to get X-server running. Simply restart for updated computer stuck at selecting wrong OS. Btw. I didn't waited I don't know how log -- simply my patience ran out, and I simply made cold shutdown. It is not that the system could not recover, it is sufficient that with broken graphic mode it waited for some answer, or anything like that. -- 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=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c15
--- Comment #15 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c16
--- Comment #16 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c17
--- Comment #17 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c18
--- Comment #18 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c19
--- Comment #19 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c20
--- Comment #20 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c21
Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c22
kk zhang
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c23
Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c24
Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c25
Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c26
--- Comment #26 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=750798
https://bugzilla.novell.com/show_bug.cgi?id=750798#c27
--- Comment #27 from Tony Jones
For first command I got error:
Cannot open /boot/vmlinuz-3.4.6-2.10-default: (null) Cannot open /boot/vmlinuz-3.4.6-2.10-default: No such file or directory
I doubt /boot/vmlinuz-`uname -r` exists the installation environment, so obviously the command isn't going to succeed. This sample command was given to execute post install. You'll have to adjust for the installation environment. -- 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