From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Konrad Wojas <wojas@vvtp.tudelft.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 oops in poll()?
Date: Wed, 05 Jan 2005 11:11:18 -0800 [thread overview]
Message-ID: <41DC3BD6.3020303@osdl.org> (raw)
In-Reply-To: <20050105185733.GJ31250@vvtp.tudelft.nl>
Konrad Wojas wrote:
> On Wed, Jan 05, 2005 at 10:24:09AM -0800, Randy.Dunlap wrote:
>
>>This probably needed to use /proc/kallsyms from the dying kernel,
>>which you most likely don't have....
>>
>>I'm having trouble seeing what sock_poll() called (i.e., where EIP
>>register points to). In the /boot/System.map-2.6.9-1-686 file,
>>is anything near address 0xc02b5513 listed?
>>(or just send me that file privately)
>
>
> Also doesn't look very helpfull to me..
True. Have you tested this problem on 2.6.10 yet?
Back to 2.6.9: do you normally run 2.6.9 with all of those same
modules loaded? If so, please send me the /proc/modules
and /proc/kallsyms files.
Anyone know what all of those __func__'s are?
> c02a592a r __func__.1
> c02a593b r __func__.0
> c02a594c r __func__.8
> c02a5960 r llc_oui
> c02a59a8 r __func__.4
> c02c6bc8 d __pci_fixup_PCI_VENDOR_ID_S3PCI_DEVICE_ID_S3_868quirk_s3_64M
> c02c6bc8 D __start_pci_fixups_header
> c02c6bd0 d __pci_fixup_PCI_VENDOR_ID_S3PCI_DEVICE_ID_S3_968quirk_s3_64M
> c02c6bd8 d __pci_fixup_PCI_VENDOR_ID_ALPCI_DEVICE_ID_AL_M7101quirk_ali7101_acpi
> c02c6be0 d __pci_fixup_PCI_VENDOR_ID_INTELPCI_DEVICE_ID_INTEL_82371AB_3quirk_piix4_acpi
--
~Randy
next prev parent reply other threads:[~2005-01-05 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 16:15 2.6.9 oops in poll()? Konrad Wojas
2005-01-04 22:45 ` Randy.Dunlap
2005-01-05 4:08 ` Konrad Wojas
2005-01-05 18:24 ` Randy.Dunlap
2005-01-05 18:57 ` Konrad Wojas
2005-01-05 19:11 ` Randy.Dunlap [this message]
2005-01-05 21:11 ` Konrad Wojas
2005-01-06 4:52 ` Randy.Dunlap
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=41DC3BD6.3020303@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wojas@vvtp.tudelft.nl \
/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