Date: Wed, 03 Feb 2010 19:40:06 +0200 From: Alexander Motin <mav@FreeBSD.org> To: David Wolfskill <david@catwhisker.org>, FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: "shutdown -p": (noperiph:aacp0:0:6:0): Device power down failed Message-ID: <4B69B4F6.1090608@FreeBSD.org> In-Reply-To: <mailpost.1265216441.7126101.44882.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw> References: <20100203144037.GA32250@bunrab.catwhisker.org> <mailpost.1265216441.7126101.44882.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
David Wolfskill wrote: > On Wed, Feb 03, 2010 at 06:40:37AM -0800, David Wolfskill wrote: >> Just updated my build machine from r203376 to r203425, which seeme dto >> go well, but after I issued "shutdown -p now" (as I leave the machine >> off when it's not in use), I saw the following on the serial console: >> >> Uptime: 1m45s >> (noperiph:aacp0:0:0:0): Device power down failed >> (noperiph:aacp0:0:1:0): Device power down failed >> (noperiph:aacp0:0:2:0): Device power down failed >> (noperiph:aacp0:0:3:0): Device power down failed >> (noperiph:aacp0:0:6:0): Device power down failed >> Kernel page fault with the following non-sleepable locks held: >> exclusive sleep mutex AAC I/O lock (AAC I/O lock) r = 0 (0xc56f2130) locked @ /usr/src/sys/dev/aac/aac.c:844 >> KDB: stack backtrace: >> db_trace_self_wrapper(c0ca2cb6,e9aefb14,c08d68a5,c0c48d6b,34c,...) at db_trace_self_wrapper+0x26 >> ... >> I'll leave the machine in that state so I can poke at it, if there's >> interest in figuring out what's wrong. My laptop is a bit behind >> the build machine at the moment -- it's just started building the >> stable/8 kernel -- but I expect to be building head on it soon, and >> I'll report if anything interesting turns up. That was my change r203420. `sysctl kern.cam.power_down=0` should disable new behavior. It can be a bug of aac driver. Is it repeatable each time at the same place? > Tried the same experiment with the laptop; didn't get the above failure, > but am seeing many (as in "hundreds") of > > atapi_poll called! > atapi_poll called! This looks like atapicam misfeature. I'll look on it. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B69B4F6.1090608>