From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 2 09:56:29 2012 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1788D4A0; Fri, 2 Nov 2012 09:56:29 +0000 (UTC) (envelope-from Tom.Lislegaard@proact.no) Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe005.messaging.microsoft.com [216.32.180.188]) by mx1.freebsd.org (Postfix) with ESMTP id C49238FC14; Fri, 2 Nov 2012 09:56:28 +0000 (UTC) Received: from mail100-co1-R.bigfish.com (10.243.78.245) by CO1EHSOBE008.bigfish.com (10.243.66.71) with Microsoft SMTP Server id 14.1.225.23; Fri, 2 Nov 2012 09:56:21 +0000 Received: from mail100-co1 (localhost [127.0.0.1]) by mail100-co1-R.bigfish.com (Postfix) with ESMTP id C52355401C5; Fri, 2 Nov 2012 09:56:21 +0000 (UTC) X-Forefront-Antispam-Report: CIP:212.214.215.133; KIP:(null); UIP:(null); IPV:NLI; H:semtaout01.proact.se; RD:semtaout01.proact.se; EFVD:NLI X-SpamScore: -7 X-BigFish: VPS-7(zzbb2dI542M1432Izz1de0h1d18h1202h1d1ah1d2ahzz8275dhz2dh668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h) Received: from mail100-co1 (localhost.localdomain [127.0.0.1]) by mail100-co1 (MessageSwitch) id 1351850178833372_24694; Fri, 2 Nov 2012 09:56:18 +0000 (UTC) Received: from CO1EHSMHS010.bigfish.com (unknown [10.243.78.244]) by mail100-co1.bigfish.com (Postfix) with ESMTP id C711A1C006B; Fri, 2 Nov 2012 09:56:18 +0000 (UTC) Received: from semtaout01.proact.se (212.214.215.133) by CO1EHSMHS010.bigfish.com (10.243.66.20) with Microsoft SMTP Server id 14.1.225.23; Fri, 2 Nov 2012 09:56:17 +0000 Received: from Semail04.proact.local (unknown [10.7.1.58]) by semtaout01.proact.se (Postfix) with ESMTP id 82AFD5727C; Fri, 2 Nov 2012 10:56:16 +0100 (CET) Received: from SEMAIL03.proact.local ([fe80::a52b:385d:b44f:ecb9]) by Semail04.proact.local ([fe80::885:6e64:c1e6:dcf1%20]) with mapi id 14.02.0318.001; Fri, 2 Nov 2012 10:56:16 +0100 From: Tom Lislegaard To: 'Andriy Gapon' Subject: RE: 9-Stable panic: resource_list_unreserve: can't find resource Thread-Topic: 9-Stable panic: resource_list_unreserve: can't find resource Thread-Index: Ac23UHFrRe/nHcv4QJaCSOXSiMVayQAP8Y0AACFOYqAAF8a9gAAYYgXw Date: Fri, 2 Nov 2012 09:56:15 +0000 Message-ID: References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> In-Reply-To: <5092F209.7090803@FreeBSD.org> Accept-Language: en-US, sv-SE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.1.59] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: proact.no Cc: "freebsd-acpi@FreeBSD.org" , "freebsd-stable@FreeBSD.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2012 09:56:29 -0000 > -----Original Message----- > From: Andriy Gapon [mailto:avg@FreeBSD.org] > Sent: 1. november 2012 23:05 > To: Tom Lislegaard > Cc: freebsd-stable@FreeBSD.org; freebsd-acpi@FreeBSD.org > Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource >=20 > on 01/11/2012 11:45 Tom Lislegaard said the following: > > > > > >> -----Original Message----- > >> From: Andriy Gapon [mailto:avg@FreeBSD.org] > >> Sent: 31. oktober 2012 19:51 > >> To: Tom Lislegaard > >> Cc: 'freebsd-stable@freebsd.org' > >> Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resou= rce > >> > >> on 31/10/2012 12:14 Tom Lislegaard said the following: > >>> Hi > >>> > >>> I'm running > >>> FreeBSD stingray 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #3: Mon Oct 29= 16:11:35 CET 2012 > >> tl@stingray:/usr/obj/usr/src/sys/stingray amd64 > >>> on a new Dell laptop and keep getting these panics (typically once or= twice per day) > >>> > >>> (kgdb) set pagination off > >>> (kgdb) bt > >>> #0 doadump (textdump=3DVariable "textdump" is not available. > >>> ) at pcpu.h:229 > >>> #1 0xffffffff80425e64 in kern_reboot (howto=3D260) at /usr/src/sys/k= ern/kern_shutdown.c:448 > >>> #2 0xffffffff8042634c in panic (fmt=3D0x1
) at > >> /usr/src/sys/kern/kern_shutdown.c:636 > >>> #3 0xffffffff8045773e in resource_list_unreserve (rl=3DVariable "rl"= is not available. > >>> ) at /usr/src/sys/kern/subr_bus.c:3338 > >>> #4 0xffffffff802c3ee4 in acpi_delete_resource (bus=3D0xfffffe00052c1= 100, child=3D0xfffffe00052c1500, > >> type=3D4, rid=3D3323) at /usr/src/sys/dev/acpica/acpi.c:1405 > >>> #5 0xffffffff802c62bc in acpi_bus_alloc_gas (dev=3D0xfffffe00052c150= 0, type=3D0xfffffe00052b786c, > >> rid=3D0xfffffe00052b7978, gas=3DVariable "gas" is not available. > >>> ) at /usr/src/sys/dev/acpica/acpi.c:1450 > >>> #6 0xffffffff802d1663 in acpi_PkgGas (dev=3D0xfffffe00052c1500, res= =3DVariable "res" is not > available. > >>> ) at /usr/src/sys/dev/acpica/acpi_package.c:120 > >>> #7 0xffffffff802cbf6b in acpi_cpu_cx_cst (sc=3D0xfffffe00052b7800) a= t > >> /usr/src/sys/dev/acpica/acpi_cpu.c:782 > >>> #8 0xffffffff802cc3a4 in acpi_cpu_notify (h=3DVariable "h" is not av= ailable. > >>> ) at /usr/src/sys/dev/acpica/acpi_cpu.c:1050 > >>> #9 0xffffffff802a3fca in AcpiEvNotifyDispatch (Context=3D0x0) at > >> /usr/src/sys/contrib/dev/acpica/events/evmisc.c:283 > >>> #10 0xffffffff802c26c3 in acpi_task_execute (context=3D0xfffffe00051d= 6800, pending=3DVariable > "pending" > >> is not available. > >>> ) at /usr/src/sys/dev/acpica/Osd/OsdSchedule.c:134 > >>> #11 0xffffffff804683c4 in taskqueue_run_locked (queue=3D0xfffffe00052= bc100) at > >> /usr/src/sys/kern/subr_taskqueue.c:308 > >>> #12 0xffffffff80469366 in taskqueue_thread_loop (arg=3DVariable "arg"= is not available. > >>> ) at /usr/src/sys/kern/subr_taskqueue.c:497 > >>> #13 0xffffffff803f762f in fork_exit (callout=3D0xffffffff80469320 , > >> arg=3D0xffffffff80a20cc8, frame=3D0xffffff80002cdb00) at /usr/src/sys/= kern/kern_fork.c:992 > >>> #14 0xffffffff806be6be in fork_trampoline () at /usr/src/sys/amd64/am= d64/exception.S:602 > >> > >> Could you please provide *sc from frame 7? > > > > (kgdb) up 7 > > #7 0xffffffff802cbf6b in acpi_cpu_cx_cst (sc=3D0xfffffe00052b7800) at > /usr/src/sys/dev/acpica/acpi_cpu.c:782 > > 782 acpi_PkgGas(sc->cpu_dev, pkg, 0, &cx_ptr->res_type, &sc->cpu_rid, > > (kgdb) print *sc > > $1 =3D {cpu_dev =3D 0xfffffe00052c1500, cpu_handle =3D 0xfffffe00052e7a= 80, cpu_pcpu =3D 0xffffffff80aa6a80, > cpu_acpi_id =3D 1, cpu_p_blk =3D 1040, cpu_p_blk_len =3D 6, cpu_cx_states= =3D {{p_lvlx =3D 0xfffffe0196f0e380, > type =3D 1, trans_lat =3D 1, power =3D 1000, res_type =3D 4}, {p_lvlx =3D= 0x0, type =3D 3, trans_lat =3D 87, power =3D > 200, res_type =3D 4}, {p_lvlx =3D 0x0, type =3D 3, trans_lat =3D 87, powe= r =3D 200, res_type =3D 4}, {p_lvlx =3D > 0x0, type =3D 0, trans_lat =3D 0, power =3D 0, res_type =3D 0}, {p_lvlx = =3D 0x0, type =3D 0, trans_lat =3D 0, power > =3D 0, res_type =3D 0}, {p_lvlx =3D 0x0, type =3D 0, trans_lat =3D 0, pow= er =3D 0, res_type =3D 0}, {p_lvlx =3D 0x0, > type =3D 0, trans_lat =3D 0, power =3D 0, res_type =3D 0}, {p_lvlx =3D 0x= 0, type =3D 0, trans_lat =3D 0, power =3D 0, > res_type =3D 0}}, cpu_cx_count =3D 2, cpu_prev_sleep =3D 619, cpu_feature= s =3D 31, cpu_non_c3 =3D 1, > cpu_cx_stats =3D {390, 0, 0, 0, 0, 0, 0, 0}, cpu_sysctl_ctx =3D {tqh_firs= t =3D 0xfffffe00088931a0, tqh_last > =3D 0xfffffe0008893228}, cpu_sysctl_tree =3D 0x0, cpu_cx_lowest =3D 0, cp= u_cx_lowest_lim =3D 0, > ! > cpu_cx_s > upported =3D "C1/1 C2/59 C3/87", '\0' , cpu_rid =3D 332= 3} >=20 > Thank you. > Did this crash occur at the time when you plugged or unplugged AC line? > Do you plug and unplug the line often? > Do you think that the line could have any problems like flaky contacts or= some such? >=20 >=20 > -- > Andriy Gapon The machine is usually connected to a docking station and I believe the pow= er is very stable. I sometimes take it home and connect it to a different p= owersupply and sees the same behavior with panics there. Panics can occur w= hile I'm at the machine working, or if I leave the machine idle for some ti= me I find it has paniced/rebooted when I come back. The time of panic seems totally random and I can't correlate this to any pa= rticular activity like cronjobs, etc. -tom