Date: Thu, 23 Jul 2009 11:54:03 +0300 From: Dan Naumov <dan.naumov@gmail.com> To: "C. C. Tang" <hiyorin@gmail.com> Cc: Attilio Rao <attilio@freebsd.org>, barbara <barbara.xxx1975@libero.it>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: 7.2-release/amd64: panic, spin lock held too long Message-ID: <cf9b1ee00907230154m6eb8f0aeh1eb8fdf53346bacd@mail.gmail.com> In-Reply-To: <4A67C9C7.6090301@gmail.com> References: <KN4BGI$40ABF3E58EAD1201403C9DA561E2402F@libero.it> <4A667469.1080805@gmail.com> <3bbf2fe10907220930y27b5da04sd0a71d57b6a9d191@mail.gmail.com> <4A67C9C7.6090301@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 23, 2009 at 5:24 AM, C. C. Tang<hiyorin@gmail.com> wrote: > Attilio Rao wrote: >> >> 2009/7/22 C. C. Tang <hiyorin@gmail.com>: >>>> >>>> Could that one (on i386) be related? >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/134584 >>>> >>> I have no idea about it but I can tell the difference... >>> My machine panic randomly rather than on shutdown and I remembered that >>> it >>> failed to write core dump. It also failed to reboot automatically.. >> >> Is your problem on -CURRENT and amd64? >> At some point there has been a problem with PAT support (and >> tlb_shootdowns() could lead to a livelock hanging forever, leading to >> such a bug) but I expect it is fixed now. >> Can you try with a fresh new -CURRENT if any? > > My problem is on i386 version of 7.2-RELEASE-p2 on Intel Atom 330 CPU. > And my system just panic randomly with "spin lock held too long". > It didn't panic at reboot or shutdown so I think it the problem is somewh= at > different from that mentioned by Barbara's PR? > > Anyway I disabled powerd and it seems become stable now. > > And I am sorry that my system has been put into service so it would be ha= rd > for me to switch to -CURRENT... =A0:( > > Regards, > C.C. My problem was essentially the same, completely random "spin lock held too long" panics not related to reboots or shutdowns, the only difference was that I was on amd64. I too was running powerd on the system, but it didn't cross my mind that it could've been the culprit. Hopefully I will get a chance to test FreeBSD again on the same hardware at some point, with and without powerd. Rather sad if powerd is the actual cause, considering that the whole point of using an Atom-based system is powersaving :( - Sincerely, Dan Naumov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cf9b1ee00907230154m6eb8f0aeh1eb8fdf53346bacd>