Best guess:
With 'noapic', I see the "irq 5: nobody cared" message on resume,
along with 1 IRQ5 counts in /proc/interrupts (the devices claiming
that IRQ are quiescent).
Without 'noapic' that must be triggering something else to go haywire,
perhaps the AER logic (though that is all MSI, so
$subject
s/arm:omap/ARM: OMAP:
On Sunday 30 December 2012 02:13 AM, ahema...@gmail.com wrote:
From: ahemaily
The variable dma_lch_count used for comparison (omap_dma_reserve_channels <=
dma_lch_count)
before it initialized to the value from omap_dma_dev_attr : d->lch_count.
s/it/it is
Quick update: booting with 'noapic' on the commandline seems to make
it resume successfully.
The main dmesg diffs, other than the obvious "Skipping IOAPIC probe"
and IRG number diffs) are:
-nr_irqs_gsi: 40
+nr_irqs_gsi: 16
-NR_IRQS:16640 nr_irqs:776 16
+NR_IRQS:16640 nr_irqs:368 16
-system
Hi,
On Tue, Dec 11, 2012 at 10:20:51AM +0900, MyungJoo Ham wrote:
> On Fri, Nov 30, 2012 at 5:42 PM, Abhilash Kesavan
> wrote:
> > drivers/devfreq/Kconfig| 10 +
> > drivers/devfreq/Makefile |1 +
> > drivers/devfreq/exynos5_bus.c | 595
> >
Hi,
Just a quick hit of review, I haven't done anything more in-depth yet.
On Fri, Dec 28, 2012 at 04:24:09AM -0500, Abhilash Kesavan wrote:
> - Setup the INT clock ops to control/vary INT frequency
> - Add PPMU support for Exynos5250
> - Add mappings initially for the PPMU device
>
>
From: Namjae Jeon
Consider Process A: huge I/O on sda
doing heavy write operation - dirty memory becomes more
than dirty_background_ratio
on HDD - flusher thread flush-8:0
Consider Process B: small I/O on sdb
doing while [1]; read 1024K + rewrite 1024K + sleep
At 12/28/2012 08:28 AM, Kamezawa Hiroyuki Wrote:
> (2012/12/27 21:16), Wen Congyang wrote:
>> At 12/26/2012 11:55 AM, Kamezawa Hiroyuki Wrote:
>>> (2012/12/24 21:09), Tang Chen wrote:
From: Wen Congyang
We call hotadd_new_pgdat() to allocate memory to store node_data. So we
From: Namjae Jeon
While creating a new entry for addition to the list(orphan inode list
and fsync inode entry list), there is no need to call HEAD initialization
for these entries. So, remove that init part.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/f2fs/checkpoint.c |
From: Namjae Jeon
Cache entry for free NID, is not getting removed under proper
lock in case of error in add_free_nid. So, free the cache entry
first before releasing the spinlock.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/f2fs/node.c |2 +-
1 file changed, 1
From: Namjae Jeon
After doing a punch hole or expanding inode doing fallocation.
The change and modification time are not update for the file.
So, update time after no issue is observed in fallocate.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/f2fs/file.c |5 +
1
From: Namjae Jeon
Introduced f2fs_msg function to differentiate f2fs specific messages in
the log. And, added few informative prints in the mount path, to convey
proper error in case of mount failure.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/f2fs/f2fs.h |2 ++
At 12/25/2012 04:35 PM, Glauber Costa Wrote:
> On 12/24/2012 04:09 PM, Tang Chen wrote:
>> From: Wen Congyang
>>
>> memory can't be offlined when CONFIG_MEMCG is selected.
>> For example: there is a memory device on node 1. The address range
>> is [1G, 1.5G). You will find 4 new directories
At 12/26/2012 11:02 AM, Kamezawa Hiroyuki Wrote:
> (2012/12/24 21:09), Tang Chen wrote:
>> From: Wen Congyang
>>
>> memory can't be offlined when CONFIG_MEMCG is selected.
>> For example: there is a memory device on node 1. The address range
>> is [1G, 1.5G). You will find 4 new directories
On Sun, Dec 30, 2012 at 1:45 AM, Du Jiulun wrote:
> I'm experiencing random (but frequent) kernel panics and system
> freezes without panic information while I'm watching videos using
> SMPlayer or Google Chrome (with Flash plugin).
>
Is it triggered only when watching video?
> [4.] Kernel
Running a suspend with pm_trace set, I get:
aer :00:03.0:pcie02: hash matches
I don't know what magic might be needed here, though.
I guess next step is to try to build a non-distro kernel.
On Sat, Dec 29, 2012 at 1:57 PM, Rafael J. Wysocki wrote:
> On Saturday, December 29, 2012 12:03:13
On Fri, Dec 28, 2012 at 05:42:46PM -0700, Stephen Warren wrote:
> From: Stephen Warren
>
> if_changed (used by the *.dts->*.dtc rule) rebuilds files if they aren't
> contained in $(targets). (make V=2 indicates this). Add $(dtb-y) to
> $(targets) to prevent *.dtb from always being rebuilt.
>
>
Hi Linus,
bit larger due to me not bothering to do anything since before Xmas, and
other people working too hard after I had clearly given up.
Its got the 3 main x86 driver fixes pulls, and a bunch of tegra fixes,
doesn't fix the Ironlake bug yet, but that does seem to be getting closer.
On Tue, Dec 18, 2012 at 3:42 AM, Claudio Fontana
wrote:
>
> Using __CPUINIT instead of __INIT puts the secondary CPU startup code
> into the "right" section: it will not be freed in hotplug configurations,
> allowing hot-add of cpus, while still getting freed in non-hotplug configs.
>
> Tested
On Mon, Dec 24, 2012 at 12:43:25AM +0100, Frederic Weisbecker wrote:
> 2012/12/21 Steven Rostedt :
> > On Thu, 2012-12-20 at 19:32 +0100, Frederic Weisbecker wrote:
> >> Let's imagine you have 4 CPUs. We keep the CPU 0 to offline RCU callbacks
> >> there and to
> >> handle the timekeeping. We set
On Sat, 2012-12-29 at 14:27 -0800, Roland Dreier wrote:
> On Sat, Dec 29, 2012 at 12:08 PM, Joe Perches wrote:
> > Sylvan Munaut did something similar
> > https://lkml.org/lkml/2012/12/5/168
>
> Missed that and duplicated the debugging :(
> Sorry Sylvain.
>
> I guess my patch may be preferable,
tm_mon is 0..11, whereas vt8500 expects 1..12 for the month field,
causing invalid date errors for January, and causing the day field
to roll over incorrectly.
The century flag is only handled in vt8500_rtc_read_time, but not
set in vt8500_rtc_set_time. This patch corrects the behaviour of the
On Sat, Dec 29, 2012 at 05:32:12PM -0600, Eric Sandeen wrote:
> yeah, that should work; great minds think alike ;) Our patches
> crossed in the ether I guess.
>
> XFS uses EWRONGFS as an alias for EINVAL internally in these cases,
> so maybe we should stick with that for consistency, *shrug*
I
>which suggests that the patch is incomplete and that I am blind :/
>mem_cgroup_cache_charge calls __mem_cgroup_try_charge for the page cache
>and that one doesn't check GFP_MEMCG_NO_OOM. So you need the following
>follow-up patch on top of the one you already have (which should catch
>all the
The file uses nothing from the header, so remove it.
Signed-off-by: Jesper Juhl
---
drivers/scsi/mpt3sas/mpt3sas_trigger_diag.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/mpt3sas/mpt3sas_trigger_diag.c
b/drivers/scsi/mpt3sas/mpt3sas_trigger_diag.c
On Sat, 2012-12-29 at 00:21 -0800, Jonathan Nieder wrote:
> Ben Hutchings wrote:
>
> > This adds PCI ID for IVB GT2 server variant which we were missing.
>
> As discussed at [1], this triggers a small regression with Debian
> wheezy userspace (X freezing instead of erroring out). libdrm hasn't
On 12/29/12 5:16 PM, Sergei Trofimovich wrote:
> It fixes boot panic when trying to boot from btrfs filesystem.
> kernel tries to mount as xfs and gets fatal -EUCLEAN:
>
> [0.17] VFS: Cannot open root device "ubda" or unknown-block(98,0):
> error -117
> [0.17] Please append a
It fixes boot panic when trying to boot from btrfs filesystem.
kernel tries to mount as xfs and gets fatal -EUCLEAN:
[0.17] VFS: Cannot open root device "ubda" or unknown-block(98,0):
error -117
[0.17] Please append a correct "root=" boot option; here are the
available
From: Rafael J. Wysocki
Commit 0090def6 (ACPI: Add interface to register/unregister device
to/from power resources) made it possible to indicate to the ACPI
core that if the given device depends on any power resources, then
it should be resumed as soon as all of the power resources required
by
arch/um/os-Linux/signal.c:18:8: error: conflicting types for 'sig_info'
In file included from /home/slyfox/linux-2.6/arch/um/os-Linux/signal.c:12:0:
arch/um/include/shared/as-layout.h:64:15: note: previous declaration of
'sig_info' was here
Signed-off-by: Sergei Trofimovich
CC: Jeff Dike
CC:
arch/um/os-Linux/start_up.c: In function 'check_coredump_limit':
arch/um/os-Linux/start_up.c:338:16: error: storage size of 'lim' isn't known
arch/um/os-Linux/start_up.c:339:2: error: implicit declaration of function
'getrlimit' [-Werror=implicit-function-declaration]
Signed-off-by: Sergei
On 2012-12-28 Friday at 23:40 +0400 Dmitry Voytik wrote:
> Add alternative vi-style keys for the menu navigation:
> / for down/up navigation, / for
> page down/up, / for first/last menu item selection
> and for entering to a submenu.
Good starting point, thanks for your initial work.
Here is
>From: Roland Eggner
• In function keys line descriptions black on darkblue are almost impossible
to read. Change colors to black on brown.
Signed-off-by: Roland Eggner
---
--- a/scripts/kconfig/nconf.gui.c 2012-11-16 17:47:22.0 +0100
+++ b/scripts/kconfig/nconf.gui.c
On Sat, Dec 29, 2012 at 12:08 PM, Joe Perches wrote:
> Sylvan Munaut did something similar
> https://lkml.org/lkml/2012/12/5/168
Missed that and duplicated the debugging :(
Sorry Sylvain.
I guess my patch may be preferable, since I happened to use the snprintf()
method that you suggest -- all
On Sat, Dec 29, 2012 at 9:56 AM, Greg Kroah-Hartman
wrote:
> Nice work. When did you start seeing this problem, 3.6 or so? I ask as
> it's probably something that should go to stable as well if so.
We happened to see it when we rebased to the 3.6 kernel, but as far as I
can see, the bug has
From: Rafael J. Wysocki
Commit 0090def6 (ACPI: Add interface to register/unregister device
to/from power resources) made it possible to indicate to the ACPI
core that if the given device depends on any power resources, then
it should be resumed as soon as all of the power resources required
by
Handle HKEY event generated on AC power change. The current message
asks users to submit data related to this event which leads to
a lot of confusion and noise on the mailing list.
The following is a list affected models and 'Message-Id'
from ibm-acpi-de...@lists.sourceforge.net of people who saw
On Saturday, December 29, 2012 12:03:13 PM Tim Hockin wrote:
> 4 days ago I had Ubuntu Lucid running on this computer. Suspend and
> resume worked flawlessly every time.
>
> Then I upgraded to Ubuntu Precise.
Well, do you use a distro kernel or a kernel.org kernel?
> Suspend seems to work, but
On Saturday, December 29, 2012 11:24:45 AM Larry Finger wrote:
> On 12/29/2012 07:27 AM, Rafael J. Wysocki wrote:
> > On Friday, December 28, 2012 07:55:20 PM Larry Finger wrote:
> >> Since commit 2aacdff entitled "cpufreq: Move common part from governors
> >> to separate file", whenever the
On Wed, Dec 26, 2012 at 11:32 AM, amit daniel kachhap
wrote:
>
> On Tue, Dec 18, 2012 at 9:45 PM, Doug Anderson wrote:
> > Amit,
> >
> > On Tue, Dec 18, 2012 at 8:17 PM, amit daniel kachhap
> > wrote:
> >> On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao wrote:
> >>> The cpu_thermal generic thermal
From: ahemaily
The variable dma_lch_count used for comparison (omap_dma_reserve_channels <=
dma_lch_count)
before it initialized to the value from omap_dma_dev_attr : d->lch_count.
I change the place of dma_lch_count initialization to be before the comparison.
Signed-off-by: Abdelrahman
On Sat, Dec 29, 2012 at 11:57:09AM -0800, David Decotigny wrote:
> In some cases, free_irq_cpu_rmap() is called while holding a lock
> (eg. rtnl). This can lead to deadlocks, because it invokes
> flush_scheduled_work() which ends up waiting for whole system
> workqueue to flush, but some pending
4 days ago I had Ubuntu Lucid running on this computer. Suspend and
resume worked flawlessly every time.
Then I upgraded to Ubuntu Precise. Suspend seems to work, but resume
fails every time. The video never initializes. By the flashing
keyboard lights, I guess it's a kernel panic. It fails from
On Sat, 2012-12-29 at 09:56 -0800, Greg Kroah-Hartman wrote:
> On Fri, Dec 28, 2012 at 08:23:04PM -0800, Roland Dreier wrote:
> > From: Roland Dreier
> >
> > print_prefix() passes a NULL buf to print_time() to get the length of
> > the time prefix; when printk times are enabled, the current code
In some cases, free_irq_cpu_rmap() is called while holding a lock
(eg. rtnl). This can lead to deadlocks, because it invokes
flush_scheduled_work() which ends up waiting for whole system
workqueue to flush, but some pending works might try to acquire the
lock we are already holding.
This commit
>> - int (*reg_read)(struct regmap *map, unsigned int reg, unsigned int
>> *val);
>> - int (*reg_write)(struct regmap *map, unsigned int reg, unsigned int
>> val);
>> + int (*reg_read)(void *context, unsigned int reg, unsigned int *val);
>> + int (*reg_write)(void *context,
On Fri, Dec 28, 2012 at 08:23:04PM -0800, Roland Dreier wrote:
> From: Roland Dreier
>
> print_prefix() passes a NULL buf to print_time() to get the length of
> the time prefix; when printk times are enabled, the current code just
> returns the constant 15, which matches the format "[%5lu.%06lu]
[1.] One line summary of the problem:
Random kernel panic and system freeze when watching video on my linux laptop
[2.] Full description of the problem/report:
I'm experiencing random (but frequent) kernel panics and system
freezes without panic information while I'm watching videos using
Hello.
On top of "uprobes: pre-filtering".
Srikar, If you still disagree and prefer to use ->filter() in
handler_chain() please argue.
Note that unapply_uprobe() added by this patch can be generalized
to implement uprobe_apply(consumer, mm, is_register).
Oleg.
--
To unsubscribe from this
Currrently the are 2 problems with pre-filtering:
1. It is not possible to add/remove a task (mm) after uprobe_register()
2. A forked child inherits all breakpoints and uprobe_consumer can not
control this.
This patch does the first step to improve the filtering. handler_chain()
removes the
On 12/29/2012 07:27 AM, Rafael J. Wysocki wrote:
On Friday, December 28, 2012 07:55:20 PM Larry Finger wrote:
Since commit 2aacdff entitled "cpufreq: Move common part from governors
to separate file", whenever the drivers that depend on this new file
(cpufreq_ondemand or cpufreq_conservative)
Ben Hutchings wrote:
> On Sat, 2012-12-29 at 00:07 -0800, Jonathan Nieder wrote:
>> Ben Hutchings wrote:
>>> The min/max call needed to have explicit types on some architectures
>>> (e.g. mn10300). Use clamp_t instead to avoid the warning:
>>>
>>> kernel/sys.c: In function 'override_release':
While remotely reading the cputime of a task running in a
full dynticks CPU, the values stored in utime/stime fields
of struct task_struct may be stale. Its values may be those
of the last kernel <-> user transition time snapshot and
we need to add the tickless time spent since this snapshot.
To
Allow to dynamically switch between tick and virtual based cputime accounting.
This way we can provide a kind of "on-demand" virtual based cputime
accounting. In this mode, the kernel will rely on the user hooks
subsystem to dynamically hook on kernel boundaries.
This is in preparation for beeing
This subsystem lacks many explanations on its purpose and
design. Add these missing comments.
Reported-by: Andrew Morton
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph Lameter
Cc: Geoff Levand
Cc: Gilad Ben Yossef
Cc: Hakan
Start with a very simple interface to define full dynticks CPU:
use a boot time option defined cpumask through the "full_nohz="
kernel parameter.
Make sure you keep at least one CPU outside this range to handle
the timekeeping.
Also full_nohz= must match rcu_nocb= value.
Suggested-by: Paul E.
Not for merge. This may become a real tracepoint.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph Lameter
Cc: Geoff Levand
Cc: Gilad Ben Yossef
Cc: Hakan Akkan
Cc: Ingo Molnar
Cc: Paul E. McKenney
Cc: Paul Gortmaker
Cc: Peter
Wake up a CPU when a timer list timer is enqueued there and
the CPU is in full dynticks mode. Sending an IPI to it makes
it reconsidering the next timer to program on top of recent
updates.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc:
Because we may update the execution time (sched_group_set_shares()->
update_cfs_shares()->reweight_entity()->update_curr()) before
reweighting the entity after updating the group shares and this requires
an uptodate version of the runqueue clock. Let's update it on the target
CPU if it
Just to avoid confusion.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph Lameter
Cc: Geoff Levand
Cc: Gilad Ben Yossef
Cc: Hakan Akkan
Cc: Ingo Molnar
Cc: Paul E. McKenney
Cc: Paul Gortmaker
Cc: Peter Zijlstra
Cc: Steven
move_tasks() and active_load_balance_cpu_stop() both need
to have the busiest rq clock uptodate because they may end
up calling can_migrate_task() that uses rq->clock_task
to determine if the task running in the busiest runqueue
is cache hot.
Hence if the busiest runqueue is tickless, update its
In this function we are making use of rq->clock right before the
update of the rq clock, let's just call update_rq_clock() just
before that to avoid using a stale rq clock value.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph
idle_balance() is called from schedule() right before we schedule the
idle task. It needs to record the idle timestamp at that time and for
this the rq clock must be accurate. If the CPU is running tickless
we need to update the rq clock manually.
Signed-off-by: Frederic Weisbecker
Cc: Alessio
[ ** BUGGY PATCH: I need to put more thinking into this ** ]
We want the nohz load balancer to be an idle CPU, thus
move that selection to strict dyntick idle logic.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph Lameter
Cc:
When a CPU is in full dynticks mode, try to switch
it to nohz mode from the interrupt exit path if it is
running a single non-idle task.
Then restart the tick if necessary if we are enqueuing a
second task while the timer is stopped, so that the scheduler
tick is rearmed.
[TODO: Check remaining
Not for merge, just for debugging.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph Lameter
Cc: Geoff Levand
Cc: Gilad Ben Yossef
Cc: Hakan Akkan
Cc: Ingo Molnar
Cc: Paul E. McKenney
Cc: Paul Gortmaker
Cc: Peter Zijlstra
Cc:
If RCU is waiting for the current CPU to complete a grace
period, don't turn off the tick. Unlike dynctik-idle, we
are not necessarily going to enter into rcu extended quiescent
state, so we may need to keep the tick to note current CPU's
quiescent states.
[added build fix from Zen Lin]
CHECKME:
If we are interrupting userspace, we don't need to keep
the tick for RCU: quiescent states don't need to be reported
because we soon run in userspace and local callbacks are handled
by the nocb threads.
CHECKME: Do the nocb threads actually handle the global
grace period completion for local
The last remaining user was oprofile and its use has been removed
a while ago on commit bc078e4eab65f11bbaeed380593ab8151b30d703
"oprofile: convert oprofile from timer_hook to hrtimer".
There doesn't seem to be any upstream user of this hook
for about two years now. And I'm not even aware of any
While trying to find a target for a non-pinned timer, use
the following logic:
- Use the closest (from a sched domain POV) busy CPU that
is not full dynticks
- If none, use the closest idle CPU that is not full dynticks.
So this is biased toward isolation over powersaving. This is
a quick hack
If either a per thread or a per process posix cpu timer is running,
don't stop the tick.
TODO: restart the tick if it is stopped and a posix cpu timer is
enqueued. Check we probably need a memory barrier for the per
process posix timer that can be enqueued from another task
of the group.
While load balancing an rq target, we look for the busiest group.
This operation may require an uptodate rq clock if we end up calling
scale_rt_power(). To this end, update it manually if the target is
running tickless.
DOUBT: don't we actually also need this in vanilla kernel, in case
this_cpu
On a full dynticks CPU, we want the RCU callbacks to be
offlined to another CPU, otherwise we need to keep
the tick to wait for the grace period completion.
Ensure the full dynticks CPU is also an rcu_nocb one.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc:
check_preempt_wakeup() of fair class needs an uptodate sched clock
value to update runtime stats of the current task.
When a task is woken up, activate_task() is usually called right before
ttwu_do_wakeup() unless the task is already in the runqueue. In this
case we need to update the rq clock
This way the full nohz CPUs can safely run with the tick
stopped with a guarantee that somebody else is taking
care of the jiffies and gtod progression.
NOTE: this doesn't handle CPU hotplug. Also we could use something
more elaborated wrt. powersaving if we have more than one non full-nohz
CPU
When a CPU in full dynticks mode doesn't respond to complete
a grace period, issue it a specific IPI so that it restarts
the tick and chases a quiescent state.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew Morton
Cc: Chris Metcalf
Cc: Christoph Lameter
Cc: Geoff
Because the sched_class::put_prev_task() callback of rt and fair
classes are referring to the rq clock to update their runtime
statistics. A CPU running in tickless mode may carry a stale value.
We need to update it there.
Signed-off-by: Frederic Weisbecker
Cc: Alessio Igor Bogani
Cc: Andrew
This is in preparation for the full dynticks feature. While
remotely reading the cputime of a task running in a full
dynticks CPU, we'll need to do some extra-computation. This
way we can account the time it spent tickless in userspace
since its last cputime snapshot.
Signed-off-by: Frederic
Hi,
So after I released 3.7-nohz1, I shut down the light then sat down
in front of an empty wall in my flat and waited in the darkness with
a black tea for december 21th's apocalypse.
But then after a few days, I've been thinking I should have taken a
second cup of tea with me.
So I eventually
If we want to stop the tick further idle, we need to be
able to account the cputime without using the tick.
Virtual based cputime accounting solves that problem by
hooking into kernel/user boundaries.
However implementing CONFIG_VIRT_CPU_ACCOUNTING require
to set low level hooks and involves
On 12/29/2012 07:27 AM, Rafael J. Wysocki wrote:
On Friday, December 28, 2012 07:55:20 PM Larry Finger wrote:
Since commit 2aacdff entitled "cpufreq: Move common part from governors
to separate file", whenever the drivers that depend on this new file
(cpufreq_ondemand or cpufreq_conservative)
The commit c8442118 introduced a struct wireless_dev pointer
as a second argument of the function pointers set_tx_power
and get_tx_power. This patch adds the missing arguments for
the wlan-ng driver.
Sparse warnings:
drivers/staging/wlan-ng/cfg80211.c:735:25: warning:
incorrect type in
On 29/12/12 13:13, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 13:01 Sat 29 Dec , Roland Stigge wrote:
>> On 29/12/12 11:20, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>> On 17:49 Sun 23 Dec , Roland Stigge wrote:
This set of patches adds:
* Block GPIO API to gpiolib
*
From: Alexander Schremmer
Support the Creative BT-D1 Bluetooth USB audio device. Before this
patch, Linux had trouble finding the correct USB descriptors and bailed
out with these messages:
no or invalid class specific endpoint descriptor
Now it still prints these messages on hotplug:
On Friday, December 28, 2012 07:55:20 PM Larry Finger wrote:
> Since commit 2aacdff entitled "cpufreq: Move common part from governors
> to separate file", whenever the drivers that depend on this new file
> (cpufreq_ondemand or cpufreq_conservative) are built as modules, a new
> module named
2012/12/26 Namhyung Kim :
> Hi Frederic,
>
> On Thu, 20 Dec 2012 19:33:07 +0100, Frederic Weisbecker wrote:
>> When a CPU is in full dynticks mode, try to switch
>> it to nohz mode from the interrupt exit path if it is
>> running a single non-idle task.
>>
>> Then restart the tick if necessary if
2012/12/26 Li Zhong :
> On Thu, 2012-12-20 at 19:32 +0100, Frederic Weisbecker wrote:
>> diff --git a/init/Kconfig b/init/Kconfig
>> index 60579d6..a64b3e8 100644
>> --- a/init/Kconfig
>> +++ b/init/Kconfig
>> @@ -340,7 +340,9 @@ config TICK_CPU_ACCOUNTING
>>
>> config VIRT_CPU_ACCOUNTING
>>
On 13:01 Sat 29 Dec , Roland Stigge wrote:
> Hi,
>
> On 29/12/12 11:20, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 17:49 Sun 23 Dec , Roland Stigge wrote:
> >> This set of patches adds:
> >>
> >> * Block GPIO API to gpiolib
> >> * Sysfs support for GPIO API, to provide userland access
On 29.12.2012 08:25, Hillf Danton wrote:
On Thu, Dec 27, 2012 at 11:42 PM, Zlatko Calusic
wrote:
On 21.12.2012 12:51, Hillf Danton wrote:
On Thu, Dec 20, 2012 at 7:25 AM, Zlatko Calusic
wrote:
static unsigned long balance_pgdat(pg_data_t *pgdat, int order,
Hi,
On 29/12/12 11:20, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 17:49 Sun 23 Dec , Roland Stigge wrote:
>> This set of patches adds:
>>
>> * Block GPIO API to gpiolib
>> * Sysfs support for GPIO API, to provide userland access
>> * Device interface for userland access (alternative to
Eric Wong wrote:
> Eric Wong wrote:
> > I'm finding ppoll() unexpectedly stuck when waiting for POLLIN on a
> > local TCP socket. The isolated code below can reproduces the issue
> > after many minutes (<1 hour). It might be easier to reproduce on
> > a busy system while disk I/O is happening.
On Fri, Dec 28, 2012 at 11:03:40PM +0100, Geert Uytterhoeven wrote:
> That's the first run. Now everything is in the buffer cache (assumed
> you have enough RAM), and try again...
Right, until you do something else on the box requiring just the right
amount of memory to overflow the buffer cache
The address should be bigger than dac_mmap_min_addr, because
a process with CAP_RAWIO can map a vma bellow mmap_min_addr.
Cc: Andrew Morton
Cc: Kees Cook
Cc: Cyrill Gorcunov
Cc: Serge Hallyn
Cc: "Eric W. Biederman"
Cc: Eric Paris
Cc: James Morris
Signed-off-by: Andrey Vagin
---
On Sat, 2012-12-29 at 00:07 -0800, Jonathan Nieder wrote:
> Ben Hutchings wrote:
>
> > The min/max call needed to have explicit types on some architectures
> > (e.g. mn10300). Use clamp_t instead to avoid the warning:
> >
> > kernel/sys.c: In function 'override_release':
> >
On 17:49 Sun 23 Dec , Roland Stigge wrote:
> This set of patches adds:
>
> * Block GPIO API to gpiolib
> * Sysfs support for GPIO API, to provide userland access
> * Device interface for userland access (alternative to sysfs)
> * Devicetree support to instantiate GPIO blocks via DT
> *
Hi Russ,
Is it possible you try this patch on your 2048 cpus ?
Thanks
-- Daniel
On 12/26/2012 11:01 AM, Daniel Lezcano wrote:
> The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
> a lock in the cpuidle_get_cpu_driver function. This function
> is used in the idle_call function.
On Friday 28 December 2012 20:53:10 Eric Dumazet wrote:
> On Fri, 2012-12-28 at 20:05 +0100, Martin Nybo Andersen wrote:
> > Hi list,
> >
> > Since the release of 3.7 my main computer has been panicking a couple of
> > times on both 3.7.0 and 3.7.1 because of a 'dma_map_area overflow xx bytes'.
>
On Wed, Dec 26, 2012 at 11:10 AM, Eric Dumazet wrote:
> I did some tests with your patches with following configuration :
>
> tc qdisc add dev eth0 root htb r2q 1000 default 3
> (to force a contention on qdisc lock, even with a multi queue net
> device)
>
> and 24 concurrent "netperf -t
The following patch adds support for the bluetooth part of
Gigabyte's GC-WB300D PCIe card (combo card with AR9462 WLAN
and ATH3012 BT).
On every boot there is an error from this device:
usb 2-1.7: string descriptor 0 read error: -22
But that doesn't seem to have any negative effect AFAICT.
It
T: Bus=02 Lev=02 Prnt=02 Port=06 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=04ca ProdID=3006 Rev= 0.02
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=81(I) Atr=03(Int.)
Hi,
It is good idea add this feature.
1: Can we let the "ret = hwspin_lock_tests(ops, hwlock);" add after
hwspin_lock_register_single have return
succeed, that can avoid test duplicated Or error lockid. Of course, If
this interface is intend to test soc hardware capability only, we can
put
1 - 100 of 212 matches
Mail list logo
