From: Harvey Harrison <harvey.harrison@gmail.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-netdev <netdev@vger.kernel.org>
Subject: sky2: early oops in pci_vpd_truncate
Date: Fri, 03 Apr 2009 17:10:19 -0700 [thread overview]
Message-ID: <1238803819.3893.3.camel@brick> (raw)
Hi Stephen,
I'm seeing an early oops in current Linus -git right after sky2_probe
unfortunately it scrolls away too fast to get it all, but after a
delayed-printk boot it appears to be a NULL dereference in
pci_vpd_truncate. sysfs also features prominantly in the backtrace..
is this a known issue?
I see there were some sky2 patches this cycle using the vpd functions,
any pointers/patches to try out?
Harvey
next reply other threads:[~2009-04-04 0:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 0:10 Harvey Harrison [this message]
2009-04-04 1:03 ` sky2: early oops in pci_vpd_truncate Jesse Barnes
2009-04-04 3:32 ` Harvey Harrison
2009-04-06 18:29 ` Jesse Barnes
2009-04-06 21:42 ` Harvey Harrison
2009-04-08 12:00 ` Ingo Molnar
2009-04-08 16:47 ` Jesse Barnes
2009-04-08 20:15 ` Harvey Harrison
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=1238803819.3893.3.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=davem@davemloft.net \
--cc=jbarnes@virtuousgeek.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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