Date: Wed, 23 Mar 2005 23:57:40 +0300 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Nate Lawson <nate@root.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi_perf.c Message-ID: <1111611460.1805.1.camel@localhost> In-Reply-To: <424079AB.6050805@root.org> References: <200503200351.j2K3pIC8068507@repoman.freebsd.org> <1111516858.1198.2.camel@localhost> <424079AB.6050805@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
=F7 =D7=D4, 22/03/2005 =D7 12:01 -0800, Nate Lawson =D0=C9=DB=C5=D4: > Vladimir Grebenschikov wrote: > > =F7 =D7=D3, 20/03/2005 =D7 03:51 +0000, Nate Lawson =D0=C9=DB=C5=D4: > >=20 > >>njl 2005-03-20 03:51:18 UTC > >> > >> FreeBSD src repository > >> > >> Modified files: > >> sys/dev/acpica acpi_perf.c=20 > >> Log: > >> Attach acpi_perf early. Especially when it is being used to provide i= nfo > >> to other devices, it needs to be attached first. (Multi-pass newbus > >> probes would be a better solution.) > >>=20 > >> Revision Changes Path > >> 1.16 +6 -1 src/sys/dev/acpica/acpi_perf.c > >=20 > >=20 > > I guess this patch makes panic on my notebook: > >=20 > > cpu0: <ACPI CPU (2 Cx states)> on acpi0 > > acpi_perf0: <ACPI CPU Frequency Control> on cpu0 > > acpi_perf0: failed in PERF_STATUS attach > > device_attach: acpi_perf0 attach returned 6 > > panic: resource_list_add: resource entry is busy > > KDB: enter: panic > > [thread pid 0 tid 0 ] > > Stopped at kdb_enter+0x2c: leave > > db> trace > > Tracing pid 0 tid 0 td 0xc064c160 > > kdb_enter() at kdb_enter+0x2c > > panic() at panic+0x122 > > resource_list_add(c1a5b710,4,0,b2,b3) at resource_list_add+0x7f > > bus_generic_rl_set_resource(...) at bus_generic_rl_set_resource+0x60 > > bus_set_resource(...) at bus_set_resource+0x4c > > acpi_bus_alloc_gas(...) at acpi_bus_alloc_gas+0x93 > > acpi_PkgGas(...) at acpi_PkgGas+0x4e > > acpi_perf_probe(...) at acpi_perf_probe+0xea > > device_probe_and_attach(...) at device_probe_and_attach+0xf8 > > bus_generic_attach(...) at bus_generic_attach+0x12 > > acpi_cpu_attach(...) at acpi_cpu_attach+0x2a1 > > ... > >=20 > > How to fix that ?=20 > >=20 >=20 > Ok, I've committed a fix: acpi.c rev 1.207. Please cvsup and test. It does not help, still same panic /sys/dev/acpica# fgrep /acpi.c/ CVS/Entries /acpi.c/1.207/Wed Mar 23 07:28:31 2005// /sys/dev/acpica#=20 --=20 Vladimir B. Grebenchikov vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1111611460.1805.1.camel>