From: Peter Nixon <listuser@peternixon.net>
To: sander@humilis.net
Cc: reiserfs-list@namesys.com
Subject: Re: corrupted disk
Date: Tue, 11 Oct 2005 17:07:32 +0300 [thread overview]
Message-ID: <200510111707.32746.listuser@peternixon.net> (raw)
In-Reply-To: <20051011135522.GB2763@favonius>
On Tuesday 11 October 2005 16:55, Sander wrote:
> Peter Nixon wrote (ao):
> > On Tuesday 11 October 2005 16:31, Sander wrote:
> > > Peter Nixon wrote (ao):
> > > > At 06:15 this morning the following errors showed up in
> > > > /var/log/messages
> > > >
> > > > Oct 11 06:15:03 DB2MUHASEBE kernel: kernel BUG at prints.c:334!
> > > > Oct 11 06:15:03 DB2MUHASEBE kernel: invalid operand: 0000
> > > > 2.4.21-138-smp #1 SMP Fri Oct 31 00:51:31 UTC 2003
> > > >
> > > > Oct 11 06:15:03 DB2MUHASEBE kernel: EIP: 0010:[<c5096ec8>]
> > > > Tainted: P
> > >
> > > Your kernel is very, very old and tainted.
> >
> > Yes. I am aware of that. As I mentioned the server is an IBM server
> > running SUSE Linux Enterprise 8 and DB2. At the time of deployment of the
> > server SLES 9 was not yet certified to run with DB2.
>
> What I'm trying to say is that you are very unlikely to receive support
> on such an old kernel. And most likely the bug is fixed in a younger
> kernel.
>
> And, you are also running a tainted kernel. You are less likely to
> receive support on a tainted kernel.
Yes I understand the issue, however without running an official SLES kernel
the customer cannot receive support on DB2 or on their IBM hardware. If there
is a bug in the kernel that causes this then I need to get SUSE to roll a new
kernel and get it certified by IBM. If it is a bug in the SCSI driver (the
module that taints the kernel) then I need to report it to IBM and get them
to supply a fixed module.
--
Peter Nixon
http://www.peternixon.net/
PGP Key: http://www.peternixon.net/public.asc
next prev parent reply other threads:[~2005-10-11 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 13:02 corrupted disk Peter Nixon
2005-10-11 13:08 ` Peter Nixon
2005-10-11 13:31 ` Sander
2005-10-11 13:34 ` Peter Nixon
2005-10-11 13:55 ` Sander
2005-10-11 14:07 ` Peter Nixon [this message]
2005-10-11 14:10 ` Vladimir V. Saveliev
2005-10-11 14:22 ` Sander
2005-10-11 13:53 ` Vladimir V. Saveliev
[not found] ` <200510111717.02119.listuser@peternixon.net>
2005-10-11 15:05 ` Vladimir V. Saveliev
2005-10-11 15:33 ` Peter Nixon
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=200510111707.32746.listuser@peternixon.net \
--to=listuser@peternixon.net \
--cc=reiserfs-list@namesys.com \
--cc=sander@humilis.net \
/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.