Hi all,
I have a small issue with the i2c-i801 driver. It does not register the
i2c adaptor due to an ACPI resource conflict:
[11074.459747] ACPI Warning: SystemIO range
0xf000-0xf01f conflicts with OpRegion
0xf000-0xf00f (\_SB_.PCI0.SBUS.SMBI)
Hi all,
I have a small issue with the i2c-i801 driver. It does not register the
i2c adaptor due to an ACPI resource conflict:
[11074.459747] ACPI Warning: SystemIO range
0xf000-0xf01f conflicts with OpRegion
0xf000-0xf00f (\_SB_.PCI0.SBUS.SMBI)
Hi Andi,
On 25/03/13 11:32, Andi Kleen wrote:
> Christian Schmidt writes:
>>
>> Is there a way I can make the scheduler put those on multiple cores?
>
> Submit the IO from multiple cores. Don't use dd.
The dd processes run on multiple cores. I do understand that you
Hi everyone,
I am trying to troubleshoot some strange performance issues I am seeing
on a machine of mine. Said machine had 10 drives mapped via separate
dm-crypt instances. The aggregate (read) throughput seems to hover
around 120-130MB/s (looking at iostat -x -d) when running an instance of
dd
Hi everyone,
I am trying to troubleshoot some strange performance issues I am seeing
on a machine of mine. Said machine had 10 drives mapped via separate
dm-crypt instances. The aggregate (read) throughput seems to hover
around 120-130MB/s (looking at iostat -x -d) when running an instance of
dd
Hi Andi,
On 25/03/13 11:32, Andi Kleen wrote:
Christian Schmidt schm...@digadd.de writes:
Is there a way I can make the scheduler put those on multiple cores?
Submit the IO from multiple cores. Don't use dd.
The dd processes run on multiple cores. I do understand that you were
saying
Hi Andi,
Andi Kleen wrote:
> Christian Schmidt <[EMAIL PROTECTED]> writes:
>> Where is the inherent limit? The partitioning software, or partitioning
>> all by itself?
>
> DOS style partitioning don't support more than 2TB. You either need
> to use EFI partiti
Hi everyone,
I added a drive to a linux software RAID-5 last night. Now that worked
fine... until I changed the partition table.
Disk /dev/md_d5: 2499.9 GB, 240978560 bytes
2 heads, 4 sectors/track, 610349360 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start
Hi everyone,
I added a drive to a linux software RAID-5 last night. Now that worked
fine... until I changed the partition table.
Disk /dev/md_d5: 2499.9 GB, 240978560 bytes
2 heads, 4 sectors/track, 610349360 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start
Hi Andi,
Andi Kleen wrote:
Christian Schmidt [EMAIL PROTECTED] writes:
Where is the inherent limit? The partitioning software, or partitioning
all by itself?
DOS style partitioning don't support more than 2TB. You either need
to use EFI partitions (e.g. using parted) or LVM. Since parted's
Hi all,
I could not find good documentation anywhere on the memory usage of
linux, or rather, how to interpret the output of the various tools
dealing with memory consumption.
First of, generally - there's resident, virtual and shared memory for
each process, and global buffers/cache.
Global
Hi all,
I could not find good documentation anywhere on the memory usage of
linux, or rather, how to interpret the output of the various tools
dealing with memory consumption.
First of, generally - there's resident, virtual and shared memory for
each process, and global buffers/cache.
Global
Dear all,
How do I actually low-level format a floppy disk in an
USB-Floppy-Disk-Drive?
I tried as with usual drives, using fdformat:
[~]>fdformat /dev/sdd
Could not determine current format type: Invalid argument
But setting the format failed as well:
[~]>setfdprm -p /dev/sdd 1440/1440
Dear all,
How do I actually low-level format a floppy disk in an
USB-Floppy-Disk-Drive?
I tried as with usual drives, using fdformat:
[~]fdformat /dev/sdd
Could not determine current format type: Invalid argument
But setting the format failed as well:
[~]setfdprm -p /dev/sdd 1440/1440
14 matches
Mail list logo
