From: devzero@web.de
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: akpm@linux-foundation.org, jgarzik@redhat.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
rjw@sisk.pl
Subject: Re: modprobe aha1542 oops with git17
Date: Sun, 04 May 2008 00:38:02 +0200 [thread overview]
Message-ID: <263952368@web.de> (raw)
thanks for the pointers !
i`m new to git and i thought i had fetched the latest git (just fetched via http some hours ago) - wondering why my copy doesn`t have that fix.....
will need learn more about git - sorry for the noise
> -----Ursprüngliche Nachricht-----
> Von: "James Bottomley" <James.Bottomley@HansenPartnership.com>
> Gesendet: 04.05.08 00:24:11
> An: devzero@web.de
> CC: akpm@linux-foundation.org, jgarzik@redhat.com, rjw@sisk.pl, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
> Betreff: Re: modprobe aha1542 oops with git17
> On Sat, 2008-05-03 at 22:29 +0200, devzero@web.de wrote:
> > this also happens on real hardware with latest git - no aha1542
> > attached
> >
> > didn`t happen before - looks like a regression to me
>
> Actually, if you check with our tool sets:
>
> http://www.kerneloops.org/search.php?search=scsi_destroy_command_freelist&btnG=Function+Search
>
> They'll point you to the bugzilla entry:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=10598
>
> And the fix (which is now upstream):
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=61d7416a286e840d905c18b1e6b0977c036c8656
>
> James
>
>
>
_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten!
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114
next reply other threads:[~2008-05-03 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 22:38 devzero [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-03 20:29 modprobe aha1542 oops with git17 devzero
2008-05-03 22:23 ` James Bottomley
2008-05-01 23:49 Roland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=263952368@web.de \
--to=devzero@web.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox