From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 29942] New: oops at drivers/gpu/drm/ttm/ttm_bo.c:272
Date: Sat, 26 Feb 2011 14:59:15 GMT [thread overview]
Message-ID: <bug-29942-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=29942
Summary: oops at drivers/gpu/drm/ttm/ttm_bo.c:272
Product: Drivers
Version: 2.5
Kernel Version: 2.6.38-rc6-wl-00360-gcf65005
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: rossi.f@inwind.it
Regression: No
Created an attachment (id=49232)
--> (https://bugzilla.kernel.org/attachment.cgi?id=49232)
snapshot of kernel OOPS
Kernel OOPS, attached a snapshot. Bug not reproducible, the kernel version is
2.6.38-rc6-wl-00360-gcf65005, latest wireless-testing.git
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
--
next reply other threads:[~2011-02-26 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 14:59 bugzilla-daemon [this message]
2011-05-29 8:16 ` [Bug 29942] oops at drivers/gpu/drm/ttm/ttm_bo.c:272 bugzilla-daemon
2011-05-29 8:30 ` 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=bug-29942-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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