linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Frank Prepelica <Frank.Prepelica@ubidyne.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Kernel fault with simple UIO interrupt driver in 2.6.30.4
Date: Tue, 04 Aug 2009 12:31:25 +1000	[thread overview]
Message-ID: <1249353085.5517.29.camel@concordia> (raw)
In-Reply-To: <29DC34A6B43468409F5A371CFE34E849DFC9A1@ex01.ads.ubidyne.de>

[-- Attachment #1: Type: text/plain, Size: 444 bytes --]

On Mon, 2009-08-03 at 15:07 +0200, Frank Prepelica wrote:
> Hi all,
> 
> due to a new revision of our custimized board, i need to port our current kernel (2.6.24)
> to the latest kernel version 2.6.30.4.
> 
> Among other things the UIO interrupt driver makes some trouble. The driver runs
> smoothly on 2.6.24 but I'll get kernel faults when running in 2.6.30.4.

You seem to have forgotten to post the log of the oops :)

cheers


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-08-04  2:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 13:07 Kernel fault with simple UIO interrupt driver in 2.6.30.4 Frank Prepelica
2009-08-04  2:31 ` Michael Ellerman [this message]

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=1249353085.5517.29.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=Frank.Prepelica@ubidyne.com \
    --cc=linuxppc-dev@ozlabs.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).