https://bugzilla.novell.com/show_bug.cgi?id=828377 https://bugzilla.novell.com/show_bug.cgi?id=828377#c2 --- Comment #2 from Matt McCann 2013-07-09 01:06:45 UTC --- https://forums.opensuse.org/english/get-technical-help-here/tumbleweed/48354... This thread was the original conversation on 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=828377 https://bugzilla.novell.com/show_bug.cgi?id=828377#c3 Joey Lee changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |matt.mccann.8@gmail.com --- Comment #3 from Joey Lee 2013-07-16 02:32:04 UTC --- Hi Matt, Does this issue also happen on v3.10 vanilla kernel? I asked because there have wall EFI clock change in v3.8 kernel but it should make things on Asus machine better but not brick it. On the other hand, that also strange for remove SSD could recover the problem. 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=828377 https://bugzilla.novell.com/show_bug.cgi?id=828377#c5 Joey Lee changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|matt.mccann.8@gmail.com | --- Comment #5 from Joey Lee 2013-07-16 03:03:15 UTC --- (In reply to comment #4)

(In reply to comment #3)

...

Hi Matt,

Does this issue also happen on v3.10 vanilla kernel?

I asked because there have wall EFI clock change in v3.8 kernel but it should make things on Asus machine better but not brick it. On the other hand, that also strange for remove SSD could recover the problem.

Thanks

Joey,

Unfortunately, I didn't try the vanilla kernel prior to my latest fresh install. Once I got the machine to a useable state I left it on the stock 3.7 desktop kernel. I can't do it just now as I need the machine to be useable, but hopefully in early August I will have time where I can test new kernels and see what happens.

Best, Matt

Thanks for your quick response. As far as i know the only possible issue causes brick machine is the flash space of EFI variables full but BIOS didn't trigger garbage collection. But it's not make sense remove SSD could rescued machine back. -- 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=828377 https://bugzilla.novell.com/show_bug.cgi?id=828377#c7 --- Comment #7 from Matt McCann 2013-07-16 04:07:25 UTC --- (In reply to comment #6)

(( OOPs, mid air collision ... resend. ))

In openSUSE, updating kernel will trigger mkinitrd and in turn performs bootloader update that will also manipulate efi boot variables as a side effect.

Actually, for kernel update, any re-installation of bootloader is unneeded and merely a waste of cpu cycles , all we need is only update the bootloader config to reflect the kernel changes (and that's solely the purpose of running update-bootloader for mkinitrd).

Anyway above could be off-topic, but it reveals some potential causes to this problem, the (although unintended) uefi variable update accompanying with kernel update process, as well as re-installation of grub and it's config to the EFI System Partition.

What I'm not clear from your report is whether you could boot into the problematic kernel (>3.7 series) by reconnecting the drive, for doing some tests and grabbing some logs to narrow down the cause ?

Thanks.

Michael, No I was not able to boot into the system after reconnecting the drive. The system recognized the drive, but dumped me straight into the UEFI/Bios and wouldn't allow me to boot to the SSD. I was only able to boot to the SSD after a full re-installation of openSUSE from a USB stick. Though I am no expert, from reading through various posts etc. it seemed like my issue had something to do with the updating of the bootloader/altering the EFI partition and not necessarily the kernel itself, but as you mentioned, installing a new kernel in openSUSE will trigger such an update which is why I reported it as a kernel bug. At first I was worried I had an issue similar to the Samsung laptop issue that was actually bricking laptops. Best, Matt -- 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=828377 https://bugzilla.novell.com/show_bug.cgi?id=828377#c9 --- Comment #9 from Matt McCann 2013-07-17 21:06:07 UTC --- (In reply to comment #8)

(In reply to comment #7)

...

(In reply to comment #6)

...

No I was not able to boot into the system after reconnecting the drive. The system recognized the drive, but dumped me straight into the UEFI/Bios and wouldn't allow me to boot to the SSD. I was only able to boot to the SSD after a full re-installation of openSUSE from a USB stick.

Looks really like ESP somehow contaminated. Or the EFI Boot Manager has problem in booting the boot loaders (could the boot variable somehow destroyed or some other changes in hardware configuration .. ??)

...

Though I am no expert, from reading through various posts etc. it seemed like my issue had something to do with the updating of the bootloader/altering the EFI partition and not necessarily the kernel itself, but as you mentioned,

Yes, I'm also suspecting it ..

Would you mind to run stress mkinitrd/reboot cycle on your up-and-running 3.7 kernel to see what's happened ??

...

installing a new kernel in openSUSE will trigger such an update which is why I reported it as a kernel bug. At first I was worried I had an issue similar to the Samsung laptop issue that was actually bricking laptops.

Yes, you're right. This is also pretty much kernel bug per the report. What I'm feeling not right is that we can avoid the mess of identifying kernel or bootloader update process if we do things right. Now we are taking extra effort in segregating them. :(

Thanks, Michael

...

Best, Matt

How do I go about doing a mkinitrd/reboot cycle stress test? Thanks. Best, Matt -- 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=828377 https://bugzilla.novell.com/show_bug.cgi?id=828377#c11 --- Comment #11 from Matt McCann 2013-07-20 16:39:46 UTC --- (In reply to comment #10)

(In reply to comment #9)

...

How do I go about doing a mkinitrd/reboot cycle stress test? Thanks.

Run the two commands several times (can't exactly tell how much times, 3 - 5 should suffice ..)

$ mkinitrd $ reboot

This is to simulate the bootloader update happened during kernel update. If we passed the test that means this is a kernel regression bug, otherwise not.

Thanks.

I'll give it a go and report back. 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=828377 https://bugzilla.novell.com/show_bug.cgi?id=828377#c13 --- Comment #13 from Joey Lee 2013-07-25 14:47:03 UTC --- (In reply to comment #12)

So I decided to try the latest and greatest kernel on my Zenbook to see what happens. I compiled the 3.11-RC2 kernel from kernel.org. It compiled and installed without issue. The system also boots after repeated restarts. It seems there is no corruption occurring. I then compiled the 3.10.2 kernel and also did not have issues.

Thanks for your testing result, I will check anything about EFI and EFI variable filesystem from v3.7 to v3.10. -- 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.