From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12686] kernel oops __ticket_spin_lock
Date: Wed, 11 Feb 2009 02:55:11 -0800 (PST) [thread overview]
Message-ID: <20090211105511.65563108040@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12686-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12686
------- Comment #1 from dmaciejak@fortinet.com 2009-02-11 02:55 -------
Created an attachment (id=20189)
--> (http://bugzilla.kernel.org/attachment.cgi?id=20189&action=view)
kern.log extract
--
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:[~2009-02-11 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 10:54 [Bug 12686] New: kernel oops __ticket_spin_lock bugme-daemon
2009-02-11 10:55 ` bugme-daemon [this message]
2009-02-11 10:55 ` [Bug 12686] " bugme-daemon
2009-05-19 19:08 ` 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=20090211105511.65563108040@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).