All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: John Riggs <jriggs@altiris.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.7 Linux Kernel Crash While Detecting PCI Devices
Date: Wed, 11 Aug 2004 14:22:24 -0700	[thread overview]
Message-ID: <20040811212224.GG21894@kroah.com> (raw)
In-Reply-To: <9B96255DE3B181429D06C6ADB0B37470232B12@sandman.altiris.com>

On Tue, Aug 10, 2004 at 12:14:09PM -0600, John Riggs wrote:
> The problem appears to be coming from the following series of calls:
> 
> returns EEXIST
> create_dir
> sysfs_create_dir
> create_dir
> kobject_add
> class_device_add
> class_device_register  
> pci_alloc_child_bus
> 
> This causes pci_bus* child->class_dev.kobj.dentry to be NULL, which is
> passed into class_device_create_file eventually becoming a NULL POINTER
> in the function sysfs_add_file. (The NULL variable in sysfs_add_file is
> now called dir.)
> 
> I don't have much of an understanding of the kernel, but it appears to
> me that a PCI device is getting created twice. Does anybody have any
> pointers as to what might be going on, or can point me in the right
> direction to look?

Yes, that sounds like what is happening.  Can you build a modular kernel
and load the drivers you need one by one until the error happens?

thanks,

greg k-h

  reply	other threads:[~2004-08-11 21:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 18:14 PROBLEM: 2.6.7 Linux Kernel Crash While Detecting PCI Devices John Riggs
2004-08-11 21:22 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-13 16:57 John Riggs
2004-08-12 17:47 John Riggs
2004-08-12 22:31 ` Greg KH
2004-08-06 18:22 John Riggs
2004-08-17 20:22 ` Jonathan Sambrook

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=20040811212224.GG21894@kroah.com \
    --to=greg@kroah.com \
    --cc=jriggs@altiris.com \
    --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 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.