Bug 193388 - [panic] bad pte
Summary: [panic] bad pte
Status: Closed Not Enough Information
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.0-RELEASE
Hardware: i386 Any
: --- Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-06 12:06 UTC by sasamotikomi
Modified: 2018-05-21 01:40 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sasamotikomi 2014-09-06 12:06:36 UTC
TPTE at 0xbfca1000  IS ZERO @ VA 28400000
panic: bad pte
cpuid = 0
KDB: stack backtrace:
#0 0xc0af6f12 at kdb_backtrace+0x52
#1 0xc0abce21 at panic+0x121
#2 0xc0f92685 at pmap_remove_pages+0x555
#3 0xc0d4f0b4 at vmspace_exit+0x94
#4 0xc0a85f1a at exit1+0x84a
#5 0xc0a856cd at sys_sys_exit+0x1d
#6 0xc0f97929 at syscall+0x479
#7 0xc0f80771 at Xint0x80_syscall+0x21
Comment 1 Alan Cox freebsd_committer 2014-12-31 04:29:19 UTC
Most people who report this panic have hardware problems such as flaky memory.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-20 23:59:54 UTC
For bugs matching the following conditions:
- Status == In Progress
- Assignee == "bugs@FreeBSD.org"
- Last Modified Year <= 2017

Do
- Set Status to "Open"
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2018-05-21 01:40:55 UTC
The PTE code has changed drastically since this was reported, and it was likely a hardware fault in the first place.

Closing unless we get more information.