[lkml]   [2009]   [Sep]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [E1000-devel] [BUG 2.6.30+] e100 sometimes causes oops during resume
On Wednesday 16 September 2009, Graham, David wrote:
> A v2.6.30..v2.6.31 diff shows that this is probably exposed by Rafael Wysocki's
> commit 6905b1f1, which now allows systems with e100 to sleep. If I understand
> correctly, it looks like these systems simply couldn't sleep before. Is that right Rafael?

The systems where e100 is not power manageable by any means couldn't suspend
before that commit. For the other systems, where e100 is power manageable
either with ACPI or natively, the commit doesn't change anything.

> I don't think its likely that the commit is a direct cause of the problem, but that the
> suspend/resume cycle now allows us to see another issue. Maybe e100 is
> leaking memory on suspend/resume cycles, or something else is leaking memory,
> or memory is becoming fragmented and the e100 driver is improperly
> requesting and being failed on an 'atomic' memory allocation from a heavily
> fragmented memory map. Or something else.

I have a couple of test systems with e100 that don't have any resume problems,


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