Re: everything in wait_for_completion, what is my system doing?

Hello Andrew, thanks for your help! On Friday 07 December 2007 02:09:11 Andrew Morton wrote: On Wed, 5 Dec 2007 21:44:54 +0100 Bernd Schubert [EMAIL PROTECTED] wrote: after scsi-recovery a system here went into some kind lock-up, everything seems to be in wait_for_completion(). Please see

sleep before boot panic

was missing. Signed-off-by: Bernd Schubert [EMAIL PROTECTED] Index: zd1211rw.git.beno/init/do_mounts.c === --- zd1211rw.git.beno.orig/init/do_mounts.c 2008-01-06 18:44:23.0 +0100 +++ zd1211rw.git.beno/init/do_mounts.c 2008-01

Re: sata sil3114 vs. certain seagate drives results in filesystem corruptions

, but as much as it fits onto the disk. On reading back this file, the filesystem will report errors somewhere between 50GB and 230GB (disk size is 250GB). Thanks. I'll try to reproduce the problem here. What's your motherboard? All tested S2882 boards here. Cheers, Bernd -- Bernd Schubert

Re: sata sil3114 vs. certain seagate drives results in filesystem corruptions

On Monday 22 October 2007 12:36:32 Soeren Sonnenburg wrote: On Mon, 2007-10-22 at 11:48 +0200, Bernd Schubert wrote: Hello, On Monday 22 October 2007 04:12:44 Tejun Heo wrote: Helo, [...] Now when I write large files of zeros to root(sdasdb) and read the file back

Re: sata sil3114 vs. certain seagate drives results in filesystem corruptions

are corrupted). Are you getting similiarly many in the 50G - 230G region? I never tested what is corrupted. Well, a diff over 250GB would take quite a lot of time... -- Bernd Schubert Q-Leap Networks GmbH - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body

Re: [PATCH 3/3] faster workaround

it would solve Soerens problem and ours as well (ours magically already went away using the mod15 fix). Well, maybe I port it anyway to 2.6.23 to see if it also solves our problem. Thanks, Bernd -- Bernd Schubert Q-Leap Networks GmbH - To unsubscribe from this list: send the line unsubscribe

2.6.23 regression: do_nanosleep will not return

Hi, we have a system here were e.g. sleep 1 will never finish. This is an issue of 2.6.23, on all older kernel versions it did work fine. Seems to hang in do_nanosleep() [ 153.775792] sleep S 0 5372 5341 [ 153.782385] 81007f0a9ea8

Re: 2.6.23 regression: do_nanosleep will not return

Bernd Schubert wrote: Hi, we have a system here were e.g. sleep 1 will never finish. This is an issue of 2.6.23, on all older kernel versions it did work fine. Seems to hang in do_nanosleep() Update: Enabling hpet in the bios and setting clocksource=hpet as command line parameter

Re: 2.6.23 regression: do_nanosleep will not return

On Monday 08 October 2007 16:32:52 Rik van Riel wrote: On Mon, 08 Oct 2007 15:20:26 +0200 Bernd Schubert [EMAIL PROTECTED] wrote: Bernd Schubert wrote: we have a system here were e.g. sleep 1 will never finish. This is an issue of 2.6.23, on all older kernel versions it did work fine

patch: improve generic_file_buffered_write()

/mailarchive/forum.php?thread_name=200708312003.30446.bernd-schubert%40gmx.deforum_name=nfs While this especially effects lustre, Olaf Kirch also noticed it on another filesystem before and wrote a nfs patch for it. This patch has two disadvantages - it requires to move all data within the pages

Re: patch: improve generic_file_buffered_write() (2nd try 1/2)

Hello Randy, thanks for your review. On Wednesday 05 September 2007 17:35:29 Randy Dunlap wrote: On Wed, 5 Sep 2007 15:45:36 +0200 Bernd Schubert wrote: Hi, meta-comments: filemap.c | 144 +- 1 file changed, 96 insertions

Re: patch: improve generic_file_buffered_write() (2nd try 2/2)

I guess when aio was introduced this was probably forgotten. For small chunks or synchronous i/o the likehood is correct, but for big data chunks and aio the likehood is false. Signed-off-by: Bernd Schubert [EMAIL PROTECTED] Signed-off-by: Goswin von Brederlow [EMAIL PROTECTED] Index: linux

[PATCH 1/2][RESEND] improve generic_file_buffered_write()

, this happens since there is an offset on the very first page due to the nfs header. http://sourceforge.net/mailarchive/forum.php?thread_name=200708312003.30446.bernd-schubert%40gmx.deforum_name=nfs While this especially effects lustre, Olaf Kirch also noticed it on another filesystem before and wrote a nfs

[PATCHES] Re: sil3114 data corruption

On Wednesday 10 October 2007 11:12:20 Bernd Schubert wrote: On Monday 08 October 2007 17:09:17 Bernd Schubert wrote: [sorry for sending twice, but after I read the sil sources, I see the mail address had been wrong] Hi, somehow the sil3114 causes data corruption with some (newer

[PATCH 1/3] Re: sil3114 data corruption

This will add the Seagate ST3250820AS to the mod15 blacklist. I think this is rather trivial and should go into any any release as soon as possible, since there will be data corruption without it for this disk. Signed-off-by: Bernd Schubert [EMAIL PROTECTED] Index: linux-2.6.23-rc9/drivers/ata

Re: [PATCH 2/3] Re: sil3114 data corruption

/s to 20-25MB/s. But better safe than lost data or damaged filesystem. Signed-off-by: Bernd Schubert [EMAIL PROTECTED] Index: linux-2.6.23-rc9/drivers/ata/sata_sil.c === --- linux-2.6.23-rc9.orig/drivers/ata/sata_sil.c2007-10

Re: [PATCH 3/3] faster workaround

| 58 ++-- include/linux/libata.h|6 +++ 3 files changed, 62 insertions(+), 11 deletions(-) Signed-off-by: Bernd Schubert [EMAIL PROTECTED] Index: linux-2.6.23-rc9/drivers/ata/libata-core.c

Re: [PATCH 3/3] faster workaround

and no definite prove... Also, this is with 3114, maybe this chip behaves a bit different than 3112? Thanks, Bernd -- Bernd Schubert Q-Leap Networks GmbH - 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

Re: [PATCH 3/3] faster workaround

On Thursday 11 October 2007 17:04:45 Jeff Garzik wrote: Bernd Schubert wrote: On Thursday 11 October 2007 16:19:37 Jeff Garzik wrote: 1) Just about the only valid optimization is to ensure that only the write path must be limited to small chunks, not both read- and write-paths. Tejun had

Re: [PATCH 3/3] faster workaround

On Friday 12 October 2007 23:08:21 Jeff Garzik wrote: Bernd Schubert wrote: a) 2.6.23 + sil-patch I posted, this is on a customer system (though my former group), I wouldn't like to use -mm there. b) .config is attached c) attached d) attached (don't get irritaded by those machine

Re: CDR read problems with 2.6.11?

[...] [EMAIL PROTECTED]:~[1009]# mount /mnt/cdrom mount: wrong fs type, bad option, bad superblock on /dev/cdrom, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so [...] The drive is a NEC DVD+RW ND-5100A

Re: Problem with kernel 2.6.11

, [RTMIN], NULL, 8) = 0 --- SIGCHLD (Child exited) @ 0 (0) --- Same here. Cheers, Bernd -- Bernd Schubert PCI / Theoretische Chemie Universität Heidelberg INF 229 69120 Heidelberg e-mail: [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel

Re: 2.6.12.3 network slowdown?

driver is only in 2.6.13-rc or 2.6.12-mm (also already in previous -mm kernel versions). Bernd -- Bernd Schubert Physikalisch Chemisches Institut / Theoretische Chemie Universität Heidelberg INF 229 69120 Heidelberg e-mail: [EMAIL PROTECTED] - To unsubscribe from this list: send the line

2.6.11.12: oops + panic

20 00 2b 4b 0c c7 03 00 01 10 00 -- Bernd Schubert PCI / Theoretische Chemie Universität Heidelberg INF 229 69120 Heidelberg e-mail: [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info

Re: x86_64: 32bit emulation problems

On Thursday 03 March 2005 10:19, Andi Kleen wrote: On Wed, Mar 02, 2005 at 08:53:07AM -0800, Trond Myklebust wrote: on den 02.03.2005 Klokka 12:33 (+0100) skreiv Bernd Schubert: I can see no good reason for truncating inode number values on platforms that actually do support 64-bit

swapper: page allocation failure. order:1, mode:0x20

} Feb 28 10:07:36 hitchcock kernel:8010f094{default_idle+36} 8010f147{cpu_idle+39} -- Bernd Schubert Physikalisch Chemisches Institut / Theoretische Chemie Universität Heidelberg INF 229 69120 Heidelberg e-mail: [EMAIL PROTECTED] - To unsubscribe from this list: send the line

Re: swapper: page allocation failure. order:1, mode:0x20

Hello Benjamin, On Monday 28 February 2005 16:23, Benjamin L. Shi wrote: We've seen these, by adding the following tueables resolved the problem. More specifically, the lower zone protection made the difference. vm.vfs_cache_pressure=1000 vm.lower_zone_protection=100 vm.max_map_count =

x86_64: 32bit emulation problems

Hi, I'm just looking into a very strange problem. Some of our systems have athlon64 CPUs. Due to our diskless nfs environment we currently still prefer a 32bit userspace environment, but would like to be able to use a 64-bit chroot environment. Well, currently there seems to be a stat64()

Re: x86_64: 32bit emulation problems

As usual we are using unfs3 for /etc and /var, but for me that looks like a client problem. I'm even not sure if this is limited to NFS at all. Sorry, that was easy to test, of course. This problem doesn't seem to exist on a local disk. - To unsubscribe from this list: send the line

Re: x86_64: 32bit emulation problems

and see what value err gets assigned. I cannot see any kernel problem. The err value will become -1 here. Trond Myklebust already suggested to look at the results of errno: On Tuesday 01 March 2005 00:43, Bernd Schubert wrote: On Monday 28 February 2005 23:26, you wrote: Given that strace

Re: x86_64: 32bit emulation problems

://www.pci.uni-heidelberg.de/tc/usr/bernd/downloads/nfs-stat/ Cheers, Bernd -- Bernd Schubert Physikalisch Chemisches Institut / Theoretische Chemie Universität Heidelberg INF 229 69120 Heidelberg e-mail: [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel

Re: x86_64: 32bit emulation problems

On Tuesday 01 March 2005 23:10, Andreas Schwab wrote: Bernd Schubert [EMAIL PROTECTED] writes: It is most likely some kind of user space problem. I would change it to int err = stat(dir, buf); and then go through it with gdb and see what value err gets assigned. I cannot see any kernel

Re: x86_64: 32bit emulation problems

On Wednesday 02 March 2005 10:13, Trond Myklebust wrote: on den 02.03.2005 Klokka 09:18 (+0100) skreiv Andi Kleen: On Wed, Mar 02, 2005 at 12:46:23AM +0100, Andreas Schwab wrote: Bernd Schubert [EMAIL PROTECTED] writes: Hmm, after compiling with -D_FILE_OFFSET_BITS=64 it works fine

Re: x86_64: 32bit emulation problems

On Wednesday 02 March 2005 17:53, Trond Myklebust wrote: on den 02.03.2005 Klokka 12:33 (+0100) skreiv Bernd Schubert: I can see no good reason for truncating inode number values on platforms that actually do support 64-bit inode numbers, but I can see several Well, at least we would

[PATCH 2 1/2] coccicheck: Allow the user to give a V= (verbose) argument

Do not run with verbosity on/off depending on the ONLINE variable, which gets set with C=1 or C=2, but allow the user to set the verbosity using kernel default make V= paramemter. Verbosity is off by default now. Signed-off-by: Bernd Schubert bernd.schub...@itwm.fraunhofer.de CC: Julia Lawall

[PATCH 2 2/2] coccicheck: Allow to show the executed command line

On my system one of the tests failed with Fatal error: exception Failure(No OCaml compiler found! Install either ocamlopt or ocamlopt.opt). Investigating such issues is easier if the executed command line is being shown. Signed-off-by: Bernd Schubert bernd.schub...@itwm.fraunhofer.de CC: Julia

Re: [PATCH 1/2] coccicheck: Allow the user to give a VERBOSE= argument

Hello Nicolas, thanks for your review! Cheers, Bernd -- 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

[PATCH 1/2] coccicheck: Allow the user to give a VERBOSE= argument

Simply running make coccicheck returns very verbose output and warnings might not be noticed. Allow the user to set the verbosity level. Signed-off-by: Bernd Schubert bernd.schub...@itwm.fraunhofer.de CC: Julia Lawall julia.law...@lip6.fr CC: Nicolas Palix nicolas.pa...@imag.fr CC: co

[PATCH 2/2] coccicheck: Allow to show the executed command line

On my system one of the tests failed with Fatal error: exception Failure(No OCaml compiler found! Install either ocamlopt or ocamlopt.opt). Investigating such issues is easier if the executed command line is being shown. Signed-off-by: Bernd Schubert bernd.schub...@itwm.fraunhofer.de CC: Julia

Re: [PATCH 1/2] coccicheck: Allow the user to give a VERBOSE= argument

? Hmm, I probably should have told in the patch description that verbosity defaults to 0 now. Shall I revert or make an extra patch for that? With the current patch and ONLINE != 0 nothing will change. Cheers, Bernd Regards, On Tue, Jan 22, 2013 at 2:34 PM, Bernd Schubert bernd.schub

aic79xx oops

the system as it is without another reboot. Of course, we would also like to know the reason for the oops. Any help is appreciated. Thanks in advance, Bernd -- Bernd Schubert Physikalisch Chemisches Institut / Theoretische Chemie Universität Heidelberg INF 229 69120 Heidelberg e-mail

Re: [PATCH]:dir.c patch

On 08/25/2012 10:37 PM, Christopher Sacchi wrote: Here is a non-style issue dir.c-patch, and as far as I can see from the lines of code, the compilation errors weren't about what I put in. This patch fixes a break statement inside an if statement, as obviously not correct. Why should that not

Re: Performance problems with 3ware 9500S-4LP and 2.6.25-rc3

being down while rsync is running. do you have the write-back cache of the controller enabled for your disks? When you disable this cache, the controller will also disable the disks, cause a write-performance between 3 to 8MB/s per disks. Cheers, Bernd -- Bernd Schubert Q-Leap Networks GmbH

memory allocation: smap large Size, but unused

Hello, I'm just investigating why a user space program has a rather large VmSize, but small VmRSS size. Looking into /proc/$pid/smaps I notice several areas with an size of about 64MB, but otherwise that area is unused. So far I did not find a way how to reproduce that with malloc() calls.

Re: [regression] 3.7 ends in APIC panic

On 12/13/2012 01:16 PM, Bernd Schubert wrote: Hello, I just tried to boot 3.7 and it ends in an APIC panic. I tried to use the recommended apic=debug, but that does not change anything in the output, at least not in the visible part. The last known kernel to boot was 3.5. If it matters I can

Re: [regression] 3.7 ends in APIC panic

On 12/16/2012 12:35 PM, Ingo Molnar wrote: * Bernd Schubert bernd.schub...@itwm.fraunhofer.de wrote: On 12/13/2012 01:16 PM, Bernd Schubert wrote: Hello, I just tried to boot 3.7 and it ends in an APIC panic. I tried to use the recommended apic=debug, but that does not change anything

Re: [regression] 3.7 ends in APIC panic

On 12/16/2012 07:07 PM, Yinghai Lu wrote: On Sun, Dec 16, 2012 at 10:01 AM, Bernd Schubert bernd.schub...@itwm.fraunhofer.de wrote: can you post your .config for v3.7 ? wonder if you have x2apic in .config Which setting is it? Config is attached. your config does not have

Re: [regression] 3.7 ends in APIC panic

On 12/16/2012 08:13 PM, Borislav Petkov wrote: On Sun, Dec 16, 2012 at 07:28:59PM +0100, Bernd Schubert wrote: CONFIG_X86_X2APIC depends on CONFIG_IRQ_REMAP, which I disabled as it is marked as experimental... You shouldn't pay too much attention to CONFIG_EXPERIMENTAL because it is on its

Re: [regression] 3.7 ends in APIC panic

On 12/16/2012 07:07 PM, Yinghai Lu wrote: On Sun, Dec 16, 2012 at 10:01 AM, Bernd Schubert bernd.schub...@itwm.fraunhofer.de wrote: can you post your .config for v3.7 ? wonder if you have x2apic in .config Which setting is it? Config is attached. your config does not have

Re: [regression] 3.7 ends in APIC panic

On 12/16/2012 09:39 PM, Borislav Petkov wrote: On Sun, Dec 16, 2012 at 08:46:06PM +0100, Bernd Schubert wrote: Hmm, I read it the other way around - x2apic depends on interrupt remapping, but interrupt remapping can be used without x2apic. Ok, you're right. X2APIC should depend on IRQ_REMAP

Re: [regression] 3.7 ends in APIC panic

On 12/17/2012 11:00 AM, Borislav Petkov wrote: + Suresh. On Mon, Dec 17, 2012 at 10:34:46AM +0100, Bernd Schubert wrote: On 12/16/2012 09:39 PM, Borislav Petkov wrote: On Sun, Dec 16, 2012 at 08:46:06PM +0100, Bernd Schubert wrote: Hmm, I read it the other way around - x2apic depends

API changes / 2.6.21 sysctl changes

Hi, in 2.6.21 register_sysctl_table(), struct ctl_table and probably something else did change. Unfortunately so far I didn't figure out the something else. Please, if generic interface modifications render all available documentation in the web invalid, is it so hard to also write kernel

Re: API changes / 2.6.21 sysctl changes

On Monday 11 June 2007 17:46:27 Alexey Dobriyan wrote: On Mon, Jun 11, 2007 at 03:13:12PM +0200, Bernd Schubert wrote: in 2.6.21 register_sysctl_table(), struct ctl_table and probably something else did change. Unfortunately so far I didn't figure out the something else. Do you have

mkfs.ext2 triggered softlockup

Maybe you still remember my report about an mkfs.ext2 triggered ram disk corruption? http://lkml.org/lkml/2007/5/4/272 Well, in principle I'm now doing the same stuff, only this time with another initrd, which mounts the root-fs over nfs. [ 1596.928552] BUG: soft lockup detected on CPU#2! [

Re: mkfs.ext2 triggered softlockup

On Wednesday 16 May 2007 18:49:57 Michal Piotrowski wrote: Hi Bernd, On 16/05/07, Bernd Schubert [EMAIL PROTECTED] wrote: Maybe you still remember my report about an mkfs.ext2 triggered ram disk corruption? http://lkml.org/lkml/2007/5/4/272 Well, in principle I'm now doing the same

mkfs.ext2 triggerd RAM corruption

whats going on? Thanks, Bernd -- Bernd Schubert Q-Leap Networks GmbH - 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

Re: mkfs.ext2 triggerd RAM corruption

Theodore Tso wrote: On Fri, May 04, 2007 at 04:59:51PM +0200, Bernd Schubert wrote: I'm presently rather puzzled, if this is really a kernel bug, its a big bug. Summary: The system ramdisk (initrd) gets corrupted while running mkfs.ext2 on a local sata disk partition. What

Re: mkfs.ext2 triggerd RAM corruption

Jan-Benedict Glaw wrote: On Fri, 2007-05-04 16:59:51 +0200, Bernd Schubert [EMAIL PROTECTED] wrote: To see whats going on, I copied the entire / (so the initrd) into a tmpfs root, chrooted into it, also bind mounted the main / into this chroot and compared several times /bin of chroot/bin

Re: mkfs.ext2 triggerd RAM corruption

On Sat, May 05, 2007 at 09:12:02PM +0200, Jan Engelhardt wrote: On May 5 2007 14:57, Theodore Tso wrote: On Sat, May 05, 2007 at 03:36:37AM +0200, Bernd Schubert wrote: distribution: modified debian sarge, in which aspect is the distribution important for this problem? mkfs2.ext2

Re: mkfs.ext2 triggerd RAM corruption

On Sat, May 05, 2007 at 02:57:35PM -0400, Theodore Tso wrote: On Sat, May 05, 2007 at 03:36:37AM +0200, Bernd Schubert wrote: distribution: modified debian sarge, in which aspect is the distribution important for this problem? mkfs2.ext2 is supposed to write to /dev/sdaX and not /dev/rd/0

Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition

Hi Nick, On 07/29/2013 12:10 PM, Nick Alcock wrote: My server's ARC-1210 has been working fine for years, but when I upgraded from 3.10.1, it started failing: Instead of [0.784044] Areca RAID Controller0: F/W V1.46 2009-01-06 Model ARC-1210 [0.804028] scsi0 : Areca SATA Host Adapter

Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition

On 07/29/2013 03:05 PM, Nix wrote: On 29 Jul 2013, Bernd Schubert said: Hi Nick, On 07/29/2013 12:10 PM, Nick Alcock wrote: arcmsr0: abort device command of scsi id = 0 lun = 1 arcmsr0: abort device command of scsi id = 0 lun = 0 arcmsr: executing bus reset eh.num_resets=0, num_

Re: [PATCH] scsi disk: Use its own buffer for the vpd request

Martin, sorry for my late reply, I entirely lost track of this (customer issues, vacation, lots of main work, ...). On 08/02/2013 05:00 AM, Martin K. Petersen wrote: Bernd == Bernd Schubert bernd.schub...@fastmail.fm writes: Bernd, Bernd Once I noticed that scsi_get_vpd_page() works fine

Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition

On 07/30/2013 01:34 AM, Martin K. Petersen wrote: Nix == Nix n...@esperi.org.uk writes: Bernd, Nix I can now confirm that reverting this commit causes this problem to Nix go away, and my machine boots fine again. Can you please send me the output of sq_inq with your 1.49 firmware? I made a

Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition

On 07/30/2013 02:56 AM, Nix wrote: On 30 Jul 2013, Douglas Gilbert outgrape: Please supply the information that Martin Petersen asked for. Did it in private IRC (the advantage of working for the same division of the same company!) I didn't realise the original fix was actually implemented

Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition

On 07/31/2013 05:15 AM, Martin K. Petersen wrote: Bernd == Bernd Schubert bernd.schub...@fastmail.fm writes: Bernd, Product revision level: R001 It's clearly not verbatim passthrough... Bernd Besides the firmware, the difference might be that I'm exporting Bernd single disks without

[PATCH] scsi disk: Use its own buffer for the vpd request

Once I noticed that scsi_get_vpd_page() works fine from other function calls and that it is not 0x89, but already 0x0 that fails fixing it became easy. Nix, any chance you could verify it also works for you? From: Bernd Schubert bernd.schub...@itwm.fraunhofer.de Somehow older areca firmware

Re: [PATCH] scsi disk: Use its own buffer for the vpd request

Whoops, the title is wrong, it should have been: [PATCH] scsi disk: Limit get_vpd_page buf size On 08/01/2013 04:34 PM, Bernd Schubert wrote: Once I noticed that scsi_get_vpd_page() works fine from other function calls and that it is not 0x89, but already 0x0 that fails fixing it became easy

Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition

On 07/30/2013 11:20 PM, Nix wrote: On 30 Jul 2013, Bernd Schubert told this: On 07/30/2013 02:56 AM, Nix wrote: On 30 Jul 2013, Douglas Gilbert outgrape: Please supply the information that Martin Petersen asked for. Did it in private IRC (the advantage of working for the same division

Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition

On 08/01/2013 06:04 PM, Nix wrote: On 1 Aug 2013, Bernd Schubert verbalised: On 07/30/2013 11:20 PM, Nix wrote: On 30 Jul 2013, Bernd Schubert told this: On 07/30/2013 02:56 AM, Nix wrote: On 30 Jul 2013, Douglas Gilbert outgrape: Please supply the information that Martin Petersen asked

Re: [PATCH 02/11][SCSI]mpt2sas: Added new driver module Parameter disable_eedp to Disable EEDP Support

u8 scsi_io_cb_idx; diff --git a/drivers/scsi/mpt2sas/mpt2sas_scsih.c b/drivers/scsi/mpt2sas/mpt2sas_scsih.c index 7f0af4f..d502728 100644 --- a/drivers/scsi/mpt2sas/mpt2sas_scsih.c +++ b/drivers/scsi/mpt2sas/mpt2sas_scsih.c @@ -127,6 +127,11 @@ static int disable_discovery =

Re: Subject: [v3.8][v3.11][Regression] [SCSI] sd: Update WRITE SAME heuristics

Hello Joseph, On 10/29/2013 08:21 PM, Joseph Salisbury wrote: Hi Martin, A bug was opened against the Ubuntu kernel[0]. After a kernel bisect, it was found that reverting the following commit resolved this bug: commit 66c28f97120e8a621afd5aa7a31c4b85c547d33d Author: Martin K. Petersen

Re: [PATCH] scsi disk: Use its own buffer for the vpd request

On 08/31/2013 09:48 PM, Nix wrote: On 31 Aug 2013, Greg KH said: On Fri, Aug 30, 2013 at 11:01:56AM +0100, Nix wrote: On 1 Aug 2013, Bernd Schubert said: Once I noticed that scsi_get_vpd_page() works fine from other function calls and that it is not 0x89, but already 0x0 that fails fixing

Re: Drivers: scsi: FLUSH timeout

On 09/24/2013 02:35 PM, KY Srinivasan wrote: -Original Message- From: Jack Wang [mailto:xjtu...@gmail.com] Sent: Tuesday, September 24, 2013 5:08 AM To: KY Srinivasan Cc: Greg KH; linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; oher...@suse.com; jbottom...@parallels.com;

Re: [RFC] extending splice for copy offloading

On 09/30/2013 06:31 PM, Miklos Szeredi wrote: Here's an example cp app using direct splice (and without fallback to non-splice, which is obviously required unless the kernel is known to support direct splice). Untested, but trivial enough... The important part is, I think, that the app must

Re: [RFC] extending splice for copy offloading

On 09/30/2013 07:44 PM, Myklebust, Trond wrote: On Mon, 2013-09-30 at 19:17 +0200, Bernd Schubert wrote: It would be nice if there would be way if the file system would get a hint that the target file is supposed to be copy of another file. That way distributed file systems could also create

Re: [RFC] extending splice for copy offloading

On 09/30/2013 08:02 PM, Myklebust, Trond wrote: On Mon, 2013-09-30 at 19:48 +0200, Bernd Schubert wrote: On 09/30/2013 07:44 PM, Myklebust, Trond wrote: On Mon, 2013-09-30 at 19:17 +0200, Bernd Schubert wrote: It would be nice if there would be way if the file system would get a hint

Re: [RFC] extending splice for copy offloading

On 09/30/2013 09:34 PM, Myklebust, Trond wrote: On Mon, 2013-09-30 at 20:49 +0200, Bernd Schubert wrote: On 09/30/2013 08:02 PM, Myklebust, Trond wrote: On Mon, 2013-09-30 at 19:48 +0200, Bernd Schubert wrote: On 09/30/2013 07:44 PM, Myklebust, Trond wrote: On Mon, 2013-09-30 at 19:17 +0200

Re: [PATCH] sysctl: Add a feature to drop caches selectively

On 06/26/2014 08:13 AM, Artem Bityutskiy wrote: On Thu, 2014-06-26 at 11:06 +1000, Dave Chinner wrote: Your particular use case can be handled by directing your benchmark at a filesystem mount point and unmounting the filesystem in between benchmark runs. There is no ned to adding kernel

Re: [PATCH] sysctl: Add a feature to drop caches selectively

On 06/26/2014 01:57 PM, Lukáš Czerner wrote: On Thu, 26 Jun 2014, Artem Bityutskiy wrote: On Thu, 2014-06-26 at 12:36 +0200, Bernd Schubert wrote: On 06/26/2014 08:13 AM, Artem Bityutskiy wrote: On Thu, 2014-06-26 at 11:06 +1000, Dave Chinner wrote: Your particular use case can be handled

Re: [PATCH] sysctl: Add a feature to drop caches selectively

On 06/27/2014 04:55 AM, Dave Chinner wrote: On Thu, Jun 26, 2014 at 02:10:28PM +0200, Bernd Schubert wrote: On 06/26/2014 01:57 PM, Lukáš Czerner wrote: On Thu, 26 Jun 2014, Artem Bityutskiy wrote: On Thu, 2014-06-26 at 12:36 +0200, Bernd Schubert wrote: On 06/26/2014 08:13 AM, Artem

kmemleak or crc32_le bug?

I'm frequently getting UG: unable to handle kernel paging request at 880f87550dc0 IP: [813016d0] crc32_le+0x30/0x110 called from kmemleak, see bottom of the message. schubert@wheezy@fsdevel2 linux-stableaddr2line -e vmlinux -i -a 813016d0 0x813016d0

Re: [PATCH v4] fuse: Add support for passthrough read/write

On 01/21/2016 01:16 AM, Nikhilesh Reddy wrote: > Add support for filesystem passthrough read/write of files > when enabled in userspace through the option FUSE_PASSTHROUGH. > > There are many FUSE based filesystems that perform checks or > enforce policy or perform some kind of decision making

Re: md: Combine two kmalloc() calls into one in sb_equal()

On 09.12.2016 22:58, SF Markus Elfring wrote: Irrelevant, the variable is not used before checking it. * Will it be more appropriate to attempt another memory allocation only if the previous one succeeded already? * Can it be a bit more efficient to duplicate only the required data in a

Re: [PATCH] md: Combine two kmalloc() calls into one in sb_equal()

On 09.12.2016 19:30, SF Markus Elfring wrote: From: Markus Elfring Date: Fri, 9 Dec 2016 19:09:13 +0100 The function "kmalloc" was called in one case by the function "sb_equal" without checking immediately if it failed. Err, your patch actually *replaces* the

Re: md: Combine two kmalloc() calls into one in sb_equal()

On 09.12.2016 20:54, SF Markus Elfring wrote: So where did you get the idea from that it is not checked immediately? Is another variable assignment performed so far before the return value is checked from a previous function call? Irrelevant, the variable is not used before checking it.

Re: CDR read problems with 2.6.11?

[...] > > [EMAIL PROTECTED]:~[1009]# mount /mnt/cdrom > mount: wrong fs type, bad option, bad superblock on /dev/cdrom, >missing codepage or other error >In some cases useful info is found in syslog - try >dmesg | tail or so > [...] > The drive is a NEC DVD+RW

2.6.11.12: oops + panic

04 00 02 20 00 2b 4b 0c c7 03 00 01 10 00 -- Bernd Schubert PCI / Theoretische Chemie Universität Heidelberg INF 229 69120 Heidelberg e-mail: [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Mor

Re: Problem with kernel 2.6.11

ow and maybe I'm interpreting it wrong, but I think you should use strace -f ... > rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0 > --- SIGCHLD (Child exited) @ 0 (0) --- Same here. Cheers, Bernd -- Bernd Schubert PCI / Theoretische Chemie Universität Heidelberg INF 229 69120 He

swapper: page allocation failure. order:1, mode:0x20

:{ret_from_intr+0} {default_idle+0} Feb 28 10:07:36 hitchcock kernel:{default_idle+36} {cpu_idle+39} -- Bernd Schubert Physikalisch Chemisches Institut / Theoretische Chemie Universität Heidelberg INF 229 69120 Heidelberg e-mail: [EMAIL PROTECTED] - To unsubscribe from this list: send

Re: swapper: page allocation failure. order:1, mode:0x20

Hello Benjamin, On Monday 28 February 2005 16:23, Benjamin L. Shi wrote: > We've seen these, by adding the following tueables resolved the problem. > More specifically, the lower zone protection made the difference. > > vm.vfs_cache_pressure=1000 > vm.lower_zone_protection=100 > vm.max_map_count

x86_64: 32bit emulation problems

Hi, I'm just looking into a very strange problem. Some of our systems have athlon64 CPUs. Due to our diskless nfs environment we currently still prefer a 32bit userspace environment, but would like to be able to use a 64-bit chroot environment. Well, currently there seems to be a stat64()

Re: x86_64: 32bit emulation problems

> As usual we are using unfs3 for /etc and /var, but for me that looks like a > client problem. I'm even not sure if this is limited to NFS at all. Sorry, that was easy to test, of course. This problem doesn't seem to exist on a local disk. - To unsubscribe from this list: send the line

Re: x86_64: 32bit emulation problems

with gdb and see what value err gets assigned. > > I cannot see any kernel problem. The err value will become -1 here. Trond Myklebust already suggested to look at the results of errno: On Tuesday 01 March 2005 00:43, Bernd Schubert wrote: > On Monday 28 February 2005 23:26, yo

Re: x86_64: 32bit emulation problems

data so far doesn't support this assertion. I have to admit that knfsd-mount moints are not affected, but on the other hand, I really cant't see anything in the ethereal captures. If someone should be interested, I have uploaded them: http://www.pci.uni-heidelberg.de/tc/usr/bernd/downloads/nfs-s

Re: x86_64: 32bit emulation problems

On Tuesday 01 March 2005 23:10, Andreas Schwab wrote: > Bernd Schubert <[EMAIL PROTECTED]> writes: > >> It is most likely some kind of user space problem. I would change > >> it to int err = stat(dir, ); > >> and then go through it with gdb and see what value e

Re: x86_64: 32bit emulation problems

On Wednesday 02 March 2005 10:13, Trond Myklebust wrote: > on den 02.03.2005 Klokka 09:18 (+0100) skreiv Andi Kleen: > > On Wed, Mar 02, 2005 at 12:46:23AM +0100, Andreas Schwab wrote: > > > Bernd Schubert <[EMAIL PROTECTED]> writes: > > > > Hmm, after c

Re: x86_64: 32bit emulation problems

On Wednesday 02 March 2005 17:53, Trond Myklebust wrote: > on den 02.03.2005 Klokka 12:33 (+0100) skreiv Bernd Schubert: > > > I can see no good reason for truncating inode number values on > > > platforms that actually do support 64-bit inode numbers, but I can see >

Re: x86_64: 32bit emulation problems

On Thursday 03 March 2005 10:19, Andi Kleen wrote: > On Wed, Mar 02, 2005 at 08:53:07AM -0800, Trond Myklebust wrote: > > on den 02.03.2005 Klokka 12:33 (+0100) skreiv Bernd Schubert: > > > > I can see no good reason for truncating inode number values on > > > > p

Re: 2.6.12.3 network slowdown?

vers for this family of NICs. > No, AFAIK the rewritten driver is only in 2.6.13-rc or 2.6.12-mm (also already in previous -mm kernel versions). Bernd -- Bernd Schubert Physikalisch Chemisches Institut / Theoretische Chemie Universität Heidelberg INF 229 69120 Heidelberg e-mail: [EMAIL PRO

  1   2   >