public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: "R. J. Wysocki" <rjwysocki@sisk.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc1: Possible SCSI-related problem on dual Opteron w/ NUMA
Date: 20 Jul 2004 14:02:11 +0200
Date: Tue, 20 Jul 2004 14:02:11 +0200	[thread overview]
Message-ID: <20040720120211.GA72772@muc.de> (raw)
In-Reply-To: <200407181448.14614.rjwysocki@sisk.pl>

> I had this problem again this morning.  I was unpacking the kernel tarball to 
> /dev/sda8 and it went south (the tarball had been partially unpacked before 
> the partition was remounted r-o).  Then, I got back to 2.6.7 and ran fsck - 
> now it found some errors (obviously) and fixed them.  Next (on 2.6.7), I 
> unpacked the kernel to /dev/sda8 (again) and compiled the 2.6.8-rc2.  I ran 
> it, unpacked the kernel to /dev/sda8 (again) and compiled it - everything 
> worked.  Then, I applied your patch on top of the newly created 2.6.8-rc2 
> tree and compiled the kernel.  After installing and running it I tried to 
> unpack the kernel to /dev/sda8 (again) and it went south, so I got back to 
> the "plain" 2.6.8-rc2, ran fsck and fixed the partition, unpacked the kernel 
> to /dev/sda8 - and it all worked.
> 
> So, it seems, there's something in your patch that causes this misbehavior.

In which patch eactly? x86_64-2.6.8rc1-1 or x86_64-2.6.8rc1-2 ? 

If it started with -2 can you check if -1 has the problem too?

-Andi

      parent reply	other threads:[~2004-07-20 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200407171826.03709.rjwysocki@sisk.pl>
2004-07-17 18:12 ` 2.6.8-rc1: Possible SCSI-related problem on dual Opteron w/ NUMA Andi Kleen
2004-07-17 19:09   ` R. J. Wysocki
2004-07-18 12:48     ` R. J. Wysocki
2004-07-18 21:38       ` R. J. Wysocki
2004-07-20 12:04         ` Andi Kleen
2004-07-20 14:23           ` R. J. Wysocki
2004-07-20 12:02       ` Andi Kleen [this message]

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=20040720120211.GA72772@muc.de \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjwysocki@sisk.pl \
    /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