>> Anybody have any ideas about how I could find when a particular device
 >> driver version was added to a particular kernel update/patch/errata ?
 >>
 >
 >   rpm -qp --changelog <rpm>
 > or
 >   download all of redhat's kernels, install them, and look.

That did it; traced down the bugzilla reports:
http://rhn.redhat.com/errata/RHBA-2007-0791.html
https://bugzilla.redhat.com/show_bug.cgi?id=245631

I still don't know why these patches were applied, but I now know when.

>> Since this kernel errata was released after rhel4 U6, the qlogic drivers
>> could potentially be newer. My concern is the qlogic device drivers in
>> scientific linux are coming from a different kernel stream.
> 
> p.s. Why are you so worried about these drivers?

Our SAN crashed last, our department lost a week's worth of work, etc (I
still have a job, hurray!). We have various manufacturer/VAR engineering
teams trying to diagnose the root cause. I was embarrassed to admit I
don't know from _when_ and _why_ that particular device driver version 
arrived on our servers.

> On Fri, 25 Jan 2008, Christopher Hunter wrote:
> 
>> To follow up on my own post, I found this kernel version was part of a 
>> recent errata released by TUV:
>> https://rhn.redhat.com/errata/RHSA-2007-1104.html
>>
>> There is nothing mentioned in the errata about updating qlogic 
>> drivers. So far no luck searching the redhat knowledgebase and bug 
>> tracker for when, exactly, these drivers were added to the kernel.
> 
> Sometimes they document it and sometimes they do not.

I find the lack of (TUV) documentation somewhat unsettling.

>> Since this kernel errata was released after rhel4 U6, the qlogic 
>> drivers could potentially be newer. My concern is the qlogic device 
>> drivers in scientific linux are coming from a different kernel stream.
> 
> They are built from TUV src.rpm ,  we DO NOT CHANGE anything for the 
> kernels.
> 
> -Connie Sieh


> We DO NOT change anything in the kernel.
>
>
> Troy

So, you're trying to tell me the kernel source is straight from TUV :)

-- 
Chris Hunter
Systems Programmer, Astronomy Yale University
[log in to unmask]