linux-kernel - [REGRESSION][BISECTED] Notebook crashes upon detecting the PCI subsystem with kernels >= 2.6.24-rc7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 19 Aug 2011 14:53:16 -0300
From:	Rogério Brito <rbrito@....usp.br>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	Thomas Meyer <thomas@...3r.de>,
	Gary Hade <garyhade@...ibm.com>, Ingo Molnar <mingo@...e.hu>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-kernel@...r.kernel.org
Subject: [REGRESSION][BISECTED] Notebook crashes upon detecting the PCI
 subsystem with kernels >= 2.6.24-rc7

Hi.

My mom has a notebook that is quite quirky and I have had a hard
time trying to install any Linux distribution on it.

This is a notebook that works fine with Windows Vista, but she
wants to use Linux and wipe Windows completely.  The notebook has
an nVidia C51 chipset (nForce), a "forcedeth" network card, with
a Geforce Go 6100 video card and an AMD Sempron 3400+.

After *many* trial and error sessions, I found that kernel 2.6.24 worked
with this notebook, but *anything* more recent (in particular, even Debian
stable is "too recent" for it) just made it hang right after the io
schedulers were set up.

In other words, a regression.

>From my dmesg logs, the next thing after the io schedulers seems
to be the PCI devices. The first lines that appear right after
the io scheduler ones are:

,----
| [    0.207345] io scheduler cfq registered (default)
| [    0.207407] pci 0000:00:05.0: Boot video device
| [    0.223320] PCI: Setting latency timer of device 0000:00:02.0 to 64
| [    0.223320] assign_interrupt_mode Found MSI capability
| [    0.223320] Allocate Port Service[0000:00:02.0:pcie00]
| [    0.223320] PM: Adding info for pci_express:0000:00:02.0:pcie00
| [    0.223320] PCI: Setting latency timer of device 0000:00:03.0 to 64
| [    0.223320] assign_interrupt_mode Found MSI capability
| [    0.223320] Allocate Port Service[0000:00:03.0:pcie00]
| [    0.223320] PM: Adding info for pci_express:0000:00:03.0:pcie00
| [    0.223320] PM: Adding info for platform:vesafb.0
`----

I took the laborious task of `git bisecting` the kernel (more than 30
recompiles, and fsck'ing the disc), I found that the first bad commit
(12c22d6e), a revert by Linus:

,----[ git bisect bad ]
| 12c22d6ef299ccf0955e5756eb57d90d7577ac68 is the first bad commit
| commit 12c22d6ef299ccf0955e5756eb57d90d7577ac68
| Author: Linus Torvalds <torvalds@...ux-foundation.org>
| Date:   Wed Mar 26 11:22:40 2008 -0700
| 
|     Revert "PCI: remove transparent bridge sizing"
|     
|     This reverts commit 8fa5913d54f3b1e09948e6a0db34da887e05ff1f, which
|     caused various interesting problems for people, including wrong resource
|     allocations.  See for example bugzilla entry "2.6.25-rc2: ohci1394
|     problem (MMIO broken)" at
|     
|     	http://bugzilla.kernel.org/show_bug.cgi?id=10080
|     
|     And Gary Hade says:
|     
|      "The same change had also exposed an issue reported by Paul Martin that
|       has been causing an Oops while hotplugging ThinkPads to a ThinkPad
|       Dock II.  See
|     
|     	http://lkml.org/lkml/2008/2/19/405
|     	http://bugzilla.kernel.org/show_bug.cgi?id=9961
|     
|       I have a fix for the ThinkPad docking Oops but if the issue being
|       discussed here is caused by the transparent bridge sizing removal
|       change I totally agree that it should be reverted."
|     
|       The transparent bridge sizing removal change was motivated by
|       insufficient PCI memory resource for a transparent bridge window that
|       was being created as a result of expansion ROM(s) being included in
|       the transparent bridge sizing calculations.
|     
|       A later "PCI: Remove default PCI expansion ROM memory allocation"
|       change ( re: http://lkml.org/lkml/2007/12/11/361 ) removes the
|       expansion ROM(s) from the transparent bridge sizing calculations which
|       actually resolves the original issue in a different manner.  So, even
|       if the "PCI: remove transparent bridge sizing" is not problematic it
|       is no longer needed anyway."
|     
|     Identified-by: Ivan Kokshaysky <ink@...assic.park.msu.ru>
|     Tested-by: Thomas Meyer <thomas@...3r.de>
|     Acked-by: Gary Hade <garyhade@...ibm.com>
|     Acked-by: Ingo Molnar <mingo@...e.hu>
|     Cc: Stefan Richter <stefanr@...6.in-berlin.de>
|     Signed-off-by: Linus Torvalds <torvalds@...ux-foundation.org>
| 
| :040000 040000 e3d0046e6ce6dc4e3bb6114db61336125fab9ea7 c60b1fdbdc2bda47dbb822b0a741d8254a7d8afa M	drivers
`----

I am willing to test anything to make this notebook work with a recent
kernel version, so that I can prepare this to her use with a modern
distribution.

Please, advise if you need any dmesg, lspci outputs, acpi dumps, etc.  You
tell me, and I try my best to get whatever you want me.

Thanks in advance for any help,

Rogério Brito.

-- 
Rogério Brito : rbrito@...e.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/