Hi Randy,
thank you very much. I would not mind dropping my name but I tested the patch
now with 5.4.89 so you may actually also add
Tested-by: Martin Mokrejs
It also happened with 5.10.7, it is probably obvious.
Thank you for quick action.
Martin
On 16/01/2021 22:13, Randy Dunlap wrote
ter successful memory
allocation, before reaching any error paths.
References: http://lkml.org/lkml/2013/1/23/191
Reported-by: Martin Mokrejs
Tested-by: Peter Wu [ACPI conflict error path]
Signed-off-by: Peter Wu
---
Hi Jean,
This memleak issue is still present in v3.13-rc4-256-gb7000ad.
F
successful memory
allocation, before reaching any error paths.
References: http://lkml.org/lkml/2013/1/23/191
Reported-by: Martin Mokrejs mmokr...@fold.natur.cuni.cz
Tested-by: Peter Wu lekenst...@gmail.com [ACPI conflict error path]
Signed-off-by: Peter Wu lekenst...@gmail.com
---
Hi Jean
While you are probably thinking about the iwlwifi issue causing RT throttling
I have one more interesting followup below.
Peter Zijlstra wrote:
> On Fri, Aug 23, 2013 at 12:38:53PM +0200, Martin Mokrejs wrote:
>>> It means you have (a) real-time task(s) that consume significant amou
Martin Mokrejs wrote:
>>>> Nope, you get that message once to tell you that we throttle RT tasks.
>>>
>>> I think the message could improved to explain this is a warn ONCE message
>>> and
>>> that there is no "[sched_delayed] sched: RT
Peter Zijlstra wrote:
> On Fri, Aug 23, 2013 at 01:35:24PM +0200, Martin Mokrejs wrote:
>
>> # ps -deo pid,cls,cmd | grep -e 'RR \[' -e 'FF \['
>
> This explicitly only lists kernel threads; from your other comment:
>
>> The shell/python tasks have 'TS' in place of
Peter Zijlstra wrote:
> On Fri, Aug 23, 2013 at 12:38:53PM +0200, Martin Mokrejs wrote:
>>> It means you have (a) real-time task(s) that consume significant amount
>>
>> How can I find them?
>
> ps -deo pid,cls,cmd | grep -e RR -e FF
# ps -deo pid,cls,cmd | gr
Hi Peter,
Peter Zijlstra wrote:
> On Fri, Aug 23, 2013 at 10:53:02AM +0200, Martin Mokrejs wrote:
>> Hi,
>> I tried to figure out what this message really means. I came to
>> https://rt.wiki.kernel.org/index.php/Frequently_Asked_Questions
>> but I am still lost.
Hi,
I tried to figure out what this message really means. I came to
https://rt.wiki.kernel.org/index.php/Frequently_Asked_Questions
but I am still lost. I lack in the FAQ some user-related information.
The first paragraph is still unclear to me. I have a i7-2640M based
laptop, hyperthreading is
Hi,
I tried to figure out what this message really means. I came to
https://rt.wiki.kernel.org/index.php/Frequently_Asked_Questions
but I am still lost. I lack in the FAQ some user-related information.
The first paragraph is still unclear to me. I have a i7-2640M based
laptop, hyperthreading is
Hi Peter,
Peter Zijlstra wrote:
On Fri, Aug 23, 2013 at 10:53:02AM +0200, Martin Mokrejs wrote:
Hi,
I tried to figure out what this message really means. I came to
https://rt.wiki.kernel.org/index.php/Frequently_Asked_Questions
but I am still lost. I lack in the FAQ some user-related
Peter Zijlstra wrote:
On Fri, Aug 23, 2013 at 12:38:53PM +0200, Martin Mokrejs wrote:
It means you have (a) real-time task(s) that consume significant amount
How can I find them?
ps -deo pid,cls,cmd | grep -e RR -e FF
# ps -deo pid,cls,cmd | grep -e 'RR \[' -e 'FF \['
7 FF
Peter Zijlstra wrote:
On Fri, Aug 23, 2013 at 01:35:24PM +0200, Martin Mokrejs wrote:
# ps -deo pid,cls,cmd | grep -e 'RR \[' -e 'FF \['
This explicitly only lists kernel threads; from your other comment:
The shell/python tasks have 'TS' in place of the FF value in the second
column
Martin Mokrejs wrote:
Nope, you get that message once to tell you that we throttle RT tasks.
I think the message could improved to explain this is a warn ONCE message
and
that there is no [sched_delayed] sched: RT throttling deactivated
counterpart
message to be anticipated.
Would
While you are probably thinking about the iwlwifi issue causing RT throttling
I have one more interesting followup below.
Peter Zijlstra wrote:
On Fri, Aug 23, 2013 at 12:38:53PM +0200, Martin Mokrejs wrote:
It means you have (a) real-time task(s) that consume significant amount
How can I
Takashi Iwai wrote:
> At Wed, 20 Mar 2013 19:41:38 +0100,
> Martin Mokrejs wrote:
>>
>> Hi Takashi,
>> would you please describe your test system in more detail? How
>> about 'lspci -tv'? And 'lsusb -v' of the broken device?
>
> I left the machine in my o
Takashi Iwai wrote:
At Wed, 20 Mar 2013 19:41:38 +0100,
Martin Mokrejs wrote:
Hi Takashi,
would you please describe your test system in more detail? How
about 'lspci -tv'? And 'lsusb -v' of the broken device?
I left the machine in my office, so I'll give details tomorrow.
It's
Hanjun Guo wrote:
> On 2013-5-29 7:30, Rafael J. Wysocki wrote:
>> On Thursday, May 23, 2013 08:44:26 PM Hanjun Guo wrote:
>>> In acpi_processor_add(), get_cpu_device() will return NULL sometimes,
>>> although the chances are small, I think it should be fixed.
>>>
>>> Signed-off-by: Hanjun Guo
>>
Hanjun Guo wrote:
On 2013-5-29 7:30, Rafael J. Wysocki wrote:
On Thursday, May 23, 2013 08:44:26 PM Hanjun Guo wrote:
In acpi_processor_add(), get_cpu_device() will return NULL sometimes,
although the chances are small, I think it should be fixed.
Signed-off-by: Hanjun Guo
Hi,
while you are chasing some problem with i2c_801 I would like to mention
that I never got an answer on the thread https://lkml.org/lkml/2013/1/23/405
about a kmemleak reported by kernel . Maybe this could give you a hint?
If these do not overlap I would be anyways glad to receive an answer
Hi,
while you are chasing some problem with i2c_801 I would like to mention
that I never got an answer on the thread https://lkml.org/lkml/2013/1/23/405
about a kmemleak reported by kernel . Maybe this could give you a hint?
If these do not overlap I would be anyways glad to receive an answer
Hi,
I opened yet another bug https://bugzilla.kernel.org/show_bug.cgi?id=57411 .
This is maybe a dupe of bug https://bugzilla.kernel.org/show_bug.cgi?id=57401
(which is vanilla 3.9) but happened on linux-next-20130501 after I did "dmesg |
less".
? pid_param_set
intel_pstate_timer_func
Hi,
I just this kernel crash on my laptop running fine so far on 3.7.10 (and 3.8.5
if really necessary). The 3.9 was running for maybe 2 hrs, at the most. :(
? cpumask_weight
call_timer_fn.clone
? init_timer_key
run_timer_softirq
? cpumask_weight
__do_softirq
smp_apic_timer_interrupt
Hi,
I just this kernel crash on my laptop running fine so far on 3.7.10 (and 3.8.5
if really necessary). The 3.9 was running for maybe 2 hrs, at the most. :(
? cpumask_weight
call_timer_fn.clone
? init_timer_key
run_timer_softirq
? cpumask_weight
__do_softirq
smp_apic_timer_interrupt
Hi,
I opened yet another bug https://bugzilla.kernel.org/show_bug.cgi?id=57411 .
This is maybe a dupe of bug https://bugzilla.kernel.org/show_bug.cgi?id=57401
(which is vanilla 3.9) but happened on linux-next-20130501 after I did dmesg |
less.
? pid_param_set
intel_pstate_timer_func
Bjorn Helgaas wrote:
> On Mon, Apr 1, 2013 at 2:51 PM, Rafael J. Wysocki wrote:
>> On Monday, April 01, 2013 11:34:46 AM Bjorn Helgaas wrote:
>>> [+cc Zheng, who added this with 71a83bd727]
>>>
>>> On Sat, Mar 30, 2013 at 4:38 PM, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
Bjorn Helgaas wrote:
On Mon, Apr 1, 2013 at 2:51 PM, Rafael J. Wysocki r...@sisk.pl wrote:
On Monday, April 01, 2013 11:34:46 AM Bjorn Helgaas wrote:
[+cc Zheng, who added this with 71a83bd727]
On Sat, Mar 30, 2013 at 4:38 PM, Rafael J. Wysocki r...@sisk.pl wrote:
From: Rafael J. Wysocki
So, I re-tested again with the patch and 3.8.3 but without laptop-mode-tools.
The xHCI port works fine provided
/sys/bus/pci/devices/:0b:00.0/power/control
is set to on and /sys/bus/pci/devices/:00:1c.4/power/control also to on.
If I set parent 1c.4 to auto, it gets suspended and the port
vostro ~ #
My apologies if that twisted the test and thanks for you detailed explanations.
I will spot below, however, a few questions.
Sarah Sharp wrote:
> On Fri, Mar 29, 2013 at 04:05:54PM +0100, Martin Mokrejs wrote:
>
>> Nevertheless, I went to check if if the USB3 socke
Hi,
I applied this patches over 3.8.3 hoping it will fix my issue under
thread: "Re: 3.8.2: xhci port is dead until pcieport PME# goes to disabled"
but unfortunately, it is even worse! Now, although lsusb -v nor lsusb -vv do
wakeup the XHCI port but it falls asleep immediately, more quickly than
Hi,
I applied this patches over 3.8.3 hoping it will fix my issue under
thread: Re: 3.8.2: xhci port is dead until pcieport PME# goes to disabled
but unfortunately, it is even worse! Now, although lsusb -v nor lsusb -vv do
wakeup the XHCI port but it falls asleep immediately, more quickly than I
vostro ~ #
My apologies if that twisted the test and thanks for you detailed explanations.
I will spot below, however, a few questions.
Sarah Sharp wrote:
On Fri, Mar 29, 2013 at 04:05:54PM +0100, Martin Mokrejs wrote:
Nevertheless, I went to check if if the USB3 socket dies after first
So, I re-tested again with the patch and 3.8.3 but without laptop-mode-tools.
The xHCI port works fine provided
/sys/bus/pci/devices/:0b:00.0/power/control
is set to on and /sys/bus/pci/devices/:00:1c.4/power/control also to on.
If I set parent 1c.4 to auto, it gets suspended and the port
Pavel Machek wrote:
> Hi!
>
>> pavel@amd:~$ cat /proc/acpi/battery/BAT0/info
>> present: yes
>> design capacity: 0 mWh
>> last full capacity: 0 mWh
>> battery technology: rechargeable
>> design voltage: 14400 mV
>>
>>
Pavel Machek wrote:
Hi!
pavel@amd:~$ cat /proc/acpi/battery/BAT0/info
present: yes
design capacity: 0 mWh
last full capacity: 0 mWh
battery technology: rechargeable
design voltage: 14400 mV
This worked before... at least it works in 2.6
Martin Mokrejs wrote:
> Hi Takashi,
> would you please describe your test system in more detail? How
> about 'lspci -tv'? And 'lsusb -v' of the broken device?
>
> 1. For me on Dell Vostro 3550 with a SandyBridge chip doing all
> SATA+USB2+ExpressCardSlot:
>
> 00
Hi Takashi,
would you please describe your test system in more detail? How
about 'lspci -tv'? And 'lsusb -v' of the broken device?
1. For me on Dell Vostro 3550 with a SandyBridge chip doing all
SATA+USB2+ExpressCardSlot:
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
Hi Takashi,
would you please describe your test system in more detail? How
about 'lspci -tv'? And 'lsusb -v' of the broken device?
1. For me on Dell Vostro 3550 with a SandyBridge chip doing all
SATA+USB2+ExpressCardSlot:
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
Martin Mokrejs wrote:
Hi Takashi,
would you please describe your test system in more detail? How
about 'lspci -tv'? And 'lsusb -v' of the broken device?
1. For me on Dell Vostro 3550 with a SandyBridge chip doing all
SATA+USB2+ExpressCardSlot:
00:00.0 Host bridge: Intel Corporation
Hi Alex,
I was just going to ask you whether your patch would "explain" why pciehp has
in my experience broken presence detection while acpiphp has not (on 3.7 kernel)
and whether the patch will fix it.
Some testing I have done in the past on 3.2 kernel and on 3.7.1, with no
fixes.
Maybe you
Hi Alex,
I was just going to ask you whether your patch would explain why pciehp has
in my experience broken presence detection while acpiphp has not (on 3.7 kernel)
and whether the patch will fix it.
Some testing I have done in the past on 3.2 kernel and on 3.7.1, with no
fixes.
Maybe you
Hi Chris,
Chris Clayton wrote:
> Hi Martin,
>
> On 01/28/13 21:02, Martin Mokrejs wrote:
>> Hi Chris,
>>
>> Chris Clayton wrote:
>>> Hi Martin,
>>>
>>> On 01/28/13 12:12, Martin Mokrejs wrote:
>>>> Chris Clayton wrote:
>>&
Hi Chris,
Chris Clayton wrote:
Hi Martin,
On 01/28/13 21:02, Martin Mokrejs wrote:
Hi Chris,
Chris Clayton wrote:
Hi Martin,
On 01/28/13 12:12, Martin Mokrejs wrote:
Chris Clayton wrote:
I've struggled with this a little. For some reason, the expresscard
doesn't always stay
Hi Chris,
Chris Clayton wrote:
> Hi Martin,
>
> On 01/28/13 12:12, Martin Mokrejs wrote:
>> Chris Clayton wrote:
>>>
>>> [snip]
>>>
>>>> [chris:~]$ cat /proc/cmdline
>>>> root=/dev/sda5 pciehp_ports=native ro resume=/dev/sda6
>
Chris Clayton wrote:
>
> [snip]
>
>> [chris:~]$ cat /proc/cmdline
>> root=/dev/sda5 pciehp_ports=native ro resume=/dev/sda6
> ^^
> **typo**
> I've run the test again with pcie_ports=native and the directories now get
> populated. Even better though, is
Chris Clayton wrote:
> Hi Yijing,
>
> On 01/28/13 02:40, Yijing Wang wrote:
>> Hi Chris,
>> Sorry for the delay reply. It seems like my reply last night was missed.
>>
>> From the sysinfo you provide, there are no pcie port devices under
>> /sys/bus/pci_express/devices.
>> Maybe because
Chris Clayton wrote:
Hi Yijing,
On 01/28/13 02:40, Yijing Wang wrote:
Hi Chris,
Sorry for the delay reply. It seems like my reply last night was missed.
From the sysinfo you provide, there are no pcie port devices under
/sys/bus/pci_express/devices.
Maybe because there are some
Chris Clayton wrote:
[snip]
[chris:~]$ cat /proc/cmdline
root=/dev/sda5 pciehp_ports=native ro resume=/dev/sda6
^^
**typo**
I've run the test again with pcie_ports=native and the directories now get
populated. Even better though, is that when I
Hi Chris,
Chris Clayton wrote:
Hi Martin,
On 01/28/13 12:12, Martin Mokrejs wrote:
Chris Clayton wrote:
[snip]
[chris:~]$ cat /proc/cmdline
root=/dev/sda5 pciehp_ports=native ro resume=/dev/sda6
^^
**typo**
I've run the test again
Hi Chris,
Chris Clayton wrote:
> Thanks again, Martin.
>
> Firstly, maybe we should remove the linux-media list from the copy list. I
> imagine this hotplug stuff is just noise to them.
>
> [snip]
>> Do you have any other express card around to try if it works at all? Try
>> that always after
Chris Clayton wrote:
>
>
> On 01/27/13 14:26, Martin Mokrejs wrote:
>> Chris Clayton wrote:
>>>
>>>
>>> On 01/27/13 12:18, Yijing Wang wrote:
>>>> 于 2013-01-27 19:19, Chris Clayton 写道:
>>>>> Hi Yijing
>>>>>
&g
Chris Clayton wrote:
>
>
> On 01/27/13 12:18, Yijing Wang wrote:
>> 于 2013-01-27 19:19, Chris Clayton 写道:
>>> Hi Yijing
>>>
>>> On 01/27/13 02:45, Yijing Wang wrote:
>>>> 于 2013-01-27 4:54, Chris Clayton 写道:
>>>>> Hi Martin,
Chris Clayton wrote:
On 01/27/13 12:18, Yijing Wang wrote:
于 2013-01-27 19:19, Chris Clayton 写道:
Hi Yijing
On 01/27/13 02:45, Yijing Wang wrote:
于 2013-01-27 4:54, Chris Clayton 写道:
Hi Martin,
On 01/24/13 19:21, Martin Mokrejs wrote:
Hi Chris,
try to include in kernel only
Chris Clayton wrote:
On 01/27/13 14:26, Martin Mokrejs wrote:
Chris Clayton wrote:
On 01/27/13 12:18, Yijing Wang wrote:
于 2013-01-27 19:19, Chris Clayton 写道:
Hi Yijing
On 01/27/13 02:45, Yijing Wang wrote:
于 2013-01-27 4:54, Chris Clayton 写道:
Hi Martin,
On 01/24/13 19:21, Martin
Hi Chris,
Chris Clayton wrote:
Thanks again, Martin.
Firstly, maybe we should remove the linux-media list from the copy list. I
imagine this hotplug stuff is just noise to them.
[snip]
Do you have any other express card around to try if it works at all? Try
that always after a cold
Hi Chris,
Chris Clayton wrote:
> Hi Martin,
>
> On 01/24/13 19:21, Martin Mokrejs wrote:
>> Hi Chris,
>>try to include in kernel only acpiphp and omit pciehp. Don't use modules
>> but include
>> them statically. And try, in addition, check whether "
Hi Chris,
Chris Clayton wrote:
Hi Martin,
On 01/24/13 19:21, Martin Mokrejs wrote:
Hi Chris,
try to include in kernel only acpiphp and omit pciehp. Don't use modules
but include
them statically. And try, in addition, check whether pcie_aspm=off in
grub.conf helped.
Thanks
Greg KH wrote:
> On Thu, Jan 24, 2013 at 10:53:25PM +0100, Martin Mokrejs wrote:
>> Hi Sarah and Alan,
>> I just saw 3.7.5 patches announced by Greg but I don't see this path in
>> there.
>> And, don't know but maybe this applies to older stable kernels as well?
>
table@"? ;-)
Date: Thu, 17 Jan 2013 10:32:16 -0500 (EST)
From: Alan Stern
To: Sarah Sharp
cc: Martin Mokrejs ,
USB list
Subject: [PATCH] USB: XHCI: fix memory leak of URB-private data
Message-ID:
Thank you,
Martin
Alan Stern wrote:
> This patch (as1640) fixes a memory lea
Hi Chris,
try to include in kernel only acpiphp and omit pciehp. Don't use modules but
include
them statically. And try, in addition, check whether "pcie_aspm=off" in
grub.conf helped.
The best would if you subscribe to linux-pci, and read my recent threads
about similar issues I had with
Hi Chris,
try to include in kernel only acpiphp and omit pciehp. Don't use modules but
include
them statically. And try, in addition, check whether pcie_aspm=off in
grub.conf helped.
The best would if you subscribe to linux-pci, and read my recent threads
about similar issues I had with
@? ;-)
Date: Thu, 17 Jan 2013 10:32:16 -0500 (EST)
From: Alan Stern st...@rowland.harvard.edu
To: Sarah Sharp sarah.a.sh...@linux.intel.com
cc: Martin Mokrejs mmokr...@fold.natur.cuni.cz,
USB list linux-...@vger.kernel.org
Subject: [PATCH] USB: XHCI: fix memory leak of URB-private data
Message-ID
Greg KH wrote:
On Thu, Jan 24, 2013 at 10:53:25PM +0100, Martin Mokrejs wrote:
Hi Sarah and Alan,
I just saw 3.7.5 patches announced by Greg but I don't see this path in
there.
And, don't know but maybe this applies to older stable kernels as well?
Where will this patch posted originally
Hi,
today I got the following report from the kernel, looks it happened when
I started/used/quit chromium browser. I haven't seen this with 3.7.1 but
I use builtin kmemleak detector only for 2-3 weeks.
unreferenced object 0x880402d08000 (size 2048):
comm "chrome_sandbox", pid 18437,
Hi Jean,
Jean Delvare wrote:
> Hi Martin,
>
> On Wed, 23 Jan 2013 12:15:37 +0100, Martin Mokrejs wrote:
>> Hi,
>> I already reported this to lkml recently with linux-3.7.1 but this is to
>> let you know
>> that with 3.7.4 I am still getting this kmemleak rep
Hi Jean,
Jean Delvare wrote:
Hi Martin,
On Wed, 23 Jan 2013 12:15:37 +0100, Martin Mokrejs wrote:
Hi,
I already reported this to lkml recently with linux-3.7.1 but this is to
let you know
that with 3.7.4 I am still getting this kmemleak reported by the kernel.
I don't read LKML
Hi,
today I got the following report from the kernel, looks it happened when
I started/used/quit chromium browser. I haven't seen this with 3.7.1 but
I use builtin kmemleak detector only for 2-3 weeks.
unreferenced object 0x880402d08000 (size 2048):
comm chrome_sandbox, pid 18437, jiffies
Yinghai Lu wrote:
> On Wed, Jan 16, 2013 at 4:24 PM, Alex Villacís Lasso
> wrote:
>> El 16/01/13 02:11, Yinghai Lu escribió:
>>
>>> On Tue, Jan 15, 2013 at 5:47 PM, Alex Villacís Lasso
>>> wrote:
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem
Yinghai Lu wrote:
On Wed, Jan 16, 2013 at 4:24 PM, Alex Villacís Lasso
a_villa...@palosanto.com wrote:
El 16/01/13 02:11, Yinghai Lu escribió:
On Tue, Jan 15, 2013 at 5:47 PM, Alex Villacís Lasso
a_villa...@palosanto.com wrote:
[0.00] e820: BIOS-provided physical RAM map:
[
Hugh Dickins wrote:
> On Sun, 6 Jan 2013, Martin Mokrejs wrote:
>
>> I was running 3.7.1 kernel quite fine for a while but I realized that it is
>> slow and that
>> I should go and drop useless kernel drivers from my kernel. I have a
>> SandyBridge-based
>>
Hi,
I just hit this thread in my bloated Inbox.
Rafael J. Wysocki wrote:
> On Thursday, January 10, 2013 03:03:53 PM Yinghai Lu wrote:
>> On Thu, Jan 10, 2013 at 1:50 PM, Rafael J. Wysocki wrote:
>>> Well, I don't see what functional problems that can bring.
>>>
>>> In theory people may want
Hi,
I just hit this thread in my bloated Inbox.
Rafael J. Wysocki wrote:
On Thursday, January 10, 2013 03:03:53 PM Yinghai Lu wrote:
On Thu, Jan 10, 2013 at 1:50 PM, Rafael J. Wysocki r...@sisk.pl wrote:
Well, I don't see what functional problems that can bring.
In theory people may want
Hugh Dickins wrote:
On Sun, 6 Jan 2013, Martin Mokrejs wrote:
I was running 3.7.1 kernel quite fine for a while but I realized that it is
slow and that
I should go and drop useless kernel drivers from my kernel. I have a
SandyBridge-based
laptop and I found that I gain speed while
Hi,
today I received the following.
[ 124.927854] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 124.987250] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 124.992228] pci_bus :11: dev 00, created physical slot 1
[ 124.992448] acpiphp: Slot [1] registered
[ 233.258244]
Hi,
today I received the following.
[ 124.927854] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 124.987250] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 124.992228] pci_bus :11: dev 00, created physical slot 1
[ 124.992448] acpiphp: Slot [1] registered
[ 233.258244]
Hi Hilf,
thank you for your answer on this albeit I am not sure I understood your
point well.
Hillf Danton wrote:
> Hello Martin
>
> On Mon, Jan 7, 2013 at 6:59 AM, Martin Mokrejs
> wrote:
>> time to time. With ondemand governor I had cores in C7 for 50-7
Hi Hilf,
thank you for your answer on this albeit I am not sure I understood your
point well.
Hillf Danton wrote:
Hello Martin
On Mon, Jan 7, 2013 at 6:59 AM, Martin Mokrejs
mmokr...@fold.natur.cuni.cz wrote:
time to time. With ondemand governor I had cores in C7 for 50-70
rcu: endless stalls
>> From: Mike Galbraith
>> linux-3.4-rc7: rcu_sched self-detected stall on CPU
>> From: Martin Mokrejs
>> RCU stalls in linux-next
>> From: Dan Carpenter
>>
>> I try to reproduce the issue on my X86 server with 12 cpu
>
-3.4-rc7: rcu_sched self-detected stall on CPU
From: Martin Mokrejs
RCU stalls in linux-next
From: Dan Carpenter
I try to reproduce the issue on my X86 server with 12 cpu
The 'endless stalls' box was 341.3 times larger. Dunno if you can
even set a serial port slow enough
On Fri, May 18, 2007 at 04:20:39PM +0200, Jesper Juhl wrote:
> On 18/05/07, Martin Mokrejs <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I just tried the 2.6.22-r1 candidate to test whether some bug I have
> > hit in the past still exists. I did use 2.6.20.6 so far. So,
On Fri, May 18, 2007 at 07:38:18PM +0530, Kalpak Shah wrote:
> On Fri, 2007-05-18 at 15:51 +0200, Martin Mokrejs wrote:
> > On Fri, May 18, 2007 at 05:17:06PM +0530, Kalpak Shah wrote:
> > > On Fri, 2007-05-18 at 11:06 +0200, Martin Mokrejs wrote:
> > > > Hi,
> &
On Fri, May 18, 2007 at 05:17:06PM +0530, Kalpak Shah wrote:
> On Fri, 2007-05-18 at 11:06 +0200, Martin Mokrejs wrote:
> > Hi,
> > I just tried the 2.6.22-r1 candidate to test whether some bug I have
> > hit in the past still exists. I did use 2.6.20.6 so far. So, I have
Hi,
I just tried the 2.6.22-r1 candidate to test whether some bug I have
hit in the past still exists. I did use 2.6.20.6 so far. So, I have
cleanly rebooted to use the new kernel, after the machine came up I
tried to mess with the bug, and had to reboot again to play with kernel
commandline
Hi,
I just tried the 2.6.22-r1 candidate to test whether some bug I have
hit in the past still exists. I did use 2.6.20.6 so far. So, I have
cleanly rebooted to use the new kernel, after the machine came up I
tried to mess with the bug, and had to reboot again to play with kernel
commandline
On Fri, May 18, 2007 at 05:17:06PM +0530, Kalpak Shah wrote:
On Fri, 2007-05-18 at 11:06 +0200, Martin Mokrejs wrote:
Hi,
I just tried the 2.6.22-r1 candidate to test whether some bug I have
hit in the past still exists. I did use 2.6.20.6 so far. So, I have
cleanly rebooted to use
On Fri, May 18, 2007 at 07:38:18PM +0530, Kalpak Shah wrote:
On Fri, 2007-05-18 at 15:51 +0200, Martin Mokrejs wrote:
On Fri, May 18, 2007 at 05:17:06PM +0530, Kalpak Shah wrote:
On Fri, 2007-05-18 at 11:06 +0200, Martin Mokrejs wrote:
Hi,
I just tried the 2.6.22-r1 candidate
On Fri, May 18, 2007 at 04:20:39PM +0200, Jesper Juhl wrote:
On 18/05/07, Martin Mokrejs [EMAIL PROTECTED] wrote:
Hi,
I just tried the 2.6.22-r1 candidate to test whether some bug I have
hit in the past still exists. I did use 2.6.20.6 so far. So, I have
cleanly rebooted to use the new
> I used to shutdown my P4 machine based on ASUS P4C800E-Deluxe
> with simple "init 0" command. That somehow broke between 2.6.12-rc6-git2
> and 2.6.13-rc1. The machines makes the sound like shutdown but it
> immediately turns the power on again. I used acpi and the kernel
> configs should be
I used to shutdown my P4 machine based on ASUS P4C800E-Deluxe
with simple init 0 command. That somehow broke between 2.6.12-rc6-git2
and 2.6.13-rc1. The machines makes the sound like shutdown but it
immediately turns the power on again. I used acpi and the kernel
configs should be almost
Hi,
I used to shutdown my P4 machine based on ASUS P4C800E-Deluxe
with simple "init 0" command. That somehow broke between 2.6.12-rc6-git2
and 2.6.13-rc1. The machines makes the sound like shutdown but it
immediately turns the power on again. I used acpi and the kernel
configs should be almost
Hi,
I used to shutdown my P4 machine based on ASUS P4C800E-Deluxe
with simple init 0 command. That somehow broke between 2.6.12-rc6-git2
and 2.6.13-rc1. The machines makes the sound like shutdown but it
immediately turns the power on again. I used acpi and the kernel
configs should be almost
Hi,
I use on i686 architecture Gentoo linux with XFS filesystem.
Recently it happened to me 3 time that the machine locked,
although at least once sys-rq+b worked. Here is the log
from remote console. I don't remeber having such problems
with 2.6.12-rc6-git2, which was my previous testing
Hi,
I use on i686 architecture Gentoo linux with XFS filesystem.
Recently it happened to me 3 time that the machine locked,
although at least once sys-rq+b worked. Here is the log
from remote console. I don't remeber having such problems
with 2.6.12-rc6-git2, which was my previous testing
DervishD wrote:
again I've hit some wird problem doing "make dep" for 2.4 kernel:
Not a kernel problem but a findutils problem. Fixed in 4.2.19,
but 4.2.20 was released recently. Upgrade.
You were right. Thanks!
M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
DervishD wrote:
again I've hit some wird problem doing make dep for 2.4 kernel:
Not a kernel problem but a findutils problem. Fixed in 4.2.19,
but 4.2.20 was released recently. Upgrade.
You were right. Thanks!
M.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
95 matches
Mail list logo
