linux-kernel - Re: 2.6.18-rc6-mm1 2.6.18-rc5-mm1 Kernel Panic on X60s

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 09 Sep 2006 01:47:55 -0400
From:	Brice Goglin <brice@...i.com>
To:	Andrew Morton <akpm@...l.org>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Brandon Philips <brandon@...p.org>,
	linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, Robert Love <rml@...ell.com>
Subject: Re: 2.6.18-rc6-mm1 2.6.18-rc5-mm1 Kernel Panic on X60s

Andrew Morton wrote:
> On Fri, 08 Sep 2006 21:27:46 -0600
> ebiederm@...ssion.com (Eric W. Biederman) wrote:
>   
>> Andrew Morton <akpm@...l.org> writes:
>>     
>>> On Fri, 8 Sep 2006 14:43:00 -0500
>>> Brandon Philips <brandon@...p.org> wrote:
>>>       
>>>> With CONFIG_PCI_MSI disabled the system boots.  
>>>>         
>>> OK, thanks.
>>>
>>> So likely candidates are:
>>>
>>> - Brice's MSI changes
>>>
>>> - The conversion of i386 to use the genirq code
>>>
>>> - Eric's MSI/genirq changes
>>>
>>> or a combination of the above.  Or something else.
>>>
>>> <adds ccs, steps back expectantly>
>>>       
>> Thanks for the heads up.
>>
>> There was another panic reported last -mm tree I believe as well.
>>     
>
> Yes, there were a couple such reports.  The MSI patches in Greg's tree were
> blamed and rc6-mm1 has a revamped version.  Whether they were sufficiently
> revamped we do not know.
>   


The revamped version is much simpler than the previous ones. We are
basically back to the early ones we had in 2.6.17-mm5, with a tiny
modification to fix the oops that was reported there.

AFAIK, the possible problems that my patches might generate should only be:
* an obvious bug in the code leading to an oops during pci_enable_msi()
or pci_enable_msix() ;
* a wrong detection of whether MSI are supported or not, leading to MSI
being disabled while supported (should not be bad for most drivers), or
enabled while unsupported by the root chipset (would be bad).

Do we have Brandon lspci so that I can see if any of the MSI quirks is
involved?

Brice

-
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/