[opensuse] MSI GE63 7RD : No openSUSE Leap 15?
Finally after a long search my selection for new laptop is the MSI GE63 7RD. Several internet tests were quite positive and -most important- it is very silent. Also the Ubuntu community said that these MSI laptops are quite "standard" stuff, only few tweaks, Optimus seems to be one thing to tweak. But: after having bought this machine I have to realize that openSUSE Leap 15 does not seem to be ready for this laptop (although amazon.de lists this machine since July 3rd 2017). There is a bunch of error messages when booting it up from USB after setting Secure boot to off and fast boot also. The worst one seems to be "NMI watchdog : BUG soft lockup CPU4 stuck for 22s!" afterwards SuSE15 seems to be stuck and I have to turn off by switch. I also tried tumbleweed on a USB stick - same error. Actually I was able to install Ubuntu 18.04 LTS with a tweak of bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi under Windows 10 because otherwise the grub boot manager is not shown. Everything else seems to work after doing that tweak with nVidia which is described in internet all over. Does this mean I have to say goodbye to SuSE on my Laptop? After approx 28 years using SuSE? :-/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30 June 2018 at 16:53, Markus Egg <Markus.Egg@a1.net> wrote:
Finally after a long search my selection for new laptop is the MSI GE63 7RD. Several internet tests were quite positive and -most important- it is very silent. Also the Ubuntu community said that these MSI laptops are quite "standard" stuff, only few tweaks, Optimus seems to be one thing to tweak.
But: after having bought this machine I have to realize that openSUSE Leap 15 does not seem to be ready for this laptop (although amazon.de lists this machine since July 3rd 2017).
There is a bunch of error messages when booting it up from USB after setting Secure boot to off and fast boot also.
The worst one seems to be "NMI watchdog : BUG soft lockup CPU4 stuck for 22s!" afterwards SuSE15 seems to be stuck and I have to turn off by switch. I also tried tumbleweed on a USB stick - same error.
Actually I was able to install Ubuntu 18.04 LTS with a tweak of bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi under Windows 10 because otherwise the grub boot manager is not shown. Everything else seems to work after doing that tweak with nVidia which is described in internet all over.
Does this mean I have to say goodbye to SuSE on my Laptop? After approx 28 years using SuSE? :-/
have you reported a bug report as documented here: https://en.opensuse.org/openSUSE:Bugreport_kernel ? Regards, -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 30 Jun 2018 17:19:40 +0200, Richard Brown wrote:
On 30 June 2018 at 16:53, Markus Egg <Markus.Egg@a1.net> wrote:
Does this mean I have to say goodbye to SuSE on my Laptop? After approx 28 years using SuSE? :-/
have you reported a bug report as documented here: https://en.opensuse.org/openSUSE:Bugreport_kernel ?
Hello: I find it ridiculous that that you expect bug reports from end users as if it was their obligation. Especially that one cannot just fill a from, he has to register first. Even more ridiculous that you expect end users to read the instructions you linked and report a bug according to that. Normal end users are unable to do that. That page is scary. I guess it even wouldn't be an easy task for developers and sysadmins either. What you are suggesting is nonsense. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Istvan Gabor <suseuser04@gmail.hu> [06-30-18 19:06]:
On Sat, 30 Jun 2018 17:19:40 +0200, Richard Brown wrote:
On 30 June 2018 at 16:53, Markus Egg <Markus.Egg@a1.net> wrote:
Does this mean I have to say goodbye to SuSE on my Laptop? After approx 28 years using SuSE? :-/
have you reported a bug report as documented here: https://en.opensuse.org/openSUSE:Bugreport_kernel ?
Hello:
I find it ridiculous that that you expect bug reports from end users as if it was their obligation. Especially that one cannot just fill a from, he has to register first.
Even more ridiculous that you expect end users to read the instructions you linked and report a bug according to that. Normal end users are unable to do that. That page is scary. I guess it even wouldn't be an easy task for developers and sysadmins either.
What you are suggesting is nonsense.
what obligation do you have? you utilize the sweat of others w/o remuneration and expect to return nothing? if everyone had that attitude there would be no openSUSE as no one would feel any obligation and there would be no effort expended. step up and do your part. it's not a terrible imposition and may provide much benefit to yourself and to others. surely you have not used openSUSE for 28 years and never contributed. if you actually have, why would you expect *anyone* to provide you with help? questions above do not require response, they are rhetorical, and not intended to start a flame ware. they are intended to invoke some thought and consideration. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 30 Jun 2018 19:34:01 -0400, Patrick Shanahan wrote:
* Istvan Gabor <suseuser04@gmail.hu> [06-30-18 19:06]:
On Sat, 30 Jun 2018 17:19:40 +0200, Richard Brown wrote:
On 30 June 2018 at 16:53, Markus Egg <Markus.Egg@a1.net> wrote:
Does this mean I have to say goodbye to SuSE on my Laptop? After approx 28 years using SuSE? :-/
have you reported a bug report as documented here: https://en.opensuse.org/openSUSE:Bugreport_kernel ?
Hello:
I find it ridiculous that that you expect bug reports from end users as if it was their obligation. Especially that one cannot just fill a from, he has to register first.
Even more ridiculous that you expect end users to read the instructions you linked and report a bug according to that. Normal end users are unable to do that. That page is scary. I guess it even wouldn't be an easy task for developers and sysadmins either.
What you are suggesting is nonsense.
what obligation do you have? you utilize the sweat of others w/o remuneration and expect to return nothing? if everyone had that attitude there would be no openSUSE as no one would feel any obligation and there would be no effort expended.
step up and do your part. it's not a terrible imposition and may provide much benefit to yourself and to others.
surely you have not used openSUSE for 28 years and never contributed. if you actually have, why would you expect *anyone* to provide you with help?
questions above do not require response, they are rhetorical, and not intended to start a flame ware. they are intended to invoke some thought and consideration.
Well, Patrick, it seems you tend to absolutely misinterpret statements and posts. You misinterpreted Linda's post earlier regarding her request on addressing mails. You also misinterpreted what I wrote but I will not explain it. I am sure there are others who get what I meant to say. Regards, Istvan ps: According to wikipedia article on SUSE Linux, the earliest SUSE Linux (which even was not an original distibution) came out in 1994, which is not 28 years ago. See: https://en.wikipedia.org/wiki/SUSE_Linux#History -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-07-01 01:01, Istvan Gabor wrote:
On Sat, 30 Jun 2018 17:19:40 +0200, Richard Brown wrote:
On 30 June 2018 at 16:53, Markus Egg <Markus.Egg@a1.net> wrote:
Does this mean I have to say goodbye to SuSE on my Laptop? After approx 28 years using SuSE? :-/
have you reported a bug report as documented here: https://en.opensuse.org/openSUSE:Bugreport_kernel ?
Hello:
I find it ridiculous that that you expect bug reports from end users as if it was their obligation. Especially that one cannot just fill a from, he has to register first.
Even more ridiculous that you expect end users to read the instructions you linked and report a bug according to that. Normal end users are unable to do that. That page is scary. I guess it even wouldn't be an easy task for developers and sysadmins either.
What you are suggesting is nonsense.
I'm sorry, but the only way to solve a kernel bug is to report it where the kernel people see it: in a bugzilla. Otherwise, you could package the laptop and send it to them. As things are, the email has close to no useful information to go by: not even logs. What do you expect them to do? Yes, the user vented some steam, but there is nothing that can be done about it. Sorry. So calm down and write the bugzilla with as much information as possible. People here will try to help, surely, but not if you start a fight. With time the problem may be solved. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Am 01/07/18 um 03:23 schrieb Carlos E. R.:
On 2018-07-01 01:01, Istvan Gabor wrote:
On Sat, 30 Jun 2018 17:19:40 +0200, Richard Brown wrote:
On 30 June 2018 at 16:53, Markus Egg <Markus.Egg@a1.net> wrote:
Does this mean I have to say goodbye to SuSE on my Laptop? After approx 28 years using SuSE? :-/
have you reported a bug report as documented here: https://en.opensuse.org/openSUSE:Bugreport_kernel ?
Hello:
I find it ridiculous that that you expect bug reports from end users as if it was their obligation. Especially that one cannot just fill a from, he has to register first.
Even more ridiculous that you expect end users to read the instructions you linked and report a bug according to that. Normal end users are unable to do that. That page is scary. I guess it even wouldn't be an easy task for developers and sysadmins either.
What you are suggesting is nonsense.
I'm sorry, but the only way to solve a kernel bug is to report it where the kernel people see it: in a bugzilla. Otherwise, you could package the laptop and send it to them.
As things are, the email has close to no useful information to go by: not even logs. What do you expect them to do? Yes, the user vented some steam, but there is nothing that can be done about it. Sorry.
It was not so much "steam", it was more a kind of feeling bad/sorry to leave SuSE after so many years (did not count exactly how many, it rather feels like a lot). Maybe there is a simple solution?
So calm down and write the bugzilla with as much information as possible.
That I will do as soon as I find time.
People here will try to help, surely, but not if you start a fight. With time the problem may be solved.
I do not have problems in filing bug reports, as I also did with the KDE5 workspace bug. BR -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-07-01 13:26, Markus Egg wrote:
Am 01/07/18 um 03:23 schrieb Carlos E. R.:
I do not have problems in filing bug reports, as I also did with the KDE5 workspace bug.
Good! So lets hope it can be solved :-) Did you read David C. Rankin post? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Istvan Gabor wrote:
On Sat, 30 Jun 2018 17:19:40 +0200, Richard Brown wrote:
On 30 June 2018 at 16:53, Markus Egg <Markus.Egg@a1.net> wrote:
Does this mean I have to say goodbye to SuSE on my Laptop? After approx 28 years using SuSE? :-/
have you reported a bug report as documented here: https://en.opensuse.org/openSUSE:Bugreport_kernel ?
Hello:
I find it ridiculous that that you expect bug reports from end users as if it was their obligation.
I think it _is_ their obligation. It is the best way an end-user can help openSUSE.
Especially that one cannot just fill a from, he has to register first.
Usually resolving a bug means repeated communication between reporter and openSUSE. Without registering, that isn't possible.
Even more ridiculous that you expect end users to read the instructions you linked and report a bug according to that. Normal end users are unable to do that. That page is scary. I guess it even wouldn't be an easy task for developers and sysadmins either.
You guess wrong. It takes about 5mins to open a good report, with a little practice.
What you are suggesting is nonsense.
What do you propose? -- Per Jessen, Zürich (21.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 01 Jul 2018 10:12:00 +0200 Per Jessen <per@computer.org> wrote:
Istvan Gabor wrote:
On Sat, 30 Jun 2018 17:19:40 +0200, Richard Brown wrote:
On 30 June 2018 at 16:53, Markus Egg <Markus.Egg@a1.net> wrote:
Does this mean I have to say goodbye to SuSE on my Laptop? After approx 28 years using SuSE? :-/
have you reported a bug report as documented here: https://en.opensuse.org/openSUSE:Bugreport_kernel ?
Hello:
I find it ridiculous that that you expect bug reports from end users as if it was their obligation.
I think it _is_ their obligation. It is the best way an end-user can help openSUSE.
Especially that one cannot just fill a from, he has to register first.
Usually resolving a bug means repeated communication between reporter and openSUSE. Without registering, that isn't possible.
Even more ridiculous that you expect end users to read the instructions you linked and report a bug according to that. Normal end users are unable to do that. That page is scary. I guess it even wouldn't be an easy task for developers and sysadmins either.
You guess wrong. It takes about 5mins to open a good report, with a little practice.
While I agree with the substance of your comments and those of other responders, I think it is worth pointing out that Istvan is questioning Richard for referring Markus to a page that says: "This document is intended for: "supporters and consultants, so they know how to provide useful and valuable bug reports. "developers, who need to know about debugging facilities provided by the Linux kernel" So it certainly seems reasonable to say that the page is not designed for end users.
What you are suggesting is nonsense.
What do you propose?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-07-01 10:41, Dave Howorth wrote:
On Sun, 01 Jul 2018 10:12:00 +0200 Per Jessen <> wrote:
Istvan Gabor wrote:
On Sat, 30 Jun 2018 17:19:40 +0200, Richard Brown wrote:
On 30 June 2018 at 16:53, Markus Egg <> wrote:
While I agree with the substance of your comments and those of other responders, I think it is worth pointing out that Istvan is questioning Richard for referring Markus to a page that says:
"This document is intended for:
"supporters and consultants, so they know how to provide useful and valuable bug reports. "developers, who need to know about debugging facilities provided by the Linux kernel"
So it certainly seems reasonable to say that the page is not designed for end users.
So it says, you are right. It also says: "Diagnosing a Kernel bug is a difficult task" However, the OP is experienced, by his own words: "approx 28 years using SuSE". He has not said he can't. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Dave Howorth wrote:
On Sun, 01 Jul 2018 10:12:00 +0200 Per Jessen <per@computer.org> wrote:
Istvan Gabor wrote:
On Sat, 30 Jun 2018 17:19:40 +0200, Richard Brown wrote:
On 30 June 2018 at 16:53, Markus Egg <Markus.Egg@a1.net> wrote:
Does this mean I have to say goodbye to SuSE on my Laptop? After approx 28 years using SuSE? :-/
have you reported a bug report as documented here: https://en.opensuse.org/openSUSE:Bugreport_kernel ?
Hello:
I find it ridiculous that that you expect bug reports from end users as if it was their obligation.
I think it _is_ their obligation. It is the best way an end-user can help openSUSE.
Especially that one cannot just fill a from, he has to register first.
Usually resolving a bug means repeated communication between reporter and openSUSE. Without registering, that isn't possible.
Even more ridiculous that you expect end users to read the instructions you linked and report a bug according to that. Normal end users are unable to do that. That page is scary. I guess it even wouldn't be an easy task for developers and sysadmins either.
You guess wrong. It takes about 5mins to open a good report, with a little practice.
While I agree with the substance of your comments and those of other responders, I think it is worth pointing out that Istvan is questioning Richard for referring Markus to a page that says:
"This document is intended for:
"supporters and consultants, so they know how to provide useful and valuable bug reports. "developers, who need to know about debugging facilities provided by the Linux kernel"
So it certainly seems reasonable to say that the page is not designed for end users.
Yeah, that is true. I overlooked the _kernel bit, I thought Richard had posted the usual link: https://en.opensuse.org/openSUSE:Submitting_bug_reports -- Per Jessen, Zürich (25.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 01/07/18 um 03:27 schrieb James Knott:
On 06/30/2018 10:53 AM, Markus Egg wrote:
After approx 28 years using SuSE?
You were using it a year before Linux was first released?
I was not counting the exact years, I just had the feeling of "a long good time" and "some time in the 90s" - something like that. Therefore "approx". ;-) Did a bit lookup and obviously it much was later, the SuSE 6.1 front picture http://krum.rz.uni-mannheim.de/linux-kurs-2001s/images/suse61.gif looks somehow familiar. That would have been after April 1999. Not so long as I thought. :-) Only 19 years. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/30/2018 09:53 AM, Markus Egg wrote:
The worst one seems to be "NMI watchdog : BUG soft lockup CPU4 stuck for 22s!"
No, it isn't scary, and it is quite common (though the message is generally "stuck for 23s"). google: "NMI watchdog : BUG soft lockup CPU stuck" You can read until you are content this isn't specific to your laptop. If you look at dmesg output that is simply an initialization issue usually associated with PCI bus and one of the Cores early in the boot process. Watchdog timers are specifically set to monitor the various initializations and to reset (or restart or kill) any process that gets stuck. Don't kill the boot. It will proceed after the watchdog timer handles the issue, but it will trigger a verification process that will loop over each core in your box to ultimately find out that everything is OK and then continue to boot. (THIS CAN TAKE 5 MINUTES) This is a kernel issue that appeared early in the 4.16.x set of releases and is also present in the 4.17 kernel for some hardware: Example: https://bugs.archlinux.org/task/59091 There is no guarantee this is your exact problem, but I suspect it is related. If you are able to boot after letting the box sit and sort itself out, then capture the dmesg output (e.g. open a terminal and...) $ dmesg > my_dmesg_output You can then view the my_dmesg_output and determine if this is related, and the output can be used as an attachment to any bug report (or posted to susepaste so others can attach it if needed to a bug report) Good luck, your hardware will work fine, it just may take sorting out a bug or two first. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 01/07/18 um 07:40 schrieb David C. Rankin:
On 06/30/2018 09:53 AM, Markus Egg wrote:
The worst one seems to be "NMI watchdog : BUG soft lockup CPU4 stuck for 22s!"
No, it isn't scary, and it is quite common (though the message is generally "stuck for 23s").
google: "NMI watchdog : BUG soft lockup CPU stuck"
You can read until you are content this isn't specific to your laptop.
I guessed that. :-)
If you look at dmesg output that is simply an initialization issue usually associated with PCI bus and one of the Cores early in the boot process. Watchdog timers are specifically set to monitor the various initializations and to reset (or restart or kill) any process that gets stuck.
Don't kill the boot. It will proceed after the watchdog timer handles the issue, but it will trigger a verification process that will loop over each core in your box to ultimately find out that everything is OK and then continue to boot. (THIS CAN TAKE 5 MINUTES)
I will try later. Afair I was not waiting 5mins.
This is a kernel issue that appeared early in the 4.16.x set of releases and is also present in the 4.17 kernel for some hardware:
Hmm, but SuSE Leap 15 has a 4.12.14 kernel afaik. Is that kernel too old for that hardware? Otoh you are right, I tried with tumbleweed and this also had the error messages (tried Snapshot20180625 so it should be kernel 4.17.X).
"X intermittent input event handling (mostly mouse) inside virtualbox" ? Rather looks similar to that one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769376
There is no guarantee this is your exact problem, but I suspect it is related. If you are able to boot after letting the box sit and sort itself out, then capture the dmesg output (e.g. open a terminal and...)
$ dmesg > my_dmesg_output
You can then view the my_dmesg_output and determine if this is related, and the output can be used as an attachment to any bug report (or posted to susepaste so others can attach it if needed to a bug report)
Good luck, your hardware will work fine, it just may take sorting out a bug or two first.
Currently the machine is running fine with Ubuntu 18.04 . BR -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-07-02 09:48, Markus Egg wrote:
Am 01/07/18 um 07:40 schrieb David C. Rankin:
This is a kernel issue that appeared early in the 4.16.x set of releases and is also present in the 4.17 kernel for some hardware:
Hmm, but SuSE Leap 15 has a 4.12.14 kernel afaik. Is that kernel too old for that hardware?
The kernel version used by Leap is not that relevant, because it is heavily patched by SLE people. So maybe they backported something from a much more modern kernel that brought this in. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 07/02/2018 2:06 AM, Carlos E. R. wrote:
On 2018-07-02 09:48, Markus Egg wrote:
Am 01/07/18 um 07:40 schrieb David C. Rankin:
This is a kernel issue that appeared early in the 4.16.x set of releases and is also present in the 4.17 kernel for some hardware:
Hmm, but SuSE Leap 15 has a 4.12.14 kernel afaik. Is that kernel too old for that hardware?
The kernel version used by Leap is not that relevant, because it is heavily patched by SLE people. So maybe they backported something from a much more modern kernel that brought this in.
More likely they FAILED to backport some critical fix or hardware driver which was added in later kernels. Hopefully the new Suse owners will straighten out this mindless backporting of patches to avoid re-certifying kernels for two customers. -- _____________________________________ ---This space for rent---
On 2018-07-02 23:04, John Andersen wrote:
On 07/02/2018 2:06 AM, Carlos E. R. wrote:
On 2018-07-02 09:48, Markus Egg wrote:
Am 01/07/18 um 07:40 schrieb David C. Rankin:
This is a kernel issue that appeared early in the 4.16.x set of releases and is also present in the 4.17 kernel for some hardware:
Hmm, but SuSE Leap 15 has a 4.12.14 kernel afaik. Is that kernel too old for that hardware?
The kernel version used by Leap is not that relevant, because it is heavily patched by SLE people. So maybe they backported something from a much more modern kernel that brought this in.
More likely they FAILED to backport some critical fix or hardware driver which was added in later kernels.
No, because previous kernels worked on his machine, obviously.
Hopefully the new Suse owners will straighten out this mindless backporting of patches to avoid re-certifying kernels for two customers.
Certainly not. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Am 03/07/18 um 10:50 schrieb Carlos E. R.:
On 2018-07-02 23:04, John Andersen wrote:
On 07/02/2018 2:06 AM, Carlos E. R. wrote:
On 2018-07-02 09:48, Markus Egg wrote:
Am 01/07/18 um 07:40 schrieb David C. Rankin:
This is a kernel issue that appeared early in the 4.16.x set of releases and is also present in the 4.17 kernel for some hardware:
Hmm, but SuSE Leap 15 has a 4.12.14 kernel afaik. Is that kernel too old for that hardware?
The kernel version used by Leap is not that relevant, because it is heavily patched by SLE people. So maybe they backported something from a much more modern kernel that brought this in.
More likely they FAILED to backport some critical fix or hardware driver which was added in later kernels.
No, because previous kernels worked on his machine, obviously.
No, on the MSI machine I never installed SuSE before. It is a laptop that I just bought recently. I was using SuSE on other machines. BR -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-07-05 22:19, Markus Egg wrote:
Am 03/07/18 um 10:50 schrieb Carlos E. R.:
On 2018-07-02 23:04, John Andersen wrote:
On 07/02/2018 2:06 AM, Carlos E. R. wrote:
On 2018-07-02 09:48, Markus Egg wrote:
Am 01/07/18 um 07:40 schrieb David C. Rankin:
This is a kernel issue that appeared early in the 4.16.x set of releases and is also present in the 4.17 kernel for some hardware:
Hmm, but SuSE Leap 15 has a 4.12.14 kernel afaik. Is that kernel too old for that hardware?
The kernel version used by Leap is not that relevant, because it is heavily patched by SLE people. So maybe they backported something from a much more modern kernel that brought this in.
More likely they FAILED to backport some critical fix or hardware driver which was added in later kernels.
No, because previous kernels worked on his machine, obviously.
No, on the MSI machine I never installed SuSE before. It is a laptop that I just bought recently.
I was using SuSE on other machines.
Oh, sorry, you did say that. Confusion. Then, maybe you should try leap 42.3 on it. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 07/05/2018 04:55 PM, Carlos E. R. wrote:
Oh, sorry, you did say that. Confusion.
Then, maybe you should try leap 42.3 on it.
I would second that. Boot 42.3, then collect dmesg and hwinfo information, that would give you some starting point and hopefully identify how your hardware is being seen by that kernel and init. Like the guy in the Archlinux bug report said (me) there is some change that was made to the kernel in the past 6-8 months (I don't know if that change has been backported to SLE or not), but whatever it is, it causes misidentification of a problem with the symptoms of NMI/CPU stall during init that throws the system into a NMI/CPU self-test, for lack of better words, that at least in my case (5 minutes later) results in the kernel figuring out that there is actually nothing wrong and the boot continues normally. In my case, I hit it with an older Supermicro H8DM8E-2 dual-quad-core board (which booted every kernel before 4.16.5 (or so) without issue and continues to boot earlier kernels fine) I have another Supermicro quad-quad-core board that is not effected. So this is a hit-or-miss issue, likely related to some code (or combination of codes) returned by some chipset during the init process. -- David C. Rankin, J.D.,P.E.
On 07/02/2018 02:48 AM, Markus Egg wrote:
"X intermittent input event handling (mostly mouse) inside virtualbox" ? Rather looks similar to that one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769376
Oops -- sorry, wrong link :) https://bugs.archlinux.org/task/58542 -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 03/07/18 um 04:20 schrieb David C. Rankin:
On 07/02/2018 02:48 AM, Markus Egg wrote:
"X intermittent input event handling (mostly mouse) inside virtualbox" ? Rather looks similar to that one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769376
Oops -- sorry, wrong link :)
Booting with the live USB from SuSE Leap 15 just ended with MSI laptop in a hanging state. No F-screens of course, no terminal. So I am note sure how I should do some "dmesg" like the guys did in the archlinux bugticket. Is there some way to enter a logging command on the grub screen of the live USB, which is written to the USB stick then? Did not find any hint on Internet. Just tried Leap 15 KDE Live on USB stick once more several "NMI watchdog: BUG: soft lockup - CPU0 stuck for 23s ! [plymouthd:468]" then "INFO: rcu_sched self-detected stall on CPU" "0-...:(14999 ticks this GP) idle=62e/1400...some zeros..1/0 softirq=1500/1500 fqs=7499 (t=15000 jiffies g=362 c=361 q=390) then some NMI watchdog again, 6 times then "INFO: rcu_sched self-detected stall on CPU" again and the tick message with different numbers. These messages simply repeat, partly with different numbers. Someone suggested to keep it running because it will sort out itself, but that does not occur. There is no terminal or whatsoever sign that it is coming back. I have to press the off-switch. I restarted the Leap 15 KDE Live USB stick this time entering "nomodeset" before "splash=silent" as with Ubuntu, and there is some KDE screen with low resolution coming up where I can get some dmesg output. What I see in this output: [ 5.772303] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170303/psargs-364) [ 5.772327] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.PRT1._GTF] (Node ffff88018fd94168), AE_NOT_FOUND (20170303/psparse-543) and later on during boot: ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared and ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared Shutdown even works in this case, which did not work with the first Ubuntu installation. Did anyone try to install SuSE from the Live USB stick on a MSI GE63? Does it make sense to try tumbleweed Live USB stick? BR -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Markus Egg wrote:
Booting with the live USB from SuSE Leap 15 just ended with MSI laptop in a hanging state. No F-screens of course, no terminal.
So I am note sure how I should do some "dmesg" like the guys did in the archlinux bugticket.
Yes, when you system is dead, there's no way to do that.
Is there some way to enter a logging command on the grub screen of the live USB, which is written to the USB stick then? Did not find any hint on Internet.
The only way I know of is to use a serial console. Your laptop probably doesn't have a serial port though :-(
Just tried Leap 15 KDE Live on USB stick once more several "NMI watchdog: BUG: soft lockup - CPU0 stuck for 23s ! [plymouthd:468]" then "INFO: rcu_sched self-detected stall on CPU" "0-...:(14999 ticks this GP) idle=62e/1400...some zeros..1/0 softirq=1500/1500 fqs=7499 (t=15000 jiffies g=362 c=361 q=390) then some NMI watchdog again, 6 times then "INFO: rcu_sched self-detected stall on CPU" again and the tick message with different numbers. These messages simply repeat, partly with different numbers.
Someone suggested to keep it running because it will sort out itself, but that does not occur.
I have also seen this problem in the past, and it only delayed things for bit, never led to a complete halt. Your situation is likely very different, even if the symptoms are similar.
I restarted the Leap 15 KDE Live USB stick this time entering "nomodeset" before "splash=silent" as with Ubuntu, and there is some KDE screen with low resolution coming up where I can get some dmesg output.
Wait - with nomodeset, your system does not grind to a halt? You have access? That seems to indicate a graphics driver issue? -- Per Jessen, Zürich (17.3°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-07-06 08:01, Per Jessen wrote:
Markus Egg wrote:
Is there some way to enter a logging command on the grub screen of the live USB, which is written to the USB stick then? Did not find any hint on Internet.
The only way I know of is to use a serial console. Your laptop probably doesn't have a serial port though :-(
Also via ethernet. I think I heard something about the usb bus, but I'm not sure.
I restarted the Leap 15 KDE Live USB stick this time entering "nomodeset" before "splash=silent" as with Ubuntu, and there is some KDE screen with low resolution coming up where I can get some dmesg output.
Wait - with nomodeset, your system does not grind to a halt? You have access? That seems to indicate a graphics driver issue?
Another thing to try would be safesettings on boot. It makes machines very slow, but sometimes bootable. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Markus Egg wrote:
Finally after a long search my selection for new laptop is the MSI GE63 7RD. Several internet tests were quite positive and -most important- it is very silent. Also the Ubuntu community said that these MSI laptops are quite "standard" stuff, only few tweaks, Optimus seems to be one thing to tweak.
But: after having bought this machine I have to realize that openSUSE Leap 15 does not seem to be ready for this laptop (although amazon.de lists this machine since July 3rd 2017).
It doesn't necessarily mean Leap15 was tested on it. Besides, like you say above, maybe your installation needs a few tweaks. -- Per Jessen, Zürich (21.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/06/18 16:53, Markus Egg wrote:
The worst one seems to be "NMI watchdog : BUG soft lockup CPU4 stuck for 22s!" afterwards SuSE15 seems to be stuck and I have to turn off by switch. I also tried tumbleweed on a USB stick - same error.
Hmmm. Have you tried to update the system firmware? I find that often helps. There was a BIOS update as recently as May: https://www.msi.com/Laptop/support/GE63-7RD-Raider -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Markus, I think, that even the newest openSUSE Leap 15 kernel is too old for your new laptop from 2017. Please try the Vanilla kernel from https://download.opensuse.org/repositories/Kernel:/vanilla/standard/ If Vanilla kernel works without problems, you can try the Kernel_stable repository, which contains openSUSE patches. I had the "NMI watchdog : BUG soft lockup CPU4 stuck for 22s!" bugs years ago. With newer kernels they were gone. But my hardware is older than yours. Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-07-03 11:30, Bjoern Voigt wrote:
Hi Markus,
I think, that even the newest openSUSE Leap 15 kernel is too old for your new laptop from 2017.
Please try the Vanilla kernel from https://download.opensuse.org/repositories/Kernel:/vanilla/standard/
You will have to explain how to do that if the Leap 15.0 install media fails... Anyway, he also tried with tumbleweed Snapshot20180625. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
You will have to explain how to do that if the Leap 15.0 install media fails...
Anyway, he also tried with tumbleweed Snapshot20180625. Ok, thanks for pointing this out.
Maybe there is a strategy to boot the openSUSE installation over network with a Vanilla kernel from openSUSE. There is a description here: https://en.opensuse.org/SDB:Network_installation#Media_free_network_installa... I haven't tested, if the standard files for Kernel and Initrd in the Vanilla packages are working with this strategy. And you need another successful Linux installation on the computer. Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (12)
-
Bjoern Voigt -
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Istvan Gabor -
James Knott -
John Andersen -
Liam Proven -
Markus Egg -
Patrick Shanahan -
Per Jessen -
Richard Brown