mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Schaber <schabios@logi-track.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at drivers/usb/storage/usb.c:848
Date: Mon, 5 Jul 2004 17:12:25 +0200	[thread overview]
Message-ID: <20040705171225.7767408b@kingfisher.intern.logi-track.com> (raw)
In-Reply-To: <20040702224927.GB7969@kroah.com>

Hi, Greg,

On Fri, 2 Jul 2004 15:49:27 -0700
Greg KH <greg@kroah.com> wrote:

> > Running Kernel 2.6.4-mm2 (We use an mm2 kernel because of problems
> > with highmem and cryto-loop playing together which seemed to be
> > solved in mm2) and dd'ing from a IDE disk in an external USB case,
> > the following just happened (from /var/log/syslog):
> 
> 2.6.4-mm2 is quite an old kernel.  Care to get a newer one to see if
> this is still an issue or not?

It's quite some effort to update those specific machines, but we planned
to update to 2.6.7 until we heared that there are some problems with
this version (especially, a co-worker of mine trying 2.6.7-mm1 on a
similar hardware and using both crypto-loop and highmem has had random
crashes, and some apps (including sun jdk 1.4) segfaulting on startup.).

Now we plan to update to some 2.6.6 version. Is dm-crypt considered
stable enough to give it a test shot? This way, we could get rid of
crypto-loop and thus avoid having to try the mm patches.


Thanks,
Markus

-- 
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios@logi-track.com | www.logi-track.com

      reply	other threads:[~2004-07-05 15:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 10:18 Markus Schaber
2004-07-02 22:49 ` Greg KH
2004-07-05 15:12   ` Markus Schaber [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=20040705171225.7767408b@kingfisher.intern.logi-track.com \
    --to=schabios@logi-track.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®