shutdown/reboot hangs on new arch install

ClientAlive · 2013-04-04 03:14:52

Hi,

I thought maybe I had just made a mistake when I installed, so a reformatted all my partitions and did another install. I tried to be very very careful and check everything 3 and 4 times as I went along. Ultimately, I get the same thing I had before doing this last install.

Some system information:

It is a uefi install using the kernels boot stub loader with an efibootmgr entry
root is in a logical volume on raid 5

If I use the command "reboot" it will hang rougly half the times
If I use the shutdown command it will print: "Broadcast message from root@archsys (<date and time is here>):

The system is going down for..."
With this one it sometimes works sometimes hangs

If I use poweroff, halt, or shutdown -h now it shuts down fine every time (I think - only tried those like twice).

Any help would be greatly appreciated. Any further information you need just let me know.

Thanks

-----------------------------------------------

Edit: shutdown -r now just hung in the middle of shutdown process. I thought there was a difference in what command I use but maybe not.

Last edited by ClientAlive (2013-04-04 03:18:01)

jasonwryan · 2013-04-04 03:20:05

What happens if you use the systemd commands:

systemctl {poweroff,reboot}

WonderWoofy · 2013-04-04 03:39:39

Also, can you find anything in the journal where there is a gap in time during your shutdown?

ClientAlive · 2013-04-04 03:43:14

In 5 tries with systemctl reboot: failed on the 4th run (all other runs successful)
In 5 tries with systemctl shutdown: failed on the 4th and 5th runs

By failed I mean it hangs. On one occasion I went outside for a ciggarette and came back (roughly 10 min later) and it was still hanging there. This was a previous occasion not from among the 10 trials mentioned at the top of this reply.

ClientAlive · 2013-04-04 03:44:21

WonderWoofy wrote:

Also, can you find anything in the journal where there is a gap in time during your shutdown?

Not real keen on how to use the journal. What would I do to pull the right thing up?

jasonwryan · 2013-04-04 03:47:57

https://wiki.archlinux.org/index.php/Sy … ribly_long

ClientAlive · 2013-04-04 04:05:57

I'll work throught that first thing in the morning. I need to break from this for tonight. Thank you.

WonderWoofy · 2013-04-04 07:26:53

See the man page for journalctl. Though this info is also in the wiki.

ClientAlive · 2013-04-04 14:56:44

WonderWoofy wrote:

See the man page for journalctl. Though this info is also in the wiki.

ok, thanks

ClientAlive · 2013-04-04 15:36:12

jasonwryan wrote:

https://wiki.archlinux.org/index.php/Sy … ribly_long

So, last night before bed, I did...

    boot with the debug options: 

systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0

    save the following script as /lib/systemd/system-shutdown/debug.sh and make it executable: 

#!/bin/sh
mount -o remount,rw /
dmesg > /shutdown-log.txt
mount -o remount,ro /

    reboot 

reference: http://freedesktop.org/wiki/Software/systemd/Debugging#Shutdown_Completes_Eventually

About an hr. later it was still hanging. Just for the heck of it (and to be sure beyond a shadow of a doubt) I didn't touch it and just went to sleep. This morning I wake up and it is still hung in the same place. What I can see printed to the screen is this:

[  ok  ] Stopped Getty on tty1.
           Stopping Permit User Sessions...
[  ok  ] Deactivated swap /dev/sdb3.
[  ok  ] Stopped Login Service
[  246.499365  ] systemd[1]: Failed to reread /proc/swaps: File exists
[  246.499710  ] systemd[1]: Failed to reread /proc/swaps: File exists
[  ok  ] Stopped Permit User Sessions.  # Second occurance of this?
[  ok  ] Stopped target Remote File Systems.  # I don't use any remote file system (NFS, Samba, etc)
[  ok  ] Stopped dhcpcd on < my network name >.
[  ok  ] Stopped target Basic System.
[  ok  ] Stopped target Sockets.
[  ok  ] Closed Device-mapper event daemon FIFOs.
[  ok  ] Closed LVM2 metadata daemon socket.
[  ok  ] Closed D-Bus System Message Bus Socket.
[  ok  ] Stopped target System Initialization.
[  ok  ] Stopped target Encrypted Volumes.  # No encrypted volumes are on this system
           Stopping Apply Kernel Variables...
[  ok  ] Stopped Apply Kernel Variables.
           Stopping Setup Virtual Console...
[  ok  ] Stopped Setup Virtual Console.
[  ok  ] Stopped target Swap.
[  ok  ] Deactivated swap /dev/disk/by-uuid/< it's uuid here >
[  ok  ] Deactivated swap /dev/disk/by-uuid/< other swap uuid here >
[  ok  ] Deactivated swap /dev/disk/by-uuid/< other swap uuid here >
[  ok  ] Stopped target Local File Systems.
           Unmounting /mnt/web...    # One of my logical volumes
           Unmounting /mnt/dev...     # One of my logical volumes
           Unmounting /mnt/vm...     # One of my logical volumes
           Unmounting /home...        # Not the logical volume, but it is a logical volume mounted to this
           Unmounting /boot/efi...     # /dev/sda1 mounted here
           Unmounting Temporary Directory...
[  ok  ] Unmounted /boot/efi.
[  ok  ] Unmounted Temporary Directory.
[  ok  ] Unmounted /mnt/vm.
[  ok  ] Unmounted /mnt/dev.
[  ok  ] Unmounted /mnt/web.
[  ok  ] Unmounted /home.
[  ok  ] Stopped target Local File Systems (Pre)
           Stopping Remount Root and Kernel File Systems...
[  ok  ] Stopped Remount Root and Kernel File Systems.
[  ok  ] Reached target Shutdown.
  # Cursor is here - system hanging...

Now I reboot into regular system by pressing the reset switch on the front of the box. shutdown-log.txt is not in / and mlocate shutdown-log.txt yeilds no result (it does not exist).

The next thing on the freedesktop.org web page (reference url) says:

If normal reboot or poweroff never finish even after waiting a few minutes, the above method to create the shutdown log will not help and the log must be obtained using other methods. Two options that are useful for debugging boot problems can be used also for shutdown problems:

    use a serial console

    use a debug shell - not only is it available from early boot, it also stays active until late shutdown.

I can probably look up how to launch and/or install (if necessary) one of those but I wouldn't know what to do with it once I had it in front of me. If that is the next step for me, I need instruction on how to use it to find the soln to my problem.

Last edited by ClientAlive (2013-04-04 15:41:49)

WonderWoofy · 2013-04-04 16:39:18

Now, I don't know what specifically is going wrong here as the debug measures failed to work for you. But in the future, instead of the "reset switch on the front of the box" you should try and use the SysRq key. I was having some hanging with remote filesystems being stopped after the network was disconnected, and using the REISUB sequence to reboot instead of a hard shutdown really helped me out.

By doing that instead, you are changing the mode of the keyboard(R), then sending SIGTERM(E), then SIGKILL(I). Then it does an "emergency sync"(S), before remounting ro(U), and finally rebooting(B). It is the "S" that really was able to give me more information, as it then is able to flush the logs out to disk before you reboot.

Also, it is probably much safer to use the SysRq method anyway. Typically the SysRq key is the print screen key (PrtSc) in combination with Alt. Though at this stage of shutdown, if you are using a desktop with a USB keyboard, you may need the keyboard hook in mkinitcpio. I really am not sure about that though since the modules *should* already be loaded, so I am not sure if switching back to the initramfs during shutdown really needs that... do you have the shutdown hook BTW?

ClientAlive · 2013-04-04 17:18:08

WonderWoofy wrote:

Now, I don't know what specifically is going wrong here as the debug measures failed to work for you. But in the future, instead of the "reset switch on the front of the box" you should try and use the SysRq key. I was having some hanging with remote filesystems being stopped after the network was disconnected, and using the REISUB sequence to reboot instead of a hard shutdown really helped me out.
By doing that instead, you are changing the mode of the keyboard(R), then sending SIGTERM(E), then SIGKILL(I). Then it does an "emergency sync"(S), before remounting ro(U), and finally rebooting(B). It is the "S" that really was able to give me more information, as it then is able to flush the logs out to disk before you reboot.
Also, it is probably much safer to use the SysRq method anyway. Typically the SysRq key is the print screen key (PrtSc) in combination with Alt. Though at this stage of shutdown, if you are using a desktop with a USB keyboard, you may need the keyboard hook in mkinitcpio. I really am not sure about that though since the modules *should* already be loaded, so I am not sure if switching back to the initramfs during shutdown really needs that... do you have the shutdown hook BTW?

Ok. I can and will investigate those things. Thank you. However, I would like to gather a little further input (get a little more ammo, if you will). --fwiw, I noticed something when running journalctl and scrolling throught it I see the following lines... (which I find alarming btw)...

journalctl | grep Bug | wgetpaste  # Blank lines by me - for readability...

Apr 03 19:24:05 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 19:24:05 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 19:24:05 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 19:24:05 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 19:24:05 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 20:34:19 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 20:34:19 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 20:34:19 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 20:34:19 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 20:34:19 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 20:55:16 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 20:56:05 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 20:56:54 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 20:58:04 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 20:58:52 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 21:00:10 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 21:00:58 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 21:10:50 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 21:14:34 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 21:22:08 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 21:58:13 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 21:58:13 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 21:58:13 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 21:58:13 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 21:58:13 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 21:59:12 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 21:59:12 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 21:59:12 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 21:59:12 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 21:59:12 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:00:34 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:00:34 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:00:34 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:00:34 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:00:34 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:02:13 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:02:13 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:02:13 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:02:13 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:02:13 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:03:57 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:03:57 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:03:57 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:03:57 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:03:57 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:06:50 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:06:50 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:06:50 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:06:50 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:06:50 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:09:27 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:09:27 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:09:27 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:09:27 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:09:27 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:10:41 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:10:41 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:10:41 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:10:41 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:10:41 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:14:23 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:14:23 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:14:23 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:14:23 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:14:23 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:15:27 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:15:27 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:15:27 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:15:27 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:15:27 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:16:27 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:16:27 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:16:27 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:16:27 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:16:27 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:17:54 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:17:54 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:17:54 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:17:54 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:17:54 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:19:23 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:19:23 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:19:23 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:19:23 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:19:23 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:20:55 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:20:55 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:20:55 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:20:55 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:20:55 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:27:02 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:27:02 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:27:02 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:27:02 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:27:02 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 22:28:37 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 22:28:37 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 22:28:37 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 22:28:37 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 22:28:37 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:14:13 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:14:13 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:14:13 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:14:13 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:14:13 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:30:53 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:30:53 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:30:53 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:30:53 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:30:53 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:31:45 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:31:45 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:31:45 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:31:45 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:31:45 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:32:38 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:32:38 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:32:38 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:32:38 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:32:38 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:33:43 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:33:43 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:33:43 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:33:43 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:33:43 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:34:47 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:34:47 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:34:47 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:34:47 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:34:47 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:35:36 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:35:36 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:35:36 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:35:36 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:35:36 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:38:07 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:38:07 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:38:07 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:38:07 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:38:07 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:39:07 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:39:07 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:39:07 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:39:07 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:39:07 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:40:10 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:40:10 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:40:10 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:40:10 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:40:10 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:41:44 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:41:44 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:41:44 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:41:44 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:41:44 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:49:43 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:49:43 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:49:43 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:49:43 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:49:43 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 03 23:50:54 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 03 23:50:54 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 03 23:50:54 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 03 23:50:54 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 03 23:50:54 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)

Apr 04 02:36:59 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 04 02:36:59 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 04 02:36:59 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 04 02:36:59 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 04 02:36:59 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 04 02:41:13 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 04 02:41:13 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 04 02:41:13 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 04 02:41:13 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 04 02:41:13 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 04 02:43:11 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 04 02:43:11 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 04 02:43:11 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 04 02:43:11 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 04 02:43:11 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 04 02:50:39 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 04 02:50:39 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 04 02:50:39 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 04 02:50:39 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 04 02:50:39 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Apr 04 11:29:49 archsys kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20121018/tbfadt-598)
Apr 04 11:29:49 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[5] not in IVRS table
Apr 04 11:29:49 archsys kernel: [Firmware Bug]: AMD-Vi: IOAPIC[6] not in IVRS table
Apr 04 11:29:49 archsys kernel: [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
Apr 04 11:29:49 archsys kernel: AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)

Could that be part of my problem? Is it something I should address even if it is not tied to my shutdown problem?

Also, I noticed this... (which repeats)...

Built 1 zonelists in zone order, mobility grouping on. Total pages: 4118988
Policy zone: Normal
Movable zone start for each node

Is that a reference to apparmour? I don't really think so but that's what it makes me think of. As far as I know, apparmor is not installed on this machine (though i guess it's conceivable arch has enabled it in the kernel). Does it merit my attention?

@WonderWoofy: Will report back with results of your suggestions. Thanks.
------------------------------------------

Edit:

Found this...

When the IOAPIC information provided in the IVRS table is
not correct or not complete the system may not boot at all #...system may not boot at all...
when interrupt remapping is enabled. So check if this
information is correct and print out a firmware bug message
when it is not.
reference: https://patchwork.kernel.org/patch/1518831/

Last edited by ClientAlive (2013-04-04 17:34:40)

ClientAlive · 2013-04-04 20:02:32

The bottom line for me is I don't know what to test for or what command(s) to run to make that happen. I can only imagine that I should want to know what that next line is that would have been printed to the sceen when shutdown hangs, but how to get that data I don't know. Is there someone who can supply the command(s) to run to determine the problem's source?

ClientAlive · 2013-04-10 06:47:57

System still screwed up. Still been trying to find the problem. Nothing works that I've tried...

Imagine I'll get my data corrupted at some point when I have to push the hardware reset button cause nothing else works. Well, it wouldn't be such a big deal I suppose, if it weren't the machine that makes my business what it is.

Last edited by ClientAlive (2013-04-10 06:50:07)

Arch Linux

#1 2013-04-04 03:14:52

shutdown/reboot hangs on new arch install

#2 2013-04-04 03:20:05

Re: shutdown/reboot hangs on new arch install

#3 2013-04-04 03:39:39

Re: shutdown/reboot hangs on new arch install

#4 2013-04-04 03:43:14

Re: shutdown/reboot hangs on new arch install

#5 2013-04-04 03:44:21

Re: shutdown/reboot hangs on new arch install

#6 2013-04-04 03:47:57

Re: shutdown/reboot hangs on new arch install

#7 2013-04-04 04:05:57

Re: shutdown/reboot hangs on new arch install

#8 2013-04-04 07:26:53

Re: shutdown/reboot hangs on new arch install

#9 2013-04-04 14:56:44

Re: shutdown/reboot hangs on new arch install

#10 2013-04-04 15:36:12

Re: shutdown/reboot hangs on new arch install

#11 2013-04-04 16:39:18

Re: shutdown/reboot hangs on new arch install

#12 2013-04-04 17:18:08

Re: shutdown/reboot hangs on new arch install

#13 2013-04-04 20:02:32

Re: shutdown/reboot hangs on new arch install

#14 2013-04-10 06:47:57

Re: shutdown/reboot hangs on new arch install

Board footer