Re: [Bulk] Re: New if_zyd driver

On Sun, Oct 21, 2007 at 12:05:42AM -0700, John Merryweather Cooper wrote:
> Weongyo Jeong wrote:
> > On Thu, Aug 30, 2007 at 04:14:22PM +0200, Ted Lindgreen wrote:
> > [... snipped ...]
> >   
> >> However, the stick needs to be inserted after booting up. Then I can
> >> also remove the stick without ill effects (for logmessages see below).
> >>
> >> When the stick is present during boot, the log shows:
> >>  Aug 30 15:25:17 lapje kernel: zyd0: <ZyDAS USB2.0 WLAN, class 255/255, rev 2.00/48.10, addr 2> on uhub4
> >>  Aug 30 15:25:17 lapje kernel: zyd0: setting config no failed
> >>     
> > [... snipped ...]
> >
> > Hello Ted,
> >
> > I send you a patch which is attached with this email to fix a reset
> > problem of the zyd driver when we reboot.
> >
> > In my environment, this patch was worked.  Would you please test this
> > patch and send me results?  I hope it works.  :-)
> >
> > Regards,
> > Weongyo Jeong
> 
> Well, the patch applies cleanly and builds on an amd64:
> 
> Copyright (c) 1992-2007 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>         The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 7.0-BETA1 #16: Sat Oct 20 14:58:28 PDT 2007
>     root_at_borgdemon3.temp.wsu.edu:/usr/obj/usr/src/sys/TURION
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-64 (2210.07-MHz K8-class CPU)
>   Origin = "AuthenticAMD"  Id = 0x60f81  Stepping = 1
>  
> Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
>   Features2=0x2001<SSE3,CX16>
>   AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!>
>   AMD Features2=0x11f<LAHF,CMP,SVM,ExtAPIC,CR8,Prefetch>
>   Cores per package: 2
> 
> . . . .
> 
> zyd0: <Belkin USB2.0 WLAN, class 255/255, rev 2.00/48.10, addr 3> on uhub1
> zyd0: HMAC ZD1211B, FW 47.25, RF AL2230, PA 0, address 00:17:3f:b0:d4:97
> zyd0: Ethernet address: 00:17:3f:b0:d4:97
> zyd0: if_start running deferred for Giant
> 
> I realize that the patch wasn't designed to fix my problem (locking up
> when zyd0 is on a moderate load--like cvsup'ing).  Nevertheless, here's
> what kgdb has to say:
> 
> jcooper_at_borgdemon3$ sudo kgdb kernel.debug /var/crash/vmcore.9
> [GDB will not be able to debug user-mode threads:
> /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "amd64-marcel-freebsd".
> 
> Unread portion of the kernel message buffer:
> zyd0: could not transmit buffer: SHORT_XFER
> 
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 1; apic id = 01
> fault virtual address   = 0x2734
> fault code              = supervisor write data, page not present
> instruction pointer     = 0x8:0xffffffff808a94fa
> stack pointer           = 0x10:0xffffffffab8dfaf0
> frame pointer           = 0x10:0xffffffffab8dfb30
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 23 (irq22: ohci0 ehci0)
> trap number             = 12
> panic: page fault
> cpuid = 1
> Uptime: 8m38s
> Physical memory: 1973 MB
> Dumping 233 MB: 218 202 186 170 154 138 122 106 90 74 58 42 26 10
> 
> #0  doadump () at pcpu.h:194
> 194             __asm __volatile("movq %%gs:0,%0" : "=r" (td));
> (kgdb)
> 
> -------
> 
> jmc

Yes.  This patch isn't related with your problem.  Your problem is
on my TODO list but I think that it would be hard and takes some times
to fix because of the lack of environments that I don't have amd64,
Belkin devices and the zyd driver on my environment works well without
problems.

Can you show me the backtrace log of `$ kgdb kernel.debug
/var/crash/vmcore.9'?

Regards,
Weongyo Jeong