On Mon, Mar 21, 2005 at 07:53:15PM -0500, Jon Smirl wrote:
> Here is fedora's initrd nash script from my system. I modified it with
> the sleep lines.
>
> It already is creating the /dev node with 'mkrootdev /dev/root'
> I don't think udev is even running yet. Something else is causing this.
>
>
On Mon, Mar 21, 2005 at 08:14:29PM -0500, Kyle Moffett wrote:
> On Mar 21, 2005, at 19:19, Andrew Morton wrote:
> >Jon Smirl <[EMAIL PROTECTED]> wrote:
> >>Jens is right that this is a user space issue, but how many people are
> >>going to find this out the hard way when their root drives stop
> >>
On Mon, Mar 21, 2005 at 07:57:04PM -0500, Jon Smirl wrote:
> On Mon, 21 Mar 2005 16:49:36 -0800, Greg KH <[EMAIL PROTECTED]> wrote:
> > Jon, what distro are you using?
>
> Up2date Fedore Core 3
Ok, sounds like a distro issue, try filing a bug in their bugzilla :)
thanks,
greg k-h
-
To unsubscri
On Mar 21, 2005, at 19:19, Andrew Morton wrote:
Jon Smirl <[EMAIL PROTECTED]> wrote:
Jens is right that this is a user space issue, but how many people are
going to find this out the hard way when their root drives stop
mounting. Since no one is complaining I have to assume that most
kernel develop
On Mon, 21 Mar 2005 16:49:36 -0800, Greg KH <[EMAIL PROTECTED]> wrote:
> The distros that use udev have already all worked out these issues with
> their init scripts and such, so it shouldn't be an issue anymore.
>
> Jon, what distro are you using?
The mkinitrd script is broken for up2date Fedore
On Mon, 21 Mar 2005 16:49:36 -0800, Greg KH <[EMAIL PROTECTED]> wrote:
> Jon, what distro are you using?
Up2date Fedore Core 3
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
On Mon, Mar 21, 2005 at 04:43:18PM -0800, Andrew Morton wrote:
> Greg KH <[EMAIL PROTECTED]> wrote:
> >
> > > I don't agree that this is a userspace issue. It's just not sane for a
> > > driver to be in an unusable state for an arbitrary length of time after
> > > modprobe returns.
> >
> > It is
Here is fedora's initrd nash script from my system. I modified it with
the sleep lines.
It already is creating the /dev node with 'mkrootdev /dev/root'
I don't think udev is even running yet. Something else is causing this.
echo "Loading libata.ko module"
insmod /lib/libata.ko
echo "Loading ata_p
On Mon, 21 Mar 2005 16:38:08 -0800, Greg KH <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 21, 2005 at 04:19:25PM -0800, Andrew Morton wrote:
> >
> > (Adds lots of cc's. I trust that's OK).
> >
> > Jon Smirl <[EMAIL PROTECTED]> wrote:
> > >
> > > No, I think Jens wants all of the distributions to fix it
Greg KH <[EMAIL PROTECTED]> wrote:
>
> > I don't agree that this is a userspace issue. It's just not sane for a
> > driver to be in an unusable state for an arbitrary length of time after
> > modprobe returns.
>
> It is a userspace issue. If you have a static /dev there are no
> problems, right?
On Mon, Mar 21, 2005 at 04:19:25PM -0800, Andrew Morton wrote:
>
> (Adds lots of cc's. I trust that's OK).
>
> Jon Smirl <[EMAIL PROTECTED]> wrote:
> >
> > No, I think Jens wants all of the distributions to fix it. I have
> > filed a bug with Fedora on it.
> >
> > Something changed in the timin
(Adds lots of cc's. I trust that's OK).
Jon Smirl <[EMAIL PROTECTED]> wrote:
>
> No, I think Jens wants all of the distributions to fix it. I have
> filed a bug with Fedora on it.
>
> Something changed in the timing for loading drivers during boot. You
> used to be able to do:
> modprobe ata_pi
On Tue, Mar 15 2005, Jon Smirl wrote:
> Is this problem still being tracked?
>
> I have figured out a work around of adding a 1 second pause in nash
> after the ata_piix driver is loaded. Something has changed in the
> driver initialization timing such that later stages of boot try to
> access the
Is this problem still being tracked?
I have figured out a work around of adding a 1 second pause in nash
after the ata_piix driver is loaded. Something has changed in the
driver initialization timing such that later stages of boot try to
access the driver before the driver has created the device w
On Sat, 12 Mar 2005 18:15:30 +0500, Alexander E. Patrakov
<[EMAIL PROTECTED]> wrote:
> Jon Smirl wrote:
>
> > Here's a big clue, if I build ata_piix in I can boot. If it is a
> > module I can't. The console output definitely shows that the module is
> > being loaded.
>
> Of course I am not an exp
Jon Smirl wrote:
> Here's a big clue, if I build ata_piix in I can boot. If it is a
> module I can't. The console output definitely shows that the module is
> being loaded.
Of course I am not an expert here, but I want to rule out some trivial
userspace things first.
Some time ago Greg KH said
On Thu, 10 Mar 2005 19:11:37 -0800, Matt Mackall <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 10, 2005 at 01:52:59PM -0500, Jon Smirl wrote:
> > Here's a big clue, if I build ata_piix in I can boot. If it is a
> > module I can't. The console output definitely shows that the module is
> > being loaded.
On Thu, Mar 10, 2005 at 01:52:59PM -0500, Jon Smirl wrote:
> Here's a big clue, if I build ata_piix in I can boot. If it is a
> module I can't. The console output definitely shows that the module is
> being loaded.
Can you post your config?
--
Mathematics is the supreme nostalgia of our time.
-
Here's a big clue, if I build ata_piix in I can boot. If it is a
module I can't. The console output definitely shows that the module is
being loaded.
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECT
I see:
Loading libata.ko module
Loading ata_piix.ko module
ACPI: PCI interupt :00:1f.2[A] -> GSI 18 (level, low) -> IRQ 169
ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 169
ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA0 irq 169
then raid autorun, one of the raid pa
On Thu, Mar 10 2005, Jon Smirl wrote:
> On Thu, 10 Mar 2005 17:01:55 +0100, Jens Axboe <[EMAIL PROTECTED]> wrote:
> > what are the major/minor numbers of /dev/root?
>
>
> If I boot on a working system it is 8,5
I see no /dev/sda detected in your system from the dmesg. Ahh this is
where it panics
On Thu, 10 Mar 2005 17:01:55 +0100, Jens Axboe <[EMAIL PROTECTED]> wrote:
> what are the major/minor numbers of /dev/root?
If I boot on a working system it is 8,5
mkrootdev is a nash command
mkrootdev path
Makes path a block inode for the device which should be mounted
On Thu, Mar 10 2005, Jon Smirl wrote:
> Here's what it is doing... looks like the first mount is failing
>
> echo Creating root device
> mkrootdev /dev/root
> umount /sys
> echo Mounting root filesystem
> mount -o defaults --ro -t ext3 /dev/root /sysroot
> mount -t tmpfs --bind /dev /sysroot/dev
>
Here's what it is doing... looks like the first mount is failing
echo Creating root device
mkrootdev /dev/root
umount /sys
echo Mounting root filesystem
mount -o defaults --ro -t ext3 /dev/root /sysroot
mount -t tmpfs --bind /dev /sysroot/dev
echo Switching to new root
switchroot /sysroot
umount /
On Thu, Mar 10 2005, Jon Smirl wrote:
> On Thu, 10 Mar 2005 16:31:51 +0100, Jens Axboe <[EMAIL PROTECTED]> wrote:
> > On Thu, Mar 10 2005, Jon Smirl wrote:
> > > LABEL=/ / ext3defaults1
> > > 1
> > > label / is on /dev/sda6
> > >
> > > Creating roo
On Thu, 10 Mar 2005 16:31:51 +0100, Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 10 2005, Jon Smirl wrote:
> > LABEL=/ / ext3defaults1 1
> > label / is on /dev/sda6
> >
> > Creating root device
> > Mounting root filesystem
> > mount: error 6
On Thu, Mar 10 2005, Jon Smirl wrote:
> LABEL=/ / ext3defaults1 1
> label / is on /dev/sda6
>
> Creating root device
> Mounting root filesystem
> mount: error 6 mounting ext3
if 6 is the errno, it looks like it is trying to open a device that does
LABEL=/ / ext3defaults1 1
label / is on /dev/sda6
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
Switchroot: mount failed 22
umount /initrd/dev failed: 2
This is what i
On Wed, Mar 09 2005, Jon Smirl wrote:
> On Wed, 9 Mar 2005 22:09:26 +0100, Jens Axboe <[EMAIL PROTECTED]> wrote:
> > probably not worth the bother, looks like barrier problems. get the
> > serial console running instead and send the full output, I'll take a
> > look in the morning.
>
> serial cons
On Wed, 9 Mar 2005 22:09:26 +0100, Jens Axboe <[EMAIL PROTECTED]> wrote:
> probably not worth the bother, looks like barrier problems. get the
> serial console running instead and send the full output, I'll take a
> look in the morning.
serial console boot output attached.
>
> --
> Jens Axboe
>
On Wed, Mar 09 2005, Jon Smirl wrote:
> On Wed, 09 Mar 2005 15:31:10 -0500, Jeff Garzik <[EMAIL PROTECTED]> wrote:
> > Well, there are no changes in libata from bk4 to present. The only
> > thing I see in the -bk4-bk5 increment diff that's immediately noticeable
> > is the barrier stuff.
>
> bk4
Jon Smirl wrote:
On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik <[EMAIL PROTECTED]> wrote:
Jon Smirl wrote:
Something in the last 24hrs in linus bk broke my ability to mount root:
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to n
On Wed, 09 Mar 2005 15:31:10 -0500, Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Well, there are no changes in libata from bk4 to present. The only
> thing I see in the -bk4-bk5 increment diff that's immediately noticeable
> is the barrier stuff.
bk4 works
bk5 is broken
Where are these *.key files?
Jon Smirl wrote:
On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik <[EMAIL PROTECTED]> wrote:
Jon Smirl wrote:
Something in the last 24hrs in linus bk broke my ability to mount root:
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to n
Jon Smirl wrote:
On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik <[EMAIL PROTECTED]> wrote:
Jon Smirl wrote:
Something in the last 24hrs in linus bk broke my ability to mount root:
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to n
On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Jon Smirl wrote:
> > Something in the last 24hrs in linus bk broke my ability to mount root:
> >
> > Creating root device
> > Mounting root filesystem
> > mount: error 6 mounting ext3
> > mount: error 2 mounting none
> > S
Jon Smirl wrote:
Something in the last 24hrs in linus bk broke my ability to mount root:
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
Switchroot: mount failed 22
umount /initrd/dev failed: 2
If I back off a day everyth
37 matches
Mail list logo
