All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.1-mm2
Date: Tue, 13 Jan 2004 14:31:58 +0100	[thread overview]
Message-ID: <4003F34E.5080508@gmx.de> (raw)
In-Reply-To: <20040110014542.2acdb968.akpm@osdl.org>

Hi,

mm2 (or even mm1 or even vanilla, have not tested (long enough)) locks 
hard on my and someone else' machine. Sometimes we get this line in our 
logs before the lock happens:

kernel: Badness in pci_find_subsys at drivers/pci/search.c:132

Any ideas? Or do you need detailed kernel config and dmesg? I thought 
you might have an idea which atch caused this... My and his system are 
quite differnt. Major Common element seems only use of Athlon XP. He has 
VIA KT based system and I have nforce2. I thought it might be APIC, but 
I also got a lock up without APIC. (Though it seems more stable without 
APIC.)

bye,

Prakash

WARNING: multiple messages have this Message-ID (diff)
From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.1-mm2
Date: Tue, 13 Jan 2004 14:31:58 +0100	[thread overview]
Message-ID: <4003F34E.5080508@gmx.de> (raw)
In-Reply-To: <20040110014542.2acdb968.akpm@osdl.org>

Hi,

mm2 (or even mm1 or even vanilla, have not tested (long enough)) locks 
hard on my and someone else' machine. Sometimes we get this line in our 
logs before the lock happens:

kernel: Badness in pci_find_subsys at drivers/pci/search.c:132

Any ideas? Or do you need detailed kernel config and dmesg? I thought 
you might have an idea which atch caused this... My and his system are 
quite differnt. Major Common element seems only use of Athlon XP. He has 
VIA KT based system and I have nforce2. I thought it might be APIC, but 
I also got a lock up without APIC. (Though it seems more stable without 
APIC.)

bye,

Prakash
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2004-01-13 13:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10  9:45 2.6.1-mm2 Andrew Morton
2004-01-10  9:45 ` 2.6.1-mm2 Andrew Morton
2004-01-10 14:55 ` 2.6.1-mm2 Roberto Sanchez
2004-01-12  5:47 ` 2.6.1-mm2 (compile stats) John Cherry
2004-01-12  5:47   ` John Cherry
2004-01-13 13:31 ` Prakash K. Cheemplavam [this message]
2004-01-13 13:31   ` 2.6.1-mm2 Prakash K. Cheemplavam
2004-01-13 17:54   ` 2.6.1-mm2 Andrew Morton
2004-01-13 17:54     ` 2.6.1-mm2 Andrew Morton
2004-01-13 19:06     ` 2.6.1-mm2 Prakash K. Cheemplavam
2004-01-13 19:06       ` 2.6.1-mm2 Prakash K. Cheemplavam
2004-01-13 19:16       ` 2.6.1-mm2 Andrew Morton
2004-01-13 19:16         ` 2.6.1-mm2 Andrew Morton
2004-01-13 19:22         ` 2.6.1-mm2 Prakash K. Cheemplavam
2004-01-13 19:22           ` 2.6.1-mm2 Prakash K. Cheemplavam
2004-01-15 23:23           ` 2.6.1-mm2 Randy.Dunlap
2004-01-15 23:23             ` 2.6.1-mm2 Randy.Dunlap
2004-01-15 23:56             ` 2.6.1-mm2 Prakash K. Cheemplavam
2004-01-15 23:56               ` 2.6.1-mm2 Prakash K. Cheemplavam

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=4003F34E.5080508@gmx.de \
    --to=prakashkc@gmx.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.