You are not logged in.
Hi guys,
Another day, another noob. I've been enjoying my arch experience so far and looking forward to continuing the journey! I've hit a small roadblock along the way however, I seem to get a kernel panic (system hang/caps lock blinking) upon trying to poweroff/reboot in the terminal. This seems to be since I updated linux from 3.19.2-1 > 3.19.3-1. Interestingly enough the hangs only occur when trying to poweroff/shutdown from X. I have no issue with either command at the initial tty console.
*Possibly related - during the upgrade I got 2 warnings - Possibly missing firmware for module: aic94xx and Possibly missing firmware for module: wd719xx
I went hunting for log files but wasn't 100% sure what I was looking for tbh.
Any help would be greatly appreciated.
Cap
Last edited by CapricornOne (2015-04-07 22:18:36)
Offline
Fixed in 3.19.4 (there are a couple of threads about this)...
Offline
Fixed in 3.19.4 (there are a couple of threads about this)...
Apologies, I hadn't noticed the threads! Thanks for the swift reply. I'll mark this thread as solved.
Offline
It is sort of buried, here, for example: https://bbs.archlinux.org/viewtopic.php … 1#p1517661
Offline
*Possibly related - during the upgrade I got 2 warnings - Possibly missing firmware for module: aic94xx and Possibly missing firmware for module: wd719xx
Offline
Fixed in 3.19.4 (there are a couple of threads about this)...
Linux 3.19.4? As in an unreleased kernel patch?
Offline
Something like that. I guess he means that it's been acknowledged, discussed and probably someone made a patch for it. It's a matter of time for 3.19.4 to pop out and therefore be built in Arch [core].
Personal spot :: https://www.smirky.net/ :: Try not to get lost!
Offline
Something like that. I guess he means that it's been acknowledged, discussed and probably someone made a patch for it. It's a matter of time for 3.19.4 to pop out and therefore be built in Arch [core].
Exactly: quoting the person who closed the original bug report
This is fixed upstream, and the relevant commit is cc: stable, i.e. should find its way to some v3.19.y. Closing, thanks for the report.
-- edit: the patch has been added in the package linux 3.19.3-3, the speed of Archlinux developers is awesome (and this should go also in the 'ooh, nice!' thread).
Last edited by mauritiusdadd (2015-04-08 18:21:49)
Offline
smirky wrote:Something like that. I guess he means that it's been acknowledged, discussed and probably someone made a patch for it. It's a matter of time for 3.19.4 to pop out and therefore be built in Arch [core].
Exactly: quoting the person who closed the original bug report
This is fixed upstream, and the relevant commit is cc: stable, i.e. should find its way to some v3.19.y. Closing, thanks for the report.
-- edit: the patch has been added in the package linux 3.19.3-3, the speed of Archlinux developers is awesome (and this should go also in the 'ooh, nice!' thread).
Issue still occurring. No change with 3-3. It's a strange one.
Offline
Issue still occurring. No change with 3-3. It's a strange one.
Maybe you should post the journal of the boot that failed to reboot/shutdown (if it is not corrupted...)? And what is the output of the following command?
$ uname -a
Offline
Maybe you should post the journal of the boot that failed to reboot/shutdown (if it is not corrupted...)? And what is the output of the following command?
$ uname -a
Hmm. How would I go about doing that? Uname -a returns 3.19.3-3 arch #1 smp preempt...
Offline
Offline
So a work around would be to ctrl+alt+fY (Y != the current X session's) and type systemctl reboot?
Offline
It the issue is still occurring with the current kernel, a new bug report needs to be filled / the old report reopened.
Offline
Upon running journalctl --verify I get one fail. File corruption detected at /var/log/journal/xxxx. I'm assuming that'd be the reason for the kp's?
Issue seems to be resolved now for some reason. Haven't changed a thing. The journal error remains though
Last edited by CapricornOne (2015-04-12 14:55:01)
Offline
File corruption detected at /var/log/journal/xxxx. I'm assuming that'd be the reason for the kp's?
No, the corruption was most likely caused by the kernel panic and not the reverse. if you want to delete the corrupted files, just do
systemctl stop systemd-journald
rm /var/log/journal/xxxx
systemctl start systemd-journald
Offline