CAM related panic on 8.2-PRERELEASE Was: Re: USB related panic on 8.2-PRERELEASE

[Oleg Nauman]

On Fri, Dec 10, 2010 at 8:15 PM, Hans Petter Selasky <hselasky at c2i.net> wrote:
> Hi,

 Hello,

>
> I think this is a known issue which never got fixed. Please try the attached
> patch and report back.
>
> XXX_SAFE != XXX_REAL_SAFE :-)

 My laptop experienced a crash again, this time it seems CAM related:

Unread portion of the kernel message buffer:
umass0: at uhub5, port 3, addr 2 (disconnected)
(probe0:umass-sim0:0:0:0): AutoSense failed
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x14
fault code              = supervisor read, page not present
instruction pointer     = 0x20:0xc0736482
stack pointer           = 0x28:0xc5225bd4
frame pointer           = 0x28:0xc5225bec
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = resume, IOPL = 0
current process         = 12 (swi2: cambio)
trap number             = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xc072ac57 at kdb_backtrace+0x47
#1 0xc06ffe97 at panic+0x117
#2 0xc09a31f3 at trap_fatal+0x323
#3 0xc09a3602 at trap+0x152
#4 0xc098c87c at calltrap+0x6
#5 0xc06f25e9 at _mtx_unlock_sleep+0x49
#6 0xc06f2669 at _mtx_unlock_flags+0x49
#7 0xc0473bb0 at camisr+0x110
#8 0xc06de98c at intr_event_execute_handlers+0x14c
#9 0xc06df77e at ithread_loop+0xbe
#10 0xc06dccde at fork_exit+0xee
#11 0xc098c8f4 at fork_trampoline+0x8
Uptime: 6m55s
Physical memory: 2027 MB
Dumping 121 MB: 106 90 74 58 42 26 10

Reading symbols from /boot/modules/bwn_v4_ucode.ko...Reading symbols
from /boot/modules/bwn_v4_ucode.ko.symbols...done.
done.
Loaded symbols for /boot/modules/bwn_v4_ucode.ko
Reading symbols from /boot/modules/cuse4bsd.ko...done.
Loaded symbols for /boot/modules/cuse4bsd.ko
#0  doadump () at pcpu.h:231
231     pcpu.h: No such file or directory.
        in pcpu.h
(kgdb) #0  doadump () at pcpu.h:231
#1  0xc06ffc93 in boot (howto=260) at ../../../kern/kern_shutdown.c:419
#2  0xc06ffed0 in panic (fmt=Variable "fmt" is not available.
) at ../../../kern/kern_shutdown.c:592
#3  0xc09a31f3 in trap_fatal (frame=0xc5225b94, eva=20)
    at ../../../i386/i386/trap.c:946
#4  0xc09a3602 in trap (frame=0xc5225b94) at ../../../i386/i386/trap.c:326
#5  0xc098c87c in calltrap () at ../../../i386/i386/exception.s:166
#6  0xc0736482 in turnstile_broadcast (ts=0x0, queue=0)
    at ../../../kern/subr_turnstile.c:831
#7  0xc06f25e9 in _mtx_unlock_sleep (m=0xc67e170c, opts=0,
    file=0xc0a04b40 "../../../cam/cam_xpt.c", line=4715)
    at ../../../kern/kern_mutex.c:675
#8  0xc06f2669 in _mtx_unlock_flags (m=0xc67e170c, opts=0,
    file=0xc0a04b40 "../../../cam/cam_xpt.c", line=4715)
    at ../../../kern/kern_mutex.c:227
#9  0xc0473bb0 in camisr (dummy=0x0) at ../../../cam/cam_xpt.c:4715
#10 0xc06de98c in intr_event_execute_handlers (p=0xc556f7f8, ie=0xc56a8800)
    at ../../../kern/kern_intr.c:1220
#11 0xc06df77e in ithread_loop (arg=0xc556e2b0)
    at ../../../kern/kern_intr.c:1233
#12 0xc06dccde in fork_exit (callout=0xc06df6c0 <ithread_loop>,
    arg=0xc556e2b0, frame=0xc5225d28) at ../../../kern/kern_fork.c:845
#13 0xc098c8f4 in fork_trampoline () at ../../../i386/i386/exception.s:273
(kgdb)

It happens with
device umass
enabled in my kernel config file

>
> --HPS
>
> On Thursday 09 December 2010 12:02:48 Oleg Nauman wrote:
>> On Wed, Dec 8, 2010 at 7:05 PM, Oleg Nauman <oleg.nauman at gmail.com> wrote:
>> >  Hello Hans,
>> >
>> > On Wed, Dec 8, 2010 at 3:33 PM, Hans Petter Selasky <hselasky at c2i.net>
> wrote:
>> >> On Wednesday 08 December 2010 11:41:28 Oleg Nauman wrote:
>> >>> Hello,
>> >>>
>> >>> Unfortunately my notebook experienced the crash during the attempts to
>> >>> attach EVDO modem supplied with builtin MicroSD cardreader.
>> >>> Related core.txt file is attached as well as 'usbconfig
>> >>> dump_all_config_desc' output (all_config.txt)
>> >>> USB subsystem reports endless USB_ERR_STALLED events during attempts
>> >>> to attach umass device, but attaches it finally ( sometimes it
>> >>> attached after two attempts, sometimes it trying to attach during
>> >>> 15-20 minutes ).MicroSD is inserted there, without any effect  on
>> >>> attachment attempts though.
>> >>
>> >> Hi,
>> >>
>> >> Can you reproduce the panic using a kernel built with INVARIANTS options
>> >> and DEBUG_MEMGUARD .
>> >
>> >  I rebuilt my kernel with options you mentioned ( have added
>> > INVARIANT_SUPPORT required  by INVARIANTS though )
>> >
>> > Waiting on panic..
>>
>>  Got it finally ( core.txt file is attached )
>>
>