From: Adrian Bunk <bunk@stusta.de>
To: Klasyk <klasyk99@poczta.onet.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: my kernel sometimes did a crash, but no panic
Date: Tue, 9 Aug 2005 22:21:47 +0200 [thread overview]
Message-ID: <20050809202147.GH4006@stusta.de> (raw)
In-Reply-To: <200508091804050500.042A58AE@friko2.onet.pl>
On Tue, Aug 09, 2005 at 06:04:05PM +0200, Klasyk wrote:
> my kernel sometimes did a crash, but no panic
> Keyboard hunged up :(
> Network were working and I can log in. Without the keybord - it
> generally worked.
>
> In logs:
> for example:
>...
> Aug 6 15:30:02 o kernel: Modules linked in: ip_nat_irc
>...
> btcx-risc tveeprom i2c-core nvidia agpgart usblp ehci-hcd uhci-hcd
>...
> Aug 6 15:30:02 o kernel: EIP: 0060:[<c026b0d9>] Tainted: P
>...
> it is not apic problem, i disabled it, and it didn't help
> Linux o 2.6.11-12mdkcustom #2 Sat Aug 6 11:02:20 CEST 2005 i686 AMD
> Duron(TM) unknown GNU/Linux
>...
Does this problem still occur with:
- a vanilla 2.6.13-rc6 ftp.kernel.org kernel and
- without loading any external modules since booting?
If it doesn't it's completely off-topic here and you should ask either
Mandrake or Nvidia for support.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-08-09 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 16:04 my kernel sometimes did a crash, but no panic Klasyk
2005-08-09 19:18 ` Mauro Carvalho Chehab
[not found] ` <1123618340.2484.9.camel@KKK>
2005-08-09 20:26 ` Mauro Carvalho Chehab
2005-08-09 20:21 ` Adrian Bunk [this message]
[not found] <4zEQ3-7Le-21@gated-at.bofh.it>
2005-08-09 18:44 ` Bodo Eggert
2005-08-09 19:05 ` Michael Krufky
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 20:14 klasyk99
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=20050809202147.GH4006@stusta.de \
--to=bunk@stusta.de \
--cc=klasyk99@poczta.onet.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.