From: Matthias Andree <matthias.andree@gmx.de>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.19 reproducable oops through Tivoli BA client 3.7.2.0
Date: Fri, 10 Aug 2001 15:09:01 +0200 [thread overview]
Message-ID: <20010810150901.A30330@krusty.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <20010810143637.B31349@emma1.>
In-Reply-To: <20010810143637.B31349@emma1.>; from matthias.andree@stud.uni-dortmund.de on Fri, Aug 10, 2001 at 14:36:37 +0200
On Fri, 10 Aug 2001, Matthias Andree wrote:
> This morning, one of our machines Oopsed while running dsmc (Tivoli
> storage manager Backup-Archive client 3.7.2.0), dsmc itself caught
> SIGSEGV:
>
> 08/10/2001 03:15:54 B/A Performance thread, fatal error, signal 11
>
> This is somewhat peculiar since it should not be possible for a
> user-space process to shoot a kernel process, and it's even more
> peculiar because it breaks our daily backup.
>
> Assistance is sought.
I tried stracing that beast (strace V4.2), but I failed, I only trace the
"Performance" thread which displays the dsmc progress. Is there any way
to trace one of the remaining two threads so I can figure which file or
directory the dsmc dies on?
prev parent reply other threads:[~2001-08-10 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 12:36 Matthias Andree
2001-08-10 13:09 ` Matthias Andree [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=20010810150901.A30330@krusty.dt.e-technik.uni-dortmund.de \
--to=matthias.andree@gmx.de \
--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®