From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org, Martin Drab <drab@kepler.fjfi.cvut.cz>
Cc: linux-raid@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: Any Intel folks on the list? Intel PCI-E bridge ACPI resource question
Date: Thu, 5 Apr 2007 18:45:44 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704051844200.14983@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0704051830040.14983@p34.internal.lan>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1113 bytes --]
My .config is attached.. I cannot reproduce this problem, it only happened
once, but I want to find out how to make sure it does not happen again.
On Thu, 5 Apr 2007, Justin Piszcz wrote:
>
>
>>> On Thu, 5 Apr 2007, Justin Piszcz wrote:
>>>
>>>> http://www.ussg.iu.edu/hypermail/linux/kernel/0701.3/0315.html
>>>>
>
> Here is the badblocks output:
>
> 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:~#
>
> Nothing wrong with the drive. This problem concerns me greatly as I am not
> sure what I can do to fix this issue, how can I make sure it does not happen
> again?
>
> Justin.
>
[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 7508 bytes --]
parent reply other threads:[~2007-04-05 22:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.64.0704051830040.14983@p34.internal.lan>]
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.0704051844200.14983@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=drab@kepler.fjfi.cvut.cz \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).