mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felix Seeger <felix.seeger@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB mouse problem, kernel panic on startup in 2.4.19
Date: Tue, 27 Aug 2002 22:48:07 +0200	[thread overview]
Message-ID: <200208272248.10846.felix.seeger@gmx.de> (raw)
In-Reply-To: <20020827193632.GD23865@kroah.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Dienstag, 27. August 2002 21:36 schrieb Greg KH:
> On Tue, Aug 27, 2002 at 09:30:11PM +0200, Felix Seeger wrote:
> > No, sorry. Doesn't help.
> > Is that a patch for 2.4.20-pre4 ? I am using 2.4.19.
>
> Yes it is, but it might apply to 2.4.19.  I am guessing you tried it,
> and it applied cleanly?  Any build errors?
Yes I tried it and there were no build errors. Only a message during the 
patch.

I copied the patch to the top level kernel dir.
Than I've done a "patch -p1 < patchfile"

I get this:
patching file drivers/usb/usb-ohci.c
Hunk #3 succeeded at 2285 (offset -13 lines).

After that: make dep, make bzImage, make modules, make modules install, copy, 
lilo

Something I fogot:
If I put the mouse in the problematic port after startup, everything works 
fine.

> > Oh, the shift and the numlock leds are blinking.
>
> That means the kernel paniced :)

Nice feature

> thanks,
>
> greg k-h


have fun
Felix
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9a+WKS0DOrvdnsewRAgoAAJ4i9FPy+7HI674Zn9VHTXF9qf54aQCeIOo5
h54EAjXg0VF0rrTHu+pF4Dk=
=xpHA
-----END PGP SIGNATURE-----


  reply	other threads:[~2002-08-27 20:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27 18:11 Felix Seeger
2002-08-27 18:23 ` Felix Seeger
2002-08-27 18:31   ` Greg KH
2002-08-27 19:30     ` Felix Seeger
2002-08-27 19:36       ` Greg KH
2002-08-27 20:48         ` Felix Seeger [this message]
2002-08-27 20:00       ` Thunder from the hill

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=200208272248.10846.felix.seeger@gmx.de \
    --to=felix.seeger@gmx.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 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®