Try disabling it if the no_reset option doesn't help.
> -> Does it identify the device before the problems start?
>
> Yes, it IDs the first controller, then the first scsi reset happens,
> then it IDs the second controller, more resets, then panic.
Does it identify the drive before the resets start? Does it print out the
speed that the drive is communicating at before the first reset? What exactly
are the messages about the reset? What kind of panic is this? Is there an
oops that goes along with the panic?
> -> What happens if you use the aic7xxx=no_reset flag on bootup?
>
> Haven't tried that. I was under the impression we were strongly discouraged
> from using it, but I'll try it and get back to you.
You are, but if it helps the problem then it gives me a good idea of where the
problem could be coming from.
--
Doug Ledford <dledford@redhat.com>
Opinions expressed are my own, but
they should be everybody's.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/