fa.linux.kernel Google Group

Re: [PATCH 29/44] includecheck fix: drivers/spi, amba-pl022.c

2009-07-09T21:22:04Z

ROTFL.
the-other-Linus

Re: Soft-Lockup/Race in networking in 2.6.31-rc1+195 ( possibly?caused by netem)

2009-07-09T21:20:17Z

Confirmed working from me as well.
Thank you for your time,
Joao Correia

Re: mptsas, msi and the dl585 g2

2009-07-09T21:19:18Z

On Thu, Jul 9, 2009 at 1:40 PM, James
sure. will send out one patch after get some sanity test here.
YH

Re: [PATCH 29/44] includecheck fix: drivers/spi, amba-pl022.c

2009-07-09T21:17:57Z

2009/7/8 Jaswinder Singh Rajput <jaswin...@kernel.org>:
Not me I hope (damned I knew this would happen sooner or later).
return -ELINWAL
Having this name is very convenient, people review my drivers like
crazy.
Linus Walleij

RE: [RFC PATCH 0/4] (Take 2): transcendent memory ("tmem") for Linux

2009-07-09T21:11:33Z

Although tmem and CMS have similar conceptual objectives,
let me try to describe what I see as a fundamental
difference in approach.
The primary objective of both is to utilize RAM more
efficiently. Both are ideally complemented with some
longer term "memory shaping" mechanism such as automatic
ballooning or hotplug.

Clock incorrect on 2.6.31-rc2

2009-07-09T21:10:35Z

My system (desktop Ubuntu 9.0) runs fine with 2.6.30, but with 2.6.31-rc2 it does
not keep time correctly. Also ntptime reports an error.
$ ntptime
ntp_gettime() returns code 5 (ERROR)
time ce00daf1.8e997000 Thu, Jul 9 2009 14:09:05.557, (.557029),
maximum error 25016 us, estimated error 16 us

Re: [PATCH] score: add regsets support for score

2009-07-09T21:05:18Z

I would not recommend adding PTRACE_{PEEK,POKE}USR to an ABI that
doesn't have it already. It only exists on other arch's for past
compatibility; it's the poorest interface for this.
If you are starting from scratch, then you should define your arch's
user_regset layouts so that everything is nicely represented in one

Re: OOM killer in 2.6.31-rc2

2009-07-09T21:03:36Z

Yes.
I am short approximately 500 megs according to top:
Mem: 3634228k total, 3522984k used, 111244k free, 308096k buffers
Swap: 8385912k total, 568k used, 8385344k free, 2544716k cached
From dmesg:
[ 0.000000] TOM2: 0000000120000000 aka 4608M <what is this?
[...]
[ 0.000000] 2694MB HIGHMEM available.

Re: [PATCH 3/5] Show kernel stack usage to /proc/meminfo and OOM log

2009-07-09T21:01:01Z

Right.

Re: [PATCH 4/5] add isolate pages vmstat

2009-07-09T21:00:29Z

No there is really no alternative to it.
Just be aware that what you may increases the cache footprint of key
functions in the vm. Some regression tests would be useful (do a page
fault test etc).

Re: Null Pointer BUG in uhci_hcd

2009-07-09T20:59:20Z

Hmmm... acpi=noirq stops the memory leak. (???)
That's the easy part - now to figure out why. ;)
Then we can go back to this thread; see if there was a real driver problem
or this thread was just demonstrating an artifact of the above <whatever>.
Mike

Re: CONFIG_VFAT_FS_DUALNAMES regressions

2009-07-09T20:57:27Z

No need for pettiness. Andrew's already intimated that he's still
working the patch, and he's a very clever lad and knows if it corrupts
it needs more work.
What I don't understand is how anybody could be satisfied with the
status quo. We cannot leave vfat unchanged, for that will perpetuate a
pool of victims to be sued, and Linux loses credibility every time that

2.6.29.5: Oops when unplugging Moschip 7840/7820 USB serial device

2009-07-09T20:57:05Z

I unplugged a Moschip 7840/7820 USB serial adapter, and it oopsed. I had been using it
with picoterm, but it was not open at the time I unplugged it.
Thanks,
J
BUG: unable to handle kernel NULL pointer dereference at 00000000000000b4
IP: [<ffffffff81029eb5>] __ticket_spin_lock+0x9/0x1a
PGD 12e19c067 PUD 12e19d067 PMD 0

[PATCH] cfq-iosched: no need to keep track of busy_rt_queues

2009-07-09T20:51:43Z

Resending as had forgotten to put "[PATCH]" in subject line.
o Get rid of busy_rt_queues infrastructure. Looks like it is redundant.
o Once an RT queue gets request it will preempt any of the BE or IDLE queues
immediately. Otherwise this queue will be put on service tree and scheduler
will anyway select this queue before any of the BE or IDLE queue. Hence

cfq-iosched: no need to keep track of busy_rt_queues

2009-07-09T20:49:35Z

o Get rid of busy_rt_queues infrastructure. Looks like it is redundant.
o Once an RT queue gets request it will preempt any of the BE or IDLE queues
immediately. Otherwise this queue will be put on service tree and scheduler
will anyway select this queue before any of the BE or IDLE queue. Hence