Bug 82 – Kernel panic: Failed to allocate buffer hash table

Bug 82 - Kernel panic: Failed to allocate buffer hash table

Summary:	Kernel panic: Failed to allocate buffer hash table

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	kernel (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	i386 Linux

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1998-11-15 19:31 EST by jan
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1998-11-23 11:23:29 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description jan 1998-11-15 19:31:16 EST

The boot floppy for the RedHat 5.2 installer contains a
vmlinuz image that crashes my new machine.

Machine Details:
	Tyan S1836DLUAN-GX motherboard
	Dual PII 450MHz
	1GB RAM
	9.1 GB Ultra SCSI western digital hard drive
	Diamond Viper 550 video controller

Boot message:
	...
	calibrating delay loop.. ok - 450.56 BogoMIPS
	initrd overwritten (0x00e00000 < 0x01014e34) - disabling
it.
	Memory: 1032740k/1048576k available (708k kernel code, 384
reserved, 14744k data)
	Bad pmd in pte_alloc: 008000e7
	Kernel panic: Failed to allocate buffer hash table

	In swapper task - not syncing


Note:

The boot floppy for -> RedHat 5.0 <- does not
crash the machine, but I want to install RedHat 5.2

Comment 1 jan 1998-11-16 16:11:59 EST

Found workaround.  It appears the kernel will not boot with very large
memory sizes (such as 1GB).  Giving the following parameters works:

linux mem=1008M expert

Comment 2 David Lawrence 1998-11-17 14:02:59 EST

This problem should be fixed in the latest 2.0.36 final release. Try
downloading the new 2.0.36 rpm when it is made available and try this
one again. If yes then please close the bug report.

Note You need to log in before you can comment on or make changes to this bug.