From: dann frazier <dannf@dannf.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Bart Schelstraete <bart@schelstraete.org>,
HPPA porters <debian-hppa@lists.debian.org>,
Debian Release <debian-release@lists.debian.org>,
admin@debian-ports.org, linux-parisc@vger.kernel.org
Subject: Re: HPPA and Squeeze
Date: Fri, 12 Jun 2009 09:35:45 -0600 [thread overview]
Message-ID: <20090612153544.GA27867@lackof.org> (raw)
In-Reply-To: <1244816185.4184.3.camel@mulgrave.site>
On Fri, Jun 12, 2009 at 09:16:25AM -0500, James Bottomley wrote:
> On Fri, 2009-06-12 at 09:55 +0200, Bart Schelstraete wrote:
> > Hello all,
> >
> > Everybody is talking about the 'random crashes' and 'segfaults' in
> > the HPPA version.
> > Over here I'm using the hppa on a small HP-UX workstation, and that
> > has an uptime of 542 days!.
> > So it's not that unstable.
> > I even need to say that I had a lot more crashes with the x86 version
> > then with the hppa version.
>
> It seems to be related to what machine you actually have.
And the load - buildds for unstable seem to trip over issues that we
don't see elsewhere.
> I run a B180
> as my network gateway, handling firewall, web,
> postfix/postgrey/spamassassin at quite a high volume on a domain. I
> also used to run it with a PCMCIA wireless card just for chuckles and
> grins (although I stopped that two years ago when I got a linksys). It
> runs debian testing and has been completely stable. I only reboot it
> for updates and in the seven or so years I've been doing this, I haven't
> had any segfaults or crashes ... have to say I only started using debian
> kernels on it for the last four or so years, because there used to be
> big problems with the ones they built.
>
> > Just to say that I'm personally not so unhappy with deb hppa, and
> > that not everything is bad.
>
> I think the main class of problem machines are anything with SMP ...
> unfortunately, I don't have one, so can't verify.
We've tried both SMP and non-SMP kernels.
--
dann frazier
next prev parent reply other threads:[~2009-06-12 15:35 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090602140734.GC26721@mx0.halon.org.uk>
2009-06-06 18:36 ` HPPA and Squeeze Grant Grundler
2009-06-08 21:26 ` Neil McGovern
2009-06-08 23:44 ` Thibaut VARENE
2009-06-09 9:29 ` Neil McGovern
2009-06-09 10:38 ` Thomas Bogendoerfer
2009-06-09 16:47 ` Aioanei Rares
2009-06-09 17:06 ` John David Anglin
[not found] ` <slrnh2scj5.720.nospam@sshway.ssh.pusling.com>
2009-06-09 19:11 ` Helge Deller
2009-06-17 2:37 ` John David Anglin
2009-06-15 16:26 ` Grant Grundler
2009-06-15 17:32 ` Helge Deller
2009-06-12 6:49 ` Luk Claes
2009-06-12 7:53 ` Bart Schelstraete
2009-06-12 7:55 ` Bart Schelstraete
2009-06-12 14:16 ` James Bottomley
2009-06-12 15:35 ` dann frazier [this message]
2009-06-13 12:19 ` Brian Szymanski
2009-06-14 18:29 ` Thibaut VARENE
2009-06-14 18:39 ` dann frazier
2009-06-15 17:31 ` Grant Grundler
2009-06-16 6:25 ` Lucas Nussbaum
2009-06-16 19:08 ` Helge Deller
2009-06-16 19:13 ` Aurelien Jarno
2009-06-17 11:14 ` Carlos O'Donell
2009-06-21 22:55 ` Carlos O'Donell
2009-07-12 12:30 ` Aurelien Jarno
2009-07-12 14:52 ` Carlos O'Donell
2009-07-13 13:30 ` Carlos O'Donell
2009-06-16 20:50 ` Grant Grundler
2009-06-16 21:35 ` dann frazier
2009-06-17 23:54 ` Matthias Klose
2009-06-18 1:35 ` John David Anglin
2009-06-18 6:33 ` Luk Claes
2009-06-18 9:40 ` Randolph Chung
2009-06-18 18:19 ` Luk Claes
2009-06-18 10:16 ` Thibaut VARENE
2009-06-18 18:16 ` Luk Claes
2009-06-18 15:03 ` John David Anglin
2009-06-18 6:29 ` Luk Claes
2009-06-24 23:32 ` Matthias Klose
2009-06-19 6:05 Luk Claes
2009-06-19 15:15 ` Kurt Roeckx
2009-06-19 15:43 ` Philipp Kern
2009-06-20 22:44 ` John David Anglin
2009-07-03 18:57 ` Kurt Roeckx
2009-07-03 19:28 ` Philipp Kern
2009-07-03 22:15 ` Kurt Roeckx
2009-07-04 23:34 ` John David Anglin
2009-07-05 9:06 ` Helge Deller
2009-07-05 13:44 ` Jurij Smakov
2009-07-05 14:01 ` Philipp Kern
2009-07-05 17:19 ` John David Anglin
2009-07-05 18:01 ` John David Anglin
2009-07-05 23:07 ` John David Anglin
2009-07-06 0:03 ` Carlos O'Donell
2009-07-06 0:17 ` John David Anglin
2009-07-06 1:06 ` James Bottomley
2009-07-06 1:43 ` John David Anglin
2009-07-06 5:38 ` Randolph Chung
2009-07-06 13:28 ` John David Anglin
2009-07-06 16:36 ` Carlos O'Donell
2009-07-06 18:45 ` John David Anglin
2009-07-06 21:43 ` Kyle McMartin
2009-07-07 1:47 ` John David Anglin
2009-07-07 2:43 ` dann frazier
2009-07-07 13:57 ` Carlos O'Donell
2009-07-07 14:11 ` James Bottomley
2009-07-07 16:21 ` John David Anglin
2009-07-07 20:42 ` Carlos O'Donell
2009-07-07 22:07 ` John David Anglin
2009-07-07 22:17 ` Carlos O'Donell
2009-07-07 22:39 ` John David Anglin
2009-07-07 14:22 ` James Bottomley
2009-07-05 23:59 ` Carlos O'Donell
2009-07-06 2:25 ` John David Anglin
2009-07-04 19:52 ` John David Anglin
2009-07-04 21:03 ` Kurt Roeckx
2009-07-04 23:30 ` Kurt Roeckx
2009-06-20 14:33 ` Kurt Roeckx
2009-06-20 16:02 ` John David Anglin
2009-06-20 17:48 ` Kurt Roeckx
2009-06-20 21:57 ` Grant Grundler
2009-06-20 22:25 ` John David Anglin
2009-06-20 23:07 ` Grant Grundler
2009-06-20 23:25 ` John David Anglin
2009-06-20 14:39 ` Kurt Roeckx
2009-06-20 14:51 ` Thibaut VARENE
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090612153544.GA27867@lackof.org \
--to=dannf@dannf.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=admin@debian-ports.org \
--cc=bart@schelstraete.org \
--cc=debian-hppa@lists.debian.org \
--cc=debian-release@lists.debian.org \
--cc=linux-parisc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox