public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ben Collins <bcollins@debian.org>
Cc: Marcel Lanz <marcel.lanz@ds9.ch>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PANIC] ohci1394 & copy large files
Date: Mon, 05 Apr 2004 09:00:24 +1000	[thread overview]
Message-ID: <1081119623.1285.121.camel@gaston> (raw)
In-Reply-To: <20040404141339.GW13168@phunnypharm.org>

On Mon, 2004-04-05 at 00:13, Ben Collins wrote:
> On Sun, Apr 04, 2004 at 04:16:00PM +0200, Marcel Lanz wrote:
> > Since 2.6.4 and still in 2.6.5 I get regurarly a Kernel panic if I try
> > to backup large files (10-35GB) to an external attached disc (200GB/JFS) via ieee1394/sbp2.
> > 
> > Has anyone similar problems ?
> 
> Known issue, fixed in our repo. I still need to sync with Linus once I
> iron one more issue and merge some more patches.

Hi Ben !

I don't want to be too critical or harsh or whatever, but why don't you
just send such fixes right upstream instead of stacking patches for a
while in your repo ? From my experience, such "batching" of patches is
the _wrong_ thing to do, and typically, there is a major useability
issue with sbp2 that could have been "right" in 2.6.5 final and will not
be (so we'll have to wait what ? 1 or 2 monthes more now to have a
release kernel with a reliable sbp2)

Ben.



  reply	other threads:[~2004-04-04 23:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-04 14:16 [PANIC] ohci1394 & copy large files Marcel Lanz
2004-04-04 14:13 ` Ben Collins
2004-04-04 23:00   ` Benjamin Herrenschmidt [this message]
2004-04-04 23:17     ` Ben Collins
2004-04-04 23:28       ` Randy.Dunlap
2004-04-05  0:09         ` Ben Collins
2004-04-05  0:07       ` Benjamin Herrenschmidt
2004-04-05  0:12         ` Ben Collins
2004-04-05  5:03   ` Dmitry Torokhov
2004-04-05 13:44     ` Ben Collins

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=1081119623.1285.121.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel.lanz@ds9.ch \
    /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