This makes me think about a problem I had with an Eeepc a while back. I
never reported it because I tracked that down to a faulty SSD that would
just hang the machine when accessing certain sectors.
The way I verified this was to run "dd if=/dev/rwd0c of=/dev/null bs=1m"
(with the appropriate device node for your drive) and see if it completes.
Do this for all your mounted drives and you may find the culprit.
2012/12/25 Philip Guenther <guent...@gmail.com>
> On Tue, Dec 25, 2012 at 2:57 PM, frantisek holop <min...@obiit.org> wrote:
> > hmm, on Tue, Dec 25, 2012 at 11:31:43PM +0100, Marc Espie said that
> >> On Tue, Dec 25, 2012 at 11:23:06PM +0100, frantisek holop wrote:
> >> > (difficult to believe no people see this, every notebook
> >> > i had since 2008 could not shutdown cleanly 50-70%
> >> > of the time)
> >>
> >> I don't know what you do with your machines, or what specific hw you
> >> have that causes this. My machines shutdown gracefully most of the time.
>
> I'll second that. When mine hang it's because I have a bug in
> whatever diff I'm working on...
>
>
> > (the dmesgs of all my current and previous notebooks can be
> > found in the misc archive). thinkpad, ideapad, eeepc,
> > all of them showed this behaviour. i use these machines
> > for simple daily use. browsing, some development work,
> > etc. as every day as it gets for unix users.
>
> So start eliminating differences. Does it hang over night if you
> never login? If not, then it's something you're running that does it.
> So login and logout and see whether it's some daemon started by your
> .xsession (dbus? that gkrellm thing that caused a 1+ load?) that
> causes it. If it does hang even if you don't login, then start
> checking off the system daemons. What if X is never started? Heck,
> boot to single user and leave it there over night.
>
> You were seeing ACPI taking more and more memory before; is that still
> happening? Is there a correlation between that and the hangs?
>
> Make a hypothesis ("it's caused by something in my .xsession"), come
> up with a way to test it ("see if it happens if I don't login") then
> do so. You have a problem; do SCIENCE on it.
>
>
> > there are normally 2 ways of unclean shutdown:
> > either "syncing now" and never "done", or
> > (on this ideapad) simply black screen, presumably
> > still part of X, and never going to the console.
>
> > i made this script to minimize damage:
> >
> > $ cat bin/ha.sh
> > #!/bin/sh
> >
> > sudo sync
> > sudo mount -u -r /data
> > sudo halt -p
>
> Does the hang in sync happen if you're not running any processes as
> you? Only happens if certain filesystems are mounted? What are the
> prerequisites on it hanging?
>
> Since this doesn't seem to affect developers, you're going to have to
> do the science.
>
>
> Philip Guenther
>
>
--
La brigade SnW veut vous recruter - http://www.brigadesnw.ca
