Here is the dmesg log: http://www.tjhsst.edu/~2010tgeorgio/fclogs/dmesg3.log Here is the complete syslog file, with more junk in it: http://www.tjhsst.edu/~2010tgeorgio/fclogs/messages3.log I will reboot the server and enable error logging. Could this issues be caused by enclosures have conflicting scsi ids? On Thu, Aug 6, 2009 at 12:49 PM, Andrew Vasquez<andrew.vasquez@xxxxxxxxxx> wrote: > Thomas, could you forward the full messages file? I'm interested in > seeing what series of events led up to the BUG_ON(). The snippets > here and in the bugzilla only document the failing point BUG_ON(). > Also, could you get a test run with the driver error-logging enabled > as well: > > $ modprobe -v qla2xxx ql2xextended_error_logging=1 -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
