Jeff Dike wrote:
> On Thu, Jul 06, 2006 at 03:09:50AM -0600, Bernard Johnson wrote:
>> The host is Fedora 3 (kernel-2.6.12-2.3.legacy_FC3.skas3). The skas3
>> patch is skas-2.6.12-v8.2.patch.
>>
>> When I attempt to download a large file using yum (~110 Meg rpm), this
>> kernel panic occurs:
>
On Mon, Jul 03, 2006 at 02:20:16PM +0200, Jan Rychter wrote:
> 1) I mount /home with hostfs using the following line in fstab:
>none /home hostfs /home,rw 0 0
>
> df shows:
>
> none 10413255443693385415481253412470784
> 10413248933519167673017998136836096 47190722440083771496
On Mon, Jul 03, 2006 at 02:20:16PM +0200, Jan Rychter wrote:
> 1) I mount /home with hostfs using the following line in fstab:
>none /home hostfs /home,rw 0 0
>
> df shows:
>
> none 10413255443693385415481253412470784
> 10413248933519167673017998136836096 47190722440083771496
On Mon, Jul 03, 2006 at 10:28:22AM -0700, Jim Carter wrote:
> Please forgive me for interpreting without suggesting how to fix, but the
> interpretation might be useful. Is there any chance of trying out the
> 2.6.16 UML kernel on a 2.6.16 host? Version skew, particularly backwards,
> is very
On Wed, Jul 05, 2006 at 08:24:42PM +0200, Josef Spillner wrote:
> Hello,
>
> after finding a combination of kernel and root fs which don't throw
> NPTL-related errors on me (like the ones linked on the "new" webpages do),
The kernel linked there has NPTL support. What exactly were the errors?
On Thu, Jul 06, 2006 at 03:09:50AM -0600, Bernard Johnson wrote:
> The host is Fedora 3 (kernel-2.6.12-2.3.legacy_FC3.skas3). The skas3
> patch is skas-2.6.12-v8.2.patch.
>
> When I attempt to download a large file using yum (~110 Meg rpm), this
> kernel panic occurs:
How reproducable is this?
On Thu, Jul 06, 2006 at 08:45:34AM -0400, Samuel Korpi wrote:
> Apparently my mistake. I run UML with gdb and it seems 'killall
> linux' was not enough to kill the UML processes while gdb was still
> running.
You can't kill a process out from under gdb. It will die when gdb
detaches or continues
On Sat, Jul 01, 2006 at 01:58:08PM +0800, paul john wrote:
> i understood.
> but where the option ubd0r used for ?
ubd0r probably isn't used, but ubd[12...]r would be used when you want
to make sure that a block device won't be modified by a UML.
It's also probably a good idea when mapping somet
On Wed, Jul 05, 2006 at 08:28:19AM +0800, paul john wrote:
> can start an uml users can write read, but when it reboot , the uml backt
> to the orginal system?
Boot it on a COW file, when the UML is shut down, remove the COW file, and
the filesystem goes back to its original data.
Sorry,
Apparently my mistake. I run UML with gdb and it seems 'killall linux' was not
enough to kill the UML processes while gdb was still running.
But an interesting question is, why does the crash even occur - and just when
the system has been almost halted? Below is part of the output I
Hi,
How can I release the file lock on rootfs after an UML crash? The lock is
showing in /proc/locks and when I try to reboot UML it can't mount rootfs (due
to the file lock). I have killed all the UML processes. Wouldn't want to reboot
the whole machine every time this happens.
BR,
Sa
The host is Fedora 3 (kernel-2.6.12-2.3.legacy_FC3.skas3). The skas3
patch is skas-2.6.12-v8.2.patch.
When I attempt to download a large file using yum (~110 Meg rpm), this
kernel panic occurs:
Kernel panic - not syncing: Segfault with no mm
EIP: 0073:[<006e3402>] CPU: 0 Not tainted ESP: 007b
12 matches
Mail list logo
