[Bug #13819] system freeze when switching to console

[Bug #13819] system freeze when switching to console

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
Subject		: system freeze when switching to console
Submitter	: Reinette Chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-23 17:57 (4 days old)

[Bug #13819] system freeze when switching to console

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
Subject		: system freeze when switching to console
Submitter	: Reinette Chatre <reinette.chatre@intel.com>
Date		: 2009-07-23 17:57 (11 days old)

[Bug #13819] system freeze when switching to console

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
Subject		: system freeze when switching to console
Submitter	: Reinette Chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-23 17:57 (18 days old)

2.6.31-rc6-git5: Reported regressions from 2.6.30

[Rafael J. Wysocki]

This message contains a list of some regressions from 2.6.30, for which there
are no fixes in the mainline I know of.  If any of them have been fixed already,
please let me know.

If you know of any other unresolved regressions from 2.6.30, please let me know
either and I'll add them to the list.  Also, please let me know if any of the
entries below are invalid.

Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2009-08-20      102       32          29
  2009-08-10       89       27          24
  2009-08-02       76       36          28
  2009-07-27       70       51          43
  2009-07-07       35       25          21
  2009-06-29       22       22          15


Unresolved regressions
----------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14018
Subject		: kernel freezes, inotify problem
Submitter	: Christoph Thielecke <christoph.thielecke-Mmb7MZpHnFY@public.gmane.org>
Date		: 2009-08-19 12:48 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=125068616818353&w=4
Handled-By	: Eric Paris <eparis-FjpueFixGhCM4zKIHC2jIg@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14016
Subject		: mm/ipw2200 regression
Submitter	: Bartlomiej Zolnierkiewicz <bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-08-15 16:56 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=125036437221408&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14015
Subject		: pty regressed again, breaking expect and gcc's testsuite
Submitter	: Mikael Pettersson <mikpe-1zs4UD6AkMk@public.gmane.org>
Date		: 2009-08-14 23:41 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=125029329805643&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14014
Subject		: kernel bug at shut down
Submitter	: Norbert Preining <preining-DX+603jRYB8@public.gmane.org>
Date		: 2009-08-14 9:11 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=125024112418870&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14013
Subject		: hd don't show up
Submitter	: Tim Blechmann <tim-xpEK/MU0Hawdnm+yROfE0A@public.gmane.org>
Date		: 2009-08-14 8:26 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=125023842514480&w=4
Handled-By	: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14012
Subject		: latest git fried my x86_64 imac
Submitter	: Justin P. Mattock <justinmattock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-08-13 07:20 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=125014080427090&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14011
Subject		: Kernel paging request failed in kmem_cache_alloc
Submitter	: Matthias Dahl <ml_kernel-Rk1lLwyeSiSCvTm3UDtA3g@public.gmane.org>
Date		: 2009-08-10 22:26 (10 days old)
References	: http://marc.info/?l=linux-kernel&m=124993603825082&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14003
Subject		: Infinite loop on bootup while handling DMAR
Submitter	: Bernhard Rosenkraenzer <bero-9zdaV+82baBg9hUCZPvPmw@public.gmane.org>
Date		: 2009-08-18 14:54 (2 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14002
Subject		: WARNING: at net/ipv4/af_inet.c:154 inet_sock_destruct+0x164/0x1c0()
Submitter	: Ralf Hildebrandt <ralf.hildebrandt-jq1tPX9l7E6ELgA04lAiVw@public.gmane.org>
Date		: 2009-08-18 12:37 (2 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13987
Subject		: Received NMI interrupt at resume
Submitter	: Christian Casteyde <casteyde.christian-GANU6spQydw@public.gmane.org>
Date		: 2009-08-15 07:55 (5 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13960
Subject		: rtl8187 not connect to wifi
Submitter	: okias <d.okias-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-08-10 19:16 (10 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13950
Subject		: Oops when USB Serial disconnected while in use
Submitter	: Bruno Prémont <bonbons-ud5FBsm0p/xEiooADzr8i9i2O/JbrIOy@public.gmane.org>
Date		: 2009-08-08 17:47 (12 days old)
References	: http://marc.info/?l=linux-kernel&m=124975432900466&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13947
Subject		: Libertas: Association request to the driver failed
Submitter	: Daniel Mack <daniel-rDUAYElUppE@public.gmane.org>
Date		: 2009-08-07 19:11 (13 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=57921c312e8cef72ba35a4cfe870b376da0b1b87
References	: http://marc.info/?l=linux-kernel&m=124967234311481&w=4
Handled-By	: Roel Kluin <roel.kluin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13943
Subject		: WARNING: at net/mac80211/mlme.c:2292 with ath5k
Submitter	: Fabio Comolli <fabio.comolli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-08-06 20:15 (14 days old)
References	: http://marc.info/?l=linux-kernel&m=124958978600600&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13942
Subject		: Troubles with AoE and uninitialized object
Submitter	: Bruno Prémont <bonbons-ud5FBsm0p/xEiooADzr8i9i2O/JbrIOy@public.gmane.org>
Date		: 2009-08-04 10:12 (16 days old)
References	: http://marc.info/?l=linux-kernel&m=124938117104811&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13941
Subject		: x86 Geode issue
Submitter	: Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>
Date		: 2009-08-03 12:58 (17 days old)
References	: http://marc.info/?l=linux-kernel&m=124930434732481&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13940
Subject		: iwlagn and sky2 stopped working, ACPI-related
Submitter	: Ricardo Jorge da Fonseca Marques Ferreira <storm@sys49152.net>
Date		: 2009-08-07 22:33 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=124968457731107&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13935
Subject		: 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)
Submitter	: Adrian Ulrich <kernel-4ZM2p5qjiQGewZBzVTKGGg@public.gmane.org>
Date		: 2009-08-08 22:08 (12 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fa047e4f6fa63a6e9d0ae4d7749538830d14a343


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13914
Subject		: e1000e reports invalid NVM Checksum on 82566DM-2 (bisected)
Submitter	:  <jsbronder-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Date		: 2009-08-04 18:06 (16 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13906
Subject		: Huawei E169 GPRS connection causes Ooops
Submitter	: Clemens Eisserer <linuxhippy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-08-04 09:02 (16 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13899
Subject		: Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.
Submitter	: Gene Heskett <gene.heskett-H+0wwilmMs3R7s880joybQ@public.gmane.org>
Date		: 2009-08-01 13:04 (19 days old)
References	: http://marc.info/?l=linux-kernel&m=124913190304149&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13869
Subject		: Radeon framebuffer (w/o KMS) corruption at boot.
Submitter	: Duncan <1i5t5.duncan-j9pdmedNgrk@public.gmane.org>
Date		: 2009-07-29 16:44 (22 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13848
Subject		: iwlwifi (4965) regression since 2.6.30
Submitter	: Lukas Hejtmanek <xhejtman-8qz54MUs51PtwjQa/ONI9g@public.gmane.org>
Date		: 2009-07-26 7:57 (25 days old)
References	: http://marc.info/?l=linux-kernel&m=124859658502866&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13836
Subject		: suspend script fails, related to stdout?
Submitter	: Tomas M. <tmezzadra-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-17 21:24 (34 days old)
References	: http://marc.info/?l=linux-kernel&m=124785853811667&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
Subject		: system freeze when switching to console
Submitter	: Reinette Chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-23 17:57 (28 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13809
Subject		: oprofile: possible circular locking dependency detected
Submitter	: Jerome Marchand <jmarchan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date		: 2009-07-22 13:35 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13740
Subject		: X server crashes with 2.6.31-rc2 when options are changed
Submitter	: Michael S. Tsirkin <m.s.tsirkin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-07 15:19 (44 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13733
Subject		: 2.6.31-rc2: irq 16: nobody cared
Submitter	: Niel Lambrechts <niel.lambrechts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-06 18:32 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=124690524027166&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13645
Subject		: NULL pointer dereference at (null) (level2_spare_pgt)
Submitter	: poornima nayak <mpnayak-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Date		: 2009-06-17 17:56 (64 days old)
References	: http://lkml.org/lkml/2009/6/17/194


Regressions with patches
------------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14017
Subject		: _end symbol missing from Symbol.map
Submitter	: Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>
Date		: 2009-08-13 6:45 (7 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=091e52c3551d3031343df24b573b770b4c6c72b6
References	: http://marc.info/?l=linux-kernel&m=125014649102253&w=4
Handled-By	: Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=125014649102253&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13948
Subject		: ath5k broken after suspend-to-ram
Submitter	: Johannes Stezenbach <js-FF7aIK3TAVNeoWH0uzbU5w@public.gmane.org>
Date		: 2009-08-07 21:51 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=124968192727854&w=4
Handled-By	: Nick Kossifidis <mickflemm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch		: http://patchwork.kernel.org/patch/38550/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13946
Subject		: x86 MCE malfunction on Thinkpad T42p
Submitter	: Johannes Stezenbach <js-FF7aIK3TAVNeoWH0uzbU5w@public.gmane.org>
Date		: 2009-08-07 17:09 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=124966500232399&w=4
Handled-By	: Bartlomiej Zolnierkiewicz <bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch		: http://patchwork.kernel.org/patch/37908/


For details, please visit the bug entries and follow the links given in
references.

As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions from 2.6.30,
unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=13615

Please let me know if there are any Bugzilla entries that should be added to
the list in there.

Thanks,
Rafael

[Bug #13645] NULL pointer dereference at (null) (level2_spare_pgt)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13645
Subject		: NULL pointer dereference at (null) (level2_spare_pgt)
Submitter	: poornima nayak <mpnayak@linux.vnet.ibm.com>
Date		: 2009-06-17 17:56 (64 days old)
References	: http://lkml.org/lkml/2009/6/17/194

[Bug #13733] 2.6.31-rc2: irq 16: nobody cared

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13733
Subject		: 2.6.31-rc2: irq 16: nobody cared
Submitter	: Niel Lambrechts <niel.lambrechts@gmail.com>
Date		: 2009-07-06 18:32 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=124690524027166&w=4

[Bug #13740] X server crashes with 2.6.31-rc2 when options are changed

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13740
Subject		: X server crashes with 2.6.31-rc2 when options are changed
Submitter	: Michael S. Tsirkin <m.s.tsirkin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-07 15:19 (44 days old)

[Bug #13809] oprofile: possible circular locking dependency detected

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13809
Subject		: oprofile: possible circular locking dependency detected
Submitter	: Jerome Marchand <jmarchan@redhat.com>
Date		: 2009-07-22 13:35 (29 days old)

[Bug #13836] suspend script fails, related to stdout?

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13836
Subject		: suspend script fails, related to stdout?
Submitter	: Tomas M. <tmezzadra-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-17 21:24 (34 days old)
References	: http://marc.info/?l=linux-kernel&m=124785853811667&w=4

[Bug #13819] system freeze when switching to console

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
Subject		: system freeze when switching to console
Submitter	: Reinette Chatre <reinette.chatre@intel.com>
Date		: 2009-07-23 17:57 (28 days old)

[Bug #13848] iwlwifi (4965) regression since 2.6.30

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13848
Subject		: iwlwifi (4965) regression since 2.6.30
Submitter	: Lukas Hejtmanek <xhejtman-8qz54MUs51PtwjQa/ONI9g@public.gmane.org>
Date		: 2009-07-26 7:57 (25 days old)
References	: http://marc.info/?l=linux-kernel&m=124859658502866&w=4

[Bug #13899] Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13899
Subject		: Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.
Submitter	: Gene Heskett <gene.heskett@verizon.net>
Date		: 2009-08-01 13:04 (19 days old)
References	: http://marc.info/?l=linux-kernel&m=124913190304149&w=4

[Bug #13906] Huawei E169 GPRS connection causes Ooops

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13906
Subject		: Huawei E169 GPRS connection causes Ooops
Submitter	: Clemens Eisserer <linuxhippy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-08-04 09:02 (16 days old)

[Bug #13869] Radeon framebuffer (w/o KMS) corruption at boot.

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13869
Subject		: Radeon framebuffer (w/o KMS) corruption at boot.
Submitter	: Duncan <1i5t5.duncan-j9pdmedNgrk@public.gmane.org>
Date		: 2009-07-29 16:44 (22 days old)

[Bug #13935] 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13935
Subject		: 2.6.31-rcX breaks Apple MightyMouse (Bluetooth version)
Submitter	: Adrian Ulrich <kernel@blinkenlights.ch>
Date		: 2009-08-08 22:08 (12 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fa047e4f6fa63a6e9d0ae4d7749538830d14a343

[Bug #13914] e1000e reports invalid NVM Checksum on 82566DM-2 (bisected)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13914
Subject		: e1000e reports invalid NVM Checksum on 82566DM-2 (bisected)
Submitter	:  <jsbronder-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Date		: 2009-08-04 18:06 (16 days old)

[Bug #13940] iwlagn and sky2 stopped working, ACPI-related

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13940
Subject		: iwlagn and sky2 stopped working, ACPI-related
Submitter	: Ricardo Jorge da Fonseca Marques Ferreira <storm@sys49152.net>
Date		: 2009-08-07 22:33 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=124968457731107&w=4

[Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13941
Subject		: x86 Geode issue
Submitter	: Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>
Date		: 2009-08-03 12:58 (17 days old)
References	: http://marc.info/?l=linux-kernel&m=124930434732481&w=4

[Bug #13942] Troubles with AoE and uninitialized object

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13942
Subject		: Troubles with AoE and uninitialized object
Submitter	: Bruno Prémont <bonbons-ud5FBsm0p/xEiooADzr8i9i2O/JbrIOy@public.gmane.org>
Date		: 2009-08-04 10:12 (16 days old)
References	: http://marc.info/?l=linux-kernel&m=124938117104811&w=4

[Bug #13943] WARNING: at net/mac80211/mlme.c:2292 with ath5k

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13943
Subject		: WARNING: at net/mac80211/mlme.c:2292 with ath5k
Submitter	: Fabio Comolli <fabio.comolli@gmail.com>
Date		: 2009-08-06 20:15 (14 days old)
References	: http://marc.info/?l=linux-kernel&m=124958978600600&w=4

[Bug #13946] x86 MCE malfunction on Thinkpad T42p

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13946
Subject		: x86 MCE malfunction on Thinkpad T42p
Submitter	: Johannes Stezenbach <js@sig21.net>
Date		: 2009-08-07 17:09 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=124966500232399&w=4
Handled-By	: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Patch		: http://patchwork.kernel.org/patch/37908/

[Bug #13947] Libertas: Association request to the driver failed

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13947
Subject		: Libertas: Association request to the driver failed
Submitter	: Daniel Mack <daniel@caiaq.de>
Date		: 2009-08-07 19:11 (13 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=57921c312e8cef72ba35a4cfe870b376da0b1b87
References	: http://marc.info/?l=linux-kernel&m=124967234311481&w=4
Handled-By	: Roel Kluin <roel.kluin@gmail.com>

[Bug #13950] Oops when USB Serial disconnected while in use

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13950
Subject		: Oops when USB Serial disconnected while in use
Submitter	: Bruno Prémont <bonbons@linux-vserver.org>
Date		: 2009-08-08 17:47 (12 days old)
References	: http://marc.info/?l=linux-kernel&m=124975432900466&w=4

[Bug #13948] ath5k broken after suspend-to-ram

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13948
Subject		: ath5k broken after suspend-to-ram
Submitter	: Johannes Stezenbach <js-FF7aIK3TAVNeoWH0uzbU5w@public.gmane.org>
Date		: 2009-08-07 21:51 (13 days old)
References	: http://marc.info/?l=linux-kernel&m=124968192727854&w=4
Handled-By	: Nick Kossifidis <mickflemm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch		: http://patchwork.kernel.org/patch/38550/

[Bug #13960] rtl8187 not connect to wifi

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13960
Subject		: rtl8187 not connect to wifi
Submitter	: okias <d.okias-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-08-10 19:16 (10 days old)

[Bug #14003] Infinite loop on bootup while handling DMAR

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14003
Subject		: Infinite loop on bootup while handling DMAR
Submitter	: Bernhard Rosenkraenzer <bero-9zdaV+82baBg9hUCZPvPmw@public.gmane.org>
Date		: 2009-08-18 14:54 (2 days old)

[Bug #14011] Kernel paging request failed in kmem_cache_alloc

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14011
Subject		: Kernel paging request failed in kmem_cache_alloc
Submitter	: Matthias Dahl <ml_kernel@mortal-soul.de>
Date		: 2009-08-10 22:26 (10 days old)
References	: http://marc.info/?l=linux-kernel&m=124993603825082&w=4

[Bug #13987] Received NMI interrupt at resume

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13987
Subject		: Received NMI interrupt at resume
Submitter	: Christian Casteyde <casteyde.christian-GANU6spQydw@public.gmane.org>
Date		: 2009-08-15 07:55 (5 days old)

[Bug #14002] WARNING: at net/ipv4/af_inet.c:154 inet_sock_destruct+0x164/0x1c0()

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14002
Subject		: WARNING: at net/ipv4/af_inet.c:154 inet_sock_destruct+0x164/0x1c0()
Submitter	: Ralf Hildebrandt <ralf.hildebrandt-jq1tPX9l7E6ELgA04lAiVw@public.gmane.org>
Date		: 2009-08-18 12:37 (2 days old)

[Bug #14012] latest git fried my x86_64 imac

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14012
Subject		: latest git fried my x86_64 imac
Submitter	: Justin P. Mattock <justinmattock@gmail.com>
Date		: 2009-08-13 07:20 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=125014080427090&w=4

[Bug #14016] mm/ipw2200 regression

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14016
Subject		: mm/ipw2200 regression
Submitter	: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Date		: 2009-08-15 16:56 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=125036437221408&w=4

[Bug #14014] kernel bug at shut down

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14014
Subject		: kernel bug at shut down
Submitter	: Norbert Preining <preining-DX+603jRYB8@public.gmane.org>
Date		: 2009-08-14 9:11 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=125024112418870&w=4

[Bug #14013] hd don't show up

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14013
Subject		: hd don't show up
Submitter	: Tim Blechmann <tim@klingt.org>
Date		: 2009-08-14 8:26 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=125023842514480&w=4
Handled-By	: Tejun Heo <tj@kernel.org>

[Bug #14015] pty regressed again, breaking expect and gcc's testsuite

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14015
Subject		: pty regressed again, breaking expect and gcc's testsuite
Submitter	: Mikael Pettersson <mikpe-1zs4UD6AkMk@public.gmane.org>
Date		: 2009-08-14 23:41 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=125029329805643&w=4

[Bug #14017] _end symbol missing from Symbol.map

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14017
Subject		: _end symbol missing from Symbol.map
Submitter	: Hannes Reinecke <hare@suse.de>
Date		: 2009-08-13 6:45 (7 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=091e52c3551d3031343df24b573b770b4c6c72b6
References	: http://marc.info/?l=linux-kernel&m=125014649102253&w=4
Handled-By	: Hannes Reinecke <hare@suse.de>
Patch		: http://marc.info/?l=linux-kernel&m=125014649102253&w=4

[Bug #14018] kernel freezes, inotify problem

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14018
Subject		: kernel freezes, inotify problem
Submitter	: Christoph Thielecke <christoph.thielecke@gmx.de>
Date		: 2009-08-19 12:48 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=125068616818353&w=4
Handled-By	: Eric Paris <eparis@parisplace.org>

Re: [Bug #13819] system freeze when switching to console

[reinette chatre]

On Wed, 2009-08-19 at 13:26 -0700, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
> Subject		: system freeze when switching to console
> Submitter	: Reinette Chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Date		: 2009-07-23 17:57 (28 days old)

This issue is still present in 2.6.31-rc6. Unfortunately the patches I
reverted to get a working system does not revert cleanly anymore.

Reinette

Re: [Bug #13940] iwlagn and sky2 stopped working, ACPI-related

[Ricardo Jorge da Fonseca Marques Ferreira]

Yes, 2.6.31-rc6 still has the bug.

On Wednesday 19 August 2009, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13940
> Subject		: iwlagn and sky2 stopped working, ACPI-related
> Submitter	: Ricardo Jorge da Fonseca Marques Ferreira <storm-cOTmPFJTJjbk1uMJSBkQmQ@public.gmane.org>
> Date		: 2009-08-07 22:33 (13 days old)
> References	: http://marc.info/?l=linux-kernel&m=124968457731107&w=4
> 

Re: [Bug #13899] Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.

[Gene Heskett]

On Wednesday 19 August 2009, Rafael J. Wysocki wrote:
>This message has been generated automatically as a part of a report
>of recent regressions.
>
>The following bug entry is on the current list of known regressions
>from 2.6.30.  Please verify if it still should be listed and let me know
>(either way).
>
>
>Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13899
>Subject		: Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.
>Submitter	: Gene Heskett <gene.heskett-H+0wwilmMs3R7s880joybQ@public.gmane.org>
>Date		: 2009-08-01 13:04 (19 days old)
>References	: http://marc.info/?l=linux-kernel&m=124913190304149&w=4

I have not seen this since I rebooted to 31-rc6 3.5 days ago.  So apparently 
something that went into rc6 that was not in rc5, has fixed it.  I have had 
one kmail crash, but IIRC that was after yum had updated something.  I 
believe this particular tar related  item has been attended to.  Close it 
out.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
<https://www.nrahq.org/nrabonus/accept-membership.asp>

If *I* had a hammer, there'd be no more folk singers.

Re: [Bug #13943] WARNING: at net/mac80211/mlme.c:2292 with ath5k

[Fabio Comolli]

This bug is still present (also in wireless-testing).

On Wed, Aug 19, 2009 at 10:26 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13943
> Subject         : WARNING: at net/mac80211/mlme.c:2292 with ath5k
> Submitter       : Fabio Comolli <fabio.comolli@gmail.com>
> Date            : 2009-08-06 20:15 (14 days old)
> References      : http://marc.info/?l=linux-kernel&m=124958978600600&w=4
>
>
>

Re: [Bug #13941] x86 Geode issue

[Martin-Éric Racine]

Yes, it's still valid.

Screenshots of the crash have been provided. Is anything else missing
for the LKML to be able to debug and fix this?

On Wed, Aug 19, 2009 at 11:26 PM, Rafael J. Wysocki<rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13941
> Subject         : x86 Geode issue
> Submitter       : Martin-Éric Racine <q-funk@iki.fi>
> Date            : 2009-08-03 12:58 (17 days old)
> References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4
>
>
>

Re: [Bug #13947] Libertas: Association request to the driver failed

[roel kluin]

> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13947
> Subject         : Libertas: Association request to the driver failed
> Submitter       : Daniel Mack <daniel-rDUAYElUppE@public.gmane.org>
> Date            : 2009-08-07 19:11 (13 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=57921c312e8cef72ba35a4cfe870b376da0b1b87
> References      : http://marc.info/?l=linux-kernel&m=124967234311481&w=4
> Handled-By      : Roel Kluin <roel.kluin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

I think this should be fixed with patch of Dan Williams found here:

http://lkml.org/lkml/2009/8/12/299

Roel

Re: [Bug #13819] system freeze when switching to console

[Rafael J. Wysocki]

On Thursday 20 August 2009, reinette chatre wrote:
> On Wed, 2009-08-19 at 13:26 -0700, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
> > Subject		: system freeze when switching to console
> > Submitter	: Reinette Chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-07-23 17:57 (28 days old)
> 
> This issue is still present in 2.6.31-rc6. Unfortunately the patches I
> reverted to get a working system does not revert cleanly anymore.

Thanks for the update.

Rafael

Re: [Bug #13899] Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.

[Rafael J. Wysocki]

On Thursday 20 August 2009, Gene Heskett wrote:
> On Wednesday 19 August 2009, Rafael J. Wysocki wrote:
> >This message has been generated automatically as a part of a report
> >of recent regressions.
> >
> >The following bug entry is on the current list of known regressions
> >from 2.6.30.  Please verify if it still should be listed and let me know
> >(either way).
> >
> >
> >Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13899
> >Subject		: Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.
> >Submitter	: Gene Heskett <gene.heskett@verizon.net>
> >Date		: 2009-08-01 13:04 (19 days old)
> >References	: http://marc.info/?l=linux-kernel&m=124913190304149&w=4
> 
> I have not seen this since I rebooted to 31-rc6 3.5 days ago.  So apparently 
> something that went into rc6 that was not in rc5, has fixed it.  I have had 
> one kmail crash, but IIRC that was after yum had updated something.  I 
> believe this particular tar related  item has been attended to.  Close it 
> out.

Thanks, closed.

Rafael

Re: [Bug #13940] iwlagn and sky2 stopped working, ACPI-related

[Rafael J. Wysocki]

On Thursday 20 August 2009, Ricardo Jorge da Fonseca Marques Ferreira wrote:
> Yes, 2.6.31-rc6 still has the bug.

Thanks for the update.

Rafael


> On Wednesday 19 August 2009, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13940
> > Subject		: iwlagn and sky2 stopped working, ACPI-related
> > Submitter	: Ricardo Jorge da Fonseca Marques Ferreira <storm-cOTmPFJTJjbk1uMJSBkQmQ@public.gmane.org>
> > Date		: 2009-08-07 22:33 (13 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124968457731107&w=4

Re: [Bug #13941] x86 Geode issue

[Rafael J. Wysocki]

On Thursday 20 August 2009, Martin-Éric Racine wrote:
> Yes, it's still valid.

Thanks for the update.

> Screenshots of the crash have been provided. Is anything else missing
> for the LKML to be able to debug and fix this?

An idea of what can be wrong?

> On Wed, Aug 19, 2009 at 11:26 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13941
> > Subject         : x86 Geode issue
> > Submitter       : Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>
> > Date            : 2009-08-03 12:58 (17 days old)
> > References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4

Rafael

Re: [Bug #13943] WARNING: at net/mac80211/mlme.c:2292 with ath5k

[Rafael J. Wysocki]

On Thursday 20 August 2009, Fabio Comolli wrote:
> This bug is still present (also in wireless-testing).

Thanks for the update.

Rafael


> On Wed, Aug 19, 2009 at 10:26 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13943
> > Subject         : WARNING: at net/mac80211/mlme.c:2292 with ath5k
> > Submitter       : Fabio Comolli <fabio.comolli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date            : 2009-08-06 20:15 (14 days old)
> > References      : http://marc.info/?l=linux-kernel&m=124958978600600&w=4

Re: [Bug #13947] Libertas: Association request to the driver failed

[Rafael J. Wysocki]

On Thursday 20 August 2009, roel kluin wrote:
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13947
> > Subject         : Libertas: Association request to the driver failed
> > Submitter       : Daniel Mack <daniel-rDUAYElUppE@public.gmane.org>
> > Date            : 2009-08-07 19:11 (13 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=57921c312e8cef72ba35a4cfe870b376da0b1b87
> > References      : http://marc.info/?l=linux-kernel&m=124967234311481&w=4
> > Handled-By      : Roel Kluin <roel.kluin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> 
> I think this should be fixed with patch of Dan Williams found here:
> 
> http://lkml.org/lkml/2009/8/12/299

Thanks, bug entry updated.

Rafael

Re: [Bug #13947] Libertas: Association request to the driver failed

[Gene Heskett]

On Thursday 20 August 2009, Rafael J. Wysocki wrote:
>On Thursday 20 August 2009, roel kluin wrote:
>> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13947
>> > Subject         : Libertas: Association request to the driver failed
>> > Submitter       : Daniel Mack <daniel-rDUAYElUppE@public.gmane.org>
>> > Date            : 2009-08-07 19:11 (13 days old)
>> > First-Bad-Commit:
>> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm
>> >it;h=57921c312e8cef72ba35a4cfe870b376da0b1b87 References      :
>> > http://marc.info/?l=linux-kernel&m=124967234311481&w=4 Handled-By     
>> > : Roel Kluin <roel.kluin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>
>> I think this should be fixed with patch of Dan Williams found here:
>>
>> http://lkml.org/lkml/2009/8/12/299
>
>Thanks, bug entry updated.
>
Has this made it into 2.6.31-rc6?  I have one of these pci cards, and it is 
still a no-show even after modprobing the mwl* and libertas modules.

>Rafael
>--
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
<https://www.nrahq.org/nrabonus/accept-membership.asp>

There is no act of treachery or mean-ness of which a political party
is not capable; for in politics there is no honour.
		-- Benjamin Disraeli, "Vivian Grey"

Re: [Bug #14014] kernel bug at shut down

[Norbert Preining]

On Wed, 19 Aug 2009, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14014
> Subject		: kernel bug at shut down
> Submitter	: Norbert Preining <preining@logic.at>
> Date		: 2009-08-14 9:11 (6 days old)
> References	: http://marc.info/?l=linux-kernel&m=125024112418870&w=4

I didn't have any BUG on recent shutdowns in -rc6, but even the last
one was a single instance and not recurring.

Don't know what to do with that.

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at>        Vienna University of Technology
Debian Developer <preining@debian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
SLIGO (n.)
An unnamed and exotic sexual act which people like to believe that
famous films stars get up to in private. 'To commit sligo.'
			--- Douglas Adams, The Meaning of Liff

Re: [Bug #14014] kernel bug at shut down

[Rafael J. Wysocki]

On Thursday 20 August 2009, Norbert Preining wrote:
> On Wed, 19 Aug 2009, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14014
> > Subject		: kernel bug at shut down
> > Submitter	: Norbert Preining <preining-DX+603jRYB8@public.gmane.org>
> > Date		: 2009-08-14 9:11 (6 days old)
> > References	: http://marc.info/?l=linux-kernel&m=125024112418870&w=4
> 
> I didn't have any BUG on recent shutdowns in -rc6, but even the last
> one was a single instance and not recurring.
> 
> Don't know what to do with that.

Let's assume it's been fixed.  I'll close the bug now and please reopen it if
you see this bug again.

Best,
Rafael

Re: [Bug #13941] x86 Geode issue

[Cyrill Gorcunov]

[Rafael J. Wysocki - Thu, Aug 20, 2009 at 05:04:06PM +0200]
| On Thursday 20 August 2009, Martin-Éric Racine wrote:
| > Yes, it's still valid.
| 
| Thanks for the update.
| 
| > Screenshots of the crash have been provided. Is anything else missing
| > for the LKML to be able to debug and fix this?
| 
| An idea of what can be wrong?
| 
| > On Wed, Aug 19, 2009 at 11:26 PM, Rafael J. Wysocki<rjw-KKrjLPT3xs0@public.gmane.org> wrote:
| > > This message has been generated automatically as a part of a report
| > > of recent regressions.
| > >
| > > The following bug entry is on the current list of known regressions
| > > from 2.6.30.  Please verify if it still should be listed and let me know
| > > (either way).
| > >
| > >
| > > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13941
| > > Subject         : x86 Geode issue
| > > Submitter       : Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>
| > > Date            : 2009-08-03 12:58 (17 days old)
| > > References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4
| 
| Rafael
| 

Hi,

may I post a thought?

It seems strange to me that alloc_inode may set 

#ifdef CONFIG_FS_POSIX_ACL
	inode->i_acl = inode->i_default_acl = ACL_NOT_CACHED;
#endif

[where ACL_NOT_CACHED is #define ACL_NOT_CACHED ((void *)(-1))]

meanwhile say jffs2_init_acl_post use ACL_NOT_CACHED
as a valid value and trying to parse it.

But perhaps, I miss something.

	-- Cyrill

Re: [Bug #13941] x86 Geode issue

[Cyrill Gorcunov]

[Cyrill Gorcunov - Thu, Aug 20, 2009 at 10:36:35PM +0400]
...
| | > > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13941
| | > > Subject         : x86 Geode issue
| | > > Submitter       : Martin-Éric Racine <q-funk-X3B1VOXEql0@public.gmane.org>
| | > > Date            : 2009-08-03 12:58 (17 days old)
| | > > References      : http://marc.info/?l=linux-kernel&m=124930434732481&w=4
| | 
| | Rafael
| | 
| 
| Hi,
| 
| may I post a thought?
| 
| It seems strange to me that alloc_inode may set 
| 
| #ifdef CONFIG_FS_POSIX_ACL
| 	inode->i_acl = inode->i_default_acl = ACL_NOT_CACHED;
| #endif
| 
| [where ACL_NOT_CACHED is #define ACL_NOT_CACHED ((void *)(-1))]
| 
| meanwhile say jffs2_init_acl_post use ACL_NOT_CACHED
| as a valid value and trying to parse it.
| 
| But perhaps, I miss something.
| 
| 	-- Cyrill

Sorry, this is unrelated and wrong. Drop this message.

	-- Cyrill

Re: [Bug #13942] Troubles with AoE and uninitialized object

[Bruno Prémont]

On Wed, 19 August 2009 "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me
> know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13942
> Subject		: Troubles with AoE and uninitialized object
> Submitter	: Bruno Prémont <bonbons-ud5FBsm0p/xEiooADzr8i9i2O/JbrIOy@public.gmane.org>
> Date		: 2009-08-04 10:12 (16 days old)
> References	:
> http://marc.info/?l=linux-kernel&m=124938117104811&w=4
> 

This one is still valid for 2.6.31-rc6 though I have not yet taken
the time to attempt bisecting it. I will probably bisect over the
week-end.

Bruno

Re: [Bug #13946] x86 MCE malfunction on Thinkpad T42p

[Johannes Stezenbach]

On Wed, Aug 19, 2009 at 10:26:57PM +0200, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13946
> Subject		: x86 MCE malfunction on Thinkpad T42p
> Submitter	: Johannes Stezenbach <js@sig21.net>
> Date		: 2009-08-07 17:09 (13 days old)
> References	: http://marc.info/?l=linux-kernel&m=124966500232399&w=4
> Handled-By	: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> Patch		: http://patchwork.kernel.org/patch/37908/

This is fixed in v2.6.31-rc6-223-g6c30c53 by
commit c7f6fa44115d401e89db730f357629d39f8e4ba6
"x86, mce: don't log boot MCEs on Pentium M (model == 13) CPUs".


Thanks
Johannes

Re: [Bug #13948] ath5k broken after suspend-to-ram

[Johannes Stezenbach]

On Wed, Aug 19, 2009 at 10:26:59PM +0200, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13948
> Subject		: ath5k broken after suspend-to-ram
> Submitter	: Johannes Stezenbach <js-FF7aIK3TAVNeoWH0uzbU5w@public.gmane.org>
> Date		: 2009-08-07 21:51 (13 days old)
> References	: http://marc.info/?l=linux-kernel&m=124968192727854&w=4
> Handled-By	: Nick Kossifidis <mickflemm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Patch		: http://patchwork.kernel.org/patch/38550/

I cannot test this at the moment, but there have been no
changes to ath5k since I reported the bug, and the
patch still applies.  Please keep this listed.


Thanks
Johannes

Re: 2.6.31-rc6-git5: Reported regressions from 2.6.30

[John Dykstra]

On Wed, 2009-08-19 at 22:20 +0200, Rafael J. Wysocki wrote:
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=14002
> Subject         : WARNING: at net/ipv4/af_inet.c:154
> inet_sock_destruct+0x164/0x1c0()
> Submitter       : Ralf Hildebrandt <ralf.hildebrandt-jq1tPX9l7E6ELgA04lAiVw@public.gmane.org>
> Date            : 2009-08-18 12:37 (2 days old)

That looks similar to the WARNING discussed in [1].

There was no resolution to that thread.  However, [2] points out
possible other occurrences of the problem in 2.6.27, 28 and 29.

--  John

[1]  http://www.spinics.net/lists/netdev/msg103267.html
[2]  http://www.spinics.net/lists/netdev/msg104120.html

Re: 2.6.31-rc6-git5: Reported regressions from 2.6.30

[Rafael J. Wysocki]

On Thursday 20 August 2009, John Dykstra wrote:
> On Wed, 2009-08-19 at 22:20 +0200, Rafael J. Wysocki wrote:
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=14002
> > Subject         : WARNING: at net/ipv4/af_inet.c:154
> > inet_sock_destruct+0x164/0x1c0()
> > Submitter       : Ralf Hildebrandt <ralf.hildebrandt@charite.de>
> > Date            : 2009-08-18 12:37 (2 days old)
> 
> That looks similar to the WARNING discussed in [1].
> 
> There was no resolution to that thread.  However, [2] points out
> possible other occurrences of the problem in 2.6.27, 28 and 29.
> 
> --  John
> 
> [1]  http://www.spinics.net/lists/netdev/msg103267.html
> [2]  http://www.spinics.net/lists/netdev/msg104120.html

Thanks for the information.

So I'll drop this from the list, since it most probably is not a recent thing.

Best,
Rafael

Re: [Bug #13942] Troubles with AoE and uninitialized object

[Rafael J. Wysocki]

On Thursday 20 August 2009, Bruno Prémont wrote:
> On Wed, 19 August 2009 "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me
> > know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13942
> > Subject		: Troubles with AoE and uninitialized object
> > Submitter	: Bruno Prémont <bonbons-ud5FBsm0p/xEiooADzr8i9i2O/JbrIOy@public.gmane.org>
> > Date		: 2009-08-04 10:12 (16 days old)
> > References	:
> > http://marc.info/?l=linux-kernel&m=124938117104811&w=4
> > 
> 
> This one is still valid for 2.6.31-rc6 though I have not yet taken
> the time to attempt bisecting it. I will probably bisect over the
> week-end.

Thanks for the update.

Rafael

Re: [Bug #13946] x86 MCE malfunction on Thinkpad T42p

[Rafael J. Wysocki]

On Thursday 20 August 2009, Johannes Stezenbach wrote:
> On Wed, Aug 19, 2009 at 10:26:57PM +0200, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13946
> > Subject		: x86 MCE malfunction on Thinkpad T42p
> > Submitter	: Johannes Stezenbach <js-FF7aIK3TAVNeoWH0uzbU5w@public.gmane.org>
> > Date		: 2009-08-07 17:09 (13 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124966500232399&w=4
> > Handled-By	: Bartlomiej Zolnierkiewicz <bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Patch		: http://patchwork.kernel.org/patch/37908/
> 
> This is fixed in v2.6.31-rc6-223-g6c30c53 by
> commit c7f6fa44115d401e89db730f357629d39f8e4ba6
> "x86, mce: don't log boot MCEs on Pentium M (model == 13) CPUs".

Thanks, closed.

Rafael

Re: [Bug #13948] ath5k broken after suspend-to-ram

[Rafael J. Wysocki]

On Thursday 20 August 2009, Johannes Stezenbach wrote:
> On Wed, Aug 19, 2009 at 10:26:59PM +0200, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13948
> > Subject		: ath5k broken after suspend-to-ram
> > Submitter	: Johannes Stezenbach <js-FF7aIK3TAVNeoWH0uzbU5w@public.gmane.org>
> > Date		: 2009-08-07 21:51 (13 days old)
> > References	: http://marc.info/?l=linux-kernel&m=124968192727854&w=4
> > Handled-By	: Nick Kossifidis <mickflemm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Patch		: http://patchwork.kernel.org/patch/38550/
> 
> I cannot test this at the moment, but there have been no
> changes to ath5k since I reported the bug, and the
> patch still applies.  Please keep this listed.

OK, thanks for the update.

Rafael

Re: [Bug #13947] Libertas: Association request to the driver failed

[Dan Williams]

On Thu, 2009-08-20 at 11:17 -0400, Gene Heskett wrote:
> On Thursday 20 August 2009, Rafael J. Wysocki wrote:
> >On Thursday 20 August 2009, roel kluin wrote:
> >> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13947
> >> > Subject         : Libertas: Association request to the driver failed
> >> > Submitter       : Daniel Mack <daniel-rDUAYElUppE@public.gmane.org>
> >> > Date            : 2009-08-07 19:11 (13 days old)
> >> > First-Bad-Commit:
> >> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm
> >> >it;h=57921c312e8cef72ba35a4cfe870b376da0b1b87 References      :
> >> > http://marc.info/?l=linux-kernel&m=124967234311481&w=4 Handled-By     
> >> > : Roel Kluin <roel.kluin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >>
> >> I think this should be fixed with patch of Dan Williams found here:
> >>
> >> http://lkml.org/lkml/2009/8/12/299
> >
> >Thanks, bug entry updated.
> >
> Has this made it into 2.6.31-rc6?  I have one of these pci cards, and it is 
> still a no-show even after modprobing the mwl* and libertas modules.

You're still looking for the softmac stuff, which the 'libertas' driver
doesn't support.  You want to keep track of mwl8k where any new support
for softmac Marvell cards would end up.

Dan

Re: [Bug #13947] Libertas: Association request to the driver failed

[Dan Williams]

On Thu, 2009-08-20 at 17:10 +0200, Rafael J. Wysocki wrote:
> On Thursday 20 August 2009, roel kluin wrote:
> > > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13947
> > > Subject         : Libertas: Association request to the driver failed
> > > Submitter       : Daniel Mack <daniel-rDUAYElUppE@public.gmane.org>
> > > Date            : 2009-08-07 19:11 (13 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=57921c312e8cef72ba35a4cfe870b376da0b1b87
> > > References      : http://marc.info/?l=linux-kernel&m=124967234311481&w=4
> > > Handled-By      : Roel Kluin <roel.kluin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > 
> > I think this should be fixed with patch of Dan Williams found here:
> > 
> > http://lkml.org/lkml/2009/8/12/299
> 
> Thanks, bug entry updated.

Rebased tested and posted to linux-wireless officially:

Subject: [PATCH] libertas: clean up and clarify get_common_rates
Date:    Fri, 21 Aug 2009 09:35:20 -0500

Dan

Re: [Bug #13947] Libertas: Association request to the driver failed

[Gene Heskett]

On Friday 21 August 2009, Dan Williams wrote:
>On Thu, 2009-08-20 at 11:17 -0400, Gene Heskett wrote:
>> On Thursday 20 August 2009, Rafael J. Wysocki wrote:
>> >On Thursday 20 August 2009, roel kluin wrote:
>> >> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13947
>> >> > Subject         : Libertas: Association request to the driver failed
>> >> > Submitter       : Daniel Mack <daniel@caiaq.de>
>> >> > Date            : 2009-08-07 19:11 (13 days old)
>> >> > First-Bad-Commit:
>> >> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
>> >> >omm it;h=57921c312e8cef72ba35a4cfe870b376da0b1b87 References      :
>> >> > http://marc.info/?l=linux-kernel&m=124967234311481&w=4 Handled-By
>> >> >
>> >> > : Roel Kluin <roel.kluin@gmail.com>
>> >>
>> >> I think this should be fixed with patch of Dan Williams found here:
>> >>
>> >> http://lkml.org/lkml/2009/8/12/299
>> >
>> >Thanks, bug entry updated.
>>
>> Has this made it into 2.6.31-rc6?  I have one of these pci cards, and it
>> is still a no-show even after modprobing the mwl* and libertas modules.
>
>You're still looking for the softmac stuff, which the 'libertas' driver
>doesn't support.  You want to keep track of mwl8k where any new support
>for softmac Marvell cards would end up.
>
>Dan

I am also loading that mwl8k module, Dan, and that isn't doing any notable 
good either.  These are NetGears latest pci 802-11bg cards.  And the only pci 
or pci-e cards widely available (Staples stocks them) unless wallmart might 
have some (spitui) Belkin cards.  I have not noted them at my local wally's.

modprobing mwl8k, then libertas, gets this in an lsmod:
Module                  Size  Used by
libertas              166456  0
lib80211                5664  1 libertas
mwl8k                  27740  0
mac80211              149932  1 mwl8k
cfg80211               88988  2 mwl8k,mac80211

removing them and reversing the order of loading:
Module                  Size  Used by
mwl8k                  27740  0
libertas              166456  0
lib80211                5664  1 libertas
mac80211              149932  1 mwl8k
cfg80211               88988  2 mwl8k,mac80211

really doesn't change anything.  And of those two loads, only one shows in 
the messages file as:

Aug 21 11:55:35 coyote kernel: [436464.036670] cfg80211: Using static regulatory domain info
Aug 21 11:55:35 coyote kernel: [436464.036673] cfg80211: Regulatory domain: US
Aug 21 11:55:35 coyote kernel: [436464.036675]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Aug 21 11:55:35 coyote kernel: [436464.036678]  (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
Aug 21 11:55:35 coyote kernel: [436464.036681]  (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Aug 21 11:55:35 coyote kernel: [436464.036684]  (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Aug 21 11:55:35 coyote kernel: [436464.036686]  (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Aug 21 11:55:35 coyote kernel: [436464.036689]  (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
Aug 21 11:55:35 coyote kernel: [436464.036692]  (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
Aug 21 11:55:35 coyote kernel: [436464.036697] cfg80211: Calling CRDA for country: US
Aug 21 11:55:59 coyote kernel: [436488.563723] lib80211: common routines for IEEE802.11 drivers

And no usable interface is created.
[root@coyote etc]# iwconfig
lo        no wireless extensions.
eth0      no wireless extensions.
eth1      no wireless extensions.

eth1 is the 2nd MCP55 (nvidia) port on this motherboard, unrelated to anything wireless.

Fedora 10 system, ASUS M2N SLI Deluxe mobo, slow 2.2ghz phenom 9550 cpu.
Running 2.6.31-rc6.

Am I doing anything wrong?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
<https://www.nrahq.org/nrabonus/accept-membership.asp>

Uncompensated overtime?  Just Say No.

Re: [Bug #13947] Libertas: Association request to the driver failed

[Rafael J. Wysocki]

On Friday 21 August 2009, Dan Williams wrote:
> On Thu, 2009-08-20 at 17:10 +0200, Rafael J. Wysocki wrote:
> > On Thursday 20 August 2009, roel kluin wrote:
> > > > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13947
> > > > Subject         : Libertas: Association request to the driver failed
> > > > Submitter       : Daniel Mack <daniel@caiaq.de>
> > > > Date            : 2009-08-07 19:11 (13 days old)
> > > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=57921c312e8cef72ba35a4cfe870b376da0b1b87
> > > > References      : http://marc.info/?l=linux-kernel&m=124967234311481&w=4
> > > > Handled-By      : Roel Kluin <roel.kluin@gmail.com>
> > > 
> > > I think this should be fixed with patch of Dan Williams found here:
> > > 
> > > http://lkml.org/lkml/2009/8/12/299
> > 
> > Thanks, bug entry updated.
> 
> Rebased tested and posted to linux-wireless officially:
> 
> Subject: [PATCH] libertas: clean up and clarify get_common_rates
> Date:    Fri, 21 Aug 2009 09:35:20 -0500

Thanks, updated.

Rafael

Re: 2.6.31-rc6-git5: Reported regressions from 2.6.30

[Larry Finger]

Rafael J. Wysocki wrote:

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13960
> Subject		: rtl8187 not connect to wifi
> Submitter	: okias <d.okias@gmail.com>
> Date		: 2009-08-10 19:16 (10 days old)

The patch for this one was sent from Linville to DaveM earlier today,
and should be sent to mainline in the near future.

AFAIK, the OP has not yet tested the patch, but I think I was able to
reproduce the problem, and the patch did fit it for me.

Larry

Re: 2.6.31-rc6-git5: Reported regressions from 2.6.30

[Rafael J. Wysocki]

On Friday 21 August 2009, Larry Finger wrote:
> Rafael J. Wysocki wrote:
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13960
> > Subject		: rtl8187 not connect to wifi
> > Submitter	: okias <d.okias@gmail.com>
> > Date		: 2009-08-10 19:16 (10 days old)
> 
> The patch for this one was sent from Linville to DaveM earlier today,
> and should be sent to mainline in the near future.
> 
> AFAIK, the OP has not yet tested the patch, but I think I was able to
> reproduce the problem, and the patch did fit it for me.

Thanks for the update.

Can you please close the bug when the patch is merged?

Rafael

Re: [Bug #14015] pty regressed again, breaking expect and gcc's testsuite

[Rafael J. Wysocki]

On Monday 24 August 2009, Mikael Pettersson wrote:
> On Wed, 19 Aug 2009 22:27:02 +0200 (CEST), Rafael J. Wysocki wrote:
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=3D14015
> > Subject		: pty regressed again, breaking expect and gcc's testsuite
> > Submitter	: Mikael Pettersson <mikpe-1zs4UD6AkMk@public.gmane.org>
> > Date		: 2009-08-14 23:41 (6 days old)
> > References	: http://marc.info/?l=3Dlinux-kernel&m=3D125029329805643&w=3D4
> 
> The good news is that I don't see this issue any more with 2.6.31-rc7
> on x86. The bad news is that the first time I reported this issue, for
> -rc3 or -rc4 I think, I thought it was fixed in -rc5 only to see it
> reappear in -rc6 on x86 and in -rc5 on ARM. So I'd like to keep this
> open another week while I run more regression tests on non-x86 platforms.
> 
> While I don't suspect any arch-specific problems in the pty/tty code,
> I do suspect timing/race-type problems which are obviously affected
> by platform speed etc.

OK, thanks for the update.

Rafael

Re: [Bug #13947] Libertas: Association request to the driver failed

[Dan Williams]

On Fri, 2009-08-21 at 12:09 -0400, Gene Heskett wrote:
> On Friday 21 August 2009, Dan Williams wrote:
> >On Thu, 2009-08-20 at 11:17 -0400, Gene Heskett wrote:
> >> On Thursday 20 August 2009, Rafael J. Wysocki wrote:
> >> >On Thursday 20 August 2009, roel kluin wrote:
> >> >> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13947
> >> >> > Subject         : Libertas: Association request to the driver failed
> >> >> > Submitter       : Daniel Mack <daniel-rDUAYElUppE@public.gmane.org>
> >> >> > Date            : 2009-08-07 19:11 (13 days old)
> >> >> > First-Bad-Commit:
> >> >> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
> >> >> >omm it;h=57921c312e8cef72ba35a4cfe870b376da0b1b87 References      :
> >> >> > http://marc.info/?l=linux-kernel&m=124967234311481&w=4 Handled-By
> >> >> >
> >> >> > : Roel Kluin <roel.kluin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >> >>
> >> >> I think this should be fixed with patch of Dan Williams found here:
> >> >>
> >> >> http://lkml.org/lkml/2009/8/12/299
> >> >
> >> >Thanks, bug entry updated.
> >>
> >> Has this made it into 2.6.31-rc6?  I have one of these pci cards, and it
> >> is still a no-show even after modprobing the mwl* and libertas modules.
> >
> >You're still looking for the softmac stuff, which the 'libertas' driver
> >doesn't support.  You want to keep track of mwl8k where any new support
> >for softmac Marvell cards would end up.
> >
> >Dan
> 
> I am also loading that mwl8k module, Dan, and that isn't doing any notable 
> good either.  These are NetGears latest pci 802-11bg cards.  And the only pci 
> or pci-e cards widely available (Staples stocks them) unless wallmart might 
> have some (spitui) Belkin cards.  I have not noted them at my local wally's.

Right, because mwl8k supports only the softmac 8687 PCI-E parts right
now.  It doesn't yet support the 8335 or 8310 or 86xx TopDog parts yet.
There hasn't been any movement on those for a while and I haven't gotten
around to abstracting mwl8k's hardware support to handle the older
parts.  But mwl8k is the only driver that could possibly be relevant for
you, since libertas will always be for the fullmac-only parts (8385,
8388, 8686, 8688).

Dan

> modprobing mwl8k, then libertas, gets this in an lsmod:
> Module                  Size  Used by
> libertas              166456  0
> lib80211                5664  1 libertas
> mwl8k                  27740  0
> mac80211              149932  1 mwl8k
> cfg80211               88988  2 mwl8k,mac80211
> 
> removing them and reversing the order of loading:
> Module                  Size  Used by
> mwl8k                  27740  0
> libertas              166456  0
> lib80211                5664  1 libertas
> mac80211              149932  1 mwl8k
> cfg80211               88988  2 mwl8k,mac80211
> 
> really doesn't change anything.  And of those two loads, only one shows in 
> the messages file as:
> 
> Aug 21 11:55:35 coyote kernel: [436464.036670] cfg80211: Using static regulatory domain info
> Aug 21 11:55:35 coyote kernel: [436464.036673] cfg80211: Regulatory domain: US
> Aug 21 11:55:35 coyote kernel: [436464.036675]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> Aug 21 11:55:35 coyote kernel: [436464.036678]  (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
> Aug 21 11:55:35 coyote kernel: [436464.036681]  (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Aug 21 11:55:35 coyote kernel: [436464.036684]  (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Aug 21 11:55:35 coyote kernel: [436464.036686]  (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Aug 21 11:55:35 coyote kernel: [436464.036689]  (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> Aug 21 11:55:35 coyote kernel: [436464.036692]  (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
> Aug 21 11:55:35 coyote kernel: [436464.036697] cfg80211: Calling CRDA for country: US
> Aug 21 11:55:59 coyote kernel: [436488.563723] lib80211: common routines for IEEE802.11 drivers
> 
> And no usable interface is created.
> [root@coyote etc]# iwconfig
> lo        no wireless extensions.
> eth0      no wireless extensions.
> eth1      no wireless extensions.
> 
> eth1 is the 2nd MCP55 (nvidia) port on this motherboard, unrelated to anything wireless.
> 
> Fedora 10 system, ASUS M2N SLI Deluxe mobo, slow 2.2ghz phenom 9550 cpu.
> Running 2.6.31-rc6.
> 
> Am I doing anything wrong?
> 

[Bug #13819] system freeze when switching to console

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
Subject		: system freeze when switching to console
Submitter	: Reinette Chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-23 17:57 (34 days old)

Re: [Bug #13947] Libertas: Association request to the driver failed

[Gene Heskett]

On Tuesday 25 August 2009, Dan Williams wrote:
>On Fri, 2009-08-21 at 12:09 -0400, Gene Heskett wrote:
>> On Friday 21 August 2009, Dan Williams wrote:
>> >On Thu, 2009-08-20 at 11:17 -0400, Gene Heskett wrote:
>> >> On Thursday 20 August 2009, Rafael J. Wysocki wrote:
>> >> >On Thursday 20 August 2009, roel kluin wrote:
>> >> >> > Bug-Entry       :
>> >> >> > http://bugzilla.kernel.org/show_bug.cgi?id=13947 Subject        
>> >> >> > : Libertas: Association request to the driver failed Submitter   
>> >> >> >    : Daniel Mack <daniel-rDUAYElUppE@public.gmane.org>
>> >> >> > Date            : 2009-08-07 19:11 (13 days old)
>> >> >> > First-Bad-Commit:
>> >> >> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;
>> >> >> >a=c omm it;h=57921c312e8cef72ba35a4cfe870b376da0b1b87 References  
>> >> >> >    : http://marc.info/?l=linux-kernel&m=124967234311481&w=4
>> >> >> > Handled-By
>> >> >> >
>> >> >> > : Roel Kluin <roel.kluin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> >> >>
>> >> >> I think this should be fixed with patch of Dan Williams found here:
>> >> >>
>> >> >> http://lkml.org/lkml/2009/8/12/299
>> >> >
>> >> >Thanks, bug entry updated.
>> >>
>> >> Has this made it into 2.6.31-rc6?  I have one of these pci cards, and
>> >> it is still a no-show even after modprobing the mwl* and libertas
>> >> modules.
>> >
>> >You're still looking for the softmac stuff, which the 'libertas' driver
>> >doesn't support.  You want to keep track of mwl8k where any new support
>> >for softmac Marvell cards would end up.
>> >
>> >Dan
>>
>> I am also loading that mwl8k module, Dan, and that isn't doing any
>> notable good either.  These are NetGears latest pci 802-11bg cards.  And
>> the only pci or pci-e cards widely available (Staples stocks them) unless
>> wallmart might have some (spitui) Belkin cards.  I have not noted them at
>> my local wally's.
>
>Right, because mwl8k supports only the softmac 8687 PCI-E parts right
>now.  It doesn't yet support the 8335 or 8310 or 86xx TopDog parts yet.
>There hasn't been any movement on those for a while and I haven't gotten
>around to abstracting mwl8k's hardware support to handle the older
>parts.  But mwl8k is the only driver that could possibly be relevant for
>you, since libertas will always be for the fullmac-only parts (8385,
>8388, 8686, 8688).
>
>Dan

Thanks Dan, now I have a clearer picture, and I should be watching for 
patches to mwl8k to go by & testing them, that I can do if you want to put me 
on your patch list for that, if & when there are patches to test. ;-)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
<https://www.nrahq.org/nrabonus/accept-membership.asp>

Bowie's Theorem:
	If an experiment works, you must be using the wrong equipment.

Re: 2.6.31-rc6-git5: Reported regressions from 2.6.30

[Larry Finger]

Rafael J. Wysocki wrote:
> On Friday 21 August 2009, Larry Finger wrote:
>> Rafael J. Wysocki wrote:
>>
>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13960
>>> Subject		: rtl8187 not connect to wifi
>>> Submitter	: okias <d.okias@gmail.com>
>>> Date		: 2009-08-10 19:16 (10 days old)
>> The patch for this one was sent from Linville to DaveM earlier today,
>> and should be sent to mainline in the near future.
>>
>> AFAIK, the OP has not yet tested the patch, but I think I was able to
>> reproduce the problem, and the patch did fit it for me.
> 
> Thanks for the update.
> 
> Can you please close the bug when the patch is merged?

The patch hit mainline as commit
1a9937b7f07ab6e35515e32a7625f0ba50ab7670. The bug has been closed.

Larry

[Bug #13819] system freeze when switching to console

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.30.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
Subject		: system freeze when switching to console
Submitter	: Reinette Chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-07-23 17:57 (46 days old)

Re: [Bug #13819] system freeze when switching to console

[reinette chatre]

On Sun, 2009-09-06 at 10:24 -0700, Rafael J. Wysocki wrote:
> Please verify if it still should be listed and let me know
> (either way).

Issue is still present in 2.6.31-rc8.

Reinette

Re: [Bug #13819] system freeze when switching to console

[Linus Torvalds]

On Tue, 8 Sep 2009, reinette chatre wrote:

> On Sun, 2009-09-06 at 10:24 -0700, Rafael J. Wysocki wrote:
> > Please verify if it still should be listed and let me know
> > (either way).
> 
> Issue is still present in 2.6.31-rc8.

Is there any chance that you could connect a serial line to the machine? 
Your report about blinking keyboard led's means that there's an oops, but 
since the display isn't in textmode (and the oops obviously happens when 
trying to enter it), we don't know what it is.

A serial line (along with a kernel compiled with serial console support, 
of course, and a kernel command line option like "console=ttyS0,115400 
console=tty0") would get that. You'd just need another machine with a 
terminal program like minicom..

The network console could also work out, but serial lines tend to be more 
reliable if you have them. But in the absense of serial lines, see the
Documentation/networking/netconsole.txt file for some details. The setup 
is more complicated, but on the other hand it's a lot more dynamic, and in 
your case - since the box works until you try to switch to text-mode, I 
suspect the network console dynamic run-time setup would be easy for you 
to use.

(For other examples of using netconsole with that dynamic mode, just 
google for "sys/kernel/config/netconsole" and you'll find a number of docs 
that explain how to find the MAC address for setup etc).

		Linus

Re: [Bug #13819] system freeze when switching to console

[Jesse Barnes]

On Sun,  6 Sep 2009 19:24:50 +0200 (CEST)
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.30.  Please verify if it still should be listed and let me
> know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13819
> Subject		: system freeze when switching to console
> Submitter	: Reinette Chatre <reinette.chatre@intel.com>
> Date		: 2009-07-23 17:57 (46 days old)

So simply switching VTs causes this problem too?  Based on your initial
description it sounds like a panic (keyboard LEDs were flashing).  If
it happens at VT switch time you should be able to capture the panic
output with netconsole like Linus mentioned.

-- 
Jesse Barnes, Intel Open Source Technology Center

Re: [Bug #13819] system freeze when switching to console

[reinette chatre]

On Tue, 2009-09-08 at 10:00 -0700, Linus Torvalds wrote:
> 
> On Tue, 8 Sep 2009, reinette chatre wrote:
> 
> > On Sun, 2009-09-06 at 10:24 -0700, Rafael J. Wysocki wrote:
> > > Please verify if it still should be listed and let me know
> > > (either way).
> > 
> > Issue is still present in 2.6.31-rc8.
> 
> Is there any chance that you could connect a serial line to the machine? 

The system does not have a serial console, but I was able to set up
netconsole. For what it is worth, I did not do this until now because
(1) I was able to bisect the problem, and (2) I asked driver developers
directly how I can help to debug this and I received no response.

As you can see from the kernel version it is not a build of a vanilla
kernel. It only contains changes related to the wireless networking work
I am doing.

Here is the output:

[  352.803652] render error detected, EIR: 0x00000010
[  352.803684]   IPEIR: 0x00000000
[  352.803709]   IPEHR: 0x01000000
[  352.803732]   INSTDONE: 0xfffffffe
[  352.803754]   INSTPS: 0x0001e000
[  352.803776]   INSTDONE1: 0xffffffff
[  352.803801]   ACTHD: 0x0480a3c8
[  352.803823] page table error
[  352.803846]   PGTBL_ER: 0x00100000
[  352.803870] [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
[  352.803960] BUG: unable to handle kernel NULL pointer dereference at 0000000000000084
[  352.804006] IP: [<ffffffffa03ecaab>] i915_driver_irq_handler+0x26b/0xd20 [i915]
[  352.804006] PGD b5d00067 PUD b9753067 PMD 0 
[  352.804006] Oops: 0000 [#1] SMP 
[  352.804006] last sysfs file: /sys/class/power_supply/BAT0/energy_full
[  352.804006] CPU 0 
[  352.804006] Modules linked in: i915 drm i2c_algo_bit i2c_core ipv6 acpi_cpufreq cpufreq_userspace cpufreq_powersave cpufreq_ondemand cpufreq_conservative cpufreq_stats freq_table container sbs sbshc arc4 ecb joydev af_packet pcmcia psmouse sony_laptop serio_raw yenta_socket rsrc_nonstatic pcmcia_core pcspkr iTCO_wdt iTCO_vendor_support rfkill intel_agp button battery tpm_infineon tpm tpm_bios processor video output ac evdev ext3 jbd mbcache sr_mod sg cdrom sd_mod ahci libata scsi_mod ehci_hcd uhci_hcd usbcore thermal fan thermal_sys [last unloaded: cfg80211]
[  352.804006] Pid: 4424, comm: Xorg Not tainted 2.6.31-rc8-wl-50925-gdcecd82-dirty #57 VGN-Z540N
[  352.804006] RIP: 0010:[<ffffffffa03ecaab>]  [<ffffffffa03ecaab>] i915_driver_irq_handler+0x26b/0xd20 [i915]
[  352.804006] RSP: 0018:ffff880001e9de58  EFLAGS: 00010082
[  352.804006] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[  352.804006] RDX: ffffc9000007d898 RSI: 0000000000000001 RDI: ffffffff8132f0f8
[  352.804006] RBP: ffff880001e9dee8 R08: 0000000000000002 R09: ffff880037373c38
[  352.804006] R10: 0000000000000000 R11: 0000000000000001 R12: ffff8800b57fe000
[  352.804006] R13: 000000000000001f R14: ffff8800b57fe000 R15: ffff8800b9746000
[  352.804006] FS:  00007fcc05d20700(0000) GS:ffff880001e9a000(0000) knlGS:0000000000000000
[  352.804006] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  352.804006] CR2: 0000000000000084 CR3: 00000000b50c3000 CR4: 00000000000006f0
[  352.804006] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  352.804006] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  352.804006] Process Xorg (pid: 4424, threadinfo ffff8800b6b1a000, task ffff880037373c00)
[  352.804006] Stack:
[  352.804006]  ffffffff8106db7d 0000000000000086 ffff88009a5ce040 ffff8800b57fe158
[  352.804006] <0> ffff8800b57fe1a8 ffff8800b57fe110 0004000000008000 0000000400440202
[  352.804006] <0> 0000000000000086 0044020200000000 0000001000040000 0000000000000040
[  352.804006] Call Trace:
[  352.804006]  <IRQ> 
[  352.804006]  [<ffffffff8106db7d>] ? mark_held_locks+0x6d/0x90
[  352.804006]  [<ffffffff81098ee8>] handle_IRQ_event+0x68/0x170
[  352.804006]  [<ffffffff8109ac01>] handle_edge_irq+0xc1/0x160
[  352.804006]  [<ffffffff8100e76f>] handle_irq+0x1f/0x30
[  352.804006]  [<ffffffff8100dc6a>] do_IRQ+0x6a/0xf0
[  352.804006]  [<ffffffff8100c793>] ret_from_intr+0x0/0xf
[  352.804006]  <EOI> 
[  352.804006]  [<ffffffff81070b88>] ? lock_acquire+0xe8/0x100
[  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180 [drm]
[  352.804006]  [<ffffffff8132d7b5>] ? mutex_lock_nested+0x45/0x320
[  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180 [drm]
[  352.804006]  [<ffffffff8106de85>] ? trace_hardirqs_on_caller+0x145/0x190
[  352.804006]  [<ffffffff8106dedd>] ? trace_hardirqs_on+0xd/0x10
[  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180 [drm]
[  352.804006]  [<ffffffffa03f3335>] ? i915_gem_idle+0x225/0x330 [i915]
[  352.804006]  [<ffffffffa03f34c7>] ? i915_gem_leavevt_ioctl+0x37/0x50 [i915]
[  352.804006]  [<ffffffffa03bdafd>] ? drm_ioctl+0x17d/0x3c0 [drm]
[  352.804006]  [<ffffffffa03f3490>] ? i915_gem_leavevt_ioctl+0x0/0x50 [i915]
[  352.804006]  [<ffffffff810d0ad5>] ? do_wp_page+0x185/0x7a0
[  352.804006]  [<ffffffff811a9a33>] ? __up_read+0x23/0xb0
[  352.804006]  [<ffffffff810ff17d>] ? vfs_ioctl+0x7d/0xa0
[  352.804006]  [<ffffffff810ff2ba>] ? do_vfs_ioctl+0x8a/0x5c0
[  352.804006]  [<ffffffff8105fec6>] ? up_read+0x26/0x30
[  352.804006]  [<ffffffff8100c829>] ? retint_swapgs+0xe/0x13
[  352.804006]  [<ffffffff810ff889>] ? sys_ioctl+0x99/0xa0
[  352.804006]  [<ffffffff8100bd6b>] ? system_call_fastpath+0x16/0x1b
[  352.804006] Code: 00 8b 18 49 8b 87 b0 05 00 00 48 8b 80 20 02 00 00 48 85 c0 74 21 48 8b 80 00 01 00 00 48 8b 50 08 48 85 d2 74 11 49 8b 44 24 78 <8b> 80 84 00 00 00 89 82 08 08 00 00 f6 45 a0 02 0f 85 47 03 00 
[  352.804006] RIP  [<ffffffffa03ecaab>] i915_driver_irq_handler+0x26b/0xd20 [i915]
[  352.804006]  RSP <ffff880001e9de58>
[  352.804006] CR2: 0000000000000084
[  352.804006] ---[ end trace 756dbe26c2f29fdd ]---
[  352.804006] Kernel panic - not syncing: Fatal exception in interrupt
[  352.804006] Pid: 4424, comm: Xorg Tainted: G      D    2.6.31-rc8-wl-50925-gdcecd82-dirty #57
[  352.804006] Call Trace:
[  352.804006]  <IRQ>  [<ffffffff8132ba7f>] panic+0xa0/0x170
[  352.804006]  [<ffffffff8132f0f8>] ? _spin_unlock_irqrestore+0x58/0x60
[  352.804006]  [<ffffffff81041b35>] ? release_console_sem+0x1f5/0x240
[  352.804006]  [<ffffffff81041e05>] ? console_unblank+0x75/0x90
[  352.804006]  [<ffffffff813306c4>] oops_end+0xd4/0xe0
[  352.804006]  [<ffffffff810279d8>] no_context+0xe8/0x260
[  352.804006]  [<ffffffff81027ca5>] __bad_area_nosemaphore+0x155/0x1f0
[  352.804006]  [<ffffffff8106ca5d>] ? trace_hardirqs_off+0xd/0x10
[  352.804006]  [<ffffffff8132f0f8>] ? _spin_unlock_irqrestore+0x58/0x60
[  352.804006]  [<ffffffff8103bb58>] ? try_to_wake_up+0xe8/0x210
[  352.804006]  [<ffffffff81027d4e>] bad_area_nosemaphore+0xe/0x10
[  352.804006]  [<ffffffff8133204e>] do_page_fault+0x29e/0x350
[  352.804006]  [<ffffffff8132f8af>] page_fault+0x1f/0x30
[  352.804006]  [<ffffffff8132f0f8>] ? _spin_unlock_irqrestore+0x58/0x60
[  352.804006]  [<ffffffffa03ecaab>] ? i915_driver_irq_handler+0x26b/0xd20 [i915]
[  352.804006]  [<ffffffffa03ec9cb>] ? i915_driver_irq_handler+0x18b/0xd20 [i915]
[  352.804006]  [<ffffffff8106db7d>] ? mark_held_locks+0x6d/0x90
[  352.804006]  [<ffffffff81098ee8>] handle_IRQ_event+0x68/0x170
[  352.804006]  [<ffffffff8109ac01>] handle_edge_irq+0xc1/0x160
[  352.804006]  [<ffffffff8100e76f>] handle_irq+0x1f/0x30
[  352.804006]  [<ffffffff8100dc6a>] do_IRQ+0x6a/0xf0
[  352.804006]  [<ffffffff8100c793>] ret_from_intr+0x0/0xf
[  352.804006]  <EOI>  [<ffffffff81070b88>] ? lock_acquire+0xe8/0x100
[  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180 [drm]
[  352.804006]  [<ffffffff8132d7b5>] ? mutex_lock_nested+0x45/0x320
[  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180 [drm]
[  352.804006]  [<ffffffff8106de85>] ? trace_hardirqs_on_caller+0x145/0x190
[  352.804006]  [<ffffffff8106dedd>] ? trace_hardirqs_on+0xd/0x10
[  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180 [drm]
[  352.804006]  [<ffffffffa03f3335>] ? i915_gem_idle+0x225/0x330 [i915]
[  352.804006]  [<ffffffffa03f34c7>] ? i915_gem_leavevt_ioctl+0x37/0x50 [i915]
[  352.804006]  [<ffffffffa03bdafd>] ? drm_ioctl+0x17d/0x3c0 [drm]
[  352.804006]  [<ffffffffa03f3490>] ? i915_gem_leavevt_ioctl+0x0/0x50 [i915]
[  352.804006]  [<ffffffff810d0ad5>] ? do_wp_page+0x185/0x7a0
[  352.804006]  [<ffffffff811a9a33>] ? __up_read+0x23/0xb0
[  352.804006]  [<ffffffff810ff17d>] ? vfs_ioctl+0x7d/0xa0
[  352.804006]  [<ffffffff810ff2ba>] ? do_vfs_ioctl+0x8a/0x5c0
[  352.804006]  [<ffffffff8105fec6>] ? up_read+0x26/0x30
[  352.804006]  [<ffffffff8100c829>] ? retint_swapgs+0xe/0x13
[  352.804006]  [<ffffffff810ff889>] ? sys_ioctl+0x99/0xa0
[  352.804006]  [<ffffffff8100bd6b>] ? system_call_fastpath+0x16/0x1b

Re: [Bug #13819] system freeze when switching to console

[Linus Torvalds]

On Tue, 8 Sep 2009, reinette chatre wrote:
> 
> As you can see from the kernel version it is not a build of a vanilla
> kernel. It only contains changes related to the wireless networking work
> I am doing.
> 
> Here is the output:

Thanks, this is great. It pinpoints the problem very effectively.

> [  352.803960] BUG: unable to handle kernel NULL pointer dereference at 0000000000000084
> [  352.804006] IP: [<ffffffffa03ecaab>] i915_driver_irq_handler+0x26b/0xd20 [i915]

The code here is

	  16:	48 8b 80 00 01 00 00 	mov    0x100(%rax),%rax
	  1d:	48 8b 50 08          	mov    0x8(%rax),%rdx
	  21:	48 85 d2             	test   %rdx,%rdx
	  24:	74 11                	je     0x37
	  26:	49 8b 44 24 78       	mov    0x78(%r12),%rax
	  2b:*	8b 80 84 00 00 00    	mov    0x84(%rax),%eax     <-- trapping instruction
	  31:	89 82 08 08 00 00    	mov    %eax,0x808(%rdx)
	  37:	f6 45 a0 02          	testb  $0x2,-0x60(%rbp)

and that "testb $0x2, -0x60(%rbp)" seems to be the

	if (iir & I915_USER_INTERRUPT) {

test if I'm reading things right. Although it could also be the

	if (eir & I915_ERROR_MEMORY_REFRESH) {

thing. The disassembly is totally impossible to read, because the stupid 
i915 driver is chock-full of crap like

	if (IS_G4X(dev)) {
		..

which expands to insane amounts of code that check the PCI ID's one by 
one.

Intel guys: could you _please_ stop doing that. Create a capability mask 
in the device or something, so that you can test for "is this a G4x" with 
a single bit test, rather than have code like this:

        mov    0x31c(%rsi),%eax
        cmp    $0x2982,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x2972,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x2992,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x29a2,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x2a02,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x2a12,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x2a42,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x2e02,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x2e12,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x2e22,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x2e32,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>
        cmp    $0x42,%eax
        je     0xffffffff8124b669 <i915_driver_irq_handler+177>

for that IS_G4X() thing (I'm not kidding - that's exactly a hundred bytes 
of code for that _stupid_ test, and it's inlined!)

Anyway, we're getting that DRM irq, and it has a normal IRQ stack trace:

> [  352.804006] Process Xorg (pid: 4424, threadinfo ffff8800b6b1a000, task ffff880037373c00)
> [  352.804006] Call Trace:
> [  352.804006]  <IRQ> 
> [  352.804006]  [<ffffffff8106db7d>] ? mark_held_locks+0x6d/0x90
> [  352.804006]  [<ffffffff81098ee8>] handle_IRQ_event+0x68/0x170
> [  352.804006]  [<ffffffff8109ac01>] handle_edge_irq+0xc1/0x160
> [  352.804006]  [<ffffffff8100e76f>] handle_irq+0x1f/0x30
> [  352.804006]  [<ffffffff8100dc6a>] do_IRQ+0x6a/0xf0
> [  352.804006]  [<ffffffff8100c793>] ret_from_intr+0x0/0xf

.. but it happened just as we're tearing down the DRM irq handling:

> [  352.804006]  <EOI> 
> [  352.804006]  [<ffffffff81070b88>] ? lock_acquire+0xe8/0x100
> [  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180 [drm]
> [  352.804006]  [<ffffffff8132d7b5>] ? mutex_lock_nested+0x45/0x320
> [  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180 [drm]
> [  352.804006]  [<ffffffff8106de85>] ? trace_hardirqs_on_caller+0x145/0x190
> [  352.804006]  [<ffffffff8106dedd>] ? trace_hardirqs_on+0xd/0x10
> [  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180 [drm]
> [  352.804006]  [<ffffffffa03f3335>] ? i915_gem_idle+0x225/0x330 [i915]
> [  352.804006]  [<ffffffffa03f34c7>] ? i915_gem_leavevt_ioctl+0x37/0x50 [i915]
> [  352.804006]  [<ffffffffa03bdafd>] ? drm_ioctl+0x17d/0x3c0 [drm]
> [  352.804006]  [<ffffffffa03f3490>] ? i915_gem_leavevt_ioctl+0x0/0x50 [i915]

so what is going on is that the i915 driver has obviously torn down some 
state before it uninstalls the irq, so the irq happens when the state has 
already been torn down, and the irq handler is not ready for that.

This patch *may* fix it - simply by getting rid of the irq early. However, 
I did not check whether maybe something in i915_gem_idle() actually needs 
the interrupt to be able to happen, so this is TOTALLY UNTESTED!

		Linus
---
 drivers/gpu/drm/i915/i915_gem.c |    6 +-----
 1 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 7edb5b9..80e5ba4 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -4232,15 +4232,11 @@ int
 i915_gem_leavevt_ioctl(struct drm_device *dev, void *data,
 		       struct drm_file *file_priv)
 {
-	int ret;
-
 	if (drm_core_check_feature(dev, DRIVER_MODESET))
 		return 0;
 
-	ret = i915_gem_idle(dev);
 	drm_irq_uninstall(dev);
-
-	return ret;
+	return i915_gem_idle(dev);
 }
 
 void

Re: [Bug #13819] system freeze when switching to console

[Jesse Barnes]

On Tue, 8 Sep 2009 11:06:21 -0700 (PDT)
Linus Torvalds <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote:

> 
> 
> On Tue, 8 Sep 2009, reinette chatre wrote:
> > 
> > As you can see from the kernel version it is not a build of a
> > vanilla kernel. It only contains changes related to the wireless
> > networking work I am doing.
> > 
> > Here is the output:
> 
> Thanks, this is great. It pinpoints the problem very effectively.
> 
> > [  352.803960] BUG: unable to handle kernel NULL pointer
> > dereference at 0000000000000084 [  352.804006] IP:
> > [<ffffffffa03ecaab>] i915_driver_irq_handler+0x26b/0xd20 [i915]
> 
> The code here is
> 
> 	  16:	48 8b 80 00 01 00 00 	mov
> 0x100(%rax),%rax 1d:	48 8b 50 08          	mov
> 0x8(%rax),%rdx 21:	48 85 d2             	test
> %rdx,%rdx 24:	74 11                	je     0x37
> 	  26:	49 8b 44 24 78       	mov
> 0x78(%r12),%rax 2b:*	8b 80 84 00 00 00    	mov
> 0x84(%rax),%eax     <-- trapping instruction 31:	89 82 08 08
> 00 00    	mov    %eax,0x808(%rdx) 37:	f6 45 a0
> 02          	testb  $0x2,-0x60(%rbp)
> 
> and that "testb $0x2, -0x60(%rbp)" seems to be the
> 
> 	if (iir & I915_USER_INTERRUPT) {
> 
> test if I'm reading things right. Although it could also be the
> 
> 	if (eir & I915_ERROR_MEMORY_REFRESH) {
> 
> thing. The disassembly is totally impossible to read, because the
> stupid i915 driver is chock-full of crap like
> 
> 	if (IS_G4X(dev)) {
> 		..
> 
> which expands to insane amounts of code that check the PCI ID's one
> by one.
> 
> Intel guys: could you _please_ stop doing that. Create a capability
> mask in the device or something, so that you can test for "is this a
> G4x" with a single bit test, rather than have code like this:
> 
>         mov    0x31c(%rsi),%eax
>         cmp    $0x2982,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x2972,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x2992,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x29a2,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x2a02,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x2a12,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x2a42,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x2e02,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x2e12,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x2e22,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x2e32,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
>         cmp    $0x42,%eax
>         je     0xffffffff8124b669 <i915_driver_irq_handler+177>
> 
> for that IS_G4X() thing (I'm not kidding - that's exactly a hundred
> bytes of code for that _stupid_ test, and it's inlined!)

Yeah things are getting a bit out of hand there...  We've moved to
feature tests for some things, but they're still PCI ID based; however
they should be easy to convert.

> 
> Anyway, we're getting that DRM irq, and it has a normal IRQ stack
> trace:
> 
> > [  352.804006] Process Xorg (pid: 4424, threadinfo
> > ffff8800b6b1a000, task ffff880037373c00) [  352.804006] Call Trace:
> > [  352.804006]  <IRQ> 
> > [  352.804006]  [<ffffffff8106db7d>] ? mark_held_locks+0x6d/0x90
> > [  352.804006]  [<ffffffff81098ee8>] handle_IRQ_event+0x68/0x170
> > [  352.804006]  [<ffffffff8109ac01>] handle_edge_irq+0xc1/0x160
> > [  352.804006]  [<ffffffff8100e76f>] handle_irq+0x1f/0x30
> > [  352.804006]  [<ffffffff8100dc6a>] do_IRQ+0x6a/0xf0
> > [  352.804006]  [<ffffffff8100c793>] ret_from_intr+0x0/0xf
> 
> .. but it happened just as we're tearing down the DRM irq handling:
> 
> > [  352.804006]  <EOI> 
> > [  352.804006]  [<ffffffff81070b88>] ? lock_acquire+0xe8/0x100
> > [  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180
> > [drm] [  352.804006]  [<ffffffff8132d7b5>] ?
> > mutex_lock_nested+0x45/0x320 [  352.804006]  [<ffffffffa03c0b85>] ?
> > drm_irq_uninstall+0x65/0x180 [drm] [  352.804006]
> > [<ffffffff8106de85>] ? trace_hardirqs_on_caller+0x145/0x190
> > [  352.804006]  [<ffffffff8106dedd>] ? trace_hardirqs_on+0xd/0x10
> > [  352.804006]  [<ffffffffa03c0b85>] ? drm_irq_uninstall+0x65/0x180
> > [drm] [  352.804006]  [<ffffffffa03f3335>] ?
> > i915_gem_idle+0x225/0x330 [i915] [  352.804006]
> > [<ffffffffa03f34c7>] ? i915_gem_leavevt_ioctl+0x37/0x50 [i915]
> > [  352.804006]  [<ffffffffa03bdafd>] ? drm_ioctl+0x17d/0x3c0 [drm]
> > [  352.804006]  [<ffffffffa03f3490>] ?
> > i915_gem_leavevt_ioctl+0x0/0x50 [i915]
> 
> so what is going on is that the i915 driver has obviously torn down
> some state before it uninstalls the irq, so the irq happens when the
> state has already been torn down, and the irq handler is not ready
> for that.
> 
> This patch *may* fix it - simply by getting rid of the irq early.
> However, I did not check whether maybe something in i915_gem_idle()
> actually needs the interrupt to be able to happen, so this is TOTALLY
> UNTESTED!
> 
> 		Linus
> ---
>  drivers/gpu/drm/i915/i915_gem.c |    6 +-----
>  1 files changed, 1 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gem.c
> b/drivers/gpu/drm/i915/i915_gem.c index 7edb5b9..80e5ba4 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -4232,15 +4232,11 @@ int
>  i915_gem_leavevt_ioctl(struct drm_device *dev, void *data,
>  		       struct drm_file *file_priv)
>  {
> -	int ret;
> -
>  	if (drm_core_check_feature(dev, DRIVER_MODESET))
>  		return 0;
>  
> -	ret = i915_gem_idle(dev);
>  	drm_irq_uninstall(dev);
> -
> -	return ret;
> +	return i915_gem_idle(dev);
>  }

Theoretically i915_gem_idle should prevent any user interrupts from
coming in.  If we uninstall the IRQ first we i915_gem_idle probably
won't work anymore, since it queues an interrupt and waits for it.

Eric, any thoughts on this?  We shouldn't be racing to queue new work
after the idle call since we suspend GEM at that point, so we must be
failing to manage our active lists properly somehow?

-- 
Jesse Barnes, Intel Open Source Technology Center

Re: [Bug #13819] system freeze when switching to console

[Linus Torvalds]

On Tue, 8 Sep 2009, Linus Torvalds wrote:
> 
> The code here is
> 
> 	  16:	48 8b 80 00 01 00 00 	mov    0x100(%rax),%rax
> 	  1d:	48 8b 50 08          	mov    0x8(%rax),%rdx
> 	  21:	48 85 d2             	test   %rdx,%rdx
> 	  24:	74 11                	je     0x37
> 	  26:	49 8b 44 24 78       	mov    0x78(%r12),%rax
> 	  2b:*	8b 80 84 00 00 00    	mov    0x84(%rax),%eax     <-- trapping instruction
> 	  31:	89 82 08 08 00 00    	mov    %eax,0x808(%rdx)
> 	  37:	f6 45 a0 02          	testb  $0x2,-0x60(%rbp)
> 
> and that "testb $0x2, -0x60(%rbp)" seems to be the
> 
> 	if (iir & I915_USER_INTERRUPT) {

Yeah, that seems to be the right thing.

So the actual faulting instruction is from this:

                if (dev->primary->master) {
                        master_priv = dev->primary->master->driver_priv;
                        if (master_priv->sarea_priv)
                                master_priv->sarea_priv->last_dispatch =
					READ_BREADCRUMB(dev_priv);

and it looks like %rax starts out being 'dev', then the

	mov    0x100(%rax),%rax

means that %rax is now 'dev->primary', and then

	mov    0x8(%rax),%rdx

moves 'dev->primary->master' into %rdx. It's not zero, so we then do that 
READ_BREADCRUMB(dev_priv), which expands to

	READ_HWSP(dev_priv, I915_BREADCRUMB_INDEX)

which in turn is

	(((volatile u32*)(dev_priv->hw_status_page))[reg])

and it looks like dev_priv->hw_status_page is NULL.

You can verify this by looking at teh exception address:

	BUG: unable to handle kernel NULL pointer dereference at 0000000000000084

and that '84' is I915_BREADCRUMB_INDEX*4 (0x21*4).

And the problem seems to be that we've cleared the hw_status_page pointer 
in i915_gem_cleanup_hws():

	dev_priv->hw_status_page = NULL;

and we did that in 

  i915_gem_idle() ->
    i915_gem_cleanup_ringbuffer() ->
      i915_gem_cleanup_hws()

so now since interrupts are still enabled, you'll get a NULL pointer 
dereference.

I think my patch is correct.

		Linus

Re: [Bug #13819] system freeze when switching to console

[Linus Torvalds]

On Tue, 8 Sep 2009, Jesse Barnes wrote:
> 
> Theoretically i915_gem_idle should prevent any user interrupts from
> coming in.

That is _entirely_ immaterial.

The thing is, interrupts can be shared. So it does not matter ONE WHIT 
that you are trying to idle the hardware - there may be _other_ hardware 
in the machine that is not idle, and that raises the same shared 
interrupt. End result: the irq handler will be called, whether your 
particular hardware is idle or not.

So if you tear down data structures that the interrupt handler needs, you 
_ABSOLUTELY_ must first unregister the whole interrupt.

Also, even if there are no shared interrupts or any other devices, there 
can easily be old pending interrupts still queued up on IO-APIC's etc. So 
even though you quiesce the hardware, there is no guarantee that there 
aren't some pending interrupts that happened just before you turned off 
the interrupt from the hardware side, and are still "en route" to the CPU.

Which gets us exactly the same rule as if there were shared interrupts: if 
your interrupt handler depends on some data structure, you must tear down 
the interrupt handler _before_ you tear down the data structures it 
depends on (and in the reverse order when setting things up, of course).

> If we uninstall the IRQ first we i915_gem_idle probably
> won't work anymore, since it queues an interrupt and waits for it.

So then you'd better fix that. Because the code as is is very 
fundamentally buggy.

> Eric, any thoughts on this?  We shouldn't be racing to queue new work
> after the idle call since we suspend GEM at that point, so we must be
> failing to manage our active lists properly somehow?

See my previous email. The bug is that you do

  i915_gem_cleanup_ringbuffer ->
    i915_gem_cleanup_hws ->
      dev_priv->hw_status_page = NULL;

while interrupts are still enabled and coming in. And the interrupt path 
wants to access that hw_status_page. Which you just destroyed.

			Linus

Re: [Bug #13819] system freeze when switching to console

[Jesse Barnes]

On Tue, 8 Sep 2009 12:26:45 -0700 (PDT)
Linus Torvalds <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote:

> 
> 
> On Tue, 8 Sep 2009, Jesse Barnes wrote:
> > 
> > Theoretically i915_gem_idle should prevent any user interrupts from
> > coming in.
> 
> That is _entirely_ immaterial.
> 
> The thing is, interrupts can be shared. So it does not matter ONE
> WHIT that you are trying to idle the hardware - there may be _other_
> hardware in the machine that is not idle, and that raises the same
> shared interrupt. End result: the irq handler will be called, whether
> your particular hardware is idle or not.

Which is fine.  We can handle interrupts in the shared case.  It's
specific IRQ statuses we can't handle.  E.g. if we've explicitly turned
off vblank events we definitely won't expect to see them in the handler
(assuming we've taken care to barrier things like you mention below).

> So if you tear down data structures that the interrupt handler needs,
> you _ABSOLUTELY_ must first unregister the whole interrupt.
> 
> Also, even if there are no shared interrupts or any other devices,
> there can easily be old pending interrupts still queued up on
> IO-APIC's etc. So even though you quiesce the hardware, there is no
> guarantee that there aren't some pending interrupts that happened
> just before you turned off the interrupt from the hardware side, and
> are still "en route" to the CPU.

The way we barrier things should handle that case.

> Which gets us exactly the same rule as if there were shared
> interrupts: if your interrupt handler depends on some data structure,
> you must tear down the interrupt handler _before_ you tear down the
> data structures it depends on (and in the reverse order when setting
> things up, of course).
> 
> > If we uninstall the IRQ first we i915_gem_idle probably
> > won't work anymore, since it queues an interrupt and waits for it.
> 
> So then you'd better fix that. Because the code as is is very 
> fundamentally buggy.
> 
> > Eric, any thoughts on this?  We shouldn't be racing to queue new
> > work after the idle call since we suspend GEM at that point, so we
> > must be failing to manage our active lists properly somehow?
> 
> See my previous email. The bug is that you do
> 
>   i915_gem_cleanup_ringbuffer ->
>     i915_gem_cleanup_hws ->
>       dev_priv->hw_status_page = NULL;
> 
> while interrupts are still enabled and coming in. And the interrupt
> path wants to access that hw_status_page. Which you just destroyed.

Yeah, saw that.  I don't think that's the root cause though.  If we see
a user interrupt after gem_idle is called we may have serious issues in
our command handling code.

-- 
Jesse Barnes, Intel Open Source Technology Center

Re: [Bug #13819] system freeze when switching to console

[Linus Torvalds]

On Tue, 8 Sep 2009, Jesse Barnes wrote:
> 
> Yeah, saw that.  I don't think that's the root cause though.  If we see
> a user interrupt after gem_idle is called we may have serious issues in
> our command handling code.

Quite frankly, I do not understand why you seem to be making excuses for 
code that causes a very nasty and undebuggable oops, causing the machine 
to die. 

This regression is almost two months old, and apparently the Intel 
graphics people DID ABSOLUTELY NOTHING about it during those two months, 
because they couldn't be bothered to look at it.

And now, when I pinpointed exactly where the oops happens, and what the 
cause is, you seem to be trying to hold things up. I wanted to do the 
final 2.6.31 release yesterday, quite frankly I'm not in the _least_ 
interested in excuses, I'm interested in something that at least gets us 
back to the 2.6.30 state that doesn't oops!

Get me a patch, please. If disabling the interrupts early won't work, get 
me something else. Stop delaying it - it's been pending for 48 days 
already.

		Linus

Re: [Bug #13819] system freeze when switching to console

[Jesse Barnes]

On Tue, 8 Sep 2009 15:06:21 -0700 (PDT)
Linus Torvalds <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote:

> 
> 
> On Tue, 8 Sep 2009, Jesse Barnes wrote:
> > 
> > Yeah, saw that.  I don't think that's the root cause though.  If we
> > see a user interrupt after gem_idle is called we may have serious
> > issues in our command handling code.
> 
> Quite frankly, I do not understand why you seem to be making excuses
> for code that causes a very nasty and undebuggable oops, causing the
> machine to die. 

No excuses.  This is a serious bug; I just don't want to paper over it.

> This regression is almost two months old, and apparently the Intel 
> graphics people DID ABSOLUTELY NOTHING about it during those two
> months, because they couldn't be bothered to look at it.

Yeah sorry, this is the first I've seen of it...  I usually troll the
regressions lists but I must have missed this one.

> And now, when I pinpointed exactly where the oops happens, and what
> the cause is, you seem to be trying to hold things up. I wanted to do
> the final 2.6.31 release yesterday, quite frankly I'm not in the
> _least_ interested in excuses, I'm interested in something that at
> least gets us back to the 2.6.30 state that doesn't oops!
> 
> Get me a patch, please. If disabling the interrupts early won't work,
> get me something else. Stop delaying it - it's been pending for 48
> days already.

Sure, looking at it now.

-- 
Jesse Barnes, Intel Open Source Technology Center

Re: [Bug #13819] system freeze when switching to console

[reinette chatre]

On Tue, 2009-09-08 at 11:06 -0700, Linus Torvalds wrote:
> so this is TOTALLY UNTESTED!

I understand that the discussion is still going on whether this is the
right thing to do. Even so, I thought you may like to know that with
this patch I can again switch to console, back again, hibernate, and
shut down .. all without crashing my system.

Tested-by: Reinette Chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

Thank you very much!

Reinette

Re: [Bug #13819] system freeze when switching to console

[Jesse Barnes]

On Tue, 8 Sep 2009 15:06:21 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> And now, when I pinpointed exactly where the oops happens, and what
> the cause is, you seem to be trying to hold things up. I wanted to do
> the final 2.6.31 release yesterday, quite frankly I'm not in the
> _least_ interested in excuses, I'm interested in something that at
> least gets us back to the 2.6.30 state that doesn't oops!

Based on the earlier mail I thought this might have been a bigger
problem with the way we handle command submission and completion; but
on looking at things again (both Linus's debugging and your
configuration), I think this is actually a DRI1 & userspace related
issue.  Back in the DRI1 days, the X server told the driver when to
register and unregister its irq handler, and had some responsibility
for making sure it didn't hose things (very easy to do with the old
architecture).  Stuff like this was one of the main reasons we moved
most of the handling of this into the kernel...

We obviously need a kernel fix though; panics like this aren't
acceptable.

This fix is along the lines of Linus's initial suggestion; we
definitely are tearing down some state that the interrupt handler
needs.  And the 2D driver isn't saving us from ourselves like it used
to (previously it would uninstall the IRQ handler before tearing down
the mappings; but with the kernel in charge of those now, we have to
handle it).

This one should disable i915 interrupts (we'll still handle shared ones
just fine as no-ops) at the point where we no longer need them, then
let the DRM core code take care of finally unregistering it.

Ugly, but I'd like to know if it works for you.  Any chance you could
give it a try Reinette?

-- 
Jesse Barnes, Intel Open Source Technology Center

diff --git a/drivers/gpu/drm/i915/i915_gem.c
b/drivers/gpu/drm/i915/i915_gem.c index 0767521..487d902 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -3990,6 +3990,7 @@ i915_gem_idle(struct drm_device *dev)
                return ret;
        }
 
+       i915_driver_irq_uninstall(dev);
        i915_gem_cleanup_ringbuffer(dev);
        mutex_unlock(&dev->struct_mutex);
 

Re: [Bug #13819] system freeze when switching to console

[Jesse Barnes]

On Tue, 08 Sep 2009 15:37:41 -0700
reinette chatre <reinette.chatre@intel.com> wrote:

> On Tue, 2009-09-08 at 11:06 -0700, Linus Torvalds wrote:
> > so this is TOTALLY UNTESTED!
> 
> I understand that the discussion is still going on whether this is the
> right thing to do. Even so, I thought you may like to know that with
> this patch I can again switch to console, back again, hibernate, and
> shut down .. all without crashing my system.
> 
> Tested-by: Reinette Chatre <reinette.chatre@intel.com>
> 
> Thank you very much!

Do you see "hardware wedged" messages in your log after using Linus's
patch?  That's what I'd expect...  ah no I see we don't call the
routine that requires interrupts in that path like I thought.

So Linus's patch is fine with me.

Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>

Sorry Linus, you were right; I was making this more complicated than it
had to be.

-- 
Jesse Barnes, Intel Open Source Technology Center

Re: [Bug #13819] system freeze when switching to console

[reinette chatre]

On Tue, 2009-09-08 at 16:16 -0700, Jesse Barnes wrote:

> Do you see "hardware wedged" messages in your log after using Linus's
> patch?  That's what I'd expect...  ah no I see we don't call the
> routine that requires interrupts in that path like I thought.

I can confirm that. While using this patch, when I am in X and then
switch to console and back to X there are no new messages (checked with
dmesg).

Reinette

Re: [Bug #13819] system freeze when switching to console

[Linus Torvalds]

On Tue, 8 Sep 2009, Jesse Barnes wrote:
> > This regression is almost two months old, and apparently the Intel 
> > graphics people DID ABSOLUTELY NOTHING about it during those two
> > months, because they couldn't be bothered to look at it.
> 
> Yeah sorry, this is the first I've seen of it...  I usually troll the
> regressions lists but I must have missed this one.

Hmm. We must have screwed up something, because this was bisected to the 
intel DRI commits back in July. See

	http://bugzilla.kernel.org/show_bug.cgi?id=13819#c4

and while there was some confusion about exactly which commit caused 
it - probably because the irq thing obviously depends on timing - 
Reinette had a list of three commits that he used to be able to revert to 
get things going:

   drm/i915: Don't update display FIFO watermark on IGDNG
   drm/i915: add FIFO watermark support
   drm/i915: enable error detection & state collection

So Andrew assigned it to DRI, and Rafael has had both Eric and Ma Ling on 
the cc for his regression reports because of the bisection. And that has 
been going on for a long time, I just checked:

    Date: Sun, 26 Jul 2009 22:28:26 +0200 (CEST)
    From: Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>
    To: Linux Kernel Mailing List <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
    Cc: Kernel Testers List <kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>, "ling.ma-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org" <ling.ma-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
        Linus Torvalds <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>, Ma Ling <ling.ma-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>, Reinette Chatre <reinette.chatre-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
    Subject: [Bug #13819] system freeze when switching to console

If you didn't see it, then that means that we have screw-ups with the 
bugzilla thing. You're actually listed as a "Reviewed-by" on the commit 
that the fixed-up bisection blamed - And I get the feeling that Rafael's 
bugzilla "bugme" scripts may only pick up "Signed-off-by:" lines.

The point is: this bug has been in bisected in bugzilla for a month and a 
half, and had at least two Intel DRI people cc'd on the weekly reminder 
reports, along with being

	Assigned To:  	drivers_video-dri-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org

We have other bugs on the regression list that are even older (no, I'm not 
proud of them):

	http://bugzilla.kernel.org/show_bug.cgi?id=13809
	http://bugzilla.kernel.org/show_bug.cgi?id=13740
	http://bugzilla.kernel.org/show_bug.cgi?id=13733
	http://bugzilla.kernel.org/show_bug.cgi?id=13645

but they aren't bisected and it's not nearly as clear what is going on 
there. The last one in particular I don't know if it even happens any 
more and the first one seems to be fixed in -rc5, or at least the 
reporter couldn't reproduce it any more..

		Linus

Re: [Bug #13819] system freeze when switching to console

[Jesse Barnes]

On Tue, 8 Sep 2009 16:36:06 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> 
> 
> On Tue, 8 Sep 2009, Jesse Barnes wrote:
> > > This regression is almost two months old, and apparently the
> > > Intel graphics people DID ABSOLUTELY NOTHING about it during
> > > those two months, because they couldn't be bothered to look at it.
> > 
> > Yeah sorry, this is the first I've seen of it...  I usually troll
> > the regressions lists but I must have missed this one.
> 
> Hmm. We must have screwed up something, because this was bisected to
> the intel DRI commits back in July. See
> 
> 	http://bugzilla.kernel.org/show_bug.cgi?id=13819#c4
> 
> and while there was some confusion about exactly which commit caused 
> it - probably because the irq thing obviously depends on timing - 
> Reinette had a list of three commits that he used to be able to
> revert to get things going:
> 
>    drm/i915: Don't update display FIFO watermark on IGDNG
>    drm/i915: add FIFO watermark support
>    drm/i915: enable error detection & state collection
> 
> So Andrew assigned it to DRI, and Rafael has had both Eric and Ma
> Ling on the cc for his regression reports because of the bisection.
> And that has been going on for a long time, I just checked:
> 
>     Date: Sun, 26 Jul 2009 22:28:26 +0200 (CEST)
>     From: Rafael J. Wysocki <rjw@sisk.pl>
>     To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
>     Cc: Kernel Testers List <kernel-testers@vger.kernel.org>, Eric
> Anholt <eric@anholt.net>, "ling.ma@intel.com" <ling.ma@intel.com>,
> Linus Torvalds <torvalds@linux-foundation.org>, Ma Ling
> <ling.ma@intel.com>, Reinette Chatre <reinette.chatre@intel.com>
> Subject: [Bug #13819] system freeze when switching to console
> 
> If you didn't see it, then that means that we have screw-ups with the 
> bugzilla thing. You're actually listed as a "Reviewed-by" on the
> commit that the fixed-up bisection blamed - And I get the feeling
> that Rafael's bugzilla "bugme" scripts may only pick up
> "Signed-off-by:" lines.

Reinette actually mailed me offlist about this; we corresponded
privately about this issue a month ago; I lost track of it while on
vacation (yeah I'm not on the cc lists for the bz or regression
updates).  Totally my fault.

Anyway the bisects look like they might just be lucky; it sounds like
this wasn't a KMS related issue at all...

> We have other bugs on the regression list that are even older (no,
> I'm not proud of them):
> 
> 	http://bugzilla.kernel.org/show_bug.cgi?id=13740

This one looks gfx related, upstream bug is
https://bugs.freedesktop.org/show_bug.cgi?id=23096.

The graphics group tracks freedesktop.org bugs on a weekly basis since
that's where a vast majority of our bugs our filed (often from OSVs);
I'll get the kernel bugzilla stuff included in our future scrubs so we
don't miss stuff like this.

-- 
Jesse Barnes, Intel Open Source Technology Center

Re: [Bug #13819] system freeze when switching to console

[reinette chatre]

On Tue, 2009-09-08 at 16:05 -0700, Jesse Barnes wrote:
> Any chance you could
> give it a try Reinette?

This patch also solves the issue for me. 

Tested-by: Reinette Chatre <reinette.chatre@intel.com>

Thank you very much

Reinette