From: Steffen Michalke <StMichalke@web.de>
To: linux-kernel@vger.kernel.org
Subject: Strange crashes of kernel v2.6.11
Date: Wed, 02 Mar 2005 18:17:08 +0000 [thread overview]
Message-ID: <1109787428.6828.14.camel@pinky.local> (raw)
Hi:
I recently upgraded from linux kernel v2.6.10 to v2.6.11.
Some programs like evolution 2.0 and leafnode2 crash the whole system
immediatedly now.
I would like to provide some further information if i could gather them.
The ones I have:
/usr/src/linux/scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux pinky 2.6.10 #6 Wed Feb 9 12:14:53 CET 2005 i686 i686 i386
GNU/Linux
Gnu C 3.4.3
Gnu make 3.80
binutils 2.15.91.0.2
util-linux 2.12c
mount 2.12c
module-init-tools 3.1-pre5
e2fsprogs 1.35
jfsutils 1.1.7
reiserfsprogs 3.6.18
reiser4progs line
nfs-utils 1.0.6
Linux C Library 02 02:30 /lib/tls/libc.so.6
Dynamic linker (ldd) 2.3.3
Linux C++ Library 6.0.3
Procps 3.2.3
Net-tools 1.60
Kbd 1.12
Sh-utils 5.2.1
udev 030
Modules Loaded snd_pcm_oss snd_mixer_oss snd_intel8x0 aes_i586
loop floppy psmouse parport_pc lp parport usblp snd_ac97_codec snd_pcm
snd_timer snd soundcore snd_page_alloc md5 ipv6 nfs lockd sunrpc rtc
pcspkr dm_crypt dm_mod joydev sg scsi_mod ide_cd cdrom natsemi crc32
intel_agp agpgart uhci_hcd hw_random usbcore unix
I did not change the configuration except of inserting the sound card
module.
I have never experienced such a disaster before coming out from a kernel
cahnge from one version to its succesor.
Ciaoi
Steffen
next reply other threads:[~2005-03-02 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 18:17 Steffen Michalke [this message]
2005-03-02 21:32 ` Strange crashes of kernel v2.6.11 Andrew Morton
2005-03-02 21:34 ` Alexander Nyberg
2005-03-04 11:33 ` Steffen Michalke
2005-03-04 12:23 ` Alexander Nyberg
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=1109787428.6828.14.camel@pinky.local \
--to=stmichalke@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