Cyril Plisko ??: > On Mon, Feb 23, 2009 at 8:20 AM, Michael Li <Mikore.Li at sun.com> wrote: > > >> Hi, Cyril Plisko and Bernd, >> >> I just found a bug in the packages, when I do the test on Nevada build109, >> it resulted to similar panic each time reboot: >> >> - integrated incorrect /etc/sock2path (from b105) file into the >> packages(b107+). >> >> Just now, I have fixed this issue in the packages, please re-run the >> btms_installer.sh script to verify the fix. >> >> > > Michael, > > I am running these bits on snv_108 (SXCE in case it is not clear) and > it panics immediately after starting VirtualBox guest (Windows XP if > it matters, but it doesn't even get to VirtualBox logo in the guest, > so I think it is irrelevant). > The kernel stack trace looks weird, but may be it will make sense to you: > > panic[cpu1]/thread=ffffff014fd1d1a0: > assertion failed: afd->a_fd[i] == -1, file: ../../common/os/fio.c, line: 464 > > > ffffff0004486df0 genunix:assfail+7e () > ffffff0004486e20 genunix:clear_stale_fd+80 () > ffffff0004486f00 genunix:post_syscall+39e () > ffffff0004486f10 unix:brand_sys_syscall+31d () > > > > BTW, I find that using ZFS snapshots for easily getting back after > installing test kernel bits is really invaluable. zfs rollback > followed by reboot and your system is back as it was ! > > Cyril,
What I can tell you so far is that this panic has nothing to do with bluetooth codes, but there might be something is broken with the un-normal install method. I tested on SXCE B107, and Nevada build108, build109, I can not reproduce the problem you reported. (Maybe needs to install virtualbox to reproduce it?) btw, I have modified source to generate standard packages for both SXCE b107 and Indinana 0906 build107, the installation test under Indianan 0906 build107 has worked with bluetooth mouse, once the same test under SXCE b107 is accomplished, I will upload them to bluetooth project asap. Thanks, Michael
