All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xevi <u1025597@correu.udg.es>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: kernel bug in page_alloc 191 !
Date: Tue, 10 Apr 2001 19:58:26 +0200	[thread overview]
Message-ID: <3AC84AF8@webmail.udg.es> (raw)

[-- Attachment #1: Type: text/plain, Size: 145 bytes --]

The information is in the file ...

If you want make some question, I hope respond as soon as I can do it.

Xevi Serrats
u1025597@correu.udg.es


[-- Attachment #2: bug-kernel-last.txt --]
[-- Type: text/plain, Size: 7056 bytes --]

REPORTING-BUGS

[1.] One line summary of the problrm:

When I boot linux (usinb lilo) appears an error message : kernel bug at page_alloc 191

[2.] Full description of the problem:

Two times, when I boot my linux - 2.4.3 appears this message after start deamon httpd.
I use linuix mandrake 7.2 and I upgrade with kernel 2.4.3 few weeks ago. I load linux in lilo,
it begin "entering" in the sistem and two times, after start httpd success a bug.
I'm sorry because I can't descrive it more, but I have some information ...

starting httpd:         [ OK ]

Kernel BUG al page_alloc.c 191 !
invalid operand 0000
CPU:0
EIP: 0010:[<c012a00a>]
EFLAGS: 00010082

eax: 00000020 ebx: c03ed324  ecx: 0000002e   edx: 00000001
esi: c02a71a0 ed: 00000000   edp: 00000001   esp: c1e97e84

ds: 018  es: 018  ss: 018

Process S85httpd (pid: 821, stackpage= c1e97000)

stack: c024ca05  c024cb13  000000bf  c02a7178  c02a7350  00000000  00000001  00000000
       00000286  00000000  c02a7178  c012a3d3  c1079a90  080f51ec  c19c20c0  00000001
       00000005  00000001  c02a734c  c011f8c2  c19c20c0  080f51es  ffffffff  00000001

Call Trace: [<c012a3d3>]  [<c011f8c2>]  [<c012004d2>]  [<c010f704>]  [<c010f85d2>]
            [<c010f704>]  [<c0112686>]  [<c012eef2>]  [<c012ef57>]  [<e01070d4>]

Code: 0f 0b 83 c4 0c 90 8b 53 04 8b 03 89 50 04 8d 4f 01 89 02 89

[3.] Keywords (i.e., modules, networking, kernel);

I don't what you are asking here, excuse me ...

[4.] kernel version

I use kernel 2.4.3

[5.] Output of Oops.. message (if applicable) with symbolic information
        resolved ...

I think this information is in the point 2, I copies it manually, I hope it
hasn't errors, I was very carefully.

[6.] A small shell script or example program which triggers the problem (if possible)

I think it is not possible because the bug succes when i tried entering linux ...

[7.] Environment

I don't undestand this point, but I use linux because I am a programmer, I use
specially gcc and now I begin use apache and PHP ... perhaps the reason the bug
kernel occurs after httpd is because I used apache and PHP ... I don't know ...
I use apache but my PC isn't a server that host a web pages. My PC don't use any
local area network, and I specially use by doing C programs ...

[8.] Software (add the output of the ver_linux here).

If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

Linux localhost.localdomain 2.4.3 #3 SMP dg. abr. 1 06:21:47 /etc/localtime 2001 i586 unknown

Gnu C                  2.95.3
Gnu make               3.79.1
binutils               2.10.0.24
util-linux             2.10p
modutils               2.4.0
e2fsprogs              1.19
PPP                    2.4.0
isdn4k-utils           3.1beta7
Linux C Library        2.1.3
Dynamic linker (ldd)   2.1.3
Procps                 2.0.7
Net-tools              1.57
Console-tools          0.2.3
Sh-utils               2.0
Modules Loaded         sb sb_lib uart401 vfat fat

[7.2.] Processor information

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 5
model		: 4
model name	: Pentium MMX
stepping	: 4
cpu MHz		: 167.047
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: yes
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr mce cx8 mmx
bogomips	: 333.41

[7.3] Module information

sb                      7296   0
sb_lib                 34912   0 [sb]
uart401                 6384   0 [sb_lib]
vfat                   10512   3 (autoclean)
fat                    31488   0 (autoclean) [vfat]

[7.4 ] Load driver and harware information

/proc/ioports:

0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0213-0213 : isapnp read
0220-022f : soundblaster
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0a79-0a79 : isapnp write
0cf8-0cff : PCI conf1
4000-403f : Intel Corporation 82371AB PIIX4 ACPI
5000-501f : Intel Corporation 82371AB PIIX4 ACPI
6400-641f : Intel Corporation 82371AB PIIX4 USB
f000-f00f : Intel Corporation 82371AB PIIX4 IDE

/proc/iomen:

00000000-0009fbff : System RAM
0009fc00-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-01ffffff : System RAM
  00100000-00240424 : Kernel code
  00240425-002bdd9f : Kernel data
e0000000-e3ffffff : S3 Inc. 86c764/765 [Trio32/64/64V+]
ffff0000-ffffffff : reserved


[7.5] PCS information

00:00.0 Host bridge: Intel Corporation 430TX - 82439TX MTXC (rev 01)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 64

00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 01)
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0

00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) (prog-if 80 [Master])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Region 4: I/O ports at f000 [size=16]

00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 64
	Interrupt: pin D routed to IRQ 11
	Region 4: I/O ports at 6400 [size=32]

00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 01)
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin ? routed to IRQ 9

00:0a.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (rev 54) (prog-if 00 [VGA])
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 10
	Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=64M]
	Expansion ROM at <unassigned> [disabled] [size=64K]

[7.6] SCSI information

Attached devices: none

[7.7] Other information that might be relevant to the problem (please look in /proc
and include al information that you think to be rellevant):

Excuse, I don't know what to put ...

[X.] Others notes, patches, fixes, workarounds ...

I think I only must say that I enjoy very much use linux kernel and I am very
happy taht there is people offering that high quality kernel to the community,
for this reason thanks a lot.

                 reply	other threads:[~2001-04-10 18:11 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=3AC84AF8@webmail.udg.es \
    --to=u1025597@correu.udg.es \
    --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.