All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] still same problem
Date: Sun, 18 Jan 2009 07:16:30 -0800	[thread overview]
Message-ID: <20090118151630.GQ29609@tesla> (raw)
In-Reply-To: <200901181034.03348.listsrv@wilsoft.nl>

On Sun, Jan 18, 2009 at 01:34:03AM -0800, W. van den Akker wrote:
> On Sunday 18 January 2009, Dmitri Seletski wrote:
> > W. van den Akker wrote:
> > > On Sunday 04 January 2009 10:58:02 Jens Ott - Opteamax wrote:
> > >> Hi,
> > >>
> > >> Luis R. Rodriguez schrieb:
> > >>> On Sat, Jan 3, 2009 at 5:53 PM, Barry Green <barry@lemonpi.net> wrote:
> > >>> [...]
> > >>> We need an oops trace of your crashes so far it seems you have not
> > >>> been able to get one, lets work on that. Until then it is not easy for
> > >>> us to provide you with patches to fix your issues.
> > >>
> > >> I also have similar problems with an D-LINK DWA-547 and I'd really like
> > >> to provide the oops trace, but unfortunately the machine seems to hang
> > >> that fast, that even no oops trace is shown. Also magic-sysreq don't
> > >> work anymore, neither via serial console nor via keyboard. Only chance I
> > >> have in this moment is to press reset-button, which already caused a
> > >> full xfs-filsystem-corruption with dataloss once :-(
> > >>
> > >> My problem is, that the hang happens not immediately after loading the
> > >> driver but "somewhen" while it is loaded.
> > >>
> > >> I have seen two types of crash:
> > >>
> > >> 1.) first investigations on my side seem to show that it happens, as
> > >> soon as there is high dataload transfered, but I don't have detailed
> > >> info yet.
> > >> 2.) Running hostapd works fine while started first time, but no client
> > >> is connected. When a client connects a system freeze occures
> > >> "sometimes". Reproducably the system freezes immediately when starting
> > >> hostapd, stop it and then restart hostapd. So every change in hostapd
> > >> conf needs a full reboot, unloading the ath9k module and reload it does
> > >> not prevent freeze, but after reboot I can start hostapd once without a
> > >> problem (only the metioned "sometime" freezes on client connect or high
> > >> data-volume).
> > >>
> > >> As this machine is productive, I suspended testing for now. I will
> > >> change the card into a non-productive environment in the next days. As
> > >> soon as I find more details, I'll report.
> > >>
> > >>> Please test with the latest drivers from
> > >>> wireless-testing/compat-wireless and restart in single user mode, we
> > >>> want to ensure X is not running at all and you are in a virtual
> > >>> terminal. We also do not want Network Manager or wpa_supplicant
> > >>> running in the background. To increase the resolution upon bootup try
> > >>> booting with vga=ask (vga=791 works well for me), then try to
> > >>> associate to your access point without encryption manually using
> > >>> iwconfig.
> > >>
> > >> Ok, that'll be a thing I'd need to test to, as in my case wpa_supplicant
> > >> is running.
> > >
> > > Hi,
> > >
> > > What is the status of your problem? I still have problems with it and
> > > have no progress...
> > >
> > > gr,
> > > Willem
> >
> > Hello Willem.
> >
> > I think I have had similar issue to yours.
> >
> > Car was working for short period of time and after a while crashed
> > computer. I was advised to change kernel version, i updated it to 2.6.27.9
> > and problem has gone away since.
> > It's something to do with DMA.
> >
> > Perhaps try to upgrade kernel?
> >
> > Regards
> > Dmitri
> 
> I have tried all kernel versions till 2.6.28 and still have the same hang-ups.
> I think indeed its a DMA-hardware-ath9k related problem.  The patch in
> 2.6.27.8 didnt work for me. I have filled a bugreport on bugzilla.kernel but
> because AP isnt supported untill 2.6.29 the report is closed.

A better description of this is that AP support does not work (is not allowed)
and therefore not supported on < 2.6.28.

> I will test today 2.6.29.rc2 and see if it has any progress.

You can also try wireless-testing (entire kernel) or compat-wireless (just updates
your wireless stuff) for bleeding edge stuff.

http://wireless.kernel.org/en/developers/Documentation/git-guide
http://wireless.kernel.org/en/users/Download

  Luis

  reply	other threads:[~2009-01-18 15:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04  1:26 [ath9k-devel] still same problem Dmitri Seletski
2009-01-04  1:53 ` Barry Green
2009-01-04  3:34   ` Luis R. Rodriguez
2009-01-04  9:58     ` Jens Ott - Opteamax
2009-01-05 16:09       ` Luis R. Rodriguez
2009-01-17 23:55       ` W. van den Akker
2009-01-18  1:41         ` Jens Ott - Opteamax
2009-01-18  9:14           ` W. van den Akker
2009-01-18  5:17         ` Dmitri Seletski
2009-01-18  9:34           ` W. van den Akker
2009-01-18 15:16             ` Luis R. Rodriguez [this message]
2009-01-19  8:35               ` W. van den Akker
2009-01-19 22:31               ` W. van den Akker
2009-01-20 17:48                 ` Luis R. Rodriguez
2009-01-20 18:32                   ` W. van den Akker
2009-01-20 22:22                   ` W. van den Akker
2009-01-20 23:08                     ` Chris Kennedy
2009-01-21  7:54                       ` W. van den Akker
2009-01-21 10:11                         ` W. van den Akker
2009-01-21 12:35                           ` Jouni Malinen
2009-01-21 17:01                             ` [ath9k-devel] [PATCH] " Chris Kennedy
2009-01-21 21:05                               ` W. van den Akker
2009-01-27  9:30                                 ` W. van den Akker
2009-01-27 21:47                                   ` Chris Kennedy
2009-01-21 17:15                             ` [ath9k-devel] " W. van den Akker
2009-01-21 10:17                         ` W. van den Akker
2009-01-04 10:33 ` W. van den Akker
2009-01-04 10:47   ` W. van den Akker

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=20090118151630.GQ29609@tesla \
    --to=lrodriguez@atheros.com \
    --cc=ath9k-devel@lists.ath9k.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.