well, if you plug in a usb device and that happens that indicates the hardware completely reset. If it was just a kernel crash then the machine would have stayed hung until you reset/power cycled it. It would have to be it crashed because of the usb device being plugged in, and it would have to be a hw issue since it immediately rebooted. So something about either the device you plugged in or the usb bus you connected to. If this was an add-in card make sure its extra power connection is plugged in. I do have a couple of pci-e usb cards that do not work right on a really old motherboard I have and will (if used with say a usb camera) immediately reset the machine the instant a program opens the camera. On Thu, Jan 6, 2022 at 5:10 PM Michael Hennebry <hennebry@xxxxxxxxxxxxxxxxxxxxx> wrote: > > On Thu, 6 Jan 2022, stan via users wrote: > > > On Thu, 6 Jan 2022 16:17:07 -0600 (CST) > > Michael Hennebry <hennebry@xxxxxxxxxxxxxxxxxxxxx> wrote: > > > >> Where does F33 keep the messages from the last system crash? > >> > > If they were captured, I think one of the places they would be is the > > journal. > > journalctl -r > > will read the journal from the end towards the beginning. You will > > have to bypass the session that is the reboot you are reading from. > > Thanks. > This is what I got: > Jan 06 15:32:47 localhost.localdomain kernel: SELinux: Permission watch in class filesystem not defined in policy. > -- Reboot -- > Jan 06 15:10:29 fedora firefox.desktop[611691]: ###!!! [Parent][DispatchAsyncMessage] Error: PMessagePort::Msg_PostMessages Processing error: message was> > Jan 06 15:10:29 fedora firefox.desktop[611691]: IPDL protocol error: Handler returned error code! > -- Reboot -- > Jan 06 09:32:37 localhost.localdomain systemd-journald[176]: Journal stopped > > As far as I could tell, > the system was running fine at 15:37 and for a bit after that. > It had been running since yesterday and my firefox windows were up. > Shortly after 15:37, I plugged in a USB cable with no device attached. > I heard what I took to be the fan being real busy and unplugged the cable. > I then tried to move the mouse so that I could close firefox. > Could not even see the mouse. > Shortly thereafter, "no signal" on the monitor and rebooting started. > > So far as I know, nothing interesting happened at 9:32:37 today. > The available evidence, my firefox windows, > suggest that there was no reboot at that time. > > What happened? > In the alternative, how do I find out what happened? > > I've had almost the same thing happen before. > I'd plug in a USB cable, possibly with a cell phone attached, > though not this time, > the fan would speed up and the mouse would freeze. > Complete lock up. Could not even switch virtual windows. > > Any ideas? > > -- > Michael hennebry@xxxxxxxxxxxxxxxxxxxxx > "Sorry but your password must contain an uppercase letter, a number, > a haiku, a gang sign, a heiroglyph, and the blood of a virgin." > -- someeecards > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
