All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 10142] DMA crash with via82cxxx module
Date: Fri,  7 Mar 2008 11:49:50 -0800 (PST)	[thread overview]
Message-ID: <20080307194950.796EC11D108@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-10142-11633@http.bugzilla.kernel.org/>

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





------- Comment #10 from qrees@poczta.fm  2008-03-07 11:49 -------
Ok, I've tested kernel version 2.6.24.8 and it didn't creash, but it's doesn't
mean that it won't crash later. I'll test it for a week or so and see if it
works fine. The problem with testing is that system may crash after few minutes
or after few weeks. Even if finding kernel with git bisect might take only few
iterations, one iteration may take very long time... I haven't found any
software that always makes system crash...

And about "drive not ready for command" error. This is related to Benq DVD
drive, and is discribed here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182996. I've disconnected
Benq drive and system did boot.


-- 
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-03-07 19:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02 12:58 [Bug 10142] New: DMA crash with via82cxxx module bugme-daemon
2008-03-02 13:37 ` [Bug 10142] " bugme-daemon
2008-03-02 13:52 ` bugme-daemon
2008-03-02 14:30 ` bugme-daemon
2008-03-02 14:31 ` bugme-daemon
2008-03-02 15:24 ` bugme-daemon
2008-03-02 15:27 ` bugme-daemon
2008-03-02 16:15 ` bugme-daemon
2008-03-03  7:55 ` bugme-daemon
2008-03-03 22:33 ` bugme-daemon
2008-03-07 19:49 ` bugme-daemon [this message]
2008-03-07 20:09 ` bugme-daemon
2008-03-15 10:11 ` bugme-daemon
2008-06-18 22:57 ` bugme-daemon
2008-09-24 13:20 ` bugme-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=20080307194950.796EC11D108@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-ide@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.