Takenori Nagano <[EMAIL PROTECTED]> writes:
>
> Hi all,
>
> IMHO, most users don't use kdump, kdump users are only kernel developers and
> enterprise users.
Not at all. So far the only kdump related bug report I have seen has
been from fedora Core.
> think enterprise users want the notifier fun
From: Mark Fortescue <[EMAIL PROTECTED]>
Date: Tue, 31 Jul 2007 06:35:29 +0100 (BST)
> The original code did a job lot of pte stuf in install_arg_page. The
> new code seems to replace this using get_user_pages but I have not
> worked out how get_user_pages gets to the point at which it
> allocated
Hi!
> Without this change, it is possible to build CONFIG_HIBERNATE
> on all !SMP architectures, but not necessarily their SMP versions.
Did you want to say "CONFIG_SUSPEND"?
> I don't know for sure if the architecture list under SUSPEND_UP_POSSIBLE
> is correct. For now it simply matches the l
On Mon, 2007-07-30 at 22:34 -0600, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
>
> > This patch adds Graphics Output Protocol support to the kernel.
> > UEFI2.0 spec deprecates Universal Graphics Adapter (UGA) protocol and
> > only Graphics Output Protocol (GOP) is produce
On Mon 2007-07-30 21:09:33, [EMAIL PROTECTED] wrote:
> On Mon, 30 Jul 2007, Len Brown wrote:
>
> >On Saturday 28 July 2007 12:55, Linus Torvalds wrote:
> >
> >>So I think the real issue is that we allow that
> >>"suspend_devices_and_enter()" code to be compiled without HOTPLUG_CPU in
> >>the first
On 07/31/2007 08:06 AM, dean gaudet wrote:
On Wed, 18 Jul 2007, Rene Herman wrote:
Would anyone happen to have a list of TLB sizes for some selected
x86{,-64} CPUs? I know it goes from a few entries on a 386 to a lot on
Opteron but I have a real hard time finding specific data.
http://sand
On Tue, 2007-07-31 at 01:46 +0200, Kasper Sandberg wrote:
> could perhaps be filesystem related, i have my maildir(extremely large)
> on reiserfs, and /home on xfs. what my mail client will do is download
> mail, spamasassin it(loading database from home), then it will put to
> imap server placing
Jeff Garzik wrote:
> Any chance the SCSI peeps could ACK this, and then let me include it in
> the ALPM patchset in the libata tree?
ATA link PS is pretty complex with HIPM, DIPM and AHCI ALPM. I'm not
sure whether this three level knob would be sufficient. It might be
good enough if we're gonna
http://sandpile.org/
On Wed, 18 Jul 2007, Rene Herman wrote:
> Good day.
>
> Would anyone happen to have a list of TLB sizes for some selected x86{,-64}
> CPUs? I know it goes from a few entries on a 386 to a lot on Opteron but I
> have a real hard time finding specific data.
>
> Rene.
> -
> To
Did I miss something or do we needlessly do an "or" to flush_cpumask
while we could just assign it ? We never exit that function with the
mask not empty and we have a spinlock...
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
---
Index: linux-work/arch/i386/kernel/smp.c
===
On Thu, 19 Jul 2007, Bill Irwin wrote:
> On Thu, Jul 19, 2007 at 10:07:59AM -0700, Nishanth Aravamudan wrote:
> > But I do think a second reason to do this is to make hugetlbfs behave
> > like a normal fs -- that is read(), write(), etc. work on files in the
> > mountpoint. But that is simply my o
Eric W. Biederman wrote:
> Vivek Goyal <[EMAIL PROTECTED]> writes:
>
>>> Bernhard's idea (kdump uses panic_notifier) is very good for me. But it
>>> isn't
>>> good for kdump user, because they want to take a dump ASAP when panicked.
>>>
>> This one is better than registering kdump as one of the u
Joseph Pingenot wrote:
While we're on the subject, is there some way to receive notification
that some aspect of a process changes (in this case, stopping using
CPU, but not exiting).
For some internal stuff a while back I did a patch that allows any
process to register for status change
these struct *_operations are all method tables, thus should be const.
Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
---
fs/gfs2/eaops.c|8
fs/gfs2/eaops.h|4 ++--
fs/gfs2/glock.c|2 +-
fs/gfs2/ops_dentry.c |3 +--
fs/gfs2/ops_dentry.h |2
Hi,
I haven't given this idea testing yet, but I just wanted to get some
opinions on it first. NUMA placement still isn't ideal (eg. tasks with
a memory policy will not do any placement, and process migrations of
course will leave the memory behind...), but it does give a bit more
chance for the m
Hi David,
One possible issue is sequencing, perhaps the stack argument copy
is occuring before the new context is setup properly on sun4c.
I think it is somthing related to this but too much has changed for me to
work out what is going on. At present, I don't have a good enough
understandi
On Tue, Jul 31, 2007 at 02:05:48AM -0300, Mauro Carvalho Chehab wrote:
> Hi Greg,
>
> Em Seg, 2007-07-30 ??s 21:33 -0700, Greg KH escreveu:
> > anexo Documento somente texto
> > (saa7134-fix-thread-shutdown-handling.patch)
> > -stable review patch. If anyone has any objections, please let us know
> +unsigned long mem_container_isolate_pages(unsigned long nr_to_scan,
> + struct list_head *dst,
> + unsigned long *scanned, int order,
> + int mode, struct zone *z,
> +
> > During bootup it panics with:
> >
> > Kernel panic - not syncing: Unable to find SBA IOMMU: Try a generic or DIG
> > kernel
I think that the fix for this has already gone into Linus's tree (on
Friday). Commit SHA1
for the patch that should fix this is:
8c8eb78f673c07b60f31751e1e47ac367c60c6b
On 7/29/07, Mark Fortescue <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> Unfortunatly Sparc32 sun4c low level memory management apears to be
> incompatible with commit b6a2fea39318e43fee84fa7b0b90d68bed92d2ba
> mm: variable length argument support.
I feel like I ought to help out with this since it's m
On Sunday 29 July 2007 17:27, Rafael J. Wysocki wrote:
> Still, there are many other files in which CONFIG_PM can be replaced
> with CONFIG_PM_SLEEP or even with CONFIG_SUSPEND, but they can be updated in
> the future.
There is #ifdef CONFIG_PM
around all the .suspend and .resume methods.
Technic
Hi Greg,
Em Seg, 2007-07-30 às 21:33 -0700, Greg KH escreveu:
> anexo Documento somente texto
> (saa7134-fix-thread-shutdown-handling.patch)
> -stable review patch. If anyone has any objections, please let us know.
>
> --
>
> From: Jeff Mahoney <[EMAIL PROTECTED]>
>
> This patc
I've been able to capture a tcpdump from both ends during the problem
and its my belief there is a bug in 2.6.20.1 (at the client side) in
that it issues a SACK option for an old sequence which the current
window being advertised is beyond it. This is the most concerning issue
as the integri
Joe Jin wrote:
Hmm.. in this config file, whats causing DIO to panic ? Which test actually
passing faulty buffer ?
By my testing, just defined job3 and job10 will also get the panic, but if
only have one of them, panic will not appear. the faulty buffer maybe passed
by mmap.
Thanks.
On Tue, 31 Jul 2007 13:29:32 +0900
KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
> On Mon, 30 Jul 2007 22:15:50 -0600
> "David Mosberger-Tang" <[EMAIL PROTECTED]> wrote:
>
> > This seems crazy to me. Flushing should occur according to the
> > *architecture*, not model-by-model. Even if we happen
"Huang, Ying" <[EMAIL PROTECTED]> writes:
> Looking forward to your comments,
After reading through the patches. I don't see any compelling
reason to use the efi runtime support. It looks like we get
the interesting support for efi without out. The graphics
and the memory map. We have ACPI wh
On Mon, Jul 30, 2007 at 09:30:47PM -0700, Greg KH wrote:
> This is the start of the stable review cycle for the 2.6.21.7 release.
> There are 26 patches in this series, all will be posted as a response to
> this one. If anyone has any issues with these being applied, please let
> us know. If anyo
On Tue, 31 Jul 2007 11:25:26 +0900 Fernando Luis Vázquez Cao <[EMAIL
PROTECTED]> wrote:
> > runtime. Some drivers don't get used by many people and users of some
> > architectures (esp embedded) tend to lag kernel.org by a long time. So it
> > could be years before all the fallout from this cha
"Huang, Ying" <[EMAIL PROTECTED]> writes:
> Changelog between v2 and v3:
>
> 1. The EFI callwrapper is re-implemented in assembler.
>
> ---
>
> This patch adds basic support for EFI x86_64 system. The main file of
> the patch is the addition of efi.c for x86_64. This file is modeled
> after the EF
"Huang, Ying" <[EMAIL PROTECTED]> writes:
> This patch adds document for EFI x86_64 support. The boot parameters
> added are documented in Documentation/i386/zero-page.txt. The setup
> and operation guide of EFI based system is documented in
> Documentation/x86_64/uefi.txt.
>
> Signed-off-by: Chan
john stultz wrote:
> On 7/29/07, Vasily Averin <[EMAIL PROTECTED]> wrote:
>> I've investigated why my testnode freezes. When I found that node is freezed
>> again I've started to press Sysrq keys and noticed the following negative
>> time jump.
>>
>> Could anybody please help me to understand the
-stable review patch. If anyone has any objections, please let us know.
--
This patch restores a couple of workarounds from 2.6.16:
* restart transmit moderation timer in case it expires during IRQ routine
* default to having 10 HZ watchdog timer.
At this point it more importan
"Huang, Ying" <[EMAIL PROTECTED]> writes:
> This patch adds Graphics Output Protocol support to the kernel.
> UEFI2.0 spec deprecates Universal Graphics Adapter (UGA) protocol and
> only Graphics Output Protocol (GOP) is produced. Therefore, the boot
> loader needs to query the UEFI firmware with
> Hmm.. in this config file, whats causing DIO to panic ? Which test actually
> passing faulty buffer ?
>
By my testing, just defined job3 and job10 will also get the panic, but if
only have one of them, panic will not appear. the faulty buffer maybe passed
by mmap.
Thanks,
Joe
-
To unsubscribe
-stable review patch. If anyone has any objections, please let us know.
--
The clock_was_set() call in seconds_overflow() which happens only when
leap seconds are inserted / deleted is wrong in two aspects:
1. it results in a call to on_each_cpu() with interrupts disabled
2. it
-stable review patch. If anyone has any objections, please let us know.
--
From: Trent Piepho <[EMAIL PROTECTED]>
If one uses a V4L *one* application, such as vlc or mplayer's v4l driver, as
the first user after the driver is loaded, the driver wedges itself and will
never captu
-stable review patch. If anyone has any objections, please let us know.
--
From: Jelle Foks <[EMAIL PROTECTED]>
v4l-info and other programs would loop indefinitely while querying the
tuners for cx88-blackbird cards.
The cause was that vidioc_g_tuner didn't return an error value
-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Mahoney <[EMAIL PROTECTED]>
This patch changes the test for the thread pid from >= 0 to > 0.
When the saa8134 driver initialization fails after a certain point, it goes
through the complete sh
-stable review patch. If anyone has any objections, please let us know.
--
From: Jay Lubomirski <[EMAIL PROTECTED]>
The interrupt clearing code in mpsc_sdma_intr_ack() mistakenly clears the
interrupt for both controllers instead of just the one its supposed to.
This can result i
-stable review patch. If anyone has any objections, please let us know.
--
The commit 635cf99a80f4ebee59d70eb64bb85ce829e4591f introduced a
regression. Executing a ptrace single step after certain int80
accesses will infinitely loop and never advance the PC.
The TIF_SINGLESTEP
-stable review patch. If anyone has any objections, please let us know.
--
From: Tony Jones <[EMAIL PROTECTED]>
Removing a watched file will oops if audit is disabled (auditctl -e 0).
To reproduce:
- auditctl -e 1
- touch /tmp/foo
- auditctl -w /tmp/foo
- auditctl -e 0
- rm /tm
-stable review patch. If anyone has any objections, please let us know.
--
This fixes a bug which can cause corruption of the floating-point state
on return from a signal handler. If we have a signal handler that has
used the floating-point registers, and it happens to context-s
-stable review patch. If anyone has any objections, please let us know.
--
From: Hugh Dickins <[EMAIL PROTECTED]>
validate_anon_vma gave a useful check on the integrity of the anon_vma list
when Andrea was developing obj rmap; but it was not enabled in SLES9
itself, nor in mainl
-stable review patch. If anyone has any objections, please let us know.
--
From: Christoph Lameter <[EMAIL PROTECTED]>
Fix massive SMP imbalance on NUMA nodes observed on 2.6.21.5 with CFS.
(and later on reproduced without CFS as well).
The intervals of domains that do not hav
-stable review patch. If anyone has any objections, please let us know.
--
posix-timers which deliver an ignored signal are currently rearmed in
the timer softirq: This is necessary because the timer needs to be
delivered again when SIG_IGN is removed. This is not a problem, when
-stable review patch. If anyone has any objections, please let us know.
--
The return value of futex_find_get_task() needs to be -ESRCH in case
that the search fails. This was part of the original futex fixes and
got accidentally dropped, when the futex-tidy-up patch was split o
-stable review patch. If anyone has any objections, please let us know.
--
From: Adam Litke <[EMAIL PROTECTED]>
Here's another breakage as a result of shared memory stacked files :(
The NUMA policy for a VMA is determined by checking the following (in the
order given):
1) vma-
-stable review patch. If anyone has any objections, please let us know.
--
From: Olaf Kirch <[EMAIL PROTECTED]>
Get rid of first_clone in dm-crypt
This gets rid of first_clone, which is not really needed. Apparently, cloned
bios used to share their bvec some time way in the pa
-stable review patch. If anyone has any objections, please let us know.
--
From: Olaf Kirch <[EMAIL PROTECTED]>
Do not access the bio after generic_make_request
We should never access a bio after generic_make_request - there's no guarantee
it still exists.
Signed-off-by: Olaf
"Huang, Ying" <[EMAIL PROTECTED]> writes:
> This patch adds runtime service support for EFI x86_64 system.
>
> The EFI support for emergency_restart and RTC clock is added. The EFI
> based implementation and legacy BIOS or CMOS based implementation are
> put in separate functions and are chosen ba
-stable review patch. If anyone has any objections, please let us know.
--
From: Milan Broz <[EMAIL PROTECTED]>
Disable barriers in dm-crypt because of current workqueue processing can
reorder requests.
This must be addresed later but for now disabling barriers is needed to
pre
-stable review patch. If anyone has any objections, please let us know.
--
From: Olaf Kirch <[EMAIL PROTECTED]>
Call clone_init early
We need to call clone_init as early as possible - at least before call
bio_put(clone) in any error path. Otherwise, the destructor will try to
-stable review patch. If anyone has any objections, please let us know.
--
From: Mike Accetta <[EMAIL PROTECTED]>
If raid1/repair (which reads all block and fixes any differences
it finds) hits a read error, it doesn't reset the bio for writing
before writing correct data back,
-stable review patch. If anyone has any objections, please let us know.
--
From: Alexey Kuznetsov <[EMAIL PROTECTED]>
1. New entries can be added to tsk->pi_state_list after task completed
exit_pi_state_list(). The result is memory leakage and deadlocks.
2. handle_mm_fault()
-stable review patch. If anyone has any objections, please let us know.
--
Eliminate UltraATA/133 support for HPT374 -- the chip isn't capable of this mode
according to the manual, and doesn't even seem to tolerate 66 MHz DPLL clock...
Signed-off-by: Sergei Shtylyov <[EMAIL PRO
-stable review patch. If anyone has any objections, please let us know.
--
1/ When resyncing a degraded raid10 which has more than 2 copies of each block,
garbage can get synced on top of good data.
2/ We round the wrong way in part of the device size calculation, which
can
-stable review patch. If anyone has any objections, please let us know.
--
Alexey Kuznetsov found some problems in the pi-futex code.
The major problem is a stale return value in rt_mutex_slowlock():
When the pi chain walk returns -EDEADLK, but the waiter was woken up
during
-stable review patch. If anyone has any objections, please let us know.
--
Alexey Kuznetsov found some problems in the pi-futex code.
One of the root causes is:
When a wakeup happens, we do not to stop the chain walk so we
we follow a non existing locking chain.
Drop out whe
-stable review patch. If anyone has any objections, please let us know.
--
We aren't sampling for holes in memory. Thus we encounter a section hole with
empty section map pointer for SPARSEMEM and OOPs for show_mem. This issue
has been seen in 2.6.21, current git and current mm.
Very sorry for the long delay in getting these out, it should be the
last 2.6.21-stable release, unless there are some patches that people
point out to us that deserve a new .21.y release.
This is the start of the stable review cycle for the 2.6.21.7 release.
There are 26 patches in this series, a
-stable review patch. If anyone has any objections, please let us know.
--
There's a bug in the driver that only initializes half of the context
memory on the 5708. Surprisingly, this works most of the time except
for some occasional netdev watchdogs when sending a lot of 64-by
On Mon, 30 Jul 2007 22:15:50 -0600
"David Mosberger-Tang" <[EMAIL PROTECTED]> wrote:
> This seems crazy to me. Flushing should occur according to the
> *architecture*, not model-by-model. Even if we happen to get "lucky"
> on pre-Montecito CPUs, that doesn't justify such ugly hacks.
I'm not s
On Mon, Jul 30, 2007 at 01:35:19PM -0700, Suresh B wrote:
> On Mon, Jul 30, 2007 at 11:20:04AM -0700, Christoph Lameter wrote:
> > On Fri, 27 Jul 2007, Siddha, Suresh B wrote:
>
> > > Observation #2: This introduces some migration overhead during IO
> > > submission.
> > > With the current protot
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.23.git
Which contains:
Adrian McMenamin (1):
sh: Fix Dreamcast DMA issues.
David McCullough (2):
sh: arch/sh/boot - fix shell usage
sh: fix get_wchan() for SH kernels without framepointers
Mag
"Huang, Ying" <[EMAIL PROTECTED]> writes:
> Following sets of patches add EFI/UEFI (Unified Extensible Firmware
> Interface) support to x86_64 architecture. The patches have been
> tested against 2.6.23-rc1 kernel on Intel platforms with EFI1.10 and
> UEFI2.0 firmware.
>
> UEFI specification can b
This seems crazy to me. Flushing should occur according to the
*architecture*, not model-by-model. Even if we happen to get "lucky"
on pre-Montecito CPUs, that doesn't justify such ugly hacks. Or you
really want to debug this *again* come next CPU?
--david
On 7/30/07, KAMEZAWA Hiroyuki <[EMA
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh64-2.6.git
Which contains:
Paul Mundt (3):
sh64: Fix fs.h removal from mm.h regressions.
sh64: Fix irq_intc build failure.
sh64: Kill off virt_to_bus()/bus_to_virt().
arch/sh64/Kconfig
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:netdev-
> [EMAIL PROTECTED] On Behalf Of Andrew Gallatin
> Sent: Monday, July 30, 2007 10:43 AM
> To: Linas Vepstas
> Cc: Jan-Bernd Themann; netdev; Thomas Klein; Jeff Garzik; Jan-Bernd
> Themann; linux-kernel; linux-ppc; Christoph Ra
On Mon, 30 Jul 2007, Len Brown wrote:
On Saturday 28 July 2007 12:55, Linus Torvalds wrote:
So I think the real issue is that we allow that
"suspend_devices_and_enter()" code to be compiled without HOTPLUG_CPU in
the first place. It's not supposed to work that way.
I don't see how CONFIG_HOT
Meelis Roos wrote:
>>> Subject : New ACPI error/warning with Linus' latest GIT
>>> References : http://lkml.org/lkml/2007/7/26/395
>>> Last known good : ?
>>> Submitter : Ismail Dönmez <[EMAIL PROTECTED]>
>>> Caused-By : ?
>>> Handled-By : ?
>>> Status : unkno
On Mon, Jul 30, 2007 at 10:56:27PM -0500, Joseph Pingenot wrote:
> >From Al Viro on Tuesday, 31 July, 2007:
> >On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote:
> >> I'm trying to implement pwait. It blocks until a specified PID exits,
> >> and then it exits.
> >er... ptrace(2)?
>
Quoting Len Brown ([EMAIL PROTECTED]):
> Hmmm, okay, the "big hammer" works. Please see
> if any of these smaller hammers work:
>
> pnpacpi=off
Went out for dinner, machine was frozen on return.
One less on the checklist ..
--
-
To unsubscribe from this list: send the line "unsubscribe linux-ke
>From Al Viro on Tuesday, 31 July, 2007:
>On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote:
>> I'm trying to implement pwait. It blocks until a specified PID exits,
>> and then it exits.
>er... ptrace(2)?
Should work for most common usage scenarios, although will suspect that it
From: Linus Torvalds <[EMAIL PROTECTED]>
Without this change, it is possible to build CONFIG_HIBERNATE
on all !SMP architectures, but not necessarily their SMP versions.
I don't know for sure if the architecture list under SUSPEND_UP_POSSIBLE
is correct. For now it simply matches the list for SU
On Mon, 30 Jul 2007 22:31:00 -0500 Chris Holvenstot wrote:
> I am having a problem, likely caused by the vacuum between my ears, but
> I thought that a few of you would find it recreational to tear up an
> inexperienced user for doing dumb things.
>
> I have what is quickly becoming a "un-ubunt
On Sunday 29 July 2007 20:21, Linus Torvalds wrote:
>
> Ok, I took this, and modified Len's patch to re-introduce ACPI_SLEEP on
> top of it (I took the easy way out, and just made PM_SLEEP imply
> ACPI_SLEEP, which should make everything come out right. I could have
> dropped ACPI_SLEEP entirel
On Mon, Jul 30, 2007 at 02:36:13AM +0400, Alexey Dobriyan wrote:
> 0) Remove fs.h from mm.h. For this,
> 1) Uninline vma_wants_writenotify(). It's pretty huge anyway.
> 2) Add back fs.h or less bloated headers (err.h) to files that need it.
>
sh ended up breaking all over the place, and sh64 in a
On Saturday 28 July 2007 12:55, Linus Torvalds wrote:
> So I think the real issue is that we allow that
> "suspend_devices_and_enter()" code to be compiled without HOTPLUG_CPU in
> the first place. It's not supposed to work that way.
I don't see how CONFIG_HOTPLUG_CPU justifies its own existenc
I just tried hooking up a Hitachi 1TB SATA-II drive to a Marvell 7042
based controller, and the most recent Linux kernel (2.6.23-rc1) fails to
properly initialize the interface. Here are the relevant kernel messages:
kernel: [43.312417] sata_mv :06:00.0: version 0.81
kernel: [43.312752] AC
On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote:
> I'm trying to implement pwait. It blocks until a specified PID exits,
> and then it exits.
er... ptrace(2)?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote:
> From Al Viro on Tuesday, 31 July, 2007:
> >On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote:
> >> >From Joseph Pingenot on Monday, 30 July, 2007:
> >> >From Al Viro on Tuesday, 31 July, 2007:
> >> >>On Mon, Jul 30, 20
On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote:
> Introduce white-out support to ext2.
>
> Known Bugs:
> - Needs a reserved inode number for white-outs
You picked different reserved inodes for the ext2 and ext3
filesystems. That's good for a NACK right there. The codepoints
(i.e., r
Joe Jin wrote:
Well, I'm having a heck of a time getting this to fail. It looks
possible, though. Joe, were you guys able to narrow it down to a
reproducible test case? Do you have any oops output messages from
the crashes?
Zach, it easy to reproduce through fio with following conf
>From Al Viro on Tuesday, 31 July, 2007:
>On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote:
>> >From Joseph Pingenot on Monday, 30 July, 2007:
>> >From Al Viro on Tuesday, 31 July, 2007:
>> >>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
>> >>> I was trying to use
On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote:
> >From Joseph Pingenot on Monday, 30 July, 2007:
> >From Al Viro on Tuesday, 31 July, 2007:
> >>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
> >>> I was trying to use inotify to watch process changes (especially p
> + lock_meta_page(page);
> + /*
> + * Check if somebody else beat us to allocating the meta_page
> + */
> + race_mp = page_get_meta_page(page);
> + if (race_mp) {
> + kfree(mp);
> + mp = race_mp;
> + atomic_inc(&mp->ref_cnt);
> +
Hi Ingo, I'm forwading this report from a Planet CCRMA user, this is
happening to him with 2.6.21.6-rt21...
-- Fernando
Forwarded Message
From: Matt Barber
To: [EMAIL PROTECTED]
Subject: [PlanetCCRMA] atl1 driver; sleeping function
Date: Mon, 30 Jul 2007 06:09:58 -0400
Hello,
Andrew Morton wrote:
> On Sun, 29 Jul 2007 13:29:26 +0300
> Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>> If a cpu is spinning in the kernel but still responding to interrupts,
>> pressing sysrq-y will show you where it's spinning.
>>
>> Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
>>
>> diff --
On Mon, Jul 30, 2007 at 10:25:21PM -0500, Joseph Pingenot wrote:
> >From Al Viro on Tuesday, 31 July, 2007:
> >On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
> >> I was trying to use inotify to watch process changes (especially process
> >> termination) by watching /proc/.
> >>
>From Joseph Pingenot on Monday, 30 July, 2007:
>From Al Viro on Tuesday, 31 July, 2007:
>>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
>>> I was trying to use inotify to watch process changes (especially process
>>> termination) by watching /proc/.
>>> Sadly, although I could
I am having a problem, likely caused by the vacuum between my ears, but
I thought that a few of you would find it recreational to tear up an
inexperienced user for doing dumb things.
I have what is quickly becoming a "un-ubuntu" 7.04 system - as time goes
on I seem to be replacing the standard d
>From Al Viro on Tuesday, 31 July, 2007:
>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
>> I was trying to use inotify to watch process changes (especially process
>> termination) by watching /proc/.
>> Sadly, although I could see something reading various files, nothing
>> w
This patch adds Graphics Output Protocol support to the kernel.
UEFI2.0 spec deprecates Universal Graphics Adapter (UGA) protocol and
only Graphics Output Protocol (GOP) is produced. Therefore, the boot
loader needs to query the UEFI firmware with appropriate Output
Protocol and pass the video info
On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
> I was trying to use inotify to watch process changes (especially process
> termination) by watching /proc/.
>
> Sadly, although I could see something reading various files, nothing
> was issued when the process I was watching e
This patch adds boot support for EFI x86_64 system.
Boot parameter setup file is updated for x86_64 EFI support. x86_64
EFI boot loader must conform to the EFI boot parameter offsets defined
in the file include/asm-x86_64/bootsetup.h (and x86_64 patches
submitted to ELILO bootloader conforms to th
This patch adds runtime service support for EFI x86_64 system.
The EFI support for emergency_restart and RTC clock is added. The EFI
based implementation and legacy BIOS or CMOS based implementation are
put in separate functions and are chosen based on the value of
efi_enabled.
Signed-off-by: Cha
This patch adds document for EFI x86_64 support. The boot parameters
added are documented in Documentation/i386/zero-page.txt. The setup
and operation guide of EFI based system is documented in
Documentation/x86_64/uefi.txt.
Signed-off-by: Chandramouli Narayanan <[EMAIL PROTECTED]>
Signed-off-by:
Following sets of patches add EFI/UEFI (Unified Extensible Firmware
Interface) support to x86_64 architecture. The patches have been
tested against 2.6.23-rc1 kernel on Intel platforms with EFI1.10 and
UEFI2.0 firmware.
UEFI specification can be found here: http://www.uefi.org
For booting the UEF
Changelog between v2 and v3:
1. The EFI callwrapper is re-implemented in assembler.
---
This patch adds basic support for EFI x86_64 system. The main file of
the patch is the addition of efi.c for x86_64. This file is modeled
after the EFI IA32 avatar. EFI initialization are implemented in
efi.c
On 7/31/07, Roland Dreier <[EMAIL PROTECTED]> wrote:
> > Fuck you Martin!
>
> I think you meant to yell at Matthew, not Martin ;)
What's amusing about this is he's yelling at me for something I didn't
do, can't even get my name right, and has the audacity to claim that
*I* am the one looking
1 - 100 of 584 matches
Mail list logo
