public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bestel <xavier.bestel@free.fr>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.4.19-pre1-ac1] usbnet frames mangled
Date: 04 Mar 2002 19:15:34 +0100	[thread overview]
Message-ID: <1015265735.3055.3.camel@bip> (raw)
In-Reply-To: <20020304174939.GB3267@kroah.com>
In-Reply-To: <1015003428.2274.5.camel@bip> <20020302071545.GB20536@kroah.com> <1015073017.777.0.camel@bip>  <20020304174939.GB3267@kroah.com>

le lun 04-03-2002 à 18:49, Greg KH a écrit :
> On Sat, Mar 02, 2002 at 01:43:36PM +0100, Xavier Bestel wrote:
> > le sam 02-03-2002 à 08:15, Greg KH a écrit :
> > > On Fri, Mar 01, 2002 at 06:23:48PM +0100, Xavier Bestel wrote:
> > > > 
> > > > which of course doesn't mean anything. I saw this behavior since I
> > > > upgraded my desktop from 2.4.18-ac2 to 2.4.19-pre1-ac1
> > > 
> > > So you kept your USB client at the same version, but your host changed
> > > versions?  And 2.4.18-ac2 works, but 2.4.19-pre1-ac1 doesn't?
> > 
> > That's it.
> > 
> > > Can you see if 2.4.19-pre2 works or not for you?
> > 
> > It works pretty well.
> 
> So you don't have a problem with 2.4.19-pre2?  Great :)

Err ... I just understood today the freeze problems I had are due to
USB, but didn't manage to produce a valid testcase yet.
Apparently, if I plug back my ipaq then modprobe usbnet, the desktop
hangs. If I modprobe first, it works well.

	Xav


      reply	other threads:[~2002-03-04 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 17:23 [2.4.19-pre1-ac1] usbnet frames mangled Xavier Bestel
2002-03-02  7:15 ` Greg KH
2002-03-02 12:43   ` Xavier Bestel
2002-03-04 17:49     ` Greg KH
2002-03-04 18:15       ` Xavier Bestel [this message]

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=1015265735.3055.3.camel@bip \
    --to=xavier.bestel@free.fr \
    --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