The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Norbert Preining <preining@logic.at>
Cc: "ipw3945-devel@lists.sourceforge.net" 
	<ipw3945-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [ipw3945-devel] hang on 2.6.33-rc4
Date: Mon, 18 Jan 2010 09:06:53 -0800	[thread overview]
Message-ID: <1263834413.2751.644.camel@rc-desk> (raw)
In-Reply-To: <20100116183056.GA18769@gamma.logic.tuwien.ac.at>

On Sat, 2010-01-16 at 10:30 -0800, Norbert Preining wrote:
> On Fr, 15 Jan 2010, reinette chatre wrote:
> > > kernel 2.6.33-rc4
> > > 
> > > I am having repeatable complete hard lockups on my laptop with 2.6.33-rc4.
> > > 2.6.32.3 works fine.
> > > 
> > > I believe that it is related to the network, because sometimes I can
> > > actually log in (gnomes session) and as soon as I do some network
> > > related suddenly hard hang, not even Sysrq working anymore.
> > > 
> > > Interestingly it only happens at a specific AP where the ESSID is
> > > hidden (at work). At home I can work without any problems (ESSID not
> > > hidden).
> > > 
> > > Unfortunately I cannot set up a serial console or similar.
> > 
> > Does that mean no netconsole either? Does anything show up in the logs?
> > Is it easy to reproduce? If so, perhaps you can have increased debug at
> > that time and hopefully something will be captured in the logs when the
> > problem occurs.
> 
> Before I can test this on monday, something else, I just got BUG_ON:
> Jan 17 03:28:58 mithrandir kernel: [34535.207253] iwlagn 0000:06:00.0: iwl_tx_agg_start on ra = 00:0a:79:eb:56:10 tid = 0
> Jan 17 03:28:58 mithrandir kernel: [34535.331218] iwlagn 0000:06:00.0: BUG_ON idx doesn't match seq control idx=139, seq_idx=3435, seq=54960
> Jan 17 03:28:58 mithrandir kernel: [34535.331275] iwlagn 0000:06:00.0: Received BA when not expected
> Jan 17 03:28:58 mithrandir kernel: [34535.331816] iwlagn 0000:06:00.0: BUG_ON idx doesn't match seq control idx=146, seq_idx=3442, seq=55072
> Jan 17 03:28:58 mithrandir kernel: [34535.331915] iwlagn 0000:06:00.0: Received BA when not expected
> Jan 17 03:28:58 mithrandir kernel: [34535.332419] iwlagn 0000:06:00.0: BUG_ON idx doesn't match seq control idx=170, seq_idx=3466, seq=55456
> 
> Actually many many many of these lines.
> 

What you are seeing here is currently being looked into at
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2098 - could you
please add your information there?

Reinette



  reply	other threads:[~2010-01-18 17:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 15:22 hang on 2.6.33-rc4 Norbert Preining
2010-01-15 17:29 ` [ipw3945-devel] " reinette chatre
2010-01-16  2:30   ` Norbert Preining
2010-01-16 18:30   ` Norbert Preining
2010-01-18 17:06     ` reinette chatre [this message]
2010-01-18 17:19       ` Norbert Preining
2010-01-19  5:47   ` Norbert Preining
2010-01-19 17:01     ` reinette chatre
2010-01-19 17:59       ` Johannes Berg
2010-01-20  0:36         ` Norbert Preining
2010-01-20  9:52           ` Johannes Berg
2010-01-20  9:32     ` Zhu Yi
2010-01-21  0:28       ` Norbert Preining
2010-01-21 18:18         ` John Ranson
2010-01-27 15:37       ` Norbert Preining
2010-01-27 16:54         ` reinette chatre
2010-01-28  8:41           ` Norbert Preining
2010-01-28 16:23             ` reinette chatre

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=1263834413.2751.644.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preining@logic.at \
    /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