public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Kobus Wolvaardt <kobus@kreon.co.za>
To: linux-mtd@lists.infradead.org
Subject: doc 2.6 kernel crashes
Date: Wed, 5 Jul 2006 14:03:21 +0200	[thread overview]
Message-ID: <200607051403.21643.kobus@kreon.co.za> (raw)

Hi,

I am getting random crashes on my 2.6.11 and 2.6.15 kernel when diskonchip 
2000 support is enabled, without it there is no crashes. How do I verify what 
causes the crashes? any ideas? and pointers to docs that'll help?

I'm a bit at a loss as to what to do. I have a crappy driver that isnt 
supported beyond 2.6.15 kernel that's preventing me from trying the latest 
and greatest 2.6.17. Can it be that by enabling unstable code in the kernel 
setup that some other unstable driver is included and that it is not the doc 
driver's fault? Or if it is the doc drivers fault how do I help to find and 
fix the bug?

Thanks,
Kobus




















 

-- 
This message was scanned for viruses by MailScanner and Sophos.

                 reply	other threads:[~2006-07-05 13:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200607051403.21643.kobus@kreon.co.za \
    --to=kobus@kreon.co.za \
    --cc=linux-mtd@lists.infradead.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