On Tuesday 17 April 2007 15:48, Alan Cox wrote:
So who is responsible for potential changing Linux code licensing for
allow if not incorporate CDDL code correct interraction without breaking
some law ?
Every single contributor, individually. Which won't happen.
The real test of whether
(Dropped LKML, whoops.)
On Wednesday 07 March 2007 04:59, you wrote:
We've finally hopefully started to put a dent in the regressions,
especially the suspend/resume problems introduced since 2.6.20.
So 2.6.21-rc3 is out there now, and there's some hope that it will work
more widely than -rc1
On Friday 09 March 2007 14:27, you wrote:
Jeff Garzik wrote:
[EMAIL PROTECTED] wrote:
From: Robert Hancock [EMAIL PROTECTED]
Reading from the ATA shadow registers while we are in ADMA mode may
cause undefined behavior. Don't read the ATA status register when
completing commands for
On Monday 12 March 2007 11:24, Frank van Maarseveen wrote:
On Mon, Mar 12, 2007 at 09:54:47AM +0100, Frank van Maarseveen wrote:
2.6.19 is ok, 2.6.20.[12] hangs from the moment DMA is turned on (hdparm
-d 1 /dev/hda):
hda: dma_timer_expiry: dma status == 0x20
hda: DMA timeout
On Monday 12 March 2007 13:25, Frank van Maarseveen wrote:
[snip]
So, are /dev/hd* going to disappear in a few years? iow, does it make
sense to _slowly_ start to migrate to /dev/sd*?
How would you propose doing this? I'm sure modern distros with an
initrd/initramfs probably already do some
On Monday 12 March 2007 15:02, Lluís Batlle wrote:
Oh, of course you're right. I was inside too much layers to think of
the tcp protocol, and I did not pay attention to it.
Maybe something could be added to the manpage anyway.
The bad thing is that there's no way I can use a socket for
On Friday 16 March 2007 23:44, you wrote:
Charles Shannon Hendrix wrote:
I normally run a modified 2.6.19 kernel and it works great.
I recently tried 2.6.20 and had severe SATA problems with it.
Yesterday I tried 2.6.20.3, and the problems are still there.
Can you try 2.6.21-rc and
On Tuesday 13 February 2007 21:19, linux-os (Dick Johnson) wrote:
Hi!
In the United States, some idiots have decided that the year 2000 scare
wasn't enough so they changed the start date for daylight savings time
from the first Sunday in April to the second Sunday in March.
Does anybody know
On Sunday 18 February 2007 19:39, Lennart Sorensen wrote:
[snip]
On a PC, the BIOS is supposed to assign interrupts to devices based on
those rules, since that is how the hardware must be done according to
the PCI specifications.
I set the BIOS for 'PnP OS installed'. Should I change
On Wednesday 21 March 2007 19:13, Paul Rolland wrote:
So, obviously, /dev is on /, but the stat(2) says no.
Who is right, and where is the bug ?
Kernel 2.4 had it right : /dev was on /, no doubt.
Some distros will mount tmpfs over /dev so that a minimal real dev can be
provided as a
On Sunday 15 April 2007 21:14, Mikko Tiihonen wrote:
Enables HPET for NVidia motherboards with broken BIOS. The patch reads the
HPET address from the pci config space. The patch should also work if ACPI
is disabled.
The HPET search is done in early-quirks because even
DECLARE_PCI_FIXUP_EARLY
On Tuesday 20 February 2007 04:17, Udo van den Heuvel wrote:
Krzysztof Halasa wrote:
Udo van den Heuvel [EMAIL PROTECTED] writes:
At the bottom I added a dmesg output of the kernel after boot.
I more or less know that irq 20 for the DVB-S card (saa7146 (1)) is
'working'. I know that irq
On Tuesday 20 February 2007 15:44, you wrote:
Alistair John Strachan wrote:
On Tuesday 20 February 2007 04:17, Udo van den Heuvel wrote:
Krzysztof Halasa wrote:
Is it a VIA ITX board? I think I have VIA's riser card somewhere,
could check what it does.
Yes, VIA Epia EN12000
On Wednesday 21 February 2007 22:40, Lennart Sorensen wrote:
On Wed, Feb 21, 2007 at 10:35:05PM +0100, Krzysztof Halasa wrote:
Do you mean both slots on the riser card? No, they have to be rotated.
Given the table from the manual:
The IRQ (interrupt request line) are hardware lines over
Hi Robert,
Despite all the work that went into making these less frequent with ADMA,
they're still possible to trigger.
[EMAIL PROTECTED]:~$ cat /proc/version
Linux version 2.6.21-rc2-damocles ([EMAIL PROTECTED]) (gcc version 4.1.2
20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Wed Feb 28
On Thursday 01 March 2007 14:45, Robert Hancock wrote:
This one seems a bit different. This time it's not related to NCQ vs.
non-NCQ (this is a non-NCQ write here), it's in ADMA mode (so it's
presumably not related to switching between ADMA and register mode,
unless perhaps a flush cache or
On Thursday 01 March 2007 15:13, Alistair John Strachan wrote:
On Thursday 01 March 2007 14:45, Robert Hancock wrote:
This one seems a bit different. This time it's not related to NCQ vs.
non-NCQ (this is a non-NCQ write here), it's in ADMA mode (so it's
presumably not related to switching
On Friday 02 March 2007 02:40, Robert Hancock wrote:
Alistair John Strachan wrote:
On Thursday 01 March 2007 15:13, Alistair John Strachan wrote:
On Thursday 01 March 2007 14:45, Robert Hancock wrote:
This one seems a bit different. This time it's not related to NCQ vs.
non-NCQ
On Friday 02 March 2007 15:05, you wrote:
Signed-off-by: Alan Cox [EMAIL PROTECTED]
[snip]
config PATA_OLDPIIX
- tristate Intel PATA old PIIX support (Experimental)
+ tristate Intel PATA support for the original PIIX
depends on PCI EXPERIMENTAL
help
- This option
Hi,
I've had some problems with 2.6.20 (but also with earlier kernels, like
Debian's 2.6.18) where one of the users on our system, running a Java6
application, is somehow able to make the userspace on the machine totally
unresponsive, denying all remote _and_ local access to the machine.
-
On Sunday 04 March 2007 23:25, Robert Hancock wrote:
Alistair John Strachan wrote:
Can you try reverting commit 721449bf0d51213fe3abf0ac3e3561ef9ea7827a
(link below) and see what effect that has?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commi
t;h
On Sunday 04 March 2007 23:25, Robert Hancock wrote:
Alistair John Strachan wrote:
Can you try reverting commit 721449bf0d51213fe3abf0ac3e3561ef9ea7827a
(link below) and see what effect that has?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commi
t;h
On Friday 30 March 2007 07:59, Bongani Hlope wrote:
On Friday 30 March 2007 05:49:14 Jan Engelhardt wrote:
On Mar 30 2007 11:37, Conke Hu wrote:
Is it possible to use C++ in linux kernel module? how?
I've tested but failed, there is an unknown symbol in the .o file from
c++ source
Bugzilla for this report: http://bugzilla.kernel.org/show_bug.cgi?id=9468
On Thursday 10 January 2008 17:28:22 you wrote:
I saw your thread on LKML about the problem with r8169. Did you ever
find a patch or solution?
No, we have not diagnosed the cause of the problem, beyond the swiotlb
On Tuesday 20 November 2007 01:53:31 Joe Perches wrote:
diff --git a/drivers/scsi/NCR_D700.c b/drivers/scsi/NCR_D700.c
index 9e64b21..99403a6 100644
--- a/drivers/scsi/NCR_D700.c
+++ b/drivers/scsi/NCR_D700.c
@@ -182,7 +182,7 @@ NCR_D700_probe_one(struct NCR_D700_private *p, int
siop, int
Hi,
I have recently assembled a Core 2 Duo system with 4GB RAM and I believe there
might be a bug in the r8169 driver in 4GB RAM configurations.
Initially I can use one of two active r8169 NICs on the motherboard with this
quantity of RAM with other devices, without issue. But after some
On Sunday 25 November 2007 00:25:10 Francois Romieu wrote:
Alistair John Strachan [EMAIL PROTECTED] :
[...]
The choke affects other devices on the system too, notably libata,
which does not recover gracefully. In my logs, I see a stream of:
DMA: Out of SW-IOMMU space for 7222 bytes
On Sunday 25 November 2007 01:27:54 Francois Romieu wrote:
Francois Romieu [EMAIL PROTECTED] :
Alistair John Strachan [EMAIL PROTECTED] :
[...]
The choke affects other devices on the system too, notably libata,
which does not recover gracefully. In my logs, I see a stream
On Tuesday 11 December 2007 23:31:18 Rene Herman wrote:
Good day.
Would some people on x86 (both 32 and 64) be kind enough to compile and run
the attached program? This is about testing how long I/O port access to
port 0x80 takes. It measures in CPU cycles so CPU speed is crucial in
On Saturday 15 December 2007 21:24:09 Gene Heskett wrote:
On Saturday 15 December 2007, Robert Hancock wrote:
Gene Heskett wrote:
Greetings;
When I asked about a sata controller earlier this week, I gave a link to
it. Unforch (maybe) when it actually arrived, the cards box showed a
Hi Jens,
I guessed from the oops that you might have an idea what's causing this oops
on shutdown/unmount. The git version (describe), a screenshot showing the
oops, a config, and dmesg for a booted kernel are available from:
http://devzero.co.uk/~alistair/oops-20071031/
I went back to -rc1
On Monday 24 September 2007 17:56:39 Antoine Martin wrote:
Hi Ted / LKML,
I've got this snapshot of an ext3 filesystem with a directory that
simply cannot be removed! (image below is just 1.2MB)
As root:
# wget http://users.nagafix.co.uk/~antoine/root-broken.bz2
# bunzip2 root-broken.bz2
#
On Tuesday 02 October 2007 04:41:49 Linus Torvalds wrote:
[snip]
In other words, people who know they may be affected and would want to
prepare can look at (for example)
git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-x86.git x86
and generally get ready for the
On Sunday 07 October 2007 20:13:09 you wrote:
On Sun, Oct 07, 2007 at 08:47:52PM +0200, Rene Herman wrote:
On 10/07/2007 06:12 PM, Ingo Molnar wrote:
* Oleg Verych [EMAIL PROTECTED] wrote:
Coloring isn't useful. If it was, it would be implemented ~16 years
ago.
Congratulations, this
On Monday 08 October 2007 00:10:10 Rene Herman wrote:
On 10/08/2007 12:40 AM, Alistair John Strachan wrote:
Splash screens are clearly cosmetic, and it's kind of shameful (imo) that
important messages explaining real problems are obscured from view by
functionless splash screens.
They're
On Monday 08 October 2007 00:10:10 Rene Herman wrote:
I find Alan's suggestion to provide the functionality the same way you'd
provide for translated kernel messages (seeing as how there also are people
that want those) much more sensible.
By the way, I agree that this is the best approach.
On Friday 05 October 2007 09:32:40 you wrote:
On Fri, 5 Oct 2007, Sam Ravnborg wrote:
cp: cannot stat `arch/x86_64/boot/bzImage': No such file or directory
Obviously, this file has moved to arch/x86/boot, but it seems like
possibly unnecessary breakage. I've been copying bzImage
On Sunday 02 September 2007 21:23:16 Jesper Juhl wrote:
On 02/09/07, Satyam Sharma [EMAIL PROTECTED] wrote:
Hi Jesper,
On Sun, 2 Sep 2007, Jesper Juhl wrote:
- if (!(interface = usb_find_interface(sisusb_driver,
subminor))) { - dev_err(sisusb-sisusb_dev-dev,
On Tuesday 04 September 2007 15:18:23 Abhijit Bhopatkar wrote:
[snip]
Anyway, it'd be helpful if someone else can check the same MacBook
(1st generation, not Pro?) whether the problem is reproducible.
To be precise its Macbook 1st Generation non pro. with subsystem id
0x106b0a00
Well a
On Monday 03 September 2007 09:06:25 Nicolas Mailhot wrote:
Mats Johannesson spamcan at bredband.net writes:
On 2007-09-01 16:07:48 Torsten Kaiser wrote:
[...]
The good:
+hpet-force-enable-on-vt8235-37-chipsets.patch
+hpet-force-enable-on-vt8235-37-chipsets-fix.patch
Kernel
On Tuesday 04 September 2007 16:26:27 Andi Kleen wrote:
Seconded. It's been largely ignored which is annoying because the HPET
works perfectly on this board. I assume the reason is still that nobody
from NVIDIA verified hardward support for the hack.
It's IMHO a bad idea to add any
On Monday 10 September 2007 14:08:45 Laurent Vivier wrote:
Avi Kivity wrote:
Ingo Molnar wrote:
* Laurent Vivier [EMAIL PROTECTED] wrote:
Ingo, please, could you have a look to these patches ?
The aim of these four patches is to introduce Virtual Machine time
accounting.
[PATCH
On Sunday 22 July 2007 22:04:24 Linus Torvalds wrote:
So give it all a good whacking, and report back about all the neat new
features!
I'm fairly sure this is already known about on SPARC64 (see David Miller's
email build-id changes break sparc64), but I just thought I'd let people
know the
On Friday 24 August 2007 20:20:02 Alan Cox wrote:
On Fri, 24 Aug 2007 14:39:10 +0100
Dermot Bradley [EMAIL PROTECTED] wrote:
I've just built a new machine using a ASUS M2A-VM boardboard (ATI SB600
chipset), AMD X2 3800+ processor, and 2 Western Digital 2.5 80Gb drives
running in RAID-1
On Monday 27 August 2007 10:28:09 Dermot Bradley wrote:
[snip]
Thanks for the help Alistair! One other point you may be able to help
with - this is the first time I've used a dual core processor and I
expected that /proc/interrupts would should interrupts distributed
between both cores whereas
On Saturday 11 August 2007 17:58:43 Gene Heskett wrote:
Greetings;
Running 23-rc2 since it came out, I've just discovered I have only the
system beep for sound. From lspci:
01:08.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
Subsystem: Creative Labs Unknown device
On Sunday 12 August 2007 21:06:43 Vadim Dyadkin wrote:
Robert Hancock пишет:
This could well be a problem with the nvidia driver as it shares the
same IRQ. The first step would be to see if the problem still shows up
without the nvidia binary module loaded.
Thank for your answer. This
On Sunday 14 October 2007 23:06:22 Stefan Heinrichsen wrote:
Hello,
I posted this question at comp.linux.misc and where told this would be a
better place therefore. I would like to do a internship in the field of the
Linux kernel.
Can someone tell me where to find a list of companies (don't
Hi,
I'm getting periodic oopses running KVM-33 on 2.6.23-rc1. Here is a digital
photo of the oops. Alarmingly, a lot of the time it triple faults the machine
and I don't get a chance to grab it. This time I was lucky, though.
http://devzero.co.uk/~alistair/kvm-2.6.23-rc1.jpg
Unfortunately,
I have absolutely no idea what triggers this crash.
Checked the RAM on the box? Kinda weird if you're getting VRAM corruption, I
wonder if this is due to the RAM failing at the point where the framebuffer
is mapped?
Try running memtest86 on it.
--
Cheers,
Alistair.
137/1 Warrender Park
On Sunday 29 July 2007 09:16:43 Avi Kivity wrote:
Alistair John Strachan wrote:
Hi,
I'm getting periodic oopses running KVM-33 on 2.6.23-rc1. Here is a
digital photo of the oops. Alarmingly, a lot of the time it triple faults
the machine and I don't get a chance to grab it. This time I
On Sunday 29 July 2007 12:34:28 you wrote:
[snip]
Doesn't help, I still get the same crashes. I tried 2.6.22 again and it's
rock solid by comparison.
Do you mean, kvm-33 on top of 2.6.22, or the kvm modules from 2.6.22?
Please describe your configuration *exactly*.
I'm using the kvm-33
On Sunday 29 July 2007 14:47:57 you wrote:
Alistair John Strachan wrote:
On Sunday 29 July 2007 12:34:28 you wrote:
[snip]
Doesn't help, I still get the same crashes. I tried 2.6.22 again and
it's rock solid by comparison.
Do you mean, kvm-33 on top of 2.6.22, or the kvm modules
On Sunday 29 July 2007 15:57:33 Gene Heskett wrote:
Is this a known problem? Do I need to report it to nvidia somehow? It
looks to me like it may be their problem, and I have submitted it, but if
anyone has a better idea, please advise. System is FC6, uptodate as of
yesterday.
Gene, this
On Monday 30 July 2007 14:00:13 Avi Kivity wrote:
How about the attached patch? (I haven't yet tried to reproduce, but
this can cause an AMD-only oops).
This seems to have fixed the problem. Thanks Avi.
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
-
To unsubscribe from
The real question is WHY do people keep writing essays about topics that have
_already_ been exhaustively explored in other threads? If you want a better
understanding of the situation, read the archives, DON'T post another
duplicate message about the same scheduler parade.
Unless you've got
On Friday 03 August 2007 15:51:59 T. J. Brumfield wrote:
I'm not going to argue with this point because I think this is exactly
what Linus meant. He wanted a scheduler that worked. And he knew it
wouldn't work immediately after merging it. So he had to go with the
person that he trusted
On Friday 03 August 2007 14:27:30 Андрій Мішковський wrote:
Bad things may happen if Linus gives a right of making decision to
other people (a big group of people). ;)
As you said, Linux is a public OS, so Con's code never will be lost.
That's the base of open source - people come and go, but
On Saturday 04 August 2007 14:17:34 Prakash Punnoor wrote:
Unfortunately this doesn't seem to have made it into 2.6.23-rc2. I need it
as well, to make Windows XP boot up w/o hanging or reebooting my host
machine.
It isn't in 2.6.23-rc2. I guess Avi should re-send to Linus and hopefully
it'll
On Thursday 26 April 2007 14:03:39 you wrote:
On Thu, Apr 26, 2007 at 05:44:40PM +0530, Sunil Naidu wrote:
Hello,
I did compile the kernel, boots good ;-) BTW, does anyone (on P-III)
facing a memory check skip or sort of? Not getting RAM info in the
dmesg. Unable to get dmseg from the
On Friday 27 April 2007 15:31:37 Sunil Naidu wrote:
On 4/26/07, Alistair John Strachan [EMAIL PROTECTED] wrote:
Don't you need to increase CONFIG_LOG_BUF_SHIFT ?
Yep, I need to. But, have to enable the Kernel Debug (DEBUG_KERNEL) to
increase the value from default 14 value to 15/16. I feel
the kernel log
buffer size.
Instead, move LOG_BUF_SHIFT into General Setup, so that people are more
likely to be able to change it such a circumstance that the default buffer
size is insufficient.
Signed-off-by: Alistair John Strachan [EMAIL PROTECTED]
---
diff --git a/init/Kconfig b/init/Kconfig
On Saturday 28 April 2007 20:53:37 Syren Baran wrote:
Hi,
i got a problem with the combination of an Asrock AM2NF4G-SATA2
mainboard with a Radeon X1900 (chip 1002,724b) graphics
card. /i386/pci/mmconfig.c reports a buggy bios (e000 is not
E820-reserved). System crashes only happen when
On Sunday 10 Apr 2005 19:29, you wrote:
Hello.
I am trying to format the CD-RW disc
on my NEC ND-3520A DVD writer, and the
results are completely unexpected: I do
cdrwtool -d /dev/cdrom -q
It proceeds with the formatting, but
while it does so, the system is pretty
much dead. It can do
On Monday 14 Feb 2005 21:11, Pavel Machek wrote:
[snip]
Table of known working systems:
Model hack (or how to do it)
---
--- IBM TP R32 / Type 2658-MMG none (1)
Athlon HP Omnibook XE3
On Tuesday 15 Feb 2005 12:12, Lorenzo Colitti wrote:
Alistair John Strachan wrote:
On Monday 14 Feb 2005 21:11, Pavel Machek wrote:
Table of known working systems:
Model hack (or how to do it)
[...]
HP NC6000 s3_bios (2)
The above report is incorrect. On 2.6.11
On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote:
[snip]
Ok, here is the output from dmidecode (Debian package) and from lspci. I
don't have acpidmp and I don't know where to get it, but if you think
it's necessary I can download it if you tell me where to find it.
Find below a diff of my
On Tuesday 15 Feb 2005 21:09, Lorenzo Colitti wrote:
[snip]
I would advise trying to compile a custom kernel from scratch with my
.config first.
I got S3 working first with a very basic kernel config, but I couldn't
get it to work with my usual kernel. Assuming it was some feature that
On Wednesday 16 Feb 2005 14:25, Kjartan Maraas wrote:
tir, 15,.02.2005 kl. 17.42 +, skrev Alistair John Strachan:
On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote:
[snip]
Ok, here is the output from dmidecode (Debian package) and from lspci.
I don't have acpidmp and I don't
On Wednesday 13 Jul 2005 16:30, Ingo Molnar wrote:
* Ingo Molnar [EMAIL PROTECTED] wrote:
it worked upon the first try, and indeed my testbox crashed within 10
seconds:
BUG: Unable to handle kernel NULL pointer dereference
BUG: Unable to handle kernel NULL pointer dereference at
On Thursday 14 Jul 2005 20:34, FyD wrote:
Dear All,
I have a problem with a program named Gaussian (http://www.gaussian.com)
(versions g98 or g03) and FC 4.0 (default kernel 2.6.11): I am used to take
Gaussian binaries compiled on the RedHat 9.0 version, and used them on FC
2.0 or FC 3.0. If
On Thursday 14 Jul 2005 21:16, Lee Revell wrote:
On Thu, 2005-07-14 at 20:58 +0100, Alistair John Strachan wrote:
the responsiveness of our instrument to 300us which is low enough
for the real-time PCR industry
PCR, as in polymerase chain reaction? They can do that in realtime?
Impressive
Hi Ingo,
(I searched the list for rt realtime x86_64 x86-64 before posting this, so I
hope it's not a duplicate).
I've noticed -31 compiles without notable error or warning on x86-64, so I
thought maybe it was a valid time to file a bug report about it not working.
The machine currently runs
On Sunday 17 Jul 2005 17:29, Michal Schmidt wrote:
Alistair John Strachan wrote:
Hi Ingo,
(I searched the list for rt realtime x86_64 x86-64 before posting this,
so I hope it's not a duplicate).
I've noticed -31 compiles without notable error or warning on x86-64, so
I thought maybe
On Tuesday 19 Jul 2005 17:47, Karim Yaghmour wrote:
I have a usb-attached HD that I use from time to time. When it's connected
to my desktop through a hub it works flawlessly. When connected to my Dell
D600 Laptop, however, it sometimes randomly exhibits a loud click (as if
the heads went
Hi,
Today I decided to try Ingo's rt-preempt patch on 2.6.12 (V0.7.51-02). I'm
most interested in the CONFIG_PREEMPT_RT mode, so I selected this option
instead of the others. I enabled a couple of the debugging options, but I
wasn't totally clear on which options are most useful, so I just
On Wednesday 06 Jul 2005 12:57, Alistair John Strachan wrote:
[snip]
Which debugging options are most useful for testing purposes? Is what I've
selected enough? Also, I got a few unexpected messages in dmesg on bootup.
I decided to just enable everything, as I got a lockup within 5 minutes
On Wednesday 06 Jul 2005 19:41, Ingo Molnar wrote:
* Ingo Molnar [EMAIL PROTECTED] wrote:
does the patch below help? We initialized the timestamps to 0, but
with jiffies starting out negative, that means a ~5 minutes gap until
we first reach a value of 0. That would explain the messages.
On Wednesday 06 Jul 2005 21:44, Ingo Molnar wrote:
[snip]
the ACPI-idle bug's primary effects were the missed wakeups, but they
should not cause lockups, because timer interrupts should always occur
and should eventually 'fix up' such missed wakeups.
but there's another side-effect of the
On Wednesday 06 Jul 2005 22:02, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
This is a completely unrelated question, but now we've got everything
under control.. how do I make quiet actually do something on the RT
patchset?
Currently I flag it on the kernel
On Wednesday 06 Jul 2005 18:27, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
great! Do the softlockup warnings still occur?
Yes, but in no greater a number.
could you apply the patch below, so that we can see what kind of time
gap the softlockup detector
On Wednesday 06 Jul 2005 18:01, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
I'm beginning to understand the issue, and I see why you think the
proposed patch fixes it. I'll compile and boot V0.7.51-05 now.
Indeed, this seems to have fixed it.
( softirq-timer
On Wednesday 06 Jul 2005 17:24, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
(generally i try to mark every message in the -RT kernel that signals
some sort of anomaly with a 'BUG:' prefix - that makes it easy to do a
'dmesg | grep BUG:' to find out whether
On Wednesday 06 Jul 2005 17:37, Alistair John Strachan wrote:
[big snip]
could you try the patch below (or the -51-05 patch that i just
uploaded), does it fix this latency?
Ingo
I'm beginning to understand the issue, and I see why you think the proposed
patch fixes it. I'll
On Wednesday 06 Jul 2005 17:28, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
On Wednesday 06 Jul 2005 14:39, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
Then it continues to boot. I'm getting periodic lockups under high
network load
On Wednesday 06 Jul 2005 14:39, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
Then it continues to boot. I'm getting periodic lockups under high
network load, however, though I suspect that might be the ipw2200
driver I compiled against the realtime-preempt kernel
On Wednesday 06 Jul 2005 14:31, Ingo Molnar wrote:
[snip]
for the first bootup it makes sense to enable most of them - just to
make sure everything is ok. They have performance overhead, but it
shouldnt show up during everyday use. (it will show up in benchmarks
though) Here's the options i
On Wednesday 06 Jul 2005 21:44, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
here's an updated patch - it will print out all timestamps too. (you'll
have to revert all previous softlockup patches first, via patch -R.)
Yep, thanks, that fixed it. I don't know why
On Thursday 07 Jul 2005 10:46, Alistair John Strachan wrote:
[snip]
Okay, when I brought my laptop back into work today for audio work, it
locked up again within two minutes. I realise now what the problem is, but
I don't have a serial cable here, so I'll have to rely on capturing the
oops
On Thursday 07 Jul 2005 12:29, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
Unfortunately, since this is called when the kernel crashes, it's
impossible for me to capture any messages prior to this spam, if there
even are any.
this is where serial logging
On Thursday 07 Jul 2005 12:42, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
do you have DEBUG_STACKOVERFLOW and latency tracing still enabled? The
combination of those two options is pretty good at detecting stack
overflows. Also, you might want to enable
On Thursday 07 Jul 2005 13:15, Alistair John Strachan wrote:
On Thursday 07 Jul 2005 12:42, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
do you have DEBUG_STACKOVERFLOW and latency tracing still enabled?
The combination of those two options is pretty good
On Thursday 07 Jul 2005 13:29, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
http://devzero.co.uk/~alistair/oops1.jpeg
I disabled the trace and the STACKOVERFLOW option seems to help; I've
got a (slightly truncated) oops from the kernel. What happens is that
I get
Hi,
Latest patch doesn't compile on non-i386 arches. I found all users of INIT_FS;
need to be audited to INIT_FS(init_fs); like i386; then it compiles fine.
Ingo, could you also respond to my other thread, I uploaded the screenshot you
requested.
--
Cheers,
Alistair.
personal:
On Thursday 07 Jul 2005 21:14, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
Latest patch doesn't compile on non-i386 arches. I found all users of
INIT_FS; need to be audited to INIT_FS(init_fs); like i386; then it
compiles fine.
thx, i've put this fix into -51-14
On Thursday 07 Jul 2005 12:42, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
do you have DEBUG_STACKOVERFLOW and latency tracing still enabled? The
combination of those two options is pretty good at detecting stack
overflows. Also, you might want to enable
On Friday 08 Jul 2005 12:48, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
Well, just to let others who have this problem know, it's clear that
Ingo's rt-preempt patches increase stack pressure on systems (like
mine) where stack is borderline under 4K by default
On Friday 08 Jul 2005 18:48, Jakub Jelinek wrote:
On Fri, Jul 08, 2005 at 06:42:53PM +0100, Alistair John Strachan wrote:
btw., which gcc version are you using?
Not the GCC version known to bloat stacks ;-)
3.4.4, on both my machines. I'm not touching 4.x until 4.0.1 is released
On Friday 08 Jul 2005 12:46, Ingo Molnar wrote:
[snip]
Ok. Could you try to debug this some more? In the -51-17 patch i've
implemented a new stack-overflow debugging feature: 'stack footprint
maximum searching'. It is automatically active if you have
CONFIG_LATENCY_TRACE and
On Friday 08 Jul 2005 20:48, Ingo Molnar wrote:
* Alistair John Strachan [EMAIL PROTECTED] wrote:
Unfortunately I see nothing like this when the machine crashes. Find
attached my config, which has CONFIG_4KSTACKS and the options you
specified. Are you sure this is sufficient to enable
1 - 100 of 417 matches
Mail list logo
