All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan <wfilardo@fuse.net>
To: Dave Jones <davej@suse.de>
Cc: Greg KH <greg@kroah.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Issues with 2.5.3-dj1
Date: Sat, 02 Feb 2002 20:04:34 -0500	[thread overview]
Message-ID: <3C5C8CA2.9000103@fuse.net> (raw)
In-Reply-To: <3C5B5EC0.40503@fuse.net> <20020202055115.GA11359@kroah.com> <3C5B8C0D.8090009@fuse.net> <20020202133358.A5738@suse.de>

Dave Jones wrote:

>On Sat, Feb 02, 2002 at 01:49:49AM -0500, Nathan wrote:
>
> > Alright... a 2.5.3 with no extras boots fine (with init=/bin/bash) and 
> > can load and unload hotplug several times without OOPSing.  So it 
> > appears to be something else.  Hope that helps.
>
> Do you have driverfs mounted ? Can you try 2.5.3 + greg's
> USB driverfs patch ?
>
Unless driverfs is mounted by default or by something other than 
/etc/fstab, no I don't have it on.

w/ Greg's USB driverfs patch : system proves to be stable.
    (though 2.5.3 sometimes looses my keyboard after a time?)

Raw -dj1:  explosion as above. [no ACPI (doesn't compile anyway), no 
preempt this time around, either.]
    (also lost my keyboard.  Odd.  Seems to be about 50% of the time 
with 2.5.3 + anything.)

--Nathan



  reply	other threads:[~2002-02-03  1:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-02  3:36 Issues with 2.5.3-dj1 Nathan
2002-02-02  5:51 ` Greg KH
2002-02-02  6:49   ` Nathan
2002-02-02 12:33     ` Dave Jones
2002-02-03  1:04       ` Nathan [this message]
2002-02-03  6:21         ` Greg KH
2002-02-03  6:30           ` Nathan
2002-02-03 14:02             ` Dave Jones
2002-02-03 15:05               ` Vojtech Pavlik
2002-02-02 11:19   ` Allan Sandfeld
  -- strict thread matches above, loose matches on Subject: below --
2002-02-02 13:36 Andreas Happe

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=3C5C8CA2.9000103@fuse.net \
    --to=wfilardo@fuse.net \
    --cc=davej@suse.de \
    --cc=greg@kroah.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.