mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	riel@redhat.com
Subject: Re: Problem: Out of memory after 2days with 2GB RAM
Date: Fri, 13 Jun 2008 16:15:15 +0200	[thread overview]
Message-ID: <c4e36d110806130715v4126d9b6vef69746e3b4e493b@mail.gmail.com> (raw)
In-Reply-To: <200806131608.31803.rjw@sisk.pl>

2008/6/13 Rafael J. Wysocki <rjw@sisk.pl>:
> On Thursday, 12 of June 2008, Zdenek Kabelac wrote:
>> Hello
>>
>> I'm attaching a trace where my machine has got into big troubles after
>> 2 day usage and several successful suspend/resumes (this seems to be
>> finally getting better now :))
>>
>> It looks like while there was a huge amount of buffers and caches -
>> system was unable to allocate few pages for kmalloc in iwl3945 driver
>> after resume.
>>
>> I've even tried to 3 > drop_cache  and reinsert iwl driver - but this
>> had fatal results - machine died completely with blinking caps lock -
>> and no oops in the log for this case:
>>
>> This is the commit aab2545fdd6641b76af0ae96456c4ca9d1e50dad  for the
>> 2.6.26-rc5 I've been in this case.
>
> Is this a regression from 2.6.25, BTW?

Well I've never seen this with 2.6.25 kernel - on the other hand
usually I've not been running machine for a longer period of time,
because suspend was failing too often I guess. Now it's more stable so
this bug has shown up.

It might be related to this issue as well http://lkml.org/lkml/2008/5/22/308

Zdenek

  reply	other threads:[~2008-06-13 14:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 10:07 Zdenek Kabelac
2008-06-12 13:38 ` Rik van Riel
2008-06-12 13:54   ` Johannes Berg
2008-06-12 14:12     ` Zdenek Kabelac
2008-06-12 14:19       ` Johannes Berg
2008-06-12 16:38       ` Tomas Winkler
2008-06-12 15:43     ` Tomas Winkler
2008-06-12 16:35       ` Tomas Winkler
2008-06-12 17:05         ` Johannes Berg
2008-06-12 17:39           ` Tomas Winkler
2008-06-12 17:46             ` Johannes Berg
2008-06-12 18:03               ` Tomas Winkler
2008-06-12 18:15                 ` Johannes Berg
2008-06-12 20:11                   ` Zdenek Kabelac
2008-06-12 22:17                     ` Tomas Winkler
2008-06-13  0:43                     ` Andrew Morton
2008-06-12 18:41               ` John W. Linville
2008-06-12 17:03       ` Johannes Berg
2008-06-12 17:35         ` Tomas Winkler
2008-06-12 17:39           ` Johannes Berg
2008-06-12 17:50             ` Tomas Winkler
2008-06-12 17:10       ` Rik van Riel
2008-06-12 21:30       ` Jiri Slaby
2008-06-12 22:26         ` Tomas Winkler
2008-06-13 14:08 ` Rafael J. Wysocki
2008-06-13 14:15   ` Zdenek Kabelac [this message]
2008-06-30 11:30     ` Zdenek Kabelac

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c4e36d110806130715v4126d9b6vef69746e3b4e493b@mail.gmail.com \
    --to=zdenek.kabelac@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®