Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Jan Beulich <[EMAIL PROTECTED]>
---
arch/x86/mm/pageattr_64.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/arch/x86/mm/pageattr_64.c
===
---
Instead of open coding the bit accesses uses standard style
*PageDeferred* macros.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Jan Beulich <[EMAIL PROTECTED]>
---
arch/x86/mm/pageattr_32.c | 14 ++
arch/x86/mm/pageattr_64.c | 11 +--
2 files changed, 19
With the infrastructure added for CLFLUSH it is possible
to only TLB flush the actually changed pages in change_page_attr()
Take care of old Athlon K7 Errata on the 32bit version
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Jan Beulich <[EMAIL PROTECTED]>
---
Now that debug pagealloc uses a separate function it is better
to change standard change_page_attr back to init_mm semaphore locking like
64bit.
Various things are simpler when sleeping is allowed.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Jan Beulich <[EMAIL PROTECTED]>
---
Queue individual data pages for flushing with CLFLUSH in change_page_attr(),
instead of doing global WBINVDs. WBINVD is a very painful operation
for the CPU (can take msecs) and quite slow too. Worse it is not interruptible
and can cause long latencies on hypervisors on older Intel VT systems.
Since change_page_attr() is tricky code it is good to have some regression
test code. This patch maps and unmaps some random pages in the direct mapping
at boot and then dumps the state and does some simple sanity checks.
Add it with a CONFIG option.
Optional patch, but I find it useful.
CONFIG_DEBUG_PAGEALLOC uses change_page_attr to map/unmap mappings for catching
stray kernel mappings. But standard c_p_a() does a lot of unnecessary work for
this simple case with pre-split mappings.
Change kernel_map_pages to just access the page table directly which
is simpler and faster.
I
Needed for the next change.
And change all the callers.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Jan Beulich <[EMAIL PROTECTED]>
---
arch/x86/mm/fault_32.c |3 ++-
arch/x86/mm/init_32.c|3 ++-
arch/x86/mm/pageattr_32.c| 10 +++---
On Wed, 16 Jan 2008, Paul Moore wrote:
> On Tuesday 15 January 2008 8:05:27 pm James Morris wrote:
> > On Tue, 15 Jan 2008, David Howells wrote:
> > > secid_to_secctx() LSM hook. This patch also includes the SELinux
> > > implementation for this hook.
> > >
> > > Signed-off-by: Paul Moore
Similar to x86-64. This is useful in other situations where we want
the page table dumped too.
Besides anything that makes i386 do_page_fault shorter is good.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Jan Beulich <[EMAIL PROTECTED]>
---
arch/x86/mm/fault_32.c | 72
64bit already had it.
Needed for later patches.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Jan Beulich <[EMAIL PROTECTED]>
---
include/asm-x86/pgtable.h|2 ++
include/asm-x86/pgtable_64.h |2 --
2 files changed, 2 insertions(+), 2 deletions(-)
Index:
The pte_* modifier functions that cleared bits dropped the NX bit on 32bit
PAE because they only worked in int, but NX is in bit 63. Fix that
by adding appropiate casts so that the arithmetic happens as long long
on PAE kernels.
I decided to just use 64bit arithmetic instead of open coding like
When CONFIG_DEBUG_RODATA is enabled undo the ro mapping and redo it again.
This gives some simple testing for change_page_attr()
Optional patch, but I find it useful.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Jan Beulich <[EMAIL PROTECTED]>
---
arch/x86/Kconfig.debug |5
Needed for some test code.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Jan Beulich <[EMAIL PROTECTED]>
---
include/asm-x86/pgtable.h |3 +++
1 file changed, 3 insertions(+)
Index: linux/include/asm-x86/pgtable.h
Port the code to check for already split 4K pages at boot over from
32bit to 64bit.
Note: should be probably put before PAT patches to avoid bisect failures later
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86/mm/pageattr_64.c |7 +++
1 file changed, 3 insertions(+), 4
No need to make it 64bit there.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Jan Beulich <[EMAIL PROTECTED]>
---
arch/x86/mm/init_32.c |4 ++--
include/asm-x86/pgtable.h |2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
Index: linux/arch/x86/mm/init_32.c
Undo random white space changes. This reverts
ddb53b5735793a19dc17bcd98b050f672f28f1ea
I simply don't have the nerves to port a 20+ patch series to the
reformatted version. And the patch series changes most lines
anyways and drops the trailing white spaces there.
And since this was a nop
Similar to 64bit.
Needed by PAT patches. Replaces 5ec5c5a2302ca8794da03f8bedec931a2a814ae9
Note: should probably be put before PAT patches to avoid bisect failures later
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86/mm/pageattr_32.c | 15 +++
1 file changed, 15
Note sure what the point of that change was
Author: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Date: Tue Jan 15 16:53:24 2008 +0100
patches/x86-pat-usable_only_map.patch
x86_64: Map only usable memory in identity map. Reserved memory maps to a
zero page.
Undoes pageattr_32.c parts of
Not sure what the point of that change was anyways.
commit 11c9734cbcf4c5862260442a5d56dd4779799fcc
Author: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Date: Tue Jan 15 09:36:03 2008 +0100
patches/x86-pat-usable_only_map_i386.patch
i386: Map only
Changes to previous versions:
- Ported to the latest git-x86 including the PAT patchkit
This undoes some changes in the PAT patches and reimplements them
in a different way. End result should be equivalent, but this
made it easier for me to merge the patches.
- Fix NX bit handling (I think even
Going to implement this differently
commit 5ec5c5a2302ca8794da03f8bedec931a2a814ae9
Author: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Date: Tue Jan 15 09:36:03 2008 +0100
patches/x86-pat-cpa_i386.patch
This makes 32 bit cpa similar to x86_64 and makes it easier for following PA
>-Original Message-
>From: Andi Kleen [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, January 16, 2008 2:02 PM
>To: Pallipadi, Venkatesh
>Cc: Andreas Herrmann; [EMAIL PROTECTED];
>[EMAIL PROTECTED]; [EMAIL PROTECTED];
>[EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
>[EMAIL
The reason, why this patch was dug up, is that if the bdi-sysfs patch
is going to use device numbers to identify BDIs, then there should be
a way for the user to map the device number into mount(s).
But it's useful regardless of the bdi-sysfs patch.
Can this be added to -mm?
In theory it could
please check
1. add pci_mmcfg_arch_free for x86_64
2. change back init sequence so we can use mmconf even acpi=off
all against to x86.git
YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
[PATCH] x86: clear pci_mmcfg_virt when mmcfg get rejected
for x86_64, need to free pci_mmcfg_virt, and iounmap some pointers
when MMCONF is not reserved in E820 or acpi _CRS and get rejected
Signed-off-by: Yinghai Lu <[EMAIL PROTECTED]>
Index: linux-2.6/arch/x86/pci/mmconfig-shared.c
[PATCH] x86: MMCONF enable MCFG early
patch
x86: validate against ACPI motherboard resources
changed the mmconf init sequence, and init MMCONF late in acpi_init.
here change it back to old sequence
1. check hostbridge in early
2. check MCFG with e820 in early
3. if all fail, will check
> This ioremap failing seems to be the real problem. This can be due to
> new tracking of ioremaps introduced by PAT patches. We do not allow
> conflicting ioremaps to same region. Probably that is happening
Normally if there is a conflict there should be a printk (or at least it was
so in the
On Wed, 16 Jan 2008, Matthew Wilcox wrote:
> I sent you a mail on December 6th ... here are the contents of that
> mail:
Dec 6th? I was on vacation then and it seems that I was unable to
reproduce the oopses. Can I get some backtraces or other information
that would allow me to diagnose the
On Wed, 16 Jan 2008 16:19:12 -0500
Andres Salomon <[EMAIL PROTECTED]> wrote:
> On Wed, 16 Jan 2008 18:44:07 +0100
> Arnd Hannemann <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I'm trying to boot 2.6.24-rc8 on a GEODE LX board (ALIX.3),
> > and it hangs during boot:
> >
> > [ 12.689971] NET:
On Tuesday January 15, [EMAIL PROTECTED] wrote:
> On Wed, 16 Jan 2008 00:09:31 -0700 "Dan Williams" <[EMAIL PROTECTED]> wrote:
>
> > > heheh.
> > >
> > > it's really easy to reproduce the hang without the patch -- i could
> > > hang the box in under 20 min on 2.6.22+ w/XFS and raid5 on 7x750GB.
>
On Wed, 16 Jan 2008, Johannes Weiner wrote:
> > Johannes, thanks for the patches, but NAK. A similar group of patches that
> > clean up the _sta and heander file (kills it, actually) has already been
> > sent to Len Brown to be merged for 2.6.25.
>
> Sorry, I missed to check his tree in advance.
In message <[EMAIL PROTECTED]>, Michael Halcrow writes:
> On Thu, Jan 10, 2008 at 10:57:46AM -0500, Erez Zadok wrote:
[...]
> Would the inclusion of Unionfs in mainline really slow down or damage
> the union mount effort? If not, then I think the pragmatic approach
> would be to make it available
On Wed, Jan 16, 2008 at 12:39:31PM -0800, Christoph Lameter wrote:
> Ahhh.. Good to hear that the issue on x86_64 gets better. I am still
> waiting for a test with the patchset that I did specifically to address
> your regression: http://lkml.org/lkml/2007/10/27/245 (where I tried to
> come up
On Jan 16, 2008 12:34 AM, Balaji Rao <[EMAIL PROTECTED]> wrote:
> On Wednesday 16 January 2008 12:21:33 pm Ingo Molnar wrote:
> Hi Ingo,
> > * Yinghai Lu <[EMAIL PROTECTED]> wrote:
> > > "
> > > commit e5ed385fa0d6f35406e3e3ed75e5eb9adeb811df
> > > Author: Balaji Rao <[EMAIL PROTECTED]>
> > >
On Mon, Jan 14, 2008 at 03:18:31PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <[EMAIL PROTECTED]>
>
> Remove the tmp file when exiting. Noticed by Arjan van de Ven.
> Catch mktemp failure and exit with message.
> Trap kill or other signals and exit cleanly.
Applied,
Sam
--
To
Alan Cox wrote:
>> Writeback cache on disk in iteself is not bad, it only gets bad if the
>> disk is not engineered to save all its dirty cache on power loss,
>> using the disk motor as a generator or alternatively a small battery.
>> It would be awfully nice to know which brands fail here, if
On Tue, 8 January 2008 11:47:00 +1100, Rusty Russell wrote:
>
> There's nothing wrong with this patch, but I think it papers over a more
> general problem: we enter the module (to parse args) while it's not in the
> module list. This also means we won't get a nice oops if it crashes.
>
>
On Thu, 2008-01-17 at 02:09 +0530, Balaji Rao wrote:
> Hi,
>
> When i set jiffies as the current_clocksource, date(1) tells me that
> wallclock time has stopped, and soon after that, the
> system becomes unresponsive. This is not seen with CONFIG_NO_HZ disabled.
>
> This happens in
On Thu, Jan 10, 2008 at 10:57:46AM -0500, Erez Zadok wrote:
> In message <[EMAIL PROTECTED]>, Christoph Hellwig
> writes:
> > On Thu, Jan 10, 2008 at 09:59:19AM -0500, Erez Zadok wrote:
> > >
> > > Dear Linus, Al, Christoph, and Andrew,
> > >
> > > As per your request, I'm posting for review the
On Thu, 17 Jan 2008, Balaji Rao wrote:
> When i set jiffies as the current_clocksource, date(1) tells me that
> wallclock time has stopped, and soon after that, the
> system becomes unresponsive. This is not seen with CONFIG_NO_HZ disabled.
>
> This happens in 2.6.24-rc4,rc5, and even in rc8.
Thanks a lot for pointing this out! I rolled the following into the
offending patch in my tree instead (I preferred avoiding #ifdefs in .c
files...)
diff --git a/drivers/infiniband/ulp/ipoib/ipoib.h
b/drivers/infiniband/ulp/ipoib/ipoib.h
index 545c5a3..fe250c6 100644
---
On Wed, 16 Jan 2008 18:44:07 +0100
Arnd Hannemann <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm trying to boot 2.6.24-rc8 on a GEODE LX board (ALIX.3),
> and it hangs during boot:
>
> [ 12.689971] NET: Registered protocol family 16
> [ 12.703329] geode-mfgpt: Registered timer 0
> [ 12.716149]
This is against x86/mm.
===
parent a9f7faa5fd229a65747f02ab0f2d45ee35856760
commit
Author: Jan Engelhardt <[EMAIL PROTECTED]>
Date: Wed Jan 16 21:23:01 2008 +0100
x86: remove unneeded casts
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
Hi Henrique,
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> On Wed, 16 Jan 2008, Johannes Weiner wrote:
>> Define _sta() helper conditionally; also remove its prototype from
>> the internal header and also some other unneeded ones.
>>
>> This function is only needed when the bay or
* Andi Kleen <[EMAIL PROTECTED]> wrote:
> > truly stuck, or just an annoying message?
>
> Just annoying message; system works after that for simple login etc.
> (haven't run anything complicated)
ok, if you see no other failures and if you have some time it would be
nice to figure out why
>
> truly stuck, or just an annoying message?
Just annoying message; system works after that for simple login etc.
(haven't run anything complicated)
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
> We have to set c->x86_power in early_identify_cpu to properly detect
> the CONSTANT_TSC bit in early_init_amd.
Hmm this definitely worked here when I wrote the patches. Must have been a merge
mistake later. I remember someone changed the early CPU init around severly
at some point and I might
Bodo Eggert wrote:
BTW1: These addresses may be used to detect ports on non-standard addresses,
but unfortunately they don't tell the IRQ.
BTW2: When I submitted a patch using the BIOS data area, I was told that it
might not exist on systems booting from non-PC firmware. This claim was not
yet
On Jan 16, 2008 3:49 AM, Pavel Machek <[EMAIL PROTECTED]> wrote:
>
> ext3's "lets fsck on every 20 mounts" is good idea, but it can be
> annoying when developing. Having option to fsck while filesystem is
> online takes that annoyance away.
I'm sure everyone on cc: knows this, but for the record
On Wed, Jan 16, 2008 at 09:19:23PM +0100, Vegard Nossum wrote:
> On Jan 16, 2008 8:33 PM, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> > On Wed, Jan 16, 2008 at 06:46:46PM +0100, Vegard Nossum wrote:
> > >
> > > I have now tried this patch. I don't see a sync error now, but the
> > > button still
On Wed, 16 Jan 2008, Mathieu Desnoyers wrote:
> >
> > In-other-words, latency_tracer is LTTng-lite ;-)
> >
>
> If LTTng is already ported to your specific kernel, the learning-curve
> is not big at all. Here is what the latency_tracer over LTTng guide
> could look like :
>
> Well, once you have
On Wed, 16 Jan 2008, Matthew Wilcox wrote:
> We tested 2.6.24-rc5 + 76be895001f2b0bee42a7685e942d3e08d5dd46c
>
> For 2.6.24-rc5 before that patch, slub had a performance penalty of
> 6.19%. With the patch, slub's performance penalty was reduced to 4.38%.
> This is great progress. Can you think
Mathieu Desnoyers wrote:
> If LTTng is already ported to your specific kernel, the learning-curve
> is not big at all. Here is what the latency_tracer over LTTng guide
> could look like :
>
> Well, once you have LTTng in your kernel and have compiled and installed
> the ltt-control and lttv
Mike Travis a écrit :
Another point: you want this change, sorry if my previous mail was not detailed
enough :
--- a/arch/x86/mm/numa_64.c
+++ b/arch/x86/mm/numa_64.c
@@ -78,7 +78,7 @@ static int __init allocate_cachealigned_memnodemap(void)
unsigned long pad, pad_addr;
Hi,
On Wed, Jan 16, 2008 at 05:04:17PM +0100, Jiri Kosina wrote:
> On Wed, 16 Jan 2008, Adrian Bunk wrote:
>
> > RSS feed of the git tree:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=rss
> > Changes since 2.6.16.57:
> > Adrian Bunk (3):
> >
> > This is an experimental patch for supporing unprivileged mounts and
> > umounts. The following features are added:
>
> same feedback as last time ... the cap stuff needs to be made optional and
> proper header checks added to configure ...
Later, sure. For now, I'm concentrating on the
On Wed, Jan 16, 2008 at 07:57:48PM +0100, Andreas Herrmann wrote:
> Hi,
>
> I just want to report that the PAT support in x86/mm causes crashes
> on two of my test machines. On both boxes the SATA detection does
> not work when the PAT support is patched into the kernel.
>
> Symptoms are as
Bjorn Helgaas <[EMAIL PROTECTED]> wrote:
> On Wednesday 16 January 2008 11:44:37 am H. Peter Anvin wrote:
>> Bjorn Helgaas wrote:
>> > +#ifdef CONFIG_X86
>> > + switch (port->iobase) {
>> > + case 0x3f8: return 0; /* COM1 -> ttyS0 */
>> > + case 0x2f8: return 1; /* COM2 ->
* Andreas Herrmann <[EMAIL PROTECTED]> wrote:
> Commits
> - c52f61fcbdb2aa84f0e4d831ef07f375e6b99b2c
> (x86: allow TSC clock source on AMD Fam10h and some cleanup)
> - e30436f05d456efaff77611e4494f607b14c2782
> (x86: move X86_FEATURE_CONSTANT_TSC into early cpu feature detection)
>
> are
On Wed, Jan 16, 2008 at 07:58:36AM +0100, Jarek Poplawski wrote:
> On Wed, Jan 16, 2008 at 11:17:08AM +1100, Herbert Xu wrote:
> ...
> > Well people are always going to operate on this model for commercial
> > reasons. FWIW I used to work for a company that stuck to a specific
> > version of the
Hi,
When i set jiffies as the current_clocksource, date(1) tells me that wallclock
time has stopped, and soon after that, the
system becomes unresponsive. This is not seen with CONFIG_NO_HZ disabled.
This happens in 2.6.24-rc4,rc5, and even in rc8.
I wonder how can jiffies be used as a
* Andreas Herrmann <[EMAIL PROTECTED]> wrote:
> I just want to report that the PAT support in x86/mm causes crashes on
> two of my test machines. On both boxes the SATA detection does not
> work when the PAT support is patched into the kernel.
>
> Symptoms are as follows -- best described by
* Steven Rostedt ([EMAIL PROTECTED]) wrote:
>
...
> >
> > > >
> > > > - Disable preemption at the read-side :
> > > > it makes sure the pointer I get will point to a data structure that
> > > > will never change while I am in the preempt disabled code. (see *)
> > > > - I use per-cpu data to
* Andi Kleen <[EMAIL PROTECTED]> wrote:
> git-x86 upto a9f7faa5fd229a65747f02ab0f2d45ee35856760 boots, but gives
>
> VFS: Mounted root (nfs filesystem).
> Freeing unused kernel memory: 264k freed
> eth0: no IPv6 routers present
> Clocksource tsc unstable (delta = 18747555652 ns)
>
> BUG: soft
> And I think there's a problem with drives that, upon sensing the
> unreadable sector, assign an alternate even though the sector is fine, and
> you eventually run out of spares.
You are assuming drives can't tell the difference between stray data loss
and sectors that can't be recovered by
On Jan 16, 2008 8:33 PM, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 16, 2008 at 06:46:46PM +0100, Vegard Nossum wrote:
> >
> > I have now tried this patch. I don't see a sync error now, but the
> > button still does not work as expected. Now the scroll down button
> > acts like a
[I recommend we direct future discussions in this thread to the unionfs
ML. -ezk]
In message <[EMAIL PROTECTED]>, Paul Albrecht writes:
[...]
> I'm not sure we're talking about the same problem. What I do is union
> mount a write enabled file system like tmpfs over a read only file
> system like
On Wed, Jan 16, 2008 at 12:59:27PM -0700, Bjorn Helgaas wrote:
> On Wednesday 16 January 2008 11:39:34 am Russell King wrote:
> > On Wed, Jan 16, 2008 at 10:05:41AM -0700, Bjorn Helgaas wrote:
> > > When 8250_pnp discovers COM ports, we only get the correct ttyS names
> > > by accident -- we rely
On Wednesday 16 January 2008, Miklos Szeredi wrote:
> This is an experimental patch for supporing unprivileged mounts and
> umounts. The following features are added:
same feedback as last time ... the cap stuff needs to be made optional and
proper header checks added to configure ...
> 1) If
> If the hardware required an intermediate junk I/O, that would be a
> reason to do one, but it doesn't, does it? It requires a delay. It's
> written thus in all of the application notes.
And the only instruction that is synchronized to the bus in question is
an I/O instruction.
> Wrong
On Jan 16, 2008 11:55 AM, Steven Rostedt <[EMAIL PROTECTED]> wrote:
>
> On Wed, 16 Jan 2008, Mark Knecht wrote:
> >
> > Jan 16 11:12:55 lightning sshd[5915]: Server listening on :: port 22.
> > Jan 16 11:12:55 lightning sshd[5915]: error: Bind to port 22 on
> > 0.0.0.0 failed: Address already in
Bjorn Helgaas wrote:
+
Arguably, the right thing is to use the addresses present in the array
at address 0x400. In particular, COM3 and COM4 aren't always at those
addresses.
Wow. I bow before your storehouse of x86 arcana :-)
I guess you're referring to the "BIOS data area," which I'd
Hi Christoph,
We tested 2.6.24-rc5 + 76be895001f2b0bee42a7685e942d3e08d5dd46c
For 2.6.24-rc5 before that patch, slub had a performance penalty of
6.19%. With the patch, slub's performance penalty was reduced to 4.38%.
This is great progress. Can you think of anything else worth trying?
--
On Wednesday 16 January 2008 11:39:34 am Russell King wrote:
> On Wed, Jan 16, 2008 at 10:05:41AM -0700, Bjorn Helgaas wrote:
> > When 8250_pnp discovers COM ports, we only get the correct ttyS names
> > by accident -- we rely on serial8250_isa_init_ports(), which discovers
> > the COM ports
On Wed, 2007-12-12 at 16:40 +1100, Nick Piggin wrote:
> On Wednesday 12 December 2007 16:11, Dave Kleikamp wrote:
> > On Wed, 2007-12-12 at 15:57 +1100, Nick Piggin wrote:
> > > Anyway, I am hoping that someone will one day and test if this and
> > > find it helps their workload, but on the
On Wed, 16 Jan 2008, Mark Knecht wrote:
>
> Jan 16 11:12:55 lightning sshd[5915]: Server listening on :: port 22.
> Jan 16 11:12:55 lightning sshd[5915]: error: Bind to port 22 on
> 0.0.0.0 failed: Address already in use.
>
> Will continue testing as I get time.
Thanks,
Are you sure you don't
On Wed, 2008-01-16 at 12:13 -0500, Erez Zadok wrote:
> In message <[EMAIL PROTECTED]>, Paul Albrecht writes:
> > Hi,
> >
> > I have a question about how unionfs handles file deletion when a write
> > enabled file system is union mounted over a read only file system. For
> > example, I do
On Wednesday 16 January 2008 11:44:37 am H. Peter Anvin wrote:
> Bjorn Helgaas wrote:
> > x86 users expect COM1-COM4 ports at the conventional ioport addresses
> > to be named ttyS0-ttyS3. For PNP devices, the BIOS determines the
> > order we discover them, so we might discover COM2 before COM1.
Commits
- c52f61fcbdb2aa84f0e4d831ef07f375e6b99b2c
(x86: allow TSC clock source on AMD Fam10h and some cleanup)
- e30436f05d456efaff77611e4494f607b14c2782
(x86: move X86_FEATURE_CONSTANT_TSC into early cpu feature detection)
are supposed to fix the detection of contant TSC for AMD CPUs.
On Wed, 16 Jan 2008, Mathieu Desnoyers wrote:
> * Steven Rostedt ([EMAIL PROTECTED]) wrote:
> >
> > Yeah, but if we replace the loop with a seq lock, then it would work.
> > albeit, more cacheline bouncing (caused by writes). (maybe not, see below)
> >
>
> Yes, but then you would trigger a
On Jan 15, 2008 8:12 PM, Steven Rostedt <[EMAIL PROTECTED]> wrote:
> We are pleased to announce the 2.6.24-rc7-rt3 tree
Up and running here:
[EMAIL PROTECTED] ~ $ uname -a
Linux lightning 2.6.24-rc7-rt3 #1 PREEMPT RT Wed Jan 16 11:06:11 PST
2008 x86_64 AMD Athlon(tm) 64 Processor 3000+
I applied the patch and I am still locking up after
Time: hpet clocksource has been installed.
I rebooted with "clocksource=tsc" to get the logs of the trace which
was added. I'm assuming the grep below gets all the interesting parts.
I enabled the HPET character device as mentioned before, which
Sorry. Never mind about e820 map. Somehow I did not notice the boot.log
you had attached earlier.
Thanks,
Venki
>-Original Message-
>From: Pallipadi, Venkatesh
>Sent: Wednesday, January 16, 2008 11:06 AM
>To: 'Andreas Herrmann'
>Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL
On Wed, Jan 16, 2008 at 06:46:46PM +0100, Vegard Nossum wrote:
>
> I have now tried this patch. I don't see a sync error now, but the
> button still does not work as expected. Now the scroll down button
> acts like a middle button instead of scrolling down.
>
> I am sorry for the confusion; on
Andrea Righi wrote:
> David Newall wrote:
>
>> Andrea Righi wrote:
>>
>>> [I/O-intensive] processes can noticeably impact the system responsiveness
>>> for some time and playing with tasks' priority is not always an
>>> acceptable solution.
>>>
>>>
>> Why?
>>
>>
>
> Well, I
>
> Another point: you want this change, sorry if my previous mail was not
> detailed enough :
>
> --- a/arch/x86/mm/numa_64.c
> +++ b/arch/x86/mm/numa_64.c
> @@ -78,7 +78,7 @@ static int __init allocate_cachealigned_memnodemap(void)
> unsigned long pad, pad_addr;
>
> memnodemap =
On Wed, Jan 16, 2008 at 12:58:01PM -0500, Andres Salomon wrote:
> On Tue, 15 Jan 2008 17:04:01 -0500
> Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
>
> > On Sat, Jan 12, 2008 at 03:12:52PM -0500, Andres Salomon wrote:
> > >
> > > The lifebook driver may register a second input device, but it never
Another version of this patch has been sent to Len Brown for 2.6.25 already.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To
Alan Cox wrote:
> On Thu, 17 Jan 2008 01:06:24 +1030
> David Newall <[EMAIL PROTECTED]> wrote:
>
>
>> This use of port 80 (or insert some other random number) is a croc of
>> hackery of the most inexperienced kind.
>>
>
> Wrong. It's a careful designed solution used by all sorts of code
Equivalent patch already sent to Len Brown for 2.6.25, removing the header
file altogether...
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
On Wed, 16 Jan 2008, Johannes Weiner wrote:
> Define _sta() helper conditionally; also remove its prototype from
> the internal header and also some other unneeded ones.
>
> This function is only needed when the bay or the dock subdriver is
> enabled. Otherwise, gcc complains about an unused
>The "disk motor as a generator" tale may not be purely folklore. When
>an IDE drive is not in writeback mode, something special needs to done
>to ensure the last write to media is not a scribble.
No it doesn't. The last write _is_ a scribble. Systems that make atomic
updates to disk drives
Can you attach the e820 map from the top of your dmesg.
Thanks,
Venki
>-Original Message-
>From: Andreas Herrmann [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, January 16, 2008 10:58 AM
>To: Pallipadi, Venkatesh
>Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
>[EMAIL
On 1/10/08, Greg KH <[EMAIL PROTECTED]> wrote:
> On Fri, Dec 28, 2007 at 11:50:49PM +, Russell King - ARM Linux wrote:
> > On Fri, Dec 28, 2007 at 03:03:22PM -0800, Andrew Morton wrote:
> > > On Fri, 28 Dec 2007 13:11:37 + "Bahadir Balban" <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > > >
On Jan 15, 2008 7:01 PM, Fengguang Wu <[EMAIL PROTECTED]> wrote:
> Basically I think rbtree is an overkill to do time based ordering.
> Sorry, Michael. But s_dirty would be enough for that. Plus, s_more_io
> provides fair queuing between small/large files, and s_more_io_wait
> provides waiting
Bjorn Helgaas wrote:
x86 users expect COM1-COM4 ports at the conventional ioport addresses
to be named ttyS0-ttyS3. For PNP devices, the BIOS determines the
order we discover them, so we might discover COM2 before COM1.
We currently always get the correct names, even without this patch.
But
Alan Cox wrote:
On a box here the kernel hangs on boot without "edd=off". Adding printfs
as hpa suggested shows that it correctly scans BIOS disk 1 (0x80) then on
disk 2 (PDC20263) it gets a version then hangs trying to read the MBR
Is there a disk connected to the PDC20263 and its BIOS
On Wed, Jan 16, 2008 at 10:05:41AM -0700, Bjorn Helgaas wrote:
> When 8250_pnp discovers COM ports, we only get the correct ttyS names
> by accident -- we rely on serial8250_isa_init_ports(), which discovers
> the COM ports earlier using the addresses in SERIAL_PORT_DFNS.
It's not by accident but
On Wed, Jan 16, 2008 at 10:05:43AM -0700, Bjorn Helgaas wrote:
> static int __devinit
> +serial_pnp_line(struct uart_port *port)
> +{
> +#ifdef CONFIG_X86
> + switch (port->iobase) {
> + case 0x3f8: return 0; /* COM1 -> ttyS0 */
> + case 0x2f8: return 1; /* COM2 ->
201 - 300 of 962 matches
Mail list logo
