On Thu, 2005-10-27 at 08:26 -0700, Andrew Vasquez wrote: > On Mon, 24 Oct 2005, Andrew Morton wrote: > > > Badari Pulavarty <pbadari@xxxxxxxxx> wrote: > > > > > > On Mon, 2005-10-24 at 01:48 -0700, Andrew Morton wrote: > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/ > > > > > > > > > > I can't seem to keep my AMD64 machine up with 2.6.14-rc5-mm1. > > > Keep running into following. qlogic driver problem ? > > > > I don't know why the qlogic driver has suddenly started doing this - were > > there any earlier messages which might tell us? Is it possible to increase > > the debugging level? > > > > I can spot one bug in there, but the lockup is just a symptom. > > > > There are no qlogic changes in 2.6.14-rc5-mm1. > > > > > Thanks, > > > Badari > > > > > > NMI Watchdog detected LOCKUP on CPU 0 > > > CPU 0 > > > Modules linked in: qlogicfc qla2300 qla2200 qla2xxx firmware_class > > > qlogicfc attaches to both 2100 and 2200 ISPs. It seems you're then > trying to load qla2xxx driver along with the 2300 and 2200 firmware > loader modules. The pci_request_regions() call during 2200 probing > fails. Hmm. This is happening because I have both qlogicfc and qla2200 as modules ? > > > > <ffffffff8010dd2e>{system_call+12 6} > > > > qla2x00_probe_one() has called qla2x00_free_device() and > > qla2x00_free_device() has locked up in > > wait_for_completion(&ha->dpc_exited); > > > > Presumably, ha->dpc_exited is not initialised yet. > > > > Causing this cleanup badness. > > > The first `goto probe_failed' in qla2x00_probe_one() will cause > > qla2x00_free_device() to run wait_for_completion() against an uninitialised > > completion struct. Because ha->dpc_pid will be >= 0. > > > > This patch might fix the lockup, but if so, qla2x00_iospace_config() > > failed. Please debug that a bit for us? > > Badari, is there some reason you are using qlogicfc? THe qla2xxx > driver supports all QLogic ISP parts. Not intentionally. I have qla2200, qla2300 cards in my machine. I build all the qlogic drivers as modules. I hate to admit it - but I do use modules for qlogic disks. I can't seem to compile the qlogic drivers (2200, 2300) into the kernel and boot without problems (consistently on all my machines - I run into few issues): (1) Between kernels, sometimes probing order changes and my local disks get probed last and screws up my boot process - I don't think this is a qlogic problem. (2) Sometimes, one of the driver complains something like "PCI region already in use" and hangs on boot. BTW, (2) happens even if its modules and I can't boot my machine. Sometimes I had to boot with old kernel and hide the modules - so boot process can't find them to workaround the problem. Is there a "dont-load-modules" option or don't load a specific module option on boot ? Thanks, Badari - : 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
