lkml.org 
[lkml]   [2009]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [BUG 2.6.30+] e100 sometimes causes oops during resume
    On Tue, Sep 29, 2009 at 02:58:11PM +0100, Mel Gorman wrote:
    > On Wed, Sep 23, 2009 at 01:35:31AM +0200, Karol Lewandowski wrote:
    > > Maybe I should revert following commits (chosen somewhat randomly)?
    > >
    > > 1. 49255c619fbd482d704289b5eb2795f8e3b7ff2e
    > >
    > > 2. dd5d241ea955006122d76af88af87de73fec25b4 - alters changes made by
    > > commit above
    > >
    > > Any ideas?
    > >
    >
    > Those commits should only make a difference on small-memory machines.
    > The exact value of "small" varies but on 32 bit x86 without PAE, it would
    > be 20MB of RAM. The fact reverting the two patches makes any difference at
    > all is a surprise and likely a co-incidence.
    >
    > If you have a reliable reproduction case, would it be possible to bisect
    > between the points
    > d239171e4f6efd58d7e423853056b1b6a74f1446..b70d94ee438b3fd9c15c7691d7a932a135c18101
    > to see if the problem is in there anywhere?

    I've started with bc75d33f0 (one commit before d239171e4 in Linus'
    tree) but then my system fails to resume.

    Whatever I do (change fb/Xorg drivers, disable X, etc.) I always end
    up with unusable display and something that looks like hard-locked
    system (I haven't tested network connectivity from another box, but
    console is surely dead).

    Thanks.


    \
     
     \ /
      Last update: 2009-09-30 17:39    [W:4.158 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site