On Sep 14, 2006, at 2:41 PM, Juan RP wrote:

> On Thu, 14 Sep 2006 19:35:19 +0100 (BST)
> Iain Hibbert <plunky@rya-online.net> wrote:
>
>> Hi,
>>    I've had this happen exactly the same three times now - situation
>> is, I am connected to net over PPP/bluetooth and try to do some
>> memory intensive task (cvs update, load firefox, ..), it first did it
>> on monday (probably source update saturday 9th) but source from last
>> night also did the same.
>>
>>
>> uvm_fault(0xcb169704, 0x4035a000, 1) -> 0xe
>> kernel: supervisor trap page fault, code=0
>> Stopped in pid 826.1 (rfcomm_sppd) at	0xcad09545:
>> testl	%eax,netbsd:cpu_info_primary+0x188(,%ebx,4)
>> db> bt
>> _prop_dictionary_keysym32_pool
>> (c0a4f000,c0b29b00,cb666960,2000,b1b2edf6) at 0xcad09545 pppintr
>> (c0acac00,0,3f661a9c,246,0) at netbsd:pppintr+0x456 softintr_dispatch
>> (1,4b,c0acac00,f0b8001b,cb6669cc) at netbsd:softintr_dispatch+0x2b
>> DDB lost frame for netbsd:Xsoftnet+0x48, trying 0xcb66699c Xsoftnet()
>> at netbsd:Xsoftnet+0x48 --- interrupt ---
>> 0xca3a2420:

That backtrace looks weird -- but you know you can't fiddle with prop  
objects in interrupt context, right?


>> db> reboot
>> syncing disks... 1 1 1 1 1 1 done
>> unmounting file systems... done
>> rebooting...
>>
>>
>> I'm guessing that there is some kind of memory flush that is causing
>> this, since ppp/rfcomm_sppd/bluetooth doesnt really use proplib in
>> this context. Any recent changes that might have caused this?
>
> I'm having problems with sysmon_cpufreq as well, and backtrace was
> something like:
>
> pool_update_curpage
> pool_put
> ...
>
> Maybe last changes to proplib about libkern/rb.c? Jason?

-- thorpej