2.6.36-rc6-git2: Reported regressions 2.6.34 -> 2.6.35

2.6.36-rc6-git2: Reported regressions 2.6.34 -> 2.6.35

[Rafael J. Wysocki]

This message contains a list of some post-2.6.34 regressions introduced before
2.6.35, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.

If you know of any other unresolved post-2.6.34 regressions, please let us know
either and we'll add them to the list.  Also, please let us 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
  ----------------------------------------
  2010-10-03      141       21          17
  2010-09-26      139       24          21
  2010-09-20      137       27          25
  2010-09-12      135       26          25
  2010-08-30      124       38          34
  2010-08-01      100       27          23
  2010-07-23       94       33          25
  2010-07-09       79       45          37
  2010-06-21       46       37          26
  2010-06-09       15       13          10


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19612
Subject		: Computer fails to hibernate - problem idling SMP CPU's
Submitter	:  <tempo444z@gmail.com>
Date		: 2010-10-02 22:26 (2 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19302
Subject		: PROBLEM: kernel crash on USB-modem (Huawei E1750) hangup.
Submitter	: O01eg <O01eg@yandex.ru>
Date		: 2010-09-26 19:50 (8 days old)
Message-ID	: <op.vjnn1up1yohvy1@localhost>
References	: http://marc.info/?l=linux-kernel&m=128553111709569&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=18522
Subject		: cdrom drive doesn't detect removal
Submitter	: Maxim Levitsky <maximlevitsky@gmail.com>
Date		: 2010-09-12 9:49 (22 days old)
First-Bad-Commit: http://git.kernel.org/linus/6b4517a7913a09d3259bb1d21c9cb300f12294bd
Message-ID	: <1284284969.2928.18.camel@maxim-laptop>
References	: http://marc.info/?l=linux-kernel&m=128428499013930&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17812
Subject		: Kernel completely frozen when memory is full
Submitter	: Mickey86 <mikael.cordon@gmail.com>
Date		: 2010-09-05 13:09 (29 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17261
Subject		: Freezes on bootup
Submitter	: Dan Dart <dandart@googlemail.com>
Date		: 2010-08-29 09:00 (36 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16891
Subject		: Kernel panic while loading intel module during boot
Submitter	: Anisse Astier <anisse@astier.eu>
Date		: 2010-08-24 13:19 (41 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16691
Subject		: IPW5100: iwlagn broken with 2.6.34.x to 2.6.35.2 update
Submitter	: Can Celasun <dcelasun@gmail.com>
Date		: 2010-08-21 08:28 (44 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16614
Subject		: [2.6.35] usb 2.0 em28xx  kernel panic general protection fault: 0000 [#1] SMP          RIP: 0010:[<ffffffffa004fbc5>]  [<ffffffffa004fbc5>] em28xx_isoc_copy_vbi+0x62e/0x812 [em28xx]
Submitter	: Sander Eikelenboom <linux@eikelenboom.it>
Date		: 2010-08-10 22:12 (55 days old)
Message-ID	: <61936849.20100811001257@eikelenboom.it>
References	: http://marc.info/?l=linux-kernel&m=128152075830927&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16562
Subject		: 2.6.35: cpu_idle bug report / on i7 870 cpu (x86_64)
Submitter	: Justin Piszcz <jpiszcz@lucidpixels.com>
Date		: 2010-08-06 22:09 (59 days old)
Message-ID	: <alpine.DEB.2.00.1008061800530.5241@p34.internal.lan>
References	: http://marc.info/?l=linux-kernel&m=128113260904048&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16549
Subject		: 2.6.35: suspicious rcu_dereference_check() usage
Submitter	: Vladislav Bolkhovitin <vst@vlnb.net>
Date		: 2010-08-04 10:56 (61 days old)
Message-ID	: <4C594740.1090608@vlnb.net>
References	: http://marc.info/?l=linux-kernel&m=128091938215177&w=2


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16525
Subject		: unexpected high load since 2.6.35
Submitter	: MadLoisae@gmx.net <MadLoisae@gmx.net>
Date		: 2010-08-02 20:53 (63 days old)
Message-ID	: <4C573041.1070103@gmx.net>
References	: http://marc.info/?l=linux-kernel&m=128078243726655&w=2
		  http://lkml.org/lkml/2010/9/14/105
		  http://lkml.org/lkml/2010/9/27/328


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16515
Subject		: [bisected] Radeon rv280 can't boot on kernel 2.6.35.
Submitter	: Albert Gall <ss3vdr@gmail.com>
Date		: 2010-08-04 16:10 (61 days old)
First-Bad-Commit: http://git.kernel.org/linus/https://bugzilla.kernel.org/attachment.cgi?id=27350
Handled-By	: Alex Deucher <alexdeucher@gmail.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16488
Subject		: [i915] Framebuffer ID error after suspend/hibernate leading to X crash
Submitter	: Milan Bouchet-Valat <nalimilan@club.fr>
Date		: 2010-08-01 08:55 (64 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16458
Subject		: Bluetooth disabled after resume
Submitter	: AttilaN <attila123456@gmail.com>
Date		: 2010-07-25 09:33 (71 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16380
Subject		: Loop devices act strangely in 2.6.35
Submitter	: Artem S. Tashkinov <t.artem@mailcity.com>
Date		: 2010-07-13 23:21 (83 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16265
Subject		: Why is kslowd accumulating so much CPU time?
Submitter	: Theodore Ts'o <tytso@mit.edu>
Date		: 2010-06-09 18:36 (117 days old)
First-Bad-Commit: http://git.kernel.org/linus/fbf81762e385d3d45acad057b654d56972acf58c
Message-ID	: <E1OMQ88-0002a1-Gb@closure.thunk.org>
References	: http://marc.info/?l=linux-kernel&m=127610857819033&w=4
		  http://bugs.freedesktop.org/show_bug.cgi?id=29536
Handled-By	: Chris Wilson <chris@chris-wilson.co.uk>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16221
Subject		: 2.6.35-rc2-git5 -- [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2010-06-11 20:31 (115 days old)
Message-ID	: <AANLkTim0jVRyqkwlGOcrg_XTvUQwcBYfWJX-aRzkkrLG@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127628828119623&w=2


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

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17772
Subject		: Unable to locate IOAPIC for GSI *
Submitter	: zersaa <zersaa@gmail.com>
Date		: 2010-09-04 21:28 (30 days old)
Handled-By	: Eric W. Biederman <ebiederm@xmission.com>
Patch		: https://patchwork.kernel.org/patch/104501/


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16462
Subject		: unable to connect to hidden SSID AP on legal channel 13
Submitter	: Daniel J Blueman <daniel.blueman@gmail.com>
Date		: 2010-07-25 17:06 (71 days old)
Handled-By	: Johannes Berg <johannes.berg@intel.com>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=31862


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16312
Subject		: WARNING: at fs/fs-writeback.c:1127 __mark_inode_dirty
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2010-06-28 9:40 (98 days old)
Message-ID	: <AANLkTin24fr5O4_q5Xbo9Y_NKkEmtcp6Hgmr9_4qXaFz@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127771804806465&w=2
		  http://lkml.indiana.edu/hypermail/linux/kernel/1007.3/00884.html
Handled-By	: Jan Kara <jack@suse.cz>
		  Jan Kara <jack@suse.cz>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=30282


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <brian.bloniarz@gmail.com>
Date		: 2010-06-16 17:57 (110 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>
Patch		: https://patchwork.kernel.org/patch/189182/
		  https://patchwork.kernel.org/patch/189232/
		  https://patchwork.kernel.org/patch/189242/
		  https://patchwork.kernel.org/patch/189252/


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 introduced
between 2.6.34 and 2.6.35, unresolved as well as resolved, at:

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

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

Thanks!

[Bug #16221] 2.6.35-rc2-git5 -- [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16221
Subject		: 2.6.35-rc2-git5 -- [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2010-06-11 20:31 (115 days old)
Message-ID	: <AANLkTim0jVRyqkwlGOcrg_XTvUQwcBYfWJX-aRzkkrLG@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127628828119623&w=2

[Bug #16312] WARNING: at fs/fs-writeback.c:1127 __mark_inode_dirty

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16312
Subject		: WARNING: at fs/fs-writeback.c:1127 __mark_inode_dirty
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2010-06-28 9:40 (98 days old)
Message-ID	: <AANLkTin24fr5O4_q5Xbo9Y_NKkEmtcp6Hgmr9_4qXaFz@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=127771804806465&w=2
		  http://lkml.indiana.edu/hypermail/linux/kernel/1007.3/00884.html
Handled-By	: Jan Kara <jack@suse.cz>
		  Jan Kara <jack@suse.cz>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=30282

[Bug #16380] Loop devices act strangely in 2.6.35

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16380
Subject		: Loop devices act strangely in 2.6.35
Submitter	: Artem S. Tashkinov <t.artem@mailcity.com>
Date		: 2010-07-13 23:21 (83 days old)

[Bug #16265] Why is kslowd accumulating so much CPU time?

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16265
Subject		: Why is kslowd accumulating so much CPU time?
Submitter	: Theodore Ts'o <tytso@mit.edu>
Date		: 2010-06-09 18:36 (117 days old)
First-Bad-Commit: http://git.kernel.org/linus/fbf81762e385d3d45acad057b654d56972acf58c
Message-ID	: <E1OMQ88-0002a1-Gb@closure.thunk.org>
References	: http://marc.info/?l=linux-kernel&m=127610857819033&w=4
		  http://bugs.freedesktop.org/show_bug.cgi?id=29536
Handled-By	: Chris Wilson <chris@chris-wilson.co.uk>

[Bug #16458] Bluetooth disabled after resume

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16458
Subject		: Bluetooth disabled after resume
Submitter	: AttilaN <attila123456@gmail.com>
Date		: 2010-07-25 09:33 (71 days old)

[Bug #16462] unable to connect to hidden SSID AP on legal channel 13

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16462
Subject		: unable to connect to hidden SSID AP on legal channel 13
Submitter	: Daniel J Blueman <daniel.blueman@gmail.com>
Date		: 2010-07-25 17:06 (71 days old)
Handled-By	: Johannes Berg <johannes.berg@intel.com>
Patch		: https://bugzilla.kernel.org/attachment.cgi?id=31862

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <brian.bloniarz@gmail.com>
Date		: 2010-06-16 17:57 (110 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>
Patch		: https://patchwork.kernel.org/patch/189182/
		  https://patchwork.kernel.org/patch/189232/
		  https://patchwork.kernel.org/patch/189242/
		  https://patchwork.kernel.org/patch/189252/

[Bug #16515] [bisected] Radeon rv280 can't boot on kernel 2.6.35.

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16515
Subject		: [bisected] Radeon rv280 can't boot on kernel 2.6.35.
Submitter	: Albert Gall <ss3vdr@gmail.com>
Date		: 2010-08-04 16:10 (61 days old)
First-Bad-Commit: http://git.kernel.org/linus/https://bugzilla.kernel.org/attachment.cgi?id=27350
Handled-By	: Alex Deucher <alexdeucher@gmail.com>

[Bug #16562] 2.6.35: cpu_idle bug report / on i7 870 cpu (x86_64)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16562
Subject		: 2.6.35: cpu_idle bug report / on i7 870 cpu (x86_64)
Submitter	: Justin Piszcz <jpiszcz@lucidpixels.com>
Date		: 2010-08-06 22:09 (59 days old)
Message-ID	: <alpine.DEB.2.00.1008061800530.5241@p34.internal.lan>
References	: http://marc.info/?l=linux-kernel&m=128113260904048&w=2

[Bug #16549] 2.6.35: suspicious rcu_dereference_check() usage

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16549
Subject		: 2.6.35: suspicious rcu_dereference_check() usage
Submitter	: Vladislav Bolkhovitin <vst@vlnb.net>
Date		: 2010-08-04 10:56 (61 days old)
Message-ID	: <4C594740.1090608@vlnb.net>
References	: http://marc.info/?l=linux-kernel&m=128091938215177&w=2

[Bug #16488] [i915] Framebuffer ID error after suspend/hibernate leading to X crash

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16488
Subject		: [i915] Framebuffer ID error after suspend/hibernate leading to X crash
Submitter	: Milan Bouchet-Valat <nalimilan@club.fr>
Date		: 2010-08-01 08:55 (64 days old)

[Bug #16525] unexpected high load since 2.6.35

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16525
Subject		: unexpected high load since 2.6.35
Submitter	: MadLoisae@gmx.net <MadLoisae@gmx.net>
Date		: 2010-08-02 20:53 (63 days old)
Message-ID	: <4C573041.1070103@gmx.net>
References	: http://marc.info/?l=linux-kernel&m=128078243726655&w=2
		  http://lkml.org/lkml/2010/9/14/105
		  http://lkml.org/lkml/2010/9/27/328

[Bug #16691] IPW5100: iwlagn broken with 2.6.34.x to 2.6.35.2 update

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16691
Subject		: IPW5100: iwlagn broken with 2.6.34.x to 2.6.35.2 update
Submitter	: Can Celasun <dcelasun@gmail.com>
Date		: 2010-08-21 08:28 (44 days old)

[Bug #16614] [2.6.35] usb 2.0 em28xx kernel panic general protection fault: 0000 [#1] SMP RIP: 0010:[<ffffffffa004fbc5>] [<ffffffffa004fbc5>] em28xx_isoc_copy_vbi+0x62e/0x812 [em28xx]

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16614
Subject		: [2.6.35] usb 2.0 em28xx  kernel panic general protection fault: 0000 [#1] SMP          RIP: 0010:[<ffffffffa004fbc5>]  [<ffffffffa004fbc5>] em28xx_isoc_copy_vbi+0x62e/0x812 [em28xx]
Submitter	: Sander Eikelenboom <linux@eikelenboom.it>
Date		: 2010-08-10 22:12 (55 days old)
Message-ID	: <61936849.20100811001257@eikelenboom.it>
References	: http://marc.info/?l=linux-kernel&m=128152075830927&w=2

[Bug #16891] Kernel panic while loading intel module during boot

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16891
Subject		: Kernel panic while loading intel module during boot
Submitter	: Anisse Astier <anisse@astier.eu>
Date		: 2010-08-24 13:19 (41 days old)

[Bug #17261] Freezes on bootup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17261
Subject		: Freezes on bootup
Submitter	: Dan Dart <dandart@googlemail.com>
Date		: 2010-08-29 09:00 (36 days old)

[Bug #17772] Unable to locate IOAPIC for GSI *

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17772
Subject		: Unable to locate IOAPIC for GSI *
Submitter	: zersaa <zersaa@gmail.com>
Date		: 2010-09-04 21:28 (30 days old)
Handled-By	: Eric W. Biederman <ebiederm@xmission.com>
Patch		: https://patchwork.kernel.org/patch/104501/

[Bug #18522] cdrom drive doesn't detect removal

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=18522
Subject		: cdrom drive doesn't detect removal
Submitter	: Maxim Levitsky <maximlevitsky@gmail.com>
Date		: 2010-09-12 9:49 (22 days old)
First-Bad-Commit: http://git.kernel.org/linus/6b4517a7913a09d3259bb1d21c9cb300f12294bd
Message-ID	: <1284284969.2928.18.camel@maxim-laptop>
References	: http://marc.info/?l=linux-kernel&m=128428499013930&w=2

[Bug #17812] Kernel completely frozen when memory is full

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17812
Subject		: Kernel completely frozen when memory is full
Submitter	: Mickey86 <mikael.cordon@gmail.com>
Date		: 2010-09-05 13:09 (29 days old)

[Bug #19302] PROBLEM: kernel crash on USB-modem (Huawei E1750) hangup.

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19302
Subject		: PROBLEM: kernel crash on USB-modem (Huawei E1750) hangup.
Submitter	: O01eg <O01eg@yandex.ru>
Date		: 2010-09-26 19:50 (8 days old)
Message-ID	: <op.vjnn1up1yohvy1@localhost>
References	: http://marc.info/?l=linux-kernel&m=128553111709569&w=2

[Bug #19612] Computer fails to hibernate - problem idling SMP CPU's

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19612
Subject		: Computer fails to hibernate - problem idling SMP CPU's
Submitter	:  <tempo444z@gmail.com>
Date		: 2010-10-02 22:26 (2 days old)

Re: [Bug #16462] unable to connect to hidden SSID AP on legal channel 13

[Daniel J Blueman]

Hi Rafael,

On 3 October 2010 22:53, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.34 and 2.6.35.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.34 and 2.6.35.  Please verify if it still should
> be listed and let the tracking team know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=16462
> Subject         : unable to connect to hidden SSID AP on legal channel 13
> Submitter       : Daniel J Blueman <daniel.blueman@gmail.com>
> Date            : 2010-07-25 17:06 (71 days old)
> Handled-By      : Johannes Berg <johannes.berg@intel.com>
> Patch           : https://bugzilla.kernel.org/attachment.cgi?id=31862

This patch addresses the issue, though it hasn't been pulled to mainline yet.

Many thanks,
  Daniel
-- 
Daniel J Blueman

Re: [Bug #16891] Kernel panic while loading intel module during boot

[Anisse Astier]

On Sun,  3 Oct 2010 23:53:02 +0200 (CEST), "Rafael J. Wysocki" <rjw@sisk.pl> wrote :

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.34 and 2.6.35.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.34 and 2.6.35.  Please verify if it still should
> be listed and let the tracking team know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16891
> Subject		: Kernel panic while loading intel module during boot
> Submitter	: Anisse Astier <anisse@astier.eu>
> Date		: 2010-08-24 13:19 (41 days old)
> 
> 

This bug is still valid, and should be listed as a regression.
I tried to upload on bugzilla a patch authored by Daniel Vetter that fixes
the problem, but then bugzilla went into blackhole mode.

I'll provide this patch here in the meantime in case anyone is interested.

Regards,
Anisse

---
From: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Fri, 1 Oct 2010 19:52:09 +0200
Subject: [PATCH] intel-gtt: fix 2.6.35 regression

Port of commit "intel-gtt: fix gtt_total_entries detection" to 2.6.35.

Also adds PINEVIEW_IG to IS_G33 detection list

Signed-off-by: Anisse Astier <anisse@astier.eu>
---
 drivers/char/agp/intel-agp.h |    1 +
 drivers/char/agp/intel-gtt.c |   63 ++++++++++++++++++------------------------
 2 files changed, 28 insertions(+), 36 deletions(-)

diff --git a/drivers/char/agp/intel-agp.h b/drivers/char/agp/intel-agp.h
index bc9a4ad..2fbbe63 100644
--- a/drivers/char/agp/intel-agp.h
+++ b/drivers/char/agp/intel-agp.h
@@ -226,6 +226,7 @@
 		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_Q35_HB || \
 		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_Q33_HB || \
 		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_M_HB || \
+		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_IG || \
 		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_HB)
 
 #define IS_PINEVIEW (agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_M_HB || \
diff --git a/drivers/char/agp/intel-gtt.c b/drivers/char/agp/intel-gtt.c
index ed11c77..ea18f64 100644
--- a/drivers/char/agp/intel-gtt.c
+++ b/drivers/char/agp/intel-gtt.c
@@ -501,7 +501,7 @@ static void intel_i830_init_gtt_entries(void)
 
 	pci_read_config_word(agp_bridge->dev, I830_GMCH_CTRL, &gmch_ctrl);
 
-	if (IS_I965) {
+	if (IS_G33 || IS_I965) {
 		u32 pgetbl_ctl;
 		pgetbl_ctl = readl(intel_private.registers+I810_PGETBL_CTL);
 
@@ -534,22 +534,6 @@ static void intel_i830_init_gtt_entries(void)
 			size = 512;
 		}
 		size += 4; /* add in BIOS popup space */
-	} else if (IS_G33 && !IS_PINEVIEW) {
-	/* G33's GTT size defined in gmch_ctrl */
-		switch (gmch_ctrl & G33_PGETBL_SIZE_MASK) {
-		case G33_PGETBL_SIZE_1M:
-			size = 1024;
-			break;
-		case G33_PGETBL_SIZE_2M:
-			size = 2048;
-			break;
-		default:
-			dev_info(&agp_bridge->dev->dev,
-				 "unknown page table size 0x%x, assuming 512KB\n",
-				(gmch_ctrl & G33_PGETBL_SIZE_MASK));
-			size = 512;
-		}
-		size += 4;
 	} else if (IS_G4X || IS_PINEVIEW) {
 		/* On 4 series hardware, GTT stolen is separate from graphics
 		 * stolen, ignore it in stolen gtt entries counting.  However,
@@ -1220,24 +1204,31 @@ static int intel_i915_get_gtt_size(void)
 	int size;
 
 	if (IS_G33) {
-		u16 gmch_ctrl;
+		u32 pgetbl_ctl;
+		pgetbl_ctl = readl(intel_private.registers+I810_PGETBL_CTL);
 
-		/* G33's GTT size defined in gmch_ctrl */
-		pci_read_config_word(agp_bridge->dev, I830_GMCH_CTRL, &gmch_ctrl);
-		switch (gmch_ctrl & I830_GMCH_GMS_MASK) {
-		case I830_GMCH_GMS_STOLEN_512:
+		switch (pgetbl_ctl & I965_PGETBL_SIZE_MASK) {
+		case I965_PGETBL_SIZE_128KB:
+			size = 128;
+			break;
+		case I965_PGETBL_SIZE_256KB:
+			size = 256;
+			break;
+		case I965_PGETBL_SIZE_512KB:
 			size = 512;
 			break;
-		case I830_GMCH_GMS_STOLEN_1024:
+		case I965_PGETBL_SIZE_1MB:
 			size = 1024;
 			break;
-		case I830_GMCH_GMS_STOLEN_8192:
-			size = 8*1024;
+		case I965_PGETBL_SIZE_2MB:
+			size = 2048;
+			break;
+		case I965_PGETBL_SIZE_1_5MB:
+			size = 1024 + 512;
 			break;
 		default:
-			dev_info(&agp_bridge->dev->dev,
-				 "unknown page table size 0x%x, assuming 512KB\n",
-				(gmch_ctrl & I830_GMCH_GMS_MASK));
+			dev_info(&intel_private.pcidev->dev,
+				 "unknown page table size, assuming 512KB\n");
 			size = 512;
 		}
 	} else {
@@ -1269,14 +1260,6 @@ static int intel_i915_create_gatt_table(struct agp_bridge_data *bridge)
 	pci_read_config_dword(intel_private.pcidev, I915_MMADDR, &temp);
 	pci_read_config_dword(intel_private.pcidev, I915_PTEADDR, &temp2);
 
-	gtt_map_size = intel_i915_get_gtt_size();
-
-	intel_private.gtt = ioremap(temp2, gtt_map_size);
-	if (!intel_private.gtt)
-		return -ENOMEM;
-
-	intel_private.gtt_total_size = gtt_map_size / 4;
-
 	temp &= 0xfff80000;
 
 	intel_private.registers = ioremap(temp, 128 * 4096);
@@ -1285,6 +1268,14 @@ static int intel_i915_create_gatt_table(struct agp_bridge_data *bridge)
 		return -ENOMEM;
 	}
 
+	gtt_map_size = intel_i915_get_gtt_size();
+
+	intel_private.gtt = ioremap(temp2, gtt_map_size);
+	if (!intel_private.gtt)
+		return -ENOMEM;
+
+	intel_private.gtt_total_size = gtt_map_size / 4;
+
 	temp = readl(intel_private.registers+I810_PGETBL_CTL) & 0xfffff000;
 	global_cache_flush();	/* FIXME: ? */
 
-- 
1.7.0.6

Re: 2.6.36-rc6-git2: Reported regressions 2.6.34 -> 2.6.35

[Rafał Miłecki]

2010/10/3 Rafael J. Wysocki <rjw@sisk.pl>:
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=19302
> Subject         : PROBLEM: kernel crash on USB-modem (Huawei E1750) hangup.
> Submitter       : O01eg <O01eg@yandex.ru>
> Date            : 2010-09-26 19:50 (8 days old)
> Message-ID      : <op.vjnn1up1yohvy1@localhost>
> References      : http://marc.info/?l=linux-kernel&m=128553111709569&w=2

Comment from bugzilla:
> I got this bug at 2.6.34-gentoo-r6 and 2.6.36-rc5. Other kernels were not
> checked.

Doesn't sound like regression.

-- 
Rafał

Re: [Bug #16891] Kernel panic while loading intel module during boot

[Rafael J. Wysocki]

On Monday, October 04, 2010, Anisse Astier wrote:
> On Sun,  3 Oct 2010 23:53:02 +0200 (CEST), "Rafael J. Wysocki" <rjw@sisk.pl> wrote :
> 
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.34 and 2.6.35.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.34 and 2.6.35.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16891
> > Subject		: Kernel panic while loading intel module during boot
> > Submitter	: Anisse Astier <anisse@astier.eu>
> > Date		: 2010-08-24 13:19 (41 days old)
> > 
> > 
> 
> This bug is still valid, and should be listed as a regression.
> I tried to upload on bugzilla a patch authored by Daniel Vetter that fixes
> the problem, but then bugzilla went into blackhole mode.
> 
> I'll provide this patch here in the meantime in case anyone is interested.

Thanks for the update and the patch.

Well, I wonder who's going to merge it?

Rafael


> ---
> From: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Fri, 1 Oct 2010 19:52:09 +0200
> Subject: [PATCH] intel-gtt: fix 2.6.35 regression
> 
> Port of commit "intel-gtt: fix gtt_total_entries detection" to 2.6.35.
> 
> Also adds PINEVIEW_IG to IS_G33 detection list
> 
> Signed-off-by: Anisse Astier <anisse@astier.eu>
> ---
>  drivers/char/agp/intel-agp.h |    1 +
>  drivers/char/agp/intel-gtt.c |   63 ++++++++++++++++++------------------------
>  2 files changed, 28 insertions(+), 36 deletions(-)
> 
> diff --git a/drivers/char/agp/intel-agp.h b/drivers/char/agp/intel-agp.h
> index bc9a4ad..2fbbe63 100644
> --- a/drivers/char/agp/intel-agp.h
> +++ b/drivers/char/agp/intel-agp.h
> @@ -226,6 +226,7 @@
>  		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_Q35_HB || \
>  		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_Q33_HB || \
>  		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_M_HB || \
> +		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_IG || \
>  		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_HB)
>  
>  #define IS_PINEVIEW (agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_M_HB || \
> diff --git a/drivers/char/agp/intel-gtt.c b/drivers/char/agp/intel-gtt.c
> index ed11c77..ea18f64 100644
> --- a/drivers/char/agp/intel-gtt.c
> +++ b/drivers/char/agp/intel-gtt.c
> @@ -501,7 +501,7 @@ static void intel_i830_init_gtt_entries(void)
>  
>  	pci_read_config_word(agp_bridge->dev, I830_GMCH_CTRL, &gmch_ctrl);
>  
> -	if (IS_I965) {
> +	if (IS_G33 || IS_I965) {
>  		u32 pgetbl_ctl;
>  		pgetbl_ctl = readl(intel_private.registers+I810_PGETBL_CTL);
>  
> @@ -534,22 +534,6 @@ static void intel_i830_init_gtt_entries(void)
>  			size = 512;
>  		}
>  		size += 4; /* add in BIOS popup space */
> -	} else if (IS_G33 && !IS_PINEVIEW) {
> -	/* G33's GTT size defined in gmch_ctrl */
> -		switch (gmch_ctrl & G33_PGETBL_SIZE_MASK) {
> -		case G33_PGETBL_SIZE_1M:
> -			size = 1024;
> -			break;
> -		case G33_PGETBL_SIZE_2M:
> -			size = 2048;
> -			break;
> -		default:
> -			dev_info(&agp_bridge->dev->dev,
> -				 "unknown page table size 0x%x, assuming 512KB\n",
> -				(gmch_ctrl & G33_PGETBL_SIZE_MASK));
> -			size = 512;
> -		}
> -		size += 4;
>  	} else if (IS_G4X || IS_PINEVIEW) {
>  		/* On 4 series hardware, GTT stolen is separate from graphics
>  		 * stolen, ignore it in stolen gtt entries counting.  However,
> @@ -1220,24 +1204,31 @@ static int intel_i915_get_gtt_size(void)
>  	int size;
>  
>  	if (IS_G33) {
> -		u16 gmch_ctrl;
> +		u32 pgetbl_ctl;
> +		pgetbl_ctl = readl(intel_private.registers+I810_PGETBL_CTL);
>  
> -		/* G33's GTT size defined in gmch_ctrl */
> -		pci_read_config_word(agp_bridge->dev, I830_GMCH_CTRL, &gmch_ctrl);
> -		switch (gmch_ctrl & I830_GMCH_GMS_MASK) {
> -		case I830_GMCH_GMS_STOLEN_512:
> +		switch (pgetbl_ctl & I965_PGETBL_SIZE_MASK) {
> +		case I965_PGETBL_SIZE_128KB:
> +			size = 128;
> +			break;
> +		case I965_PGETBL_SIZE_256KB:
> +			size = 256;
> +			break;
> +		case I965_PGETBL_SIZE_512KB:
>  			size = 512;
>  			break;
> -		case I830_GMCH_GMS_STOLEN_1024:
> +		case I965_PGETBL_SIZE_1MB:
>  			size = 1024;
>  			break;
> -		case I830_GMCH_GMS_STOLEN_8192:
> -			size = 8*1024;
> +		case I965_PGETBL_SIZE_2MB:
> +			size = 2048;
> +			break;
> +		case I965_PGETBL_SIZE_1_5MB:
> +			size = 1024 + 512;
>  			break;
>  		default:
> -			dev_info(&agp_bridge->dev->dev,
> -				 "unknown page table size 0x%x, assuming 512KB\n",
> -				(gmch_ctrl & I830_GMCH_GMS_MASK));
> +			dev_info(&intel_private.pcidev->dev,
> +				 "unknown page table size, assuming 512KB\n");
>  			size = 512;
>  		}
>  	} else {
> @@ -1269,14 +1260,6 @@ static int intel_i915_create_gatt_table(struct agp_bridge_data *bridge)
>  	pci_read_config_dword(intel_private.pcidev, I915_MMADDR, &temp);
>  	pci_read_config_dword(intel_private.pcidev, I915_PTEADDR, &temp2);
>  
> -	gtt_map_size = intel_i915_get_gtt_size();
> -
> -	intel_private.gtt = ioremap(temp2, gtt_map_size);
> -	if (!intel_private.gtt)
> -		return -ENOMEM;
> -
> -	intel_private.gtt_total_size = gtt_map_size / 4;
> -
>  	temp &= 0xfff80000;
>  
>  	intel_private.registers = ioremap(temp, 128 * 4096);
> @@ -1285,6 +1268,14 @@ static int intel_i915_create_gatt_table(struct agp_bridge_data *bridge)
>  		return -ENOMEM;
>  	}
>  
> +	gtt_map_size = intel_i915_get_gtt_size();
> +
> +	intel_private.gtt = ioremap(temp2, gtt_map_size);
> +	if (!intel_private.gtt)
> +		return -ENOMEM;
> +
> +	intel_private.gtt_total_size = gtt_map_size / 4;
> +
>  	temp = readl(intel_private.registers+I810_PGETBL_CTL) & 0xfffff000;
>  	global_cache_flush();	/* FIXME: ? */
>  
> 

Re: [Bug #16891] Kernel panic while loading intel module during boot

[Rafael J. Wysocki]

On Monday, October 04, 2010, Rafael J. Wysocki wrote:
> On Monday, October 04, 2010, Anisse Astier wrote:
> > On Sun,  3 Oct 2010 23:53:02 +0200 (CEST), "Rafael J. Wysocki" <rjw@sisk.pl> wrote :
> > 
> > > This message has been generated automatically as a part of a report
> > > of regressions introduced between 2.6.34 and 2.6.35.
> > > 
> > > The following bug entry is on the current list of known regressions
> > > introduced between 2.6.34 and 2.6.35.  Please verify if it still should
> > > be listed and let the tracking team know (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16891
> > > Subject		: Kernel panic while loading intel module during boot
> > > Submitter	: Anisse Astier <anisse@astier.eu>
> > > Date		: 2010-08-24 13:19 (41 days old)
> > > 
> > > 
> > 
> > This bug is still valid, and should be listed as a regression.
> > I tried to upload on bugzilla a patch authored by Daniel Vetter that fixes
> > the problem, but then bugzilla went into blackhole mode.
> > 
> > I'll provide this patch here in the meantime in case anyone is interested.
> 
> Thanks for the update and the patch.
> 
> Well, I wonder who's going to merge it?

Chris, can you please have a look?

Thanks,
Rafael


> > ---
> > From: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date: Fri, 1 Oct 2010 19:52:09 +0200
> > Subject: [PATCH] intel-gtt: fix 2.6.35 regression
> > 
> > Port of commit "intel-gtt: fix gtt_total_entries detection" to 2.6.35.
> > 
> > Also adds PINEVIEW_IG to IS_G33 detection list
> > 
> > Signed-off-by: Anisse Astier <anisse@astier.eu>
> > ---
> >  drivers/char/agp/intel-agp.h |    1 +
> >  drivers/char/agp/intel-gtt.c |   63 ++++++++++++++++++------------------------
> >  2 files changed, 28 insertions(+), 36 deletions(-)
> > 
> > diff --git a/drivers/char/agp/intel-agp.h b/drivers/char/agp/intel-agp.h
> > index bc9a4ad..2fbbe63 100644
> > --- a/drivers/char/agp/intel-agp.h
> > +++ b/drivers/char/agp/intel-agp.h
> > @@ -226,6 +226,7 @@
> >  		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_Q35_HB || \
> >  		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_Q33_HB || \
> >  		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_M_HB || \
> > +		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_IG || \
> >  		agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_HB)
> >  
> >  #define IS_PINEVIEW (agp_bridge->dev->device == PCI_DEVICE_ID_INTEL_PINEVIEW_M_HB || \
> > diff --git a/drivers/char/agp/intel-gtt.c b/drivers/char/agp/intel-gtt.c
> > index ed11c77..ea18f64 100644
> > --- a/drivers/char/agp/intel-gtt.c
> > +++ b/drivers/char/agp/intel-gtt.c
> > @@ -501,7 +501,7 @@ static void intel_i830_init_gtt_entries(void)
> >  
> >  	pci_read_config_word(agp_bridge->dev, I830_GMCH_CTRL, &gmch_ctrl);
> >  
> > -	if (IS_I965) {
> > +	if (IS_G33 || IS_I965) {
> >  		u32 pgetbl_ctl;
> >  		pgetbl_ctl = readl(intel_private.registers+I810_PGETBL_CTL);
> >  
> > @@ -534,22 +534,6 @@ static void intel_i830_init_gtt_entries(void)
> >  			size = 512;
> >  		}
> >  		size += 4; /* add in BIOS popup space */
> > -	} else if (IS_G33 && !IS_PINEVIEW) {
> > -	/* G33's GTT size defined in gmch_ctrl */
> > -		switch (gmch_ctrl & G33_PGETBL_SIZE_MASK) {
> > -		case G33_PGETBL_SIZE_1M:
> > -			size = 1024;
> > -			break;
> > -		case G33_PGETBL_SIZE_2M:
> > -			size = 2048;
> > -			break;
> > -		default:
> > -			dev_info(&agp_bridge->dev->dev,
> > -				 "unknown page table size 0x%x, assuming 512KB\n",
> > -				(gmch_ctrl & G33_PGETBL_SIZE_MASK));
> > -			size = 512;
> > -		}
> > -		size += 4;
> >  	} else if (IS_G4X || IS_PINEVIEW) {
> >  		/* On 4 series hardware, GTT stolen is separate from graphics
> >  		 * stolen, ignore it in stolen gtt entries counting.  However,
> > @@ -1220,24 +1204,31 @@ static int intel_i915_get_gtt_size(void)
> >  	int size;
> >  
> >  	if (IS_G33) {
> > -		u16 gmch_ctrl;
> > +		u32 pgetbl_ctl;
> > +		pgetbl_ctl = readl(intel_private.registers+I810_PGETBL_CTL);
> >  
> > -		/* G33's GTT size defined in gmch_ctrl */
> > -		pci_read_config_word(agp_bridge->dev, I830_GMCH_CTRL, &gmch_ctrl);
> > -		switch (gmch_ctrl & I830_GMCH_GMS_MASK) {
> > -		case I830_GMCH_GMS_STOLEN_512:
> > +		switch (pgetbl_ctl & I965_PGETBL_SIZE_MASK) {
> > +		case I965_PGETBL_SIZE_128KB:
> > +			size = 128;
> > +			break;
> > +		case I965_PGETBL_SIZE_256KB:
> > +			size = 256;
> > +			break;
> > +		case I965_PGETBL_SIZE_512KB:
> >  			size = 512;
> >  			break;
> > -		case I830_GMCH_GMS_STOLEN_1024:
> > +		case I965_PGETBL_SIZE_1MB:
> >  			size = 1024;
> >  			break;
> > -		case I830_GMCH_GMS_STOLEN_8192:
> > -			size = 8*1024;
> > +		case I965_PGETBL_SIZE_2MB:
> > +			size = 2048;
> > +			break;
> > +		case I965_PGETBL_SIZE_1_5MB:
> > +			size = 1024 + 512;
> >  			break;
> >  		default:
> > -			dev_info(&agp_bridge->dev->dev,
> > -				 "unknown page table size 0x%x, assuming 512KB\n",
> > -				(gmch_ctrl & I830_GMCH_GMS_MASK));
> > +			dev_info(&intel_private.pcidev->dev,
> > +				 "unknown page table size, assuming 512KB\n");
> >  			size = 512;
> >  		}
> >  	} else {
> > @@ -1269,14 +1260,6 @@ static int intel_i915_create_gatt_table(struct agp_bridge_data *bridge)
> >  	pci_read_config_dword(intel_private.pcidev, I915_MMADDR, &temp);
> >  	pci_read_config_dword(intel_private.pcidev, I915_PTEADDR, &temp2);
> >  
> > -	gtt_map_size = intel_i915_get_gtt_size();
> > -
> > -	intel_private.gtt = ioremap(temp2, gtt_map_size);
> > -	if (!intel_private.gtt)
> > -		return -ENOMEM;
> > -
> > -	intel_private.gtt_total_size = gtt_map_size / 4;
> > -
> >  	temp &= 0xfff80000;
> >  
> >  	intel_private.registers = ioremap(temp, 128 * 4096);
> > @@ -1285,6 +1268,14 @@ static int intel_i915_create_gatt_table(struct agp_bridge_data *bridge)
> >  		return -ENOMEM;
> >  	}
> >  
> > +	gtt_map_size = intel_i915_get_gtt_size();
> > +
> > +	intel_private.gtt = ioremap(temp2, gtt_map_size);
> > +	if (!intel_private.gtt)
> > +		return -ENOMEM;
> > +
> > +	intel_private.gtt_total_size = gtt_map_size / 4;
> > +
> >  	temp = readl(intel_private.registers+I810_PGETBL_CTL) & 0xfffff000;
> >  	global_cache_flush();	/* FIXME: ? */
> >  
> > 

Re: [Bug #16891] Kernel panic while loading intel module during boot

[Anisse Astier]

On Mon, Oct 4, 2010 at 9:42 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>> I'll provide this patch here in the meantime in case anyone is interested.
>
> Thanks for the update and the patch.
>
> Well, I wonder who's going to merge it?
>

I'm not sure is going to be merged because most of this code has been
re-written and has been sitting in drm-intel-next for a few weeks now.
This (welcome) rewrite will likely be merged in 2.6.37 (but I can't
speak for Chris).

This is a port of this patch:
http://git.kernel.org/?p=linux/kernel/git/ickle/drm-intel.git;a=commit;h=e5e408fc94595aab897f613b6f4e2f5b36870a6f
, but on completely different code.

Also this patch is new and didn't see much testing (I tested on 4
different Intel GPUs, belonging only to 2 different families); if it's
not merged for 2.6.36, it won't be for 2.6.37 (the new code will land
first). If that happens, it might not meet conditions to be accepted
in -stable (being in linus' tree first).



Anisse

Re: [Bug #16891] Kernel panic while loading intel module during boot

[Rafael J. Wysocki]

On Monday, October 04, 2010, Anisse Astier wrote:
> On Mon, Oct 4, 2010 at 9:42 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> I'll provide this patch here in the meantime in case anyone is interested.
> >
> > Thanks for the update and the patch.
> >
> > Well, I wonder who's going to merge it?
> >
> 
> I'm not sure is going to be merged because most of this code has been
> re-written and has been sitting in drm-intel-next for a few weeks now.
> This (welcome) rewrite will likely be merged in 2.6.37 (but I can't
> speak for Chris).
> 
> This is a port of this patch:
> http://git.kernel.org/?p=linux/kernel/git/ickle/drm-intel.git;a=commit;h=e5e408fc94595aab897f613b6f4e2f5b36870a6f
> , but on completely different code.
> 
> Also this patch is new and didn't see much testing (I tested on 4
> different Intel GPUs, belonging only to 2 different families); if it's
> not merged for 2.6.36, it won't be for 2.6.37 (the new code will land
> first). If that happens, it might not meet conditions to be accepted
> in -stable (being in linus' tree first).

It's a panic fix, so I think it is -stable material anyway.  Greg?

Thanks,
Rafael

Re: [Bug #16891] Kernel panic while loading intel module during boot

[Greg KH]

On Tue, Oct 05, 2010 at 12:40:59AM +0200, Rafael J. Wysocki wrote:
> On Monday, October 04, 2010, Anisse Astier wrote:
> > On Mon, Oct 4, 2010 at 9:42 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > >> I'll provide this patch here in the meantime in case anyone is interested.
> > >
> > > Thanks for the update and the patch.
> > >
> > > Well, I wonder who's going to merge it?
> > >
> > 
> > I'm not sure is going to be merged because most of this code has been
> > re-written and has been sitting in drm-intel-next for a few weeks now.
> > This (welcome) rewrite will likely be merged in 2.6.37 (but I can't
> > speak for Chris).
> > 
> > This is a port of this patch:
> > http://git.kernel.org/?p=linux/kernel/git/ickle/drm-intel.git;a=commit;h=e5e408fc94595aab897f613b6f4e2f5b36870a6f
> > , but on completely different code.
> > 
> > Also this patch is new and didn't see much testing (I tested on 4
> > different Intel GPUs, belonging only to 2 different families); if it's
> > not merged for 2.6.36, it won't be for 2.6.37 (the new code will land
> > first). If that happens, it might not meet conditions to be accepted
> > in -stable (being in linus' tree first).
> 
> It's a panic fix, so I think it is -stable material anyway.  Greg?

That sounds good, please cc: stable@kernel.org with the proper
information for this (git commit id, patch info, etc.)

thanks,

greg k-h

Re: [Bug #16891] Kernel panic while loading intel module during boot

[Daniel Vetter]

On Tue, Oct 05, 2010 at 06:28:29AM -0700, Greg KH wrote:
> On Tue, Oct 05, 2010 at 12:40:59AM +0200, Rafael J. Wysocki wrote:
> > On Monday, October 04, 2010, Anisse Astier wrote:
> > > Also this patch is new and didn't see much testing (I tested on 4
> > > different Intel GPUs, belonging only to 2 different families); if it's
> > > not merged for 2.6.36, it won't be for 2.6.37 (the new code will land
> > > first). If that happens, it might not meet conditions to be accepted
> > > in -stable (being in linus' tree first).
> > 
> > It's a panic fix, so I think it is -stable material anyway.  Greg?
> 
> That sounds good, please cc: stable@kernel.org with the proper
> information for this (git commit id, patch info, etc.)

I'll do that as soon as drm-intel-next has hit -linus. I've written the
original fix and marked it cc: stable so it won't get lost. I've been
rather cautious with pushing this because it's the 3rd trial to fix a bug
in late .35-rc. The previous fixes already caused regressions in -stable
and I'd simply like to avoid causing yet another regression over the same
problem.

Yours, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <brian.bloniarz@gmail.com>
Date		: 2010-06-16 17:57 (124 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>
Patch		: https://patchwork.kernel.org/patch/189182/
		  https://patchwork.kernel.org/patch/189232/
		  https://patchwork.kernel.org/patch/189242/
		  https://patchwork.kernel.org/patch/189252/

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <brian.bloniarz@gmail.com>
Date		: 2010-06-16 17:57 (117 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>
Patch		: https://patchwork.kernel.org/patch/189182/
		  https://patchwork.kernel.org/patch/189232/
		  https://patchwork.kernel.org/patch/189242/
		  https://patchwork.kernel.org/patch/189252/

Re: [Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

On Monday, September 27, 2010, Bjorn Helgaas wrote:
> On Sunday, September 26, 2010 02:33:08 pm Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.34 and 2.6.35.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.34 and 2.6.35.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
> > Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
> > Submitter	: Brian Bloniarz <brian.bloniarz@gmail.com>
> > Date		: 2010-06-16 17:57 (103 days old)
> > Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>
> > Patch		: https://patchwork.kernel.org/patch/189182/
> > 		  https://patchwork.kernel.org/patch/189232/
> > 		  https://patchwork.kernel.org/patch/189242/
> > 		  https://patchwork.kernel.org/patch/189252/
> 
> We plan to merge this patches soon after the 2.6.36 release, so
> this regression will still exist in 2.6.36.

Thanks for the info.

The bug is going to be listed until 2.6.36 is released, then.

Rafael

Re: [Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Bjorn Helgaas]

On Sunday, September 26, 2010 02:33:08 pm Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.34 and 2.6.35.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.34 and 2.6.35.  Please verify if it still should
> be listed and let the tracking team know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
> Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
> Submitter	: Brian Bloniarz <brian.bloniarz@gmail.com>
> Date		: 2010-06-16 17:57 (103 days old)
> Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>
> Patch		: https://patchwork.kernel.org/patch/189182/
> 		  https://patchwork.kernel.org/patch/189232/
> 		  https://patchwork.kernel.org/patch/189242/
> 		  https://patchwork.kernel.org/patch/189252/

We plan to merge this patches soon after the 2.6.36 release, so
this regression will still exist in 2.6.36.

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <brian.bloniarz@gmail.com>
Date		: 2010-06-16 17:57 (103 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>
Patch		: https://patchwork.kernel.org/patch/189182/
		  https://patchwork.kernel.org/patch/189232/
		  https://patchwork.kernel.org/patch/189242/
		  https://patchwork.kernel.org/patch/189252/

Re: [Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

On Monday, September 20, 2010, Bjorn Helgaas wrote:
> On Monday, September 20, 2010 01:57:17 pm Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.34 and 2.6.35.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.34 and 2.6.35.  Please verify if it still should
> > be listed and let the tracking team know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
> > Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
> > Submitter	: Brian Bloniarz <brian.bloniarz@gmail.com>
> > Date		: 2010-06-16 17:57 (97 days old)
> > Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>
> 
> The four patches here: https://patchwork.kernel.org/patch/189182/
> should resolve this problem.  They've been tested by Stefan Becker.

Thanks, bug entry updated with the patch information.

Rafael

Re: [Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Bjorn Helgaas]

On Monday, September 20, 2010 01:57:17 pm Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.34 and 2.6.35.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.34 and 2.6.35.  Please verify if it still should
> be listed and let the tracking team know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
> Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
> Submitter	: Brian Bloniarz <brian.bloniarz@gmail.com>
> Date		: 2010-06-16 17:57 (97 days old)
> Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>

The four patches here: https://patchwork.kernel.org/patch/189182/
should resolve this problem.  They've been tested by Stefan Becker.

Bjorn

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <brian.bloniarz@gmail.com>
Date		: 2010-06-16 17:57 (97 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <phunge0@hotmail.com>
Date		: 2010-06-16 17:57 (89 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.

The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35.  Please verify if it still should
be listed and let the tracking team know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <phunge0@hotmail.com>
Date		: 2010-06-16 17:57 (75 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>

Re: [Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Bjorn Helgaas]

On Sunday, August 01, 2010 07:52:16 am Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.34.  Please verify if it still should be listed and let the tracking team
> know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
> Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
> Submitter	: Brian Bloniarz <phunge0@hotmail.com>
> Date		: 2010-06-16 17:57 (47 days old)
> Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>

This bug should still be on the list.  I hope to work on it this week.

Bjorn

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <phunge0@hotmail.com>
Date		: 2010-06-16 17:57 (47 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <phunge0@hotmail.com>
Date		: 2010-06-16 17:57 (38 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <phunge0@hotmail.com>
Date		: 2010-06-16 17:57 (23 days old)
Handled-By	: Bjorn Helgaas <bjorn.helgaas@hp.com>

[Bug #16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Rafael J. Wysocki]

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

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


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=16228
Subject		: BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)
Submitter	: Brian Bloniarz <phunge0@hotmail.com>
Date		: 2010-06-16 17:57 (5 days old)

Re: [Bug 16228] BUG/boot failure on Dell Precision T3500 (pci/ahci_stop_engine)

[Yinghai Lu]

On 06/17/2010 09:37 AM, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=16228
> 
> 
> Bjorn Helgaas <bjorn.helgaas@hp.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |yinghai@kernel.org
> 
> 
> 
> 
> --- Comment #8 from Bjorn Helgaas <bjorn.helgaas@hp.com>  2010-06-17 16:37:42 ---
> That's perfect, thanks!
> 
> The E820 memory map from BIOS reports a range that overlaps the first
> megabyte (0xbff00000-0xbfffffff) of that host bridge window:
> 
>   BIOS-e820: 0000000000100000 - 00000000bfdf9c00 (usable)
>   BIOS-e820: 00000000bfdf9c00 - 00000000bfe4bc00 (ACPI NVS)
>   BIOS-e820: 00000000bfe4bc00 - 00000000bfe4dc00 (ACPI data)
>   BIOS-e820: 00000000bfe4dc00 - 00000000c0000000 (reserved)
>   pci_root PNP0A03:00: host bridge window [mem 0xbff00000-0xdfffffff]
> 
> The 0x100000-0xbfdf9c00 range is system RAM, and I would expect that
> the ACPI NVS and data area is also RAM, and the last reserved piece is
> probably RAM, too, because RAM tends to end at nicely aligned boundaries.
> 
> Table 14-1 in the ACPI 4.0 spec says "reserved" ranges from the E820
> table are "unsuitable for a standard device to use as a device memory
> space."
> 
> I think maybe Linux should regard those reserved ranges as unavailable
> for allocation to PCI devices, even if they happen to be included in a
> host bridge window.  What do you think, Yinghai?

for above 1M area, 
current kernel will honor setting from HW register and later will use insert_resource_expand_to_fit()
with e820 reserved entries.
so in this case will have one big 0xbfe4dc00 - 0xe000000 reserved entry in /proc/iomem as parent of
0xbff00000 - 0xe0000000

Sane BIOS should not put allocated range to PCI bridge/device into e820 table as reserved entries.

But there IS some BIOS doing that.
So Linus decided to trust setting from PCI bar at first.

later for pci_assign_unsigned, We should avoid those range.

one solution is expanding my one of old version for below 1M handling to:
use reserve_region_with_split instead.
will get /proc/iomem
bfe4dc00 - bfefffff reserved
bff00000 - dfffffff PCI BUS #00
  bff00000 - bfffffff reserved
  ...

so will use bff0000 - bfffffff reserved as holder to prevent those range to be allocated to unassigned devices.
reserve_region_with_split need to need be updated a little bit to make sure it will not put holder on range with children already.

something like this

Subject: [PATCH] x86, resource: Add reserve_region_with_split_check_child()

It will cover the whole region to BUSY, except that some regions that have
children under them.

those children normally is PCI bar but it is falling into E820_RESERVED.
We can not put BUSY on them, otherwise driver can not use pci_request_region()
later

/proc/iomem will have
00010000-00094fff : System RAM
00095000-0009ffff : reserved
000a0000-000bffff : PCI Bus 0000:00
  000a0000-000bffff : reserved
000c0000-000cffff : reserved
000d0000-000dffff : PCI Bus 0000:00
  000d0000-000dffff : reserved
000e0000-000fffff : reserved

-v2: Add function pointer to put string comparing with caller
-v3: expand to use it above 1M resources.

Tested-by: Guenter Roeck <guenter.roeck@ericsson.com>
Tested-by: Andy Isaacson <adi@hexapodia.org>
Signed-off-by: Yinghai Lu <yinghai@kernel.org>

---
 arch/x86/kernel/e820.c |   15 ++++++++++++---
 include/linux/ioport.h |    3 +++
 kernel/resource.c      |   29 ++++++++++++++++++++++++-----
 3 files changed, 39 insertions(+), 8 deletions(-)

Index: linux-2.6/arch/x86/kernel/e820.c
===================================================================
--- linux-2.6.orig/arch/x86/kernel/e820.c
+++ linux-2.6/arch/x86/kernel/e820.c
@@ -1094,7 +1094,7 @@ void __init e820_reserve_resources(void)
 		 * pci device BAR resource and insert them later in
 		 * pcibios_resource_survey()
 		 */
-		if (e820.map[i].type != E820_RESERVED || res->start < (1ULL<<20)) {
+		if (e820.map[i].type != E820_RESERVED) {
 			res->flags |= IORESOURCE_BUSY;
 			insert_resource(&iomem_resource, res);
 		}
@@ -1128,6 +1128,14 @@ static unsigned long ram_alignment(resou
 
 #define MAX_RESOURCE_SIZE ((resource_size_t)-1)
 
+static int __init check_func(struct resource *cf)
+{
+	if (strstr(cf->name, "PCI Bus"))
+		return 1;
+
+        return 0;
+}
+
 void __init e820_reserve_resources_late(void)
 {
 	int i;
@@ -1135,8 +1143,9 @@ void __init e820_reserve_resources_late(
 
 	res = e820_res;
 	for (i = 0; i < e820.nr_map; i++) {
-		if (!res->parent && res->end)
-			insert_resource_expand_to_fit(&iomem_resource, res);
+		if (!res->parent && res->end) {
+			reserve_region_with_split_check_child(&iomem_resource, res->start, res->end, res->name, check_func);
+		}
 		res++;
 	}
 
Index: linux-2.6/include/linux/ioport.h
===================================================================
--- linux-2.6.orig/include/linux/ioport.h
+++ linux-2.6/include/linux/ioport.h
@@ -120,6 +120,9 @@ void release_child_resources(struct reso
 extern void reserve_region_with_split(struct resource *root,
 			     resource_size_t start, resource_size_t end,
 			     const char *name);
+void reserve_region_with_split_check_child(struct resource *root,
+			     resource_size_t start, resource_size_t end,
+			     const char *name, int (*check_func)(struct resource *cf));
 extern struct resource *insert_resource_conflict(struct resource *parent, struct resource *new);
 extern int insert_resource(struct resource *parent, struct resource *new);
 extern void insert_resource_expand_to_fit(struct resource *root, struct resource *new);
Index: linux-2.6/kernel/resource.c
===================================================================
--- linux-2.6.orig/kernel/resource.c
+++ linux-2.6/kernel/resource.c
@@ -607,9 +607,14 @@ int adjust_resource(struct resource *res
 	return result;
 }
 
+static int __init check_func_nop(struct resource *cf)
+{
+	return 1;
+}
+
 static void __init __reserve_region_with_split(struct resource *root,
 		resource_size_t start, resource_size_t end,
-		const char *name)
+		const char *name, bool check_child, int (*check_func)(struct resource *cf))
 {
 	struct resource *parent = root;
 	struct resource *conflict;
@@ -631,13 +636,18 @@ static void __init __reserve_region_with
 	kfree(res);
 
 	/* conflict covered whole area */
-	if (conflict->start <= start && conflict->end >= end)
+	if (conflict->start <= start && conflict->end >= end) {
+		if (check_child && !conflict->child && check_func(conflict))
+			__reserve_region_with_split(conflict, start, end, name, false, check_func_nop);
 		return;
+	}
 
 	if (conflict->start > start)
-		__reserve_region_with_split(root, start, conflict->start-1, name);
+		__reserve_region_with_split(root, start, conflict->start-1, name, check_child, check_func);
 	if (conflict->end < end)
-		__reserve_region_with_split(root, conflict->end+1, end, name);
+		__reserve_region_with_split(root, conflict->end+1, end, name, check_child, check_func);
+	if (check_child && !conflict->child && check_func(conflict))
+		__reserve_region_with_split(conflict, conflict->start, conflict->end, name, false, check_func_nop);
 }
 
 void __init reserve_region_with_split(struct resource *root,
@@ -645,7 +655,16 @@ void __init reserve_region_with_split(st
 		const char *name)
 {
 	write_lock(&resource_lock);
-	__reserve_region_with_split(root, start, end, name);
+	__reserve_region_with_split(root, start, end, name, false, check_func_nop);
+	write_unlock(&resource_lock);
+}
+
+void __init reserve_region_with_split_check_child(struct resource *root,
+		resource_size_t start, resource_size_t end,
+		const char *name, int (*check_func)(struct resource *cf))
+{
+	write_lock(&resource_lock);
+	__reserve_region_with_split(root, start, end, name, true, check_func);
 	write_unlock(&resource_lock);
 }