Just modify the driver slightly to hijack a different device prefix :)
Adrian 2009/6/17 pluknet <[email protected]>: > 2009/6/17 Ed Maste <[email protected]>: >> On Tue, Jun 16, 2009 at 07:03:34PM +0400, pluknet wrote: >> >>> As for allpcpu, I often see the picture, when one CPU runs the "irq17: >>> bce1 aacu0" thread >>> and another one runs arcconf. I wonder if that might be a source of >>> bad locking or races, or.. >>> The arcconf utility uses ioctl that goes into aac/aacu(4) internals. >> >> Do you see the same result w/ the in-tree aac(4) driver as opposed to >> Adaptec's version? >> >> -Ed >> > > [It's quite hard to move back to aac(4) as that requires fstab update > [ aacdu0 -> aacd0] > and instant reboot, because we use quotas and quotacheck looks into > /etc/fstab. > Such preparations as fstab update and commenting out load_aacu="YES" will give > discrepancy between fstab and actual mount points.] > > I will try anyway. Thank you for your help. > > -- > wbr, > pluknet > _______________________________________________ > [email protected] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[email protected]" > _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
