On Thursday 25 of October 2012 20:06:54 Heinz Diehl wrote:
On 25.10.2012, Paweł Sikora wrote:
what is the reason of loading nouveau driver for laptops
with nvidia optimus and enabling vga switcheroo
which doesn't work in such (optimus) cases.
You can safely compile a kernel without
On Thu, Oct 25, 2012 at 02:14:21PM -0700, Joe Perches wrote:
On Fri, 2012-10-26 at 02:30 +0800, Fengguang Wu wrote:
Hi Joe,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
pci/misc
head: 334a57560cf08a04f530aa5546b4c9379c622544
The function ptep_set_access_flags is only ever used to upgrade
access permissions to a page. That means the only negative side
effect of not flushing remote TLBs is that other CPUs may incur
spurious page faults, if they happen to access the same address,
and still have a PTE with the old
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git
tags/rdma-for-linus
Small batch of fixes for 3.7:
- Fix crash in error path in cxgb4
- Fix build error on 32 bits in mlx4
-
On 10/26/2012 02:29 PM, Stephen Warren wrote:
From: Stephen Warren swar...@nvidia.com
Modify cmd_dtc to run the C pre-processor on the input .dts file before
passing it to dtc for final compilation. This allows the use of #define
and #include within the .dts file.
While this change is small
On Fri, 2012-10-26 at 10:03 -0700, Mike Galbraith wrote:
The bug is in the patch that used sched_setscheduler_nocheck(). Plain
sched_setscheduler() would have replied -EGOAWAY.
sched_setscheduler_nocheck() should say go away too methinks. This
isn't about permissions, it's about not being
Hi,
On Fri, Oct 26, 2012 at 10:16:55AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [121025 23:55]:
On Thu, Oct 25, 2012 at 10:44:47AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [121024 23:24]:
Hi,
On Wed, Oct 24, 2012 at 05:48:07PM -0700, Tony Lindgren
On Fri, Oct 26, 2012 at 10:21:41AM -0700, Tony Lindgren wrote:
* Arnd Bergmann a...@arndb.de [121026 00:48]:
On Friday 26 October 2012, Felipe Balbi wrote:
+static void omap_init_ocp2scp(void)
+{
+ struct omap_hwmod *oh;
+ struct platform_device *pdev;
+
On 10/26/2012 10:06 AM, Shuah Khan wrote:
On Fri, 2012-10-26 at 09:45 -0700, David Daney wrote:
On 10/26/2012 09:01 AM, Shuah Khan wrote:
Add support for debug_dma_mapping_error() call to avoid warning from
debug_dma_unmap() interface when it checks for mapping error checked
status. Without
Hi Greg,
in the next few days with that change along with any modifications
necessary after a sparse sanity check.
We have a change that fixes things, but I wanted to check if you
had any additional comments before we send out more patches. In
all likelihood you'd probably already given up in
On Fri, 2012-10-26 at 13:43 +0800, Tang Chen wrote:
Hi Toshi,
On 10/26/2012 01:20 AM, Toshi Kani wrote:
...
Why do you need to call acpi_bus_trim(device,0) to stop the container
device first?
This issue was introduced by Lu Yinghai, I think he could give a better
answer than me. :)
On Fri, Oct 26, 2012 at 01:02:53PM -0700, Andy King wrote:
Hi Greg,
in the next few days with that change along with any modifications
necessary after a sparse sanity check.
We have a change that fixes things, but I wanted to check if you
had any additional comments before we send out
On Fri, Oct 26, 2012 at 12:46 PM, Kees Cook keesc...@chromium.org wrote:
I think there's value in being able to enable these protections at
build-time so there's no need for a distro to have to ship extra
files/lines, spend time setting it, etc.
The value in not having to change the distro is
On 10/24/2012 07:38 PM, Martin wrote:
On 10/24/2012 01:40 AM, Nix wrote:
It's true that in less than a week
probably not all that many people have rebooted often enough to trip
over this.
I hope.
[previous bug report]
First off let me apologize for not having the right follow-up headers,
* Felipe Balbi ba...@ti.com [121026 13:07]:
On Fri, Oct 26, 2012 at 10:21:41AM -0700, Tony Lindgren wrote:
* Arnd Bergmann a...@arndb.de [121026 00:48]:
On Friday 26 October 2012, Felipe Balbi wrote:
+static void omap_init_ocp2scp(void)
+{
+ struct omap_hwmod *oh;
On Thu, Oct 25, 2012 at 06:41:11PM +0900, Jun'ichi Nomura wrote:
[PATCH] dm: stay in blk_queue_bypass until queue becomes initialized
With 749fefe677 (block: lift the initial queue bypass mode on
blk_register_queue() instead of blk_init_allocated_queue()),
add_disk() eventually calls
On 10/26/2012 01:43 PM, Wallak wrote:
Chris Friesen wrote:
On 10/25/2012 04:49 PM, Wallak wrote:
I've a very annoying behavior with the linux-3.6.x kernels release, and
a monolithic configuration. The USB 2.0 drives are mapped first with
/dev/sda, /dev/sdb... devices, and than the SATA AHCI
Hi,
The latest round of perf parser changes broke my PEBS-LL patch series
(at the last minute). For PEBS-LL, I need to add to generic events but I want
to keep them PMU specific. As such, they need to live in the sysfs events
subdir: /sys/devices/cpu/events/mem-loads,
On Fri, Oct 26, 2012 at 1:12 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Fri, Oct 26, 2012 at 12:46 PM, Kees Cook keesc...@chromium.org wrote:
Would a single config item be acceptable? What would be an agreeable
way to enable this at build-time?
I dunno. Maybe a CONFIG_LOCKDOWN
On 26 Oct 2012, Martin spake thusly:
On 10/24/2012 07:38 PM, Martin wrote:
On 10/24/2012 01:40 AM, Nix wrote:
It's true that in less than a week
probably not all that many people have rebooted often enough to trip
over this.
I hope.
[previous bug report]
First off let me apologize
On Fri, Oct 26, 2012 at 02:00:36PM +, Liu, Jinsong wrote:
Updated per Jan's comments.
Thanks,
Jinsong
===
From e6d4eceba9538c6873f9c970425e65e257fd9bf0 Mon Sep 17 00:00:00 2001
From: Liu, Jinsong jinsong@intel.com
Date: Sat, 27 Oct 2012 05:34:50 +0800
Subject:
On Fri, Oct 26, 2012 at 1:23 PM, Kees Cook keesc...@chromium.org wrote:
I'd like it to be the exception to turn it _off_, rather than the
exception to turn it on.
Kees, you don't seem to understand.
Breaking applications is unacceptable. End of story. It's broken them.
Get over it.
On Sat, 2012-10-20 at 08:38 -0400, Mike Galbraith wrote:
So what I would do is either let the user decide once at boot, in which
case if off, creating groups would be stupid), or, just rip autogroup
completely out, since systemd is taking over the known universe anyway.
I'm traveling, but
From: Andi Kleen a...@linux.intel.com
Add histogram support for the transaction flags. Each flags instance becomes
a separate histogram. Support sorting and displaying the flags in report
and top.
The patch is fairly large, but it's really mostly just plumbing to pass the
flags around.
From: Andi Kleen a...@linux.intel.com
perf record has a new option -W that enables weightened sampling.
Add sorting support in top/report for the average weight per sample and the
total weight sum. This allows to both compare relative cost per event
and the total cost over the measurement
From: Andi Kleen a...@linux.intel.com
Add support for the v2 PEBS format. It has a superset of the v1 PEBS
fields, but has a longer record so we need to adjust the code paths.
The main advantage is the new EventingRip support which directly
gives the instruction, not off-by-one instruction. So
From: Andi Kleen a...@linux.intel.com
Haswell supplies the address for every PEBS memory event, so always fill it in
when the user requested it. It will be 0 when not useful (no memory access)
Signed-off-by: Andi Kleen a...@linux.intel.com
---
arch/x86/kernel/cpu/perf_event_intel_ds.c |4
[Updated version for the latest master tree and various fixes.
See end for details. This should be ready for merging now I hope.
Arnaldo, especially needs attention from you for the user space part.]
This adds perf PMU support for the upcoming Haswell core. The patchkit
is fairly large, mainly
From: Andi Kleen a...@linux.intel.com
Add LBR filtering for branch in transaction, branch not in transaction
or transaction abort. This is exposed as new sample types.
v2: Rename ABORT to ABORTTX
Signed-off-by: Andi Kleen a...@linux.intel.com
---
arch/x86/kernel/cpu/perf_event_intel_lbr.c |
From: Andi Kleen a...@linux.intel.com
Add basic Haswell PMU support.
Similar to SandyBridge, but has a few new events. Further
differences are handled in followon patches.
There are some new counter flags that need to be prevented
from being set on fixed counters.
Contains fixes from Stephane
From: Andi Kleen a...@linux.intel.com
When the LBR format is unknown disable LBR recording. This prevents
crashes when the LBR address is misdecoded and mis-sign extended.
Signed-off-by: Andi Kleen a...@linux.intel.com
---
arch/x86/kernel/cpu/perf_event_intel_lbr.c |3 ++-
1 files changed,
From: Andi Kleen a...@linux.intel.com
When an event fails to parse and it's not in a new style format,
try to parse it again as a cpu event.
This allows to use sysfs exported events directly without //, so I can use
perf record -e tx-aborts ...
instead of
perf record -e cpu/tx-aborts/
v2:
From: Andi Kleen a...@linux.intel.com
Extend the parser/lexer to allow generic event names like
instructions as a sysfs supplied PMU event name.
This resolves the problem that cpu/instructions/ gives a parse
error, even when the kernel supplies a instructions event
This is useful to add sysfs
From: Andi Kleen a...@linux.intel.com
Report all the supported arch perfmon events as event aliases in
/sys/devices/cpu/...
This is needed to use the TSX intx,intx_cp attributes with
symbolic events, at least for these basic events.
Currently cpu/instructions/ doesn't work because instructions
From: Andi Kleen a...@linux.intel.com
- looks nicer than _, so allow - in the event names. Used for various
of the arch perfmon and Haswell events.
Signed-off-by: Andi Kleen a...@linux.intel.com
---
tools/perf/util/parse-events.l |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
From: Andi Kleen a...@linux.intel.com
Add a instructions-p event alias that uses the PDIR randomized instruction
retirement event. This is useful to avoid some systematic sampling shadow
problems. Normally PEBS sampling has a systematic shadow. With PDIR
enabled the hardware adds some
From: Andi Kleen a...@linux.intel.com
List the kernel supplied pmu event aliases in perf list
It's better when the users can actually see them.
v2: Fix pattern matching
Signed-off-by: Andi Kleen a...@linux.intel.com
---
tools/perf/Documentation/perf-list.txt |4 +-
From: Andi Kleen a...@linux.intel.com
Implement the TSX transaction and checkpointed transaction qualifiers for
Haswell. This allows e.g. to profile the number of cycles in transactions.
The checkpointed qualifier requires forcing the event to
counter 2, implement this with a custom constraint
From: Andi Kleen a...@linux.intel.com
Add basic PEBS support for Haswell.
The constraints are similar to SandyBridge with a few new events.
v2: Readd missing pebs_aliases
v3: Readd missing hunk. Fix some constraints.
Signed-off-by: Andi Kleen a...@linux.intel.com
---
From: Andi Kleen a...@linux.intel.com
When a weighted sample is requested, first try to report the TSX abort cost
on Haswell. If that is not available report the memory latency. This
allows profiling both by abort cost and by memory latencies.
Memory latencies requires enabling a different PEBS
From: Andi Kleen a...@linux.intel.com
For some events it's useful to weight sample with a hardware
provided number. This expresses how expensive the action the
sample represent was. This allows the profiler to scale
the samples to be more informative to the programmer.
There is already the
From: Andi Kleen a...@linux.intel.com
With checkpointed counters there can be a situation where the counter
is overflowing, aborts the transaction, is set back to a non overflowing
checkpoint, causes interupt. The interrupt doesn't see the overflow
because it has been checkpointed. This is then
From: Andi Kleen a...@linux.intel.com
Add the glue in the user tools to record transaction flags with
--transaction (-T was already taken) and dump them.
Followon patches will use them.
Signed-off-by: Andi Kleen a...@linux.intel.com
---
tools/perf/Documentation/perf-record.txt |5 -
On 10/23/12 3:57 PM, Nix wrote:
[Bruce, Trond, I fear it may be hard for me to continue chasing this NFS
lockd crash as long as ext4 on 3.6.3 is hosing my filesystems like
this. Apologies.]
big snip
The only unusual thing about the filesystems on this machine are that
they have hardware
From: Andi Kleen a...@linux.intel.com
Add infrastructure to generate event aliases in /sys/devices/cpu/events/
And use this to set up user friendly aliases for the common TSX events.
TSX tuning relies heavily on the PMU, so it's important to be user friendly.
This replaces the generic
From: Andi Kleen a...@linux.intel.com
Add a generic qualifier for transaction events, as a new sample
type that returns a flag word. This is particularly useful
for qualifying aborts: to distinguish aborts which happen
due to asynchronous events (like conflicts caused by another
CPU) versus
From: Andi Kleen a...@linux.intel.com
The callers of parse_events usually have their own error handling.
Move the fprintf for a bad event to parse_events_options, which
is the only one who should need it.
Signed-off-by: Andi Kleen a...@linux.intel.com
---
tools/perf/util/parse-events.c | 10
From: Andi Kleen a...@linux.intel.com
Add a precise qualifier, like cpu/event=0x3c,precise=1/
This is needed so that the kernel can request enabling PEBS
for TSX events. The parser bails out on any sysfs parse errors,
so this is needed in any case to handle any event on the TSX
perf kernel.
From: Andi Kleen a...@linux.intel.com
Add support to perf stat to print the basic transactional execution statistics:
Total cycles, Cycles in Transaction, Cycles in aborted transsactions
using the intx and intx_checkpoint qualifiers.
Transaction Starts and Elision Starts, to compute the average
From: Andi Kleen a...@linux.intel.com
Recent Intel CPUs have a new alternative MSR range for perfctrs that allows
writing the full counter width. Enable this range if the hardware reports it
using a new capability bit. This lowers overhead of perf stat slightly because
it has to do less
From: Andi Kleen a...@linux.intel.com
I had some problems with spurious PMIs, so print the PMU state
on a spurious one. This will not interact well with other NMI users.
Disabled by default, has to be explicitely enabled through sysfs.
Optional, but useful for debugging.
v2: Move to
From: Andi Kleen a...@linux.intel.com
This is not arch perfmon, but older CPUs will just ignore it. This makes
it possible to do at least some TSX measurements from a KVM guest
Cc: a...@redhat.com
Cc: g...@redhat.com
v2: Various fixes to address review feedback
v3: Ignore the bits when no CPUID.
On 26 Oct 2012, Eric Sandeen outgrape:
On 10/23/12 3:57 PM, Nix wrote:
The only unusual thing about the filesystems on this machine are that
they have hardware RAID-5 (using the Areca driver), so I'm mounting with
'nobarrier': the full set of options for all my ext4 filesystems are:
From: Andi Kleen a...@linux.intel.com
Extend the perf branch sorting code to support sorting by intx
or abort qualifiers. Also print out those qualifiers.
Signed-off-by: Andi Kleen a...@linux.intel.com
---
tools/perf/builtin-report.c |3 +-
tools/perf/builtin-top.c|4 ++-
From: Andi Kleen a...@linux.intel.com
The --sort documentation for top and report was hopelessly out-of-date
Instead of having two more places that would need to be updated,
just point to --help.
Signed-off-by: Andi Kleen a...@linux.intel.com
---
tools/perf/Documentation/perf-report.txt |2
From: Andi Kleen a...@linux.intel.com
In the PEBS handler report the transaction flags using the new
generic transaction flags facility. Most of them come from
the tsx_tuning field in PEBSv2, but the abort code is derived
from the RAX register reported in the PEBS record.
Signed-off-by: Andi
From: Andi Kleen a...@linux.intel.com
So that the browser still shows the abort label
Signed-off-by: Andi Kleen a...@linux.intel.com
---
tools/perf/util/annotate.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/tools/perf/util/annotate.c b/tools/perf/util/annotate.c
From: Andi Kleen a...@linux.intel.com
Haswell has two additional LBR from flags for TSX: intx and abort, implemented
as a new v4 version of the LBR format.
Handle those in and adjust the sign extension code to still correctly extend.
The flags are exported similarly in the LBR record to the
From: Andi Kleen a...@linux.intel.com
Make perf report -j aware of the new intx,notx,abort branch qualifiers.
v2: ABORT - ABORTTX
Signed-off-by: Andi Kleen a...@linux.intel.com
---
tools/perf/Documentation/perf-record.txt |3 +++
tools/perf/builtin-record.c |3 +++
2 files
On 10/26/2012 10:24 PM, Nix wrote:
On 26 Oct 2012, Martin spake thusly:
[...]
I have studied my corruption problem more closely and can give you a
description of what happened below. Would you say this may be the same
bug?
No. You want to keep up with the thread. Ted's first educated guess
On 26 Oct 2012, Martin said:
On 10/26/2012 10:24 PM, Nix wrote:
On 26 Oct 2012, Martin spake thusly:
Computer is booted again in order to copy a few files to memory stick.
Unbeknownst to me, the following entries are logged in the
system log:
Oct 15 20:00:16 harold kernel: EXT4-fs error
On Fri, Oct 26, 2012 at 5:29 AM, Vinod Koul vk...@infradead.org wrote:
git://git.infradead.org/users/vkoul/slave-dma.git fixes
git.infradead.org is sick, and is apparently not accepting connections...
Can you check whether git-daemon is actually running there? The
machine is pinging ok.
Hi Tony,
@@ -124,6 +156,12 @@ static int __devinit pwm_probe(struct
platform_device *pdev)
chip-chip.base = -1;
chip-chip.npwm = VT8500_NR_PWMS;
+ chip-clk = devm_clk_get(pdev-dev, NULL);
+ if (IS_ERR_OR_NULL(chip-clk)) {
+ dev_err(pdev-dev, clock source
On Fri, 26 Oct 2012, Peter LaDow wrote:
(I've added netfilter and linux-rt-users to try to pull in more help).
On Fri, Oct 26, 2012 at 9:48 AM, Eric Dumazet eric.duma...@gmail.com wrote:
Upstream kernel is fine, there is no race, as long as :
local_bh_disable() disables BH and
On Thursday 25 October 2012, Nicolas Ferre wrote:
ARM: at91: fix external interrupts in non-DT case
This patch now leads to build errors with at91x40_defconfig,
which I've fixed up by applying the patch below on top.
Please yell if this is not the right fix.
Arnd
commit
On Fri, Oct 26, 2012 at 09:37:08PM +0100, Nix wrote:
I can reproduce this on a small filesystem and stick the image somewhere
if that would be of any use to anyone. (If I'm very lucky, merely making
this offer will make the problem go away. :} )
I'm not sure the image is going to be that
On 10/26/2012 01:05 AM, Daniel Vetter wrote:
On Fri, Oct 26, 2012 at 6:43 AM, Justin P. Mattock
justinmatt...@gmail.com wrote:
No worries, it is another ILK hang similar to the ones reported earlier
- it just seems the ring stops advancing. Hopefully it is a missing w/a
from
On 26 Oct 2012, Theodore Ts'o stated:
On Fri, Oct 26, 2012 at 09:37:08PM +0100, Nix wrote:
I can reproduce this on a small filesystem and stick the image somewhere
if that would be of any use to anyone. (If I'm very lucky, merely making
this offer will make the problem go away. :} )
I'm
On Fri, 2012-10-26 at 11:51 -0700, Peter LaDow wrote:
(I've added netfilter and linux-rt-users to try to pull in more help).
On Fri, Oct 26, 2012 at 9:48 AM, Eric Dumazet eric.duma...@gmail.com wrote:
Upstream kernel is fine, there is no race, as long as :
local_bh_disable() disables BH
On Fri, 26 Oct 2012 14:45:02 -0400
Rik van Riel r...@redhat.com wrote:
Intel has an architectural guarantee that the TLB entry causing
a page fault gets invalidated automatically. This means
we should be able to drop the local TLB invalidation.
Because of the way other areas of the page
On Friday, October 26, 2012 08:01:49 PM Oleg Nesterov wrote:
On 10/26, Tejun Heo wrote:
Acked-by: Tejun Heo t...@kernel.org
Thanks!
Rafael, sorry that this one doesn't have pm cc'd
Ah, sorry Rafael. Yes, I have read you email, and I was going to
add linux-pm but forgot.
but
This looks very different. The symptoms are quite different, and it's
most likely that an unclean shutdown is involved. In your case,
you're doing clean shutdowns, with some suspend/resume cycles thrown
in. Also, kernel version 3.5.5 doesn't have the commits that were
added between 3.6.1 and
On Friday 26 October 2012, Chris Brand wrote:
@@ -124,6 +156,12 @@ static int __devinit pwm_probe(struct
platform_device *pdev)
chip-chip.base = -1;
chip-chip.npwm = VT8500_NR_PWMS;
+ chip-clk = devm_clk_get(pdev-dev, NULL);
+ if (IS_ERR_OR_NULL(chip-clk)) {
+
This isn't the first time that journal_checksum has proven problematic.
It's a shame that we're stuck between two error-inducing stools here...
The problem is that it currently bails out be aborting the entire
journal replay, and the file system will get left in a mess when it
does that. It's
Hi Linus,
Please pull from the git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
pm+acpi-for-3.7-rc3
to receive power management and ACPI fixes for v3.7-rc3 with top-most commit
879dca019dc43a1622edca3e7dde644b14b5acc5
ACPI: missing break
on top of
On 26 Oct 2012, Theodore Ts'o uttered the following:
The plan is that eventually, we will have checksums on a
per-journalled block basis, instead of a per-commit basis, and when we
get a failed checksum, we skip the replay of that block,
But not of everything it implies, since that's quite
On 10/26/2012 01:23 PM, Kees Cook wrote:
Every distro will ship with this enabled (except perhaps Damn
Vulnerable Linux), so why make it harder?
So please remind me why can't it be on by default in code.
And the normal sysctl to turn it off for these who want to
experiment with filesystem
On Fri, Oct 26, 2012 at 2:05 PM, Eric Dumazet eric.duma...@gmail.com wrote:
Do you know what is per cpu data in linux kernel ?
I sorta did. But since your response, I did more reading, and now I
see what you mean. But I don't think this is a per cpu issue. More
below.
Because its not
On Friday, October 26, 2012 11:14:17 PM Rafael J. Wysocki wrote:
On Friday, October 26, 2012 08:01:49 PM Oleg Nesterov wrote:
On 10/26, Tejun Heo wrote:
Acked-by: Tejun Heo t...@kernel.org
Thanks!
Rafael, sorry that this one doesn't have pm cc'd
Ah, sorry Rafael. Yes, I
Hello,
On Fri, Oct 26, 2012 at 11:29:56PM +0200, Rafael J. Wysocki wrote:
Actually, what tree is it supposed to apply to?
The change in kernel/cgroup_freezer.c doesn't look like anything in
the current Linus' tree to me.
Ooh, right. This depends on the earlier cgroup_freezer changes.
Sorry
This is what we usually expect at this stage of the game, lots of
little things, mostly in drivers. With the occaisional oops didn't
mean to do that kind of regressions in the core code.
1) Uninitialized data in __ip_vs_get_timeouts(), from Arnd Bergmann
2) Reject invalid ACK sequences in Fast
Changelog
v2 - v3
- Create patches 6/7 and 7/7 to work with an existing format of variable name
v1 - v2
- Separate into 5 patches in accordance with Mike's comment
- Erase an extra line of comment in patch 1/5
[Issue]
Currently, efi_pstore driver simply overwrites existing panic
[Issue]
As discussed in a thread below, Running out of space in EFI isn't a well-tested
scenario.
And we wouldn't expect all firmware to handle it gracefully.
http://marc.info/?l=linux-kernelm=134305325801789w=2
On the other hand, current efi_pstore doesn't check a remaining space of
storage
On Fri, 2012-10-26 at 15:10 -0400, David Miller wrote:
From: David Miller da...@davemloft.net
Date: Fri, 26 Oct 2012 15:01:53 -0400 (EDT)
From: Shuah Khan shuah.k...@hp.com
Date: Fri, 26 Oct 2012 10:13:09 -0600
Add support for debug_dma_mapping_error() call to avoid warning from
[Issue]
Currently, efi_pstore driver simply overwrites existing panic messages in NVRAM.
So, in the following scenario, we will lose 1st panic messages.
1. kernel panics.
2. efi_pstore is kicked and writes panic messages to NVRAM.
3. system reboots.
4. kernel panics again before a user
[Issue]
Currently, efi_pstore driver simply overwrites existing panic messages in NVRAM.
So, in the following scenario, we will lose 1st panic messages.
1. kernel panics.
2. efi_pstore is kicked and writes panic messages to NVRAM.
3. system reboots.
4. kernel panics again before a user checks
On Fri, Oct 26, 2012 at 1:27 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Fri, Oct 26, 2012 at 1:23 PM, Kees Cook keesc...@chromium.org wrote:
I'd like it to be the exception to turn it _off_, rather than the
exception to turn it on.
Kees, you don't seem to understand.
[Issue]
Currently, a variable name, which is used to identify each log entry, consists
of type,
id and ctime. But an erase callback does not use ctime.
If efi_pstore supported just one log, type and id were enough.
However, in case of supporting multiple logs, it doesn't work because
it can't
[Issue]
Currently, a variable name, which identifies each entry, consists of type, id
and ctime.
But if multiple events happens in a short time, a second/third event may fail
to log because
efi_pstore can't distinguish each event with current variable name.
[Solution]
A reasonable way to
[Issue]
A format of variable name has been updated to type, id, count and ctime
to support holding multiple logs.
Format of current variable name
dump-type0-1-2-12345678
type:0
id:1
count:2
ctime:12345678
On the other hand, if an old variable name before being updated
remains, users
[Issue]
A format of variable name has been updated to type, id, count and ctime
to support holding multiple logs.
Format of current variable name
dump-type0-1-2-12345678
type:0
id:1
count:2
ctime:12345678
On the other hand, if an old variable name before being updated
remains, users
On Fri, 2012-10-26 at 13:49 -0700, Linus Torvalds wrote:
On Fri, Oct 26, 2012 at 5:29 AM, Vinod Koul vk...@infradead.org
wrote:
git://git.infradead.org/users/vkoul/slave-dma.git fixes
git.infradead.org is sick, and is apparently not accepting
connections...
Can you check whether
On 10/02/2012 01:17 PM, Dan Magenheimer wrote:
If so, shake hands and move forward? What do you see as next steps?
I've been reviewing the changes between zcache and zcache2 and getting
a feel for the scope and direction of those changes.
- Getting the community engaged to review zcache1 at
On Fri, 2012-10-26 at 13:07 -0700, David Daney wrote:
On 10/26/2012 10:06 AM, Shuah Khan wrote:
On Fri, 2012-10-26 at 09:45 -0700, David Daney wrote:
On 10/26/2012 09:01 AM, Shuah Khan wrote:
Add support for debug_dma_mapping_error() call to avoid warning from
debug_dma_unmap() interface
On Fri, 26 Oct 2012, Peter LaDow wrote:
On Fri, Oct 26, 2012 at 2:05 PM, Eric Dumazet eric.duma...@gmail.com wrote:
If this were safe, we wouldn't be seeing this lockup and your patch
wouldn't be needed. So it seems that your patch doesn't really
address the issue that we are not sure a
Systems running with Yama enabled expect restrictions on various
potentially dangerous operations that could create backward-compaibility
issues with rare userspace corner-cases. Since 561ec64ae67e (VFS:
don't do protected {sym,hard}links by default) has disabled VFS link
restrictions by default,
On Fri, Oct 26, 2012 at 7:19 AM, Alan Cox a...@lxorguk.ukuu.org.uk wrote:
So we only need to check this in serial8250_handle_irq when IIR indicates
a data timeout interrupt ?
Can we do
if ((iir 0x0F) == 0x0C) {
/* Expensive RDI check */
}
Alan
On Fri, 26 Oct 2012, Thomas Gleixner wrote:
Dear RT Folks,
I'm pleased to announce the 3.6.3-rt7 release.
Changes since 3.6.3-rt6:
* Enable SLUB for RT
Last time I looked at SLUB for RT (some years ago) it was just
way more painful than dealing with SLAB, but Christoph
Hi Guys,
I am debugging a reported kmemleak involving a sierra wireless MC8705 connected
through isp1763 on powerpc linux-3.0.22
We are still isolating the exact trigger, but this is a pretty good one so far
send at!reset to the modem control tty, wait until it finishes rebooting
then try to
The patch works around two UART interrupt bugs when the serial console is
flooded with inputs:
1. syslog shows serial8250: too much works for irq
2. serial console stops responding to key stroke
serial8250_handle_irq() checks UART_IIR_RDI before reading receive fifo
and clears bogus interrupt
1101 - 1200 of 1238 matches
Mail list logo
