From: Wolfgang Grandegger <wg@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Kernel lockup with lapic on old AMD Athlon
Date: Sun, 25 Feb 2007 16:09:52 +0100 [thread overview]
Message-ID: <45E1A6C0.6030908@domain.hid> (raw)
In-Reply-To: <17889.38390.369037.176076@domain.hid>
Gilles Chanteperdrix wrote:
> Wolfgang Grandegger wrote:
> > Hello,
> >
> > here is the boot log of an hangup of 2.6.20 with I-pipe 1.7-02 and
> > Xenomai todays trunk. I already reported this hangup a while ago but now
> > I get an oops. At that time Gilles said that lapic on old Athlons might
> > be buggy. Does the attached boot log confirm this assumption? 2.6.20-rt8
> > is working, BTW.
>
> What I had observed with an old Athlon were some random lockups. I was
> trying to setup a samba print server at the time, and the lockup always
> occured when some windows machine was trying to use the shared printer
> through network. I think the IO-APIC was also enabled. Then, at some
> later time, I read somewhere on the internet that the IO-APIC or LAPIC
> could be buggy on some Athlons, so I understood what had happened to
> me. So, I did not investigate this issue any further.
I didn't either, especially because it works with lapic disabled in the
kernel config. I just thought that this oops might be useful to somebody.
Wolfgang.
next prev parent reply other threads:[~2007-02-25 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 10:25 [Xenomai-core] Kernel lockup with lapic on old AMD Athlon Wolfgang Grandegger
2007-02-25 13:58 ` Gilles Chanteperdrix
2007-02-25 15:09 ` Wolfgang Grandegger [this message]
2007-02-25 22:03 ` Philippe Gerum
2007-02-26 9:08 ` Wolfgang Grandegger
2007-02-26 14:09 ` Philippe Gerum
2007-02-26 14:54 ` Wolfgang Grandegger
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=45E1A6C0.6030908@domain.hid \
--to=wg@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.