[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200707172142.42008.lists4me@web.de>
Date: Tue, 17 Jul 2007 21:42:41 +0200
From: Markus <lists4me@....de>
To: Ingo Molnar <mingo@...e.hu>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Mike Galbraith <efault@....de>,
Arjan van de Ven <arjan@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Dmitry Adamushko <dmitry.adamushko@...il.com>,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [patch] CFS scheduler, -v19
> 9173 1184675906.194424 ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS,
0x7fff341af5c0)
> = -1 ENOTTY (Inappropriate ioctl for device) <0.000006>
> 9173 1184675906.194463 ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS,
0x7fff341af5c0)
> = -1 ENOTTY (Inappropriate ioctl for device) <0.000004>
>
> ? Are those -ENOTTY results normal?
Yes, I see it on any kernel.
> 9173 1184675906.155015 write(2, "In file
kernel/qpixmap_x11.cpp, "..., 56) = 56 <0.000006>
> 9173 1184675906.155052 write(2, "QImage::convertDepth: Image is
a"..., 44) = 44 <0.000004>
> 9173 1184675906.155169 gettimeofday({1184675906, 155179}, NULL) = 0
<0.000006>
> 9173 1184675906.155249 write(11, "close(6f1c2f7):about:konqueror\n",
31) = 31 <0.000032>
>
> i think konqueror tried to say something here about an image problem?
Well, yes:
In file kernel/qpixmap_x11.cpp, line 633: Out of memory
QImage::convertDepth: Image is a null image
In file kernel/qpixmap_x11.cpp, line 633: Out of memory
QImage::convertDepth: Image is a null image
In file kernel/qpixmap_x11.cpp, line 633: Out of memory
QImage::convertDepth: Image is a null image
In file kernel/qpixmap_x11.cpp, line 633: Out of memory
QImage::convertDepth: Image is a null image
konqueror: Fatal IO error: client killed
And no, my 2 GB of RAM are not full:
$ free -m
total used free shared buffers
cached
Mem: 2012 1077 935 0 22
441
-/+ buffers/cache: 612 1400
Swap: 2070 0 2070
> could you perhaps upload the strace to some webpage so that others can
> take a look too?
hm, I dont have any webspace...
> it might also be good to add "-s 1000" to the strace command, so that
we
> can see the full messages that konqueror tried to log to some other
> task, i.e.:
>
> strace -s 1000 -ttt -TTT -o trace.log -f <app>
>
> and perhaps try to do a 'comparison' trace.normal.log as well, with
> konqueror having no problems.
I now made some new strace logs:
- konq crash 251K
- Konq without crash on cfs 302K
- konq without crash on non-cfs 248K
Markus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists