On Thu, Apr 04, 2013 at 12:41:27PM -0600, Bjorn Helgaas wrote:
> On Thu, Apr 4, 2013 at 11:51 AM, Neil Horman wrote:
>
> > Oh, you want the bug report that I'm fixing this against? Sure, I can do
> > that.
> > I thought you wanted me to include a url in the WARN_TAINT, with which user
> >
On Thu, Apr 4, 2013 at 11:51 AM, Neil Horman wrote:
> Oh, you want the bug report that I'm fixing this against? Sure, I can do
> that.
> I thought you wanted me to include a url in the WARN_TAINT, with which user
> could report occurances of this bug. Yeah, the bug that this is reported in
>
On Thu, Apr 04, 2013 at 11:14:30AM -0600, Bjorn Helgaas wrote:
> On Thu, Apr 4, 2013 at 9:39 AM, Neil Horman wrote:
> > On Thu, Apr 04, 2013 at 08:57:06AM -0600, Bjorn Helgaas wrote:
> >> On Thu, Apr 4, 2013 at 8:50 AM, Neil Horman wrote:
> >> > On Thu, Apr 04, 2013 at 03:27:29PM +0100, David
On Thu, Apr 4, 2013 at 9:39 AM, Neil Horman wrote:
> On Thu, Apr 04, 2013 at 08:57:06AM -0600, Bjorn Helgaas wrote:
>> On Thu, Apr 4, 2013 at 8:50 AM, Neil Horman wrote:
>> > On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
>> >> On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas
On Thu, Apr 04, 2013 at 08:57:06AM -0600, Bjorn Helgaas wrote:
> On Thu, Apr 4, 2013 at 8:50 AM, Neil Horman wrote:
> > On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
> >> On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
> >> > );
> >> > > +
> >> > > + if ((revision
On Thu, Apr 4, 2013 at 8:50 AM, Neil Horman wrote:
> On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
>> On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
>> > );
>> > > +
>> > > + if ((revision == 0x13) && irq_remapping_enabled) {
>> > > +
On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
> On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
> > );
> > > +
> > > + if ((revision == 0x13) && irq_remapping_enabled) {
> > > +pr_warn(HW_ERR "This system BIOS has enabled interrupt
> > >
On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
> );
> > +
> > + if ((revision == 0x13) && irq_remapping_enabled) {
> > +pr_warn(HW_ERR "This system BIOS has enabled interrupt
> > remapping\n"
> > +"on a chipset that contains an errata making
On Wed, Apr 03, 2013 at 05:53:27PM -0600, Bjorn Helgaas wrote:
> [+cc David and iommu list, Yinghai, Jiang]
>
> On Mon, Mar 4, 2013 at 12:04 PM, Neil Horman wrote:
> > A few years back intel published a spec update:
> >
On Wed, Apr 03, 2013 at 05:53:27PM -0600, Bjorn Helgaas wrote:
[+cc David and iommu list, Yinghai, Jiang]
On Mon, Mar 4, 2013 at 12:04 PM, Neil Horman nhor...@tuxdriver.com wrote:
A few years back intel published a spec update:
On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
);
+
+ if ((revision == 0x13) irq_remapping_enabled) {
+pr_warn(HW_ERR This system BIOS has enabled interrupt
remapping\n
+on a chipset that contains an errata making
that\n
+
On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
);
+
+ if ((revision == 0x13) irq_remapping_enabled) {
+pr_warn(HW_ERR This system BIOS has enabled interrupt
remapping\n
+
On Thu, Apr 4, 2013 at 8:50 AM, Neil Horman nhor...@tuxdriver.com wrote:
On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
);
+
+ if ((revision == 0x13) irq_remapping_enabled) {
+
On Thu, Apr 04, 2013 at 08:57:06AM -0600, Bjorn Helgaas wrote:
On Thu, Apr 4, 2013 at 8:50 AM, Neil Horman nhor...@tuxdriver.com wrote:
On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
);
+
+ if
On Thu, Apr 4, 2013 at 9:39 AM, Neil Horman nhor...@tuxdriver.com wrote:
On Thu, Apr 04, 2013 at 08:57:06AM -0600, Bjorn Helgaas wrote:
On Thu, Apr 4, 2013 at 8:50 AM, Neil Horman nhor...@tuxdriver.com wrote:
On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
On Wed, 2013-04-03
On Thu, Apr 04, 2013 at 11:14:30AM -0600, Bjorn Helgaas wrote:
On Thu, Apr 4, 2013 at 9:39 AM, Neil Horman nhor...@tuxdriver.com wrote:
On Thu, Apr 04, 2013 at 08:57:06AM -0600, Bjorn Helgaas wrote:
On Thu, Apr 4, 2013 at 8:50 AM, Neil Horman nhor...@tuxdriver.com wrote:
On Thu, Apr 04,
On Thu, Apr 4, 2013 at 11:51 AM, Neil Horman nhor...@tuxdriver.com wrote:
Oh, you want the bug report that I'm fixing this against? Sure, I can do
that.
I thought you wanted me to include a url in the WARN_TAINT, with which user
could report occurances of this bug. Yeah, the bug that this
On Thu, Apr 04, 2013 at 12:41:27PM -0600, Bjorn Helgaas wrote:
On Thu, Apr 4, 2013 at 11:51 AM, Neil Horman nhor...@tuxdriver.com wrote:
Oh, you want the bug report that I'm fixing this against? Sure, I can do
that.
I thought you wanted me to include a url in the WARN_TAINT, with which
[+cc David and iommu list, Yinghai, Jiang]
On Mon, Mar 4, 2013 at 12:04 PM, Neil Horman wrote:
> A few years back intel published a spec update:
> http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
>
> For the 5520 and 5500 chipsets which
[+cc David and iommu list, Yinghai, Jiang]
On Mon, Mar 4, 2013 at 12:04 PM, Neil Horman nhor...@tuxdriver.com wrote:
A few years back intel published a spec update:
http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
For the 5520 and
On 03/11/2013 07:25 AM, Neil Horman wrote:
> On Sat, Mar 09, 2013 at 03:20:57PM -0700, Myron Stowe wrote:
>> On Sat, Mar 9, 2013 at 1:49 PM, Neil Horman wrote:
>>> On Mon, Mar 04, 2013 at 02:04:19PM -0500, Neil Horman wrote:
A few years back intel published a spec update:
On Sat, Mar 09, 2013 at 03:20:57PM -0700, Myron Stowe wrote:
> On Sat, Mar 9, 2013 at 1:49 PM, Neil Horman wrote:
> > On Mon, Mar 04, 2013 at 02:04:19PM -0500, Neil Horman wrote:
> >> A few years back intel published a spec update:
> >>
On Sat, Mar 09, 2013 at 03:20:57PM -0700, Myron Stowe wrote:
On Sat, Mar 9, 2013 at 1:49 PM, Neil Horman nhor...@tuxdriver.com wrote:
On Mon, Mar 04, 2013 at 02:04:19PM -0500, Neil Horman wrote:
A few years back intel published a spec update:
On 03/11/2013 07:25 AM, Neil Horman wrote:
On Sat, Mar 09, 2013 at 03:20:57PM -0700, Myron Stowe wrote:
On Sat, Mar 9, 2013 at 1:49 PM, Neil Horman nhor...@tuxdriver.com wrote:
On Mon, Mar 04, 2013 at 02:04:19PM -0500, Neil Horman wrote:
A few years back intel published a spec update:
On 03/09/2013 05:20 PM, Myron Stowe wrote:
On Sat, Mar 9, 2013 at 1:49 PM, Neil Horman wrote:
On Mon, Mar 04, 2013 at 02:04:19PM -0500, Neil Horman wrote:
A few years back intel published a spec update:
On 03/09/2013 05:20 PM, Myron Stowe wrote:
On Sat, Mar 9, 2013 at 1:49 PM, Neil Hormannhor...@tuxdriver.com wrote:
On Mon, Mar 04, 2013 at 02:04:19PM -0500, Neil Horman wrote:
A few years back intel published a spec update:
On Sat, Mar 9, 2013 at 1:49 PM, Neil Horman wrote:
> On Mon, Mar 04, 2013 at 02:04:19PM -0500, Neil Horman wrote:
>> A few years back intel published a spec update:
>> http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
>>
>> For the 5520
On Mon, Mar 04, 2013 at 02:04:19PM -0500, Neil Horman wrote:
> A few years back intel published a spec update:
> http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
>
> For the 5520 and 5500 chipsets which contained an errata (specificially
On Mon, Mar 04, 2013 at 02:04:19PM -0500, Neil Horman wrote:
A few years back intel published a spec update:
http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
For the 5520 and 5500 chipsets which contained an errata (specificially
On Sat, Mar 9, 2013 at 1:49 PM, Neil Horman nhor...@tuxdriver.com wrote:
On Mon, Mar 04, 2013 at 02:04:19PM -0500, Neil Horman wrote:
A few years back intel published a spec update:
http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
A few years back intel published a spec update:
http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
For the 5520 and 5500 chipsets which contained an errata (specificially errata
53), which noted that these chipsets can't properly do
A few years back intel published a spec update:
http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
For the 5520 and 5500 chipsets which contained an errata (specificially errata
53), which noted that these chipsets can't properly do
32 matches
Mail list logo
