From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Olaf Hering <olh@suse.de>
Cc: Andreas Koch <koch@esa.informatik.tu-darmstadt.de>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Greg KH <greg@kroah.com>
Subject: Re: 2.6.13: Crash in Yenta initialization
Date: Tue, 13 Sep 2005 00:07:33 +0400 [thread overview]
Message-ID: <20050913000733.A14261@jurassic.park.msu.ru> (raw)
In-Reply-To: <20050912174209.GA3965@suse.de>; from olh@suse.de on Mon, Sep 12, 2005 at 07:42:09PM +0200
On Mon, Sep 12, 2005 at 07:42:09PM +0200, Olaf Hering wrote:
> Did you find the reason for this already?
Unfortunately, no.
> We have a similar report:
> https://bugzilla.novell.com/show_bug.cgi?id=113778
> ...
> It dies in yenta_config_init because dev->subordinate is NULL.
> ...
Yes, this looks identical to Andreas' report.
Perhaps adding the line
#define DEBUG 1
at the very top of drivers/pci/probe.c could help to catch something
interesting in dmesg.
Ivan.
next prev parent reply other threads:[~2005-09-12 20:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 23:38 Andreas Koch
2005-09-03 0:37 ` Andrew Morton
2005-09-03 0:45 ` Andreas Koch
2005-09-03 18:34 ` Ivan Kokshaysky
2005-09-12 17:42 ` Olaf Hering
2005-09-12 20:07 ` Ivan Kokshaysky [this message]
2005-09-13 6:30 ` Olaf Hering
2005-09-13 11:45 ` Ivan Kokshaysky
2005-09-14 4:10 ` Olaf Hering
2005-09-20 10:02 ` Continuing PCI and Yenta troubles in 2.6.13.1 and 2.6.14-rc1 Andreas Koch
2005-09-20 12:59 ` Ivan Kokshaysky
[not found] ` <200509202006.19193.koch@esa.informatik.tu-darmstadt.de>
2005-09-21 15:55 ` Ivan Kokshaysky
2005-09-13 12:36 ` 2.6.13: Crash in Yenta initialization Andreas Koch
2005-09-13 12:43 ` Andreas Koch
2005-09-12 20:13 Marcus Wegner
2005-09-12 20:17 Marcus Wegner
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=20050913000733.A14261@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=koch@esa.informatik.tu-darmstadt.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
/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®