Date: Tue, 09 Nov 2004 14:39:45 -0500 From: Adam K Kirchhoff <adamk@voicenet.com> To: Nate Lawson <nate@root.org> Cc: freebsd-acpi@freebsd.org Subject: Re: Laptop troubles... Message-ID: <41911D01.1090303@voicenet.com> In-Reply-To: <419113BA.9000806@root.org> References: <41910F00.3070402@voicenet.com> <419113BA.9000806@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Nate Lawson wrote: > Adam K Kirchhoff wrote: > >> Not sure the correct list for this problem, but since I think I've >> traced the problem back to ACPI, it gonna go to this list first :-) >> >> Basically, I have a cvsup config file to pull RELENG_5. I built a >> kernel and world on my HP Omnibook on the 29th of October, and it >> works great. I updated my source tree today, though (November 9th), >> rebuilt the kernel + world, and my system hangs shortly after my >> system starts up some services (usually sshd or nfsd). If I boot up, >> with ACPI disabled, I don't have this problem. I also don't have any >> acpi functionality :-) Not a great tradeoff. > > > What happens if you boot single-user? So far, it's been fine. I've been in single user long enough to run fsck on my filesystems... I launched sshd manually once (without any problems) since that's where it appeared to lockup most frequently. When I then continued into multi-user mode, it locked up around the time it loaded the linux compat module. >> Any ideas what may have changed between October 29th and today, or >> how I can track down this problem? > > > A lot of minor changes were MFCd yesterday. > >> Unfortunately, nothing comes on the console. No debugger, no panic, >> etc. > > > You can't break to the debugger with ctrl-alt-backspace? Nope. Didn't realize that was usually a possibility, but when I tried it just now, it didn't break into the debugger. >> I'm attaching a syslog from my current bootup (with the kernel from >> October 29th), and a syslog from a failed bootup (with today's >> kernel). Nothing is jumping out at me, but that doesn't necessarily >> mean anything. >> >> I also noticed this problem back around the 29th of October when I >> considerd installing -CURRENT on it. When that happened, I changed >> my cvsup file to RELENG_5 > > > Try a boot -v -s with the bad kernel and see how long it takes to hang > while sitting there idle. > Well, so far so good. I've booted up with -s and -v... fsck'ed the filesystems, and I'm now sitting at the single user prompt. I ifconfiged my wireless card, and all seems well. I'm about to leave work for the day. I'll leave it like this during my drive home and see if it stays running the entire time. When I'm home, I'll reboot with -v -s and dump the kernel output to the serial port, and then post it here. Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41911D01.1090303>