Ingo Molnar wrote:
i was adding WARN_ON()s that werent true 'warnings' but 'bugs'.
IME, the trace dump in the kernel log looks scary enough to be
eventually reported, even if prefixed with WARNING:.
--
Stefan Richter
-=-=-=== -=-= ==--=
http://arcgraph.de/sr/
-
To unsubscribe from this
On Fri, 25 May 2007, Stefan Richter wrote:
Ingo Molnar wrote:
i was adding WARN_ON()s that werent true 'warnings' but 'bugs'.
IME, the trace dump in the kernel log looks scary enough to be
eventually reported, even if prefixed with WARNING:.
Oh, absolutely. It will stand out like a sore
On Fri, 25 May 2007 14:34:56 +0200 Ingo Molnar [EMAIL PROTECTED] wrote:
* Chris Newport [EMAIL PROTECTED] wrote:
There is a fundamental problem in getting a decent log to debug a
crashed kernel. Maybe we should take a hint from Solaris. If the
kernel crashes Solaris dumps core to swap
On Fri, 25 May 2007, Andrew Morton wrote:
the image. But we're not - kernel developers don't know how to turn the
thing on in $RANDOM_DISTRO, testers have no experience with the feature
and kernel developers don't have experience handling the crash images.
Well, we for instance have problems
Disk dumps etc are options at things like wall street. But look at the bug
reports, and ask yourself how many of them happen at Wall Street, and how
many of them would even be _relevant_ to somebody there?
There is an additional factor - dumps contain data which variously is -
copyright
On Fri, 25 May 2007, Chuck Ebbert wrote:
Windows can dump memory to the swap file on crash. Default is a minidump
IIRC but you can set it to dump all memory (or none.)
And Linux can too.
And exactly as with Windows, nobody should ever use it. It's a *developer*
thing. It's not a user
On 05/25/2007 12:45 PM, Linus Torvalds wrote:
Yes, in a controlled environment, dumping the whole memory image to disk
may be the right thing to do. BUT: in a controlled environment, you'll
never get the kind of usage that Linux gets. Why do you think Linux (and
Windows, for that matter)
On Fri, May 25, 2007 at 10:37:14AM -0700, Andrew Morton wrote:
Often we don't even get that: I was in X and it didn't hit the logs.
Thats mostly solved by fixing the Oops and framebuffer code to co-operate
and is a different problem
Alan
-
To unsubscribe from this list: send the line
On Fri, 25 May 2007 10:19:52 -0700 (PDT) Linus Torvalds [EMAIL PROTECTED]
wrote:
On Fri, 25 May 2007, Alan Cox wrote:
There is an additional factor - dumps contain data which variously is -
copyright third parties, protected by privacy laws, just personally
private, security
Sorry, I did not make myself clear.
Linus Torvalds wrote:
On Fri, 25 May 2007, Chris Newport wrote:
Maybe we should take a hint from Solaris.
No. Solaris is shit. They make their decisions based on we control the
hardware kind of setup.
Not really a Solaris feature. This is a
Hi Linus.
Davem asked me to look at the sparc64 linker script.
It used a hardcoded alignment value of 8192 where the correct
size is PAGE_SIZE (which may be 8192).
I have made both a minimal fix (see below) and
a version where the linker script becomes as readable as linker scripts can be.
Signed-off-by: Kyle McMartin [EMAIL PROTECTED]
---
PS: Anyone have a nice prebuilt i386-sparc{32,64} xcompiler setup
I could snag? Would be nice to testbuild these patches before I send
them out next time.
diff --git a/arch/sparc/lib/atomic32.c b/arch/sparc/lib/atomic32.c
index 559335f..a45caca
From: Chris Newport [EMAIL PROTECTED]
Date: Fri, 25 May 2007 19:03:51 +0100
Not really a Solaris feature. This is a feature of the Openboot PROM
which is also used by several other vendors.
The Openboot PROM knows how to write to disk. The same should
apply on Apple hardware and others
From: Martin Habets [EMAIL PROTECTED]
Date: Sat, 26 May 2007 01:24:40 +0100
Hi Kyle,
After some minor fixes this builds, and the DRM drivers also
build again. I cannot test this since I do not have a machine with
PCI or these cards.
Removed your name in the comment, as that went out of
On Fri, 2007-05-25 at 22:00 -0700, David Miller wrote:
Sparc 32-bit barely has PCI let alone 3D graphics cards.
If it's a build issue, simply disallow DRM to be turned on for
SPARC32.
I was really wondering about this one. I'd assumed DRM was already
conditionalized out for sparc32.
~spot
15 matches
Mail list logo
