19.03.2015 14:56, One Thousand Gnomes wrote:
> On Thu, 19 Mar 2015 14:09:29 +0300
> Michael Tokarev wrote:
>
>> Half a year passed since my first email in this thread, and current kernels
>> (4.0-tobe) still does not work properly. Meanwhile, I found
19.03.2015 23:05, One Thousand Gnomes wrote:
>> Yes, with video=LVDS-1:d boot parameter, kernel boots fine and there is
>> graphics/video output on the screen, with the following message from kernel
>> when loading gma500_gfx:
>>
>> [6.472859] [drm] forcing LVDS-1 connector OFF
>>
>> (and a few
19.03.2015 14:56, One Thousand Gnomes wrote:
> On Thu, 19 Mar 2015 14:09:29 +0300
> Michael Tokarev wrote:
>
>> Half a year passed since my first email in this thread, and current kernels
>> (4.0-tobe) still does not work properly. Meanwhile, I found
19.03.2015 14:09, Michael Tokarev wrote:
> Half a year passed since my first email in this thread, and current kernels
Actually it was more than a year, since Feb-2014 ;)
> (4.0-tobe) still does not work properly. Meanwhile, I found this thread:
> http://www.linuxquestions.org/
wonder where they got these boot params from...
Thanks,
/mjt
05.08.2014 20:15, Michael Tokarev wrote:
> 05.08.2014 20:11, Michael Tokarev wrote:
>> Hello again.
>>
>> It's been 4 more months since last message in this thread (which was mine).
>> Now kernel 3.16 has
05.08.2014 20:11, Michael Tokarev wrote:
> Hello again.
>
> It's been 4 more months since last message in this thread (which was mine).
> Now kernel 3.16 has been released, and I decided to give it a try. And it
> behaves just like all previous kernels, -- once gma500_
;no signal detected") and nothing to
be seen until reboot.
Can we try to debug this somehow, after more than half a year?... :)
Thank you,
/mjt
05.04.2014 12:15, Michael Tokarev wrote:
> Hello again
>
> It's been about 2 months since I sent the original debugging output. Today I
&g
03.06.2014 16:04, Paolo Bonzini wrote:
> Il 01/06/2014 01:05, Rickard Strandqvist ha scritto:
>> There is a risk that the variable will be used without being initialized.
>>
>> This was largely found by using a static code analysis program called
>> cppcheck.
>>
>> Signed-off-by: Rickard Strandqvi
for cmdline mode on
connector 20
[ 45.351945] [drm:drm_target_preferred], looking for preferred mode on
connector 20
[ 45.351949] [drm:drm_target_preferred], found mode 1024x768
[ 45.351953] [drm:drm_setup_crtcs], picking CRTCs for 4096x4096 config
[ 45.351962] [drm:drm_setup_crtcs],
27.03.2014 20:14, Alejandro Comisario wrote:
> Seems like virtio (kvm 1.0) doesnt expose timeout on the guest side
> (ubuntu 12.04 on host and guest).
> So, how can i adjust the tinmeout on the guest ?
After a bit more talks on IRC yesterday, it turned out that the situation
is _much_ more "intere
10.02.2014 14:44, One Thousand Gnomes wrote:
>> fbcon is loaded so it isn't an issue.
>>
>> I tried 3.10 kernel initially (the above messages are from it), next
>> I tried 3.13 kernel too, and that one behaves exactly the same.
>>
>> As far as I remember, this system never worked with graphics well
12.02.2014 13:29, Heiko Carstens wrote:
> We want to remove s390 31 bit kernel support with Linux kernel 3.16.
Maybe you can send a patch for Documentation/feature-removal-schedule.txt
about this now?
Thanks,
/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Hello.
Today I rebooted my router into a new kernel and noticed that
the screen goes blank after booting the system (initial bootup
messages are visible). After some debugging it turns out that
the screen goes blank when loading gma500_gfx module.
This is an intel D2500CC motherboard with Atom D
Hello.
This is just an initial/preliminary heads-up, maybe mis-directed, about
a possible issue.
I upgraded 2 machines today to 3.10.25, and both shows some.. strangeness
within linux guests, which are also running 3.10.25. Revering to 3.10.24
in guests (compiled by the same compiler with the sa
31.08.2013 15:42, Ian Kent wrote:
[...]
> By leaving a Kconfig and Makefile in fs/autofs4 (to build autofs4.ko)
> with a deprication message sub-system maintainers and other users will
> make any needed changes before these are removed after two kernel versions.
> IMHO the presence of the warning i
15.04.2013 13:59, l...@tigusoft.pl пишет:
> There are 2 hard drives (normal, magnetic) in software raid 1
> on 3.2.41 kernel.
>
> When I write into them e.g. using dd from /dev/zero to a local file
> (ext4 on default settings), running 2 dd at once (writing two files) it
> starves all other progra
13.02.2013 11:37, Ian Kent wrote:
[]
So, you would like me to forward this to Linus?
I'd be inclined to wait until the window for 3.9 opens since Linus
probably has more than enough to do finalizing 3.8 right now.
I guess this change is anything but urgent ;)
Thanks,
/mjt
--
To unsubscribe f
It is nothing about code flow or anything else, it is about calling
kfree() unconditionally regardless whenever the argument is actually
NULL or non-NULL. It makes the code shorter and easier to read.
You can add my
Signed-off-by: Michael Tokarev
if you want.
Cc: Ian Kent
Cc: aut...@vger.kernel.o
Hello.
I'm trying to understand how to use transparent huge pages
(currently in x86). Before I used "explicit" huge pages
alot (mostly about hugetlbfs), but it looked like THP should
be easier so I gave it a try.
This tiny program:
- cut -
#include
#include
#include
#include
#inclu
On 20.12.2012 23:48, Fenghua Yu wrote:
> From: Fenghua Yu
>
> The problem in current microcode loading method is that we load a microcode
> way,
> way too late; ideally we should load it before turning paging on. This may
> only
> be practical on 32 bits since we can't get to 64-bit mode witho
On 02.10.2012 23:59, Jeff Garzik wrote:
> On 10/02/2012 03:44 PM, Michael Tokarev wrote:
>> On 02.10.2012 23:40, Jeff Garzik wrote:
>>
>>> Minor libata updates, nothing notable.
>>>
>>> 1) Apply -- and then revert -- the FUA feature. Caused
>>>
On 02.10.2012 23:40, Jeff Garzik wrote:
> Minor libata updates, nothing notable.
>
> 1) Apply -- and then revert -- the FUA feature. Caused
>disk corruption in linux-next, proving it cannot be turned on by
>default.
Any details on that? Disk corruprion is rather a nasty
side-effect ind
On 02.10.2012 22:49, Ferenc Wagner wrote:
> "Michael Chan" writes:
>> These are the likely fixes:
>>
>> commit cf9ecf4b631f649a964fa611f1a5e8874f2a76db
>> Author: Matt Carlson
>> Date: Mon Nov 28 09:41:03 2011 +
>>
>> tg3: Fix TSO CAP for 5704 devs w / ASF enabled
>
> You are exactly right:
On 19.09.2012 06:02, Rusty Russell wrote:
> From: Matthew Garrett
> Subject: module: taint kernel when lve module is loaded
> Date: Fri, 22 Jun 2012 13:49:31 -0400
>
> Cloudlinux have a product called lve that includes a kernel module. This
> was previously GPLed but is now under a proprietary l
On 20.08.2012 21:13, Tomas Racek wrote:
[]
Can we trim the old, large and now not-so-relevant discussion please? ;)
> I can provide you with more different traces if it can help. But I thought
> that maybe it will be more useful for you to try it on your own. So I've
> prepared some minimal debi
On 21.08.2012 08:47, Will Drewry wrote:
[]
> Functionally, I suspect this will work fine, but I am concerned that
> it is a bad move from an efficiency perspective (not unfixable
> though). Right now, the user-supplied value is converted from
> string-uuid to packed-uuid. This is then memcmp'd ac
On 18.08.2012 15:13, J. Bruce Fields wrote:
> On Sat, Aug 18, 2012 at 10:49:31AM +0400, Michael Tokarev wrote:
[]
>> Well. What can I say? With the change below applied (to 3.2 kernel
>> at least), I don't see any stalls or high CPU usage on the server
>> anymore.
>
> The results is a svc_recv() that will repeatedly return -EAGAIN, causing
> server threads to loop without doing any actual work.
>
> Reported-by: Michael Tokarev
> Signed-off-by: J. Bruce Fields
>
> diff --git a/net/sunrpc/svc_xprt.c b/net/sunrp
On 17.08.2012 21:26, Michael Tokarev wrote:
> On 17.08.2012 21:18, J. Bruce Fields wrote:
>> On Fri, Aug 17, 2012 at 09:12:38PM +0400, Michael Tokarev wrote:
> []
>>> So we're calling svc_recv in a tight loop, eating
>>> all available CPU. (The ab
On 17.08.2012 21:18, J. Bruce Fields wrote:
> On Fri, Aug 17, 2012 at 09:12:38PM +0400, Michael Tokarev wrote:
[]
>> So we're calling svc_recv in a tight loop, eating
>> all available CPU. (The above is with just 2 nfsd
>> threads).
>>
>> Something is defin
On 17.08.2012 20:00, J. Bruce Fields wrote:
[]> Uh, if I grepped my way through this right: it looks like it's the
> "memory" column of the "TCP" row of /proc/net/protocols; might be
> interesting to see how that's changing over time.
This file does not look interesting. Memory usage does not jum
On 12.07.2012 16:53, J. Bruce Fields wrote:
> On Tue, Jul 10, 2012 at 04:52:03PM +0400, Michael Tokarev wrote:
>> I tried to debug this again, maybe to reproduce in a virtual machine,
>> and found out that it is only 32bit server code shows this issue:
>> after updating the ke
On 03.08.2012 12:41, Jens Axboe wrote:
> On 08/03/2012 07:07 AM, majianpeng wrote:
[]
>> diff --git a/block/genhd.c b/block/genhd.c
>> index cac7366..d839723 100644
>> --- a/block/genhd.c
>> +++ b/block/genhd.c
>> @@ -835,7 +835,7 @@ static void disk_seqf_stop(struct seq_file *seqf, void
>> *v)
>>
On 15.07.2012 23:12, werner wrote:
> Even if rdev isn't often used, it should kept working, as it's included in
> many other programs, and principally in the installers.
rdev doesn't _exist_ anymore in current software,
including installers.
/mjt
--
To unsubscribe from this list: send the line
On 12.07.2012 16:08, werner wrote:
> There is a big problem since 3.5-rc1 which potentially mess the installations
>
> rdev don't give longer back the root device like /dev/sda1 , but in the
> bios form like 0x80010300
Note rdev returns information which is written to kernel image, not
inform
On 03.07.2012 00:25, Andrew Hunter wrote:
> diff --git a/include/linux/hash.h b/include/linux/hash.h
> index b80506b..daabc3d 100644
> --- a/include/linux/hash.h
> +++ b/include/linux/hash.h
> @@ -34,7 +34,9 @@
> static inline u64 hash_64(u64 val, unsigned int bits)
> {
> u64 hash = val;
>
again.
Something apparenlty isn't right on 32bits... ;)
(And yes, the prob is still present and is very annoying :)
Thanks,
/mjt
On 31.05.2012 17:51, Michael Tokarev wrote:
> On 31.05.2012 17:46, Myklebust, Trond wrote:
>> On Thu, 2012-05-31 at 17:24 +0400, Michael Tokarev wrote:
Jeremy Higdon wrote:
[]
> I'll put it even more strongly. My experience is that disabling write
> cache plus disabling barriers is often much faster than enabling both
> barriers and write cache enabled, when doing metadata intensive
> operations, as long as you have a drive that is good at CTQ/NC
Ric Wheeler wrote:
> Alasdair G Kergon wrote:
>> On Fri, Feb 15, 2008 at 03:20:10PM +0100, Andi Kleen wrote:
>>> On Fri, Feb 15, 2008 at 04:07:54PM +0300, Michael Tokarev wrote:
>>>> I wonder if it's worth the effort to try to implement this.
>>
>
Andrew Morton wrote:
> (suitable cc added)
Thanks. I was meant to sent it to linux-nfs originally, but
looks like i mistyped the address.
> (regression)
Now, after we did some more experiments with it, I don't think it's
a regression. I'll post a bit more details in a few hours when the
ongoin
Hugo Mills wrote:
> On Fri, Feb 15, 2008 at 10:00:00AM -0500, Calvin Walton wrote:
>> On Fri, 2008-02-15 at 13:46 +, Hugo Mills wrote:
>>> I'm getting these on my Dell Latitude D830:
>>>
>>> Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr
>>> 0x0 action 0x2 frozen
>>>
Jan Engelhardt wrote:
> On Feb 11 2008 13:39, Jan Kara wrote:
>>> But... I'm thinking about this scenario:
>>>
>>> # mount /data
>>> # quotaon /data
>>> (some maintenance stuff to be planned)
>>> # mount -o remount,ro /data
>>> (do backup etc)
>>> # mount -r remount,rw /data
>>>
>>> at this
Alasdair G Kergon wrote:
> On Fri, Feb 15, 2008 at 01:08:21PM +0100, Andi Kleen wrote:
>> Implement barrier support for single device DM devices
>
> Thanks. We've got some (more-invasive) dm patches in the works that
> attempt to use flushing to emulate barriers where we can't just
> pass them d
Hello!
After upgrading to 2.6.24 (from .23), we're seeing ALOT
of messages like in $subj in dmesg:
Feb 13 13:21:39 paltus kernel: RPC: bad TCP reclen 0x00020090 (large)
Feb 13 13:21:46 paltus kernel: printk: 3586 messages suppressed.
Feb 13 13:21:46 paltus kernel: RPC: bad TCP reclen 0x00020090 (
Andrew Morton wrote:
> On Thu, 7 Feb 2008 15:37:21 +0100 Jan Kara <[EMAIL PROTECTED]> wrote:
>
>> Turn off quotas before filesystem is remounted read only. Otherwise quota
>> will
>> try to write to read-only filesystem which does no good... We could also just
>> refuse to remount ro when quota i
Jan Kara wrote:
[]
>> I mean, why it locks in the first place? Quota subsystem trying
>> to write something into an read-only filesystem? If so, WHY it
>> is trying to do that on umount instead on a remount-ro?
> Actually, I couldn't reproduce the hang on my testing machine so I don't
> know e
Jan Kara wrote:
[deadlock after remount-ro followed with umount when
quota is enabled]
> Of course, thanks for report :). The problem is we allow remounting
> read only which we should refuse when quota is enabled. I'll fix that in
> a minute.
Hmm. While that will prevent the lockup, maybe it
For a long time I'm bitten by a bad interaction
of mount -o remount,ro and quota operations.
The sequence is as follows:
mount /fs
quotaon -ug /fs
mount -o remount,ro /fs
umount /fs
At this point, umount never returns. /proc/$pid/wchan
shows vfs_quota_off:
Feb 6 20:53:25 linux kernel: umo
Michael Tokarev wrote:
> Rafael J. Wysocki wrote:
[]
>> I guess it's a special variation of
>> http://bugzilla.kernel.org/show_bug.cgi?id=9528
>>
>> Please try to hibernate in the shutdown mode (ie. echo
>> "shutdown" into /sys/power/disk before hibe
Rafael J. Wysocki wrote:
> On Friday, 1 of February 2008, Michael Tokarev wrote:
[]
>> no_console_suspend it is. Tried that, the "S|" thing is still
>> here, but instead of "Suspending console(s)" it now shows
>> progress of suspending other devices. T
Pavel Machek wrote:
> On Fri 2008-02-01 00:41:06, Michael Tokarev wrote:
[]
>> With 2.6.24, it tries to suspend, saves pages to disk,
>> when prints this:
>>
>> ..Saving pages... done.
>> Sl
It's actually "S|", not "Sl".
>> Susp
Pavel Machek wrote:
[]
>> I'm looking at the uswsusp source (while the kernel compiles),
>> and have a question here. Is it possible to call some external
>> application (typically a shell script) to do the final work after
>> when the image has been written? I mean in principle - I
>> understand
Since I upgraded from 2.6.23 to 2.6.24, suspend to
disk does not work anymore on this machine. I'm
trying to debug this now, for several hours already,
without much luck so far.
The machine is based on AMD X2-64 (BE-2400) CPU and
NVidia MCP51PV (GeForce 6150/NForce 430) chipset.
Up until 2.6.23
Nigel Cunningham wrote:
[]
> That should be doable. How is your UPS connected? Presumably, with some
> modifications to the appropriate driver, we could send the commands when
> we're ready to shutdown. It would probably be useful whether or not your
> hibernating (if not, sending the commands coul
Rafael J. Wysocki wrote:
> On Wednesday, 30 of January 2008, Michael Tokarev wrote:
>> I'm trying to "glue" hibernation and UPS control
>> together, and have a question.
[]
> If your box hibernates and resumes correctly in the shutdown mode (ie.
Ohh-well.. :)
Bruno Prémont wrote:
> On Wednesday 30 January 2008 20:18:40 you wrote:
>> I'm trying to "glue" hibernation and UPS control
>> together, and have a question.
>>
>> When the system power comes off an UPS (Uninterruptable
>> Power Supply I mean), it's probably a good idea to turn
>> the UPS off when
I'm trying to "glue" hibernation and UPS control
together, and have a question.
When the system power comes off an UPS (Uninterruptable
Power Supply I mean), it's probably a good idea to turn
the UPS off when shutting the system down or hibernating.
Even with shutdown (not related to hibernating)
Yoav Artzi wrote:
> Hi,
>
>
> I have a 32-bit user land application which sends an IOCTL to a 64-bit
> Kernel module. I have a few different cmd codes that I can send through
> the IOCTL. For some reason I seem to always get the same IOCTL cmd from
> user land, no matter what the ioctl() call is
Stephen Hemminger wrote:
> On Tue, 29 Jan 2008 03:46:08 +0300
> Michael Tokarev <[EMAIL PROTECTED]> wrote:
[]
>> There are 2 drivers for 8139-based NICs. For really different two kinds
>> of hardware, which both uses the same PCI identifiers. Both drivers
>> "
Frederik Himpe wrote:
> Linux 2.6.24 kernel gives the following messages when udev coldplugging
> loads the driver for my NIC:
>
> 8139too :00:0b.0: This (id 10ec:8139 rev 20) is an enhanced 8139C+ chip
> 8139too :00:0b.0: Use the "8139cp" driver for improved performance and
> stability.
Is it normal that once I enable cpufreq on
a tickless system, it spews a warning:
Clocksource tsc unstable (delta = -288201154 ns)
?
It's an old problem, and I was thinking about
differences between x86-64 (it worked there) and
i386 kernels. But with 2.6.24, x86-64 can run
tickless as well, and
Michael Tokarev wrote:
> Dmitry Torokhov wrote:
> []
>>> Well, you use event device in any case; as for finding right one - I guess
>>> you look at device capabilities and filter what you need ...
>>>
>>> {pts/0}%
>>> cat /sys/devices/LN
Dmitry Torokhov wrote:
[]
>> Well, you use event device in any case; as for finding right one - I guess
>> you look at device capabilities and filter what you need ...
>>
>> {pts/0}%
>> cat /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/capabilities/key
>> 10 0 0 0
>
> Exactly. Any driver w
Dmitry Torokhov wrote:
> Hi Michael,
Hello!
[]
> There are keyboards (USB, PS2) with Sleep and Suspend buttons
> that are not related to ACPI nor APM. We had 2 options - add
> an input handler that would translate input events into ACPI
> events and feed /proc/acpi/event[*] or go other way around
(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
Jose de la Mancha wrote:
[]
> Jan Engelhardt wrote:
>> Not sure about Debian, but perhaps /sys/block/md0/md/safe_mode_delay
>> does something?
>
> --> I'll check that out. Does someone know about how this "safe mode delay"
> works ?
It's about something entirely different. This parameter tells m
Jiri Slaby wrote:
> (Old) mxser is obsoleted by mxser_new and scheduled for removal on Dec 2007.
> Remove it.
>
> Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
> ---
> Documentation/feature-removal-schedule.txt |8 -
> drivers/char/Kconfig | 11 -
> drivers/char/Makefi
Johannes Weiner wrote:
[]
> I still have a bug with cpufreq when using ondemand governor as default.
>
> The performance governor, which has been the essential default until
> 1c2562459faedc35927546cfa5273ec6c2884cce, was initialized with
> fs_initcall() instead of module_init() to make sure the
Michael Tokarev wrote:
> Kay Sievers wrote:
>> On Mon, 2007-12-17 at 08:29 +0300, Michael Tokarev wrote:
> []
>>> How to distinguish char devices from block devices in sysfs?
>>> Is the only way to read a symlink `subsystem' in the device
>>> directory?
Kay Sievers wrote:
> On Mon, 2007-12-17 at 08:29 +0300, Michael Tokarev wrote:
[]
>> How to distinguish char devices from block devices in sysfs?
>> Is the only way to read a symlink `subsystem' in the device
>> directory?
>
> By its subsystem value (block), from t
Kay Sievers wrote:
> On Mon, 2007-12-17 at 09:43 +1100, Neil Brown wrote:
>> On Saturday December 15, [EMAIL PROTECTED] wrote:
>>> On Dec 14, 2007 7:26 AM, NeilBrown <[EMAIL PROTECTED]> wrote:
Given an fd on a block device, returns a string like
/block/sda/sda1
whic
Michael Tokarev wrote:
> Erez Zadok wrote:
[...]
JFYI: My message bounced back:
<[EMAIL PROTECTED]>: host cs.sunysb.edu[130.245.1.15] said: 550 5.7.1 Access
denied (in reply to MAIL FROM command)
(stupid anti-spam policy @sunysb.edu, it seems - refusing
to accept *.ru as sender ad
Erez Zadok wrote:
> --- a/Documentation/filesystems/unionfs/usage.txt
> +++ b/Documentation/filesystems/unionfs/usage.txt
[]
> +OPTIONS can be any legal combination one of:
^
A small typo.
> +
> +- ro # mount file system read-only
> +- rw
This isn't a new issue, but so far no solution(s)
has been found, it seems. And with kernel development
going on, the issue becomes worse.
Up to 2.6.20 or so (I don't remember exactly, but if
I recall correctly the issue first appeared when new
timer code has been merged), there was no issues at
Lukas Hejtmanek wrote:
> Hello,
>
> the following patch should be applied into 2.6.24-rc3 as the mentioned Hitachi
> disk has also problem with NCQ.
Which problems, exactly?
Note that recent massive "NCQ horkage" isn't necessary due to drives fault.
Search for "spurious completions during NCQ" f
H. Peter Anvin wrote:
> Michael Tokarev wrote:
[2.6.23 on an i486 machine]
>> The result is immediately machine reboot right
>> after bootloader (etherboot) passes control to
>> the kernel -- BEFORE "Uncompressing linux"
>> message.
>>
>> 2.6.22
I tried to upgrade one of our old machines
(used as print servers and similar tasks) today
from 2.6.22 to 2.6.23[.9]. The same config (with
minor tweaks for new options), i486 base arch,
X86_GENERIC=y.
The result is immediately machine reboot right
after bootloader (etherboot) passes control
H. Peter Anvin wrote:
> Paul Rolland (ポール・ロラン) wrote:
[]
>> Measured 3978592228 cycles TSC warp between CPUs, turning off TSC clock.
>> Marking TSC unstable due to: check_tsc_sync_source failed.
[]
>> but I was wondering if this is a bug or a feature ;)
> The problem you're having is that the TSCs
Greg Kroah-Hartman wrote:
> We (the -stable team) are announcing the release of the 2.6.23.3 kernel.
> It contains a number of bugfixes for a number of architecture specific
> issues.
[.4, .5, .6 and .7 follows after .2 and .3]
I've seen the bunch of patches posted for review - split to several
se
Phillip Lougher wrote:
> Hi,
>
> I'm pleased to announce another release of Squashfs. This is the 22nd
> release in just over five years.
Thanks Phillip.
A tiny bug[fix] I always forgot to send... In fs/squashfs/inode.c,
constants TASK_UNINTERRUPTIBLE and TASK_INTERRUPTIBLE are used, but
they
Justin Piszcz wrote:
> On Sun, 4 Nov 2007, Michael Tokarev wrote:
[]
>> The next time you come across something like that, do a SysRq-T dump and
>> post that. It shows a stack trace of all processes - and in particular,
>> where exactly each task is stuck.
> Yes I got i
Justin Piszcz wrote:
> # ps auxww | grep D
> USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
> root 273 0.0 0.0 0 0 ?DOct21 14:40 [pdflush]
> root 274 0.0 0.0 0 0 ?DOct21 13:00 [pdflush]
>
> After several days/wee
vince kim wrote:
> This is a kernel patch to add support LZO compression in cramfs.
[]
> --- linux-2.6.23/fs/cramfs/inode.c 2007-10-09 13:31:38.0 -0700
> +++ linux-2.6.23_cramfs_lzo/fs/cramfs/inode.c2007-10-26
> 14:35:59.0 -0700
> @@ -31,6 +31,8 @@
> static const struct
Ingo Molnar wrote:
> * René Rebe <[EMAIL PROTECTED]> wrote:
>
>> Hi Linus et al.,
>>
>> 2.6.23 does not build with my usual .config on x86_64 and gcc-4.2.1:
[]
> your superblock build failure would be a new and so far unknown build
> breakage variant - please send the .config you used, and double
Jan Engelhardt wrote:
> On Oct 10 2007 14:36, Alexey Dobriyan wrote:
> --- linux-2.6.23/include/linux/mm.h.vanilla
> +++ linux-2.6.23/include/linux/mm.h
> +struct super_block;
> extern void drop_pagecache_sb(struct super_block *);
> void drop_pagecache(void);
> void drop_
Alexey Dobriyan wrote:
> On 10/10/07, René Rebe <[EMAIL PROTECTED]> wrote:
>> 2.6.23 does not build with my usual .config on x86_64 and gcc-4.2.1:
>>
>> In file included from fs/drop_caches.c:8:
>> include/linux/mm.h:1210: warning: 'struct super_block' declared inside
>> parameter list
>
>> --- li
Boaz Harrosh wrote:
[]
> If your target is a SCSI target you can gain up to 15% by using
> sg. Search on the net for the "sg utils" package. The source code
> of sg_dd and others are a grate example of how to do it.
>
> Other wise O_DIRECT is your friend. Also look for asynchronous
> I/O so you ha
Guennadi Liakhovetski wrote:
> Hi
>
> Ok, after a day of biseting, it turns out to be a compiler problem. The
> gcc-3.3.5 produces at least these two problems (Oops on i2c-viapro probe
> and disabled IRQs in USB), whereas 4.1.2 has no problem so far. Up to now
> 3.3.5 had no problem compiling 2
Al Viro wrote:
> On Mon, Oct 01, 2007 at 11:07:15AM +0100, Denys Vlasenko wrote:
>> Also attached is ndelaytest.c which can be used to test that
>> send(MSG_DONTWAIT) indeed is failing with EAGAIN if write would block
>> and that other processes never see O_NONBLOCK set.
>>
>> Comments?
>
> Never
Jan Engelhardt wrote:
> On Aug 2 2007 16:56, Michael Tokarev wrote:
>>>> I already can see comments from udev/sysfs maintainers here: "naming
>>>> is a policy which does not belong to kernel". It's a bullshit, because
>>>> kernel too has to
Jan Engelhardt wrote:
> On Aug 2 2007 12:56, Herbert Rosmanith wrote:
>>> On Aug 2 2007 12:42, Herbert Rosmanith wrote:
>>> There never *were* days when eth0 remained eth0 across such changes.
>> but there *were* days when eth0 was eth0, if the kernel reports it as such.
>> now there is no eth0 at
Jan Engelhardt wrote:
> On Aug 2 2007 15:23, Michael Tokarev wrote:
>> Herbert Rosmanith wrote:
>>>> On Aug 2 2007 12:42, Herbert Rosmanith wrote:
>>>> There never *were* days when eth0 remained eth0 across such changes.
>> []
>>> of course, that&#
Herbert Rosmanith wrote:
>> On Aug 2 2007 12:42, Herbert Rosmanith wrote:
>> There never *were* days when eth0 remained eth0 across such changes.
[]
> of course, that's problem with gentoo, not with the kernel.
Whenever it's a problem or not is questionable too. I mean,
ethX order depends on modu
Herbert Rosmanith wrote:
> hi,
Hello.
[]
> When doing the module load, the kernel says:
> eth0: VIA Rhine III at 0x1d000, 00:40:63:ee:96:56, IRQ 17.
> eth0: MII PHY found at address 1, status 0x7869 advertising 05e1 Link
> 45e1.
> eth1: VIA Rhine II at 0x1ec00, 00:40:63:ee:96:55, IRQ
BuraphaLinux Server wrote:
> Hello,
>
>I have had a hard time determining if /dev/sda is SCSI or SATA
> from my boot scripts. It matters for smartd which needs an added
> parameter -d sat in the configuration file for SATA drives. Finally I
Just FYI: Recent smartmontools (5.36+) can figure
One more reference to devfs in arch/i386/Kconfig, microcode driver description.
Signed-Off-By: Michael Tokarev <[EMAIL PROTECTED]>
--- linux-2.6.22/arch/i386/Kconfig.orig 2007-07-09 03:32:17.0 +0400
+++ linux-2.6.22/arch/i386/Kconfig 2007-07-11 23:35:45.0 +0400
@@
Michael Tokarev wrote:
> I bought a VIA PC2500 board a few days ago - this
> new series of their mobos,
>
[]
> It works generally - it boots, I can run my usual apps
> etc. But on a random (yet frequent) basis it segfaults
> here and there. For example:
Replying to my old
Dan Aloni wrote:
> On Thu, Jun 28, 2007 at 02:51:58PM +0400, Michael Tokarev wrote:
>> [..]
>> Test machine was using MPTSAS driver for the following card:
>> SCSI storage controller: LSI Logic / Symbios Logic SAS1064E PCI-Express
>> Fusion-MPT SAS (rev 02)
>&g
Tejun Heo wrote:
> Hello,
>
> Michael Tokarev wrote:
>> Well. It looks like the results does not depend on the
>> elevator. Originally I tried with deadline, and just
>> re-ran the test with noop (hence the long delay with
>> the answer) - changing linux elev
Tejun Heo wrote:
> Michael Tokarev wrote:
[]
>> A test drive is Seagate Barracuda ST3250620AS "desktop" drive,
>> 250Gb, cache size is 16Mb, 7200RPM.
[test shows that NCQ makes no difference whatsoever]
> And which elevator?
Well. It looks like the results doe
1 - 100 of 195 matches
Mail list logo
