Jung-uk Kim wrote: > On Tuesday 13 October 2009 05:50 pm, Lawrence Stewart wrote: >> Jung-uk Kim wrote: >> >> [snip] >> >>> by new ACPICA. However, if you see "ACPI Error", that's >>> something to worry about, e.g., cannot convert predefined types. >> So I should be worried about this line from my Toshiba R600 >> laptop's dmesg? >> >> ACPI Error: Package List length (0xC) larger than NumElements count >> (0x4), truncated > > Strictly speaking, it is an error because ACPI specification says so > (hence the error message). However, no exception is returned because > of Windows compatibility according to the comments in the source. > Ok thanks for explaining. > If everything is working fine, just ignore it. :-) When I boot this particular laptop into windows and then back into FreeBSD (even after a power down in between), I get a reproducible panic while the kernel is booting and probing devices which can only be fixed by going into the BIOS config screen and restoring to defaults. I suspect the Windows drivers are leaving the hardware in some fancy state the FreeBSD kernel doesn't like. I have a hunch it is ACPI related. Is there some way I can tell? The panic/backtrace is always the same as follows: Slab at 0xffffff00025d5b18, freei 3 = 0. panic: Duplicate free of item 0xffffff00025f8c00 from zone 0xffffff00b697d400(1024) Backtrace at the ddb prompt looks like this: db> bt kdb_enter()+0x3d panic()+0x17b uma_dbg_free()+0x171 uma_zfree_arg()+0x68 free()+0xbd device_set_driver()+0x8e device_attach()+0x19b bus_generic_attach()+0x1a acpi_pci_attach()+0x147 device_attach()+0x69 bus_generic_attach()+0x1a acpi_pcib_attach()+0x1a7 acpi_pcib_acpi_attach()+0x1a5 device_attach()+0x69 bus_generic_attach()+0x1a acpi_attach()+0x9e4 device_attach()+0x69 bus_generic_attach()+0x1a device_attach()+0x69 root_bus_configure()+0x28 configure()+0xa mi_startup()+0x59 btext()+0x2c Cheers, LawrenceReceived on Tue Oct 13 2009 - 21:43:05 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:56 UTC