From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 11646] QLA2xxx: Kernel deadlock on high load somewhere after 2.6.20
Date: Tue, 7 Oct 2008 13:52:29 -0700 (PDT) [thread overview]
Message-ID: <20081007205229.932AC108047@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-11646-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=11646
------- Comment #12 from grin@grin.hu 2008-10-07 13:52 -------
Okay, but _which_ part you mean? One HBA? As I've mentioned the problem
happened on multiple machines, and they have dual HBAs. (Or can one bad HBA
mess up the others? How could be spotted which one is bad? Is there a way to
test this particular problem?)
By the reply I guess they talk about the dumps, and #4 was the second card of
the machine in question. But originally this wasn't the server I had most
problem with, but that one locks usually up alright on newer kernels and reboot
clears the firmware dumps you mentioned. So if machine#3 have bad HBA#2, why
did machine #1 lock up every 30 minutes? Still not clear to me.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-10-07 20:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 13:55 [Bug 11646] New: QLA2xxx: Kernel deadlock on high load somewhere after 2.6.20 bugme-daemon
2008-09-25 14:10 ` [Bug 11646] " bugme-daemon
2008-09-25 15:00 ` bugme-daemon
2008-09-25 15:04 ` bugme-daemon
2008-09-26 13:48 ` bugme-daemon
2008-09-26 13:59 ` bugme-daemon
2008-09-27 8:17 ` bugme-daemon
2008-09-30 7:49 ` bugme-daemon
2008-10-01 22:40 ` bugme-daemon
2008-10-03 0:23 ` bugme-daemon
2008-10-03 14:42 ` bugme-daemon
2008-10-06 19:21 ` bugme-daemon
2008-10-07 20:38 ` bugme-daemon
2008-10-07 20:52 ` bugme-daemon [this message]
2008-10-07 21:27 ` bugme-daemon
2008-10-13 11:45 ` bugme-daemon
2008-10-21 7:13 ` bugme-daemon
2008-11-19 22:10 ` bugme-daemon
2008-11-23 19:21 ` bugme-daemon
2009-02-23 0:54 ` bugme-daemon
2009-02-27 9:50 ` bugme-daemon
2009-02-27 10:28 ` bugme-daemon
2009-02-27 16:17 ` bugme-daemon
2009-02-27 18:29 ` bugme-daemon
2009-03-03 19:00 ` bugme-daemon
2009-03-04 16:14 ` bugme-daemon
2009-03-31 16:02 ` bugzilla-daemon
2009-05-12 9:03 ` bugzilla-daemon
2009-07-19 14:25 ` bugzilla-daemon
2009-07-20 8:26 ` bugzilla-daemon
2010-01-28 23:35 ` bugzilla-daemon
2010-01-29 0:46 ` bugzilla-daemon
2010-01-31 22:06 ` bugzilla-daemon
2010-03-03 9:37 ` bugzilla-daemon
2010-03-03 9:59 ` bugzilla-daemon
2010-03-03 10:45 ` bugzilla-daemon
[not found] <bug-11646-11613@https.bugzilla.kernel.org/>
2010-08-31 6:22 ` bugzilla-daemon
2010-08-31 13:56 ` bugzilla-daemon
2012-05-22 14:34 ` bugzilla-daemon
2012-10-30 15:12 ` bugzilla-daemon
2014-07-29 19:59 ` bugzilla-daemon
2014-07-29 20:22 ` bugzilla-daemon
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=20081007205229.932AC108047@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.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.