https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289943

--- Comment #19 from Leo Bicknell <[email protected]> ---
Ok, I think I was able to sort this out from /var/log/messages.  I don't think
any of these are hung boots because the information is in /var/log/messages so
it must have gotten far enough to save that.

FreeBSD 13.5-RELEASE successful boot in LEGACY BIOS mode with ig4_load="YES" in
/boot/loader.conf and boot1.efi in use:

Oct  2 08:39:42 fileserver kernel: Copyright (c) 1992-2021 The FreeBSD Project.
Oct  2 08:39:42 fileserver kernel: FreeBSD 13.5-RELEASE
releng/13.5-n259162-882b9f3f2218 GENERIC amd64
Oct  2 08:39:42 fileserver kernel: ig4iic0: <Intel Cannon Lake-H I2C
Controller-0> at device 21.0 on pci0
Oct  2 08:39:42 fileserver kernel: ig4iic0: Using MSI
Oct  2 08:39:42 fileserver kernel: ig4iic0: controller error during attach-1
Oct  2 08:39:42 fileserver kernel: device_attach: ig4iic0 attach returned 6
Oct  2 08:39:42 fileserver kernel: ig4iic0: <Intel Cannon Lake-H I2C
Controller-1> at device 21.1 on pci0
Oct  2 08:39:42 fileserver kernel: ig4iic0: Using MSI
Oct  2 08:39:42 fileserver kernel: ig4iic0: controller error during attach-1
Oct  2 08:39:42 fileserver kernel: device_attach: ig4iic0 attach returned 6
Oct  2 08:39:42 fileserver kernel: ig4iic0: <Intel Cannon Lake-H I2C
Controller-0> mem 0x90000000-0x90000fff irq 16 at device 21.0 on pci0
Oct  2 08:39:42 fileserver kernel: ig4iic0: Using MSI
Oct  2 08:39:42 fileserver kernel: iicbus0: <Philips I2C bus (ACPI-hinted)> on
ig4iic0
Oct  2 08:39:42 fileserver kernel: ig4iic1: <Intel Cannon Lake-H I2C
Controller-1> mem 0x90001000-0x90001fff irq 17 at device 21.1 on pci0
Oct  2 08:39:42 fileserver kernel: ig4iic1: Using MSI
Oct  2 08:39:42 fileserver kernel: iicbus1: <Philips I2C bus (ACPI-hinted)> on
ig4iic1
Oct  2 08:42:19 fileserver kernel: Copyright (c) 1992-2021 The FreeBSD Project.

FreeBSD 14.3-RELEASE successful boot in LEGACY BIOS mode with ig4_load="YES" in
/boot/loader.conf and boot1.efi in use:

Oct  2 09:20:55 fileserver kernel: Copyright (c) 1992-2023 The FreeBSD Project.
Oct  2 09:20:55 fileserver kernel: FreeBSD 14.3-RELEASE-p3 GENERIC amd64
Oct  2 09:20:55 fileserver kernel: ig4iic0: <Intel Cannon Lake-H I2C
Controller-0> at device 21.0 on pci0
Oct  2 09:20:55 fileserver kernel: ig4iic0: Using MSI
Oct  2 09:20:55 fileserver kernel: ig4iic0: controller error during attach-1
Oct  2 09:20:55 fileserver kernel: device_attach: ig4iic0 attach returned 6
Oct  2 09:20:55 fileserver kernel: ig4iic0: <Intel Cannon Lake-H I2C
Controller-1> at device 21.1 on pci0
Oct  2 09:20:55 fileserver kernel: ig4iic0: Using MSI
Oct  2 09:20:55 fileserver kernel: ig4iic0: controller error during attach-1
Oct  2 09:20:55 fileserver kernel: device_attach: ig4iic0 attach returned 6
Oct  2 09:20:55 fileserver kernel: ig4iic0: <Intel Cannon Lake-H I2C
Controller-0> mem 0x90000000-0x90000fff irq 16 at device 21.0 on pci0
Oct  2 09:20:55 fileserver kernel: ig4iic0: Using MSI
Oct  2 09:20:55 fileserver kernel: iicbus0: <Philips I2C bus (ACPI-hinted)> on
ig4iic0
Oct  2 09:20:55 fileserver kernel: ig4iic1: <Intel Cannon Lake-H I2C
Controller-1> mem 0x90001000-0x90001fff irq 17 at device 21.1 on pci0
Oct  2 09:20:55 fileserver kernel: ig4iic1: Using MSI
Oct  2 09:20:55 fileserver kernel: iicbus1: <Philips I2C bus (ACPI-hinted)> on
ig4iic1

FreeBSD 14.3-RELEASE successful boot in UEFI BIOS mode without ig4_load and
loader.efi in use:

Oct  3 13:55:21 fileserver kernel: Copyright (c) 1992-2023 The FreeBSD Project.
Oct  3 13:55:21 fileserver kernel: FreeBSD 14.3-RELEASE-p3 GENERIC amd64
Oct  3 13:55:21 fileserver kernel: ig4iic0: <Intel Cannon Lake-H I2C
Controller-0> at device 21.0 on pci0
Oct  3 13:55:21 fileserver kernel: ig4iic0: Using MSI
Oct  3 13:55:21 fileserver kernel: iicbus0: <Philips I2C bus (ACPI-hinted)> on
ig4iic0
Oct  3 13:55:21 fileserver kernel: ig4iic1: <Intel Cannon Lake-H I2C
Controller-1> at device 21.1 on pci0
Oct  3 13:55:21 fileserver kernel: ig4iic1: Using MSI
Oct  3 13:55:21 fileserver kernel: iicbus1: <Philips I2C bus (ACPI-hinted)> on
ig4iic1

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to