CURRENT + amd64 + user-ppp = panic

[Vladimir Kushnir]

On Fri, 28 Oct 2005, John Baldwin wrote:

> On Friday 28 October 2005 05:59 pm, Vladimir Kushnir wrote:
>> On Fri, 28 Oct 2005, John Baldwin wrote:
>>> On Wednesday 26 October 2005 09:36 pm, Scott Long wrote:
>>>> Vladimir Kushnir wrote:
>>>>> I'm running now on the kernel from Oct 19 which also panicks, BTW, with
>>>>> "kmem_map too small" on an attempt to run something like Linux
>>>>> OpenOffice or Mathematica (neither kern.ipc.nmbclusters nor
>>>>> vm.kmem_size_max tweaking helps; besides, I've only 512 MB RAM)
>>
>> <snip>
>>
>>> This looks like a page fault rather than a 'kmem_map too small' panic.
>>
>> Sorry I was unclear. It IS a page fault. Panic with a 'kmem_map too small'
>> is with my old (otherwise working) kernel.
>>
>> <snip>
>>
>>> This is here:
>>> 		while (c) {
>>> 			depth++;
>>> 		==>	if (c->c_time != curticks) {
>>> 				c = TAILQ_NEXT(c, c_links.tqe);
>>>
>>> c can't be NULL due to the while loop.  Are any kernel modules being
>>> unloaded when this happens?
>>
>> No. /usr/sbin/ppp was trying to connect to my provider was all.
>
> How?  Using pppoe does try to kldload ng_pppoe.ko and its dependencies for
> example, and ppp might also try to kldload if_tun.ko as well if it's needed.
> Also, is this reproducible?
>

Plain modem (external, on COM1...errr...sio0) dial-up, no pppoe. And tun 
is compiled into GENERIC. And yes, it's 100% reproducible :-(