I would like to help as well, but I'm not super experienced with the
Debian way of doing things.
I am a decent developer, but I found attempting to get libc fixed for
Alpha to be just simply traumatic.
Could someone tell me offline what would be involved? I have a few
Alpha systems here tha
i don't need any of the 2.6.23 functionality - I was just really trying the
2.6.23 kernel to
make sure nothing major was broken with it.
I *could* use bootp I suppose, but that would require a tftp service someplace
- suppose that's not so hard.
I will probably just wait for an update, or fin
Is it the same kernel? Does the new machine's kernel have firmware upload
enabled?
...tom
On Fri, 13 Apr 2007 15:39:43 +0100, Tim Cutts <[EMAIL PROTECTED]> wrote:
> I'm in the process of preparing an ES45 for porting use by Debian
> developers. The machine is essentially identical to goetz; i
Sorry to confuse 'unstable' with 'not fixed'.
Lots of zombies often led to 'unstable' for me...
...tom
-Original Message-
From: "Uwe Schindler" <[EMAIL PROTECTED]>
To: "'Thomas Evans'" <[EMAIL PROTECTED]>; "&#
Not cool that the experimental glibc doesn't fix this...
...tom
-Original Message-
From: "Stan Lewis" <[EMAIL PROTECTED]>
To: debian-alpha@lists.debian.org
Sent: 2/20/07 3:08 PM
Subject: Hello! (and zombie processes...)
Hey all!
I've just gotten a Compaq XP1000 last Friday and have been
I just noticed that libc6.1 is scheduled to be upgraded in "stable" -
will this be a broken one?
I'd hate for a broken libc to be in stable
...tom
Uwe Schindler wrote:
At 10:45 27.02.2006, Steve Langasek wrote:
> Now I am very happy with alpha support, the only thing is the problem
> wi
So, is it just the case that the x86 interpreter needs to be rebuilt
with a newer glibc?
While at DEC I had been partially responsible for that component on
Linux/Alpha.
The last round, we tried to make that component open source, without luck.
I had tried to find out what needed to be done t
Another datapoint - I have a 2nd 164LX, runs Debian testing instead of
unstable (libc version 2.3.2.ds1-2) - I built the same kernel (2.6.12.5) that
is running on the Debian unstable system.
Threads clean up just fine, so I'm going to hazard a guess that it is not the
kernel at this time - porb
I switched back to a previous kernel version that I ran for months.
I don't remember seeing zombie threads back then - the zombies still appear
now - perhaps this is not a kernel issue, but rather a pthreads issue?
I gave up on reverting to stable - too many frightening messages.
Has anyone els
Has anyone else been using Reiser4 with Alpha?
I've been using it for a while, but only just realized that it generated tons
of alignment fixups - during intense operation, it can be hundreds of
thousands per second.
I was wondering why kernel compiles were so slow - they would basically lock
Thanks for the advice -
> There's something about X should be run niced on 2.4.X and not on 2.5.X and
> later (the new kernel scheduler passes credits along sockets when processes
> are stalled or something like that).
>
> Maybe changing your nice value with a "dpkg-reconfigure xfree86-common"
Slight update - if I change KDE to not include the window
contents when dragging or resizing, all is well with auto
playback.
The main reason this bugs me is because it used to work fine
with the last 2.4.X kernel I used.
...tom
On Sun, 2004-10-10 at 20:19, Thomas Evans wrote:
> Hi
Hi all -
I upgraded from a 2.4.X kernel a few weeks back and have been
experiencing choppy audio playback whenever I move or scroll
windows in X.
This didn't (doesn't) happen when I us a 2.4 kernel.
My machine is 164LX, 600Mhz, 1GB RAM, a Permedia2 graphics card.
I have tried playback with mpg3
Not certain if it's an on on-disk structure - it is used all over,
but the comments in it would suggest that it is in-memory only
(especially since it contains at least one pointer, which would
make little sense in an on disk struct).
Even in that case, the purpose of the cassert() in the coords_
Just checked - the Andrew Morton -mm4 patch has the offending cassert
ifdef'd out.
This is why the reiser4 stuff compiles on 64bit platforms in that patch.
...tom
-Original Message-
From: Thomas Evans [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 09, 2004 3:11 PM
To: [
kernel sources.
...tom
-Original Message-
From: Tyson Whitehead [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 09, 2004 3:13 PM
To: debian-alpha@lists.debian.org
Cc: Thomas Evans; debian-user@lists.debian.org
Subject: Re: reiser4 kernel patch
-BEGIN PGP SIGNED MESSAGE-
Hash
Hi all -
I was trying out the reiser4 kernel patch and ran in a build-time assert on
my Alpha machine.
I wasn't sure what package I should attribute the issue to - any suggestions
would be great!
Thanks,
...tom
Hi All -
I was getting ready to file a bug for Mozilla in
Debian Alpha unstable - just curious if anyone else has
seen this - essentially a crash when rendering a page.
Sometimes it happens, sometime it doesn't. It doesn't happen
as much when I run it as root (probably just coincedence).
In an
I guess I'm in the minority (based on prior discussions on
debian-alpha), but IMHO the above is a better way to work around this
issue than making slower performance the default... :-)
Yeah, many of us would rather have applications "just work".
Those doing serious FP work on an Alpha for which
Yes I am booting from MILO (spare me the SRM lecture :-)
I still use NT on the machine and would rather
not have to reflash each time I boot into NT or Linux).
...tom
On Wed, 2004-01-14 at 11:41, John Goerzen wrote:
> On Tue, Jan 13, 2004 at 09:49:13PM -0500, Thomas Evans wrote:
> >
&
I have a panic with the released 2.6.1 on my 164LX
and Adaptec controller. I happens when my root
partition is being mounted (EXT3). An unaligned
access occurs followed by a message stating that init
was killed.
...tom
On Tue, 2004-01-13 at 21:17, John Goerzen wrote:
> On Fri, Jan 09, 2004 at
On Wed, Nov 05, 2003 at 11:23:09AM, Phil Mendelsohn wrote:
>I don't have a beef. But, having seen DEC introduce a lot of things
>that the world hasn't really grokked yet makes me mad at the parallel
>between your concern with IEEE compliance and Kurt Vonnegut's story
>"Harrison Bergeron." (Brie
On Wed, 2003-11-05 at 04:12, Falk Hueffner wrote:
> Phil Carmody <[EMAIL PROTECTED]> writes:
>
> > --- Thomas Evans <[EMAIL PROTECTED]> wrote:
> > > I really hope that no one is doing severely high
> > > performance, mission critical, FP code on pre-EV6
> I do all of my presieving and some of my testing for
> my PIES project on a pre-EV6 alpha. No, it's not
> exactly mission critical, but it _is_ high performance,
> and it is FP code. (And it doesn't depend on IEEE
> nappy-changing as it doesn't shit itself.)
> http://primes.utm.edu/bios/top2
Has there been any resolution to the SIGFPE issue on
pre-EV6 Alpha and Debian (just had another crash that
pissed me off)?
I really hope that no one is doing severely high
performance, mission critical, FP code on pre-EV6
alphas these days, so I really feel that defaulting
all Debian built Alpha
2.6.0-test9 kernel
Thus spake Thomas Evans:
> I can boot and all seems fine until gdm/X starts - a few seconds
> afterwards, the whole machine hangs.
>
> I have a 164LX/600Mhz/1GB/Adaptec SCSI (I've tried the "old" and the
> new driver)/Permedia2.
>
> I can b
Hi all -
I've been tring to using the most recent 2.6.0-test9 kernel
with my "stable" Debian installaiton.
I built the kernel with gcc-3.0 (3.3 caused an alignment fixup
that killed init). I've also built previous test versions
with 2.95 and have the same problem.
I can boot and all seems fi
Hi All -
Tried building and using the "latest" 2.6.0 kernel with patches.
After finally figuring out yet another device naming scheme
for "root=", I now get a crash in some mm file (at work now
don't remember the exact error). Anyway, it happens just after
loading devfs (since my fstad is still
I used to agree with this logic - it annoyed me to no end
that most of the FPEs out there were the result of
sloppy FP programming.
Then this week, an application I needed to use started
giving me FPEs. No number crunching here, just silly project
management. I have rebuilt glib, libgnomecanvas,
> BTW, I recently added a 1394 firewire interface to my PC164LX.
> It works great. I get 27mb/sec to/from a firewire disk. The on board
> IDE interface and Symbios SCSI interfaces only get 12-14mb/sec. USB 2.0
> got around 17mb/sec before hanging. The 1394 interface is very stable
> in 2.4.21;
On Wed, 2003-05-07 at 04:18, Matt Simis wrote:
> "Thomas Evans" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > >Interesting that the Alpha consistantly outperforms the Athlon on
> > >"verify/s" but looses ground on signs/s.
>
>Interesting that the Alpha consistantly outperforms the Athlon on
>"verify/s" but looses ground on signs/s.
It's been a while, but one of my tasks before
leaving Compaq was analyzing openssl for
potential optimizations to boost it's
performance on Alpha.
The lack of rotate instructions seemed to
Is the SCSI card supported by SRM?
Didn't some PWS NT-only systems shipped
with SCSI adaptors known to be unsupported
by SRM?
...tom
-Original Message-
From: Joerg Hoh [mailto:[EMAIL PROTECTED]
Sent: Thursday, 27 March 2003 2:27 PM
To: debian-alpha@lists.debian.org
Subject: Re: question
I used the IDE interface. That's where SRM wasn't able
to help.
On Wed, 2003-02-26 at 02:23, Rob B wrote:
> At 02:33 AM 26/02/03, Thomas Evans sent this up the stick:
>
> >I was gonna say, I thought the Multia SRM wasn't capable
> >of booting linux - I had to us
I was gonna say, I thought the Multia SRM wasn't capable
of booting linux - I had to use ARC/MILO, which really
isn't a big deal.
...tom
-Original Message-
From: Ted S. Letofsky [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 25 February 2003 10:03 AM
To: Debian-Alpha
Cc: Mark T. Valites
Subjec
> > I get the error:
> > Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter)
> > serial 55936 error_code 9 request_code 132 minor_code 1
> >
> > when I run a few different GDK applications (gabber and gaim).
> > I'm running "stable" Debian 3.0 - is this problem on all
> > stable Deb
Hi All -
I get the error:
Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter)
serial 55936 error_code 9 request_code 132 minor_code 1
when I run a few different GDK applications (gabber and gaim).
I'm running "stable" Debian 3.0 - is this problem on all
stable Debian-supported arc
37 matches
Mail list logo
