From: Barry Gamblin <bgamblin@hao.ucar.edu>
To: linux-kernel@vger.kernel.org, linux-smp@vger.kernel.org
Subject: kernel bug in /var/log/messages
Date: Mon, 10 Feb 2003 15:38:33 -0700 (MST) [thread overview]
Message-ID: <200302102238.PAA06069@jabba.hao.ucar.edu> (raw)
System is running Redhat 7.3 with Kernel 2.4.18-19.7.xsmp on an i686.
It is a dual Xeon Supermicro P4DC6 motherboard. This is the message I
got over the weekend:
Feb 9 04:02:01 cedar-l syslogd 1.4.1: restart.
Feb 9 04:22:46 cedar-l kernel: Page has mapping still set. This is a
serious si
tuation. However if you
Feb 9 04:22:46 cedar-l kernel: are using the NVidia binary only module
please r
eport this bug to
Feb 9 04:22:46 cedar-l kernel: NVidia and not to Red Hat Bugzilla or
the linux
kernel mailinglist.
Feb 9 04:22:46 cedar-l kernel: ------------[ cut here ]------------
Feb 9 04:22:46 cedar-l kernel: kernel BUG at page_alloc.c:130!
Feb 9 04:22:46 cedar-l kernel: invalid operand: 0000
Feb 9 04:22:46 cedar-l kernel: nfsd autofs nfs lockd sunrpc eepro100
usb-uhci u
sbcore aic7xxx sd_mod scsi_mod
Feb 9 04:22:46 cedar-l kernel: CPU: 1
Feb 9 04:22:46 cedar-l kernel: EIP: 0010:[<c013ac4e>] Not tainted
Feb 9 04:22:46 cedar-l kernel: EFLAGS: 00010282
Feb 9 04:22:46 cedar-l kernel:
Feb 9 04:22:46 cedar-l kernel: EIP is at __free_pages_ok [kernel] 0x5e
(2.4.18-
19.7.xsmp)
Feb 9 04:22:46 cedar-l kernel: eax: 00000047 ebx: c173ac60 ecx:
00000001
edx: 00000001
Feb 9 04:22:46 cedar-l kernel: esi: 00000000 edi: 00000061 ebp:
00000000
esp: e0ff5e64
Feb 9 04:22:46 cedar-l kernel: ds: 0018 es: 0018 ss: 0018
Feb 9 04:22:46 cedar-l kernel: Process awk (pid: 11418,
stackpage=e0ff5000)
Feb 9 04:22:46 cedar-l kernel: Stack: c024ffc0 c024ff60 c024ff00
00000001 c1038
030 c0305da4 00000202 ffffffff
Feb 9 04:22:46 cedar-l kernel: 00020cd6 0001066b c039d65c
0000001b 00000
061 c1764f00 c012cdfc c173ac60
Feb 9 04:22:46 cedar-l kernel: 00062000 00000061 00062000
00000061 080e2
000 e229d084 08400000 c039d5e0
Feb 9 04:22:46 cedar-l kernel: Call Trace: [<c012cdfc>]
do_zap_page_range [kern
el] 0x37c (0xe0ff5e9c))
Feb 9 04:22:46 cedar-l kernel: [<c0156f1c>] dput [kernel] 0x1c
(0xe0ff5ef8))
Feb 9 04:22:46 cedar-l kernel: [<c012d2d0>] zap_page_range [kernel]
0x50 (0xe0f
f5f10))
Feb 9 04:22:46 cedar-l kernel: [<c012fe2b>] exit_mmap [kernel] 0xdb
(0xe0ff5f34
))
Feb 9 04:22:46 cedar-l kernel: [<c011bea8>] mmput [kernel] 0x38
(0xe0ff5f6c))
Feb 9 04:22:46 cedar-l kernel: [<c0120d5c>] do_exit [kernel] 0xdc
(0xe0ff5f78))
Feb 9 04:22:46 cedar-l kernel: [<c01435c2>] sys_read [kernel] 0x102
(0xe0ff5f8c
))
Feb 9 04:22:46 cedar-l kernel: [<c012fa55>] sys_munmap [kernel] 0x35
(0xe0ff5fa
0))
Feb 9 04:22:46 cedar-l kernel: [<c0108c83>] system_call [kernel] 0x33
(0xe0ff5f
c0))
Feb 9 04:22:46 cedar-l kernel:
Feb 9 04:22:46 cedar-l kernel:
Feb 9 04:22:46 cedar-l kernel: Code: 0f 0b 82 00 17 09 25 c0 8b 53 08
83 c4 0c
8b 3d d0 82 3c c0
Today I have experienced several lockups on the system requiring a
reset. I had to re-install this system on Friday due to a system disk
that got corrupted. I upgraded the kernel, modutils and glibc, but
nothing else.
Barry
Barry S. Gamblin, UNIX Administrator III, bgamblin@ucar.edu
High Altitude Observatory - National Center for Atmospheric Research
P.O.Box 3000, Boulder CO 80307-3000
voice - 303-497-1509 fax - 303-497-1589
reply other threads:[~2003-02-10 22:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200302102238.PAA06069@jabba.hao.ucar.edu \
--to=bgamblin@hao.ucar.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@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
all inboxes | Powered by JetHome®