Prev: ftrace,kdb: Extend kdb to be able to dump the ftrace buffer
Next: obsolete in kernel source (B43_LEGACY_RFKILL)
From: Norbert Preining on 15 Jan 2010 10:30
Dear all,

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.

Is there still anything else I can provide you for tracking that down.

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
------------------------------------------------------------------------
POGES (pl.n.)
The lumps of dry powder that remain after cooking a packet soup.
--- Douglas Adams, The Meaning of Liff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: reinette chatre on 15 Jan 2010 12:40
Hi Norbert,

On Fri, 2010-01-15 at 07:22 -0800, Norbert Preining 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.

>
> Is there still anything else I can provide you for tracking that down.

Can you try to boot without X and attempt a command line association
(using iw, iwconfig or wpa_supplicant) to reproduce?

Reinette


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Norbert Preining on 15 Jan 2010 21:40
On Fr, 15 Jan 2010, reinette chatre wrote:
> Can you try to boot without X and attempt a command line association
> (using iw, iwconfig or wpa_supplicant) to reproduce?

I try on Monday back at work.

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
------------------------------------------------------------------------
PIDDLETRENTHIDE (n.)
A trouser stain caused by a wimbledon (q.v.). Not to be confused with
a botley (q.v.)
--- Douglas Adams, The Meaning of Liff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Norbert Preining on 16 Jan 2010 13:40
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.

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
------------------------------------------------------------------------
LARGOWARD (n.)
Motorists' name for the kind of pedestrian who stands beside a main
road and waves on the traffic, as if it's their right of way.
--- Douglas Adams, The Meaning of Liff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: reinette chatre on 18 Jan 2010 12:10
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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 |  Next  |  Last
Pages: 1 2 3 4
Prev: ftrace,kdb: Extend kdb to be able to dump the ftrace buffer
Next: obsolete in kernel source (B43_LEGACY_RFKILL)