LinuxLists.cc - [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Robert Hancock wrote:
> This fixes some problems with ATAPI devices on nForce4 controllers in ADMA mode
> on systems with memory located above 4GB. We need to delay setting the 64-bit
> DMA mask until the PRD table and padding buffer are allocated so that they don't
> get allocated above 4GB and break legacy mode (which is needed for ATAPI
> devices).
...

Mmm.. I wonder how many other libata drivers have this exact same bug,
whether noticed yet or not ?

Cheers

2007-11-23 17:35:18

by Morrison, Tom

[permalink] [raw]

Subject: RE: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

I am hopeful that the sata_mv has this bug (I proved that the
problem I was experiencing was due to the sata_mv driver
with 3.75Gig or more of memory)...

I am on vacation for a week or more ...or I'd tell you today
if it did have this bug!

________________________________

From: [email protected] on behalf of Mark Lord
Sent: Fri 11/23/2007 10:22 AM
To: Robert Hancock
Cc: linux-kernel; ide; Jeff Garzik; Tejun Heo
Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Robert Hancock wrote:
> This fixes some problems with ATAPI devices on nForce4 controllers in ADMA mode
> on systems with memory located above 4GB. We need to delay setting the 64-bit
> DMA mask until the PRD table and padding buffer are allocated so that they don't
> get allocated above 4GB and break legacy mode (which is needed for ATAPI
> devices).
...

Mmm.. I wonder how many other libata drivers have this exact same bug,
whether noticed yet or not ?

Cheers

2007-11-23 17:46:50

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Morrison, Tom wrote:
> I am hopeful that the sata_mv has this bug (I proved that the
> problem I was experiencing was due to the sata_mv driver
> with 3.75Gig or more of memory)...
>
> I am on vacation for a week or more ...or I'd tell you today
> if it did have this bug!
..

Yeah, I kind of had your reports in mind when I asked that. :)

On a related note, I now have lots of Marvell (sata_mv) hardware here,
and an Intel CPU/chipset box with physical RAM above the 4GB boundary.

Cheers

2007-11-23 18:47:20

by Morrison, Tom

[permalink] [raw]

Subject: RE: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Yes, I believe that - otherwise, this problem would have
been a crisis a LONG time ago...:-)

But I do have some more questions in relationship to how
things are mapped in your environment. I have a flat memory
map (i.e.: the full 0x0 -- 0x1_0000_0000 is passed to the 32bit
Linux kernel without any 'holes' and/or reserved areas).

Does your Intel memory map have this same type of flat memory
model (and thus allow use of the FULL lower 4Gig) - or does it
reserve areas of lower 4Gig for devices and such - if not - where
are these reserved areas - and how do the relate to the I/O memory
map for the device?

In other words, I would be very interested in seeing the memory
map & the PCI memory mapping to see if any overlap/correspond
to reserve areas of lower 4 Gig (in a linux 32bit mode)...

Tom

________________________________

From: Mark Lord [mailto:[email protected]]
Sent: Fri 11/23/2007 12:46 PM
To: Morrison, Tom
Cc: Robert Hancock; linux-kernel; ide; Jeff Garzik; Tejun Heo
Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Morrison, Tom wrote:
> I am hopeful that the sata_mv has this bug (I proved that the
> problem I was experiencing was due to the sata_mv driver
> with 3.75Gig or more of memory)...
>
> I am on vacation for a week or more ...or I'd tell you today
> if it did have this bug!
..

Yeah, I kind of had your reports in mind when I asked that. :)

On a related note, I now have lots of Marvell (sata_mv) hardware here,
and an Intel CPU/chipset box with physical RAM above the 4GB boundary.

Cheers

2007-11-23 20:40:26

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Mark wrote:
> Yeah, I kind of had your reports in mind when I asked that. :)
>
> On a related note, I now have lots of Marvell (sata_mv) hardware here,
> and an Intel CPU/chipset box with physical RAM above the 4GB boundary.

Morrison, Tom wrote:
> Yes, I believe that - otherwise, this problem would have
> been a crisis a LONG time ago...:-)
>
> But I do have some more questions in relationship to how
> things are mapped in your environment. I have a flat memory
> map (i.e.: the full 0x0 -- 0x1_0000_0000 is passed to the 32bit
> Linux kernel without any 'holes' and/or reserved areas).
>
> Does your Intel memory map have this same type of flat memory
> model (and thus allow use of the FULL lower 4Gig) - or does it
> reserve areas of lower 4Gig for devices and such - if not - where
> are these reserved areas - and how do the relate to the I/O memory
> map for the device?
>
> In other words, I would be very interested in seeing the memory
> map & the PCI memory mapping to see if any overlap/correspond
> to reserve areas of lower 4 Gig (in a linux 32bit mode)...
...

I believe that only 2GB or so of the 4GB RAM appears below the 4GB boundary.
The rest is accessed above 4GB, using Intel's 36-bit PAE functionality.

I think what you want to see is /proc/mtrr, annotated below by me:

reg00: base=0x080000000 (2048MB), size=2048MB: uncachable, count=1 I/O space
reg01: base=0x000000000 ( 0MB), size=4096MB: write-back, count=1 first 2GB of RAM + I/O space
reg02: base=0x100000000 (4096MB), size=1024MB: write-back, count=1 third GB of RAM
reg03: base=0x140000000 (5120MB), size= 512MB: write-back, count=1 portion of 4th GB of RAM
reg04: base=0x160000000 (5632MB), size= 256MB: write-back, count=1 portion of 4th GB of RAM
reg05: base=0x170000000 (5888MB), size= 128MB: write-back, count=1 portion of 4th GB of RAM
reg06: base=0x178000000 (6016MB), size= 64MB: write-back, count=1 portion of 4th GB of RAM
reg07: base=0x0af800000 (2808MB), size= 8MB: uncachable, count=1 (?) dunno

>From that, the visible RAM should be 2048 + 1024 + 512 + 256 + 128 + 64 = 3968MB.
In /proc/meminfo, it reports MemTotal of 4067260kB, which divided by 1024 gives 3971MB.

The BIOS reports 4024MB.

But the MTRR values above do make it rather clear that nearly half the RAM
requires 33-bit physical addressing for access.

Cheers

2007-11-24 00:14:00

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Mark Lord wrote:
> Morrison, Tom wrote:
>> I am hopeful that the sata_mv has this bug (I proved that the
>> problem I was experiencing was due to the sata_mv driver with 3.75Gig
>> or more of memory)...
>>
>> I am on vacation for a week or more ...or I'd tell you today
>> if it did have this bug!
> ..
>
> Yeah, I kind of had your reports in mind when I asked that. :)
>
> On a related note, I now have lots of Marvell (sata_mv) hardware here,
> and an Intel CPU/chipset box with physical RAM above the 4GB boundary.

Based on a quick look at sata_mv it appears it sets a 64-bit DMA mask
unconditionally, but for non-ATA_PROT_DMA commands (which includes all
ATAPI), it just falls back to ata_qc_issue_prot which issues via the
legacy SFF interface and can only handle 32-bit addressing. So yes, it
appears to have a similar bug as sata_nv had.

Likely it needs a similar slave_config trick to change bounce limit
depending on the connected device, unless there is really a way to issue
ATAPI commands with this EDMA interface, as the TODO list in sata_mv.c
suggests may be possible..

--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/

2007-11-24 00:20:26

by Jeff Garzik

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Robert Hancock wrote:
> Based on a quick look at sata_mv it appears it sets a 64-bit DMA mask
> unconditionally, but for non-ATA_PROT_DMA commands (which includes all
> ATAPI), it just falls back to ata_qc_issue_prot which issues via the
> legacy SFF interface and can only handle 32-bit addressing. So yes, it
> appears to have a similar bug as sata_nv had.

sata_mv doesn't do ATAPI at all...

Jeff

2007-11-24 00:32:56

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Jeff Garzik wrote:
> Robert Hancock wrote:
>> Based on a quick look at sata_mv it appears it sets a 64-bit DMA mask
>> unconditionally, but for non-ATA_PROT_DMA commands (which includes all
>> ATAPI), it just falls back to ata_qc_issue_prot which issues via the
>> legacy SFF interface and can only handle 32-bit addressing. So yes, it
>> appears to have a similar bug as sata_nv had.
>
>
> sata_mv doesn't do ATAPI at all...

Right.. missed that ATA_FLAG_NO_ATAPI. So these issues Tom is reporting
are just with a normal SATA hard drive?

--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/

2007-11-24 02:48:23

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

2007-11-24 05:12:31

by Tejun Heo

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Robert Hancock wrote:
> This fixes some problems with ATAPI devices on nForce4 controllers in ADMA mode
> on systems with memory located above 4GB. We need to delay setting the 64-bit
> DMA mask until the PRD table and padding buffer are allocated so that they don't
> get allocated above 4GB and break legacy mode (which is needed for ATAPI
> devices).
>
> Signed-off-by: Robert Hancock <[email protected]>

Acked-by: Tejun Heo <[email protected]>

Thanks.

--
tejun

2007-12-04 22:17:24

by Jeff Garzik

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Robert Hancock wrote:
> This fixes some problems with ATAPI devices on nForce4 controllers in ADMA mode
> on systems with memory located above 4GB. We need to delay setting the 64-bit
> DMA mask until the PRD table and padding buffer are allocated so that they don't
> get allocated above 4GB and break legacy mode (which is needed for ATAPI
> devices).
>
> Signed-off-by: Robert Hancock <[email protected]>

This is a bit nasty :/

I would consider setting the consistent DMA mask to 32-bit, and setting
the overall mask to 64-bit.

Seems like that would solve the problem?

Also, does this need to be rebased on top of what I just pushed upstream?

Jeff

2007-12-05 01:10:00

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Jeff Garzik wrote:
> Robert Hancock wrote:
>> This fixes some problems with ATAPI devices on nForce4 controllers in
>> ADMA mode
>> on systems with memory located above 4GB. We need to delay setting the
>> 64-bit
>> DMA mask until the PRD table and padding buffer are allocated so that
>> they don't
>> get allocated above 4GB and break legacy mode (which is needed for ATAPI
>> devices).
>>
>> Signed-off-by: Robert Hancock <[email protected]>
>
> This is a bit nasty :/
>
> I would consider setting the consistent DMA mask to 32-bit, and setting
> the overall mask to 64-bit.
>
> Seems like that would solve the problem?

The issue with that is that it would also constrain the ADMA CPB/PRD
table allocation to 32-bit, which I'd rather avoid having to do. There
are dual-socket Opteron boxes like HP xw9300 that use this controller,
and limiting the allocation to 32-bit could force a non-optimal node
allocation for the table memory.

These type of devices really want a version of dma_alloc_coherent that
allows overriding the DMA mask for specific allocations to make this
cleaner. I'm sure this isn't the only device that has different DMA mask
requirements for different consistent memory allocations..

This patch does has the advantage of being confirmed to fix the
reporter's problem (https://bugzilla.redhat.com/show_bug.cgi?id=351451)
which there's something to be said for this late in the .24-rc series..

>
> Also, does this need to be rebased on top of what I just pushed upstream?

It don't think so.. this change is independent from the "sata_nv: don't
use legacy DMA in ADMA mode (v3)" patch you just merged.

--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/

2007-12-08 18:38:25

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

2007-12-17 12:19:31

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Hello,

I am seeing that this doesn't fix a Dell PowerEdge T105 which has the CK804 chipset.

This system has a "HL-DT-ST" DVD-ROM (See dmesg with this posting) attached to the sata ports and has 8Gb physical memory.

The SATA DVD rom gets detected but any I/O like dd or mount is not successful.

If I reduce the memory with mem=<4Gb or disable the adma mode by passing adma=0, I am able to mount the media or do I/O.

Dmesg output -

Linux version 2.6.24-rc5-default (root@Pandora) (gcc version 4.1.2 20070115 (prerelease) (SUSE Linux)) #2 SMP Thu Dec 13 15:38:25 IST 2007
Command line: root=/dev/disk/by-id/scsi-3600508e0000000003ad8e2c732a09d08-part3 vga=0x31a resume=/dev/sda2 splash=verbose showopts
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009cc00 (usable)
BIOS-e820: 000000000009cc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000cc000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007fff0000 (usable)
BIOS-e820: 000000007fff0000 - 0000000080000000 (reserved)
BIOS-e820: 0000000080000000 - 00000000cff00000 (usable)
BIOS-e820: 00000000cff00000 - 00000000cff0a000 (ACPI data)
BIOS-e820: 00000000cff0a000 - 00000000cff80000 (ACPI NVS)
BIOS-e820: 00000000cff80000 - 00000000d0000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000230000000 (usable)
Entering add_active_range(0, 0, 156) 0 entries of 3200 used
Entering add_active_range(0, 256, 524272) 1 entries of 3200 used
Entering add_active_range(0, 524288, 851712) 2 entries of 3200 used
Entering add_active_range(0, 1048576, 2293760) 3 entries of 3200 used
end_pfn_map = 2293760
DMI present.
ACPI: RSDP 000F7AE0, 0014 (r0 PTLTD )
ACPI: RSDT CFF064D5, 004C (r1 DELL PE_SC3 6040000 DELL 0)
ACPI: FACP CFF09906, 0074 (r1 DELL PE_SC3 6040000 DELL F4240)
ACPI: DSDT CFF06521, 33E5 (r1 DELL PE_SC3 6040000 MSFT 100000E)
ACPI: FACS CFF0AFC0, 0040
ACPI: TCPA CFF0997A, 0032 (r1 Phoeni x 6040000 TL 0)
ACPI: SLIC CFF099AC, 0176 (r1 DELL PE_SC3 6040000 PTL 1)
ACPI: SPCR CFF09B22, 0050 (r1 DELL PE_SC3 6040000 PTL 1)
ACPI: SRAT CFF09B72, 00C8 (r1 AMD HAMMER 6040000 AMD 1)
ACPI: SSDT CFF09C3A, 02CC (r1 AMD POWERNOW 6040000 AMD 1)
ACPI: MCFG CFF09F06, 003C (r1 PTLTD MCFG 6040000 LTP 0)
ACPI: HPET CFF09F42, 0038 (r1 PTLTD HPETTBL 6040000 LTP 1)
ACPI: APIC CFF09F7A, 005E (r1 PTLTD APIC 6040000 LTP 0)
ACPI: BOOT CFF09FD8, 0028 (r1 PTLTD $SBFTBL$ 6040000 LTP 1)
SRAT: PXM 0 -> APIC 0 -> Node 0
SRAT: PXM 0 -> APIC 1 -> Node 0
SRAT: Node 0 PXM 0 0-a0000
Entering add_active_range(0, 0, 156) 0 entries of 3200 used
SRAT: Node 0 PXM 0 0-d0000000
Entering add_active_range(0, 0, 156) 1 entries of 3200 used
Entering add_active_range(0, 256, 524272) 1 entries of 3200 used
Entering add_active_range(0, 524288, 851712) 2 entries of 3200 used
SRAT: Node 0 PXM 0 0-230000000
Entering add_active_range(0, 0, 156) 3 entries of 3200 used
Entering add_active_range(0, 256, 524272) 3 entries of 3200 used
Entering add_active_range(0, 524288, 851712) 3 entries of 3200 used
Entering add_active_range(0, 1048576, 2293760) 3 entries of 3200 used
NUMA: Using 63 for the hash shift.
Bootmem setup node 0 0000000000000000-0000000230000000
Zone PFN ranges:
DMA 0 -> 4096
DMA32 4096 -> 1048576
Normal 1048576 -> 2293760
Movable zone start PFN for each node
early_node_map[4] active PFN ranges
0: 0 -> 156
0: 256 -> 524272
0: 524288 -> 851712
0: 1048576 -> 2293760
On node 0 totalpages: 2096780
DMA zone: 96 pages used for memmap
DMA zone: 2540 pages reserved
DMA zone: 1360 pages, LIFO batch:0
DMA32 zone: 24480 pages used for memmap
DMA32 zone: 823120 pages, LIFO batch:31
Normal zone: 29184 pages used for memmap
Normal zone: 1216000 pages, LIFO batch:31
Movable zone: 0 pages used for memmap
ACPI: PM-Timer IO Port: 0x8008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
ACPI: HPET id: 0x10de8201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
swsusp: Registered nosave memory region: 000000000009c000 - 000000000009d000
swsusp: Registered nosave memory region: 000000000009d000 - 00000000000a0000
swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000cc000
swsusp: Registered nosave memory region: 00000000000cc000 - 0000000000100000
swsusp: Registered nosave memory region: 000000007fff0000 - 0000000080000000
swsusp: Registered nosave memory region: 00000000cff00000 - 00000000cff0a000
swsusp: Registered nosave memory region: 00000000cff0a000 - 00000000cff80000
swsusp: Registered nosave memory region: 00000000cff80000 - 00000000d0000000
swsusp: Registered nosave memory region: 00000000d0000000 - 00000000e0000000
swsusp: Registered nosave memory region: 00000000e0000000 - 00000000f0000000
swsusp: Registered nosave memory region: 00000000f0000000 - 00000000fec00000
swsusp: Registered nosave memory region: 00000000fec00000 - 00000000fec10000
swsusp: Registered nosave memory region: 00000000fec10000 - 00000000fee00000
swsusp: Registered nosave memory region: 00000000fee00000 - 00000000fee01000
swsusp: Registered nosave memory region: 00000000fee01000 - 00000000fff80000
swsusp: Registered nosave memory region: 00000000fff80000 - 0000000100000000
Allocating PCI resources starting at d1000000 (gap: d0000000:10000000)
SMP: Allowing 2 CPUs, 0 hotplug CPUs
PERCPU: Allocating 441112 bytes of per cpu data
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2040480
Policy zone: Normal
Kernel command line: root=/dev/disk/by-id/scsi-3600508e0000000003ad8e2c732a09d08-part3 vga=0x31a resume=/dev/sda2 splash=verbose showopts
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
hpet clockevent registered
TSC calibrated against HPET
Marking TSC unstable due to TSCs unsynchronized
time.c: Detected 2812.958 MHz processor.
Console: colour dummy device 80x25
console [tty0] enabled
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES: 8
... MAX_LOCK_DEPTH: 30
... MAX_LOCKDEP_KEYS: 2048
... CLASSHASH_SIZE: 1024
... MAX_LOCKDEP_ENTRIES: 8192
... MAX_LOCKDEP_CHAINS: 16384
... CHAINHASH_SIZE: 8192
memory used by lock dependency info: 1712 kB
per task-struct memory footprint: 2160 bytes
Checking aperture...
CPU 0: aperture @ 4000000 size 32 MB
Aperture too small (32 MB)
No AGP bridge found
Your BIOS doesn't leave a aperture memory hole
Please enable the IOMMU option in the BIOS setup
This costs you 64 MB of RAM
Mapping aperture over 65536 KB of RAM @ 4000000
Memory: 8091848k/9175040k available (2232k kernel code, 295272k reserved, 1390k data, 720k init)
Calibrating delay using timer specific routine.. 5629.62 BogoMIPS (lpj=11259258)
Security Framework initialized
Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU 0/0 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
lockdep: not fixing up alternatives.
ACPI: Core revision 20070126
Parsing all Control Methods:
Table [DSDT](id 0001) - 513 Objects with 62 Devices 170 Methods 25 Regions
Parsing all Control Methods:
Table [SSDT](id 0002) - 8 Objects with 0 Devices 0 Methods 0 Regions
tbxface-0598 [00] tb_load_namespace : ACPI Tables successfully acquired
evxfevnt-0091 [00] enable : Transition to ACPI mode successful
Using local APIC timer interrupts.
APIC timer calibration result 12557856
Detected 12.557 MHz APIC timer.
lockdep: not fixing up alternatives.
Booting processor 1/2 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 5625.95 BogoMIPS (lpj=11251909)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU 1/1 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
Dual-Core AMD Opteron(tm) Processor 1220 stepping 03
Brought up 2 CPUs
CPU0 attaching sched-domain:
domain 0: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002
domain 1: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000003
CPU1 attaching sched-domain:
domain 0: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000001
domain 1: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000003
net_namespace: 152 bytes
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG at e0000000 - e04fffff
PCI: No mmconfig possible on device 00:18
evgpeblk-0956 [00] ev_create_gpe_block : GPE 00 to 1F [_GPE] 4 regs on int 0x9
evgpeblk-1052 [00] ev_initialize_gpe_bloc: Found 2 Wake, Enabled 2 Runtime GPEs in this block
ACPI: EC: Look up EC in DSDT
Completing Region/Field/Buffer/Package initialization:................................................................
Initialized 20/25 Regions 2/2 Fields 26/26 Buffers 16/19 Packages (530 nodes)
Initializing Device/Processor/Thermal objects by executing _INI methods:
Executed 0 _INI methods requiring 0 _STA executions (examined 80 objects)
ACPI: Interpreter enabled
ACPI: (supports S0 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR3._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 16 17 18 19) *0
ACPI: PCI Interrupt Link [LNK2] (IRQs 16 17 18 19) *0
ACPI: PCI Interrupt Link [LNK3] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNK4] (IRQs 16 17 18 19) *0
ACPI: PCI Interrupt Link [LNK5] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [LUS0] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [LUS2] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LMAC] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LACI] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LMCI] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LPID] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LTID] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [LSI1] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [APCP] (IRQs 20 21 22 23) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 12 devices
ACPI: ACPI bus type pnp unregistered
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
DMAR:No DMAR devices found
PCI-DMA: Disabling AGP.
PCI-DMA: aperture base @ 4000000 size 65536 KB
PCI-DMA: using GART IOMMU.
PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 31
hpet0: 3 32-bit timers, 25000000 Hz
ACPI: RTC can wake from S4
Time: hpet clocksource has been installed.
Switched to high resolution mode on CPU 0
Switched to high resolution mode on CPU 1
system 00:00: iomem range 0xffc00000-0xffffffff could not be reserved
system 00:00: iomem range 0xfec00000-0xfec00fff could not be reserved
system 00:00: iomem range 0xfee00000-0xfeefffff could not be reserved
system 00:00: iomem range 0xfed00000-0xfed00fff has been reserved
system 00:02: iomem range 0xe0000000-0xefffffff could not be reserved
system 00:03: ioport range 0x8000-0x807f has been reserved
system 00:03: ioport range 0x8080-0x80ff has been reserved
system 00:03: ioport range 0x8400-0x847f has been reserved
system 00:03: ioport range 0x8480-0x84ff has been reserved
system 00:03: ioport range 0x8800-0x887f has been reserved
system 00:03: ioport range 0x8880-0x88ff has been reserved
system 00:03: ioport range 0x1440-0x147f has been reserved
system 00:03: ioport range 0x1400-0x143f has been reserved
system 00:05: ioport range 0x4d0-0x4d1 has been reserved
system 00:0a: ioport range 0xc00-0xc7f has been reserved
PCI: Bridge: 0000:00:09.0
IO window: 2000-2fff
MEM window: d0100000-d01fffff
PREFETCH window: d8000000-dfffffff
PCI: Bridge: 0000:00:0b.0
IO window: disabled.
MEM window: d0200000-d02fffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:0c.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Failed to allocate mem resource #6:100000@d0400000 for 0000:04:00.0
PCI: Bridge: 0000:00:0d.0
IO window: 3000-3fff
MEM window: d0300000-d03fffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:0e.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Setting latency timer of device 0000:00:09.0 to 64
PCI: Setting latency timer of device 0000:00:0b.0 to 64
PCI: Setting latency timer of device 0000:00:0c.0 to 64
PCI: Setting latency timer of device 0000:00:0d.0 to 64
PCI: Setting latency timer of device 0000:00:0e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 262144 (order: 9, 2097152 bytes)
TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
TCP bind hash table entries: 65536 (order: 10, 4194304 bytes)
TCP: Hash tables configured (established 524288 bind 65536)
TCP reno registered
Unpacking initramfs... done
Freeing initrd memory: 3019k freed
Simple Boot Flag at 0x62 set to 0x1
audit: initializing netlink socket (disabled)
audit(1197902862.548:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Found disabled HT MSI Mapping on 0000:00:0b.0
PCI: Found enabled HT MSI Mapping on 0000:00:00.0
PCI: Linking AER extended capability on 0000:00:0b.0
PCI: Found disabled HT MSI Mapping on 0000:00:0c.0
PCI: Found enabled HT MSI Mapping on 0000:00:00.0
PCI: Linking AER extended capability on 0000:00:0c.0
PCI: Found disabled HT MSI Mapping on 0000:00:0d.0
PCI: Found enabled HT MSI Mapping on 0000:00:00.0
PCI: Linking AER extended capability on 0000:00:0d.0
PCI: Found disabled HT MSI Mapping on 0000:00:0e.0
PCI: Found enabled HT MSI Mapping on 0000:00:00.0
PCI: Linking AER extended capability on 0000:00:0e.0
Boot video device is 0000:01:08.0
PCI: Setting latency timer of device 0000:00:0b.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0b.0:pcie00]
Allocate Port Service[0000:00:0b.0:pcie01]
Allocate Port Service[0000:00:0b.0:pcie03]
PCI: Setting latency timer of device 0000:00:0c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0c.0:pcie00]
Allocate Port Service[0000:00:0c.0:pcie01]
Allocate Port Service[0000:00:0c.0:pcie03]
PCI: Setting latency timer of device 0000:00:0d.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0d.0:pcie00]
Allocate Port Service[0000:00:0d.0:pcie01]
Allocate Port Service[0000:00:0d.0:pcie03]
PCI: Setting latency timer of device 0000:00:0e.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0e.0:pcie00]
Allocate Port Service[0000:00:0e.0:pcie01]
Allocate Port Service[0000:00:0e.0:pcie03]
AER service couldn't init device 0000:00:0b.0:pcie01 - no _OSC support
AER service couldn't init device 0000:00:0c.0:pcie01 - no _OSC support
AER service couldn't init device 0000:00:0d.0:pcie01 - no _OSC support
AER service couldn't init device 0000:00:0e.0:pcie01 - no _OSC support
vesafb: framebuffer at 0xd8000000, mapped to 0xffffc20002000000, using 5120k, total 32768k
vesafb: mode is 1280x1024x16, linelength=2560, pages=11
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 160x64
fb0: VESA VGA frame buffer device
Real Time Clock Driver v1.12ac
hpet_resources: 0xfed00000 is busy
Non-volatile memory driver v1.2
Linux agpgart interface v0.102
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 1.1.18
ixgbe: Copyright (c) 1999-2007 Intel Corporation.
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: PC Speaker as /devices/platform/pcspkr/input/input0
Driver for 1-wire Dallas network protocol.
1-Wire driver for the DS2760 battery monitor chip - (c) 2004-2005, Szabolcs Gyurko
cpuidle: using governor ladder
cpuidle: using governor menu
NET: Registered protocol family 1
registered taskstats version 1
Freeing unused kernel memory: 720k freed
SCSI subsystem initialized
Fusion MPT base driver 3.04.06
Copyright (c) 1999-2007 LSI Corporation
Fusion MPT SAS Host driver 3.04.06
ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 19
ACPI: PCI Interrupt 0000:04:00.0[A] -> Link [LNK4] -> GSI 19 (level, low) -> IRQ 19
mptbase: ioc0: Initiating bringup
ioc0: LSISAS1068E B2: Capabilities={Initiator}
PCI: Setting latency timer of device 0000:04:00.0 to 64
scsi0 : ioc0: LSISAS1068E B2, FwRev=00142d00h, Ports=1, MaxQ=511, IRQ=19
scsi 0:0:0:0: Direct-Access SEAGATE ST3300555SS T107 PQ: 0 ANSI: 5
scsi 0:0:1:0: Direct-Access SEAGATE ST3300555SS T107 PQ: 0 ANSI: 5
scsi 0:1:0:0: Direct-Access Dell VIRTUAL DISK 1028 PQ: 0 ANSI: 5
sd 0:1:0:0: [sda] 583983104 512-byte hardware sectors (298999 MB)
sd 0:1:0:0: [sda] Write Protect is off
sd 0:1:0:0: [sda] Mode Sense: 03 00 00 08
sd 0:1:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
scsi 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:1:0:0: [sda] 583983104 512-byte hardware sectors (298999 MB)
sd 0:1:0:0: [sda] Write Protect is off
sd 0:1:0:0: [sda] Mode Sense: 03 00 00 08
sd 0:1:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
scsi 0:0:1:0: Attached scsi generic sg1 type 0
sd 0:1:0:0: [sda] Attached SCSI disk
sd 0:1:0:0: Attached scsi generic sg2 type 0
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
BIOS EDD facility v0.16 2004-Jun-25, 6 devices found
ReiserFS: sda3: found reiserfs format "3.6" with standard journal
ReiserFS: sda3: using ordered data mode
ReiserFS: sda3: journal params: device sda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda3: checking transaction log (sda3)
ReiserFS: sda3: Using r5 hash to sort names
Adding 2104504k swap on /dev/disk/by-id/scsi-3600508e0000000003ad8e2c732a09d08-part2. Priority:-1 extents:1 across:2104504k
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
i2c-adapter i2c-0: nForce2 SMBus adapter at 0x1440
i2c-adapter i2c-1: nForce2 SMBus adapter at 0x1400
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUS2] -> GSI 23 (level, low) -> IRQ 23
PCI: Setting latency timer of device 0000:00:02.1 to 64
ehci_hcd 0000:00:02.1: EHCI Host Controller
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.1: debug port 1
PCI: cache line size of 64 is not supported by device 0000:00:02.1
Floppy drive(s): fd0 is 1.44M<6>ehci_hcd 0000:00:02.1: irq 23, io mem 0xd0001000
ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 10 ports detected

tg3.c:v3.86 (November 9, 2007)
ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 18
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNK2] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:02:00.0 to 64
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ffb00000-0x00000000ffffffff - kernel bug?
eth0: Tigon3 [partno(BCM95722) rev a200 PHY(5722/5756)] (PCI Express) 10/100/1000Base-T Ethernet 00:1d:09:02:ca:01
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUS0] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
rtc_cmos: probe of 00:08 failed with error -16
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:02.0: irq 22, io mem 0xd0000000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 10 ports detected
CFI: Found no ck804xrom @ffc00000 device at location zero
JEDEC: Found no ck804xrom @ffc00000 device at location zero
CFI: Found no ck804xrom @ffc00000 device at location zero
JEDEC: Found no ck804xrom @ffc00000 device at location zero
CFI: Found no ck804xrom @ffc00000 device at location zero
JEDEC: Found no ck804xrom @ffc00000 device at location zero
CFI: Found no ck804xrom @ffc10000 device at location zero
JEDEC: Found no ck804xrom @ffc10000 device at location zero
CFI: Found no ck804xrom @ffc10000 device at location zero
JEDEC: Found no ck804xrom @ffc10000 device at location zero
CFI: Found no ck804xrom @ffc10000 device at location zero
JEDEC: Found no ck804xrom @ffc10000 device at location zero
CFI: Found no ck804xrom @ffc20000 device at location zero
JEDEC: Found no ck804xrom @ffc20000 device at location zero
CFI: Found no ck804xrom @ffc20000 device at location zero
JEDEC: Found no ck804xrom @ffc20000 device at location zero
CFI: Found no ck804xrom @ffc20000 device at location zero
JEDEC: Found no ck804xrom @ffc20000 device at location zero
CFI: Found no ck804xrom @ffc30000 device at location zero
JEDEC: Found no ck804xrom @ffc30000 device at location zero
CFI: Found no ck804xrom @ffc30000 device at location zero
JEDEC: Found no ck804xrom @ffc30000 device at location zero
CFI: Found no ck804xrom @ffc30000 device at location zero
JEDEC: Found no ck804xrom @ffc30000 device at location zero
CFI: Found no ck804xrom @ffc40000 device at location zero
JEDEC: Found no ck804xrom @ffc40000 device at location zero
CFI: Found no ck804xrom @ffc40000 device at location zero
JEDEC: Found no ck804xrom @ffc40000 device at location zero
CFI: Found no ck804xrom @ffc40000 device at location zero
JEDEC: Found no ck804xrom @ffc40000 device at location zero
CFI: Found no ck804xrom @ffc50000 device at location zero
JEDEC: Found no ck804xrom @ffc50000 device at location zero
CFI: Found no ck804xrom @ffc50000 device at location zero
JEDEC: Found no ck804xrom @ffc50000 device at location zero
CFI: Found no ck804xrom @ffc50000 device at location zero
JEDEC: Found no ck804xrom @ffc50000 device at location zero
CFI: Found no ck804xrom @ffc60000 device at location zero
JEDEC: Found no ck804xrom @ffc60000 device at location zero
CFI: Found no ck804xrom @ffc60000 device at location zero
JEDEC: Found no ck804xrom @ffc60000 device at location zero
CFI: Found no ck804xrom @ffc60000 device at location zero
JEDEC: Found no ck804xrom @ffc60000 device at location zero
CFI: Found no ck804xrom @ffc70000 device at location zero
JEDEC: Found no ck804xrom @ffc70000 device at location zero
CFI: Found no ck804xrom @ffc70000 device at location zero
JEDEC: Found no ck804xrom @ffc70000 device at location zero
CFI: Found no ck804xrom @ffc70000 device at location zero
JEDEC: Found no ck804xrom @ffc70000 device at location zero
CFI: Found no ck804xrom @ffc80000 device at location zero
JEDEC: Found no ck804xrom @ffc80000 device at location zero
CFI: Found no ck804xrom @ffc80000 device at location zero
JEDEC: Found no ck804xrom @ffc80000 device at location zero
CFI: Found no ck804xrom @ffc80000 device at location zero
JEDEC: Found no ck804xrom @ffc80000 device at location zero
CFI: Found no ck804xrom @ffc90000 device at location zero
JEDEC: Found no ck804xrom @ffc90000 device at location zero
CFI: Found no ck804xrom @ffc90000 device at location zero
JEDEC: Found no ck804xrom @ffc90000 device at location zero
CFI: Found no ck804xrom @ffc90000 device at location zero
JEDEC: Found no ck804xrom @ffc90000 device at location zero
CFI: Found no ck804xrom @ffca0000 device at location zero
JEDEC: Found no ck804xrom @ffca0000 device at location zero
CFI: Found no ck804xrom @ffca0000 device at location zero
JEDEC: Found no ck804xrom @ffca0000 device at location zero
CFI: Found no ck804xrom @ffca0000 device at location zero
JEDEC: Found no ck804xrom @ffca0000 device at location zero
CFI: Found no ck804xrom @ffcb0000 device at location zero
JEDEC: Found no ck804xrom @ffcb0000 device at location zero
CFI: Found no ck804xrom @ffcb0000 device at location zero
JEDEC: Found no ck804xrom @ffcb0000 device at location zero
CFI: Found no ck804xrom @ffcb0000 device at location zero
JEDEC: Found no ck804xrom @ffcb0000 device at location zero
CFI: Found no ck804xrom @ffcc0000 device at location zero
JEDEC: Found no ck804xrom @ffcc0000 device at location zero
CFI: Found no ck804xrom @ffcc0000 device at location zero
JEDEC: Found no ck804xrom @ffcc0000 device at location zero
CFI: Found no ck804xrom @ffcc0000 device at location zero
JEDEC: Found no ck804xrom @ffcc0000 device at location zero
CFI: Found no ck804xrom @ffcd0000 device at location zero
JEDEC: Found no ck804xrom @ffcd0000 device at location zero
CFI: Found no ck804xrom @ffcd0000 device at location zero
JEDEC: Found no ck804xrom @ffcd0000 device at location zero
CFI: Found no ck804xrom @ffcd0000 device at location zero
JEDEC: Found no ck804xrom @ffcd0000 device at location zero
CFI: Found no ck804xrom @ffce0000 device at location zero
JEDEC: Found no ck804xrom @ffce0000 device at location zero
CFI: Found no ck804xrom @ffce0000 device at location zero
JEDEC: Found no ck804xrom @ffce0000 device at location zero
CFI: Found no ck804xrom @ffce0000 device at location zero
JEDEC: Found no ck804xrom @ffce0000 device at location zero
CFI: Found no ck804xrom @ffcf0000 device at location zero
JEDEC: Found no ck804xrom @ffcf0000 device at location zero
CFI: Found no ck804xrom @ffcf0000 device at location zero
JEDEC: Found no ck804xrom @ffcf0000 device at location zero
CFI: Found no ck804xrom @ffcf0000 device at location zero
JEDEC: Found no ck804xrom @ffcf0000 device at location zero
CFI: Found no ck804xrom @ffd00000 device at location zero
JEDEC: Found no ck804xrom @ffd00000 device at location zero
CFI: Found no ck804xrom @ffd00000 device at location zero
JEDEC: Found no ck804xrom @ffd00000 device at location zero
CFI: Found no ck804xrom @ffd00000 device at location zero
JEDEC: Found no ck804xrom @ffd00000 device at location zero
CFI: Found no ck804xrom @ffd10000 device at location zero
JEDEC: Found no ck804xrom @ffd10000 device at location zero
CFI: Found no ck804xrom @ffd10000 device at location zero
JEDEC: Found no ck804xrom @ffd10000 device at location zero
CFI: Found no ck804xrom @ffd10000 device at location zero
JEDEC: Found no ck804xrom @ffd10000 device at location zero
CFI: Found no ck804xrom @ffd20000 device at location zero
JEDEC: Found no ck804xrom @ffd20000 device at location zero
CFI: Found no ck804xrom @ffd20000 device at location zero
JEDEC: Found no ck804xrom @ffd20000 device at location zero
CFI: Found no ck804xrom @ffd20000 device at location zero
JEDEC: Found no ck804xrom @ffd20000 device at location zero
CFI: Found no ck804xrom @ffd30000 device at location zero
JEDEC: Found no ck804xrom @ffd30000 device at location zero
CFI: Found no ck804xrom @ffd30000 device at location zero
JEDEC: Found no ck804xrom @ffd30000 device at location zero
CFI: Found no ck804xrom @ffd30000 device at location zero
JEDEC: Found no ck804xrom @ffd30000 device at location zero
CFI: Found no ck804xrom @ffd40000 device at location zero
JEDEC: Found no ck804xrom @ffd40000 device at location zero
CFI: Found no ck804xrom @ffd40000 device at location zero
JEDEC: Found no ck804xrom @ffd40000 device at location zero
CFI: Found no ck804xrom @ffd40000 device at location zero
JEDEC: Found no ck804xrom @ffd40000 device at location zero
CFI: Found no ck804xrom @ffd50000 device at location zero
JEDEC: Found no ck804xrom @ffd50000 device at location zero
CFI: Found no ck804xrom @ffd50000 device at location zero
JEDEC: Found no ck804xrom @ffd50000 device at location zero
CFI: Found no ck804xrom @ffd50000 device at location zero
JEDEC: Found no ck804xrom @ffd50000 device at location zero
CFI: Found no ck804xrom @ffd60000 device at location zero
JEDEC: Found no ck804xrom @ffd60000 device at location zero
CFI: Found no ck804xrom @ffd60000 device at location zero
JEDEC: Found no ck804xrom @ffd60000 device at location zero
CFI: Found no ck804xrom @ffd60000 device at location zero
JEDEC: Found no ck804xrom @ffd60000 device at location zero
CFI: Found no ck804xrom @ffd70000 device at location zero
JEDEC: Found no ck804xrom @ffd70000 device at location zero
CFI: Found no ck804xrom @ffd70000 device at location zero
JEDEC: Found no ck804xrom @ffd70000 device at location zero
CFI: Found no ck804xrom @ffd70000 device at location zero
JEDEC: Found no ck804xrom @ffd70000 device at location zero
CFI: Found no ck804xrom @ffd80000 device at location zero
JEDEC: Found no ck804xrom @ffd80000 device at location zero
CFI: Found no ck804xrom @ffd80000 device at location zero
JEDEC: Found no ck804xrom @ffd80000 device at location zero
CFI: Found no ck804xrom @ffd80000 device at location zero
JEDEC: Found no ck804xrom @ffd80000 device at location zero
CFI: Found no ck804xrom @ffd90000 device at location zero
JEDEC: Found no ck804xrom @ffd90000 device at location zero
CFI: Found no ck804xrom @ffd90000 device at location zero
JEDEC: Found no ck804xrom @ffd90000 device at location zero
CFI: Found no ck804xrom @ffd90000 device at location zero
JEDEC: Found no ck804xrom @ffd90000 device at location zero
CFI: Found no ck804xrom @ffda0000 device at location zero
JEDEC: Found no ck804xrom @ffda0000 device at location zero
CFI: Found no ck804xrom @ffda0000 device at location zero
JEDEC: Found no ck804xrom @ffda0000 device at location zero
CFI: Found no ck804xrom @ffda0000 device at location zero
JEDEC: Found no ck804xrom @ffda0000 device at location zero
CFI: Found no ck804xrom @ffdb0000 device at location zero
JEDEC: Found no ck804xrom @ffdb0000 device at location zero
CFI: Found no ck804xrom @ffdb0000 device at location zero
JEDEC: Found no ck804xrom @ffdb0000 device at location zero
CFI: Found no ck804xrom @ffdb0000 device at location zero
JEDEC: Found no ck804xrom @ffdb0000 device at location zero
CFI: Found no ck804xrom @ffdc0000 device at location zero
JEDEC: Found no ck804xrom @ffdc0000 device at location zero
CFI: Found no ck804xrom @ffdc0000 device at location zero
JEDEC: Found no ck804xrom @ffdc0000 device at location zero
CFI: Found no ck804xrom @ffdc0000 device at location zero
JEDEC: Found no ck804xrom @ffdc0000 device at location zero
CFI: Found no ck804xrom @ffdd0000 device at location zero
JEDEC: Found no ck804xrom @ffdd0000 device at location zero
CFI: Found no ck804xrom @ffdd0000 device at location zero
JEDEC: Found no ck804xrom @ffdd0000 device at location zero
CFI: Found no ck804xrom @ffdd0000 device at location zero
JEDEC: Found no ck804xrom @ffdd0000 device at location zero
CFI: Found no ck804xrom @ffde0000 device at location zero
JEDEC: Found no ck804xrom @ffde0000 device at location zero
CFI: Found no ck804xrom @ffde0000 device at location zero
JEDEC: Found no ck804xrom @ffde0000 device at location zero
CFI: Found no ck804xrom @ffde0000 device at location zero
JEDEC: Found no ck804xrom @ffde0000 device at location zero
CFI: Found no ck804xrom @ffdf0000 device at location zero
JEDEC: Found no ck804xrom @ffdf0000 device at location zero
CFI: Found no ck804xrom @ffdf0000 device at location zero
JEDEC: Found no ck804xrom @ffdf0000 device at location zero
CFI: Found no ck804xrom @ffdf0000 device at location zero
JEDEC: Found no ck804xrom @ffdf0000 device at location zero
CFI: Found no ck804xrom @ffe00000 device at location zero
JEDEC: Found no ck804xrom @ffe00000 device at location zero
CFI: Found no ck804xrom @ffe00000 device at location zero
JEDEC: Found no ck804xrom @ffe00000 device at location zero
CFI: Found no ck804xrom @ffe00000 device at location zero
JEDEC: Found no ck804xrom @ffe00000 device at location zero
CFI: Found no ck804xrom @ffe10000 device at location zero
JEDEC: Found no ck804xrom @ffe10000 device at location zero
CFI: Found no ck804xrom @ffe10000 device at location zero
JEDEC: Found no ck804xrom @ffe10000 device at location zero
CFI: Found no ck804xrom @ffe10000 device at location zero
JEDEC: Found no ck804xrom @ffe10000 device at location zero
CFI: Found no ck804xrom @ffe20000 device at location zero
JEDEC: Found no ck804xrom @ffe20000 device at location zero
CFI: Found no ck804xrom @ffe20000 device at location zero
JEDEC: Found no ck804xrom @ffe20000 device at location zero
CFI: Found no ck804xrom @ffe20000 device at location zero
JEDEC: Found no ck804xrom @ffe20000 device at location zero
CFI: Found no ck804xrom @ffe30000 device at location zero
JEDEC: Found no ck804xrom @ffe30000 device at location zero
CFI: Found no ck804xrom @ffe30000 device at location zero
JEDEC: Found no ck804xrom @ffe30000 device at location zero
CFI: Found no ck804xrom @ffe30000 device at location zero
JEDEC: Found no ck804xrom @ffe30000 device at location zero
CFI: Found no ck804xrom @ffe40000 device at location zero
JEDEC: Found no ck804xrom @ffe40000 device at location zero
CFI: Found no ck804xrom @ffe40000 device at location zero
JEDEC: Found no ck804xrom @ffe40000 device at location zero
CFI: Found no ck804xrom @ffe40000 device at location zero
JEDEC: Found no ck804xrom @ffe40000 device at location zero
CFI: Found no ck804xrom @ffe50000 device at location zero
JEDEC: Found no ck804xrom @ffe50000 device at location zero
CFI: Found no ck804xrom @ffe50000 device at location zero
JEDEC: Found no ck804xrom @ffe50000 device at location zero
CFI: Found no ck804xrom @ffe50000 device at location zero
JEDEC: Found no ck804xrom @ffe50000 device at location zero
CFI: Found no ck804xrom @ffe60000 device at location zero
JEDEC: Found no ck804xrom @ffe60000 device at location zero
CFI: Found no ck804xrom @ffe60000 device at location zero
JEDEC: Found no ck804xrom @ffe60000 device at location zero
CFI: Found no ck804xrom @ffe60000 device at location zero
JEDEC: Found no ck804xrom @ffe60000 device at location zero
CFI: Found no ck804xrom @ffe70000 device at location zero
JEDEC: Found no ck804xrom @ffe70000 device at location zero
CFI: Found no ck804xrom @ffe70000 device at location zero
JEDEC: Found no ck804xrom @ffe70000 device at location zero
CFI: Found no ck804xrom @ffe70000 device at location zero
JEDEC: Found no ck804xrom @ffe70000 device at location zero
CFI: Found no ck804xrom @ffe80000 device at location zero
JEDEC: Found no ck804xrom @ffe80000 device at location zero
CFI: Found no ck804xrom @ffe80000 device at location zero
JEDEC: Found no ck804xrom @ffe80000 device at location zero
CFI: Found no ck804xrom @ffe80000 device at location zero
JEDEC: Found no ck804xrom @ffe80000 device at location zero
CFI: Found no ck804xrom @ffe90000 device at location zero
JEDEC: Found no ck804xrom @ffe90000 device at location zero
CFI: Found no ck804xrom @ffe90000 device at location zero
JEDEC: Found no ck804xrom @ffe90000 device at location zero
CFI: Found no ck804xrom @ffe90000 device at location zero
JEDEC: Found no ck804xrom @ffe90000 device at location zero
CFI: Found no ck804xrom @ffea0000 device at location zero
JEDEC: Found no ck804xrom @ffea0000 device at location zero
CFI: Found no ck804xrom @ffea0000 device at location zero
JEDEC: Found no ck804xrom @ffea0000 device at location zero
CFI: Found no ck804xrom @ffea0000 device at location zero
JEDEC: Found no ck804xrom @ffea0000 device at location zero
CFI: Found no ck804xrom @ffeb0000 device at location zero
JEDEC: Found no ck804xrom @ffeb0000 device at location zero
CFI: Found no ck804xrom @ffeb0000 device at location zero
JEDEC: Found no ck804xrom @ffeb0000 device at location zero
CFI: Found no ck804xrom @ffeb0000 device at location zero
JEDEC: Found no ck804xrom @ffeb0000 device at location zero
CFI: Found no ck804xrom @ffec0000 device at location zero
JEDEC: Found no ck804xrom @ffec0000 device at location zero
CFI: Found no ck804xrom @ffec0000 device at location zero
JEDEC: Found no ck804xrom @ffec0000 device at location zero
CFI: Found no ck804xrom @ffec0000 device at location zero
JEDEC: Found no ck804xrom @ffec0000 device at location zero
CFI: Found no ck804xrom @ffed0000 device at location zero
JEDEC: Found no ck804xrom @ffed0000 device at location zero
CFI: Found no ck804xrom @ffed0000 device at location zero
JEDEC: Found no ck804xrom @ffed0000 device at location zero
CFI: Found no ck804xrom @ffed0000 device at location zero
JEDEC: Found no ck804xrom @ffed0000 device at location zero
CFI: Found no ck804xrom @ffee0000 device at location zero
JEDEC: Found no ck804xrom @ffee0000 device at location zero
CFI: Found no ck804xrom @ffee0000 device at location zero
JEDEC: Found no ck804xrom @ffee0000 device at location zero
CFI: Found no ck804xrom @ffee0000 device at location zero
JEDEC: Found no ck804xrom @ffee0000 device at location zero
CFI: Found no ck804xrom @ffef0000 device at location zero
JEDEC: Found no ck804xrom @ffef0000 device at location zero
CFI: Found no ck804xrom @ffef0000 device at location zero
JEDEC: Found no ck804xrom @ffef0000 device at location zero
CFI: Found no ck804xrom @ffef0000 device at location zero
JEDEC: Found no ck804xrom @ffef0000 device at location zero
CFI: Found no ck804xrom @fff00000 device at location zero
JEDEC: Found no ck804xrom @fff00000 device at location zero
CFI: Found no ck804xrom @fff00000 device at location zero
JEDEC: Found no ck804xrom @fff00000 device at location zero
CFI: Found no ck804xrom @fff00000 device at location zero
Found: SST 49LF080A
ck804xrom @fff00000: Found 1 x8 devices at 0x0 in 8-bit bank
number of JEDEC chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
usb 2-6: new low speed USB device using ohci_hcd and address 2
usb 2-6: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
input: Avocent USB_AMIQ as /devices/pci0000:00/0000:00:02.0/usb2/2-6/2-6:1.0/input/input1
input,hidraw0: USB HID v1.10 Keyboard [Avocent USB_AMIQ] on usb-0000:00:02.0-6
input: Avocent USB_AMIQ as /devices/pci0000:00/0000:00:02.0/usb2/2-6/2-6:1.1/input/input2
input,hidraw1: USB HID v1.10 Mouse [Avocent USB_AMIQ] on usb-0000:00:02.0-6
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
floppy0: no floppy controllers found
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: [email protected]
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
loop: module loaded
ReiserFS: sda1: found reiserfs format "3.6" with standard journal
ReiserFS: sda1: using ordered data mode
ReiserFS: sda1: journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda1: checking transaction log (sda1)
ReiserFS: sda1: Using r5 hash to sort names
Floppy drive(s): fd0 is 1.44M
input: Power Button (FF) as /devices/virtual/input/input3
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /devices/virtual/input/input4
floppy0: no floppy controllers found
ACPI: Power Button (CM) [PWRB]
audit(1197883126.367:2): audit_pid=3174 old=0 by auid=4294967295
powernow-k8: Found 1 Dual-Core AMD Opteron(tm) Processor 1220 processors (2 cpu cores) (version 2.20.00)
powernow-k8: 0 : fid 0x14 (2800 MHz), vid 0x8
powernow-k8: 1 : fid 0x12 (2600 MHz), vid 0xa
powernow-k8: 2 : fid 0x10 (2400 MHz), vid 0xc
powernow-k8: 3 : fid 0xe (2200 MHz), vid 0xe
powernow-k8: 4 : fid 0xc (2000 MHz), vid 0x10
powernow-k8: 5 : fid 0xa (1800 MHz), vid 0x10
powernow-k8: 6 : fid 0x2 (1000 MHz), vid 0x12
Clocksource tsc unstable (delta = -70875418 ns)
libata: disagrees about version of symbol struct_module
libata version 3.00 loaded.
sata_nv 0000:00:07.0: version 3.5
ACPI: PCI Interrupt Link [LTID] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [LTID] -> GSI 21 (level, low) -> IRQ 21
sata_nv 0000:00:07.0: Using ADMA mode
PCI: Setting latency timer of device 0000:00:07.0 to 64
scsi1 : sata_nv
scsi2 : sata_nv
ata1: SATA max UDMA/133 cmd 0x14f0 ctl 0x14e0 bmdma 0x14b0 irq 21
ata2: SATA max UDMA/133 cmd 0x14d0 ctl 0x14c0 bmdma 0x14b8 irq 21
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATAPI: HL-DT-STDVD-ROM GDRH10N, 0D04, max UDMA/100
ata1.00: configured for UDMA/100
ata2: SATA link down (SStatus 0 SControl 300)
scsi 1:0:0:0: CD-ROM HL-DT-ST DVD-ROM GDRH10N 0D04 PQ: 0 ANSI: 5
ata1: bounce limit 0xFFFFFFFF, segment boundary 0xFFFF, hw segs 127
sr0: scsi3-mmc drive: 0x/0x caddy
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
sr 1:0:0:0: Attached scsi generic sg3 type 5
ACPI: PCI Interrupt Link [LSI1] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LSI1] -> GSI 20 (level, low) -> IRQ 20
sata_nv 0000:00:08.0: Using ADMA mode
PCI: Setting latency timer of device 0000:00:08.0 to 64
scsi3 : sata_nv
scsi4 : sata_nv
ata3: SATA max UDMA/133 cmd 0x1840 ctl 0x1830 bmdma 0x1800 irq 20
ata4: SATA max UDMA/133 cmd 0x1820 ctl 0x1810 bmdma 0x1808 irq 20
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
end_request: I/O error, dev sr0, sector 1235328
end_request: I/O error, dev sr0, sector 1235328
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sr0.
hfs: can't find a HFS filesystem on dev sr0.
MINIX-fs: blocksize too small for device
ReiserFS: sr0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on sr0
ISOFS: Unable to identify CD-ROM format.

--
This message was sent on behalf of [email protected] at openSubscriber.com
http://www.opensubscriber.com/message/[email protected]/8048235.html

2007-12-17 12:19:58

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

2007-12-17 16:17:21

[permalink] [raw]

Subject: Re: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

I found that the patch Robert has provided hasn't gone into 2.6.24-rc5 so maybe it is not working.

At the same time I did apply a small patch to 2.6.24-rc5 that seems to fix the issue.

I feel this could just be added to 2.6.24-rc5 without Robert's patch because of Jeff Garzik's" sata_nv: don't use legacy DMA in ADMA mode (v3)" patch.

It doesn't work without this patch because there is an allocation of memory from hpriv before the mask can be set.

Please review.

Signed-off-by: Shyam Iyer

--- sata_nv.c.orig 2007-12-17 21:08:12.000000000 +0530
+++ sata_nv.c 2007-12-17 21:08:25.000000000 +0530
@@ -2407,6 +2407,12 @@
type = GENERIC;
}

+ /* set 64bit dma masks, may fail */
+ if (type == ADMA) {
+ if (pci_set_dma_mask(pdev, DMA_64BIT_MASK) == 0)
+ pci_set_consistent_dma_mask(pdev, DMA_64BIT_MASK);
+ }
+
ppi[0] = &nv_port_info[type];
rc = ata_pci_prepare_sff_host(pdev, ppi, &host);
if (rc)
@@ -2418,12 +2424,6 @@
hpriv->type = type;
host->private_data = hpriv;

- /* set 64bit dma masks, may fail */
- if (type == ADMA) {
- if (pci_set_dma_mask(pdev, DMA_64BIT_MASK) == 0)
- pci_set_consistent_dma_mask(pdev, DMA_64BIT_MASK);
- }
-
/* request and iomap NV_MMIO_BAR */
rc = pcim_iomap_regions(pdev, 1 << NV_MMIO_BAR, DRV_NAME);
if (rc)

--
This message was sent on behalf of [email protected] at openSubscriber.com
http://www.opensubscriber.com/message/[email protected]/8211470.html

2007-12-18 02:51:18

by Tejun Heo

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Hello,

[email protected] wrote:
> --- sata_nv.c.orig 2007-12-17 21:08:12.000000000 +0530
> +++ sata_nv.c 2007-12-17 21:08:25.000000000 +0530
> @@ -2407,6 +2407,12 @@
> type = GENERIC;
> }
>
> + /* set 64bit dma masks, may fail */
> + if (type == ADMA) {
> + if (pci_set_dma_mask(pdev, DMA_64BIT_MASK) == 0)
> + pci_set_consistent_dma_mask(pdev, DMA_64BIT_MASK);
> + }
> +
> ppi[0] = &nv_port_info[type];
> rc = ata_pci_prepare_sff_host(pdev, ppi, &host);
> if (rc)
> @@ -2418,12 +2424,6 @@
> hpriv->type = type;
> host->private_data = hpriv;
>
> - /* set 64bit dma masks, may fail */
> - if (type == ADMA) {
> - if (pci_set_dma_mask(pdev, DMA_64BIT_MASK) == 0)
> - pci_set_consistent_dma_mask(pdev, DMA_64BIT_MASK);
> - }
> -

This is weird. IIRC, the problem is caused by allocating consistent
memory for legacy DMA over 32bit limit. Your patch moves setting 64bit
DMA mask upward but it doesn't affect anything because
ata_pci_prepare_sff_host() and hpriv allocation are not DMA memory
allocations and thus unaffected by DMA mask.

Robert's last patch seems correct to me. I have no idea why it doesn't
work for you tho. Another interesting point is that you are reporting
data corruption instead of time out or HSM violation, which indicates
that the PRD table is accessible but what it contains is incorrect.

I guess it's time to print out some memory addresses. I'll prep a debug
patch soon.

Thanks.

--
tejun

2007-12-18 03:52:42

by Tejun Heo

[permalink] [raw]

Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 4753a18..acaa8b8 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -4537,6 +4537,10 @@ static void ata_fill_sg(struct ata_queued_cmd *qc)
* Note h/w doesn't support 64-bit, so we unconditionally
* truncate dma_addr_t to u32.
*/
+ if (sg_dma_address(sg) & ~DMA_BIT_MASK(32))
+ ata_dev_printk(qc->dev, KERN_WARNING,
+ "XXX DMA address %llx is above 32bit\n",
+ sg_dma_address(sg));
addr = (u32) sg_dma_address(sg);
sg_len = sg_dma_len(sg);

@@ -6628,6 +6632,10 @@ int ata_port_start(struct ata_port *ap)
if (rc)
return rc;

+ ata_port_printk(ap, KERN_INFO, "XXX: prd %p/%llx pad %p/%llx\n",
+ ap->prd, (unsigned long long)ap->prd_dma,
+ ap->pad, (unsigned long long)ap->pad_dma);
+
DPRINTK("prd alloc, virt %p, dma %llx\n", ap->prd,
(unsigned long long)ap->prd_dma);
return 0;
diff --git a/drivers/ata/sata_nv.c b/drivers/ata/sata_nv.c
index ed5dc7c..c55d2ae 100644
--- a/drivers/ata/sata_nv.c
+++ b/drivers/ata/sata_nv.c
@@ -247,6 +247,7 @@ struct nv_adma_port_priv {
void __iomem *ctl_block;
void __iomem *gen_block;
void __iomem *notifier_clear_block;
+ u64 adma_dma_mask;
u8 flags;
int last_issue_ncq;
};
@@ -748,7 +749,7 @@ static int nv_adma_slave_config(struct scsi_device *sdev)
adma_enable = 0;
nv_adma_register_mode(ap);
} else {
- bounce_limit = *ap->dev->dma_mask;
+ bounce_limit = pp->adma_dma_mask;
segment_boundary = NV_ADMA_DMA_BOUNDARY;
sg_tablesize = NV_ADMA_SGTBL_TOTAL_LEN;
adma_enable = 1;
@@ -1134,10 +1135,20 @@ static int nv_adma_port_start(struct ata_port *ap)
void *mem;
dma_addr_t mem_dma;
void __iomem *mmio;
+ struct pci_dev *pdev = to_pci_dev(dev);
u16 tmp;

VPRINTK("ENTER\n");

+ /* Ensure DMA mask is set to 32-bit before allocating legacy PRD and
+ pad buffers */
+ rc = pci_set_dma_mask(pdev, DMA_BIT_MASK(32));
+ if (rc)
+ return rc;
+ rc = pci_set_consistent_dma_mask(pdev, DMA_BIT_MASK(32));
+ if (rc)
+ return rc;
+
rc = ata_port_start(ap);
if (rc)
return rc;
@@ -1153,6 +1164,15 @@ static int nv_adma_port_start(struct ata_port *ap)
pp->notifier_clear_block = pp->gen_block +
NV_ADMA_NOTIFIER_CLEAR + (4 * ap->port_no);

+ /* Now that the legacy PRD and padding buffer are allocated we can
+ safely raise the DMA mask to allocate the CPB/APRD table.
+ These are allowed to fail since we store the value that ends up
+ being used to set as the bounce limit in slave_config later if
+ needed. */
+ pci_set_dma_mask(pdev, DMA_BIT_MASK(64));
+ pci_set_consistent_dma_mask(pdev, DMA_BIT_MASK(64));
+ pp->adma_dma_mask = *dev->dma_mask;
+
mem = dmam_alloc_coherent(dev, NV_ADMA_PORT_PRIV_DMA_SZ,
&mem_dma, GFP_KERNEL);
if (!mem)
@@ -2418,12 +2438,6 @@ static int nv_init_one(struct pci_dev *pdev, const struct pci_device_id *ent)
hpriv->type = type;
host->private_data = hpriv;

- /* set 64bit dma masks, may fail */
- if (type == ADMA) {
- if (pci_set_dma_mask(pdev, DMA_64BIT_MASK) == 0)
- pci_set_consistent_dma_mask(pdev, DMA_64BIT_MASK);
- }
-
/* request and iomap NV_MMIO_BAR */
rc = pcim_iomap_regions(pdev, 1 << NV_MMIO_BAR, DRV_NAME);
if (rc)
diff --git a/include/linux/libata.h b/include/linux/libata.h

Attachments:

patch (3.24 kB)

2007-12-18 10:32:08

[permalink] [raw]

Subject: RE: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

The dmesg snippet with the patched kernel. This does not contain my
patch.

Linux version 2.6.24-rc5-default (root@Pandora) (gcc version 4.1.2
20070115 (prerelease) (SUSE Linux)) #2 SMP Thu Dec 13 15:38:25 IST 2007
Command line:
root=/dev/disk/by-id/scsi-3600508e0000000003ad8e2c732a09d08-part3
vga=0x31a resume=/dev/sda2 splash=verbose showopts 1
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009cc00 (usable)
BIOS-e820: 000000000009cc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000cc000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007fff0000 (usable)
BIOS-e820: 000000007fff0000 - 0000000080000000 (reserved)
BIOS-e820: 0000000080000000 - 00000000cff00000 (usable)
BIOS-e820: 00000000cff00000 - 00000000cff0a000 (ACPI data)
BIOS-e820: 00000000cff0a000 - 00000000cff80000 (ACPI NVS)
BIOS-e820: 00000000cff80000 - 00000000d0000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000230000000 (usable)
Entering add_active_range(0, 0, 156) 0 entries of 3200 used
Entering add_active_range(0, 256, 524272) 1 entries of 3200 used
Entering add_active_range(0, 524288, 851712) 2 entries of 3200 used
Entering add_active_range(0, 1048576, 2293760) 3 entries of 3200 used
end_pfn_map = 2293760
DMI present.
ACPI: RSDP 000F7AE0, 0014 (r0 PTLTD )
ACPI: RSDT CFF064D5, 004C (r1 DELL PE_SC3 6040000 DELL 0)
ACPI: FACP CFF09906, 0074 (r1 DELL PE_SC3 6040000 DELL F4240)
ACPI: DSDT CFF06521, 33E5 (r1 DELL PE_SC3 6040000 MSFT 100000E)
ACPI: FACS CFF0AFC0, 0040
ACPI: TCPA CFF0997A, 0032 (r1 Phoeni x 6040000 TL 0)
ACPI: SLIC CFF099AC, 0176 (r1 DELL PE_SC3 6040000 PTL 1)
ACPI: SPCR CFF09B22, 0050 (r1 DELL PE_SC3 6040000 PTL 1)
ACPI: SRAT CFF09B72, 00C8 (r1 AMD HAMMER 6040000 AMD 1)
ACPI: SSDT CFF09C3A, 02CC (r1 AMD POWERNOW 6040000 AMD 1)
ACPI: MCFG CFF09F06, 003C (r1 PTLTD MCFG 6040000 LTP 0)
ACPI: HPET CFF09F42, 0038 (r1 PTLTD HPETTBL 6040000 LTP 1)
ACPI: APIC CFF09F7A, 005E (r1 PTLTD APIC 6040000 LTP 0)
ACPI: BOOT CFF09FD8, 0028 (r1 PTLTD $SBFTBL$ 6040000 LTP 1)
SRAT: PXM 0 -> APIC 0 -> Node 0
SRAT: PXM 0 -> APIC 1 -> Node 0
SRAT: Node 0 PXM 0 0-a0000
Entering add_active_range(0, 0, 156) 0 entries of 3200 used
SRAT: Node 0 PXM 0 0-d0000000
Entering add_active_range(0, 0, 156) 1 entries of 3200 used
Entering add_active_range(0, 256, 524272) 1 entries of 3200 used
Entering add_active_range(0, 524288, 851712) 2 entries of 3200 used
SRAT: Node 0 PXM 0 0-230000000
Entering add_active_range(0, 0, 156) 3 entries of 3200 used
Entering add_active_range(0, 256, 524272) 3 entries of 3200 used
Entering add_active_range(0, 524288, 851712) 3 entries of 3200 used
Entering add_active_range(0, 1048576, 2293760) 3 entries of 3200 used
NUMA: Using 63 for the hash shift.
Bootmem setup node 0 0000000000000000-0000000230000000
Zone PFN ranges:
DMA 0 -> 4096
DMA32 4096 -> 1048576
Normal 1048576 -> 2293760
Movable zone start PFN for each node
early_node_map[4] active PFN ranges
0: 0 -> 156
0: 256 -> 524272
0: 524288 -> 851712
0: 1048576 -> 2293760
On node 0 totalpages: 2096780
DMA zone: 96 pages used for memmap
DMA zone: 2540 pages reserved
DMA zone: 1360 pages, LIFO batch:0
DMA32 zone: 24480 pages used for memmap
DMA32 zone: 823120 pages, LIFO batch:31
Normal zone: 29184 pages used for memmap
Normal zone: 1216000 pages, LIFO batch:31
Movable zone: 0 pages used for memmap
ACPI: PM-Timer IO Port: 0x8008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
ACPI: HPET id: 0x10de8201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
swsusp: Registered nosave memory region: 000000000009c000 -
000000000009d000
swsusp: Registered nosave memory region: 000000000009d000 -
00000000000a0000
swsusp: Registered nosave memory region: 00000000000a0000 -
00000000000cc000
swsusp: Registered nosave memory region: 00000000000cc000 -
0000000000100000
swsusp: Registered nosave memory region: 000000007fff0000 -
0000000080000000
swsusp: Registered nosave memory region: 00000000cff00000 -
00000000cff0a000
swsusp: Registered nosave memory region: 00000000cff0a000 -
00000000cff80000
swsusp: Registered nosave memory region: 00000000cff80000 -
00000000d0000000
swsusp: Registered nosave memory region: 00000000d0000000 -
00000000e0000000
swsusp: Registered nosave memory region: 00000000e0000000 -
00000000f0000000
swsusp: Registered nosave memory region: 00000000f0000000 -
00000000fec00000
swsusp: Registered nosave memory region: 00000000fec00000 -
00000000fec10000
swsusp: Registered nosave memory region: 00000000fec10000 -
00000000fee00000
swsusp: Registered nosave memory region: 00000000fee00000 -
00000000fee01000
swsusp: Registered nosave memory region: 00000000fee01000 -
00000000fff80000
swsusp: Registered nosave memory region: 00000000fff80000 -
0000000100000000
Allocating PCI resources starting at d1000000 (gap: d0000000:10000000)
SMP: Allowing 2 CPUs, 0 hotplug CPUs
PERCPU: Allocating 441112 bytes of per cpu data
Built 1 zonelists in Zone order, mobility grouping on. Total pages:
2040480
Policy zone: Normal
Kernel command line:
root=/dev/disk/by-id/scsi-3600508e0000000003ad8e2c732a09d08-part3
vga=0x31a resume=/dev/sda2 splash=verbose showopts 1
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
hpet clockevent registered
TSC calibrated against HPET
Marking TSC unstable due to TSCs unsynchronized
time.c: Detected 2812.958 MHz processor.
Console: colour dummy device 80x25
console [tty0] enabled
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES: 8
... MAX_LOCK_DEPTH: 30
... MAX_LOCKDEP_KEYS: 2048
... CLASSHASH_SIZE: 1024
... MAX_LOCKDEP_ENTRIES: 8192
... MAX_LOCKDEP_CHAINS: 16384
... CHAINHASH_SIZE: 8192
memory used by lock dependency info: 1712 kB
per task-struct memory footprint: 2160 bytes
Checking aperture...
CPU 0: aperture @ c776000000 size 32 MB
Aperture too small (32 MB)
No AGP bridge found
Your BIOS doesn't leave a aperture memory hole
Please enable the IOMMU option in the BIOS setup
This costs you 64 MB of RAM
Mapping aperture over 65536 KB of RAM @ 4000000
Memory: 8091848k/9175040k available (2232k kernel code, 295272k
reserved, 1390k data, 720k init)
Calibrating delay using timer specific routine.. 5629.63 BogoMIPS
(lpj=11259264)
Security Framework initialized
Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU 0/0 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
lockdep: not fixing up alternatives.
ACPI: Core revision 20070126
Parsing all Control Methods:
Table [DSDT](id 0001) - 513 Objects with 62 Devices 170 Methods 25
Regions
Parsing all Control Methods:
Table [SSDT](id 0002) - 8 Objects with 0 Devices 0 Methods 0 Regions
tbxface-0598 [00] tb_load_namespace : ACPI Tables successfully
acquired
evxfevnt-0091 [00] enable : Transition to ACPI mode
successful
Using local APIC timer interrupts.
APIC timer calibration result 12557858
Detected 12.557 MHz APIC timer.
lockdep: not fixing up alternatives.
Booting processor 1/2 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 5625.95 BogoMIPS
(lpj=11251910)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU 1/1 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
Dual-Core AMD Opteron(tm) Processor 1220 stepping 03
Brought up 2 CPUs
CPU0 attaching sched-domain:
domain 0: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000001
00000000,00000000,00000000,00000002
domain 1: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000003
CPU1 attaching sched-domain:
domain 0: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000002
00000000,00000000,00000000,00000001
domain 1: span 00000000,00000000,00000000,00000003
groups: 00000000,00000000,00000000,00000003
net_namespace: 152 bytes
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG at e0000000 - e04fffff
PCI: No mmconfig possible on device 00:18
evgpeblk-0956 [00] ev_create_gpe_block : GPE 00 to 1F [_GPE] 4 regs on
int 0x9
evgpeblk-1052 [00] ev_initialize_gpe_bloc: Found 2 Wake, Enabled 2
Runtime GPEs in this block
ACPI: EC: Look up EC in DSDT
Completing Region/Field/Buffer/Package
initialization:.........................................................
.......
Initialized 20/25 Regions 2/2 Fields 26/26 Buffers 16/19 Packages (530
nodes)
Initializing Device/Processor/Thermal objects by executing _INI methods:
Executed 0 _INI methods requiring 0 _STA executions (examined 80
objects)
ACPI: Interpreter enabled
ACPI: (supports S0 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR3._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 16 17 18 19) *0
ACPI: PCI Interrupt Link [LNK2] (IRQs 16 17 18 19) *0
ACPI: PCI Interrupt Link [LNK3] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LNK4] (IRQs 16 17 18 19) *0
ACPI: PCI Interrupt Link [LNK5] (IRQs 16 17 18 19) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [LUS0] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [LUS2] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LMAC] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LACI] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LMCI] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LPID] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LTID] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [LSI1] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [APCP] (IRQs 20 21 22 23) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 12 devices
ACPI: ACPI bus type pnp unregistered
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
report
DMAR:No DMAR devices found
PCI-DMA: Disabling AGP.
PCI-DMA: aperture base @ 4000000 size 65536 KB
PCI-DMA: using GART IOMMU.
PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 31
hpet0: 3 32-bit timers, 25000000 Hz
ACPI: RTC can wake from S4
Time: hpet clocksource has been installed.
Switched to high resolution mode on CPU 0
Switched to high resolution mode on CPU 1
system 00:00: iomem range 0xffc00000-0xffffffff could not be reserved
system 00:00: iomem range 0xfec00000-0xfec00fff could not be reserved
system 00:00: iomem range 0xfee00000-0xfeefffff could not be reserved
system 00:00: iomem range 0xfed00000-0xfed00fff has been reserved
system 00:02: iomem range 0xe0000000-0xefffffff could not be reserved
system 00:03: ioport range 0x8000-0x807f has been reserved
system 00:03: ioport range 0x8080-0x80ff has been reserved
system 00:03: ioport range 0x8400-0x847f has been reserved
system 00:03: ioport range 0x8480-0x84ff has been reserved
system 00:03: ioport range 0x8800-0x887f has been reserved
system 00:03: ioport range 0x8880-0x88ff has been reserved
system 00:03: ioport range 0x1440-0x147f has been reserved
system 00:03: ioport range 0x1400-0x143f has been reserved
system 00:05: ioport range 0x4d0-0x4d1 has been reserved
system 00:0a: ioport range 0xc00-0xc7f has been reserved
PCI: Bridge: 0000:00:09.0
IO window: 2000-2fff
MEM window: d0100000-d01fffff
PREFETCH window: d8000000-dfffffff
PCI: Bridge: 0000:00:0b.0
IO window: disabled.
MEM window: d0200000-d02fffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:0c.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Failed to allocate mem resource #6:100000@d0400000 for 0000:04:00.0
PCI: Bridge: 0000:00:0d.0
IO window: 3000-3fff
MEM window: d0300000-d03fffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:0e.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Setting latency timer of device 0000:00:09.0 to 64
PCI: Setting latency timer of device 0000:00:0b.0 to 64
PCI: Setting latency timer of device 0000:00:0c.0 to 64
PCI: Setting latency timer of device 0000:00:0d.0 to 64
PCI: Setting latency timer of device 0000:00:0e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 262144 (order: 9, 2097152 bytes)
TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
TCP bind hash table entries: 65536 (order: 10, 4194304 bytes)
TCP: Hash tables configured (established 524288 bind 65536)
TCP reno registered
Unpacking initramfs... done
Freeing initrd memory: 3019k freed
Simple Boot Flag at 0x62 set to 0x1
audit: initializing netlink socket (disabled)
audit(1197990334.536:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Found disabled HT MSI Mapping on 0000:00:0b.0
PCI: Found enabled HT MSI Mapping on 0000:00:00.0
PCI: Found disabled HT MSI Mapping on 0000:00:0c.0
PCI: Found enabled HT MSI Mapping on 0000:00:00.0
PCI: Found disabled HT MSI Mapping on 0000:00:0d.0
PCI: Found enabled HT MSI Mapping on 0000:00:00.0
PCI: Found disabled HT MSI Mapping on 0000:00:0e.0
PCI: Found enabled HT MSI Mapping on 0000:00:00.0
Boot video device is 0000:01:08.0
PCI: Setting latency timer of device 0000:00:0b.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0b.0:pcie00]
Allocate Port Service[0000:00:0b.0:pcie01]
Allocate Port Service[0000:00:0b.0:pcie03]
PCI: Setting latency timer of device 0000:00:0c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0c.0:pcie00]
Allocate Port Service[0000:00:0c.0:pcie01]
Allocate Port Service[0000:00:0c.0:pcie03]
PCI: Setting latency timer of device 0000:00:0d.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0d.0:pcie00]
Allocate Port Service[0000:00:0d.0:pcie01]
Allocate Port Service[0000:00:0d.0:pcie03]
PCI: Setting latency timer of device 0000:00:0e.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0e.0:pcie00]
Allocate Port Service[0000:00:0e.0:pcie01]
Allocate Port Service[0000:00:0e.0:pcie03]
AER service couldn't init device 0000:00:0b.0:pcie01 - no _OSC support
AER service couldn't init device 0000:00:0c.0:pcie01 - no _OSC support
AER service couldn't init device 0000:00:0d.0:pcie01 - no _OSC support
AER service couldn't init device 0000:00:0e.0:pcie01 - no _OSC support
vesafb: framebuffer at 0xd8000000, mapped to 0xffffc20002000000, using
5120k, total 32768k
vesafb: mode is 1280x1024x16, linelength=2560, pages=11
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 160x64
fb0: VESA VGA frame buffer device
Real Time Clock Driver v1.12ac
hpet_resources: 0xfed00000 is busy
Non-volatile memory driver v1.2
Linux agpgart interface v0.102
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 1.1.18
ixgbe: Copyright (c) 1999-2007 Intel Corporation.
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: PC Speaker as /devices/platform/pcspkr/input/input0
Driver for 1-wire Dallas network protocol.
1-Wire driver for the DS2760 battery monitor chip - (c) 2004-2005,
Szabolcs Gyurko
cpuidle: using governor ladder
cpuidle: using governor menu
NET: Registered protocol family 1
registered taskstats version 1
Freeing unused kernel memory: 720k freed
SCSI subsystem initialized
Fusion MPT base driver 3.04.06
Copyright (c) 1999-2007 LSI Corporation
Fusion MPT SAS Host driver 3.04.06
ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 19
ACPI: PCI Interrupt 0000:04:00.0[A] -> Link [LNK4] -> GSI 19 (level,
low) -> IRQ 19
mptbase: ioc0: Initiating bringup
ioc0: LSISAS1068E B2: Capabilities={Initiator}
PCI: Setting latency timer of device 0000:04:00.0 to 64
scsi0 : ioc0: LSISAS1068E B2, FwRev=00142d00h, Ports=1, MaxQ=511, IRQ=19
scsi 0:0:0:0: Direct-Access SEAGATE ST3300555SS T107 PQ: 0
ANSI: 5
scsi 0:0:1:0: Direct-Access SEAGATE ST3300555SS T107 PQ: 0
ANSI: 5
scsi 0:1:0:0: Direct-Access Dell VIRTUAL DISK 1028 PQ: 0
ANSI: 5
scsi 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:1:0:0: [sda] 583983104 512-byte hardware sectors (298999 MB)
sd 0:1:0:0: [sda] Write Protect is off
sd 0:1:0:0: [sda] Mode Sense: 03 00 00 08
sd 0:1:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't
support DPO or FUA
sd 0:1:0:0: [sda] 583983104 512-byte hardware sectors (298999 MB)
sd 0:1:0:0: [sda] Write Protect is off
sd 0:1:0:0: [sda] Mode Sense: 03 00 00 08
sd 0:1:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't
support DPO or FUA
sda: sda1 sda2 sda3
scsi 0:0:1:0: Attached scsi generic sg1 type 0
sd 0:1:0:0: [sda] Attached SCSI disk
sd 0:1:0:0: Attached scsi generic sg2 type 0
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is
not present [20070126]
BIOS EDD facility v0.16 2004-Jun-25, 6 devices found
ReiserFS: sda3: found reiserfs format "3.6" with standard journal
ReiserFS: sda3: using ordered data mode
ReiserFS: sda3: journal params: device sda3, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: sda3: checking transaction log (sda3)
ReiserFS: sda3: Using r5 hash to sort names
ReiserFS: sda3: Removing [1280 96069 0x0 SD]..done
ReiserFS: sda3: There were 1 uncompleted unlinks/truncates. Completed
Adding 2104504k swap on
/dev/disk/by-id/scsi-3600508e0000000003ad8e2c732a09d08-part2.
Priority:-1 extents:1 across:2104504k
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
usbcore: registered new device driver usb
tg3.c:v3.86 (November 9, 2007)
ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 18
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNK2] -> GSI 18 (level,
low) -> IRQ 18
PCI: Setting latency timer of device 0000:02:00.0 to 64
i2c-adapter i2c-0: nForce2 SMBus adapter at 0x1440
i2c-adapter i2c-1: nForce2 SMBus adapter at 0x1400
Floppy drive(s): fd0 is 1.44M
rtc_cmos: probe of 00:08 failed with error -16
eth0: Tigon3 [partno(BCM95722) rev a200 PHY(5722/5756)] (PCI Express)
10/100/1000Base-T Ethernet 00:1d:09:02:ca:01
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]
ck804xrom ck804xrom_init_one(): Unable to register resource
0x00000000ffb00000-0x00000000ffffffff - kernel bug?
ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUS2] -> GSI 23 (level,
low) -> IRQ 23
PCI: Setting latency timer of device 0000:00:02.1 to 64
ehci_hcd 0000:00:02.1: EHCI Host Controller
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.1: debug port 1
PCI: cache line size of 64 is not supported by device 0000:00:02.1
ehci_hcd 0000:00:02.1: irq 23, io mem 0xd0001000
CFI: Found no ck804xrom @ffc00000 device at location zero
ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 10 ports detected
JEDEC: Found no ck804xrom @ffc00000 device at location zero
CFI: Found no ck804xrom @ffc00000 device at location zero
JEDEC: Found no ck804xrom @ffc00000 device at location zero
CFI: Found no ck804xrom @ffc00000 device at location zero
JEDEC: Found no ck804xrom @ffc00000 device at location zero
CFI: Found no ck804xrom @ffc10000 device at location zero
JEDEC: Found no ck804xrom @ffc10000 device at location zero
CFI: Found no ck804xrom @ffc10000 device at location zero
JEDEC: Found no ck804xrom @ffc10000 device at location zero
CFI: Found no ck804xrom @ffc10000 device at location zero
JEDEC: Found no ck804xrom @ffc10000 device at location zero
CFI: Found no ck804xrom @ffc20000 device at location zero
JEDEC: Found no ck804xrom @ffc20000 device at location zero
CFI: Found no ck804xrom @ffc20000 device at location zero
JEDEC: Found no ck804xrom @ffc20000 device at location zero
CFI: Found no ck804xrom @ffc20000 device at location zero
JEDEC: Found no ck804xrom @ffc20000 device at location zero
CFI: Found no ck804xrom @ffc30000 device at location zero
JEDEC: Found no ck804xrom @ffc30000 device at location zero
CFI: Found no ck804xrom @ffc30000 device at location zero
JEDEC: Found no ck804xrom @ffc30000 device at location zero
CFI: Found no ck804xrom @ffc30000 device at location zero
JEDEC: Found no ck804xrom @ffc30000 device at location zero
CFI: Found no ck804xrom @ffc40000 device at location zero
JEDEC: Found no ck804xrom @ffc40000 device at location zero
CFI: Found no ck804xrom @ffc40000 device at location zero
JEDEC: Found no ck804xrom @ffc40000 device at location zero
CFI: Found no ck804xrom @ffc40000 device at location zero
JEDEC: Found no ck804xrom @ffc40000 device at location zero
CFI: Found no ck804xrom @ffc50000 device at location zero
JEDEC: Found no ck804xrom @ffc50000 device at location zero
CFI: Found no ck804xrom @ffc50000 device at location zero
JEDEC: Found no ck804xrom @ffc50000 device at location zero
CFI: Found no ck804xrom @ffc50000 device at location zero
JEDEC: Found no ck804xrom @ffc50000 device at location zero
CFI: Found no ck804xrom @ffc60000 device at location zero
JEDEC: Found no ck804xrom @ffc60000 device at location zero
CFI: Found no ck804xrom @ffc60000 device at location zero
JEDEC: Found no ck804xrom @ffc60000 device at location zero
CFI: Found no ck804xrom @ffc60000 device at location zero
JEDEC: Found no ck804xrom @ffc60000 device at location zero
CFI: Found no ck804xrom @ffc70000 device at location zero
JEDEC: Found no ck804xrom @ffc70000 device at location zero
CFI: Found no ck804xrom @ffc70000 device at location zero
JEDEC: Found no ck804xrom @ffc70000 device at location zero
CFI: Found no ck804xrom @ffc70000 device at location zero
JEDEC: Found no ck804xrom @ffc70000 device at location zero
CFI: Found no ck804xrom @ffc80000 device at location zero
JEDEC: Found no ck804xrom @ffc80000 device at location zero
CFI: Found no ck804xrom @ffc80000 device at location zero
JEDEC: Found no ck804xrom @ffc80000 device at location zero
CFI: Found no ck804xrom @ffc80000 device at location zero
JEDEC: Found no ck804xrom @ffc80000 device at location zero
CFI: Found no ck804xrom @ffc90000 device at location zero
JEDEC: Found no ck804xrom @ffc90000 device at location zero
CFI: Found no ck804xrom @ffc90000 device at location zero
JEDEC: Found no ck804xrom @ffc90000 device at location zero
CFI: Found no ck804xrom @ffc90000 device at location zero
JEDEC: Found no ck804xrom @ffc90000 device at location zero
CFI: Found no ck804xrom @ffca0000 device at location zero
JEDEC: Found no ck804xrom @ffca0000 device at location zero
CFI: Found no ck804xrom @ffca0000 device at location zero
JEDEC: Found no ck804xrom @ffca0000 device at location zero
CFI: Found no ck804xrom @ffca0000 device at location zero
JEDEC: Found no ck804xrom @ffca0000 device at location zero
CFI: Found no ck804xrom @ffcb0000 device at location zero
JEDEC: Found no ck804xrom @ffcb0000 device at location zero
CFI: Found no ck804xrom @ffcb0000 device at location zero
JEDEC: Found no ck804xrom @ffcb0000 device at location zero
CFI: Found no ck804xrom @ffcb0000 device at location zero
JEDEC: Found no ck804xrom @ffcb0000 device at location zero
CFI: Found no ck804xrom @ffcc0000 device at location zero
JEDEC: Found no ck804xrom @ffcc0000 device at location zero
CFI: Found no ck804xrom @ffcc0000 device at location zero
JEDEC: Found no ck804xrom @ffcc0000 device at location zero
CFI: Found no ck804xrom @ffcc0000 device at location zero
JEDEC: Found no ck804xrom @ffcc0000 device at location zero
CFI: Found no ck804xrom @ffcd0000 device at location zero
JEDEC: Found no ck804xrom @ffcd0000 device at location zero
CFI: Found no ck804xrom @ffcd0000 device at location zero
JEDEC: Found no ck804xrom @ffcd0000 device at location zero
CFI: Found no ck804xrom @ffcd0000 device at location zero
JEDEC: Found no ck804xrom @ffcd0000 device at location zero
CFI: Found no ck804xrom @ffce0000 device at location zero
JEDEC: Found no ck804xrom @ffce0000 device at location zero
CFI: Found no ck804xrom @ffce0000 device at location zero
JEDEC: Found no ck804xrom @ffce0000 device at location zero
CFI: Found no ck804xrom @ffce0000 device at location zero
JEDEC: Found no ck804xrom @ffce0000 device at location zero
CFI: Found no ck804xrom @ffcf0000 device at location zero
JEDEC: Found no ck804xrom @ffcf0000 device at location zero
CFI: Found no ck804xrom @ffcf0000 device at location zero
JEDEC: Found no ck804xrom @ffcf0000 device at location zero
CFI: Found no ck804xrom @ffcf0000 device at location zero
JEDEC: Found no ck804xrom @ffcf0000 device at location zero
CFI: Found no ck804xrom @ffd00000 device at location zero
JEDEC: Found no ck804xrom @ffd00000 device at location zero
CFI: Found no ck804xrom @ffd00000 device at location zero
JEDEC: Found no ck804xrom @ffd00000 device at location zero
CFI: Found no ck804xrom @ffd00000 device at location zero
JEDEC: Found no ck804xrom @ffd00000 device at location zero
CFI: Found no ck804xrom @ffd10000 device at location zero
JEDEC: Found no ck804xrom @ffd10000 device at location zero
CFI: Found no ck804xrom @ffd10000 device at location zero
JEDEC: Found no ck804xrom @ffd10000 device at location zero
CFI: Found no ck804xrom @ffd10000 device at location zero
JEDEC: Found no ck804xrom @ffd10000 device at location zero
CFI: Found no ck804xrom @ffd20000 device at location zero
JEDEC: Found no ck804xrom @ffd20000 device at location zero
CFI: Found no ck804xrom @ffd20000 device at location zero
JEDEC: Found no ck804xrom @ffd20000 device at location zero
CFI: Found no ck804xrom @ffd20000 device at location zero
JEDEC: Found no ck804xrom @ffd20000 device at location zero
CFI: Found no ck804xrom @ffd30000 device at location zero
JEDEC: Found no ck804xrom @ffd30000 device at location zero
CFI: Found no ck804xrom @ffd30000 device at location zero
JEDEC: Found no ck804xrom @ffd30000 device at location zero
CFI: Found no ck804xrom @ffd30000 device at location zero
JEDEC: Found no ck804xrom @ffd30000 device at location zero
CFI: Found no ck804xrom @ffd40000 device at location zero
JEDEC: Found no ck804xrom @ffd40000 device at location zero
CFI: Found no ck804xrom @ffd40000 device at location zero
JEDEC: Found no ck804xrom @ffd40000 device at location zero
CFI: Found no ck804xrom @ffd40000 device at location zero
JEDEC: Found no ck804xrom @ffd40000 device at location zero
CFI: Found no ck804xrom @ffd50000 device at location zero
JEDEC: Found no ck804xrom @ffd50000 device at location zero
CFI: Found no ck804xrom @ffd50000 device at location zero
JEDEC: Found no ck804xrom @ffd50000 device at location zero
CFI: Found no ck804xrom @ffd50000 device at location zero
JEDEC: Found no ck804xrom @ffd50000 device at location zero
CFI: Found no ck804xrom @ffd60000 device at location zero
JEDEC: Found no ck804xrom @ffd60000 device at location zero
CFI: Found no ck804xrom @ffd60000 device at location zero
JEDEC: Found no ck804xrom @ffd60000 device at location zero
CFI: Found no ck804xrom @ffd60000 device at location zero
JEDEC: Found no ck804xrom @ffd60000 device at location zero
CFI: Found no ck804xrom @ffd70000 device at location zero
JEDEC: Found no ck804xrom @ffd70000 device at location zero
CFI: Found no ck804xrom @ffd70000 device at location zero
JEDEC: Found no ck804xrom @ffd70000 device at location zero
CFI: Found no ck804xrom @ffd70000 device at location zero
JEDEC: Found no ck804xrom @ffd70000 device at location zero
CFI: Found no ck804xrom @ffd80000 device at location zero
JEDEC: Found no ck804xrom @ffd80000 device at location zero
CFI: Found no ck804xrom @ffd80000 device at location zero
JEDEC: Found no ck804xrom @ffd80000 device at location zero
CFI: Found no ck804xrom @ffd80000 device at location zero
JEDEC: Found no ck804xrom @ffd80000 device at location zero
CFI: Found no ck804xrom @ffd90000 device at location zero
JEDEC: Found no ck804xrom @ffd90000 device at location zero
CFI: Found no ck804xrom @ffd90000 device at location zero
JEDEC: Found no ck804xrom @ffd90000 device at location zero
CFI: Found no ck804xrom @ffd90000 device at location zero
JEDEC: Found no ck804xrom @ffd90000 device at location zero
CFI: Found no ck804xrom @ffda0000 device at location zero
JEDEC: Found no ck804xrom @ffda0000 device at location zero
CFI: Found no ck804xrom @ffda0000 device at location zero
JEDEC: Found no ck804xrom @ffda0000 device at location zero
CFI: Found no ck804xrom @ffda0000 device at location zero
JEDEC: Found no ck804xrom @ffda0000 device at location zero
CFI: Found no ck804xrom @ffdb0000 device at location zero
JEDEC: Found no ck804xrom @ffdb0000 device at location zero
CFI: Found no ck804xrom @ffdb0000 device at location zero
JEDEC: Found no ck804xrom @ffdb0000 device at location zero
CFI: Found no ck804xrom @ffdb0000 device at location zero
JEDEC: Found no ck804xrom @ffdb0000 device at location zero
CFI: Found no ck804xrom @ffdc0000 device at location zero
JEDEC: Found no ck804xrom @ffdc0000 device at location zero
CFI: Found no ck804xrom @ffdc0000 device at location zero
JEDEC: Found no ck804xrom @ffdc0000 device at location zero
CFI: Found no ck804xrom @ffdc0000 device at location zero
JEDEC: Found no ck804xrom @ffdc0000 device at location zero
CFI: Found no ck804xrom @ffdd0000 device at location zero
JEDEC: Found no ck804xrom @ffdd0000 device at location zero
CFI: Found no ck804xrom @ffdd0000 device at location zero
JEDEC: Found no ck804xrom @ffdd0000 device at location zero
CFI: Found no ck804xrom @ffdd0000 device at location zero
JEDEC: Found no ck804xrom @ffdd0000 device at location zero
CFI: Found no ck804xrom @ffde0000 device at location zero
JEDEC: Found no ck804xrom @ffde0000 device at location zero
CFI: Found no ck804xrom @ffde0000 device at location zero
JEDEC: Found no ck804xrom @ffde0000 device at location zero
CFI: Found no ck804xrom @ffde0000 device at location zero
JEDEC: Found no ck804xrom @ffde0000 device at location zero
CFI: Found no ck804xrom @ffdf0000 device at location zero
JEDEC: Found no ck804xrom @ffdf0000 device at location zero
CFI: Found no ck804xrom @ffdf0000 device at location zero
JEDEC: Found no ck804xrom @ffdf0000 device at location zero
CFI: Found no ck804xrom @ffdf0000 device at location zero
JEDEC: Found no ck804xrom @ffdf0000 device at location zero
CFI: Found no ck804xrom @ffe00000 device at location zero
JEDEC: Found no ck804xrom @ffe00000 device at location zero
CFI: Found no ck804xrom @ffe00000 device at location zero
JEDEC: Found no ck804xrom @ffe00000 device at location zero
CFI: Found no ck804xrom @ffe00000 device at location zero
JEDEC: Found no ck804xrom @ffe00000 device at location zero
CFI: Found no ck804xrom @ffe10000 device at location zero
JEDEC: Found no ck804xrom @ffe10000 device at location zero
CFI: Found no ck804xrom @ffe10000 device at location zero
JEDEC: Found no ck804xrom @ffe10000 device at location zero
CFI: Found no ck804xrom @ffe10000 device at location zero
JEDEC: Found no ck804xrom @ffe10000 device at location zero
CFI: Found no ck804xrom @ffe20000 device at location zero
JEDEC: Found no ck804xrom @ffe20000 device at location zero
CFI: Found no ck804xrom @ffe20000 device at location zero
JEDEC: Found no ck804xrom @ffe20000 device at location zero
CFI: Found no ck804xrom @ffe20000 device at location zero
JEDEC: Found no ck804xrom @ffe20000 device at location zero
CFI: Found no ck804xrom @ffe30000 device at location zero
JEDEC: Found no ck804xrom @ffe30000 device at location zero
CFI: Found no ck804xrom @ffe30000 device at location zero
JEDEC: Found no ck804xrom @ffe30000 device at location zero
CFI: Found no ck804xrom @ffe30000 device at location zero
JEDEC: Found no ck804xrom @ffe30000 device at location zero
CFI: Found no ck804xrom @ffe40000 device at location zero
JEDEC: Found no ck804xrom @ffe40000 device at location zero
CFI: Found no ck804xrom @ffe40000 device at location zero
JEDEC: Found no ck804xrom @ffe40000 device at location zero
CFI: Found no ck804xrom @ffe40000 device at location zero
JEDEC: Found no ck804xrom @ffe40000 device at location zero
CFI: Found no ck804xrom @ffe50000 device at location zero
JEDEC: Found no ck804xrom @ffe50000 device at location zero
CFI: Found no ck804xrom @ffe50000 device at location zero
JEDEC: Found no ck804xrom @ffe50000 device at location zero
CFI: Found no ck804xrom @ffe50000 device at location zero
JEDEC: Found no ck804xrom @ffe50000 device at location zero
CFI: Found no ck804xrom @ffe60000 device at location zero
JEDEC: Found no ck804xrom @ffe60000 device at location zero
CFI: Found no ck804xrom @ffe60000 device at location zero
JEDEC: Found no ck804xrom @ffe60000 device at location zero
CFI: Found no ck804xrom @ffe60000 device at location zero
JEDEC: Found no ck804xrom @ffe60000 device at location zero
CFI: Found no ck804xrom @ffe70000 device at location zero
JEDEC: Found no ck804xrom @ffe70000 device at location zero
CFI: Found no ck804xrom @ffe70000 device at location zero
JEDEC: Found no ck804xrom @ffe70000 device at location zero
CFI: Found no ck804xrom @ffe70000 device at location zero
JEDEC: Found no ck804xrom @ffe70000 device at location zero
CFI: Found no ck804xrom @ffe80000 device at location zero
JEDEC: Found no ck804xrom @ffe80000 device at location zero
CFI: Found no ck804xrom @ffe80000 device at location zero
JEDEC: Found no ck804xrom @ffe80000 device at location zero
CFI: Found no ck804xrom @ffe80000 device at location zero
JEDEC: Found no ck804xrom @ffe80000 device at location zero
CFI: Found no ck804xrom @ffe90000 device at location zero
JEDEC: Found no ck804xrom @ffe90000 device at location zero
CFI: Found no ck804xrom @ffe90000 device at location zero
JEDEC: Found no ck804xrom @ffe90000 device at location zero
CFI: Found no ck804xrom @ffe90000 device at location zero
JEDEC: Found no ck804xrom @ffe90000 device at location zero
CFI: Found no ck804xrom @ffea0000 device at location zero
JEDEC: Found no ck804xrom @ffea0000 device at location zero
CFI: Found no ck804xrom @ffea0000 device at location zero
JEDEC: Found no ck804xrom @ffea0000 device at location zero
CFI: Found no ck804xrom @ffea0000 device at location zero
JEDEC: Found no ck804xrom @ffea0000 device at location zero
CFI: Found no ck804xrom @ffeb0000 device at location zero
JEDEC: Found no ck804xrom @ffeb0000 device at location zero
CFI: Found no ck804xrom @ffeb0000 device at location zero
JEDEC: Found no ck804xrom @ffeb0000 device at location zero
CFI: Found no ck804xrom @ffeb0000 device at location zero
JEDEC: Found no ck804xrom @ffeb0000 device at location zero
CFI: Found no ck804xrom @ffec0000 device at location zero
JEDEC: Found no ck804xrom @ffec0000 device at location zero
CFI: Found no ck804xrom @ffec0000 device at location zero
JEDEC: Found no ck804xrom @ffec0000 device at location zero
CFI: Found no ck804xrom @ffec0000 device at location zero
JEDEC: Found no ck804xrom @ffec0000 device at location zero
CFI: Found no ck804xrom @ffed0000 device at location zero
JEDEC: Found no ck804xrom @ffed0000 device at location zero
CFI: Found no ck804xrom @ffed0000 device at location zero
JEDEC: Found no ck804xrom @ffed0000 device at location zero
CFI: Found no ck804xrom @ffed0000 device at location zero
JEDEC: Found no ck804xrom @ffed0000 device at location zero
CFI: Found no ck804xrom @ffee0000 device at location zero
JEDEC: Found no ck804xrom @ffee0000 device at location zero
CFI: Found no ck804xrom @ffee0000 device at location zero
JEDEC: Found no ck804xrom @ffee0000 device at location zero
CFI: Found no ck804xrom @ffee0000 device at location zero
JEDEC: Found no ck804xrom @ffee0000 device at location zero
CFI: Found no ck804xrom @ffef0000 device at location zero
JEDEC: Found no ck804xrom @ffef0000 device at location zero
CFI: Found no ck804xrom @ffef0000 device at location zero
JEDEC: Found no ck804xrom @ffef0000 device at location zero
CFI: Found no ck804xrom @ffef0000 device at location zero
JEDEC: Found no ck804xrom @ffef0000 device at location zero
CFI: Found no ck804xrom @fff00000 device at location zero
JEDEC: Found no ck804xrom @fff00000 device at location zero
CFI: Found no ck804xrom @fff00000 device at location zero
JEDEC: Found no ck804xrom @fff00000 device at location zero
CFI: Found no ck804xrom @fff00000 device at location zero
Found: SST 49LF080A
ck804xrom @fff00000: Found 1 x8 devices at 0x0 in 8-bit bank
ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUS0] -> GSI 22 (level,
low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:02.0: irq 22, io mem 0xd0000000
number of JEDEC chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 10 ports detected
usb 2-6: new low speed USB device using ohci_hcd and address 2
usb 2-6: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
input: Avocent USB_AMIQ as
/devices/pci0000:00/0000:00:02.0/usb2/2-6/2-6:1.0/input/input1
input,hidraw0: USB HID v1.10 Keyboard [Avocent USB_AMIQ] on
usb-0000:00:02.0-6
input: Avocent USB_AMIQ as
/devices/pci0000:00/0000:00:02.0/usb2/2-6/2-6:1.1/input/input2
input,hidraw1: USB HID v1.10 Mouse [Avocent USB_AMIQ] on
usb-0000:00:02.0-6
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
floppy0: no floppy controllers found
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised:
[email protected]
loop: module loaded
ReiserFS: sda1: found reiserfs format "3.6" with standard journal
ReiserFS: sda1: using ordered data mode
ReiserFS: sda1: journal params: device sda1, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: sda1: checking transaction log (sda1)
ReiserFS: sda1: Using r5 hash to sort names
Floppy drive(s): fd0 is 1.44M
USB Universal Host Controller Interface driver v3.0
floppy0: no floppy controllers found
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
input: Power Button (FF) as /devices/virtual/input/input3
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /devices/virtual/input/input4
ACPI: Power Button (CM) [PWRB]
audit(1197970676.702:2): audit_pid=4043 old=0 by auid=4294967295
powernow-k8: Found 1 Dual-Core AMD Opteron(tm) Processor 1220 processors
(2 cpu cores) (version 2.20.00)
powernow-k8: 0 : fid 0x14 (2800 MHz), vid 0x8
powernow-k8: 1 : fid 0x12 (2600 MHz), vid 0xa
powernow-k8: 2 : fid 0x10 (2400 MHz), vid 0xc
powernow-k8: 3 : fid 0xe (2200 MHz), vid 0xe
powernow-k8: 4 : fid 0xc (2000 MHz), vid 0x10
powernow-k8: 5 : fid 0xa (1800 MHz), vid 0x10
powernow-k8: 6 : fid 0x2 (1000 MHz), vid 0x12
Clocksource tsc unstable (delta = -107159976 ns)
libata version 3.00 loaded.
sata_nv 0000:00:07.0: version 3.5
ACPI: PCI Interrupt Link [LTID] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [LTID] -> GSI 21 (level,
low) -> IRQ 21
sata_nv 0000:00:07.0: Using ADMA mode
PCI: Setting latency timer of device 0000:00:07.0 to 64
ata4294967295: XXX: prd ffff8100cf838000/cf838000 pad
ffff8100cf837000/cf837000
ata4294967295: XXX: prd ffff8100cf836000/cf836000 pad
ffff8100cf835000/cf835000
scsi1 : sata_nv
scsi2 : sata_nv
ata1: SATA max UDMA/133 cmd 0x14f0 ctl 0x14e0 bmdma 0x14b0 irq 21
ata2: SATA max UDMA/133 cmd 0x14d0 ctl 0x14c0 bmdma 0x14b8 irq 21
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATAPI: HL-DT-STDVD-ROM GDRH10N, 0D04, max UDMA/100
ata1.00: configured for UDMA/100
ata2: SATA link down (SStatus 0 SControl 300)
scsi 1:0:0:0: CD-ROM HL-DT-ST DVD-ROM GDRH10N 0D04 PQ: 0
ANSI: 5
ata1: bounce limit 0xFFFFFFFF, segment boundary 0xFFFF, hw segs 127
scsi 1:0:0:0: Attached scsi generic sg3 type 5
ACPI: PCI Interrupt Link [LSI1] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LSI1] -> GSI 20 (level,
low) -> IRQ 20
sata_nv 0000:00:08.0: Using ADMA mode
PCI: Setting latency timer of device 0000:00:08.0 to 64
ata4294967295: XXX: prd ffff8100cf834000/cf834000 pad
ffff8100cf833000/cf833000
ata4294967295: XXX: prd ffff8100cf832000/cf832000 pad
ffff8100cf831000/cf831000
scsi3 : sata_nv
scsi4 : sata_nv
ata3: SATA max UDMA/133 cmd 0x1840 ctl 0x1830 bmdma 0x1800 irq 20
ata4: SATA max UDMA/133 cmd 0x1820 ctl 0x1810 bmdma 0x1808 irq 20
sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
ata1.00: XXX DMA address 21c121d68 is above 32bit
ata1.00: XXX DMA address 220189000 is above 32bit
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata1.00: XXX DMA address 21ece2000 is above 32bit
ata1.00: XXX DMA address 21ece2000 is above 32bit
ata1.00: XXX DMA address 21f83b000 is above 32bit
ata1.00: XXX DMA address 21e021000 is above 32bit
ata1.00: XXX DMA address 220140000 is above 32bit
ata1.00: XXX DMA address 21e1c7000 is above 32bit
ata1.00: XXX DMA address 21e11d000 is above 32bit
ata1.00: XXX DMA address 21c089000 is above 32bit
ata1.00: XXX DMA address 21d960000 is above 32bit
ata1.00: XXX DMA address 21c0ce000 is above 32bit
ata1.00: XXX DMA address 21ec29000 is above 32bit
ata1.00: XXX DMA address 21f043000 is above 32bit
ata1.00: XXX DMA address 21c0a1000 is above 32bit
ata1.00: XXX DMA address 21c01a000 is above 32bit
ata1.00: XXX DMA address 21f029000 is above 32bit
ata1.00: XXX DMA address 21c148000 is above 32bit
ata1.00: XXX DMA address 21c1ad000 is above 32bit
ata1.00: XXX DMA address 21c009000 is above 32bit
ata1.00: XXX DMA address 21c46b000 is above 32bit
ata1.00: XXX DMA address 21c1b3000 is above 32bit
ata1.00: XXX DMA address 21e14b000 is above 32bit
ata1.00: XXX DMA address 21d5a3000 is above 32bit
ata1.00: XXX DMA address 21c0fb000 is above 32bit
ata1.00: XXX DMA address 21d922000 is above 32bit
ata1.00: XXX DMA address 21c193000 is above 32bit
ata1.00: XXX DMA address 21f0be000 is above 32bit
ata1.00: XXX DMA address 21ec3c000 is above 32bit
ata1.00: XXX DMA address 21dce2000 is above 32bit
ata1.00: XXX DMA address 21c153000 is above 32bit
ata1.00: XXX DMA address 21c1b6000 is above 32bit
ata1.00: XXX DMA address 21c14c000 is above 32bit
ata1.00: XXX DMA address 21c0fc000 is above 32bit
ata1.00: XXX DMA address 21c169000 is above 32bit
ata1.00: XXX DMA address 21dce4000 is above 32bit
ata1.00: XXX DMA address 21c08b000 is above 32bit
ata1.00: XXX DMA address 21f090000 is above 32bit
ata1.00: XXX DMA address 21f080000 is above 32bit
ata1.00: XXX DMA address 21c1ba000 is above 32bit
ata1.00: XXX DMA address 21e886000 is above 32bit
ata1.00: XXX DMA address 220448000 is above 32bit
ata1.00: XXX DMA address 220194000 is above 32bit
ata1.00: XXX DMA address 21c101000 is above 32bit
ata1.00: XXX DMA address 21f0a4000 is above 32bit
ata1.00: XXX DMA address 21dc93000 is above 32bit
ata1.00: XXX DMA address 21edb5000 is above 32bit
ata1.00: XXX DMA address 21dd56000 is above 32bit
ata1.00: XXX DMA address 21c5d1000 is above 32bit
ata1.00: XXX DMA address 21f086000 is above 32bit
ata1.00: XXX DMA address 21f020000 is above 32bit
ata1.00: XXX DMA address 21cd3a000 is above 32bit
ata1.00: XXX DMA address 21c0f4000 is above 32bit
ata1.00: XXX DMA address 21c52f000 is above 32bit
ata1.00: XXX DMA address 21c05a000 is above 32bit
ata1.00: XXX DMA address 21e950000 is above 32bit
ata1.00: XXX DMA address 21f1b6000 is above 32bit
ata1.00: XXX DMA address 21c01d000 is above 32bit
ata1.00: XXX DMA address 21c1c0000 is above 32bit
ata1.00: XXX DMA address 21c157000 is above 32bit
ata1.00: XXX DMA address 21f08b000 is above 32bit
ata1.00: XXX DMA address 21f088000 is above 32bit
ata1.00: XXX DMA address 21e189000 is above 32bit
ata1.00: XXX DMA address 21c037000 is above 32bit
ata1.00: XXX DMA address 21ecd1000 is above 32bit
ata1.00: XXX DMA address 21f04bd68 is above 32bit
ata1.00: XXX DMA address 21c109000 is above 32bit
ata1.00: XXX DMA address 21c194000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
ata1.00: XXX DMA address 21c194000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
ata1.00: XXX DMA address 21c194000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
ata1.00: XXX DMA address 21c194000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
ata1.00: XXX DMA address 21c194000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
ata1.00: XXX DMA address 21c194000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
ata1.00: XXX DMA address 22008c000 is above 32bit
ata1.00: XXX DMA address 21c113000 is above 32bit
ata1.00: XXX DMA address 21c1ae000 is above 32bit
ata1.00: XXX DMA address 21c16c000 is above 32bit
ata1.00: XXX DMA address 21f9f8000 is above 32bit
ata1.00: XXX DMA address 21f05b000 is above 32bit
ata1.00: XXX DMA address 21f095000 is above 32bit
ata1.00: XXX DMA address 21ecb2000 is above 32bit
ata1.00: XXX DMA address 220409000 is above 32bit
ata1.00: XXX DMA address 21c534000 is above 32bit
ata1.00: XXX DMA address 21c1ac000 is above 32bit
ata1.00: XXX DMA address 21f029000 is above 32bit
ata1.00: XXX DMA address 21c0a1000 is above 32bit
ata1.00: XXX DMA address 21c155000 is above 32bit
ata1.00: XXX DMA address 21f08f000 is above 32bit
ata1.00: XXX DMA address 21c01d000 is above 32bit
ata1.00: XXX DMA address 21f1b6000 is above 32bit
ata1.00: XXX DMA address 21e950000 is above 32bit
ata1.00: XXX DMA address 21c52f000 is above 32bit
ata1.00: XXX DMA address 21c1ec000 is above 32bit
ata1.00: XXX DMA address 220534000 is above 32bit
ata1.00: XXX DMA address 21dc6a000 is above 32bit
ata1.00: XXX DMA address 21f04b848 is above 32bit
ata1.00: XXX DMA address 21f04b848 is above 32bit
ata1.00: XXX DMA address 21f04bd68 is above 32bit
ata1.00: XXX DMA address 21c4a1000 is above 32bit
ata1.00: XXX DMA address 21cc61000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
ata1.00: XXX DMA address 21cc61000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
ata1.00: XXX DMA address 21cc61000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
ata1.00: XXX DMA address 21cc61000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
Buffer I/O error on device sr0, logical block 154416
ata1.00: XXX DMA address 21cc61000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
ata1.00: XXX DMA address 21cc61000 is above 32bit
end_request: I/O error, dev sr0, sector 1235328
ata1.00: XXX DMA address 21e1ed000 is above 32bit
ata1.00: XXX DMA address 21dc11000 is above 32bit
ata1.00: XXX DMA address 21c4a2000 is above 32bit
ata1.00: XXX DMA address 21c0bd000 is above 32bit
ata1.00: XXX DMA address 220078000 is above 32bit
ata1.00: XXX DMA address 21c50b000 is above 32bit
ata1.00: XXX DMA address 21dce5000 is above 32bit
ata1.00: XXX DMA address 21e10d000 is above 32bit
ata1.00: XXX DMA address 21e10c000 is above 32bit
ata1.00: XXX DMA address 21f023000 is above 32bit
ata1.00: XXX DMA address 21f022000 is above 32bit
ata1.00: XXX DMA address 21e15f000 is above 32bit
ata1.00: XXX DMA address 21e15e000 is above 32bit
ata1.00: XXX DMA address 21c053000 is above 32bit
ata1.00: XXX DMA address 21c052000 is above 32bit
ata1.00: XXX DMA address 21f0af000 is above 32bit
ata1.00: XXX DMA address 21f0ae000 is above 32bit
ata1.00: XXX DMA address 21c055000 is above 32bit
ata1.00: XXX DMA address 21c054000 is above 32bit
ata1.00: XXX DMA address 21c05d000 is above 32bit
ata1.00: XXX DMA address 21c05c000 is above 32bit
ata1.00: XXX DMA address 21c139000 is above 32bit
ata1.00: XXX DMA address 21f04b848 is above 32bit
ata1.00: XXX DMA address 204b9e000 is above 32bit
FAT: bogus logical sector size 37008
VFS: Can't find a valid FAT filesystem on dev sr0.
ata1.00: XXX DMA address 21f04b848 is above 32bit
ata1.00: XXX DMA address 1fdd42000 is above 32bit
hfs: can't find a HFS filesystem on dev sr0.
ata1.00: XXX DMA address 21f04b848 is above 32bit
MINIX-fs: blocksize too small for device
ata1.00: XXX DMA address 21f04b848 is above 32bit
ata1.00: XXX DMA address 1fdd42000 is above 32bit
ata1.00: XXX DMA address 1fdd43000 is above 32bit
ReiserFS: sr0: warning: sh-2021: reiserfs_fill_super: can not find
reiserfs on sr0
ata1.00: XXX DMA address 21f04b848 is above 32bit
ata1.00: XXX DMA address 1fde09000 is above 32bit
ata1.00: XXX DMA address 1fde09800 is above 32bit
ata1.00: XXX DMA address 2046f4000 is above 32bit
ata1.00: XXX DMA address 2046f4800 is above 32bit
ata1.00: XXX DMA address 202030000 is above 32bit
ata1.00: XXX DMA address 202030800 is above 32bit
ata1.00: XXX DMA address 203d47000 is above 32bit
ata1.00: XXX DMA address 203d47800 is above 32bit
ata1.00: XXX DMA address 203d46000 is above 32bit
ata1.00: XXX DMA address 203d46800 is above 32bit
ata1.00: XXX DMA address 203d45000 is above 32bit
ata1.00: XXX DMA address 203d45800 is above 32bit
ata1.00: XXX DMA address 203d44000 is above 32bit
ata1.00: XXX DMA address 203d44800 is above 32bit
ata1.00: XXX DMA address 200173000 is above 32bit
ata1.00: XXX DMA address 200173800 is above 32bit
ata1.00: XXX DMA address 200172000 is above 32bit
ata1.00: XXX DMA address 200172800 is above 32bit
ata1.00: XXX DMA address 200171000 is above 32bit
ata1.00: XXX DMA address 200171800 is above 32bit
ata1.00: XXX DMA address 200170000 is above 32bit
ata1.00: XXX DMA address 200170800 is above 32bit
ata1.00: XXX DMA address 200617000 is above 32bit
ata1.00: XXX DMA address 200617800 is above 32bit
ata1.00: XXX DMA address 200616000 is above 32bit
ata1.00: XXX DMA address 200616800 is above 32bit
ata1.00: XXX DMA address 202277000 is above 32bit
ata1.00: XXX DMA address 202277800 is above 32bit
ata1.00: XXX DMA address 202276000 is above 32bit
ata1.00: XXX DMA address 202276800 is above 32bit
ata1.00: XXX DMA address 202275000 is above 32bit
ata1.00: XXX DMA address 202275800 is above 32bit
ata1.00: XXX DMA address 202274000 is above 32bit
ata1.00: XXX DMA address 202274800 is above 32bit
ata1.00: XXX DMA address 208f73000 is above 32bit
ata1.00: XXX DMA address 208f73800 is above 32bit
ata1.00: XXX DMA address 208f72000 is above 32bit
ata1.00: XXX DMA address 208f72800 is above 32bit
ata1.00: XXX DMA address 208f71000 is above 32bit
ata1.00: XXX DMA address 208f71800 is above 32bit
ata1.00: XXX DMA address 208f70000 is above 32bit
ata1.00: XXX DMA address 208f70800 is above 32bit
ata1.00: XXX DMA address 206947000 is above 32bit
ata1.00: XXX DMA address 206947800 is above 32bit
ata1.00: XXX DMA address 206946000 is above 32bit
ata1.00: XXX DMA address 206946800 is above 32bit
ata1.00: XXX DMA address 206945000 is above 32bit
ata1.00: XXX DMA address 206945800 is above 32bit
ata1.00: XXX DMA address 206944000 is above 32bit
ata1.00: XXX DMA address 206944800 is above 32bit
ata1.00: XXX DMA address 206c3b000 is above 32bit
ata1.00: XXX DMA address 206c3b800 is above 32bit
ata1.00: XXX DMA address 206c3a000 is above 32bit
ata1.00: XXX DMA address 206c3a800 is above 32bit
ata1.00: XXX DMA address 206c39000 is above 32bit
ata1.00: XXX DMA address 206c39800 is above 32bit
ata1.00: XXX DMA address 206c38000 is above 32bit
ata1.00: XXX DMA address 206c38800 is above 32bit
ata1.00: XXX DMA address 1fd9fb000 is above 32bit
ata1.00: XXX DMA address 1fd9fb800 is above 32bit
ata1.00: XXX DMA address 1fd9fa000 is above 32bit
ata1.00: XXX DMA address 1fd9fa800 is above 32bit
ata1.00: XXX DMA address 1fd9f9000 is above 32bit
ata1.00: XXX DMA address 1fd9f9800 is above 32bit
ata1.00: XXX DMA address 1fd9f8000 is above 32bit
ata1.00: XXX DMA address 1fd9f8800 is above 32bit
ata1.00: XXX DMA address 207abf000 is above 32bit
ata1.00: XXX DMA address 207abf800 is above 32bit
ata1.00: XXX DMA address 207abe000 is above 32bit
ata1.00: XXX DMA address 207abe800 is above 32bit
ata1.00: XXX DMA address 207abd000 is above 32bit
ata1.00: XXX DMA address 207abd800 is above 32bit
ata1.00: XXX DMA address 207abc000 is above 32bit
ata1.00: XXX DMA address 207abc800 is above 32bit
ata1.00: XXX DMA address 207b63000 is above 32bit
ata1.00: XXX DMA address 207b63800 is above 32bit
ata1.00: XXX DMA address 207b62000 is above 32bit
ata1.00: XXX DMA address 207b62800 is above 32bit
ata1.00: XXX DMA address 207b61000 is above 32bit
ata1.00: XXX DMA address 207b61800 is above 32bit
ata1.00: XXX DMA address 207b60000 is above 32bit
ata1.00: XXX DMA address 207b60800 is above 32bit
ata1.00: XXX DMA address 20668b000 is above 32bit
ata1.00: XXX DMA address 20668b800 is above 32bit
ISOFS: Unable to identify CD-ROM format.

2007-12-18 12:13:16

[permalink] [raw]

Subject: RE: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

>ata1.00: XXX DMA address 202275000 is above 32bit

Tejun-I find the allocation always above 32bit with the following tests
-

1) kernel-2.6.24-rc5 + the 32 bit limiting patch that you provided in a
previous posting.
2) vanilla-2.6.24-rc5.

But I don't find the DMA allocation above 32bit in the kernel logs when
I apply my patch on the vanilla-2.6.24-rc5 kernel.

-Shyam

2007-12-20 11:15:33

[permalink] [raw]

Subject: RE: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)

Robert Hancock wrote:
>@@ -1153,6 +1164,15 @@
> pp->notifier_clear_block = pp->gen_block +
> NV_ADMA_NOTIFIER_CLEAR + (4 * ap->port_no);
>
>+ /* Now that the legacy PRD and padding buffer are allocated we can
>+ safely raise the DMA mask to allocate the CPB/APRD table.
>+ These are allowed to fail since we store the value that ends up
>+ being used to set as the bounce limit in slave_config later if
>+ needed. */
>+ pci_set_dma_mask(pdev, DMA_BIT_MASK(64));
>+ pci_set_consistent_dma_mask(pdev, DMA_BIT_MASK(64));
>+ pp->adma_dma_mask = *dev->dma_mask;
>+
> mem = dmam_alloc_coherent(dev, NV_ADMA_PORT_PRIV_DMA_SZ,
> &mem_dma, GFP_KERNEL);

This causes my DMA memory to always be above 4GB no matter how much I delay the setting of the 64bit DMA mask. I find that if I set the DMA mask as 32bit and not increase it to 64 bit at all then all my I/O to the DVD rom are fine.

Jeff Garzik wrote:
>I would consider setting the consistent DMA mask to 32-bit, and setting
>the overall mask to 64-bit.

>Seems like that would solve the problem?

I agree and I have tested that it is working.

-Shyam Iyer

--
This message was sent on behalf of [email protected] at openSubscriber.com
http://www.opensubscriber.com/message/[email protected]/8218887.html

2007-12-28 21:39:11