Date: Tue, 08 Aug 2006 16:53:19 +0200 From: =?UTF-8?B?RXJpayBOw7hyZ2FhcmQ=?= <norgaard@locolomo.org> To: =?UTF-8?B?RXJpayBOw7hyZ2FhcmQ=?= <norgaard@locolomo.org> Cc: freebsd-mobile@freebsd.org Subject: Solved: ACPI problems: System grinds to a halt Message-ID: <44D8A55F.4040502@locolomo.org> In-Reply-To: <44D36569.1000104@locolomo.org> References: <44D36569.1000104@locolomo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] I have eventually found the solution, for others who may have problems, the solution is below: Erik Nørgaard wrote: > I have problems booting with ACPI enabled. The result varies among three: > > 1) The kernel will print a number of error messages: > > ACPI-0800: *** ERROR: AcpiEvGpeDispatch: No handler or methdo > for GPE[ 6], disabling event > > then hang after identifying the hard disk. > > 2) Same as above, but the messages repeats flickering over the screen > apparently in an infinite loop. > > 3) The system boots up, but with seriously reduced performance: > > Booting takes 3min20sec before the login console is presented, and > building the acpi kernel module takes 54min15sec! With acpi disabled > booting takes 30sec, and building the acpi module 19sec. > > Evidently something is going on, > > I beleive it to be hardware conflicts. I have had interrupt storm on > irq5 when configuring the wireless nic which is on irq10 (default), and > on irq7 when moving a connected usb mouse. Usb devices may be found if > attached before boot, although this is no guarantee that they will work. > > Another peculiar observation is that it seems to give more consistent > result when acpi is built with debugging on(!). > > ACPI however seems to be supported when/if the system comes up: The > device is found and kernel tunables are there. 'halt -p' will halt and > power down the machine. All the problems I have had, including the described problems with iwi (other thread) turned out to be related to one issue: There is a conflict between acpi and apic. apic is compiled in the GENERIC kernel, and the config leaves no clue of what it's for. Looking in the NOTES, "The apic device enables the use of the I/O APIC for interrupt delivery" and is required for SMP. This explains the interrupt problems when both ACPI and APIC attempts to handle interrupts - I guess this should result in a PR? Anyway, two equivalent solutions seem to be: 1) Disable apic, set hint.apic.0.disabled="1" in loader.conf 2) Compile the kernel without "device apic" I have only tried 2) though. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9 [-- Attachment #2 --] 0 *H 01 0 + 0 *H 00נ U O 0 *H 01 0 UES10U Daemon Security1 0 U Certificate Authority1 0 UCertificate Authority1$0" *H ca@daemonsecurity.com1 0U00 060420131650Z 070420131650Z0b1 0 UES10U LocoLomo.Org10U Erik Norgaard1$0" *H norgaard@locolomo.org0"0 *H 0 >NPLGMK $^ha~ Xם-`Y^P oœtƥ*\.e _!2\j]m)B>v +z 2VfDѝR}Tc&E/#_. 9DŽ9÷ (3 ?ԝWu%)vŅͯTr)FA+(R6ƶw {9zP_ Q^zpk/jXMY n0j0U 0 0 U 0 U iy,]ñtb? i0U #0Àa&WtЕna=⥡01 0 UES10U Daemon Security1 0 U Certificate Authority1 0 UCertificate Authority1$0" *H ca@daemonsecurity.com1 0U0 U O0 U 0norgaard@locolomo.org08U 10/0-+)'http://www.daemonsecurity.com/ca/ds.crl0 *H ǟ@&<mWc4LS@G4['s5\\VN^`I &>"@>"[xq 89` @sG;LP ]ƜTT|sGٶ2 Ҋctx?'ҭ$0r; 2#ba"%$B p%rԆU ì> !73ȁg6_ I.2Ġ!AaAmF G' bךuf>-dxqq09#XOSk+FuyTvr+p!!}n.6NH' 5+9`CVĩ;7RߔRKIpv&S@P`;%eƓxC uiL Cb Y,)x:3ѓGjRe EtPҰk< c\;9pT9/K̩ L HzMMuʔ(dkskj <ds08PxZ NWC00נ U O 0 *H 01 0 UES10U Daemon Security1 0 U Certificate Authority1 0 UCertificate Authority1$0" *H ca@daemonsecurity.com1 0U00 060420131650Z 070420131650Z0b1 0 UES10U LocoLomo.Org10U Erik Norgaard1$0" *H norgaard@locolomo.org0"0 *H 0 >NPLGMK $^ha~ Xם-`Y^P oœtƥ*\.e _!2\j]m)B>v +z 2VfDѝR}Tc&E/#_. 9DŽ9÷ (3 ?ԝWu%)vŅͯTr)FA+(R6ƶw {9zP_ Q^zpk/jXMY n0j0U 0 0 U 0 U iy,]ñtb? i0U #0Àa&WtЕna=⥡01 0 UES10U Daemon Security1 0 U Certificate Authority1 0 UCertificate Authority1$0" *H ca@daemonsecurity.com1 0U0 U O0 U 0norgaard@locolomo.org08U 10/0-+)'http://www.daemonsecurity.com/ca/ds.crl0 *H ǟ@&<mWc4LS@G4['s5\\VN^`I &>"@>"[xq 89` @sG;LP ]ƜTT|sGٶ2 Ҋctx?'ҭ$0r; 2#ba"%$B p%rԆU ì> !73ȁg6_ I.2Ġ!AaAmF G' bךuf>-dxqq09#XOSk+FuyTvr+p!!}n.6NH' 5+9`CVĩ;7RߔRKIpv&S@P`;%eƓxC uiL Cb Y,)x:3ѓGjRe EtPҰk< c\;9pT9/K̩ L HzMMuʔ(dkskj <ds08PxZ NWC10001 0 UES10U Daemon Security1 0 U Certificate Authority1 0 UCertificate Authority1$0" *H ca@daemonsecurity.com1 0U0 U O 0 + )0 *H 1 *H 0 *H 1 060808145319Z0# *H 1#Yhe(2vr O20R *H 1E0C0 *H 0*H 0 *H @0+0 *H (0 +71001 0 UES10U Daemon Security1 0 U Certificate Authority1 0 UCertificate Authority1$0" *H ca@daemonsecurity.com1 0U0 U O 0 *H 101 0 UES10U Daemon Security1 0 U Certificate Authority1 0 UCertificate Authority1$0" *H ca@daemonsecurity.com1 0U0 U O 0 *H 2:d>њN YJLrI:K rXY942&Z=FF<'̷cPt' { EϊBG=pm>ÍÛ8d+cEm F= ٿ<|\ Zϕº<g|+7;0I%8exp 1Grژ:<w~b\){ms/ A#nJ£yS+7 +ho{
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44D8A55F.4040502>