A. explains why I am having troubles duping this issue thus far.
This is prerelease Firmware on a yet to be released card and thus should
not get any driver workarounds if this issue can be resolved in
Firmware. If this can be duped on a released card with released
Firmware, then the story cha
SUN coguar with 11731
YH
On 5/31/07, Salyzyn, Mark <[EMAIL PROTECTED]> wrote:
> No, still get adapter kernel panic
Which adapter are you using?
Sincerely -- Mark Salyzyn
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
Mor
> No, still get adapter kernel panic
Which adapter are you using?
Sincerely -- Mark Salyzyn
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 5/30/07, Salyzyn, Mark <[EMAIL PROTECTED]> wrote:
Yinghai Lu [mailto:[EMAIL PROTECTED] writes:
> aacraid_commit_reset.patch is in the mainline already.
But aacraid_commit_reset.patch is not in 2.6.22-rc3 (to which you report
the issue). Does the aacraid_commit_reset.patch work to resolve this
Yinghai Lu [mailto:[EMAIL PROTECTED] writes:
> aacraid_commit_reset.patch is in the mainline already.
But aacraid_commit_reset.patch is not in 2.6.22-rc3 (to which you report
the issue). Does the aacraid_commit_reset.patch work to resolve this
issue all by itself in the kexec'd kernel? Or alternat
On 5/30/07, Salyzyn, Mark <[EMAIL PROTECTED]> wrote:
I believe this issue is a result of the aacraid_commit_reset patch (as
posted for scsi-misc-2.6, enclosed to permit testing) not yet propagated
to the 2.6.22-rc3 tree.
This is the adapter taking longer than 3 minutes to start after a reset.
I
On 5/30/07, Salyzyn, Mark <[EMAIL PROTECTED]> wrote:
Vivek Goyal [mailto:[EMAIL PROTECTED] writes:
> So most likely if we start disabling the interrupts
> in .shutdown routine we might skip resetting adapter
> on every kexec without any side affects?
Not that simple. The .shutdown would need to
Vivek Goyal [mailto:[EMAIL PROTECTED] writes:
> So most likely if we start disabling the interrupts
> in .shutdown routine we might skip resetting adapter
> on every kexec without any side affects?
Not that simple. The .shutdown would need to perform more resource
cleanups of the .remove call to p
On Wed, May 30, 2007 at 09:57:08AM -0400, Salyzyn, Mark wrote:
> This is clouding the issue, Vivek.
>
> There should be no harm, except to time, resetting the adapter. I do
> want to optimize for boot time, but do not view this as a 'bug' if the
> Adapter should reset during the initialization pro
oyal [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 30, 2007 9:25 AM
> To: Salyzyn, Mark
> Cc: Andrew Morton; Yinghai Lu; Eric W. Biederman; Linux
> Kernel Mailing List; linux-scsi@vger.kernel.org; Michal Piotrowski
> Subject: Re: kexec and aacraid broken
>
>
> On Wed
On Wed, May 30, 2007 at 07:44:02AM -0400, Salyzyn, Mark wrote:
> I believe this issue is a result of the aacraid_commit_reset patch (as
> posted for scsi-misc-2.6, enclosed to permit testing) not yet propagated
> to the 2.6.22-rc3 tree.
>
> This is the adapter taking longer than 3 minutes to start
Morton [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 29, 2007 10:14 PM
> To: Yinghai Lu
> Cc: Vivek Goyal; Eric W. Biederman; AACRAID; Linux Kernel
> Mailing List; linux-scsi@vger.kernel.org; Michal Piotrowski
> Subject: Re: kexec and aacraid broken
>
>
> On Tue, 29 May 2
On Tue, 29 May 2007 18:59:32 -0700 "Yinghai Lu" <[EMAIL PROTECTED]> wrote:
> latest tree, can not use kexec to load 2.6.22-rc3 at least.
>
> got:
>
> AAC0: adapter kernel panic'd fffd
> AAC0: adapter kernel failed to start, init status=0
One of the two diffs below, I guess. Please do a `pa
13 matches
Mail list logo
