mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sy, Dely L" <dely.l.sy@intel.com>
To: <Tom.Duffy@Sun.COM>
Cc: <pcihpd-discuss@lists.sourceforge.net>, <linux-kernel@vger.kernel.org>
Subject: RE: 2.6.12-rc2-mm3 pciehp regression
Date: Wed, 20 Apr 2005 11:56:30 -0700	[thread overview]
Message-ID: <468F3FDA28AA87429AD807992E22D07E04FC7DD9@orsmsx408> (raw)

On Friday, April 15, 2005 12:48 PM, Tom Duffy wrote:
> From: "Sy, Dely L" <dely.l.sy@intel.com>
> > Thanks for reporting this.  I'll look into it.  Which was the last 
> > kernel you tested on your hw and worked for you?

> That is a good question.  I think it was a 2.6.11 kernel.  It was 
> definately before express was moved to a different directory, 
> whenever that occured.

Tom,

I was not able to duplicate this problem on my system yet for I have
trouble in getting my system booted up on 2.6.12-rc2-mm3.  I did some
back-tracking and found that the boot problem occurred also with 
2.6.12-rc2-mm2 & 2.6.12-rc2-mm3, and on two systems using IDE as boot 
drive. The config file I used worked fine on 2.6.11.7. I tried 
different config file without success.

The errors I encountered were:
Reading all physical volumes.  This may take a while...
Umount /sys failed: 16
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
Switchroot: mount failed 22
umount /initrd/dev failed: 2

I also encountered issue you & others discussed in the thread on
"Re: Heads up on 2.6.12-rc1 and later" if I used SCSI drive.

Can you send me the config file you used successfully on your 
system?

Thanks,
Dely

             reply	other threads:[~2005-04-20 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 18:56 Sy, Dely L [this message]
2005-04-20 19:50 ` Tom Duffy
2005-04-20 23:34 Sy, Dely L
2005-04-27 18:02 ` Tom Duffy
2005-04-28 23:26 kylin

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=468F3FDA28AA87429AD807992E22D07E04FC7DD9@orsmsx408 \
    --to=dely.l.sy@intel.com \
    --cc=Tom.Duffy@Sun.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    /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®