All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-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: Thu, 28 Jan 2010 23:35:59 GMT	[thread overview]
Message-ID: <201001282335.o0SNZxKL009122@demeter.kernel.org> (raw)
In-Reply-To: <bug-11646-11613@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=11646





--- Comment #29 from Csillag Tamas <cstamas@digitus.itk.ppke.hu>  2010-01-28 23:35:43 ---
I upgraded to this kernel @ 2010-01-18:
Linux somehost 2.6.24-9-pve #1 SMP PREEMPT Tue Nov 17 09:34:41 CET 2009 x86_64 
GNU/Linux

and I experienced this issue again.

In some forum I get the idea to upgrade the cards firmware (ISP2422):

$ md5sum qlgc_flash_image_multiboot143.img
1f43310c7bb24db53d561b60080b5211  qlgc_flash_image_multiboot143.img

I do not have a problem since I did the upgrade (2010-01-20).

YMMV

--
Regards, 
  cstamas

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-01-28 23:35 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
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 [this message]
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=201001282335.o0SNZxKL009122@demeter.kernel.org \
    --to=bugzilla-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.