From: Norbert Preining <preining@logic.at>
To: reinette chatre <reinette.chatre@intel.com>
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 18:19:03 +0100 [thread overview]
Message-ID: <20100118171903.GT3150@gamma.logic.tuwien.ac.at> (raw)
In-Reply-To: <1263834413.2751.644.camel@rc-desk>
Hi Reinette,
On Mo, 18 Jan 2010, reinette chatre wrote:
> > > 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.
I tried it today, but had "real work" (university job) to do. It worked
and I found out that it happend (up to now) *NOT* when I was only doing
a ping on a server, but when I ssh-ed into my server it hang.
More testing tomorrow (here it is already 2am).
BTW, logs were empty, unfortunately, complete hard hang.
> > 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?
I did that, although I was not sure what information to provide.
Best wishes
Norbert
------------------------------------------------------------------------
Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
THURNBY (n.)
A rucked-up edge of carpet or linoleum which everyone says someone
will trip over and break a leg unless it gets fixed. After a year or
two someone trips over it and breaks a leg.
--- Douglas Adams, The Meaning of Liff
next prev parent reply other threads:[~2010-01-18 17:19 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
2010-01-18 17:19 ` Norbert Preining [this message]
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=20100118171903.GT3150@gamma.logic.tuwien.ac.at \
--to=preining@logic.at \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.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;
as well as URLs for NNTP newsgroup(s).