).
Adding nopaic/nolapic/noacpi options to the kernel command line helped
in my case.
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
this would be
greatly appreciated.
Does it make a difference if you embed initramfs directly in the kernel?
CONFIG_INITRAMFS_SOURCE=/path/to/your/initramfs/directory
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
Andrew Walrond schrieb:
On Friday 23 February 2007 13:32, Tomasz Chmielewski wrote:
Andrew Walrond schrieb:
On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the
same procedure successfully on x86_64 and itanium2 servers).
The relevent silo section looks like this:
image
initrd/initramfs
to start your favourite program that wipes the memory...
--
Tomasz Chmielewski
http://blog.wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
across reboots.
IIRC only mounted partitions' reads are cached.
Or, in general, those devices which kernel actually uses (mounted, but
also LVM, RAID, which don't have to be mounted to get cached).
--
Tomasz Chmielewski
http://lists.wpkg.org
-
To unsubscribe from this list: send the line
projects? RedHat, Novell, IBM,
others - anyone reading this thread?
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
because of a 2.6.23 regression ;)
--
Tomasz Chmielewski
http://blog.wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
8,1 807791616
45 /file (deleted)
That said, you might want to use lsof and search for deleted before
concluding any further.
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
by your distribution, the
newest kernel from kernel.org (there are some older, still maintaned
kernels with security fixes, too).
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
and USB modules, and the modprobing them again
should help.
Just take care if you have it connected to the PC with a USB keyboard ;)
--
Tomasz Chmielewski
http://blog.wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
and only the storage one
is recognized
:(
What modules exactly do you unload/load again, in what order, using
which commands?
--
Tomasz Chmielewski
http://blog.wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
backup_modules/? Where do you keep your modules?
--
Tomasz Chmielewski
http://blog.wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
Oct 3 10:14:12 tomek kernel: [c011c3fe] sys_exit_group+0xf/0x11
Oct 3 10:14:12 tomek kernel: [c0103da2] sysenter_past_esp+0x5f/0x99
Oct 3 10:14:12 tomek kernel: ===
--
Tomasz Chmielewski
http://blog.wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux
- the system will
be waiting for the I/O to complete, until the systems are connected again).
A brief reading of official DRBD FAQ didn't give me an answer to that
problem.
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
communication here? How many bugs are there that
are falsely opened, when in reality they were resolved long ago?
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
list?
Bugzilla sucks, emails rules because it is in your face and
gets people to work on things.
Bugzilla can be configured to send emails, too (to the list for a newly
reported bug for example).
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe
of them are
relevant? How many of them are duplicates?
And - how many of these bug reports have kernel's bugzilla ever
forwarded to lkml so that other people could see them?
Is that number zero (because kernel's bugzilla is configured this way)?
--
Tomasz Chmielewski
-
To unsubscribe from
patch to the main
developer?
Wouldn't be your problem fixed if you did it?
WHY?
BECAUSE EMAIL ENGAGES PEOPLE AND BUGZILLA DOES NOT!
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
Adrian Bunk schrieb:
On Sun, Apr 29, 2007 at 11:04:10PM +0200, Tomasz Chmielewski wrote:
Linus Torvalds wrote:
On Sun, 29 Apr 2007, Adrian Bunk wrote:
The kernel Bugzilla currently contains 1600 open bugs.
Adrian, why do you keep harping on this, and ignoring reality?
Kernel bugzilla has
I have a Silicon Image SIL3112A SATA PCI controller + 2x 200GB, 8MB
Barracuda drives.
The performance under 2.6 kernels is *very* poor (Timing buffered disk
reads never more than 20 MB/sec); under 2.4 it runs quite fine (Timing
buffered disk reads around 60 MB/sec).
Below three hdparm reads on
I have a Silicon Image SIL3112A SATA PCI controller + 2x 200GB, 8MB
Barracuda drives.
The performance under 2.6 kernels is *very* poor (Timing buffered disk
reads never more than 20 MB/sec); under 2.4 it runs quite fine (Timing
buffered disk reads around 60 MB/sec).
Below three hdparm reads on
Tomasz Torcz wrote:
On Thu, Apr 14, 2005 at 06:23:30PM +0200, Tomasz Chmielewski wrote:
I have a Silicon Image SIL3112A SATA PCI controller + 2x 200GB, 8MB
Barracuda drives.
Bad combination.
OK, from the link you gave I can see that there might be some problems
with SIL3112 controller + seagate
Tomasz Torcz wrote:
See: http://home-tj.org/m15w/
...but this link just doesn't explain why performance is sooo bad with
2.6.11.x kernels (Timing buffered disk reads at 10-20 MB/sec), and is
just OK with older 2.6 kernels (Timing buffered disk reads even at about
100 MB/sec with 2.6.8.1).
any
Chris Wright wrote:
* Tomasz Chmielewski ([EMAIL PROTECTED]) wrote:
or should I wait for 2.6.11.7 (?), where it should be corrected?
well, indeed, a week ago or more :)
Wait, no longer, 2.6.11.7 has been here already ;-) However, nothing in
this area was touched. If there's an outstanding issue
Andre Bender wrote:
OK so Tomasz Torch suggested that my drive was blacklisted somewhere
after 2.6.8.1 (it's the last kernel on which I have good performance).
Does drive blacklisting = very poor performance?
And no drive blacklisting = good performance, and possibly data corruption?
That's what
Jeff Garzik wrote:
My Linux SATA software/hardware status reports have just been updated.
To see where libata (SATA) support stands for a particular piece of
hardware, or a particular feature, go to
http://linux.yyz.us/sata/
A nice thing in FAQ would be some info on problematic
Andre Tomt wrote:
Tomasz Chmielewski wrote:
[1] although my drive is blacklisted (Seagate barracuda -
ST3200822AS), I unblacklisted it to get full performance - it's
under heavy stress for 12th hour, and still no error.
It could be that your drive has newer firmware. Too bad firmware
upgrades
Bodo Eggert [EMAIL PROTECTED] wrote:
Bodo Eggert [EMAIL PROTECTED] wrote:
Tomasz Chmielewski [EMAIL PROTECTED] wrote:
Is there a way to check what firmware a drive has
The obvious one: hdparm
Ingrid
Or, since hdparm doesn't work for SCSI devices,
cat /sys/block/sd$n/device/rev
(might depend
:59 s9 kernel: [57826.921982] wlan0: associated
Jul 18 01:34:59 s9 kernel: [57826.929627] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0:
link becomes ready
--
Tomasz Chmielewski
http://www.ptraveler.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
We are running almost 20 Fujitsu-Siemens Scenic machines, 2.6.8.1
kernel, equipped with a onboard card that uses a tulip module:
02:01.0 Ethernet controller: Linksys NC100 Network Everywhere Fast
Ethernet 10/100 (rev 11)
No problem with those.
We are running four more machines like that,
jerome lacoste schrieb:
On 8/23/05, Tomasz Chmielewski [EMAIL PROTECTED] wrote:
We are running almost 20 Fujitsu-Siemens Scenic machines, 2.6.8.1
kernel, equipped with a onboard card that uses a tulip module:
02:01.0 Ethernet controller: Linksys NC100 Network Everywhere Fast
Ethernet 10/100
jerome lacoste schrieb:
On 8/23/05, Tomasz Chmielewski [EMAIL PROTECTED] wrote:
(...)
We are running four more machines like that, the only difference is the
kernel they are running (2.6.11.4).
On some of them, there are serious problems with a network, and they
usually happen when
static int __init do_mount_root and void
__init mount_block_root? Any clues on that?
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
Alon Bar-Lev wrote:
On 1/17/07, Tomasz Chmielewski [EMAIL PROTECTED] wrote:
Does this make sense?
Why not add this logic into your initramfs?
Because the kernel itself is on a small flash partition (RedBoot
executes the kernel from /dev/mtd1), which is only 1572864 bytes big.
So
use uClibc and busybox)?
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
H. Peter Anvin wrote:
Tomasz Chmielewski wrote:
All right.
I see that initramfs is attached to the kernel itself.
So it leaves me only a question: will I fit all tools into 300 kB
(considering I'll use uClibc and busybox)?
You don't need to use busybox and have a bunch of tools
H. Peter Anvin wrote:
Tomasz Chmielewski wrote:
H. Peter Anvin wrote:
Tomasz Chmielewski wrote:
All right.
I see that initramfs is attached to the kernel itself.
So it leaves me only a question: will I fit all tools into 300 kB
(considering I'll use uClibc and busybox)?
You don't need
it with initramfs (although not as flexible).
I tried your patch against 2.6.19, with some minor changes (as it
wouldn't apply), but it didn't work for me (perhaps I just screwed
something).
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux
Synchronizing SCSI cache for disk sda:
ACPI: PCI interrupt for device :01:00.0 disabled
Now I could remove the module without problems.
What was using the module in the first scenario (I couldn't remove the
module)?
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send
Andreas Schwab wrote:
Tomasz Chmielewski [EMAIL PROTECTED] writes:
What was using the module in the first scenario (I couldn't remove the
module)?
Check lsmod for modules depending on this one.
You mean the Used by column? No, it's not used by any other module
according to lsmod output
Ross Vandegrift wrote:
On Sun, Dec 03, 2006 at 12:58:24PM +0100, Tomasz Chmielewski wrote:
You mean the Used by column? No, it's not used by any other module
according to lsmod output.
Any other methods of checking what uses /dev/sda*?
There's a good chance that if it was loaded at system
Jim Crilly wrote:
On 12/03/06 08:59:10PM +0100, Tomasz Chmielewski wrote:
Ross Vandegrift wrote:
On Sun, Dec 03, 2006 at 12:58:24PM +0100, Tomasz Chmielewski wrote:
You mean the Used by column? No, it's not used by any other module
according to lsmod output.
Any other methods of checking
Tobias Oed wrote:
Tomasz Chmielewski wrote:
Ross Vandegrift wrote:
On Sun, Dec 03, 2006 at 12:58:24PM +0100, Tomasz Chmielewski wrote:
You mean the Used by column? No, it's not used by any other module
according to lsmod output.
Any other methods of checking what uses /dev/sda*?
There's
his patch adds VT6421 PATA support to sata_via.
If we don't want to enable PATA support, nothing is changed in sata_via
driver:
M VIA SATA support
[ ] VT6421 PATA support (HIGHLY EXPERIMENTAL)
The patch is based on the patch from VIA, it applies to 2.6.19.
--
Tomasz Chmielewski
.
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
is
started again (kernel upgrade, target daemon upgrade, server reboot etc.).
Imagine you have to reboot all your NFS clients when you reboot your NFS
server. Not only that - your data is probably corrupted, or at least the
filesystem deserves checking...
--
Tomasz Chmielewski
http://wpkg.org
FUJITA Tomonori schrieb:
On Tue, 05 Feb 2008 08:14:01 +0100
Tomasz Chmielewski [EMAIL PROTECTED] wrote:
James Bottomley schrieb:
These are both features being independently worked on, are they not?
Even if they weren't, the combination of the size of SCST in kernel plus
the problem of having
.
If you're 64 bit, you need to have really loads of storage and/or RAM to
accumulate 16EB:
# mount -t tmpfs -o size=171798691839G tmpfs /mnt/2
# df -h
(...)
tmpfs 16E 0 16E 0% /mnt/2
--
Tomasz Chmielewski
http://lists.wpkg.org
--
To unsubscribe from this list: send the line
for this rebooting problem.
The way kexec works now makes rebooting unreliable again:
- network interfaces are brought down,
- kernel tries to sync - it never will, as we're booted off network,
which is down
Any ideas why kexec insists on syncing?
--
Tomasz Chmielewski
http://blog.wpkg.org
Vivek Goyal schrieb:
On Thu, Feb 07, 2008 at 03:13:30PM +0100, Tomasz Chmielewski wrote:
According to kernel/kexec.c:
* kexec does not sync, or unmount filesystems so if you need
* that to happen you need to do that yourself.
In latest kexec code I do see it syncing. But it does
).
(forever = 1 hour ... or never completes)
Is this similar to the problem that the OP is asking about?
Is it a diskless station?
Even in not, just make sure you don't shut the network down before NFS
is actually unmounted...?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from
.
And for reducing power on CPUs that can't do any power management, just
throttling.
For example, a server that doesn't crunch any numbers at night will
certainly use less power when throttled.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe
to be increased.
What CPUFreq processor driver are you using?
I had a similar problem with CPUfreq and dm-crypt (slow reads), see
(more setup problem than something kernel-related):
http://blog.wpkg.org/2008/01/22/cpufreq-and-dm-crypt-performance-problems/
--
Tomasz Chmielewski
--
To unsubscribe
% Mounted on
/dev/sda 1,2T 697G 452G 61% /mnt/iscsi_backup
# df -i
FilesystemInodes IUsed IFree IUse% Mounted on
/dev/sda154M 20M134M 13% /mnt/iscsi_backup
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send
, as files/hardlinks come and go, it would degrade again.
Are there better choices than ext3 for a filesystem with lots of
hardlinks? ext4, once it's ready? xfs?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
most of the files will
have multiple hardlinks).
I noticed using write back helps a tiny bit, but as dm and md don't
support write barriers, I'm not very eager to use it.
[1] http://backuppc.sf.net
http://backuppc.sourceforge.net/faq/BackupPC.html#some_design_issues
--
Tomasz Chmielewski
.
As most of the ideas here in this thread assume (re)creating a new
filesystem from scratch - would perhaps playing with
/proc/sys/vm/dirty_ratio and /proc/sys/vm/dirty_background_ratio help a bit?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line
Chris Mason schrieb:
On Tuesday 19 February 2008, Tomasz Chmielewski wrote:
Theodore Tso schrieb:
(...)
The following ld_preload can help in some cases. Mutt has this hack
encoded in for maildir directories, which helps.
It doesn't work very reliable for me.
For some reason, it hangs
On 07/22/2012 12:48 PM, Roland Dreier wrote:
Thanks Hugh. I just went ahead and built 3.5 final, and suspend/resume
look to be working again.
I'm not even going to try to understand how a timekeeping bug broke resume...
Yep, seems to be working fine here, too.
--
Tomasz Chmielewski
http
Performance Monitor (rev 07)
--
Tomasz Chmielewski
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
.
Especially, if a pendrive is used as a rootfs for a small device.
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
Jörn Engel schrieb:
On Mon, 11 June 2007 13:53:00 +0200, Tomasz Chmielewski wrote:
jffs2 only works on mtd devices, and that excludes pendrives, which are
block devices. I know LogFS will work with block devices one day, but
currently, it doesn't (and is not in the kernel yet as well
stuff natively on some small mipsel devices, and generally
moving files back and forth a lot (ext3 + noatime).
Still, it works just fine.
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
-a /dev/sda gives normal output, and no
more strange kernel errors.
Hopefully, it'll get fixed in smartmontools soon (or is fixed already,
but not yet mainline).
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
such a specialised
network operation.
Krzysztof, why is LE not supported?
Do you need access to ixp4xx that starts in LE mode?
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
Alexey Zaytsev schrieb:
On 5/8/07, Tomasz Chmielewski [EMAIL PROTECTED] wrote:
Michael Jones wrote:
+#ifndef __ARMEB__
+#warning Little endian mode not supported
+#endif
Personally I'm less fussed about WAN / LE support. Anyone with any
sense will run ixp4xx boards doing
then, and (at best) put that trivial workaround?
Does using ixp4xx on LE have any other drawbacks than inferior network
performance?
And talking about network performance, what numbers are we talking about
(LE vs BE; 30% performance hit on LE, more, or less)?
--
Tomasz Chmielewski
http
adapter looks just like a mouse).
And yet another viable alternative is to use a totally different device
which is fully supported under Linux or another system, right? :)
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
to engineer properly).
--
Tomasz Chmielewski
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
engines.
The device I use is Thecus n4100, it is Platform: IQ31244 (XScale),
and has 600 MHz CPU.
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
Tomasz Chmielewski schrieb:
Ronen Shitrit wrote:
The resync numbers you sent, looks very promising :)
Do you have any performance numbers that you can share for these set of
patches, which shows the Rd/Wr IO bandwidth.
I have some simple tests made with hdparm, with the results I don't
information
part: 11/48594944 files (9.1% non-contiguous), 1574757/97187200 blocks
9.1% non-contiguous - what meaning does it really have?
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
regressiobs on linux-ide list (at least
when looking at the subjects: lots of patches from you, and two reports
from me).
--
Tomasz Chmielewski
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
)
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
be certainly unwanted in some cases.
Certainly, I would like the norecovery option.
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
Version: P06RBV
Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129
Card Reader Controller
--
Tomasz Chmielewski
http://www.sslrack.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo
]---
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[kworker/0:221]
root 19492 0.0 0.0 0 0 ?D06:54 0:00 \_
[kworker/0:226]
root 19533 0.0 0.0 0 0 ?D06:54 0:00 \_
[kworker/4:257]
Is it a known issue?
The server has 8 CPUs and 32 GB RAM.
Tomasz Chmielewski
https://lxadm.com
On 2016-09-19 16:08, Tomasz Chmielewski wrote:
On several servers running 4.7.x and 4.8-rc6/7 kernels I'm seeing
thousands of kworker processes.
# ps auxf|grep -c kworker
2104
Load average goes into hundreds on a pretty much idle server (biggest
CPU and RAM consumers are probably SSHD with one
s/5036 - kernel 4.7.2, initially
attributed to ZFS on Linux, but then reproduced without ZFS
https://github.com/systemd/systemd/issues/4069 - kernel 4.7.2
I'll try to bisect.
Tomasz Chmielewski
https://lxadm.com
On 2016-09-25 18:29, Tomasz Chmielewski wrote:
I'll try to bisect.
OK, not a kernel regression, but some config change caused it.
However, I'm not able to locate which change exactly.
I'm attaching two configs which I've tried with 4.7.3 - one results in
thousands of kworkers, and the other
/proc/$kworker-pid/stack files and see if a pattern emerges.
FYI, it was reproduced and bisected here (scroll to the bottom):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626564
Tomasz Chmielewski
https://lxadm.com
I have a Silicon Image SIL3112A SATA PCI controller + 2x 200GB, 8MB
Barracuda drives.
The performance under 2.6 kernels is *very* poor (Timing buffered disk
reads never more than 20 MB/sec); under 2.4 it runs quite fine (Timing
buffered disk reads around 60 MB/sec).
Below three hdparm reads on
I have a Silicon Image SIL3112A SATA PCI controller + 2x 200GB, 8MB
Barracuda drives.
The performance under 2.6 kernels is *very* poor (Timing buffered disk
reads never more than 20 MB/sec); under 2.4 it runs quite fine (Timing
buffered disk reads around 60 MB/sec).
Below three hdparm reads on
Tomasz Torcz wrote:
On Thu, Apr 14, 2005 at 06:23:30PM +0200, Tomasz Chmielewski wrote:
I have a Silicon Image SIL3112A SATA PCI controller + 2x 200GB, 8MB
Barracuda drives.
Bad combination.
OK, from the link you gave I can see that there might be some problems
with SIL3112 controller + seagate
Tomasz Torcz wrote:
See: http://home-tj.org/m15w/
...but this link just doesn't explain why performance is sooo bad with
2.6.11.x kernels (Timing buffered disk reads at 10-20 MB/sec), and is
just OK with older 2.6 kernels (Timing buffered disk reads even at about
100 MB/sec with 2.6.8.1).
any
Chris Wright wrote:
* Tomasz Chmielewski ([EMAIL PROTECTED]) wrote:
or should I wait for 2.6.11.7 (?), where it should be corrected?
well, indeed, a week ago or more :)
Wait, no longer, 2.6.11.7 has been here already ;-) However, nothing in
this area was touched. If there's an outstanding issue
Andre Bender wrote:
OK so Tomasz Torch suggested that my drive was blacklisted somewhere
after 2.6.8.1 (it's the last kernel on which I have good performance).
Does drive blacklisting = very poor performance?
And no drive blacklisting = good performance, and possibly data corruption?
That's what
Jeff Garzik wrote:
My Linux SATA software/hardware status reports have just been updated.
To see where libata (SATA) support stands for a particular piece of
hardware, or a particular feature, go to
http://linux.yyz.us/sata/
A nice thing in FAQ would be some info on problematic
Andre Tomt wrote:
Tomasz Chmielewski wrote:
<
[1] although my drive is blacklisted (Seagate barracuda -
ST3200822AS), I "unblacklisted" it to get full performance - it's
under heavy stress for 12th hour, and still no error.
It could be that your drive has newer firmware. Too
Bodo Eggert <[EMAIL PROTECTED]> wrote:
Bodo Eggert <[EMAIL PROTECTED]> wrote:
Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
Is there a way to check what firmware a drive has
The obvious one: hdparm
Or, since hdparm doesn't work for SCSI devices,
cat /sys/block/sd$n/device
We are running almost 20 Fujitsu-Siemens Scenic machines, 2.6.8.1
kernel, equipped with a onboard card that uses a tulip module:
02:01.0 Ethernet controller: Linksys NC100 Network Everywhere Fast
Ethernet 10/100 (rev 11)
No problem with those.
We are running four more machines like that,
jerome lacoste schrieb:
On 8/23/05, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
We are running almost 20 Fujitsu-Siemens Scenic machines, 2.6.8.1
kernel, equipped with a onboard card that uses a tulip module:
02:01.0 Ethernet controller: Linksys NC100 Network Everywhere Fast
Ethernet
jerome lacoste schrieb:
On 8/23/05, Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
(...)
We are running four more machines like that, the only difference is the
kernel they are running (2.6.11.4).
On some of them, there are serious problems with a network, and they
usually happe
ta_mv
# dmesg -c
Synchronizing SCSI cache for disk sda:
ACPI: PCI interrupt for device :01:00.0 disabled
Now I could remove the module without problems.
What was using the module in the first scenario (I couldn't remove the
module)?
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscrib
Andreas Schwab wrote:
Tomasz Chmielewski <[EMAIL PROTECTED]> writes:
What was using the module in the first scenario (I couldn't remove the
module)?
Check lsmod for modules depending on this one.
You mean the "Used by" column? No, it's not used by any other module
ac
Ross Vandegrift wrote:
On Sun, Dec 03, 2006 at 12:58:24PM +0100, Tomasz Chmielewski wrote:
You mean the "Used by" column? No, it's not used by any other module
according to lsmod output.
Any other methods of checking what uses /dev/sda*?
There's a good chance that if it was loaded
Jim Crilly wrote:
On 12/03/06 08:59:10PM +0100, Tomasz Chmielewski wrote:
Ross Vandegrift wrote:
On Sun, Dec 03, 2006 at 12:58:24PM +0100, Tomasz Chmielewski wrote:
You mean the "Used by" column? No, it's not used by any other module
according to lsmod output.
Any other methods o
Tobias Oed wrote:
Tomasz Chmielewski wrote:
Ross Vandegrift wrote:
On Sun, Dec 03, 2006 at 12:58:24PM +0100, Tomasz Chmielewski wrote:
You mean the "Used by" column? No, it's not used by any other module
according to lsmod output.
Any other methods of checking what uses /dev/sda*
his patch adds VT6421 PATA support to sata_via.
If we don't want to enable PATA support, nothing is changed in sata_via
driver:
VIA SATA support
[ ] VT6421 PATA support (HIGHLY EXPERIMENTAL)
The patch is based on the patch from VIA, it applies to 2.6.19.
--
Tomasz Chmielewski
http
1 - 100 of 164 matches
Mail list logo
