[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#571741: tested with 2.6.32-3



Hi!

Santiago Garcia Mantinan <manty@debian.org> (28/02/2010):
> [  396.756554] Restarting tasks ... 
> [  396.757030] klogd[1194]: segfault at cc9cd400 ip 00007fe87ebb3c02 sp
> 00007fffcc9ccf40 error 6 in libc-2.10.2.so[7fe87eb6f000+14a000]

Strange.

> [  396.770142] done.
> [  396.786099] PM: Basic memory bitmaps freed
> [  397.130452] [drm] TV-14: set mode NTSC 480i 0
> [  397.184644] syslogd[1185]: segfault at 664cb00 ip 00007fe0a31bcc02 sp
> 00007fff0664c5d0 error 6 in libc-2.10.2.so[7fe0a3178000+14a000]

Strange as well.

> [  397.448046] [drm] TV-14: set mode NTSC 480i 0
> 
> This kind of corruption tends to happen more likely if I have more
> ram used, I mean, if I only load my Xwindow environment (icewm and a
> couple of terms) it doesn't happen or happens only from time to
> time, but if I load iceweasel and pidgin it starts to happen almost
> all the time.

Hrm. See below.

> Just a note so that you see how badly the system is right now... I just did
> this on a terminal:
> 
> manty@bat:~$ ps ax
>   PID TTY      STAT   TIME COMMAND
> 
> 
> Signal 11 (SEGV) caught by ps (procps version 3.2.8).
> Please send bug reports to <feedback@lists.sf.net> or <albert@users.sf.net>

Also strange.

From a quick look upstream, I think the only related bugreport (about
RAM being an issue) would be:
  https://bugs.freedesktop.org/show_bug.cgi?id=21802

I'm a bit unsure about what you're getting though, it looks like
several applications, including not-to-greedy ones are segfaulting
(and we don't see any traces of OOM-ing). Could it be your RAM is
getting a bit oldish and is starting to be on crack?

As for your test with 2.6.33, could it be that some kind of core
component started to crash in a similar fashion, preventing you from
logging in?

As a wild guess, since we have shared (as opposed to dedicated)
memory, the video stuff might screw up with the rest of the memory,
but wow. Maybe you could try and disable drm/dri? (The former in the
kernel, the latter in X; if you want to do it the hackish way, mv the
related .ko out of the way for the former, that probably should
disable the latter automatically; if that's not the case, try adding
option nodri to your configuration.)

(Also, please keep in mind I'm very new to all this, I might be
talking nonsense as well…)

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


Reply to: