On Wed, Feb 08, 2006 at 03:13:19PM -0500, Jeff Dike wrote:
> On Thu, Feb 02, 2006 at 01:17:49PM -0500, [EMAIL PROTECTED] wrote:
> > I'm also seeing this on skas3.
>
> Can you try out the patch below? It fixes it on i386, but I'm still seeing
> segfaulting on x86_64.
Yup, that fixed it. 2.6.15.2-
On Thursday 09 February 2006 00:11, Allen Chan wrote:
> On Wednesday 08 February 2006 15:13, Jeff Dike wrote:
> > Can you try out the patch below? It fixes it on i386, but I'm
> > still seeing segfaulting on x86_64.
>
> The patch works great on my vanilla 2.6.15.3 guest kernel compiled on
> i386 r
On Wednesday 08 February 2006 15:13, Jeff Dike wrote:
> Can you try out the patch below? It fixes it on i386, but I'm
> still seeing segfaulting on x86_64.
The patch works great on my vanilla 2.6.15.3 guest kernel compiled on
i386 running on a skas3 host. No segfaults after several thousand
it
On Thu, Feb 02, 2006 at 01:17:49PM -0500, [EMAIL PROTECTED] wrote:
> I'm also seeing this on skas3.
Can you try out the patch below? It fixes it on i386, but I'm still seeing
segfaulting on x86_64.
Jeff
Index: linux-2.6.15/arch/um/sys-i386/signal.c
=
On Thu, Feb 02, 2006 at 12:01:26PM -0500, Allen Chan wrote:
> This issue may not be limited to skas0, as I'm encountering these
> symptoms while using skas3 patched hosts, both on my own machines and
> on a UML guest hosted at linode.com.
I'm also seeing this on skas3.
---
On Thursday 02 February 2006 11:23, Jeff Dike wrote:
> On Wed, Feb 01, 2006 at 03:28:06PM -0500, Allen Chan wrote:
>> The problem can be reproduced by repeatedly
> > executing the following command inside the UML guest:
> > tcsh -c 'echo `hostname`'
>
> Nice test case! This appears to be a ska
On Wed, Feb 01, 2006 at 03:28:06PM -0500, Allen Chan wrote:
The problem can be reproduced by repeatedly
> executing the following command inside the UML guest:
> tcsh -c 'echo `hostname`'
Nice test case! This appears to be a skas0 bug - the skas0 segfault handler
is segfaulting for some re
On Wed, Feb 01, 2006 at 03:28:06PM -0500, Allen Chan wrote:
> On Tuesday 31 January 2006 22:23, [EMAIL PROTECTED] wrote:
> > I tried upgrading my UML running 2.4.28-1um to 2.6.15.2-bs1. After
> > bringing the UML up under the later kernel, I noticed random
> > processes within the UML would segfaul
On Tuesday 31 January 2006 22:23, [EMAIL PROTECTED] wrote:
> I tried upgrading my UML running 2.4.28-1um to 2.6.15.2-bs1. After
> bringing the UML up under the later kernel, I noticed random
> processes within the UML would segfault. For instance, I tried
> SSHing to it over and over and in about 1
Resending, forgot to CC the list. Please excuse my dupe Blaisorblade.
On Wed, Feb 01, 2006 at 03:28:21PM +0100, Blaisorblade wrote:
> That's indeed harmless... but didn't the ssh log contain anything?
Nope. I was watching all syslog messages (all facilities, level debug and
higher) and no error
On Wednesday 01 February 2006 04:23, [EMAIL PROTECTED] wrote:
> I tried upgrading my UML running 2.4.28-1um to 2.6.15.2-bs1. After bringing
> the UML up under the later kernel, I noticed random processes within the
> UML would segfault. For instance, I tried SSHing to it over and over and in
> abou
I tried upgrading my UML running 2.4.28-1um to 2.6.15.2-bs1. After bringing
the UML up under the later kernel, I noticed random processes within the UML
would segfault. For instance, I tried SSHing to it over and over and in
about 1 in 5 attempts my shell or something else during the login procedu
12 matches
Mail list logo
