From: Andrew Morton <akpm@zip.com.au>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.20-BUG] 3c59x + highmem + acpi + nfs -> kernel panic
Date: Mon, 03 Jun 2002 02:48:55 -0700 [thread overview]
Message-ID: <3CFB3B87.74C7E9DF@zip.com.au> (raw)
In-Reply-To: <1023096034.19717.62.camel@storm.christs.cam.ac.uk>
Anton Altaparmakov wrote:
>
> Hi,
>
> Just got this (reproducible) kernel panic (BUG in
> asm-i386/highmem.h::kmap_atomic(), the if (!pte_none(*(kmap_pte-idx)))
> BUG(); triggers). It happens every time I boot and on an NFS mount do a
> ./configure.
Dunno about this one. I'm seeing some (totally different) NFS funnies
at present - pagecache data on the client is coming up zeroes under
memory pressure. Trond mentioned that NFS recently went to kmap_atomic,
so there is a common thread there.
> I am now seeing this error during boot as well. Don't know if it is
> related:
>
> ---snip---
> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> 00:09.0: 3Com PCI 3c590 Vortex 10Mbps at 0xe800. Vers LK1.1.17
> 00:09.0: Overriding PCI latency timer (CFLT) setting of 32, new value is
> 248.
> ***INVALID CHECKSUM 002f*** phy=0, phyx=24, mii_status=0x782d
> ---snip---
>
> Note that on previous kernels it says:
>
> ---snip---
> PCI: Assigned IRQ 11 for device 00:09.0
> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> 00:09.0: 3Com PCI 3c905C Tornado at 0xe800. Vers LK1.1.17
> phy=0, phyx=24, mii_status=0x782d
> ---snip---
It misidentified the device. How bizarre. 3c590 is 0x10B7, 0x5900
and 3c905C is 0x10B7, 0x9200. lspci saw the 905C OK. Possibly the
PCI device table walking got broken or miscompiled. Works OK here,
as does NFS client on SMP+highmem.
-
next prev parent reply other threads:[~2002-06-03 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 9:20 [2.5.20-BUG] 3c59x + highmem + acpi + nfs -> kernel panic Anton Altaparmakov
2002-06-03 9:48 ` Andrew Morton [this message]
2002-06-03 11:32 ` Trond Myklebust
2002-06-04 6:37 ` Andrew Morton
2002-06-04 11:39 ` Trond Myklebust
2002-06-04 10:39 ` David S. Miller
2002-06-04 12:10 ` Trond Myklebust
2002-06-04 11:46 ` Anton Altaparmakov
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=3CFB3B87.74C7E9DF@zip.com.au \
--to=akpm@zip.com.au \
--cc=aia21@cantab.net \
--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