From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1-mm4
Date: Thu, 12 Feb 2004 14:15:43 +0100 [thread overview]
Message-ID: <402B7C7F.1040103@gmx.de> (raw)
In-Reply-To: <200402120846.i1C8k6x7006645@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Thu, 12 Feb 2004 08:30:54 +0100, "Prakash K. Cheemplavam" said:
>
>
>>Well, I don't know whether my system actually locks up, it is like it
>>seems the log gets flooded (when I wait long enough) but I cannot do
>>anything with the system at that point, ie it seems like frozen.
>
>
> I don't think anybody's going to be able to shoot that bug report without more
> info. "seems like frozen" doesn't give us much to go on. Does the machine
> still ping/ssh/etc on the net? Is it totally locked up? Any disk activity
> lights left on/flickering, indicating life? Can you get a serial console or
> kgdb-ethernet or something to see if there's an oops/panic?
Hmm, I'll test those bk-snapshots and when it locks up, I'll try to
access the pc form another machine. As I said it seems (when I wait long
enough, within the first minute nothing in the log survives the reboot,
probably due to reiserfs journalling) the log writes the oops I posted
in the first message infinite times.
> Well, the 53.36 drivers are rock-solid on my Dell laptop with a GeForce4 440Go
> and the 2.6.3-rc1-mm1 kernel. There very well may be bugs in there, but
> they're not ones I can replicate or diagnose...
Maybe it is a nforce2 issue then. I think it is ACPI specific. I'll also
try compiling latest kernel without ACPI and report back.
Thanx,
Prakash
next prev parent reply other threads:[~2004-02-12 13:15 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 6:59 2.6.1-mm4 Andrew Morton
2004-01-16 9:34 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-21 18:46 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-21 19:20 ` 2.6.1-mm4 Valdis.Kletnieks
2004-02-11 22:22 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-02-12 5:52 ` 2.6.1-mm4 Valdis.Kletnieks
2004-02-12 7:30 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-02-12 8:46 ` 2.6.1-mm4 Valdis.Kletnieks
2004-02-12 13:15 ` Prakash K. Cheemplavam [this message]
2004-02-12 16:11 ` 2.6.1-mm4 Prakash K. Cheemplavam
2004-01-16 13:45 ` 2.6.1-mm4 Ed Tomlinson
2004-01-16 17:32 ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 14:49 ` 2.6.1-mm4 Fabian Fenaut
[not found] ` <200401161449.i0GEnoAv026627@fire-1.osdl.org>
2004-01-16 17:03 ` 2.6.1-mm4 Andrew Morton
2004-01-16 18:11 ` 2.6.1-mm4 Fabian Fenaut
2004-01-16 17:14 ` 2.6.1-mm4 (compile stats) John Cherry
2004-01-16 17:37 ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 17:58 ` 2.6.1-mm4 Thomas Schlichter
2004-01-16 18:17 ` Oops in register_proc_table (2.6.1-mm4) Thomas Schlichter
2004-01-17 20:11 ` Paul Misner
2004-01-17 1:31 ` 2.6.1-mm4 Greg Fitzgerald
2004-01-17 1:40 ` 2.6.1-mm4 Mike Fedyk
2004-01-17 2:07 ` 2.6.1-mm4 Greg Fitzgerald
2004-01-17 2:24 ` 2.6.1-mm4 Mike Fedyk
2004-01-17 4:05 ` 2.6.1-mm4 Dmitry Torokhov
2004-01-17 4:22 ` 2.6.1-mm4 Greg Fitzgerald
2004-01-17 2:22 ` 2.6.1-mm4 Adrian Bunk
2004-01-18 0:12 ` 2.6.1-mm4 J.A. Magallon
2004-01-18 5:55 ` 2.6.1-mm4 Andrew Morton
2004-01-18 8:11 ` 2.6.1-mm4 J.A. Magallon
2004-01-18 8:17 ` 2.6.1-mm4 Andrew Morton
2004-01-19 11:42 ` 2.6.1-mm4 Rusty Russell
2004-01-19 11:00 ` 2.6.1-mm4 same sound oops as mm3 Helge Hafting
2004-01-19 11:46 ` 2.6.1-mm4 Luiz Fernando Capitulino
2004-01-20 0:26 ` 2.6.1-mm4 Thomas Molina
2004-01-20 0:57 ` 2.6.1-mm4 Andrew Morton
2004-01-20 2:13 ` 2.6.1-mm4 Thomas Molina
-- strict thread matches above, loose matches on Subject: below --
2004-01-17 13:13 2.6.1-mm4 Thomas Molina
2004-01-17 18:14 ` 2.6.1-mm4 Hugh Dickins
2004-01-17 18:52 ` 2.6.1-mm4 Andrew Morton
2004-01-19 7:16 ` 2.6.1-mm4 Rusty Russell
2004-01-19 11:29 ` 2.6.1-mm4 Rusty Russell
[not found] <20040115225948.6b994a48.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20040118001217.GE3125@werewolf.able.es.suse.lists.linux.kernel>
[not found] ` <20040117215535.0e4674b8.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20040118081128.GA3153@werewolf.able.es.suse.lists.linux.kernel>
[not found] ` <20040118001708.09291455.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20040119224219.65991501.rusty@rustcorp.com.au.suse.lists.linux.kernel>
2004-01-19 12:40 ` 2.6.1-mm4 Andi Kleen
2004-01-21 4:06 ` 2.6.1-mm4 Rusty Russell
2004-01-21 4:56 ` 2.6.1-mm4 Valdis.Kletnieks
2004-01-21 8:40 ` 2.6.1-mm4 Vojtech Pavlik
2004-01-21 12:27 ` 2.6.1-mm4 Andi Kleen
2004-01-21 12:34 ` 2.6.1-mm4 Vojtech Pavlik
2004-01-21 12:46 ` 2.6.1-mm4 Andi Kleen
2004-01-21 13:13 ` 2.6.1-mm4 Vojtech Pavlik
2004-01-22 1:31 ` 2.6.1-mm4 Rusty Russell
2004-01-21 12:53 ` 2.6.1-mm4 Dmitry Torokhov
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=402B7C7F.1040103@gmx.de \
--to=prakashkc@gmx.de \
--cc=Valdis.Kletnieks@vt.edu \
--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