Re: Riddle me this: unsolicited orderly shutdown
On 12/03/2021 14:08, Shachar Shemesh wrote: >I've cracked it!!! > >The problem was that my USB-C docking station was incapable of >providing enough power to run the computer. It should not have been a >problem, as I'm guessing the problem was momentary and the computer's >battery would have also sufficed. It did, however, respond to this >situation by sending a power-off key (which is why the BIOS did not >say anything - it wasn't it that initiated the shutdown). > >I've connected the computer's provided power supply, and the problem >is now GONE. > >Thank you, everyone. Nice troubleshooting Shachar! Something like that could be extremely elusive. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques ___ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
Re: Riddle me this: unsolicited orderly shutdown
That's a great story Shachar, thanks for sharing. Hopefully I will remember this if it ever happens to me. On Fri, Mar 12, 2021 at 4:47 PM Shachar Shemesh wrote: > > On 12/03/2021 14:08, Shachar Shemesh wrote: > > > On 12/03/2021 12:34, borissh1...@gmail.com wrote: > > > > > > Would it be possible to monitor both dbus messages (system and user) AND > Xsession errors while you do so ? > > Yes, that provided some progress. At least I can tell the name of the > component that triggers the shutdown. The session dbus monitor says: > > signal time=1615549109.464622 sender=:1.13 -> destination=(null > destination) serial=832 path=/component/org_kde_powerdevil; > interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed >string "org_kde_powerdevil" >string "PowerOff" >int64 6630990 > > I'm not 100% sure what that means. It seems that powerdevil thinks that > someone pressed the power button. More research necessary, but at least > we're finally getting a log admitting _something_ happened. > > I've cracked it!!! > > The problem was that my USB-C docking station was incapable of providing > enough power to run the computer. It should not have been a problem, as I'm > guessing the problem was momentary and the computer's battery would have > also sufficed. It did, however, respond to this situation by sending a > power-off key (which is why the BIOS did not say anything - it wasn't it > that initiated the shutdown). > > I've connected the computer's provided power supply, and the problem is > now GONE. > > Thank you, everyone. > > Shachar > ___ > Linux-il mailing list > Linux-il@cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > ___ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
Re: Riddle me this: unsolicited orderly shutdown
On 12/03/2021 14:08, Shachar Shemesh wrote: On 12/03/2021 12:34, borissh1...@gmail.com wrote: Would it be possible to monitor both dbus messages (system and user) AND Xsession errors while you do so ? Yes, that provided some progress. At least I can tell the name of the component that triggers the shutdown. The session dbus monitor says: signal time=1615549109.464622 sender=:1.13 -> destination=(null destination) serial=832 path=/component/org_kde_powerdevil; interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed string "org_kde_powerdevil" string "PowerOff" int64 6630990 I'm not 100% sure what that means. It seems that powerdevil thinks that someone pressed the power button. More research necessary, but at least we're finally getting a log admitting _something_ happened. I've cracked it!!! The problem was that my USB-C docking station was incapable of providing enough power to run the computer. It should not have been a problem, as I'm guessing the problem was momentary and the computer's battery would have also sufficed. It did, however, respond to this situation by sending a power-off key (which is why the BIOS did not say anything - it wasn't it that initiated the shutdown). I've connected the computer's provided power supply, and the problem is now GONE. Thank you, everyone. Shachar ___ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
Re: Riddle me this: unsolicited orderly shutdown
On 12/03/2021 12:34, borissh1...@gmail.com wrote: Would it be possible to monitor both dbus messages (system and user) AND Xsession errors while you do so ? Yes, that provided some progress. At least I can tell the name of the component that triggers the shutdown. The session dbus monitor says: signal time=1615549109.464622 sender=:1.13 -> destination=(null destination) serial=832 path=/component/org_kde_powerdevil; interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed string "org_kde_powerdevil" string "PowerOff" int64 6630990 I'm not 100% sure what that means. It seems that powerdevil thinks that someone pressed the power button. More research necessary, but at least we're finally getting a log admitting _something_ happened. ___ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
Re: Riddle me this: unsolicited orderly shutdown
On 12/03/2021 12:27, Dotan Shavit wrote: Nice indeed. Have you tried starting this app from a different desktop environment? What syslog says at the shutdown time? Nothing that seems relevant. kernel.log says that a few of the cores went into overheat and then came out. Shachar ___ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
Re: Riddle me this: unsolicited orderly shutdown
This takes me back ~15 years. We had Sun x86_64 servers, which randomly decided to shutdown. After investigation it appeared that the problem was that the computer wrongly decided it's too hot and sent ACPI command to shutdown. Long story short - firmware update solved it. Bottom line, have you tried the latest firmware for your XPS15? On Fri, Mar 12, 2021 at 12:18 PM Shachar Shemesh wrote: > Allow me, if I may, to set up the stage for you. > > I don't know the precise scenario that causes this to happen, but one > thing that triggers it reliably is starting up X-Plane 11 and taking off. A > few second and up to a minute into the flight, my KDE "shutting down" > screen comes up. If I cancel the shutdown, the screen comes up one more > time on its own, and then the computer just shuts down. > > Now, I know what you're all thinking. So I ran X-Plane while monitoring > the CPU's and GPU's temperatures. Sure enough, they get hot. I opened up > the laptop (Dell XPS 15, a gamer's laptop), cleaned the fans, and ran the > game again. Temperatures were much more reasonable. But the shutdown screen > popped up again. > > I ran it with dmesg running. While there are some temperature throttling > messages, not a lot, and none that claim I *have* to shut down. > > I am looking for a way to debug this. Obviously, something in the hardware > gives the command to shut down the computer. I have, however, not been able > to find out what and why. > > Does anyone have any idea which system might be issuing this command, and > where it might be writing its logs? > > Shachar > ___ > Linux-il mailing list > Linux-il@cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > ___ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
Re: Riddle me this: unsolicited orderly shutdown
On Friday, 12 March 2021 12:17:26 IST Shachar Shemesh wrote: Allow me, if I may, to set up the stage for you. I don't know the precise scenario that causes this to happen, but one thing that triggers it reliably is starting up X-Plane 11 and taking off. A few second and up to a minute into the flight, my KDE "shutting down" screen comes up. If I cancel the shutdown, the screen comes up one more time on its own, and then the computer just shuts down. Now, I know what you're all thinking. So I ran X-Plane while monitoring the CPU's and GPU's temperatures. Sure enough, they get hot. I opened up the laptop (Dell XPS 15, a gamer's laptop), cleaned the fans, and ran the game again. Temperatures were much more reasonable. But the shutdown screen popped up again. I ran it with dmesg running. While there are some temperature throttling messages, not a lot, and none that claim I *have* to shut down. I am looking for a way to debug this. Obviously, something in the hardware gives the command to shut down the computer. I have, however, not been able to find out what and why. Does anyone have any idea which system might be issuing this command, and where it might be writing its logs? Shachar Would it be possible to monitor both dbus messages (system and user) AND Xsession errors while you do so ? It could be that you have some tool (something like TLP that might trigger a shutdown script when you hit a threashold ) . If I were you I would also check for messages such as "temperature reached" in syslog, the temp values may be set both in the UEFI and on kernel level. ___ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
Re: Riddle me this: unsolicited orderly shutdown
Nice indeed. Have you tried starting this app from a different desktop environment? What syslog says at the shutdown time? בברכה, דותן שביט, 0544-456656 On Fri, 12 Mar 2021 at 12:18, Shachar Shemesh wrote: > Allow me, if I may, to set up the stage for you. > > I don't know the precise scenario that causes this to happen, but one > thing that triggers it reliably is starting up X-Plane 11 and taking off. A > few second and up to a minute into the flight, my KDE "shutting down" > screen comes up. If I cancel the shutdown, the screen comes up one more > time on its own, and then the computer just shuts down. > > Now, I know what you're all thinking. So I ran X-Plane while monitoring > the CPU's and GPU's temperatures. Sure enough, they get hot. I opened up > the laptop (Dell XPS 15, a gamer's laptop), cleaned the fans, and ran the > game again. Temperatures were much more reasonable. But the shutdown screen > popped up again. > > I ran it with dmesg running. While there are some temperature throttling > messages, not a lot, and none that claim I *have* to shut down. > > I am looking for a way to debug this. Obviously, something in the hardware > gives the command to shut down the computer. I have, however, not been able > to find out what and why. > > Does anyone have any idea which system might be issuing this command, and > where it might be writing its logs? > > Shachar > ___ > Linux-il mailing list > Linux-il@cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > ___ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
