From: Randy Dunlap <rdunlap@xenotime.net>
To: "samson yeung" <fragmede@onepatchdown.net>
Cc: linux-kernel@vger.kernel.org, rdunlap@xenotime.net,
alan@lxorguk.ukuu.org.uk, AndrewL733@aol.com,
bbermack@alum.mit.edu, "Justin Mazzola Paluska" <jmp@mit.edu>
Subject: Re: [Re: NMI error and Intel S5000PSL Motherboards]
Date: Wed, 26 Sep 2007 13:52:29 -0700 [thread overview]
Message-ID: <20070926135229.67edd4eb.rdunlap@xenotime.net> (raw)
In-Reply-To: <c038f5910709261207k740ad130k151a9b0c8d8e48e0@mail.gmail.com>
On Wed, 26 Sep 2007 15:07:14 -0400 samson yeung wrote:
> Hello,
>
> I'm working with AndrewL733 on this issue. I'm doing the git bisect right now.
>
> scanpci -f -1 causes the problem, scanpci -f -2 and scanpci -O do not.
Does the problem always happen when scanpci is making an ioperm
syscall (as in the strace output below)?
> The driver does not even need to be loaded to have the problem
> (e1000). I have not tried the 2.6.18 driver with 2.6.20, but I have
> tried both the in-kernel driver as well as the newer driver from Intel
> with the same result.
>
> The drive is a Seagate Barracuda 7200.9 80 Gbytes with fimware 3.AAE
> I can include hdparm -i output if it will help.
>
> The problem is only happening on 64-bit. As noted above, I'm running
> git-bisect to test a stock kernel.org kernel. 32-bit Ubuntu does not
> exhibit the problem, I have not tested a kernel.org 32-bit kernel.
>
-----------------------------------------------------------------------------------------
> strace: I don't know what syscall_273 does. I trimmed the output to
> include syscall 273 and the lines surrounding it. I can include the
> entirety of the strace if it will help.
Does this include trace info all the way to the end of the trace
output file? If not, please send that part also.
> arch_prctl(ARCH_SET_FS, 0x2aca24060f50) = 0
> mprotect(0x2aca23e3b000, 12288, PROT_READ) = 0
> munmap(0x2aca238e2000, 36649) = 0
> set_tid_address(0x2aca24060fe0) = 10319
> syscall_273(0x2aca24060ff0, 0x18, 0x7fff87790188, 0x2aca233193c0,
> 0x2aca24060f50, 0x2aca233352b8, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1,
> 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1, 0x1,
> 0x1, 0x1, 0x1, 0x1, 0x1) = 0
> rt_sigaction(SIGRTMIN, {0x2aca23e4a3a0, [], SA_RESTORER|SA_SIGINFO,
> 0x2aca23e53200}, NULL, 8) = 0
> rt_sigaction(SIGRT_1, {0x2aca23e4a2f0, [],
> SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x2aca23e53200}, NULL, 8) = 0
> rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
> ioperm(0, 0x400, 0x1) = 0
---
~Randy
Phaedrus says that Quality is about caring.
next prev parent reply other threads:[~2007-09-26 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 19:07 samson yeung
2007-09-26 20:52 ` Randy Dunlap [this message]
2007-09-26 10:12 ` NMI error and Intel S5000PSL Motherboards AndrewL733
2007-09-26 2:59 ` Randy Dunlap
2007-09-26 23:48 ` Jim Paris
2007-09-27 0:03 ` Randy Dunlap
2007-09-28 15:11 ` AndrewL733
2007-09-28 15:13 ` AndrewL733
2007-10-01 4:09 ` Repost: " AndrewL733
2007-09-26 4:58 ` Randy Dunlap
2007-09-26 11:16 ` Alan Cox
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=20070926135229.67edd4eb.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=AndrewL733@aol.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bbermack@alum.mit.edu \
--cc=fragmede@onepatchdown.net \
--cc=jmp@mit.edu \
--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 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®