www.rich-dad.com.ar
Please see this site in Subject
Re: NSLU2 Install problems with 4.0r2
I had one crash and one failure while trying to install Debian 4.0r2 on my NSLU2: 1. Crashed while trying to write a new partition table. 2. Failed during software install step, tried to setup as a Web Server and File Server. The crash was a one time event, I haven't tried to recreate the failure because it only happens after taking some two hours to install all the necessary software. After installing using only the base software I was successful in getting the slug up and running. - jake On Dec 30, 2007 11:03 AM, John Winters [EMAIL PROTECTED] wrote: On 29/12/2007, John Winters [EMAIL PROTECTED] wrote: Dave Potts wrote: The relevant lines towards the end seem to be: Dec 29 21:34:12 base-installer: Err http://ftp.uk.debian.org etch Release.gpg Dec 29 21:34:12 base-installer: Could not connect to ftp.uk.debian.org:80 (1.0.0.0), connection timed out The slug seems to think that ftp.uk.debian.org has an IP address of 1.0.0.0 which is obviously wrong. It should be 83.142.228.128. This suggests that there is something wrong with the DNS setup, either on the slug itself, or on the machine which it is using as a DNS server. Given that you're picking up your IP address by DHCP, what values are being sent for the DNS server? What ends up in /etc/resolv.conf on the slug? Contents of resolv.conf are: nameserver 192.168.1.1 ...which is the IP of my ADSL router and the same setting as on my laptop that resolves the address just fine. Funnily enough I've just started experiencing exactly the same problem with a cheap no-name ADSL router which I'm trying to set up for my father. The first computer to connect to it gets working DNS whilst the second one gets all DNS queries answered with 1.0.0.0 as the address. This is on the end of a Tiscali ADSL connection, so I don't know whether it's the router or Tiscali f**king things up. Sounds like it's the same as your problem though. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458745: arm-only miscompilation of alloca code
Package: gcc-4.2
Version: 4.2.2-4
Severity: important
/tmp/foo.c:
=
#include stdio.h
#include alloca.h
#include stdarg.h
#define object void *
int VFUN_NARGS;
void *alloca_val;
struct cons {
object c_cdr;
object c_car;
};
#define Cnil 0
static void
foo(object first,...) {
va_list ap;
int narg = VFUN_NARGS;
struct cons *V1128;
object V1129;
va_start(ap,first);
V1129 =
!narg? Cnil : (alloca_val=alloca((narg)*sizeof(struct cons)+sizeof(object)),
({object _b=(void *)alloca_val;if (((unsigned
long)_b)sizeof(_b)) _b++;
{register struct cons *_p=(void *)_b;
{struct cons *_e=_p+(narg-1);
for (;_p_e;_p++) {_p-c_car=({object
_t=first;first=va_arg(ap,object);_t;});_p-c_cdr=(object)(_p+1);}}
_p-c_car=first;_p-c_cdr=Cnil;}_b;}));
va_end(ap);
V1128= V1129;
for (;V1128!=Cnil;V1128=V1128-c_cdr)
printf(%p\n,V1128-c_car);
}
int
main(int argc,char * argv[]) {
VFUN_NARGS=4;
foo(argc,1,2,3);
return 0;
}
=
i386 sid:
=
cc -g /tmp/foo.c -o /tmp/foo
/tmp/foo
0xbf867bd0
0x1
0x2
0x3
=
leisner dchroot sid:
=
cc -g foo.c -o foo
./foo
0x18beed5d
Segmentation fault
=
Take care,
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.20-gen
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages gcc-4.2 depends on:
ii binutils2.18.1~cvs20071027-1 The GNU assembler, linker and bina
ii cpp-4.2 4.2.2-4 The GNU C preprocessor
ii gcc-4.2-base4.2.2-4 The GNU Compiler Collection (base
ii libc6 2.7-2GNU C Library: Shared libraries
ii libgcc1 1:4.2.2-4GCC support library
ii libgomp14.2.2-4 GCC OpenMP (GOMP) support library
Versions of packages gcc-4.2 recommends:
ii libc6-dev 2.7-2 GNU C Library: Development Librari
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more ram/swap on leisner, please?
On 2008-01-02 11:00 -0500, Camm Maguire wrote: I requested this a few weeks ago too -- don't know if the message got through. It did, but may not have been spotted by Bill on the end of the fortran transition thread. Bill Gatliff is the man with the access to add RAM or swap. I suspect he board is already maxed out on physical RAM (it's only little), but some more swap ought to be do-able. Bill? Some better hardware is in the works, but leisner will have to suffice for a little while longer. Wookey -- Principal hats: Balloonz - Toby Churchill - Aleph One - Debian http://wookware.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more ram/swap on leisner, please?
On Wed, 02 Jan 2008, Wookey wrote: On 2008-01-02 11:00 -0500, Camm Maguire wrote: I requested this a few weeks ago too -- don't know if the message got through. It did, but may not have been spotted by Bill on the end of the fortran transition thread. Bill Gatliff is the man with the access to add RAM or swap. I suspect he board is already maxed out on physical RAM (it's only little), but some more swap ought to be do-able. Currently the box only does NFS, and I'm not sure how well swapfiles over NFS work. But maybe we can get a physical disk for swap purposes, or Bill can come up with another solution. Some better hardware is in the works, but leisner will have to suffice for a little while longer. We also have agnesi (ssh on 2260), which has also only 64 megs of physical memory, but at least has swap. Peter -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more ram/swap on leisner, please?
Guys: Ok, I've set up a 5GB swap over NBD. If the system reboots, it won't automagically reattach it. The kernel is NOT running the nbd swap patch, so I don't know if the system will deadlock under stress, or not... b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more ram/swap on leisner, please?
On Wed, Jan 02, 2008 at 01:00:02PM -0600, Bill Gatliff wrote: Ok, I've set up a 5GB swap over NBD. If the system reboots, it won't automagically reattach it. The kernel is NOT running the nbd swap patch, so I don't know if the system will deadlock under stress, or not... It most likely will... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more ram/swap on leisner, please?
Lennert Buytenhek wrote: On Wed, Jan 02, 2008 at 01:00:02PM -0600, Bill Gatliff wrote: Ok, I've set up a 5GB swap over NBD. If the system reboots, it won't automagically reattach it. The kernel is NOT running the nbd swap patch, so I don't know if the system will deadlock under stress, or not... It most likely will... Older kernels definitely would. But the mailing lists aren't so clear about the current state of things, and I can't seem to find the patches either... b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more ram/swap on leisner, please?
2008/1/2, Bill Gatliff [EMAIL PROTECTED]: Lennert Buytenhek wrote: On Wed, Jan 02, 2008 at 01:00:02PM -0600, Bill Gatliff wrote: Ok, I've set up a 5GB swap over NBD. If the system reboots, it won't automagically reattach it. The kernel is NOT running the nbd swap patch, so I don't know if the system will deadlock under stress, or not... It most likely will... Older kernels definitely would. But the mailing lists aren't so clear about the current state of things, and I can't seem to find the patches either... I run NDB swap on little arms and qemus routinely and have never had a lockup despite stressing them. The trick is *not* to include nbd-client's -swap flag, with which, if i remember correctly, it doesn't work at all. The other way is to create an ext2 in a file on an NFS-mounted volume, loop-mount it on the ARM box, create a big file in it, mkswap and swapon that. A bit contorted but it was stable the one time I had to do that. M Sorry about repetitions, Bill, thought I'd put this on list too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more ram/swap on leisner, please?
On Wed, Jan 02, 2008 at 02:17:46PM -0600, Bill Gatliff wrote: Ok, I've set up a 5GB swap over NBD. If the system reboots, it won't automagically reattach it. The kernel is NOT running the nbd swap patch, so I don't know if the system will deadlock under stress, or not... It most likely will... Older kernels definitely would. But the mailing lists aren't so clear about the current state of things, The issue of network swap deadlocking has not been fixed so far. and I can't seem to find the patches either... Peter Zijlstra and Daniel Phillips have been posting patches to fix the underlying issue, but those have not been merged yet, as far as I know. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more ram/swap on leisner, please?
On Wed, Jan 02, 2008 at 08:30:07PM +, Martin Guy wrote: I run NDB swap on little arms and qemus routinely and have never had a lockup despite stressing them. You obviously haven't stressed your systems hard enough, then. :) Current mainline kernels all eventually deadlock when swapping over the network. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more ram/swap on leisner, please?
Martin Guy wrote: I run NDB swap on little arms and qemus routinely and have never had a lockup despite stressing them. The trick is *not* to include nbd-client's -swap flag, with which, if i remember correctly, it doesn't work at all. Indeed. With that flag, nbd-client won't run at all. The other way is to create an ext2 in a file on an NFS-mounted volume, loop-mount it on the ARM box, create a big file in it, mkswap and swapon that. A bit contorted but it was stable the one time I had to do that. Yea, I can't get my head around that until next week, at least. :) Sorry about repetitions, Bill, thought I'd put this on list too. You did. :) b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: more ram/swap on leisner, please?
Lennert Buytenhek wrote: On Wed, Jan 02, 2008 at 08:30:07PM +, Martin Guy wrote: I run NDB swap on little arms and qemus routinely and have never had a lockup despite stressing them. You obviously haven't stressed your systems hard enough, then. :) Heh, maybe because they're stressing _me_ even harder! :) b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
