Skip to contentSkip to conversation

Fusion problems with 2.6.5rc1 on AMD x86-64 III

DISCUSSION Andi Kleen 1 participant 2 messages Mar 17, 2004 2 messages not in the archive SCSI

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#2 lore raw
Quoted 3 lines · On Wed, 17 Mar 2004 06:03:32 +0100 Andi Kleen <[email protected]> wrote:

The actual problem is the recent consistent_dma_mask change from James. For some reason the x86-64 pci_alloc_consistent always sees an 0xffffffffffffffff dma mask now and that breaks Fusion.

I found some bugs in x86-64 code now that explained the problem. For some reason the consistent mask patchkit seems to have triggered them. It's fixed now.

-Andi

author
#3 lore raw

Re: Fusion problems with 2.6.5rc1 on AMD x86-64 IV

Quoted 10 lines · On Wed, 17 Mar 2004 10:00:40 +0100 Andi Kleen <[email protected]> wrote:
Quoted 3 lines · On Wed, 17 Mar 2004 06:03:32 +0100 Andi Kleen <[email protected]> wrote:

The actual problem is the recent consistent_dma_mask change from James. For some reason the x86-64 pci_alloc_consistent always sees an 0xffffffffffffffff dma mask now and that breaks Fusion.

I found some bugs in x86-64 code now that explained the problem. For some reason the consistent mask patchkit seems to have triggered them. It's fixed now.

Sorry for the many follow ups to myself :-)

Anyways the consistent mask problem is still with us. I just have a workaround that works (force it to 4GB) and there were related bugs in the x86-64 IOMMU code.

James, can you take a look at that please? From a first look i didn't find the place where it is set to 0xffffffffffffffff. It isn't the driver.

-Andi