linux-kernel - Re: 2.6.18-rc3-mm2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 23 Aug 2006 10:02:37 -0700
From:	Mark Haverkamp <markh@...l.org>
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.18-rc3-mm2

On Fri, 2006-08-11 at 15:58 -0700, Andrew Morton wrote:
> On Fri, 11 Aug 2006 13:31:03 -0700
> Mark Haverkamp <markh@...l.org> wrote:
> 
> > > NR_IRQS is (sometimes) calculated from NR_CPUS via complex means.  Reducing
> > > your NR_CPUS should fix things up.
> > 
> > It helps.  I set NR_CPUS to 8 and got past that problem.  Now I can't
> > get the root to mount.
> > 
> > Here is some output.  I had to copy it from the VGA since this doesn't
> > show up on the serial output.
> > 
> > Creating root device
> > Mounting root filesystem
> > mount: error 6 mounting ext3
> > Switching to new root
> > ERROR opening /dev/console!!!!:2
> > error dup2'ing fd of 0 to 0
> > error dup2'ing fd of 0 to 1
> > error dup2'ing fd of 0 to 2
> > umounting old /proc
> > unmounting old /sys
> > Switchroot: mount failed: 22
> > Kernel Panic ....
> 
> Looks like early userspace got ENXIO when trying to mount the root fs.
> 
> Don't know, sorry.  What distro is this running?
> 
> It might be useful to diff this kernel's boot log with 2.6.18-rc4's, see if
> we can spot the problem that way.

Sorry for taking so long to respond.  When I got back to it this week I
noticed that there was a new mm kernel patch.  I updated to it and now I
can boot my system OK.

Mark.


> 
-- 
Mark Haverkamp <markh@...l.org>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/