Subject: Re: panic pppintr/prop_dictionary_keysym32_pool
To: Iain Hibbert <email@example.com>
From: Jason Thorpe <firstname.lastname@example.org>
Date: 09/27/2006 15:48:03
On Sep 17, 2006, at 1:08 AM, Iain Hibbert wrote:
What's the status of this issue? Any updates? Has a PR been filed?
> On Fri, 15 Sep 2006, Iain Hibbert wrote:
>> I'm thinking that the only 'new' thing I have done recently with
>> to proplib is that bthub_attach() creates a prop_data object and
>> stores it
>> in its device properties dictionary. So, in my current system there
>> be two of these persistent objects.
>> Could this be significant?
> For the record, I think the answer is No.
> I tried without those persistent objects and still managed a
> exactly the same:
> uvm_fault(0xcb166464, 0x35a000, 1) -> 0xe
> kernel: supervisor trap page fault, code=0
> Stopped in pid 6955.1 (rfcomm_sppd) at 0xcad0a545: testl %
> db> bt
> (c0aa1000,c08b7800,cae17960,2000,c0102145) at 0xcad0a545
> pppintr(c0a6a400,f0b800f2,c0a6a400,246,0) at netbsd:pppintr+0x456
> softintr_dispatch(1,36,c0a6a400,f0b800f2,cae179cc) at
> DDB lost frame for netbsd:Xsoftnet+0x48, trying 0xcae1799c
> Xsoftnet() at netbsd:Xsoftnet+0x48
> --- interrupt ---
> I have DIAGNOSTIC enabled, is there anything else I can do that may
> more information?