Bug 28163

Summary:	in_pcballoc Panic in RELENG_4 with large memory. _Not_ Related to swap_pager
Product:	Base System	Reporter:	Simon Shapiro <shimon>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description Simon Shapiro 2001-06-15 04:30:03 UTC

Regardless of the swap_pager problem (which apppears new since 4.2),
the kernel will panic immediately after mounting the root fs.
It appears to have a NULL poiner passed to in_pcballoc.

Fix: 

none :-(
How-To-Repeat: Boot any FreeBSD 4.2 and above on a machine with lots of memory.

Comment 1 billf 2001-06-15 06:45:25 UTC

On Thu, Jun 14, 2001 at 08:25:28PM -0700, Simon Shapiro wrote:

> >Description:
> Regardless of the swap_pager problem (which apppears new since 4.2),
> the kernel will panic immediately after mounting the root fs.
> It appears to have a NULL poiner passed to in_pcballoc.
> >How-To-Repeat:
> Boot any FreeBSD 4.2 and above on a machine with lots of memory.
> >Fix:
> none :-(

so it panics, but you don't include the string[1]. it has a traceback,
but you don't include it. on top of that you provide a way of "repeating"
the problem that is so obviously ambigious that it couldn't even be
considered helpful.

do you expect someone to even look at this PR or is it just a way to
get some anger off your chest? if its the latter, let us know so we
can close this...

-- 
Bill Fumerola - security yahoo         / Yahoo! inc.
              - fumerola@yahoo-inc.com / billf@FreeBSD.org

1. in_pcb.c::in_pcballoc() doesn't even have a panic() in it, unless
something it calls panic()s.

Comment 2 iedowse freebsd_committer

2001-12-03 00:35:45 UTC

State Changed
From-To: open->feedback


Does this problem still occur? If so, could you provide further 
information such as the panic messages and gdb/ddb traces.

Comment 3 iedowse freebsd_committer

2002-06-02 12:19:19 UTC

State Changed
From-To: feedback->closed


Feedback timeout.