From: Ananth N Mavinakayanahalli [EMAIL PROTECTED]
Move kprobes examples from Documentation/kprobes.txt to under samples/.
Patch originally by Randy Dunlap.
o Updated the patch to apply on 2.6.24-rc6-mm1
o Modified examples code to build on multiple architectures. Currently,
the examples code
Andi Kleen a écrit :
They now look like
hal-resmgr[13791]: segfault at 3c rip 2b9c8caec182 rsp 7fff1e825d30 error 4 in
libacl.so.1.1.0[2b9c8caea000+6000]
This makes it easier to pinpoint bugs to specific libraries.
And printing the offset into a mapping also always allows to find the
On Thu, Jan 03, 2008 at 01:50:20PM +0800, Dave Young wrote:
Convert semaphore to mutex in struct class.
...
One lockdep warning detected as following, thus use mutex_lock_nested with
SINGLE_DEPTH_NESTING in class_device_add
Jan 3 10:45:15 darkstar kernel:
On Wed, Jan 02, 2008 at 08:05:14PM -0800, Harvey Harrison wrote:
Thanks for the cleanup...
...
diff --git a/arch/x86/mm/fault_32.c b/arch/x86/mm/fault_32.c
index a2273d4..f2e909b 100644
--- a/arch/x86/mm/fault_32.c
+++ b/arch/x86/mm/fault_32.c
@@ -33,28 +33,6 @@
extern void die(const
On Thu, Jan 03, 2008 at 08:06:09AM +0100, Jarek Poplawski wrote:
On Thu, Jan 03, 2008 at 01:50:20PM +0800, Dave Young wrote:
Convert semaphore to mutex in struct class.
...
One lockdep warning detected as following, thus use mutex_lock_nested with
SINGLE_DEPTH_NESTING in class_device_add
On Jan 3, 2008 3:24 PM, Jarek Poplawski [EMAIL PROTECTED] wrote:
On Thu, Jan 03, 2008 at 08:06:09AM +0100, Jarek Poplawski wrote:
On Thu, Jan 03, 2008 at 01:50:20PM +0800, Dave Young wrote:
Convert semaphore to mutex in struct class.
...
One lockdep warning detected as following, thus
On Wed, Jan 02, 2008 at 02:12:28PM -0800, Roland McGrath wrote:
I have no opinions about the config symbol names. Among the existing
precedents for internal/descriptionless symbols I find more not using the
HAVE_ prefix than those using it.
The convention is newly established - so no suprise.
The following patch series brings to vanilla Linux a bit of the RT kernel
trace facility. This incorporates the -pg profiling option of gcc
that will call the mcount function for all functions called in
the kernel.
This patch series implements the code for x86 (32 and 64 bit), but
other archs
The design is for mcount based tracers to be added thru the
lib/mcount/tracer_interface.h file, just like mcount users should add
themselves to lib/mcount/mcount.h. A Kconfig rule chooses the right MCOUNT and
MCOUNT_TRACER user.
This is to avoid function call costs for something that is supposed
Add /debugfs/mctracer/trace to output trace output.
Here's an example of the content.
CPU 0: [80494691] notifier_call_chain+0x16/0x60 --
[80494701] __atomic_notifier_call_chain+0x26/0x56
CPU 0: [802161c8] mce_idle_callback+0x9/0x2f --
[804946b3]
From patch-2.6.21.5-rt20. Annotates functions that should not be profiler
instrumented, i.e. where mcount should not be called at function entry.
Signed-off-by: Arnaldo Carvalho de Melo [EMAIL PROTECTED]
Signed-off-by: Steven Rostedt [EMAIL PROTECTED]
---
arch/x86/kernel/apic_32.c |2 +-
Mark with notrace functions in core code that should not be
traced. The notrace attribute will prevent gcc from adding
a call to mcount on the annotated funtions.
Signed-off-by: Arnaldo Carvalho de Melo [EMAIL PROTECTED]
Signed-off-by: Steven Rostedt [EMAIL PROTECTED]
---
Add the notrace annotations to some of the vsyscall functions.
Note: checkpatch errors on the define of vsyscall_fn because it thinks
that it is a complex macro that needs paranthesis. Unfortunately
we can't put paranthesis on this macro.
Signed-off-by: Steven Rostedt [EMAIL PROTECTED]
---
If CONFIG_MCOUNT is selected and /proc/sys/kernel/mcount_enabled is set to a
non-zero value the mcount routine will be called everytime we enter a kernel
function that is not marked with the notrace attribute.
The mcount routine will then call a registered function if a function
happens to be
MCOUNT will disable the regparm parameters of the i386 compile
options. When doing so, this breaks the prototype of do_IRQ
where the fastcall must be explicitly called.
Also fixed some whitespace damage in the call to do_IRQ.
Signed-off-by: Steven Rostedt [EMAIL PROTECTED]
---
This patch adds an interface into debugfs.
/debugfs/mctracer/ctrl
echoing 1 into the ctrl file turns on the tracer,
and echoing 0 turns it off.
Signed-off-by: Steven Rostedt [EMAIL PROTECTED]
---
lib/mcount/tracer.c | 87 +++-
This adds the task comm and pid to the trace output. This gives the
output like:
CPU 0: sshd:2605 [80251858] remove_wait_queue+0xc/0x4a --
[802ad7be] free_poll_entry+0x1e/0x2a
CPU 2: bash:2610 [8038c3aa] tty_check_change+0x9/0xb6 --
[8038d295]
Add notrace annotation to x86_64 specific files.
Signed-off-by: Arnaldo Carvalho de Melo [EMAIL PROTECTED]
Signed-off-by: Steven Rostedt [EMAIL PROTECTED]
---
arch/x86/kernel/head64.c |2 +-
arch/x86/kernel/nmi_64.c |2 +-
arch/x86/kernel/setup64.c |4 ++--
The trace output is very verbose with outputing both the
IP address (Instruction Pointer not Internet Protocol!)
and the kallsyms symbol. So if kallsyms is configured into
the kernel, another file is created in the debugfs system.
This is the trace_symonly file that leaves out the IP address.
On Thu, Jan 03, 2008 at 03:21:36PM +0800, Dave Young wrote:
...
I don't know if there's other possible warning places with this mutex
or not, if you have any ideas about this, please tell me.
I think lockdep is just to tell such things. So, the question is, how
much it was tested already,
On Wednesday 02 January 2008, Bryan Wu wrote:
B.T.W, 2 questions about the MUSB driver:
1. What's the plan for mainline merge of the whole MUSB driver? maybe
I can cleanup current Blackfin ports to you guys.
It might as well merge in 2.6.25-early. It'll be easier to integrate
patches that
On Wed 2 Jan 2008 22:43, David Brownell pondered:
This patch might be improved slightly -- in ways that, as I
understand things, could save some RAM on Blackfin! -- by
having the BLACKLIST_HUB option get rid of the transaction
translator support (changing C code not just Kconfig).
It's pretty
James Morris wrote:
On Fri, 28 Dec 2007, KaiGai Kohei wrote:
Remaining issues:
- We have to mount securityfs explicitly, or use /etc/fstab.
It can cause a matter when we want to use this feature on
very early phase on boot. (like /sbin/init)
Why can't early userspace itself mount
From: Christoph Hellwig <[EMAIL PROTECTED]>
Date: Wed, 2 Jan 2008 07:50:33 +
> The only non-kernel user of this known to me is silo, which should just
> have it's own header documenting the solaris sparc ufs variant it needs
> to understand, possibly by using a copy of the kernel version at
Andrew Morgan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> KaiGai Kohei wrote:
>> Remaining issues:
>> - We have to mount securityfs explicitly, or use /etc/fstab.
>> It can cause a matter when we want to use this feature on
>> very early phase on boot. (like /sbin/init)
>
>
On Wed, Jan 02, 2008 at 12:04:44AM -0800, David Miller wrote:
> From: Christoph Hellwig <[EMAIL PROTECTED]>
> Date: Wed, 2 Jan 2008 07:50:33 +
>
> > The only non-kernel user of this known to me is silo, which should just
> > have it's own header documenting the solaris sparc ufs variant it
On Dec 28, 2007 3:12 AM, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
> * pci_map_sg() -> dma_map_sg() in ide_build_sglist().
>
> * pci_unmap_sg() -> dma_unmap_sg() in ide_destroy_dmatable().
>
> There should be no functionality changes caused by this patch except
> for blackfin arch whose
* Miguel Botón <[EMAIL PROTECTED]> wrote:
> These hardlocks start to appear with commit
> f10c1cfd359660c01446807b6c2bc8ce3aee919a
thanks, that's really useful! I dont see anything obviously wrong with
the commit though, and cannot (yet) reproduce it, so to help us track it
down further,
Hi Bart,
here's the unfinished redux of ide-floppy which i'm sending now so that we could
sinchronize trees. There are some things left to be done which are not so
trivial and i'd like to give them a bit more thought :).
drivers/ide/ide-floppy.c | 1248
On Wed, 2008-01-02 at 14:42 +0800, WANG Cong wrote:
> diff --git a/arch/s390/kernel/Makefile b/arch/s390/kernel/Makefile
> index 56cb710..b3b650a 100644
> --- a/arch/s390/kernel/Makefile
> +++ b/arch/s390/kernel/Makefile
> @@ -31,7 +31,3 @@ S390_KEXEC_OBJS := machine_kexec.o crash.o
>
On Die, 2008-01-01 at 22:58 -0600, Matt Domsch wrote:
> On Mon, Dec 31, 2007 at 12:39:11PM +0700, Theewara Vorakosit wrote:
> > Hello,
> >
> > I get MAC address from ioctl. However, ifconfig can change this MAC
> > address. Can I get a real physical MAC address of the NIC?
>
> yes. It's
* Carlos R. Mafra <[EMAIL PROTECTED]> wrote:
> On Tue 1.Jan'08 at 17:05:49 -0800, Carlos R. Mafra wrote:
> > This patch fixes most errors detected by checkpatch.pl.
> > [...]
>
> As pointed out by Jesper Juhl, my patch was not inlined :-(
ah. This explains why your patch had 'whitespace
On Wed, Jan 02, 2008 at 10:25:05AM +0100, Borislav Petkov wrote:
by the way, i messed up the numbering of the patches: their correct count is not
12 but 10 so you shouldn't be missing any even if it seems so at a first glance.
--
Regards/Gruß,
Boris.
--
To unsubscribe from this list: send
On Wed, Jan 02, 2008 at 10:31:35AM +0100, Martin Schwidefsky wrote:
> On Wed, 2008-01-02 at 14:42 +0800, WANG Cong wrote:
> > diff --git a/arch/s390/kernel/Makefile b/arch/s390/kernel/Makefile
> > index 56cb710..b3b650a 100644
> > --- a/arch/s390/kernel/Makefile
> > +++ b/arch/s390/kernel/Makefile
This is did not happen before; I am not sure right now what caused this (i.e.
battery aging or some software change) nor whether this is
kernel/HAL/kpowersave
issue.
kpowersave is stuck at assuming battery is loading and at 94%. Sysfs displays
battery state as Full:
UEVENT[1199264702.345795]
On Tue, Jan 01, 2008 at 12:12:22PM +0200, Benny Halevy wrote:
> checkpatch.pl does not recognize #elif as a preprocessor directive
> causing it to print bogus errors for, e.g.:
> ERROR: need consistent spacing around '&' (ctx:WxV)
> when the operator is not recognized as unary in this context.
>
On Tue, Jan 01, 2008 at 03:13:11PM +0800, WANG Cong wrote:
>
> TOPDIR is obsolete, use srctree or objtree instead.
>
> This patch set removes all the TOPDIR use in the whole
> source tree and finally drops it in the top Makefile.
> They're against the current linus-tree.
>
> Note that Patch
(Not so) recently, ACPI events started appearing as
key press events over linux input subsystem. The
question regarding this is simple: how it's supposed
to be handled?
First of all, I don't know any software so far that
can handle input layer in userspace when not running
X. In X, it's usually
On Tue, Jan 01, 2008 at 06:15:46PM +0200, Boaz Harrosh wrote:
> I have this code:
>
>
> /*
> * osd-r10 4.12.5 Data-In and Data-Out buffer offsets
> * byte offset = mantissa * (2^(exponent+8))
> */
> typedef __be32 osd_cdb_offset;
>
> osd_cdb_offset __osd_encode_offset(u64 offset, unsigned
I think it's more reasonable to only apply this rule onto AMD platform.
BRs
Peer Chen
-Original Message-
From: Eric W. Biederman [mailto:[EMAIL PROTECTED]
Sent: Monday, December 24, 2007 7:49 PM
To: Peer Chen
Cc: peerchen; linux-kernel; akpm; Andy Currid
Subject: Re: [PATCH] msi: set
On Wed, 2 Jan 2008, KaiGai Kohei wrote:
> > Another issue is that securityfs depends on CONFIG_SECURITY, which might be
> > undesirable, given that capabilities are a standard feature.
>
> We can implement this feature on another pseudo filesystems.
> Do you think what filesystem is the best
* Alan Cox <[EMAIL PROTECTED]> wrote:
> > udelay is supposed to be reliable. If someone runs a new kernel and
> > has no TSC (which might happen even on modern hardware or with
> > notsc) _and_ finds that udelay is not calibrated well enough then
> > that's a kernel bug we want to fix.
>
>
* H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> Christer Weinigel wrote:
>>
>> out 80h, al is only two bytes. Any alternative that has been suggested
>> in this discussion will use more space. mov dx, alt_port; out dx, al
>> will be larger, a function call will definitely be a lot larger. People
On Tue, Jan 01, 2008 at 06:15:46PM +0200, Boaz Harrosh wrote:
> I have this code:
>
>
> /*
> * osd-r10 4.12.5 Data-In and Data-Out buffer offsets
> * byte offset = mantissa * (2^(exponent+8))
> */
> typedef __be32 osd_cdb_offset;
Given that you can't do normal arithmetic on this type it
Am Dienstag 01 Januar 2008 schrieb Pavel Machek:
> Hi1
>
> > I would like to request a feature in the Linux kernel that would allow
> > a user to unplug a live read-only root file system which exists on a
> > detachable storage device such as a USB key drive. The desired
> > behavior is that once
Greg,
find the patch from Piotr Roszatycki, submitted to:
http://bugzilla.kernel.org/show_bug.cgi?id=9626
as an email plain-text patch submission below.
Ingo
>
Subject: usb: add support for 4348:5523 WinChipHead USB->RS 232 adapter with
Prolifec PL 2303 chipset
From:
Theodore Tso <[EMAIL PROTECTED]> wrote:
>
> The question is whether the size of the Unix domain sockets support is
> worth the complexity of yet another config option that we expose to
> the user. For the embedded world, OK, maybe they want to save 14k of
> non-swappable memory. But for the
On Monday 31 December 2007 00:10, Ingo Molnar wrote:
> * Herbert Xu <[EMAIL PROTECTED]> wrote:
> > > Ingo, it's not good that we have cond_resched() definitions
> > > conditionally duplicated in kernel.h - that's increasing the risk of
> > > bugs like this one.
> >
> > Actually, why do we even
Andrey Borzenkov wrote:
This is did not happen before; I am not sure right now what caused this (i.e.
battery aging or some software change) nor whether this is kernel/HAL/kpowersave
issue.
kpowersave is stuck at assuming battery is loading and at 94%. Sysfs displays
battery state as Full:
Am Montag, 31. Dezember 2007 15:44:47 schrieb Pavel Machek:
> On Sun 2007-12-30 17:39:42, Oliver Neukum wrote:
> > But what's wrong with calling suspend() the conventional way once you've
> > decided to go into sleepy mode?
>
> I'm not sure if it can be done in non-racy way. It is different from
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Some device drivers register CPU hotplug notifiers and use them to
> destroy device objects when removing the corresponding CPUs and to
> create these objects when adding the CPUs back.
>
> Unfortunately, this is not the right thing to
I'm getting this on latest git (v2.6.24-rc6-174-gdc51281)
WARNING: vmlinux.o(.text+0x104f8): Section mismatch: reference to
.init.text:fork_idle (between 'do_fork_idle' and 'lapic_timer_broadcast')
WARNING: vmlinux.o(.text.head+0xe4): Section mismatch: reference to
* James Bottomley <[EMAIL PROTECTED]> wrote:
> Could you direct this poster to linux-scsi and we'll see if we can
> finger the root cause (which will be difficult to do without getting a
> boot trace).
FYI, here's a new one reported against 2.6.24-rc6-git7:
On Wed, 2008-01-02 at 21:31 +1100, Nick Piggin wrote:
> On Monday 31 December 2007 00:10, Ingo Molnar wrote:
> > * Herbert Xu <[EMAIL PROTECTED]> wrote:
> > > > Ingo, it's not good that we have cond_resched() definitions
> > > > conditionally duplicated in kernel.h - that's increasing the risk of
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> (or -- why do we even make CONFIG_PREEMPT_BKL an option? [...]
thanks for the reminder - i just zapped it. Was a pleasure ;-)
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Wednesday 02 January 2008 22:01, Peter Zijlstra wrote:
> On Wed, 2008-01-02 at 21:31 +1100, Nick Piggin wrote:
> > On Monday 31 December 2007 00:10, Ingo Molnar wrote:
> > > * Herbert Xu <[EMAIL PROTECTED]> wrote:
> > > > > Ingo, it's not good that we have cond_resched() definitions
> > > > >
Tejun Heo wrote:
> Tejun Heo wrote:
>> Kbuild now generates and installs modules.order along with modules.
>> This patch updates depmod such that it sorts module list according to
>> the file before generating output files. Modules which aren't on
>> modules.order are put after modules which are
Dave Young wrote:
> On Dec 29, 2007 7:42 PM, Stefan Richter <[EMAIL PROTECTED]> wrote:
>> However, Dave's postings lack a References: header which refer to his
>> 00/12 posting.
[To let mail readers show it as a thread.]
>> (Also, a bonus in the 00/12 posting would be a listing of all patch
>>
On Wed, 2008-01-02 at 22:12 +1100, Nick Piggin wrote:
> On Wednesday 02 January 2008 22:01, Peter Zijlstra wrote:
> > I've seen 1s+ desktop latencies due to PREEMPT_BKL when I was still
> > using reiserfs.
>
> Fair enough; so the former ifdefery would be preferable for now then.
To be honest,
On Jan 2 2008 12:14, Stefan Richter wrote:
>There is nothing wrong with a 0/n posting per se. But whenever you
>write a 0/n posting, ask yourself:
> - Isn't the information I provide here necessary to keep around by
>somebody who takes my patch series into his quilt series or into his
>
From: Andrew Murray <[EMAIL PROTECTED]>
This patch provides a correct value for CONFIG_SH_PCLK_FREQ for the SH7712
solution engine when used with the board's default factory settings. This
results in the board running at its maximum CPU clock rate (200 MHz).
The board I have is a Japanese
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > > Document the fact that __save_processor_state() has to save all
> > > CPU registers referred to by the kernel in case a different kernel
> > > is used to load and restore a hibernation image containing it.
> > >
> > > Sigend-off-by: Rafael
Hi,
In file include/asm-i386/system.h, _set_base and _set_limit use an
useless do ... while(0)
Why is this needed ?
exemple with _set_base from linux-2.6.23
#define _set_base(addr,base) do { unsigned long __pr; \
__asm__ __volatile__ ("movw %%dx,%1\n\t" \
"rorl $16,%%edx\n\t" \
* Mike Frysinger <[EMAIL PROTECTED]> wrote:
> Forgot to mention this before, but since the msr.h header uses types
> like __u32, it should pull in linux/types.h.
does not build with the attached config.
Ingo
#
# Automatically generated make config: don't edit
# Linux kernel version:
On Wed, Jan 02, 2008 at 12:45:39PM +0100, Abdel wrote:
> Hi,
>
> In file include/asm-i386/system.h, _set_base and _set_limit use an
> useless do ... while(0)
>
> Why is this needed ?
>
> exemple with _set_base from linux-2.6.23
>
> #define _set_base(addr,base) do { unsigned long __pr; \
>
Abdel <[EMAIL PROTECTED]> wrote:
> In file include/asm-i386/system.h, _set_base and _set_limit use an
> useless do ... while(0)
>
> Why is this needed ?
http://kernelnewbies.org/FAQ/DoWhile0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
* Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> > It would be sweet to have them use private mutexes for the job
> > instead (although even then it probably wouldn't be a straight
> > conversion)...
>
> I tried a quick conversion of reiser3 at the time, but it really wants
> a recursive lock
On Wed, 2 Jan 2008, Herbert Xu wrote:
> Theodore Tso <[EMAIL PROTECTED]> wrote:
> > The question is whether the size of the Unix domain sockets support is
> > worth the complexity of yet another config option that we expose to
> > the user. For the embedded world, OK, maybe they want to save 14k
On Wed, Jan 02 2008 at 12:08 +0200, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 01, 2008 at 06:15:46PM +0200, Boaz Harrosh wrote:
>> I have this code:
>>
>>
>> /*
>> * osd-r10 4.12.5 Data-In and Data-Out buffer offsets
>> * byte offset = mantissa * (2^(exponent+8))
>> */
>>
On 02-01-2008 08:00, Greg KH wrote:
...
> If no one has noticed any issues in this area, [...]
...Could also mean there are hidden issues, so it doesn't look like
very convincing argument.
...Unless after the change there will be found no hidden issues,
then, of course, it looks like convincing
* Ananth N Mavinakayanahalli <[EMAIL PROTECTED]> wrote:
> > Signed-off-by: Quentin Barnes <[EMAIL PROTECTED]>
> > Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
> > Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
>
> Tested on x86.
>
> Acked-by: Ananth N Mavinakayahanalli <[EMAIL
We get die() from kdebug.h, no need for forward declaration.
Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
---
arch/x86/mm/fault_32.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/arch/x86/mm/fault_32.c b/arch/x86/mm/fault_32.c
index bfb0917..870b561 100644
---
Move X86_32 only get_segment_eip to X86_64
Move X86_64 only is_errata93 to X86_32
Change X86_32 loop in is_prefetch to highlight the differences
between them. Fold the logic from __is_prefetch in as well on
X86_32.
Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
---
arch/x86/mm/fault_32.c |
* Frank Ch. Eigler <[EMAIL PROTECTED]> wrote:
> Ingo Molnar <[EMAIL PROTECTED]> writes:
>
> > [...] Firstly, why on earth does a full format string have to be
> > passed in for something as simple as a CPU id? This way we basically
> > codify it forever that tracing _has_ to be expensive when
* Harvey Harrison <[EMAIL PROTECTED]> wrote:
> We get die() from kdebug.h, no need for forward declaration.
thanks, applied.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Wednesday, 2 of January 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > Some device drivers register CPU hotplug notifiers and use them to
> > destroy device objects when removing the corresponding CPUs and to
> > create these objects when
Hi Abdel :)
* Abdel <[EMAIL PROTECTED]> dixit:
> In file include/asm-i386/system.h, _set_base and _set_limit use an
> useless do ... while(0)
>
> Why is this needed ?
Google for "do while swallow semicolon". This looks like an useless and
weird construction but it is very useful when it comes
Jan Engelhardt wrote:
> And [0/n] sometimes contain a diffstat which gives an approximate
> line count of how big the patchset actually is.
There is actually no good reason for omitting such a diffstat. It's
easy enough to generate.
$ quilt diff --combine first.patch -P last.patch | diffstat
On Wed, Jan 02, 2008 at 01:39:38PM +0100, Jarek Poplawski wrote:
> On 02-01-2008 08:00, Greg KH wrote:
> ...
> > If no one has noticed any issues in this area, [...]
BTW, if 'we' are sure there are no issues, and only lockdep is not
clever enough yet, why not do such a change partially, e.g. with
On Wednesday, 2 of January 2008, Christian Hesse wrote:
> On Wednesday 02 January 2008, Nigel Cunningham wrote:
> > Hi Christian.
> >
> > Christian Hesse wrote:
> > > On Tuesday 01 January 2008, Nigel Cunningham wrote:
> > >> Third, regarding the patch itself, I'm taking my time in working towards
On Wednesday, 2 of January 2008, Zhenyu Wang wrote:
> On 2008.01.01 22:02:57 +, Rafael J. Wysocki wrote:
> > Subject : linux-2.6.24-rcX regression /
> > xserver-xorg-video-intel / Q35
> > Submitter : Harald Welte <[EMAIL PROTECTED]>
> > Date: 2007-12-22 04:37
> >
On Wednesday 02 January 2008, Alexey Starikovskiy wrote:
> Andrey Borzenkov wrote:
> > This is did not happen before; I am not sure right now what caused this
(i.e.
> > battery aging or some software change) nor whether this is
kernel/HAL/kpowersave
> > issue.
> >
> > kpowersave is stuck at
FYI - another quirky Quanta motherboard from HP, with DMI readings
reported to me.
Original Message
Date: Wed, 2 Jan 2008 16:23:27 +1030
From: Joel Stanley <[EMAIL PROTECTED]>
To: David P. Reed <[EMAIL PROTECTED]>
Subject:Re: [PATCH] Option to disable AMD C1E
(David Brownell Cc:-ed too)
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> Well, we have the following test script in the userland suspend
> package that is supposed to work right now:
>
> #!/bin/bash
> date
> cd /sys/class/rtc/rtc0
> echo $(( $(cat since_epoch) + 20 )) > wakealarm
> s2ram
2008/1/2, DervishD <[EMAIL PROTECTED]>:
>* Abdel <[EMAIL PROTECTED]> dixit:
>> In file include/asm-i386/system.h, _set_base and _set_limit use an
>> useless do ... while(0)
>>
>> Why is this needed ?
>
>Google for "do while swallow semicolon". This looks like an useless
Hi Nigel,
I do agree with all your plans ;)
I'm also happy with the current version of tuxonice.
The main question is :
"What is the status of merging into mainline" (with or without any
additional patch from other suspend patch).
I have seen quite a lot of mails about this topic on the lmkl
* David P. Reed <[EMAIL PROTECTED]> wrote:
> FYI - another quirky Quanta motherboard from HP, with DMI readings reported
> to me.
> Using port80.c, I could hard lock a HP Pavilion tx1000 laptop on the
> first go. This was with ubuntu hardy's stock kernel (a 2.6.24-rc)
>
>> dmidecode -s
On Wednesday, 2 of January 2008, Ingo Molnar wrote:
>
> (David Brownell Cc:-ed too)
>
> * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> > Well, we have the following test script in the userland suspend
> > package that is supposed to work right now:
> >
> > #!/bin/bash
> > date
> > cd
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> On Wednesday, 2 of January 2008, Zhenyu Wang wrote:
> > On 2008.01.01 22:02:57 +, Rafael J. Wysocki wrote:
> > > Subject : linux-2.6.24-rcX regression /
> > > xserver-xorg-video-intel / Q35
> > > Submitter : Harald Welte <[EMAIL
On Wednesday, 2 of January 2008, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <[EMAIL PROTECTED]>
>
> It sometimes is necessary to destroy a device object during a suspend or
> hibernation, but the PM core is supposed to control all device objects in that
> cases. For this reason, it is
Use the force_sig_info_fault helper from X86_32 in X86_64.
Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
---
arch/x86/mm/fault_32.c |2 +-
arch/x86/mm/fault_64.c | 31 ++-
2 files changed, 19 insertions(+), 14 deletions(-)
diff --git
On Wednesday, 2 of January 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> > On Wednesday, 2 of January 2008, Zhenyu Wang wrote:
> > > On 2008.01.01 22:02:57 +, Rafael J. Wysocki wrote:
> > > > Subject : linux-2.6.24-rcX regression /
> > > >
> BKL properties, that could be wrapped. I guess fixing the TTY code to
> have no BKL dependencies has a higher chance of success - given that
> Alan is working on it :-)
Bit by bit when I can face it, and with a lot of other people
contributing parts. Right now the BKL mostly protects the
On Wednesday 02 January 2008, Ingo Molnar wrote:
> * Mike Frysinger <[EMAIL PROTECTED]> wrote:
> > Forgot to mention this before, but since the msr.h header uses types
> > like __u32, it should pull in linux/types.h.
>
> does not build with the attached config.
sorry, forgot about __ASSEMBLY__
On Wednesday 02 January 2008, David Miller wrote:
> From: Christoph Hellwig <[EMAIL PROTECTED]>
> > The only non-kernel user of this known to me is silo, which should just
> > have it's own header documenting the solaris sparc ufs variant it needs
> > to understand, possibly by using a copy of the
Hi David, hi Eric,
Le 29/12/2007, "David Brownell" <[EMAIL PROTECTED]> a écrit:
>From: eric miao <[EMAIL PROTECTED]>
>
>This adds a new-style I2C driver with basic support for the sixteen
>bit PCA9539 GPIO expanders. These chips have multiple registers,
>push-pull output drivers, and (not
> ok, you are right. How about we go with one of your suggestions: rename
> the API family to isa_*_p() in the affected ISA drivers? That makes it
> perfectly clear that this is an ISA related historic quirk that we just
> cannot properly emulate in an acceptable fashion. It will also make the
> > same with radio-sf16fmr2 and esp
> >
> > after repeatedly modrpobe/modprobe -r radio-sf16fmr2, i can hang my
> > system when loading esp afterwards
> >
> > before loading esp, doing a "cat /proc/ioport" segfaults
> >
> > this is with 2.6.24rc6 and also with 2.6.22
> >
> > i have found
Contents of /proc/*/maps is sensitive and may become sensitive
after open() (e.g. if target originally shares our ->mm and later
does exec on suid-root binary).
Check at read() (actually, ->start() of iterator) time that
mm_struct we'd grabbed and locked is
* still the ->mm
On Wed, 2 Jan 2008 14:09:57 +
Al Viro <[EMAIL PROTECTED]> wrote:
> Contents of /proc/*/maps is sensitive and may become sensitive
> after open() (e.g. if target originally shares our ->mm and later
> does exec on suid-root binary).
> Check at read() (actually, ->start() of
401 - 500 of 855 matches
Mail list logo
