From: Olaf Hering <olh@suse.de>
To: Stefan Kaltenbrunner <mm-mailinglist@madness.at>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>, linux-kernel@vger.kernel.org
Subject: Re: qla2xxx related oops in 2.6.16-rc1
Date: Tue, 31 Jan 2006 22:30:09 +0100 [thread overview]
Message-ID: <20060131213009.GA27795@suse.de> (raw)
In-Reply-To: <43DFD542.7090508@madness.at>
On Tue, Jan 31, Stefan Kaltenbrunner wrote:
> After applying Andrews patches I have so far failed to reproduce the
> issue again - but I'm not really convinced that it is really gone now
> since I could not trigger it very reliably before too ...
I hit that several times, and will track it down once my memcorruption
bug is sorted out.
--
short story of a lazy sysadmin:
alias appserv=wotan
prev parent reply other threads:[~2006-01-31 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 17:27 qla2xxx related oops in 2.6.16-rc1 Stefan Kaltenbrunner
2006-01-30 15:34 ` Andrew Vasquez
2006-01-30 20:24 ` Olaf Hering
2006-01-31 10:07 ` Olaf Hering
2006-01-31 21:23 ` Stefan Kaltenbrunner
2006-01-31 21:30 ` Olaf Hering [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=20060131213009.GA27795@suse.de \
--to=olh@suse.de \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-mailinglist@madness.at \
/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