Re: How is an OS bound to the Linux kernel

Am Sonntag, 29. Juni 2014, 11:54:32 schrieb Gideon D'souza: > hey guys, Hi Gideon, > I generally manage to understand the various pieces of the linux > kernel and what their functions are. > > However, one thing I don't fully understand is how is any OS, say > fedora (which is what I use) is

Re: How is an OS bound to the Linux kernel

Am Sonntag, 29. Juni 2014, 11:54:32 schrieb Gideon D'souza: hey guys, Hi Gideon, I generally manage to understand the various pieces of the linux kernel and what their functions are. However, one thing I don't fully understand is how is any OS, say fedora (which is what I use) is bound to

Re: 3.16, i915: less colors in X?

Am Samstag, 21. Juni 2014, 22:29:01 schrieb Pavel Machek: > Hi! > > I just test-booted 3.16-rc1, and background in X looked just wrong -- > very noticeable bands on the background gradient. I thought that maybe > it is just my eyes, but I went back to older kernel, and background is > ok now. >

Re: 3.16, i915: less colors in X?

Am Samstag, 21. Juni 2014, 22:29:01 schrieb Pavel Machek: Hi! I just test-booted 3.16-rc1, and background in X looked just wrong -- very noticeable bands on the background gradient. I thought that maybe it is just my eyes, but I went back to older kernel, and background is ok now. I'm

Re: How to disable Lazy Preempt in the kernel

Am Donnerstag, 19. Juni 2014, 08:11:21 schrieb tdjames: > I'm relatively new to Linux and working on getting a real-time kernel up and > running for robot applications. I'm on Ubuntu 14.04, using kernel 3.14.3 > and the 3.14.3-rt5 real-time patch. Also using x86-64. I don´t know about lazy

Re: How to disable Lazy Preempt in the kernel

Am Donnerstag, 19. Juni 2014, 08:11:21 schrieb tdjames: I'm relatively new to Linux and working on getting a real-time kernel up and running for robot applications. I'm on Ubuntu 14.04, using kernel 3.14.3 and the 3.14.3-rt5 real-time patch. Also using x86-64. I don´t know about lazy preempt,

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

n > > --Dirk > > On 06/09/2014 02:33 PM, Martin Steigerwald wrote: > > Hi! > > > > Added linux-pm to Cc. Also reboots seems to fix up the condition: > > > > merkaba:~> grep . /sys/devices/system/cpu/cpu[0-3]/cpufreq/cpuinfo_cur_freq > > /sys/dev

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Should I hit throttling temperatures I will try to capture this output once more. Thanks, Martin > > --Dirk > > On 06/09/2014 02:33 PM, Martin Steigerwald wrote: > > Hi! > > > > Added linux-pm to Cc. Also reboots seems to fix up the condition: > > >

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

to capture this output once more. Thanks, Martin --Dirk On 06/09/2014 02:33 PM, Martin Steigerwald wrote: Hi! Added linux-pm to Cc. Also reboots seems to fix up the condition: merkaba:~ grep . /sys/devices/system/cpu/cpu[0-3]/cpufreq/cpuinfo_cur_freq /sys/devices/system/cpu/cpu0

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

there is quite some CPU activity for a while. But way better than before. I can test whether this also happens with ACPI cpufreq driver. I think I didn´t see this with 3.14. Am Montag, 9. Juni 2014, 23:24:54 schrieb Martin Steigerwald: Hi! I get: Jun 9 22:41:32 merkaba kernel

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Am Montag, 9. Juni 2014, 15:44:02 schrieb Dirk Brandewie: > On 06/09/2014 03:02 PM, Martin Steigerwald wrote: > > Am Montag, 9. Juni 2014, 23:41:40 schrieb Martin Steigerwald: > >> Am Montag, 9. Juni 2014, 23:33:43 schrieb Martin Steigerwald: > >>> Hi! > >

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Am Dienstag, 10. Juni 2014, 00:29:52 schrieb Rafael J. Wysocki: > On Tuesday, June 10, 2014 12:20:20 AM Rafael J. Wysocki wrote: > > On Monday, June 09, 2014 11:41:40 PM Martin Steigerwald wrote: > > > Am Montag, 9. Juni 2014, 23:33:43 schrieb Martin Steigerwald: > > > &

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Am Dienstag, 10. Juni 2014, 00:29:52 schrieb Rafael J. Wysocki: On Tuesday, June 10, 2014 12:20:20 AM Rafael J. Wysocki wrote: On Monday, June 09, 2014 11:41:40 PM Martin Steigerwald wrote: Am Montag, 9. Juni 2014, 23:33:43 schrieb Martin Steigerwald: Hi! Added linux-pm to Cc

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Am Montag, 9. Juni 2014, 15:44:02 schrieb Dirk Brandewie: On 06/09/2014 03:02 PM, Martin Steigerwald wrote: Am Montag, 9. Juni 2014, 23:41:40 schrieb Martin Steigerwald: Am Montag, 9. Juni 2014, 23:33:43 schrieb Martin Steigerwald: Hi! Added linux-pm to Cc. Also reboots seems to fix up

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Am Dienstag, 10. Juni 2014, 00:20:20 schrieb Rafael J. Wysocki: > On Monday, June 09, 2014 11:41:40 PM Martin Steigerwald wrote: > > Am Montag, 9. Juni 2014, 23:33:43 schrieb Martin Steigerwald: > > > Hi! > > > > > > Added linux-pm to Cc. Also r

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Am Montag, 9. Juni 2014, 23:41:40 schrieb Martin Steigerwald: > Am Montag, 9. Juni 2014, 23:33:43 schrieb Martin Steigerwald: > > Hi! > > > > Added linux-pm to Cc. Also reboots seems to fix up the condition: > > > > merkaba:~> grep . /sys/devices/system/c

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Am Montag, 9. Juni 2014, 23:33:43 schrieb Martin Steigerwald: > Hi! > > Added linux-pm to Cc. Also reboots seems to fix up the condition: > > merkaba:~> grep . /sys/devices/system/cpu/cpu[0-3]/cpufreq/cpuinfo_cur_freq > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

ession there is quite some CPU activity for a while. But way better than before. I can test whether this also happens with ACPI cpufreq driver. I think I didn´t see this with 3.14. Am Montag, 9. Juni 2014, 23:24:54 schrieb Martin Steigerwald: > Hi! > > I get: > > Jun 9 22

[REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Hi! I get: Jun 9 22:41:32 merkaba kernel: [39978.006479] CPU0: Package temperature/speed normal Jun 9 22:41:32 merkaba kernel: [39978.006481] CPU3: Package temperature/speed normal Jun 9 22:41:32 merkaba kernel: [39978.006482] CPU2: Package temperature/speed normal Jun 9 22:41:32 merkaba

[REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Hi! I get: Jun 9 22:41:32 merkaba kernel: [39978.006479] CPU0: Package temperature/speed normal Jun 9 22:41:32 merkaba kernel: [39978.006481] CPU3: Package temperature/speed normal Jun 9 22:41:32 merkaba kernel: [39978.006482] CPU2: Package temperature/speed normal Jun 9 22:41:32 merkaba

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

there is quite some CPU activity for a while. But way better than before. I can test whether this also happens with ACPI cpufreq driver. I think I didn´t see this with 3.14. Am Montag, 9. Juni 2014, 23:24:54 schrieb Martin Steigerwald: Hi! I get: Jun 9 22:41:32 merkaba kernel: [39978.006479

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Am Montag, 9. Juni 2014, 23:33:43 schrieb Martin Steigerwald: Hi! Added linux-pm to Cc. Also reboots seems to fix up the condition: merkaba:~ grep . /sys/devices/system/cpu/cpu[0-3]/cpufreq/cpuinfo_cur_freq /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:830957 /sys/devices/system

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Am Montag, 9. Juni 2014, 23:41:40 schrieb Martin Steigerwald: Am Montag, 9. Juni 2014, 23:33:43 schrieb Martin Steigerwald: Hi! Added linux-pm to Cc. Also reboots seems to fix up the condition: merkaba:~ grep . /sys/devices/system/cpu/cpu[0-3]/cpufreq/cpuinfo_cur_freq /sys/devices

Re: [REGRESSION] 3.15: Seems to turbo mode Intel Sandybridge Dual Core without need, overheating CPU

Am Dienstag, 10. Juni 2014, 00:20:20 schrieb Rafael J. Wysocki: On Monday, June 09, 2014 11:41:40 PM Martin Steigerwald wrote: Am Montag, 9. Juni 2014, 23:33:43 schrieb Martin Steigerwald: Hi! Added linux-pm to Cc. Also reboots seems to fix up the condition: merkaba:~ grep

Re: [RFC] Tux3 for review

Hi Daniel! Am Freitag, 16. Mai 2014, 17:50:59 schrieb Daniel Phillips: > We would like to offer Tux3 for review for mainline merge. We have > prepared a new repository suitable for pulling: At long last! Congrats for arriving at this point. Ciao, -- Martin 'Helios' Steigerwald -

Re: [RFC] Tux3 for review

Hi Daniel! Am Freitag, 16. Mai 2014, 17:50:59 schrieb Daniel Phillips: We would like to offer Tux3 for review for mainline merge. We have prepared a new repository suitable for pulling: At long last! Congrats for arriving at this point. Ciao, -- Martin 'Helios' Steigerwald -

Re: 3.13 <= rc6. Using USB 2.0 devices is braking the system when using "threadirqs" kernel option

Am Dienstag, 31. Dezember 2013, 20:13:04 schrieb Vi0L0: > Hi, Hi, > as said the problem does not occur when not using "threadirqs" kernel > option. Ah, thats interesting. I found SD cards via internal MMC card reader in ThinkPad T520 to be broken with "threadirqs" on when writing files,

Re: 3.13 = rc6. Using USB 2.0 devices is braking the system when using threadirqs kernel option

Am Dienstag, 31. Dezember 2013, 20:13:04 schrieb Vi0L0: Hi, Hi, as said the problem does not occur when not using threadirqs kernel option. Ah, thats interesting. I found SD cards via internal MMC card reader in ThinkPad T520 to be broken with threadirqs on when writing files, freezes

Re: [REGRESSION] 3.13-rc2: locks up hard on trying to transfer a file to mmc based internal SD card slot [FOUND]

Am Dienstag, 31. Dezember 2013, 13:52:05 schrieb Martin Steigerwald: > Am Dienstag, 31. Dezember 2013, 13:41:22 schrieb Martin Steigerwald: > > Am Samstag, 30. November 2013, 14:53:51 schrieb Martin Steigerwald: > > > Just added linux-mmc. And I might git-bisect that at s

Re: [REGRESSION] 3.13-rc2: locks up hard on trying to transfer a file to mmc based internal SD card slot

Am Samstag, 30. November 2013, 14:53:51 schrieb Martin Steigerwald: > Just added linux-mmc. And I might git-bisect that at some time, but I do not > intend to do it during my precious weekend. The chances of me bisecting it > increase with workable suggestions on how to cut down t

Re: [REGRESSION] 3.13-rc2: locks up hard on trying to transfer a file to mmc based internal SD card slot

Am Samstag, 30. November 2013, 14:53:51 schrieb Martin Steigerwald: Just added linux-mmc. And I might git-bisect that at some time, but I do not intend to do it during my precious weekend. The chances of me bisecting it increase with workable suggestions on how to cut down the amount

Re: [REGRESSION] 3.13-rc2: locks up hard on trying to transfer a file to mmc based internal SD card slot [FOUND]

Am Dienstag, 31. Dezember 2013, 13:52:05 schrieb Martin Steigerwald: Am Dienstag, 31. Dezember 2013, 13:41:22 schrieb Martin Steigerwald: Am Samstag, 30. November 2013, 14:53:51 schrieb Martin Steigerwald: Just added linux-mmc. And I might git-bisect that at some time, but I do not intend

[REGRESSION] 3.13-rc2: locks up hard on trying to transfer a file to mmc based internal SD card slot

Just added linux-mmc. And I might git-bisect that at some time, but I do not intend to do it during my precious weekend. The chances of me bisecting it increase with workable suggestions on how to cut down the amount of iterations needed and avoid testing highly experimental between 3.12 and

[REGRESSION] 3.13-rc2: locks up hard on trying to transfer a file to mmc based internal SD card slot

Hi! Just does that on a ThinkPad T520 with: merkaba:~> lspci -nn | grep MMC 0d:00.0 System peripheral [0880]: Ricoh Co Ltd PCIe SDXC/MMC Host Controller [1180:e823] (rev 08) Mouse pointer freezes, no Ctrl-Alt-F1. merkaba:~> fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 31.4 GB, 31439454208 bytes

[REGRESSION] 3.13-rc2: locks up hard on trying to transfer a file to mmc based internal SD card slot

Hi! Just does that on a ThinkPad T520 with: merkaba:~ lspci -nn | grep MMC 0d:00.0 System peripheral [0880]: Ricoh Co Ltd PCIe SDXC/MMC Host Controller [1180:e823] (rev 08) Mouse pointer freezes, no Ctrl-Alt-F1. merkaba:~ fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 31.4 GB, 31439454208 bytes

[REGRESSION] 3.13-rc2: locks up hard on trying to transfer a file to mmc based internal SD card slot

Just added linux-mmc. And I might git-bisect that at some time, but I do not intend to do it during my precious weekend. The chances of me bisecting it increase with workable suggestions on how to cut down the amount of iterations needed and avoid testing highly experimental between 3.12 and

Re: Linux 3.11-rc2 (acpi backlight, revert)

Am Freitag, 26. Juli 2013, 14:40:58 schrieb Rafael J. Wysocki: > On Friday, July 26, 2013 02:09:08 PM Martin Steigerwald wrote: > > Am Donnerstag, 25. Juli 2013, 15:00:26 schrieb Rafael J. Wysocki: > > > On Monday, July 22, 2013 09:54:21 PM Rafael J. Wysocki wrote: > > >

Re: Linux 3.11-rc2 (acpi backlight, revert)

Am Freitag, 26. Juli 2013, 14:40:58 schrieb Rafael J. Wysocki: On Friday, July 26, 2013 02:09:08 PM Martin Steigerwald wrote: Am Donnerstag, 25. Juli 2013, 15:00:26 schrieb Rafael J. Wysocki: On Monday, July 22, 2013 09:54:21 PM Rafael J. Wysocki wrote: On Monday, July 22, 2013 11:11:54

Re: Linux 3.11-rc2 (acpi backlight, revert)

Am Donnerstag, 25. Juli 2013, 15:00:26 schrieb Rafael J. Wysocki: > On Monday, July 22, 2013 09:54:21 PM Rafael J. Wysocki wrote: > > On Monday, July 22, 2013 11:11:54 AM Linus Torvalds wrote: > > > On Mon, Jul 22, 2013 at 6:02 AM, Rafael J. Wysocki wrote: > > > > Linus, do you want me to send a

Re: Linux 3.11-rc2 (acpi backlight, revert)

Am Donnerstag, 25. Juli 2013, 15:00:26 schrieb Rafael J. Wysocki: On Monday, July 22, 2013 09:54:21 PM Rafael J. Wysocki wrote: On Monday, July 22, 2013 11:11:54 AM Linus Torvalds wrote: On Mon, Jul 22, 2013 at 6:02 AM, Rafael J. Wysocki r...@sisk.pl wrote: Linus, do you want me to send

Re: Linux 3.11-rc2

Am Montag, 22. Juli 2013, 15:37:42 schrieb Rafael J. Wysocki: > On Monday, July 22, 2013 03:15:38 PM Martin Steigerwald wrote: > > Am Montag, 22. Juli 2013, 15:02:22 schrieb Rafael J. Wysocki: > > > On Monday, July 22, 2013 12:08:40 AM James Hogan wrote: > > > >

Re: Linux 3.11-rc2

Am Montag, 22. Juli 2013, 15:02:22 schrieb Rafael J. Wysocki: > On Monday, July 22, 2013 12:08:40 AM James Hogan wrote: > > On 21 July 2013 20:53, Linus Torvalds wrote: > > > (b) we had a late change to how ACPI backlight handling is done on > > > > > > certain machines, and while this kind of

Re: Linux 3.11-rc2

Am Montag, 22. Juli 2013, 15:02:22 schrieb Rafael J. Wysocki: On Monday, July 22, 2013 12:08:40 AM James Hogan wrote: On 21 July 2013 20:53, Linus Torvalds torva...@linux-foundation.org wrote: (b) we had a late change to how ACPI backlight handling is done on certain machines, and

Re: Linux 3.11-rc2

Am Montag, 22. Juli 2013, 15:37:42 schrieb Rafael J. Wysocki: On Monday, July 22, 2013 03:15:38 PM Martin Steigerwald wrote: Am Montag, 22. Juli 2013, 15:02:22 schrieb Rafael J. Wysocki: On Monday, July 22, 2013 12:08:40 AM James Hogan wrote: On 21 July 2013 20:53, Linus Torvalds torva

Re: mistakes in code vs. maintainer flow mistakes (was: [ 00/19] 3.10.1-stable review)

Am Freitag, 19. Juli 2013, 12:01:27 schrieb Sarah Sharp: > On Fri, Jul 19, 2013 at 11:22:56AM +0200, Ingo Molnar wrote: > > * Sarah Sharp wrote: […] > "Respect" means different things to different people. Here's a list of > potentially disrespectful behaviors: > > * cussing > * belittling

Re: mistakes in code vs. maintainer flow mistakes (was: [ 00/19] 3.10.1-stable review)

Am Freitag, 19. Juli 2013, 12:01:27 schrieb Sarah Sharp: On Fri, Jul 19, 2013 at 11:22:56AM +0200, Ingo Molnar wrote: * Sarah Sharp sarah.a.sh...@linux.intel.com wrote: […] Respect means different things to different people. Here's a list of potentially disrespectful behaviors: * cussing

Re: zswap: How to determine whether it is compressing swap pages?

Am Mittwoch, 17. Juli 2013, 09:38:34 schrieb Seth Jennings: > On Wed, Jul 17, 2013 at 01:41:44PM +0200, Martin Steigerwald wrote: > > Is there any way to run zcache concurrently with zswap? I.e. use zcache only > > for read caches for filesystem and zswap for swap? &g

Re: zswap: How to determine whether it is compressing swap pages?

Am Mittwoch, 17. Juli 2013, 18:42:18 schrieb Bob Liu: > On 07/17/2013 06:04 PM, Martin Steigerwald wrote: > > Hi Seth, hi everyone, > > > > Yesterday I build 3.11-rc1 with CONFIG_ZSWAP and wanted to test it. > > > > I added zswap.enabled=1 and get: > > &

zswap: How to determine whether it is compressing swap pages?

Hi Seth, hi everyone, Yesterday I build 3.11-rc1 with CONFIG_ZSWAP and wanted to test it. I added zswap.enabled=1 and get: martin@merkaba:~> dmesg | grep zswap [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.11.0-rc1-tp520+ root=/dev/mapper/merkaba-debian ro rootflags=subvol=root

zswap: How to determine whether it is compressing swap pages?

Hi Seth, hi everyone, Yesterday I build 3.11-rc1 with CONFIG_ZSWAP and wanted to test it. I added zswap.enabled=1 and get: martin@merkaba:~ dmesg | grep zswap [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.11.0-rc1-tp520+ root=/dev/mapper/merkaba-debian ro rootflags=subvol=root

Re: zswap: How to determine whether it is compressing swap pages?

Am Mittwoch, 17. Juli 2013, 18:42:18 schrieb Bob Liu: On 07/17/2013 06:04 PM, Martin Steigerwald wrote: Hi Seth, hi everyone, Yesterday I build 3.11-rc1 with CONFIG_ZSWAP and wanted to test it. I added zswap.enabled=1 and get: martin@merkaba:~ dmesg | grep zswap [0.00

Re: zswap: How to determine whether it is compressing swap pages?

Am Mittwoch, 17. Juli 2013, 09:38:34 schrieb Seth Jennings: On Wed, Jul 17, 2013 at 01:41:44PM +0200, Martin Steigerwald wrote: Is there any way to run zcache concurrently with zswap? I.e. use zcache only for read caches for filesystem and zswap for swap? No, at least not with zcache's

Re: [ATTEND] How to act on LKML (was: [ 00/19] 3.10.1-stable review)

Am Montag, 15. Juli 2013, 15:50:03 schrieb Sarah Sharp: > On Mon, Jul 15, 2013 at 03:38:42PM -0700, Linus Torvalds wrote: > > On Mon, Jul 15, 2013 at 3:08 PM, Steven Rostedt > > wrote: > > > Can we please make this into a Kernel Summit discussion. I highly doubt > > > we would solve anything,

Re: [ATTEND] How to act on LKML (was: [ 00/19] 3.10.1-stable review)

Am Montag, 15. Juli 2013, 15:50:03 schrieb Sarah Sharp: On Mon, Jul 15, 2013 at 03:38:42PM -0700, Linus Torvalds wrote: On Mon, Jul 15, 2013 at 3:08 PM, Steven Rostedt rost...@goodmis.org wrote: Can we please make this into a Kernel Summit discussion. I highly doubt we would solve

Re: Linux 3.10-rc6

Am Sonntag, 16. Juni 2013, 08:09:03 schrieb Linus Torvalds: > On Sun, Jun 16, 2013 at 2:37 AM, Martin Steigerwald wrote: > > Do you really think your cursing controls how other people behave? > > Yes. In three ways: > > - I have magic mind-powers, and cursing rel

Re: Linux 3.10-rc6

Am Sonntag, 16. Juni 2013, 14:52:13 schrieb Linus Walleij: > On Sun, Jun 16, 2013 at 2:37 PM, Martin Steigerwald wrote: > > Am Samstag, 15. Juni 2013, 12:12:18 schrieb Linus Torvalds: > >> Another week, another rc. > >> > >> And I didn't even need to cu

Re: Linux 3.10-rc6

Linus, Am Samstag, 15. Juni 2013, 12:12:18 schrieb Linus Torvalds: > Another week, another rc. > > And I didn't even need to curse all that much at people. Sure, I > talked smack about some of your hamsters, and I declined a couple of > pull requests, but let's face it, it was pretty

Re: Linux 3.10-rc6

Linus, Am Samstag, 15. Juni 2013, 12:12:18 schrieb Linus Torvalds: Another week, another rc. And I didn't even need to curse all that much at people. Sure, I talked smack about some of your hamsters, and I declined a couple of pull requests, but let's face it, it was pretty halfhearted.

Re: Linux 3.10-rc6

Am Sonntag, 16. Juni 2013, 14:52:13 schrieb Linus Walleij: On Sun, Jun 16, 2013 at 2:37 PM, Martin Steigerwald mar...@lichtvoll.de wrote: Am Samstag, 15. Juni 2013, 12:12:18 schrieb Linus Torvalds: Another week, another rc. And I didn't even need to curse all that much at people. Sure

Re: Linux 3.10-rc6

Am Sonntag, 16. Juni 2013, 08:09:03 schrieb Linus Torvalds: On Sun, Jun 16, 2013 at 2:37 AM, Martin Steigerwald mar...@lichtvoll.de wrote: Do you really think your cursing controls how other people behave? Yes. In three ways: - I have magic mind-powers, and cursing releases them

Slow swap-in with SSD

pretty sure it was slow as well. But I had ZCACHE compiled in, as far as I guess from hints on the web, I bet its basically a no-op unless enabled with "zcache" kernel commandline parameter. Thanks, -- Martin Steigerwald - teamix GmbH - http://www.teamix.de gpg: 19E3 8D42 896F D004 08AC A0

Slow swap-in with SSD

as well. But I had ZCACHE compiled in, as far as I guess from hints on the web, I bet its basically a no-op unless enabled with zcache kernel commandline parameter. Thanks, -- Martin Steigerwald - teamix GmbH - http://www.teamix.de gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90

Re: [REGRESSION] fan always on with 3.10-rc2

Am Samstag, 8. Juni 2013, 22:34:44 schrieb Martin Steigerwald: > Am Freitag, 24. Mai 2013, 13:03:18 schrieb Martin Steigerwald: > > Hi! > > > > With 3.10-rc2 I see fan always or almost always on, even during extended > > periods of basically idling around. I d

Re: [REGRESSION] fan always on with 3.10-rc2

Am Samstag, 8. Juni 2013, 22:34:44 schrieb Martin Steigerwald: Am Freitag, 24. Mai 2013, 13:03:18 schrieb Martin Steigerwald: Hi! With 3.10-rc2 I see fan always or almost always on, even during extended periods of basically idling around. I did not notice this with 3.9

Re: [REGRESSION] fan always on with 3.10-rc2

Am Freitag, 24. Mai 2013, 13:03:18 schrieb Martin Steigerwald: > Hi! > > With 3.10-rc2 I see fan always or almost always on, even during extended > periods of basically idling around. I did not notice this with 3.9. This is > on an ThinkPad T520 with Intel Sandybridge i5-

Re: [REGRESSION] fan always on with 3.10-rc2

Am Freitag, 24. Mai 2013, 13:03:18 schrieb Martin Steigerwald: Hi! With 3.10-rc2 I see fan always or almost always on, even during extended periods of basically idling around. I did not notice this with 3.9. This is on an ThinkPad T520 with Intel Sandybridge i5-2520M dual core

[REGRESSION] fan always on with 3.10-rc2

Hi! With 3.10-rc2 I see fan always or almost always on, even during extended periods of basically idling around. I did not notice this with 3.9. This is on an ThinkPad T520 with Intel Sandybridge i5-2520M dual core with hyperthreading at regularily 2,5 GhZ and Intel graphics (no nvidia). I am

[REGRESSION] fan always on with 3.10-rc2

Hi! With 3.10-rc2 I see fan always or almost always on, even during extended periods of basically idling around. I did not notice this with 3.9. This is on an ThinkPad T520 with Intel Sandybridge i5-2520M dual core with hyperthreading at regularily 2,5 GhZ and Intel graphics (no nvidia). I am

Re: Tux3 Report: Initial fsck has landed

Am Mittwoch, 20. März 2013 schrieb David Lang: > On Wed, 20 Mar 2013, Martin Steigerwald wrote: > > Am Dienstag, 29. Januar 2013 schrieb Daniel Phillips: > >> On Mon, Jan 28, 2013 at 5:40 PM, Theodore Ts'o wrote: > >>> On Mon, Jan 28, 2013 at 04:20:11PM -0800, Darric

Re: Tux3 Report: Initial fsck has landed

Am Mittwoch, 20. März 2013 schrieb David Lang: On Wed, 20 Mar 2013, Martin Steigerwald wrote: Am Dienstag, 29. Januar 2013 schrieb Daniel Phillips: On Mon, Jan 28, 2013 at 5:40 PM, Theodore Ts'o ty...@mit.edu wrote: On Mon, Jan 28, 2013 at 04:20:11PM -0800, Darrick J. Wong wrote: On Mon

Re: Tux3 Report: Initial fsck has landed

Am Dienstag, 29. Januar 2013 schrieb Daniel Phillips: > On Mon, Jan 28, 2013 at 5:40 PM, Theodore Ts'o wrote: > > On Mon, Jan 28, 2013 at 04:20:11PM -0800, Darrick J. Wong wrote: > >> On Mon, Jan 28, 2013 at 03:27:38PM -0800, David Lang wrote: > >> > The situation I'm thinking of is when dealing

Re: Tux3 Report: Initial fsck has landed

Am Dienstag, 29. Januar 2013 schrieb Daniel Phillips: On Mon, Jan 28, 2013 at 5:40 PM, Theodore Ts'o ty...@mit.edu wrote: On Mon, Jan 28, 2013 at 04:20:11PM -0800, Darrick J. Wong wrote: On Mon, Jan 28, 2013 at 03:27:38PM -0800, David Lang wrote: The situation I'm thinking of is when

Re: btrfs crash when low on memory.

Am Mittwoch, 27. Februar 2013 schrieb Ahmet Inan: > > Yeah we have a lot of > > > > ptr = kmalloc(); > > BUG_ON(ptr); > > > > everywhere. I'll fix this one up but I really need to sit down and go > > through all of them and make sure we do the right thing in all these > > places. Thanks, > >

Re: btrfs crash when low on memory.

Am Mittwoch, 27. Februar 2013 schrieb Ahmet Inan: Yeah we have a lot of ptr = kmalloc(); BUG_ON(ptr); everywhere. I'll fix this one up but I really need to sit down and go through all of them and make sure we do the right thing in all these places. Thanks, But what would be

Re: btrfs crash when low on memory.

Am Mittwoch, 27. Februar 2013 schrieb Dave Jones: > Something I've yet to repeat managed to leak a whole bunch of memory > while I was travelling, and locked up my workstation. > > When I got home, this was the last thing printed out before it locked up > (it did make it into the logs thankfully)

Re: btrfs crash when low on memory.

Am Mittwoch, 27. Februar 2013 schrieb Dave Jones: Something I've yet to repeat managed to leak a whole bunch of memory while I was travelling, and locked up my workstation. When I got home, this was the last thing printed out before it locked up (it did make it into the logs thankfully)

Re: Tux3 report: New news for the new year

Am Dienstag, 1. Januar 2013 schrieb Daniel Phillips: > On Tuesday, January 01, 2013 02:06:19 PM Martin Steigerwald wrote: > > Sounds all good and nice and interesting to test, but where to grab the > > source? > > > > I found no obvious URL. > > Hi Martin, >

Re: Tux3 report: New news for the new year

Hi Daniel, Happy new year to you and everyone else! Am Dienstag, 1. Januar 2013 schrieb Daniel Phillips: [… long description on Tux3 design and current state …] > We have made plausible plans for all of the above, but indeed the devil > is in the doing. So we are considering the merits of

Re: Tux3 report: New news for the new year

Hi Daniel, Happy new year to you and everyone else! Am Dienstag, 1. Januar 2013 schrieb Daniel Phillips: [… long description on Tux3 design and current state …] We have made plausible plans for all of the above, but indeed the devil is in the doing. So we are considering the merits of

Re: Tux3 report: New news for the new year

Am Dienstag, 1. Januar 2013 schrieb Daniel Phillips: On Tuesday, January 01, 2013 02:06:19 PM Martin Steigerwald wrote: Sounds all good and nice and interesting to test, but where to grab the source? I found no obvious URL. Hi Martin, Sorry about that, I knew I forgot something

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Freitag, 7. Dezember 2012 schrieb Ingo Molnar: > * Martin Steigerwald wrote: > > > > The thing that people are complaining about is exactly the > > > reverse of this. It's *protecting* us from making mistakes, > > > and doesn't actually

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Freitag, 7. Dezember 2012 schrieb Ingo Molnar: * Martin Steigerwald mar...@lichtvoll.de wrote: The thing that people are complaining about is exactly the reverse of this. It's *protecting* us from making mistakes, and doesn't actually add any new interfaces in itself

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Donnerstag, 6. Dezember 2012 schrieb Linus Torvalds: > On Wed, Dec 5, 2012 at 5:14 PM, Dave Chinner wrote: > > And for changes to syscalls? That's something that must be peer > > reviewed because we are going to be stuck with those changes forever > > as we can't undo them at a later date. It

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Donnerstag, 6. Dezember 2012 schrieb Dave Chinner: > > That being said, you'll note that unlike Dave, I have > > **not** thrown a hissy fit when btrfs grabbed bits from the inode > > field, even though quite a bit more bits allocated for the inode > > flags than the fallocate flags. > > IOWs,

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Donnerstag, 6. Dezember 2012 schrieb Dave Chinner: That being said, you'll note that unlike Dave, I have **not** thrown a hissy fit when btrfs grabbed bits from the inode field, even though quite a bit more bits allocated for the inode flags than the fallocate flags. IOWs, pointing

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Donnerstag, 6. Dezember 2012 schrieb Linus Torvalds: On Wed, Dec 5, 2012 at 5:14 PM, Dave Chinner da...@fromorbit.com wrote: And for changes to syscalls? That's something that must be peer reviewed because we are going to be stuck with those changes forever as we can't undo them at a

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Mittwoch, 5. Dezember 2012 schrieb Theodore Ts'o: > On Wed, Dec 05, 2012 at 06:24:05PM +0100, Martin Steigerwald wrote: > > > Heck, I probably have more to complain about with the inode flags > > > field, which were originally created specifically for ext2/3/4, and >

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Mittwoch, 5. Dezember 2012 schrieb Theodore Ts'o: > On Wed, Dec 05, 2012 at 05:18:43PM +0100, Martin Steigerwald wrote: > > Dave provided technical reasons. > > > > First in the patch description and then in: > > > > https://lkml.org/lkml/2012/11/26/700 >

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Mittwoch, 5. Dezember 2012 schrieb Linus Torvalds: > On Wed, Dec 5, 2012 at 2:48 AM, Martin Steigerwald wrote: > > Linus, while I am interested in an answer I think that Dave and > > Christoph as Linux filesystem developers actually deserve one > > (instead of silentl

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Montag, 26. November 2012 schrieb Dave Chinner: > On Sun, Nov 25, 2012 at 09:55:20PM -0500, Theodore Ts'o wrote: > > On Mon, Nov 26, 2012 at 11:28:14AM +1100, Dave Chinner wrote: > > > fs: revert commit bbdd6808 to fallocate UAPI > > > > > > From: Dave Chinner > > > > > > Commit bbdd6808

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Montag, 26. November 2012 schrieb Dave Chinner: On Sun, Nov 25, 2012 at 09:55:20PM -0500, Theodore Ts'o wrote: On Mon, Nov 26, 2012 at 11:28:14AM +1100, Dave Chinner wrote: fs: revert commit bbdd6808 to fallocate UAPI From: Dave Chinner dchin...@redhat.com Commit bbdd6808

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Mittwoch, 5. Dezember 2012 schrieb Linus Torvalds: On Wed, Dec 5, 2012 at 2:48 AM, Martin Steigerwald mar...@lichtvoll.de wrote: Linus, while I am interested in an answer I think that Dave and Christoph as Linux filesystem developers actually deserve one (instead of silently being

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Mittwoch, 5. Dezember 2012 schrieb Theodore Ts'o: On Wed, Dec 05, 2012 at 05:18:43PM +0100, Martin Steigerwald wrote: Dave provided technical reasons. First in the patch description and then in: https://lkml.org/lkml/2012/11/26/700 There were no technical reasons. We are only

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Mittwoch, 5. Dezember 2012 schrieb Theodore Ts'o: On Wed, Dec 05, 2012 at 06:24:05PM +0100, Martin Steigerwald wrote: Heck, I probably have more to complain about with the inode flags field, which were originally created specifically for ext2/3/4, and which has since been grabbed

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Montag, 26. November 2012 schrieb Dave Chinner: > On Mon, Nov 26, 2012 at 11:53:45AM +, Alan Cox wrote: > > > It's not like there is any shortage of flag bits, so what's the > > > harm of reserving the bit? > > > > Why not just reserve a small group of bits for fs private use in that > >

Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI

Am Montag, 26. November 2012 schrieb Dave Chinner: On Mon, Nov 26, 2012 at 11:53:45AM +, Alan Cox wrote: It's not like there is any shortage of flag bits, so what's the harm of reserving the bit? Why not just reserve a small group of bits for fs private use in that case - for any

Re: [PATCH 00/16 v3] f2fs: introduce flash-friendly file system

Am Montag, 12. November 2012 schrieb Arnd Bergmann: > On Monday 12 November 2012, Martin Steigerwald wrote: > > Am Samstag, 10. November 2012 schrieb Arnd Bergmann: > > > > I would also recommend using flashbench to find out the optimum parameters > > > for your de

Re: [PATCH 00/16 v3] f2fs: introduce flash-friendly file system

Am Montag, 12. November 2012 schrieb Arnd Bergmann: On Monday 12 November 2012, Martin Steigerwald wrote: Am Samstag, 10. November 2012 schrieb Arnd Bergmann: I would also recommend using flashbench to find out the optimum parameters for your device. You can download it from git

Re: [PATCH 00/16 v3] f2fs: introduce flash-friendly file system

Am Samstag, 10. November 2012 schrieb Arnd Bergmann: > On Saturday 10 November 2012, Martin Steigerwald wrote: > > Command (m for help): n > > Partition type: > >p primary (0 primary, 0 extended, 4 free) > >e extended > > Select (default p): p > &g

Re: [REGRESSION] 3.7-rc3+git hard lockup on CPU after inserting/removing USB stick

Am Sonntag, 11. November 2012 schrieb Liu, Chuansheng: > > The first bad commit is: > > > > commit 73d4066055e0e2830533041f4b91df8e6e5976ff > > Author: Chuansheng Liu > > Date: Tue Sep 11 16:00:30 2012 +0800 > > > > USB/host: Cleanup unneccessary irq disable code > > > > Because the

<    1   2   3   4   5   >