mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Luuk van der Duim <l.a.van.der.duim@student.rug.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.5.59-mm6
Date: Mon, 27 Jan 2003 19:50:24 +0100	[thread overview]
Message-ID: <5.1.1.6.2.20030127191904.00cc2508@pop.gmx.net> (raw)
In-Reply-To: <1043670419.1691.30.camel@cc75757-a.groni1.gr.home.nl>

At 01:27 PM 1/27/2003 +0100, Luuk van der Duim wrote:
>Hello mm-users,
>
>
>   . The mysterious "machine hangs late in boot" problem has been narrowed
>     down thanks to some great work by Andres Salomon.  The machine is stuck
>     waiting on I/O completion when performing the initial lookup for
>     /sbin/devfs_helper:
>
>
>I don't believe it to be an exclusively small-devfs helper problem.

Well, my test box agrees (I have never ever used devfs, but could lock hard 
in minutes)  mm6 works fine here, so I _think_ it's probably resolved...

>It is an interaction at best. Sure I had problems using devfs-small, but
>mm2 worked and mm3 was the first that halted during boot. Both have
>devfs-small, and both need its helper. Or I am missing a subtlety here?

I don't think you're missing anything, but I also don't know wtf the 
interaction is.  I put a couple of man-days into looking for it, and came 
up with exactly nada of interest.

>Secondly, Andrew sent me a rollup of patches against 2.5.59 he thought
>were suspicious, without smalldevfs and it also halted, but at another
>place in boot, at adding swap.

Mine locked hard hard hard.  Booted fine, but died reliably under heavy load.

(something seems funky with nmi_watchdog... hard lock = no_more_nmi_ticks 
.  Anybody out there know enough about local APIC to explain why idle=poll 
gives nice 1 second nmi, but everything else depends upon cpu load?... and 
why when hardlock happens, it _stops_)

>Can someone besides me confirm this behavior or am I the loon who just
>won't understand?

My box agrees that you're not a loon fwTw :)

         -Mike


  reply	other threads:[~2003-01-27 18:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 12:27 2.5.59-mm6 Luuk van der Duim
2003-01-27 18:50 ` Mike Galbraith [this message]
2003-01-27 19:17   ` 2.5.59-mm6 Zwane Mwaikambo
     [not found]   ` <Pine.LNX.4.44.0301271414230.28141-100000@montezuma.mastece nde.com>
2003-01-27 20:11     ` 2.5.59-mm6 Mike Galbraith
2003-01-27 21:13       ` 2.5.59-mm6 Zwane Mwaikambo
  -- strict thread matches above, loose matches on Subject: below --
2003-01-27  7:10 2.5.59-mm6 Andrew Morton
2003-01-27  8:17 ` 2.5.59-mm6 Andres Salomon
2003-01-27  8:24   ` 2.5.59-mm6 Joshua Kwan
2003-01-27  8:40     ` 2.5.59-mm6 Andrew Morton
2003-01-27  8:46       ` 2.5.59-mm6 Joshua Kwan
2003-01-27  9:51 ` 2.5.59-mm6 Helge Hafting

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.1.6.2.20030127191904.00cc2508@pop.gmx.net \
    --to=efault@gmx.de \
    --cc=l.a.van.der.duim@student.rug.nl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®