Hi,
the same thing[0] happened again in 3.7-rc7, after ~20h uptime:
[40007.339487] [sched_delayed] sched: RT throttling activated
[69731.388717] BUG: MAX_STACK_TRACE_ENTRIES too low!
[69731.390371] turning off the locking correctness validator.
[69731.391942] Call Trace:
[69731.393525] [c9a61c10]
On Tue, 27 Nov 2012 at 19:06, Christian Kujau wrote:
> the same thing[0] happened again in 3.7-rc7, after ~20h uptime:
I found the following on patchwork, but this seems to deal with powerpc64
only, while this PowerBook G4 of mine is powerpc32:
http://patchwork.ozlabs.org/patch/193414/
On Wed, 28 Nov 2012 at 16:41, Li Zhong wrote:
> Would you please help to try the following fix? I don't have a powerpc32
> machine for test...
I've just applied this to 3.7-rc7 and booted the machine. I don't know how
to trigger this bug, so it might take a while until it happens again - or
not,
On Sun, 27 Jan 2013 at 14:56, Christian Kujau wrote:
> Hm, is there no chance to get this into 3.8? I've been running with this
> patch applied since 3.7-rc7 and it got rid of this
> "MAX_STACK_TRACE_ENTRIES too low" message. I've just upgraded to 3.8-rc5
>
Hi,
similar to what I reported earlier [0] for 3.8.0-rc1, this happens during
"ifup wlan0" (which in effect starts wpa_supplicant to bring up a Broadcom
b43 wifi network interface). The interface is working though and continues
to work over several ifup/ifdown iterations.
The backtrace looks a
forwarding to lkml, not sure how many people read b43-dev...
Hi,
while playing around with this BCM4306 (b43) wifi NIC (and reporting some
lockdep issues, [0]), I noticed that the chip could be used as a HWRNG and
driver support for this has been added years ago - great, I never knew!
But when
On Tue, 15 Jan 2013 at 14:59, Li Zhong wrote:
> FYI, it is already in the next of ppc tree
> http://git.kernel.org/?p=linux/kernel/git/benh/powerpc.git;a=shortlog;h=refs/heads/next
>
> I guess it would get into 3.9, at least.
Hm, is there no chance to get this into 3.8? I've been running with t
Vasiliy Kulikov wrote:
>> But still, I wonder if this is
>> intended behaviour.
>
>Yes.
>
>If you think such side channel attacks are something you don't care,
>just turn hidepid off. That's why it is an option.
>
>If you want to turn it off for some users, use gid=XXX.
Maybe my initial questio
Christian Kujau wrote:
>Vasiliy Kulikov
>"pgrep sgid-program" returned nothing but "kill pics off stiff program"
Gaah, that should read "kill pid-of-sgid-program", sorry.
C.
--
To unsubscribe from this list: send the line "unsubscribe linux-k
Hi,
I was wondering why I cannot see processes that were started from SGID
programs:
$ grep ^proc /proc/mounts
proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2 0 0
$ ls -n `which ssh-agent`
-rwxr-sr-x 1 0 103 132748 Feb 8 2013 /usr/bin/ssh-agent
$ ev
On Sun, 8 Sep 2013 at 23:42, Eric W. Biederman wrote:
> I don't have a clue why anyone would want to hide processes, and make
> their own lives more difficult.
Oh, there are plenty of usescases, I'm sure. And I for one am thankful
that this process hiding option made it into the kernel. Or, to an
On Wed, 28 Nov 2012 at 16:41, Li Zhong wrote:
> On Tue, 2012-11-27 at 19:22 -0800, Christian Kujau wrote:
> > On Tue, 27 Nov 2012 at 19:06, Christian Kujau wrote:
> > > the same thing[0] happened again in 3.7-rc7, after ~20h uptime:
> >
> > I found the following o
Hi,
after upgrading from 3.6.0-08492-gd43 to 3.7.0-rc4 and running it for a
day or so, this happened:
[27148.965634] BUG: MAX_STACK_TRACE_ENTRIES too low!
[27148.967356] turning off the locking correctness validator.
[27148.968967] Call Trace:
[27148.970577] [ec633d00] [c0009064] show_stack+0x70
On Sun, 23 Dec 2012 at 13:34, Christian Kujau wrote:
> On Sat, 22 Dec 2012 at 16:28, Maciej Rutecki wrote:
> > Got during suspend to disk:
>
> I got a similar message on a powerpc G4 system, right after bootup (no
> suspend involved):
>
> http://nerdbynature.de/bit
On Sat, 22 Dec 2012 at 16:28, Maciej Rutecki wrote:
> Got during suspend to disk:
I got a similar message on a powerpc G4 system, right after bootup (no
suspend involved):
http://nerdbynature.de/bits/3.8.0-rc1/
[ 97.803049] ==
[ 97.803
Since no one objected[0] and Nico kinda approved of my suggestion to
remove "git update-index", I propose the 2nd version of this patch
for 3.11 (Linux, that is)
[0] https://lkml.org/lkml/2013/6/9/185
---
Signed-off-by: Christian Kujau
Cc: Nico Schottelius
I just stumb
Hi,
I just stumbled across another[0] issue when scripts/setlocalversion
operates on a write-protected source tree. Back then[0] the source tree
was on an read-only NFS share, so "test -w" was introduced before "git
update-index" was run.
This time, the source tree is on read/write NFS share,
Hi,
after upgrading from 3.8.0-rc7 to 3.9.0-rc1, the following message appears
after booting and after dm-crypt (LUKS) partitions are mounted and
exported via NFS:
---
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off
On Sun, 17 Feb 2008, Sergio Luis wrote:
It doesn't fix the problem totally. If we select
Virtualization->Linux hypervisor example code (CONFIG_LGUEST)
as a module, we will get the same build errors,
Confirmed, the build errors persist with CONFIG_LGUEST=m and Rusty's patch
applied.
thanks,
C
On Sun, 17 Feb 2008, allied internet ag- Stefan Priebe wrote:
One week ago we upgraded about 300 servers from 2.6.20.20 to 2.6.24.2.
Did you test with *one* server before upgrading all 300? If not, please do
and try to upgrade in smaller steps, e.g. 2.6.20->2.6.21 and see when it
breaks. Add
On Sun, 17 Feb 2008, Sergio Luis wrote:
oops. sorry, I just realized I missed the makefile part. I changed
the config symbol to CONFIG_LGUEST_HYPERVISOR so I should change it on
the makefile as well. reposting an updated patch for testing:
Hm, now I cannot select LGUEST as a module any more:
On Mon, 18 Feb 2008, Sergio Luis wrote:
if you select Y here it will prompt you about the lguest
hypervisor, the code in question, the one you want to build, and you
will then be able to select it as a module, if you want, or built-in
into the kernel.
Ah, thanks for the clarification. And yes
[Cc'ed lkml, hence the full-quote]
On Fri, 12 Oct 2012 at 08:33, Dave Chinner wrote:
> On Thu, Oct 11, 2012 at 11:13:14AM -0700, Christian Kujau wrote:
> > Hi,
> >
> > since Linux 3.5 I'm seeing these "inconsistent lock state" lockdep
> > warni
On Wed, 28 Nov 2012 at 16:41, Li Zhong wrote:
> On Tue, 2012-11-27 at 19:22 -0800, Christian Kujau wrote:
> > On Tue, 27 Nov 2012 at 19:06, Christian Kujau wrote:
> > > the same thing[0] happened again in 3.7-rc7, after ~20h uptime:
> >
> > I found the following o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
howdy,
yesterday i hit an Oops when i tried to play an mp3 with xmms. nothing
unusual. the thing is - i've not changed the kernel (2.6.11-gentoo-r5) for
a while, but changed some (multimedia related) libs on my system. xmms
just segfaults and it all s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lee Revell wrote:
>
> Fixed in 2.6.11.7.
>
thank you & sorry for the noise.
Christian.
- --
BOFH excuse #20:
divide-by-zero error
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesper Juhl wrote:
>
> ^ you should send such info inline in the email - having to go check
> external links makes a lot of people ignore the stuff right then and
yeah, but the oops doesn't wrap at 80 chars itsself and often oopses are
hardly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Takashi Iwai wrote:
>
> Also, the latest CVS alsa-lib checks the timer protocol version to
> avoid this Oops with the older kenel. 1.0.9-rc3 is planned to be
> released soon, so wait for a moment...
um, i'll wait for the next release as i don't trac
Stelian Pop schrieb:
> After resyncing cogito to the latest version (which incorporates the
> 'pack' changes, which were causing the failure), it does indeed work
> again, when using rsync.
>
hm, i haven't updated my git-tree (linux-2.6.git) for a while and i got
similiar error messages. i update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hello,
upon unmounting some NFSv3 shares, the following oops happened and i could
not remount any nfs shares after this:
lockd: cannot unmonitor 192.168.10.10
Unable to handle kernel NULL pointer dereference at virtual address
printing eip:
hi,
a few minutes after upgrading from -rc5 to -rc6 I got:
[ 1310.670986] =
[ 1310.671690] [ INFO: possible recursive locking detected ]
[ 1310.672097] 2.6.24-rc6 #1
[ 1310.672421] -
[ 1310.672828] FahCore_a0
On Sat, 5 Jan 2008, Davide Libenzi wrote:
A solution may be to move the call to ep_poll_safewake() (that'd become a
simple wake_up()) inside a tasklet or whatever is today trendy for delayed
work. But his kinda scares me to be honest, since epoll has already a
bunch of places where it could be as
Hi,
just FYI, upgrading to -rc8 gave the following messages in kern.log in
the morning hours, when the backups were run:
===
[ INFO: possible circular locking dependency detected ]
2.6.24-rc8 #2
-
On Sun, 25 Nov 2007, Christoph Hellwig wrote:
This patch does exactly that and reverts xfs_file_readdir to what's
basically the 2.6.23 version minus the uio and vnops junk.
Thanks, works here too (without nordirplus as a mountoption).
Am I supposed to close the bug[0] or do you guys want to lea
On Tue, 4 Dec 2007, Ingo Molnar wrote:
thanks for the patch and the extensive description. I've applied this to
x86.git. Do you agree that this has no urgency for v2.6.24 and is thus
v2.6.25 material?
Pardon my ignorance, but: aren't we in -rc already? I was under the
assumption that during th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mauricio Lin wrote:
>>>
>>>Did this problem start from 2.6.11-rc2-bk10?
>>
>>i noticed it first at 2.6.11, then again with 2.6.11-rc5-bk2. suspecting
>>pppd to be the culprit to chew up all RAM after being terminated by my ISP
>>once a day - i just hav
hello again,
unfortunately i've hit OOM again, this time with "#define DEBUG" enabled
in mm/oom_kill.c:
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.3.txt
by "Mar 16 18:32" pppd died again and OOM kicked in 30min later.
(there are a *lot* messages of a shell script named "check-route.
Andrew Morton wrote:
>
> Some application went berzerk, used up all the swap and then oomed the box.
>
> You could perhaps run `top -d1' then hit M so the output is sorted by
> bloatiness, then try to catch the culprit.
i've already done that. as OOM happens when i am not around, i did that
with
Coywolf Qi Hunt wrote:
> I do "grep check-route.sh oom_2.6.11.3.txt | wc" and it shows 4365
duh, good catch! really!
> lines, which means there're 4365 that script processes running, from
> pid 4260 to12747, mostly with pretty low points, 123.
> Based on this points, suppose each script consumes
for the record: the "oom bug" turned out to be user generated. a *lot* of
small scripts were started, triggering oom again and again, user error.
the source of the problem is still pppd and the discussion continues as a
debian bugreport:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299875
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leigh Brown wrote:
>>>It detects the HBA, tries device discovery, gets a timeout, ABORT,
>>>timeout, TARGET RESET, timeout, BUS RESET, timeout, HOST RESET and
>>>there it hangs.
it does not really hang, it just tries to initialize every target of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Luther wrote:
>
> Oh, damn, need to fix my daily builder, should be ok for tomorrow. IN the
> meanwhile, you can try :
>
>
> http://people.debian.org/~luther/d-i/images/2005-02-23/powerpc/netboot/vmlinuz-prep.initrd
oh, what fun - it's boot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
i'm running 2.6.11-rc2-bk10 and still get my syslog clobbered with
messages like this:
PCI: :00:0c.0 has unsupported PM cap regs version (1)
$ lspci | grep :00:0c.0
:00:0c.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX
[Cyc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dominik Brodowski wrote:
> As the "unsupported PCI PM cap regs version (1)" handling caused trouble on
> some devices, it got removed in 2.6.11-rc5.
hm, the only change in the changelog with "PCI_PM_CAP" is:
<[EMAIL PROTECTED]>
[PATCH] PCI: s
hallo list,
today my machine went out out memory and noticing it several hours after
the first OOM message in the log, i wonder
1) why this happened at all and
2) why almost every service was killed despite the clever algorithms
documented in mm/oom_kill.c.
the first oom message went
Tony Luck wrote:
>
> Take a look at the driver (fs/proc/kcore.c) that creates this pseudo-file.
will do ;)
> Initially the size of the file is set from the size of your memory.
>
> Reading the file has the side-effect of setting up the ELF headers to make
> this look like an ELF file ... in fact
...replying to myself: it happened again!
switched back to 2.6.11-rc5-bk2, details will follow.
thanks,
Christian.
--
BOFH excuse #311:
transient bus protocol violation
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More m
Mauricio Lin wrote:
> Hi Christian,
>
> I found the 2.6.11-rc3 patch. The oom killer modification from
> Arcangeli was included in 2.6.11-rc3. Right? So this is correct, so
> the problem is not related to Arcangeli modification.
>
> Does anyone have idea?
hi Mauricio,
thank you for your answers
ok,
as "promised", it the OOM happened again with the same plain 2.6.11,
details here.
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11_2.txt
the following is a quite long, but please read on
(if anyone is reading at all :))
this time it happened at 08:01, and i could image some heavy cr
Andrew Morton wrote:
> Christian Kujau <[EMAIL PROTECTED]> wrote:
>
>>i was going to compile 2.6.11-rc5-bk4, to sort out the "bad" kernel.
>>compiling went fine. ok, finished some email, ok, suddenly my swap was
>>used up again, and no memory left
Mauricio Lin wrote:
> Hi Christian,
>
> I would like to know what are the kernel versions this problem happened.
>
> Did this problem start from 2.6.11-rc2-bk10?
i noticed it first at 2.6.11, then again with 2.6.11-rc5-bk2. suspecting
pppd to be the culprit to chew up all RAM after being termina
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Coywolf Qi Hunt wrote:
> In file mm/oom_kill.c, uncomment line 24: /* #define DEBUG */.
> And next time when oom happens again, we'll see the badness.
oh, good hint. will do this before the next reboot (in a few hours i guess)
thanks,
Christian.
-
hi again,
i had to wait for my pppoe session to be terminated by the remote peer
[1], and now it happened again with 2.6.11-rc5-bk2:
http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11-rc5-bk2_2.txt
http://nerdbynature.de/bits/sheep/2.6.11/oom/lsmod_2.6.11-rc5-bk2
http://nerdbynature.de/bits/
Hi there,
I noticed that I cannot use kernel nfsd any more with 2.6.24-rc2, last
working kernel as of now is 2.6.23.1. First I was using nfsv4 but
switching to nfsv3 did not help either: exported shares can be mounted
(client: 2.6-git/powerpc32, nfs-common-1.1.1~git-20070709-3ubuntu1), but
ru
On Tue, 13 Nov 2007, Andrew Morton wrote:
I think that we're fairly good about working the regressions in
Adrian/Michal/Rafael's lists but once Linus releases 2.6.x we tend to let
the unsolved ones slide, and we don't pay as much attention to the
regressions which 2.6.x testers report.
Can't we
On Tue, 13 Nov 2007, J. Bruce Fields wrote:
Could you get a sysrq-T trace? (First get the [nfsd] processes in [D]
Ah, I forgot about that. Will do as soon as I get a working kernel again.
I'm in the middle of git-bisecting and I had to mark the last 2 versions
as "bad" but only because they
On Tue, 13 Nov 2007, Andrew Morton wrote:
There are a number of process things we _could_ do. Like
- have bugfix-only kernel releases
Adrian Bunk does (did?) this with 2.6.16.x, although it always seemed to
me like an unrewarded one man show. AFAIK not even the big distros are
begging for bu
On Tue, 13 Nov 2007, Christian Kujau wrote:
Ah, I forgot about that. Will do as soon as I get a working kernel again. I'm
in the middle of git-bisecting and I had to mark the last 2 versions as "bad"
but only because they 1) Oopsed during boot or 2) could not load the kernel
On Wed, 14 Nov 2007, J. Bruce Fields wrote:
On Wed, Nov 14, 2007 at 09:43:40AM +0200, Benny Halevy wrote:
I wonder if this is a similar hang to what Christian was seeing here:
http://lkml.org/lkml/2007/11/13/319
Ah, thanks for noticing that. Christian Kujau, is /data an xfs
partition
On Wed, 14 Nov 2007, Chris Wedgwood wrote:
After some bisection pain (sg broken in the middle and XFS not
compiling in other places) the regression seems to be:
commit 051e7cd44ab8f0f7c2958371485b4a1ff64a8d1b
Author: Christoph Hellwig <[EMAIL PROTECTED]>
Date: Tue Aug 28 13:58:24 2007
On Wed, 14 Nov 2007, Christian Kujau wrote:
Yes, the nfsd process only got stuck when I did ls(1) (with or without -l) on
a NFS share which contained a XFS partition.
Since NFS was not working (the nfsd processes were already in D state), to
mount a CIFS share from the very same server (and
On Thu, November 15, 2007 08:51, Christian Kujau wrote:
> Since NFS was not working (the nfsd processes were already in D state),
> to mount a CIFS share from the very same server (and the same client).
That should read:
Since NFS was not working (the nfsd processes were already in D sta
On Thu, 15 Nov 2007, Christian Kujau wrote:
Upon accessing the /data/sub part of the CIFS share, the client hung, waiting
for the server to respond (the [cifs] kernel thread on the client was
spinning, waiting for i/o). On the server, similar things as with the nfsd
processes happened
Turns
On Fri, November 16, 2007 01:34, Chris Wedgwood wrote:
> I'm not sure what you're doing here, but a viable work-around for now
> might be to use nfsv2 mounts, something like
>
> mount -o vers=2 ...
> or to keep v3 and disable readdirplus doing something like:
> mount -o vers=3,nordirplus ...
OK, I
On Fri, 16 Nov 2007, Chris Wedgwood wrote:
Oops, I meant it for NFSD... and I'm somewhat serious. I'm not
saying it's a good long term solution, but a potentially safer
short-term workaround.
I've opened http://bugzilla.kernel.org/show_bug.cgi?id=9400 to track this
one (and to not forget abo
On Sun, 18 Nov 2007, Justin Piszcz wrote:
I wonder why so few people are seeing this, I'd have assumed that
NFSv3 && XFS is not sooo exotic...
Still on 2.6.23.x here (also use nfsv3 + xfs).
So, it's the "too few people are testing -rc kernels" issue again :(
Christian.
--
BOFH excuse #118:
t
Hi,
today I switched from 2.6.22.3 to 2.6.23-rc5 (skipped quite a few -rc
versions due to lack of time), and the box keeps panicking under certain
circumstances. I suspected disk related problems, because: when the box
is up, I usually resume ~10 bittorrent files. When doing this, each
file (
On Sun, 2 Sep 2007, Herbert Xu wrote:
You want this patch (by davem).
I applied the patch and the box is up for 1hr now. Since I was able to
reproduce the oops pretty reliable with this bittorrent thingy, I
did the same a few times now, but the box did NOT crash :)
Unfortunately people are
Hi,
after upgrading to 2.6.23-rc5 (and applying davem's fix [0]), lockdep
was quite noisy when I tried to shape my external (wireless) interface:
[ 6400.534545] FahCore_78.exe/3552 just changed the state of lock:
[ 6400.534713] (&dev->ingress_lock){-+..}, at: []
netif_receive_skb+0x2d5/0x3c0
Wow, I should really update more often. Skipping the last -rc versions
AND adding a new device (zd1211rw) to the box turns out to be quite
interesting ([0],[1]).
However, this time loading of a (proprietary) module is involved. Knowing
that lkml cannot really help here (and I should contact vmw
On Sun, 2 Sep 2007, Stephen Hemminger wrote:
Vendor module calls kernel api incorrectly. dev_set_promiscuity requires
that the calling thread hold rtnl mutex (ie call rtnl_lock). It's their bug,
netdev doesn't want to hear about it.
OK, that's all I needed to know. Thank you both for your comme
Hi,
I just wanted to report a 'it works again' for rc6: after encountering
the very same problems with -rc3 Jeff Garzik described in [0], I
upgraded to -rc5 and applied the proposed[1] patch[2].
Now, the knfsd behaved a bit better (nfs-mounted /home, X11
applications created thousands of empty
Hi there,
Since a few days I'm experiencing weird oopses on my iBook/G4 with
ubuntu's 2.6.22-7-powerpc and also with a vanilla 2.6.22-rc7-git8.
Now for the "weird" part: The oops happens when doing "make install" for
a piece of software (xine-ui media player) as *root*. No kidding, it
does N
On Thu, 12 Jul 2007, Nathan Lynch wrote:
Have you tried 2.6.22? Linus committed a utimensat-related oops fix
right before releasing it:
Ah, this seem to have fixed http://lkml.org/lkml/2007/7/8/21 and really
looks promising, I'll try 2.6.22-git2 now.
thanks,
Christian.
--
BOFH excuse #208:
Michel Dänzer wrote:
Does the patch below against the drm tree fix it? Only build tested.
yes, now glxinfo/glxgears returns without this badness, DRI is still
working fine. I've attached some details.
Thank you!
Christian.
---
From f0e6bdc165cb484b8992b14172a7280f301bf513 Mon Sep 17 00:00:0
On Sat, 2 Jun 2007, Justin Piszcz wrote:
Wondering as their were a lot of XFS related issues early on in
development..? The 2.6.22-rc3 kernel has the core 2 duo coretemp patch by
ruik which I want be running as long as 2.6.22-rc3 does not have any severe
XFS issues?
Tracking -rc and running
On Fri, 13 Jul 2007, Christian Kujau wrote:
Ah, this seem to have fixed http://lkml.org/lkml/2007/7/8/21 and really
looks promising, I'll try 2.6.22-git2 now.
for the record: running 2.6.22-git3 now and the Oopses went away ;)
thanks,
Christian.
--
BOFH excuse #352:
The cables are no
On Sat, 2 Jun 2007, Justin Piszcz wrote:
On Sat, 2 Jun 2007, Jeremy Fitzhardinge wrote:
XFS currently has a data-corrupting bug, where files which were appended
by small amounts may lose their updates on umount - I see this
corrupting hg repos. There's a patch which works for me, and is in
2.6.2
Just wondering: the last git snapshot is -rc3-git7 from 04.06.2007, have
they been discontinued or is some magic script just on vacation for a
few days?
thanks,
Christian.
--
make bzImage, not war
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Thu, 7 Jun 2007, Jan Engelhardt wrote:
After that came -rc4. Next one will be -rc4-git1.
Ah, ok. I'm using ketchup(1) to track 2.6-git, so it'd take a -rc4-git0
(same as rc4) to notice that the next version came out...
C.
--
make bzImage, not war
-
To unsubscribe from this list: send the
On Thu, 7 Jun 2007, Erik Mouw wrote:
If you want to track 2.6-git, why don't you just use git? A daily "git
Good point :)
But sometimes I want to track -mm and with ketchup(1) it's really easy
to switch between different trees. But don't bother, I'll take another
look at git...
C.
--
make b
seems to fix this.
Signed-off-by: Christian Kujau <[EMAIL PROTECTED]>
--- linux-2.6-dev/scripts/extract-ikconfig.orig 2007-06-01 22:53:49.0
+0200
+++ linux-2.6-dev/scripts/extract-ikconfig 2007-06-01 23:00:54.0
+0200
@@ -8,8 +8,8 @@ test -e $binoffset || cc -o $bin
On Sat, 9 Jun 2007, Julio M. Merino Vidal wrote:
Wouldn't this be better expressed as:
start=$(($start + 8))
size=$(($end - $start))
to avoid invoking a subshell?
This is certainly possible for lots for scripts, but was not the "scope"
of this patch. ` is not bash-specific and does not b
On Wed, 6 Jun 2007, Andreas Hartmann wrote:
After the first of the files is closed and the second has been started,
the machine is getting slower and slower and tons of the following
messages can be found in messages (that's the last one - afterwards the
machine crashed silently).
Is this 2.6.1
On Sat, 9 Jun 2007, Willy Tarreau wrote:
That's wrong. It will now require "expr" to be present and working on
the machine, eventhough it's certainly needed for other parts of the
Oh, I was under the strange assumption that "expr" was a shell-builtin.
Well, it's not so I guess I'll just live w
hi there,
yet another[0] badness, again from this very iBook running vanilla
2.6.22-rc1-git8:
[41653.487050] Badness at include/linux/slub_def.h:77
[41653.487060] Call Trace:
[41653.487068] [ecafbcb0] [c0008d00] show_stack+0x3c/0x194 (unreliable)
[41653.487097] [ecafbce0] [c01426d4] report_bug
On Wed, 4 Apr 2007, Francois Romieu wrote:
No serial cable ?
No, unfortunately this hosting provider does not have a serial console
to access :(
4 - try:
http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.21-rc5/r8169-20070402
Are they in -rc5 yet or 'not in -rc5 but should be applied to -r
On Wed, 4 Apr 2007, Christian Kujau wrote:
Maybe it's a real locking problem. Here are some more
suggestions for testing (if you don't find anything better):
- try without SMP, so: 'acpi=off lapic nosmp'
We were able to have our hosting provider to replace the 8139too with
On Fri, 6 Apr 2007, Christian Kujau wrote:
but yes, this seem to be different problems, for the curious among you I've
put details here: http://nerdbynature.de/bits/2.6.20.4/db2/
that's http://nerdbynature.de/bits/2.6.20.4/db1/2/ sorry.
--
BOFH excuse #270:
Someone has mes
Hi,
I've got this Asus A7N8X-X board and when using lm-sensors, these
messages occasionally show up in my kernel logs:
w83l785ts 1-002e: Couldn't read value from register 0x53. Please report.
...and reporting is what I do with this email :)
Please see .config, dmidecode and more right here:
h
Hi there,
we have serious problems with 2 of our servers: both shiny new amd64
dual core, with both 2GB RAM, 32bit kernel+userland (Debian/testing).
Both servers have 2 NICs, RTL8139 (eth0, irq10) and RTL8169s
(eth1, irq11).
Both boxes are running fine but after "a while" they lock up and
ev
On Mon, 2 Apr 2007, Chuck Ebbert wrote:
Please see http://nerdbynature.de/bits/2.6.20.4/ for details for both
hosts and feel free to ask for more details. Although both boxes are in
production we'll be happy test more bootoptions/patches and the like.
Where is the info from before you changed t
On Mon, 2 Apr 2007, Chuck Ebbert wrote:
Where is the info from before you changed to "noapic"? Or were the
machines always using XT-PIC for all the interrupts???
XT-PIC is only used since we switched to noapic, before there was
IO-APIC-fasteoi on both ethernet cards and interrupts were balance
On Tue, 3 Apr 2007, Len Brown wrote:
Which increased stability, disabling ACPI, or disabling the IOAPIC?
To be honest, we're not sure. See below.
Your box has MPS, so you should be able to use the IOAPIC in either mode.
MPS - Multiprocessor Specification? SMP? Yes, it'd be good to use the
On Tue, 3 Apr 2007, Jarek Poplawski wrote:
Did you try with 8139cp instead of 8139too?
I forgot about that, thanks.
(Maybe even try some other card to narrow the problem?)
We're try to convince our hosting provider to replace the NIC with a
e1000.
You could also try to test without ehci
On Mon, 2 Apr 2007, Chuck Ebbert wrote:
Where is the info from before you changed to "noapic"? Or were the
machines always using XT-PIC for all the interrupts???
We booted with 'acpi=off lapic' (with ACPI options compiled in, to be
able to boot with acpi=on later on) and the box locked up agai
On Tue, 3 Apr 2007, Jarek Poplawski wrote:
Did you try with 8139cp instead of 8139too?
Tried that, 8139cp could not be loaded :(
(Maybe even try some other card to narrow the problem?)
You could also try to test without ehci, if it's possible.
USB has been disabled completely. After booting
On Tue, 3 Apr 2007, Robert Hancock wrote:
These days I think it's usually best to have ACPI on with current systems.
Whooha, really? While I honor the acpi-folks' work when using a desktop
machine I am otherwise always reminded to the comment in
arch/i386/kernel/apm.c, which basically says: "
On Tue, 3 Apr 2007, Francois Romieu wrote:
Christian Kujau <[EMAIL PROTECTED]> :
If the apic voodoo makes no difference, you can:
1 - leave it enabled
Well, we tried to boot with ACPI compiled in again, but disabled during
boot:
- acpi=off lapic, crashed after 1h (almost exactly) of s
On Wed, 4 Apr 2007, Jarek Poplawski wrote:
So, it's a lot sooner than before. (BTW, isn't there anything
in debug log?)
No, nothing. I've set up remote-syslgging to the other node (node1
logging to node2 and vice versa) - nothing :(
I see both CPUs did interrupt handling again.
Yes, when
1 - 100 of 165 matches
Mail list logo
