Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Nov 2012 09:56:15 +0000
From:      Tom Lislegaard <Tom.Lislegaard@proact.no>
To:        'Andriy Gapon' <avg@FreeBSD.org>
Cc:        "freebsd-acpi@FreeBSD.org" <freebsd-acpi@FreeBSD.org>, "freebsd-stable@FreeBSD.org" <freebsd-stable@FreeBSD.org>
Subject:   RE: 9-Stable panic: resource_list_unreserve: can't find resource
Message-ID:  <E8A24BEFDC390C4491718DEE8A9C4F20920DD1@Semail03.proact.local>
In-Reply-To: <5092F209.7090803@FreeBSD.org>
References:  <E8A24BEFDC390C4491718DEE8A9C4F2091F824@Semail03.proact.local> <509172F6.2040400@FreeBSD.org> <E8A24BEFDC390C4491718DEE8A9C4F2091FC33@Semail03.proact.local> <5092F209.7090803@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help


> -----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 <Address 0x1 out of bounds=
>) 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 <ta=
skqueue_thread_loop>,
> >> 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' <repeats 47 times>, 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E8A24BEFDC390C4491718DEE8A9C4F20920DD1>