Launchpad has imported 31 comments from the remote bug at https://bugzilla.suse.com/show_bug.cgi?id=1035601.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-04-23T14:57:15+00:00 miko wrote: KDE Plasma Version :5.9.4 KDE Frameworks Version 5.32.0 Qt Version 5.7.1 Kernel Version : 4.10.9-1 default Intel Core i5-3337U Intel HD Graphics 4000 I own a Samsung Ativ Book 9 running Opensuse Tumbleweed. I have this problem with the random freezes when i'm watching videos.Screen,keyboard and mouse freezes and sometimes the caps lock light flashes.Not responding to terminal switch.Last 2 seconds of sound repeats forever. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/0 ------------------------------------------------------------------------ On 2017-04-23T16:57:21+00:00 miko wrote: https://s29.postimg.org/kyi3ym653/DSC_0008.jpg https://s29.postimg.org/dwk6cf2jb/DSC_0009.jpg https://s29.postimg.org/b3qyse26v/DSC_0010.jpg https://s29.postimg.org/cwtvgpndj/DSC_0011.jpg Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/1 ------------------------------------------------------------------------ On 2017-04-24T14:27:31+00:00 Tiwai-r wrote: Could you give hwinfo output, and also the output of dmesg after the fresh boot? The screenshots show one MCE log, and two flaky USB responses, and one harmless error message. But your reported issue sounds rather like a kernel panic, and these might be a red herring. It 'd be best if you can catch the crash via kdump... Put Boris to Cc for the MCE issue. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/2 ------------------------------------------------------------------------ On 2017-04-24T16:38:53+00:00 miko wrote: Created attachment 722365 hwinfo outpout Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/3 ------------------------------------------------------------------------ On 2017-04-24T16:45:45+00:00 miko wrote: Created attachment 722366 dmesg Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/4 ------------------------------------------------------------------------ On 2017-04-24T16:49:43+00:00 miko wrote: (In reply to Takashi Iwai from comment #2) > Could you give hwinfo output, and also the output of dmesg after the fresh > boot? > > The screenshots show one MCE log, and two flaky USB responses, and one > harmless error message. But your reported issue sounds rather like a kernel > panic, and these might be a red herring. It 'd be best if you can catch the > crash via kdump... > > Put Boris to Cc for the MCE issue. I do not know if i am doing something wrong or just it can not be catched by kdump I tried Intel Microcode but it keeps crashing.Memtest is clean. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/5 ------------------------------------------------------------------------ On 2017-04-24T17:00:04+00:00 Bpetkov wrote: And it freezes always when you watch videos? Because the MCE is what causes the system to freeze, AFAICT: Hardware event. This is not a software error. CPU 0 BANK 4 TIME 1492965186 Sun Apr 23 18:33:06 2017 MCG status:RIPV MCIP MCi status: Uncorrected error Error enabled Processor context corrupt MCA: Internal unclassified error: 402 STATUS b200000000100402 MCGSTATUS 5 CPUID Vendor Intel Family 6 Model 58 SOCKET 0 APIC 0 microcode 1c Unfortunately, the decoder doesn't tell us a whole lot: MCA: Internal unclassified error: 402 Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/6 ------------------------------------------------------------------------ On 2017-04-24T17:10:17+00:00 miko wrote: (In reply to Borislav Petkov from comment #6) > And it freezes always when you watch videos? > > Because the MCE is what causes the system to freeze, AFAICT: > > Hardware event. This is not a software error. > CPU 0 BANK 4 > TIME 1492965186 Sun Apr 23 18:33:06 2017 > MCG status:RIPV MCIP > MCi status: > Uncorrected error > Error enabled > Processor context corrupt > MCA: Internal unclassified error: 402 > STATUS b200000000100402 MCGSTATUS 5 > CPUID Vendor Intel Family 6 Model 58 > SOCKET 0 APIC 0 microcode 1c > > Unfortunately, the decoder doesn't tell us a whole lot: > > MCA: Internal unclassified error: 402 By the time i installed iucode-tool it crashes without watching videos.Much more often Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/7 ------------------------------------------------------------------------ On 2017-04-24T17:33:10+00:00 Bpetkov wrote: (In reply to miko sabor from comment #7) > By the time i installed iucode-tool it crashes without watching videos.Much > more often Can you make a picture of the screen right after it crashes and upload it? Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/8 ------------------------------------------------------------------------ On 2017-04-24T17:43:29+00:00 miko wrote: (In reply to Borislav Petkov from comment #8) > (In reply to miko sabor from comment #7) > > By the time i installed iucode-tool it crashes without watching videos.Much > > more often > > Can you make a picture of the screen right after it crashes and upload > it? https://www.dropbox.com/sh/eprgx1jl71bmw4a/AAD-MgCYMMzjK18iD4nF- Ur7a?dl=0 Nothing special with the screen immediately after the freeze.Caps lock blinking and nothing reacting.Sometimes it reboots sometimes no. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/9 ------------------------------------------------------------------------ On 2017-04-24T17:58:58+00:00 Bpetkov wrote: (In reply to miko sabor from comment #9) > Nothing special with the screen immediately after the freeze.Caps lock > blinking and nothing reacting.Sometimes it reboots sometimes no. Ok, without changing anything else, start the machine, enter grub and add "dis_ucode_ldr" at the kernel command line. Then boot and see if it generates that same MCE. Do a photo again if you can't log into the box, otherwise send dmesg again. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/10 ------------------------------------------------------------------------ On 2017-04-24T18:20:54+00:00 miko wrote: Created attachment 722391 dmesg Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/11 ------------------------------------------------------------------------ On 2017-04-24T18:38:04+00:00 Bpetkov wrote: Ok, can you watch videos without the freezing now? Is the box stable? Also, please do this as root: # modprobe msr cpuid # zypper install msr-tools cpuid and do # wrmsr -a 0x8b 0 # for i in $(seq 0 $(cut -d- -f2 /sys/devices/system/cpu/online)); do cpuid -1r | grep 0x00000001; done # rdmsr -a 0x8b and send me that whole output. Ask if something's not clear. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/12 ------------------------------------------------------------------------ On 2017-04-24T19:00:44+00:00 miko wrote: linux-qf8a:/home/miko # wrmsr -a 0x8b 0 linux-qf8a:/home/miko # for i in $(seq 0 $(cut -d- -f2 /sys/devices/system/cpu/online)); do cpuid -1r | grep 0x00000001; done 0x00000001 0x00: eax=0x000306a9 ebx=0x03100800 ecx=0x7dbae3bf edx=0xbfebfbff 0x0000000b 0x00: eax=0x00000001 ebx=0x00000002 ecx=0x00000100 edx=0x00000003 0x0000000d 0x01: eax=0x00000001 ebx=0x00000000 ecx=0x00000000 edx=0x00000000 0x80000001 0x00: eax=0x00000000 ebx=0x00000000 ecx=0x00000001 edx=0x28100800 0x00000001 0x00: eax=0x000306a9 ebx=0x03100800 ecx=0x7dbae3bf edx=0xbfebfbff 0x0000000b 0x00: eax=0x00000001 ebx=0x00000002 ecx=0x00000100 edx=0x00000003 0x0000000d 0x01: eax=0x00000001 ebx=0x00000000 ecx=0x00000000 edx=0x00000000 0x80000001 0x00: eax=0x00000000 ebx=0x00000000 ecx=0x00000001 edx=0x28100800 0x00000001 0x00: eax=0x000306a9 ebx=0x01100800 ecx=0x7dbae3bf edx=0xbfebfbff 0x0000000b 0x00: eax=0x00000001 ebx=0x00000002 ecx=0x00000100 edx=0x00000001 0x0000000b 0x01: eax=0x00000004 ebx=0x00000004 ecx=0x00000201 edx=0x00000001 0x0000000d 0x01: eax=0x00000001 ebx=0x00000000 ecx=0x00000000 edx=0x00000000 0x80000001 0x00: eax=0x00000000 ebx=0x00000000 ecx=0x00000001 edx=0x28100800 0x00000001 0x00: eax=0x000306a9 ebx=0x03100800 ecx=0x7dbae3bf edx=0xbfebfbff 0x0000000b 0x00: eax=0x00000001 ebx=0x00000002 ecx=0x00000100 edx=0x00000003 0x0000000d 0x01: eax=0x00000001 ebx=0x00000000 ecx=0x00000000 edx=0x00000000 0x80000001 0x00: eax=0x00000000 ebx=0x00000000 ecx=0x00000001 edx=0x28100800 linux-qf8a:/home/miko # rdmsr -a 0x8b 1700000000 1700000000 1700000000 1700000000 Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/13 ------------------------------------------------------------------------ On 2017-04-24T19:01:31+00:00 miko wrote: (In reply to Borislav Petkov from comment #12) > Ok, can you watch videos without the freezing now? Is the box stable? > > Also, please do this as root: > > # modprobe msr cpuid > # zypper install msr-tools cpuid > > and do > > # wrmsr -a 0x8b 0 > # for i in $(seq 0 $(cut -d- -f2 /sys/devices/system/cpu/online)); do cpuid > -1r | grep 0x00000001; done > # rdmsr -a 0x8b > > and send me that whole output. > > Ask if something's not clear. > > Thanks. Forgot to mention it freezed again Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/14 ------------------------------------------------------------------------ On 2017-04-24T20:53:21+00:00 Bpetkov wrote: (In reply to miko sabor from comment #14) > Forgot to mention it freezed again even with 'dis_ucode_ldr' on the command line? If so, then the microcode update has only influence on the frequency of the failure. Ok, let's try this: boot with "mce=3" on the kernel command line. Then try to reproduce the freeze. This time the machine should hopefully not panic and freeze but print the MCE in dmesg and we can see it at the time it happens. And it would hopefully contain more info then. Then, if you're still able, catch dmesg and upload it. If not, try to do a photo. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/15 ------------------------------------------------------------------------ On 2017-04-24T21:02:32+00:00 miko wrote: (In reply to Borislav Petkov from comment #15) > (In reply to miko sabor from comment #14) > > Forgot to mention it freezed again > > even with 'dis_ucode_ldr' on the command line? > > If so, then the microcode update has only influence on the frequency of > the failure. > > Ok, let's try this: boot with "mce=3" on the kernel command line. Then > try to reproduce the freeze. This time the machine should hopefully not > panic and freeze but print the MCE in dmesg and we can see it at the > time it happens. And it would hopefully contain more info then. > > Then, if you're still able, catch dmesg and upload it. If not, try to do > a photo. > > Thanks. https://www.dropbox.com/s/wlqjkvtt1xzpavv/DSC_0015.JPG?dl=0 That is the error i got this time with the "dis_ucode_ldr" i will now proceed to the mce=3 Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/16 ------------------------------------------------------------------------ On 2017-04-26T17:37:30+00:00 miko wrote: Again MCE error.What drives me crazy is that it works perfect with Windows OS Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/17 ------------------------------------------------------------------------ On 2017-04-26T22:13:24+00:00 Bpetkov wrote: (In reply to miko sabor from comment #17) > Again MCE error. with "mce=3"? Can you upload full dmesg with it? > What drives me crazy is that it works perfect with Windows OS Well, it could be that the GPU driver is causing those and the windoze GPU driver doesn't. But we still can't pinpoint with certainty which hw part causes it so the GPU driver is just a conjecture. But since you said it happens while watching videos then the GPU looks likely... Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/18 ------------------------------------------------------------------------ On 2017-04-26T22:55:15+00:00 miko wrote: (In reply to Borislav Petkov from comment #18) > (In reply to miko sabor from comment #17) > > Again MCE error. > > with "mce=3"? > > Can you upload full dmesg with it? > > > What drives me crazy is that it works perfect with Windows OS > > Well, it could be that the GPU driver is causing those and the windoze > GPU driver doesn't. But we still can't pinpoint with certainty which hw > part causes it so the GPU driver is just a conjecture. But since you > said it happens while watching videos then the GPU looks likely... I will try to catch the error to the dmesg next time it will freeze. One of my thoughts is..what if the microcode is not "booted" in the startup.Maybe i need to add something on the kernel command line parameter to start the intel-ucode.You previously mentioned this "dis_ucode_ldr".Is there any intel specific one? Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/19 ------------------------------------------------------------------------ On 2017-04-27T09:22:31+00:00 Bpetkov wrote: (In reply to miko sabor from comment #19) > One of my thoughts is..what if the microcode is not "booted" in the > startup. We've seen that the microcode doesn't have any influence on this as you see the error regardless whether microcode was updated or not. Make sure to boot with "mce=3" and catch dmesg after the error happens. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/20 ------------------------------------------------------------------------ On 2017-04-27T09:35:26+00:00 Tiwai-r wrote: Just to be sure: try to trigger the crash manually to see whether your kdump setup really works, e.g. "echo c > /proc/sysrq-trigger" Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/21 ------------------------------------------------------------------------ On 2017-04-27T09:56:02+00:00 Bpetkov wrote: (In reply to Takashi Iwai from comment #21) > Just to be sure: try to trigger the crash manually to see whether your kdump > setup really works, e.g. "echo c > /proc/sysrq-trigger" No, please don't confuse him. The mce=3 setting should not panic the machine and I want to see the full MCE right after it got logged, not after a reboot. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/22 ------------------------------------------------------------------------ On 2017-04-28T22:07:22+00:00 miko wrote: Created attachment 723218 dmesg My dmesg is clean.The system freezes completely and i have to restart it by using the power button. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/23 ------------------------------------------------------------------------ On 2017-04-29T08:43:01+00:00 Bpetkov wrote: (In reply to miko sabor from comment #23) > The system freezes completely and i have to restart it by > using the power button. Even with mce=3 ? Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/24 ------------------------------------------------------------------------ On 2017-04-29T10:45:34+00:00 miko wrote: (In reply to Borislav Petkov from comment #24) > (In reply to miko sabor from comment #23) > > The system freezes completely and i have to restart it by > > using the power button. > > Even with mce=3 ? Yes. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/25 ------------------------------------------------------------------------ On 2017-04-29T18:47:48+00:00 Bpetkov wrote: Hmmkay. Looks like the severity grading says this error is fatal and we panic. Ok, please try this: 1. Boot with "mce=3" 2. As root do: # mount -t debugfs none /sys/kernel/debug # echo 1 > /sys/kernel/debug/mce/fake_panic # cat /sys/kernel/debug/mce/fake_panic 1 That last command verifies it accepted the setting. 3. Now, try to reproduce the MCE and keep watching dmesg in another window: # while true; do dmesg | tail -n 20 ; sleep 2s; done The moment you see the MCE, you do dmesg > log and upload that "log" file. The idea is to fake-panic the machine to be able to catch dmesg and send it out. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/26 ------------------------------------------------------------------------ On 2017-04-30T11:51:08+00:00 miko wrote: Created attachment 723247 dmesg made a completely fresh install on my system again on tumbleweed.booted with mce=3 and that's what i got Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/27 ------------------------------------------------------------------------ On 2017-04-30T12:12:10+00:00 Bpetkov wrote: That's no different from before. Please do the steps in comment #26 instead. It is important to try to reproduce it and catch it in dmesg *before* rebooting. My hope is that the MCE reported at that time would have more information as to pinpoint which device on your system is causing it. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/28 ------------------------------------------------------------------------ On 2017-05-01T14:08:08+00:00 miko wrote: Forgive me but i can not continue with this.It is getting to complicate for me!Thank you for the help until now ! Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/29 ------------------------------------------------------------------------ On 2017-05-01T20:03:14+00:00 Bpetkov wrote: Sorry to hear that. But ok, let me know if you change your mind. Closing for now. Reply at: https://bugs.launchpad.net/ubuntu/+bug/1687437/comments/32 ** Changed in: opensuse Importance: Unknown => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687437 Title: Unexpected system crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1687437/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
