Re: USB CF Reader causes Fatal trap 12

Hi,

I've updated the card reader's firmware, cvsup'ed source and rebuilt
kernel and can no longer reproduce this.

Regards,

> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/    >

On Fri, 16 May 2003, Andre Guibert de Bruet wrote:

> "It" was the dump, yes. I accidentally deleted the dump and I'm off to
> work at the moment, so I won't be able to produce another dump until later
> today. Anyway, here are the source code offsets for the functions listed
> in the trace:

[...snip...]

> On Fri, 16 May 2003, Robert Watson wrote:
>
> > On Fri, 16 May 2003, Andre Guibert de Bruet wrote:
> >
> > > No go on the backtrace. It appears as if it got corrupted somehow...
> >
> > I assume "it" here is the dump.  You can still generate source code
> > offsets using the function+offset values in the ddb trace by attaching gdb
> > to the debugging kernel on disk and using:
> >
> > (kgdb) l *g_disk_access+0xa9
> > ...
> > (kgdb) l *g_access_rel+0x20e
> > ...
> >
> > And so on.  No local variable inspection, but helps if your source code
> > and build options aren't quite in sync with the ones of the person doing
> > the debugging.
> >
> > > On Fri, 16 May 2003, Andre Guibert de Bruet wrote:
> > >
> > > > The reader I'm using is a Dazzle 6 in 1 unit. It has worked flawlessly up
> > > > until last night's USB commit. At last boot, it came up as:
> > > >
> > > > > umass0: SCM Microsystems Inc. eUSB ORCA Quad Reader, rev 1.10/5.07, addr 4
> > > > > da0 at umass-sim0 bus 0 target 0 lun 0
> > > > > da0: <eUSB Compact Flash 5.07> Removable Direct Access SCSI-2 device
> > > > > da0: 1.000MB/s transfers
> > > > > da0: 122MB (250368 512 byte sectors: 64H 32S/T 122C)
> > > >
> > > > Upon connection, at the console:
> > > >
> > > > [... some messages that i couldn't copy and paste in time...]
> > > > umass0: Invalid CSW: tag 0 should be 10
> > > > (da0:umass-sim0:0:0:0): AutoSense Failed
> > > > (da0:umass-sim0:0:0:0): removing device entry
> > > > Opened disk da0 -> 5
> > > >
> > > > Fatal trap 12: page fault while in kernel mode
> > > > cpuid = 0; lapic.id = 00000000
> > > > fault virtual address   = 0x1c
> > > > fault code              = supervisor read, page not present
> > > > instruction pointer     = 0x8:0xc01daf29
> > > > stack pointer           = 0x10:0xe42e8b5c
> > > > frame pointer           = 0x10:0xe42e8b84
> > > > code segment            = base 0x0, limit 0xfffff, type 0x1b
> > > >                         = DPL 0, pres 1, def32 1, gran 1
> > > > processor eflags        = interrupt enabled, resume, IOPL = 0
> > > > current process         = 2 (g_event)
> > > > kernel: type 12 trap, code=0
> > > > Stopped at      g_disk_access+0xa9:     cmpl    $0,0x1c(%esi)
> > > > db> call doadump
> > > > Dumping 3583 MB
> > > > ata3: resetting devices ..
> > > > done
> > > >  16 32 48 64 80 [... snip ...] 3568
> > > > Dump complete
> > > > 0xf
> > > >
> > > > db> tr
> > > > g_disk_access(caafdd80,1,0,0,0) at g_disk_access+0xa9
> > > > g_access_rel(cb598b80,1,0,0,e42e8c30) at g_access_rel+0x20e
> > > > g_slice_new(c0406b20,8,caafdd80,e42e8c2c,e42e8c30) at g_slice_new+0xdb
> > > > g_bsd_taste(c0406b20,caafdd80,0,102,caafdd00) at g_bsd_taste+0xa9
> > > > g_new_provider_event(caafdd80,0,c03a3701,b2,66666667) at g_new_provider_event+0x9c
> > > > one_event(e42e8d14,c01dd7a5,c041b30c,0,4c) at one_event+0x20a
> > > > g_run_events(c041b30c,0,4c,c03a3a23,a) at g_run_events+0x8
> > > > g_event_procbody(0,e42e8d48,c03a5629,2f8,c60f7e40) at g_event_procbody+0x45
> > > > fork_exit(c01dd760,0,e42e8d48) at fork_exit+0xc0
> > > > fork_trampoline() at fork_trampoline+0x1a
> > > > --- trap 0x1, eip = 0, esp = 0xe42e8d7c, ebp = 0 ---
> > > >
> > > > GDB trace to follow. Stay tuned...