From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
David Miller <davem@davemloft.net>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: sky2: early oops in pci_vpd_truncate
Date: Mon, 6 Apr 2009 11:29:17 -0700 [thread overview]
Message-ID: <20090406112917.54c864ee@hobbes> (raw)
In-Reply-To: <1238815934.3893.4.camel@brick>
On Fri, 03 Apr 2009 20:32:14 -0700
Harvey Harrison <harvey.harrison@gmail.com> wrote:
> On Fri, 2009-04-03 at 18:03 -0700, Jesse Barnes wrote:
> > On Fri, 03 Apr 2009 17:10:19 -0700
> > Harvey Harrison <harvey.harrison@gmail.com> wrote:
> >
> > > 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?
> >
> > Yeah there's a patch for that in my queue (not pushed to Linus yet
> > though), subject "[PATCH] PCI: Fix oops in pci_vpd_truncate" from
> > Anton Vorontsov.
> >
>
> What tree is that?
git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6.git.
It'll be in my for-linus branch as soon as I push it out later today.
I'll probably ask Linus to pick it up later this week.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-04-06 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 0:10 sky2: early oops in pci_vpd_truncate Harvey Harrison
2009-04-04 1:03 ` Jesse Barnes
2009-04-04 3:32 ` Harvey Harrison
2009-04-06 18:29 ` Jesse Barnes [this message]
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=20090406112917.54c864ee@hobbes \
--to=jbarnes@virtuousgeek.org \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--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