All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: biswa.nayak@wipro.com
Cc: Linux-Kernel@vger.kernel.org
Subject: Re: PCI ERROR: Segmentation fault in pci_do_scan_bus
Date: Tue, 25 Apr 2006 23:13:28 -0700	[thread overview]
Message-ID: <20060426061328.GA2279@kroah.com> (raw)
In-Reply-To: <4F36B0A4CDAD6F46A61B2B32C33DC69C02502ABC@BLR-EC-MBX03.wipro.com>

On Tue, Apr 25, 2006 at 05:25:32PM +0530, biswa.nayak@wipro.com wrote:
> Hi 
> 
> I am getting segmentation fault, consistently on call to
> 'pci_do_scan_bus'. This is a small test code ( attached with this mail)
> to test the APIs exposed by the PCI subsystem.

The module code you attached isn't exactly "small" :)

What chunk of code is causing the problem?

Why are you scanning the PCI bus from a module?

>I just checked where it
> faults and found out that inside 'sysfs_create_bin_file' it is not able
> to find the kobject out of the dev pointer passed to it. Now extracting
> of the dev object out of the bus pointer is done by
> 'list_for_each_entry(dev, &bus->devices, bus_list)' in
> 'pci_bus_add_devices'. Now I am not able to understand why the kobject
> is missing. Is it something that I am missing or is it a kernel defect?
> Any help in this will be really appreciated. The bug message is pasted
> below.

I'm confused as to why you are trying to set up the pci bus for a pci
bus that is already set up.  That's why the function is dying...

thanks,

greg k-h

  reply	other threads:[~2006-04-26  6:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 11:55 PCI ERROR: Segmentation fault in pci_do_scan_bus biswa.nayak
2006-04-26  6:13 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-26 11:35 biswa.nayak
2006-04-26 17:21 ` Greg KH

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=20060426061328.GA2279@kroah.com \
    --to=greg@kroah.com \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=biswa.nayak@wipro.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 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.