Title: Soft lockups while debugging
Is it normal to get a "BUG: soft lockup detected on CPU#0!" when using gdb in SKAS0 mode?
Can they be safely ignored; i.e. is the process continuing on without changes afterwards?
-- John
> > If the UML website was a Wiki, I'd add text describing the
different
> > block device naming and how it affects root filesystems.
>
> The UML wiki is http://uml.harlowhill.com/
http://uml.harlowhill.com/index.php/DevfsUdev. Feel free to correct,
copy elsewhere or barf.
-- John
> > If the UML website was a Wiki, I'd add text describing the different
> > block device naming and how it affects root filesystems.
> > But I can't, so you might want to.
>
> The UML wiki is http://uml.harlowhill.com/
Do you know off-hand when in the 2.6 series ufs replaced devfs, for UML
p
> Starting udev:
> > [ OK ]
>
> This is the point - it remounts a tmpfs filesystem on /dev
> and fills it via udev.
There are lines above that saying:
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Is the "true" root fs mounte
I've got another cannot-boot problem. My UML is built from 2.6.16-rc4
source, with Jeff's patch set and the defconfig configuration. My root
filesystem is
http://www.stearns.org/uml-root/root_fs.fc-3-base.pristine.20050605.bz2,
with MAKEDEV std, generic, and the ubd0 etc. devices created per the
> > The TLS patches in that set assume that the host OS provides
> > thread-area syscalls, doesn't it? >
>
> That being said, it would be nice to see if it can be
> emulated somehow.
Agreed, but I'm not the man for the job. I don't know anything about
that corner of the kernel.
-- John
> On Thu, Feb 16, 2006 at 02:08:13PM -0600, John Dykstra wrote:
> > That got me further. I ran into the "set_thread_area failed when
> > setting up thread-local storage" problem, found your post on the
> > mailing list, and added
> "LD_LIBRARY_PATH=
Title: Build error in arch/um/os-Linux/aio.c with today's 2.6.16-rc4 patch set
It appears to me that the kernel tree will not build with the 2.6.16-rc4 patch set I downloaded today, if HAVE_AIO_ABI is not defined.
finish_aio_26() is referenced in arch/um/os-Linux/aio.c, but is not defined.
> That got me further. I ran into the "set_thread_area failed
> when setting up thread-local storage" problem, found your
> post on the mailing list, and added
> "LD_LIBRARY_PATH=/lib/obsolete/linuxthreads" to the command
> line. Unfortunately, I'm still getting the same error:
And once I ha
> "plus I've
> added the /dev links needed to boot without devfs"
>
> If by "/dev links" you mean indeed "symlinks" I don't
> understand well what you
> did and it could be wrong. I mean, you could have either:
>
> a) used MAKEDEV
> b) setup udev and created basic device nodes only
> and both t
> Instead, make sure that before building you did "make
> defconfig ARCH=um". If
> not, it doesn't start from the defconfig but instead from the
> host config (if
> the versions match) and you get a wrong config.
The config I'm using right now, I extracted from the UML built for 2.6
that I re
> > and extracted the
> > initrd image from /boot (see below).
>
> In short - this is your error. a) it's not needed, b) it
> couldn't work, c) it
> should fail more gracefully but it hangs.
When I boot without the initrd, it hangs after "unable to open an
initial console". I figured that, a
This is another one of those "I can't get it to boot" postings.
Actually, in two weeks of trying, I haven't been able to get any 2.6
kernel to boot under UML, at least not with a root filesystem that
faintly approaches what the kernel requires. I've used UML quite
extensively with 2.4 kernels, but
13 matches
Mail list logo
