From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Markus <M4rkusXXL@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: programs vanish with 2.6.22+
Date: Thu, 6 Dec 2007 22:12:18 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0712062207320.25344@axis700.grange> (raw)
In-Reply-To: <200712061927.35976.M4rkusXXL@web.de>
On Thu, 6 Dec 2007, Markus wrote:
> Just forgot to mention:
> dmesg gives nothing (/var/log/messages)
> the global X log aswell
>
> and in the users .xsession-errors I have:
> amarokapp: Fatal IO error: client killed
> kdesktop: Fatal IO error: client killed
> konqueror: Fatal IO error: client killed
> The application 'xchat' lost its connection to the display :0.0;
>
> I dont know what that means, but at least its something ;)
Hm, no good idea, but some possible hints:
1. Ask Gentoo folks - if anyone has seen similar problems
2. RAM test - even if earlier kernels ran stable, the new one might stress
your RAM differently
3. Are you sure nothing else has changed apart from the kernel?
4. You might try to recompile a vanilla 2.6.23+ kernel and enable as many
kernel debugging options as you can...
5. Are you sure the installed kernel matches your CPU and your user-space
64- / 32-bit combination? Don't know whether a wrongly configured kernel
could cause such problems though
Good luck
Guennadi
>
> Markus
>
> > Hello!
> >
> > Excuse my bad english, I am no native speaker. And please CC me, as I
> am
> > not subscribed!
> >
> > I am running an amd64 system with a stable gentoo. Today I upgraded to
> > the kernel 2.6.22 and noticed many programs to disappear.
> > I use a kde desktop (3.5.7) and when amarok or kmail crash, normaly
> > a "kde-crash-manager" pops up (but that happend very rarely), but not
> > with 2.6.22+. It happens often and without any messagebox.
> > kdesktop, xchat, kicker, konqueror crashed as well.
> > It happens more often under heavy load. But it can also happen when
> > idle. Also I have the feeling that it happens more often on 2.6.23+ I
> > might be wrong.
> >
> > I tried 2.6.23 and the current 2.6.24-rc4, which all show this problem
> > aswell!
> > What has changed in 2.6.21 -> 2.6.22 that could cause such things?
> > Or who can tell that?
> > Can I help? How? (I use linux for years and can code, but I never
> > debugged anything as big as the kernel...)
> >
> >
> > Markus
> >
> > PS: Sorry thats so late, but I normaly stay on the distros stable
> kernel
> > and only try vanilla when something is wrong ;)
> >
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
---
Guennadi Liakhovetski
next prev parent reply other threads:[~2007-12-06 21:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 18:06 Markus
2007-12-06 18:27 ` Markus
2007-12-06 21:12 ` Guennadi Liakhovetski [this message]
2007-12-06 22:21 ` Markus
2007-12-07 11:40 ` Markus
2007-12-07 11:53 ` Guennadi Liakhovetski
2007-12-07 22:52 ` Markus
2007-12-07 23:09 ` Simon Holm Thøgersen
2007-12-08 12:12 ` Markus
2007-12-08 14:06 ` Paolo Ornati
2007-12-08 15:54 ` Markus
2007-12-08 21:38 ` Markus
2007-12-07 23:46 ` Guennadi Liakhovetski
2007-12-08 12:25 ` Markus
2007-12-08 13:50 ` Patrick Mau
2007-12-09 19:03 ` Ray Lee
2007-12-16 23:18 ` Bill Davidsen
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=Pine.LNX.4.64.0712062207320.25344@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=M4rkusXXL@web.de \
--cc=linux-kernel@vger.kernel.org \
/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®