lkml.org 
[lkml]   [2009]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [crash] NULL pointer dereference at IP: [<ffffffff812e9ccb>] uart_close+0x2a/0x1e4

* Ingo Molnar <mingo@elte.hu> wrote:

> i also have a crash with vanilla -rc4, test on this commit:
>
> d93a8f8: Revert "USB: Work around BIOS bugs by quiescing USB controllers earlier"
>
> crashlog pasted below - config attached.

i did a full .31 -> .32-rc4 bisection and came up with this result:

| 46d57a449aa13d9c6adcc9d1dbc7b9a0ecfb69d8 is first bad commit
| commit 46d57a449aa13d9c6adcc9d1dbc7b9a0ecfb69d8
| Author: Alan Cox <alan@linux.intel.com>
| Date: Sat Sep 19 13:13:29 2009 -0700
|
| serial: use tty_port pointers in the core code

this is the second time i have bisected back to this commit, see also
this prior thread on lkml:

Subject: [origin tree boot crash] Re: [GIT PATCH] TTY patches for 2.6.31-git

i chalked that first crash/hang up to potential cosmic entropy
(especially since it happened even with all serial logging disabled, and
because i was unable to get any log of the spontaneous reboot), but this
second crash occurs on a completely different system and has an
analyzable crash signature as well.

Both systems are rock-solid with no known hardware weirdness, the first
test-system passed two hundred thousand boot tests in the past 1.5
years, and the second one has performed tens of thousands of build+boot
tests as well. I'd exclude hardware failure as a likely candidate for
now.

Unfortunately 46d57a449aa13d9c6adcc9d1dbc7b9a0ecfb69d8 is not easy to
revert, at all. Would be glad to try any patch - fixes or some manual
revert as well (if that's feasible).

Ingo


\
 
 \ /
  Last update: 2009-10-12 13:29    [W:0.045 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site