From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Any Intel folks on the list? Intel PCI-E bridge ACPI resource question
Date: Thu, 5 Apr 2007 18:13:13 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704051812340.14476@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0704051809160.14476@p34.internal.lan>
On Thu, 5 Apr 2007, Justin Piszcz wrote:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0701.3/0315.html
>
> I have similar issues as this poster-- I was wondering (if anyone) had an
> idea to the root cause of this issue; is it a problem with the chipset, the
> BIOS revision?
>
> Mobo: Intel DG965WHMKR
> BIOS: 1666
>
> Is it only Intel Chipsets that suffer from this problem?
>
> ... or is it a way the kernel handles ACPI/IO-APIC/etc?
>
> Justin.
>
p34:~# /usr/bin/time badblocks -b 512 -s -v -w /dev/sdl
Checking for bad blocks in read-write mode
>From block 0 to 293046768
Testing with pattern 0xaa: done
Reading and comparing: done
Testing with pattern 0x55: done
Reading and comparing: done
Testing with pattern 0xff: done
Reading and comparing: done
Testing with pattern 0x00: done
Reading and comparing: done
Pass completed, 0 bad blocks found.
1929.06user 467.89system 4:36:23elapsed 14%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (1major+257minor)pagefaults 0swaps
p34:~#
Not a single bad block found. Does the ICH8 chipset have issues, or the
cards I am using and how they are routed?
Any suggestions as to what this is?
Justin.
next prev parent reply other threads:[~2007-04-05 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 22:12 Justin Piszcz
2007-04-05 22:13 ` Justin Piszcz [this message]
2007-04-05 22:18 ` Justin Piszcz
2007-04-05 22:31 ` Justin Piszcz
2007-04-05 22:45 ` Justin Piszcz
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=Pine.LNX.4.64.0704051812340.14476@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--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®