From: Mike Christie <michaelc@cs.wisc.edu>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: 2.6.20.3: kernel BUG at mm/slab.c:597 try#2
Date: Mon, 19 Mar 2007 12:49:57 -0500 [thread overview]
Message-ID: <45FECD45.20705@cs.wisc.edu> (raw)
In-Reply-To: <45FDDA8E.8030100@domdv.de>
Andreas Steinmetz wrote:
> As posted to lkml and linux-scsi on 2007-03-15 without reply, see
> http://marc.info/?l=linux-kernel&m=117395128412313&w=2 for original post:
>
> It is not so nice when one can write backup tapes but the tapes cannot
> be read. I don't know if memory management or the st driver is the
> culprit, but this is a not so nice situation.
>
> I can't even say if the tapes are written correctly as I can't read them
> (one does not reboot production machines back to 2.4.x just to try to
> read a backup tape - I don't have 2.6.x older than 2.6.20 on these
> machines).
Could you try this patch
http://marc.info/?l=linux-scsi&m=116464965414878&w=2
I thought st was modified to not send offsets in the last elements but
it looks like it wasn't.
next prev parent reply other threads:[~2007-03-19 17:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 0:34 2.6.20.3: kernel BUG at mm/slab.c:597 try#2 Andreas Steinmetz
2007-03-19 6:00 ` Andrew Morton
2007-03-19 8:00 ` Pekka Enberg
2007-03-19 8:32 ` Pekka Enberg
2007-03-19 8:35 ` Pekka Enberg
2007-03-19 17:49 ` Mike Christie [this message]
2007-03-19 18:29 ` James Bottomley
2007-03-19 19:06 ` Mike Christie
2007-03-19 21:12 ` Mike Christie
2007-03-19 23:25 ` Andreas Steinmetz
2007-03-19 23:40 ` Andrew Morton
2007-03-19 23:46 ` Andreas Steinmetz
2007-03-19 23:25 ` Andreas Steinmetz
2007-03-19 21:47 ` Gene Heskett
2007-03-19 22:06 ` James Bottomley
2007-03-19 23:29 ` Gene Heskett
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=45FECD45.20705@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=akpm@linux-foundation.org \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.