public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Dave Jones <davej@suse.de>, Benjamin Pharr <ben@benpharr.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.5-dj1 - Bug Reports
Date: Fri, 22 Feb 2002 02:23:29 +0100	[thread overview]
Message-ID: <20020222022329.A3533@suse.cz> (raw)
In-Reply-To: <20020221233700.GA512@hst000004380um.kincannon.olemiss.edu> <20020222022149.N5583@suse.de>
In-Reply-To: <20020222022149.N5583@suse.de>; from davej@suse.de on Fri, Feb 22, 2002 at 02:21:49AM +0100

On Fri, Feb 22, 2002 at 02:21:49AM +0100, Dave Jones wrote:
>  > It compiled fine. When I booted up everything looked normal with the
>  > exception of a 
>  > eth1: going OOM 
>  > message that kept scrolling down the screen. My eth1 is a natsemi card.
> 
>  That's interesting. Probably moreso for Manfred. I'll double check
>  I didn't goof merging the oom-handling patch tomorrow.
> 
>  > Eventually that stopped and gdm came up. For some reason my keyboard and
>  > mouse wouldn't work.
> 
>  -dj includes a different input layer to Linus' tree, which requires
>  some extra options enabled.  Vojtech, this is quite a frequent
>  'bug report', and I think if you merged that with Linus, the number
>  of reports would climb. Is there a possibility of simplifying the
>  config.in somewhat? Or at least changing the defaults to give the
>  element of least surprise..

The defaults are changed :(. However people coying their .configs over
don't use the defaults. The help files say what to do in case of doubt.
I'm not sure what more I can do.

I'll try to think about that.

>  > It got to check.c in fs/partitions before stopping with an error.
> 
>  That one I've not got an answer for. Can you give me more information
>  about your disk layout, partitions, number of disks, scsi?/ide?/lvm?
>  
> -- 
> | Dave Jones.        http://www.codemonkey.org.uk
> | SuSE Labs

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-02-22  1:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 23:37 Linux 2.5.5-dj1 - Bug Reports Benjamin Pharr
2002-02-22  1:21 ` Dave Jones
2002-02-22  1:23   ` Vojtech Pavlik [this message]
2002-02-23 21:28     ` Pavel Machek
2002-02-24 21:00     ` Linux 2.5.5-dj1 - problem with /dev/input/mice Ben Clifford
2002-02-24 21:27       ` Vojtech Pavlik
2002-02-24 21:42         ` Ben Clifford
2002-02-24 21:45           ` Vojtech Pavlik
2002-02-28  9:58         ` Pavel Machek
2002-02-22  6:37   ` Linux 2.5.5-dj1 - Bug Reports Nathan Walp
2002-02-28 16:59     ` Nathan Walp
2002-02-28 19:57       ` Benjamin Pharr
2002-02-28 20:47       ` Dave Jones
2002-03-01 18:12     ` Manfred Spraul
2002-02-24 21:02   ` Linux 2.5.5-dj1 - IPv6 not loading correctly Ben Clifford
2002-02-25  6:16     ` Ben Clifford
2002-02-25 21:32       ` Dave Jones
2002-02-25 22:18         ` David S. Miller
2002-02-27 20:23           ` Arnaldo Carvalho de Melo

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=20020222022329.A3533@suse.cz \
    --to=vojtech@suse.cz \
    --cc=ben@benpharr.com \
    --cc=davej@suse.de \
    --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