kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
To: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: hostap kernel lockup?
Date: Tue, 10 Jun 2008 08:24:44 +0100	[thread overview]
Message-ID: <g2la7s$g8r$1@ger.gmane.org> (raw)
In-Reply-To: g2760n$7f0$1@ger.gmane.org

Sitsofe Wheeler wrote:

> hostap_pci on a 32bit x86 machine seems to be unstable under load in
> next-20080604. Using iperf between a wired machine on the other side of
> the AP and the hostap box makes hostap output the message
> wifi0: SW TICK stuck? bits=0x0 EvStat=8000 IntEn=e09f
> before things slowly grind to a halt in a lockup that seemingly needs a
> sysrq reboot. This problem seems to be reproducible every time but does
> not happen with Ubuntu's 2.6.22 kernel.

This issue seems to be happening at least as far back as 2.6.22 vanilla with
the config on http://sucs.org/~sits/test/config-2.6.22.txt although things
always seem to be recoverable. Sometimes the system will recover after the
lockup with a message like:
Clocksource tsc unstable (delta = 9377016871 ns)
Time acpi_pm clocksource has been installed.
Unfortunately even after if this does happen supsequent runs can still
freeze things to the extent that caps lock will stop responding. It can get
to the stage where screen updates in X only seem to happen when a key is
pressed on the keyboard. 

-- 
Sitsofe | http://sucs.org/~sits/

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2008-06-10  7:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <g2760n$7f0$1@ger.gmane.org>
2008-06-10  7:24 ` Sitsofe Wheeler [this message]
2008-06-10 22:16   ` DEBUG_LOCK_ALLOC causes hostap kernel lockup Sitsofe Wheeler

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='g2la7s$g8r$1@ger.gmane.org' \
    --to=sitsofe-/e1597as9lqavxtiumwx3w@public.gmane.org \
    --cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).