From: Vincent Pelletier <plr.vincent@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-leds@vger.kernel.org
Subject: Re: leds-gpio on x86
Date: Tue, 18 Aug 2015 09:32:26 +0200 [thread overview]
Message-ID: <20150818093226.3db0b553@x2> (raw)
In-Reply-To: <20150817230823.61de477a@x2>
On Mon, 17 Aug 2015 23:08:23 +0200, Vincent Pelletier
<plr.vincent@gmail.com> wrote:
> How can I debug this further ?
I made a bit of progress: disabling all but one cpu (...which, in this
case, just means disabling the second core) makes the error messages go
away, and blinking works fine.
There is a lock taken in __request_region, and released around
schedule() when muxed. I guess this means region request is just pushed
into a queue when resource is busy, then scheduler is told to let
whatever else available run.
I have no idea if the lock should be taken before or after
remove_wait_queue after schedule call.
FWIW:
# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Celeron(R) CPU J1800 @ 2.41GHz
stepping : 8
microcode : 0x811
cpu MHz : 2582.817
cache size : 1024 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bugs :
bogomips : 4825.60
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
I'm looking for some resource tracing mechanism, but haven't found one
yet. I suspect that there is a driver I haven't identified yet which
would allocate resources incorrectly (or in an incompatible way, at
least).
Regards,
--
Vincent Pelletier
next prev parent reply other threads:[~2015-08-18 7:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 20:09 leds-gpio on x86 Vincent Pelletier
2015-08-06 16:59 ` Mika Westerberg
2015-08-06 17:17 ` Vincent Pelletier
2015-08-06 17:35 ` Mika Westerberg
2015-08-06 18:18 ` Vincent Pelletier
2015-08-07 10:57 ` Mika Westerberg
2015-08-08 12:06 ` Vincent Pelletier
2015-08-11 12:00 ` Mika Westerberg
2015-08-11 17:42 ` Vincent Pelletier
2015-08-12 12:53 ` Mika Westerberg
2015-08-15 10:36 ` Vincent Pelletier
2015-08-17 21:08 ` Vincent Pelletier
2015-08-18 7:32 ` Vincent Pelletier [this message]
2015-08-18 9:02 ` Mika Westerberg
2015-08-18 11:38 ` Vincent Pelletier
2015-08-18 22:56 ` Vincent Pelletier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150818093226.3db0b553@x2 \
--to=plr.vincent@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox