mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Harish K Harshan <harish@amritapuri.amrita.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i830 lockup
Date: Fri, 22 Apr 2005 08:47:55 -0700	[thread overview]
Message-ID: <20050422154755.GA2892@taniwha.stupidest.org> (raw)
In-Reply-To: <47196.203.197.150.195.1114171742.squirrel@mail.amrita.ac.in>

On Fri, Apr 22, 2005 at 05:39:02PM +0530, Harish K Harshan wrote:

> But the system works pretty fine when other applications are
> running.

so either the driver is poking something that is causing problems or
maybe the card when operating makes the system unstabel

> Oncei load the driver, the system gets messed up. Could it be the
> problem with the way I handle DMA and interrupts??

maybe, but i would wouldn't think so

> I mean, is it possible to mess up everything by wrong programming???

yes

> This driver works prefectly on the other IPCs we have, but not on
> the two-piece board (Chino-Laxons) systems we have.

if these are embedded system they might have some weird wiring or
similar (embedded PCs used to have lots of strangeness to them, i
assume that hasn't changed)

> The DMA channels are both free before loading the drivers all the
> time, and one it is loaded, the /proc/dma file shows the DMA has
> been hooked properly. Could it still be the problem with the
> CPU/Cache/Chipset as you said?

i would ask the mainboard maker and also make sure you have the most
recent bios

also make sure your driver isn't stomping on bad memory in the slight
chance it whacking chipset registers I guess

      reply	other threads:[~2005-04-22 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20  7:06 Harish K Harshan
2005-04-20  6:57 ` Chris Wedgwood
2005-04-22 12:09   ` Harish K Harshan
2005-04-22 15:47     ` Chris Wedgwood [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=20050422154755.GA2892@taniwha.stupidest.org \
    --to=cw@f00f.org \
    --cc=harish@amritapuri.amrita.edu \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®