All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 11045] Bug in MPT Fusion 2.6.26-rc7 unbootable
Date: Wed,  9 Jul 2008 01:40:02 -0700 (PDT)	[thread overview]
Message-ID: <20080709084002.4D9F511D109@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-11045-11613@http.bugzilla.kernel.org/>

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





------- Comment #13 from kurk@shiftmail.org  2008-07-09 01:40 -------
>Hi,
>Can you please attach the complete log that you collected with a
>serial console to this bug report:
>  http://bugzilla.kernel.org/show_bug.cgi?id=11045
>
>The excerpts are missing important information about how the MPT
>interrupt is routed when the driver claims the device.  It's
>easier if we can just look at the complete log; sometimes it
>answers questions we didn't think of the first time around.
>
>Thanks,
>  Bjorn

Hi Bjorn,
what I pasted in, it is absolutely the complete log obtained with the serial
cable. I did not modify it in any way or cut away parts. As I wrote, I obtained
it twice, once stopping the boot after 8 minutes, the other stopping after 5
(and stack traces are slightly different in the two boots as you can see). The
error messages loop as you can see and never end so it is necessary to stop
that after a while. The other attachments like dmesg (2.6.25), lspci (2.6.25),
.config yes, I grepped or cut them, but not the serial dump.

(Is it ok if I reply from the web interface or should I do via email? Sorry
it's the first time I use bugzilla.kernel.org)


-- 
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.

  parent reply	other threads:[~2008-07-09  8:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11045-11613@http.bugzilla.kernel.org/>
2008-07-06 18:58 ` [Bug 11045] Bug in MPT Fusion 2.6.26-rc7 unbootable bugme-daemon
2008-07-06 19:34 ` bugme-daemon
2008-07-06 20:28 ` bugme-daemon
2008-07-06 20:50 ` bugme-daemon
2008-07-07  9:36 ` bugme-daemon
2008-07-08  9:03 ` bugme-daemon
2008-07-08 14:09 ` bugme-daemon
2008-07-08 16:52 ` bugme-daemon
2008-07-08 17:24 ` bugme-daemon
2008-07-08 20:57 ` bugme-daemon
2008-07-08 21:53 ` bugme-daemon
2008-07-08 21:57 ` bugme-daemon
2008-07-09  8:19 ` bugme-daemon
2008-07-09  8:40 ` bugme-daemon [this message]
2008-07-10 13:57 ` bugme-daemon
2008-07-10 14:25 ` bugme-daemon
2008-07-10 14:25 ` bugme-daemon
2008-07-10 16:02 ` bugme-daemon
2008-07-10 23:50 ` bugme-daemon
2008-07-11  0:42 ` bugme-daemon
2008-07-11  4:35 ` bugme-daemon
2008-07-11 14:06 ` bugme-daemon
2008-07-16 20:40 ` bugme-daemon
2008-07-13 17:59 2.6.26-rc9-git12: Reported regressions from 2.6.25 Rafael J. Wysocki
2008-07-13 18:00 ` [Bug #11045] Bug in MPT Fusion 2.6.26-rc7 unbootable Rafael J. Wysocki
2008-07-13 18:00   ` Rafael J. Wysocki
2008-07-13 23:54   ` Oliver Pinter
2008-07-13 23:54     ` Oliver Pinter
     [not found]     ` <6101e8c40807131654q24e9f3ffo3f4cec179c355c89-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-13 23:59       ` Oliver Pinter
2008-07-13 23:59         ` Oliver Pinter

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=20080709084002.4D9F511D109@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.