mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Donepudi, Suneeta" <sdonepudi@3eti.com>
To: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Cc: "'Matt D. Robinson'" <yakker@aparity.com>
Subject: RE: Kernel Panic during memcpy_toio to PCI card
Date: Fri, 1 Nov 2002 15:34:45 -0500	[thread overview]
Message-ID: <EF5625F9F795C94BA28B150706A215480DF84D@MAIL> (raw)


Matt,

Thanks for the response, I am using a 2.4.18 kernel with
a busybox. This is an embedded system with the file system
laid out by an 'initrd.gz'. I am new to Linux. Can LKCD
still be used in our case ?


Suneeta

-----Original Message-----
From: Matt D. Robinson [mailto:yakker@aparity.com]
Sent: Friday, November 01, 2002 3:26 PM
To: Donepudi, Suneeta; Matt D. Robinson
Subject: Re: Kernel Panic during memcpy_toio to PCI card


Hey, Suneeta.  Can you try LKCD and see if you can get
a crash dump with it?  Also, is this 2.4 or 2.5?

--Matt

On Fri, 1 Nov 2002, Donepudi, Suneeta wrote:
|>Hi,
|>
|>I would like help in diagnosing a kernel panic while accessing a PCI
device.
|>
|>Everything runs fine for sometime and in about 1/2 hour I get a Kernel
Panic
|>message saying :
|>
|>"Unable to handle kernel paging request at virtual address 0xc2821000"
|>
|>Analysis with Ksymoops shows that it is happening during a memcpy_toio()
|>with the PCI card. The PCI card uses three Base Address Registers with
|>virtual addresses mapped as follows (after ioremap has been issued):
|>
|>BAR0 = 0xc280f000
|>BAR1 = 0xc2811000
|>BAR2 = 0xc2822000
|>
|>It seems like the kernel panic is complaining about an address which is a
|>combination of BAR1 (lower bytes) and BAR2 (upper bytes). It should really
|>be accessing the BAR1 address at the point the crash occurred.
|>
|>I put the following if-statement just before the memcpy_toio():
|>-----------------------------------------------------------
|>if (((long int)pci_bar1) == 0xc2821000)
|>{
|>	printk (KERN_ERR "Illegal address for BAR1\n");
|>	return -1;
|>}
|>memcpy_toio (pci_bar1, in_ptr, len);
|>------------------------------------------------------------
|>
|>It still caused the crash in the same manner and at the same location.
|>Could someone help me with pointers to where I should start looking ?
|>Disabling interrupts around the memcpy_toio() did not make any
|>difference. Is this a hardware problem with the PCI card ? We are using
|>a Xilinx core with out FPGA build into it.
|>Is there a book I could read to learn more about debugging this in the 
|>Kernel ?
|>
|>Thanks a bunch,
|>Suneeta

             reply	other threads:[~2002-11-01 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01 20:34 Donepudi, Suneeta [this message]
2002-11-01 23:28 ` Matt D. Robinson
2002-11-01 23:29   ` Dave Jones
2002-11-02  1:15     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-11-02 19:46 Donepudi, Suneeta
2002-11-01 20:06 Donepudi, Suneeta

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=EF5625F9F795C94BA28B150706A215480DF84D@MAIL \
    --to=sdonepudi@3eti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yakker@aparity.com \
    /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®