public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jack Steiner <steiner@sgi.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: PATCH [1/1]: x86:fix i686 panic with the early_per_cpu macro
Date: Mon, 21 Apr 2008 15:47:04 -0700	[thread overview]
Message-ID: <480D1968.5050704@sgi.com> (raw)
In-Reply-To: <480CE4BC.2030002@sgi.com>

Mike Travis wrote:
> Ingo Molnar wrote:
>> * Mike Travis <travis@sgi.com> wrote:
>>
>>> ...  Do you 
>>> want me to consolidate the outstanding patches and send them again all 
>>> together?  
...
>> resending would be appreciated, if it's not hard. I had to disable the 
>> early-pointers cleanup patch because of the breakage it caused.
>>
>> 	Ingo
> 

The build tests have passed.  The kernel in all it's variations runs on
my intel box fine but fails on the amd box with boot disk errors.  Here's
what it should say:

    scsi0 : sata_nv
    ata1: SATA max UDMA/133 cmd 0x34d0 ctl 0x34c4 bmdma 0x3490 irq 19
    ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata1.00: ATA-7: WDC WD2500YD-01NVB1, 10.02E01, max UDMA/133
    ata1.00: 490234752 sectors, multi 16: LBA48 NCQ (depth 0/1)
    ata1.00: configured for UDMA/133
    scsi 0:0:0:0: Direct-Access     ATA      WDC WD2500YD-01N 10.0 PQ: 0 ANSI: 5
    sd 0:0:0:0: [sda] 490234752 512-byte hardware sectors (251000 MB)
    ...
     sda: sda1 sda2 < sda5 sda6 sda7 sda8 >
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    ...
    EXT3-fs: mounted filesystem with ordered data mode.
    VFS: Mounted root (ext3 filesystem) readonly.

But instead it fails:

    scsi0 : sata_nv
    ata1: SATA max UDMA/133 cmd 0x34d0 ctl 0x34c4 bmdma 0x3490 irq 19
    ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ...
    Root-NFS: No NFS server available, giving up.
    VFS: Unable to mount root fs via NFS, trying floppy.
    VFS: Insert root floppy and press ENTER

This is linux-2.6 + sched-latest with or without my patches installed
and different configurations including the simplest nosmp.  The root
FS is ok as I can boot an older kernel fine.  I've checked to insure
the file system is configured (ext2 in this case).  [Obviously the sata
driver is config'd.]

Any ideas?

Thanks,
Mike

           reply	other threads:[~2008-04-21 22:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <480CE4BC.2030002@sgi.com>]

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=480D1968.5050704@sgi.com \
    --to=travis@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=steiner@sgi.com \
    /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