From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 36702] 2.6.39 kernel panic w/screenshots & kernel cfg link provided
Date: Mon, 27 Jun 2011 15:06:26 GMT [thread overview]
Message-ID: <201106271506.p5RF6QqB027329@demeter2.kernel.org> (raw)
In-Reply-To: <bug-36702-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=36702
--- Comment #2 from Justin Piszcz <jpiszcz@lucidpixels.com> 2011-06-27 15:06:21 ---
Hi,
Right after I wrote this, a few hours later it crashed again for the first time
in week and since it hadn't crashed in a while, I had X started so I don't have
a crash dump, will leave X off (on console, to capture the next crash) until it
crashes again.
Justin.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-06-27 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 13:11 [Bug 36702] New: 2.6.39 kernel panic w/screenshots & kernel cfg link provided bugzilla-daemon
2011-06-05 13:11 ` [Bug 36702] " bugzilla-daemon
2011-06-26 23:01 ` bugzilla-daemon
2011-06-27 15:06 ` bugzilla-daemon [this message]
2011-07-02 1:51 ` bugzilla-daemon
2011-07-02 1:52 ` bugzilla-daemon
2011-07-02 12:42 ` bugzilla-daemon
2011-07-02 12:42 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2011-06-12 21:06 3.0-rc2: Reported regressions 2.6.38 -> 2.6.39 Rafael J. Wysocki
2011-06-12 21:12 ` [Bug #36702] 2.6.39 kernel panic w/screenshots & kernel cfg link provided Rafael J. Wysocki
2011-06-26 22:26 3.0-rc4: Reported regressions 2.6.38 -> 2.6.39 Rafael J. Wysocki
2011-06-26 22:35 ` [Bug #36702] 2.6.39 kernel panic w/screenshots & kernel cfg link provided Rafael J. Wysocki
2011-06-26 22:35 ` Rafael J. Wysocki
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=201106271506.p5RF6QqB027329@demeter2.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.