Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Ryan Bradetich <rbradetich@uswest.net>
To: Jeremy Drake <jeremyd@apptechsys.com>
Cc: parisc-linux@lists.parisc-linux.org, richard_hirst@linuxcare.com
Subject: Re: [parisc-linux] Unaligned access failures with apt-get on SMP K460.
Date: 16 Jun 2002 21:37:56 -0600	[thread overview]
Message-ID: <1024285076.8850.36.camel@beavis> (raw)
In-Reply-To: <Pine.LNX.4.44.0206162014520.24659-100000@garibaldi.apptechsys.com>

Hello Jeremy,

The SMP problem is what I am trying to debug.  I am running SMP cvs head
on the J200 and the K460 and also an A500 recently thanks to the ESIEE
team.  The K460 has 4 processors which I am hoping will help to identify
the SMP problems faster, but it is also exposing new SMP problems for me
to look into :(

Hopefully we will be able to identify and fix these SMP problems, but
they do not appear to be easy and will probably take a while to fix.

Thanks for the report! and if you notice anything else odd (or
repeatable patterns) let me and/or the list know so maybe it will
provide additional insights into the problems.

Thanks,

- Ryan

On Sun, 2002-06-16 at 21:19, Jeremy Drake wrote:
> On 16 Jun 2002, Ryan Bradetich wrote:
> 
> > Hello parisc-linux hackers,
> > 
> > I (with a lot of help from Richard) am  looking into a problem with
> > apt-get .... on a SMP kernel for the K460. 
> > 
> > The problem is that when I run apt-get <command> I get the following
> > error message:
> > 	apt-get(<PID>): unaligned access to 0x403ce094 at ip=0x4005e47f
> > 
> I get stuff like this on my J5000, only it locks up and/or HPMC's when it 
> does it.  (Sometimes prints HPMC info to the LCD, sometimes not, but 
> always locks up).
> 
> I try to keep up-to-date with the cvs kernels, and I try it on SMP every 
> now and then, but I generally run this box under UP and it is very stable.  
> I started having problems with this box when the latest 2.4.17-32-smp was 
> released.  With the previous one, this box was stable under SMP.  (this 
> was before I got the courage to build my own kernels on parisc).  Not sure 
> what versions in cvs this corresponds to, but maybe some change between 
> caused the problem.
> 
> Not sure if this is the same problem you are encountering, because Samba 
> also tends to lock this box up, and if I leave it alone, it just crashes 
> itself later...
> 
> 
> -- 
> Troubled day for virgins over 16 who are beautiful and wealthy and live
> in eucalyptus trees.
> 
> 

  reply	other threads:[~2002-06-17  3:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17  0:22 [parisc-linux] Unaligned access failures with apt-get on SMP K460 Ryan Bradetich
2002-06-17  0:59 ` John David Anglin
2002-06-17  2:31   ` John David Anglin
2002-06-17  3:04     ` Ryan Bradetich
2002-06-17  4:12       ` [parisc-linux] Unaligned access failures with apt-get on SMP John David Anglin
2002-06-17 20:43         ` Ryan Bradetich
2002-06-17 22:11           ` John David Anglin
2002-06-17  3:19 ` [parisc-linux] Unaligned access failures with apt-get on SMP K460 Jeremy Drake
2002-06-17  3:37   ` Ryan Bradetich [this message]
2002-06-17  4:45     ` Jeremy Drake

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=1024285076.8850.36.camel@beavis \
    --to=rbradetich@uswest.net \
    --cc=jeremyd@apptechsys.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=richard_hirst@linuxcare.com \
    /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