Hi Ben,
--- Benjamin Herrenschmidt <[EMAIL PROTECTED]>
escribió:
> Yes. We discussed that with Linus back then. The
> problem is that the
> printk subsystem tend to abuse calling low level
> drivers at interrupt
> time, and in the case of blanking/unblanking, this
> can be a problem.
> Radeonfb f
Hi,
--- Jan Engelhardt <[EMAIL PROTECTED]>
escribió:
> The console is unblanked when you hit a key (or
> probably move a mouse too),
> not when some application outputs something on
> stdout/stderr/etc.
Before 2.6.12-rc2, the console was unblanked by just
writing to the console.
For keyboardles
Hi,
Looks like, since [1] was merged, a blanked console
(due to inactivity for example) doesn't get unblanked
anymore when new output is written to it.
This hunk of the already metioned patch, which
modifies vt_console_print() in drivers/char/vt.c, is
possibly the cause:
@@ -2220,9 +2220,6 @@
Hi,
Signed-off-by: Albert Herranz
<[EMAIL PROTECTED]>
The following patch prevents the crash dump helper
code found within kexec from breaking ppc which still
lacks crash dump functionality.
As discussed in [1], ksysfs crash_notes attribute
handling was left under CONFIG_KEXEC for simp
Hi,
On ppc machine_kexec.c, we must apply NORET_TYPE to
machine_kexec() as it does not return, and make it
noreturn (otherwise compiler complains).
NORET_TYPE is in fact not needed for
machine_kexec_simple().
Signed-off-by: Albert Herranz
Cheers,
Albert
--- Dave Jones <[EMAIL PROTECTED]> escribió:
> I'm at a loss to explain whats been happening with
> this symbol.
My patch was against the -mm series, as reported in
the original subject.
In the -mm series, the perfctr-ppc.patch already
defines that symbol. As that patch contains all the
perfctr
--- Andreas Gruenbacher <[EMAIL PROTECTED]> escribió:
> Hello again,
>
> this looks like a good candidate. Could you please
> try if it fixes the
> problem?
The Oops went away with this one.
> Thanks,
Your welcome.
Cheers,
Albert
__
--- Andreas Gruenbacher <[EMAIL PROTECTED]> escribió:
> Hello,
>
> here is a fix for a NULL pointer access problem with
> NFSv2 that isn't in
> 2.6.11-rc2-mm1, but it can't explain this NULL
> inode->i_op.
>
> -- Andreas.
Hi,
Yes, that patch seems unrelated.
Same Oops with or without it.
Tha
--- Andrew Morton <[EMAIL PROTECTED]> escribió:
> Can you tell us which filesystem is being bad? Add
> this:
>
> if (!inode->i_op)
> printk("%s is naughty\n", inode->i_sb->s_id);
>
> It's probably NFS - there has been some work done in
> there in -mm.
0:a is naughty
Cheer
Hi,
I'm getting a kernel Oops while booting 2.6.11-rc2-mm1
on a diskless (nfsroot based) embedded ppc system.
Vanilla 2.6.11-rc2 works Ok.
[...]
VFS: Mounted root (nfs filesystem) readonly.
Freeing unused kernel memory: 112k init
INIT: version 2.86 booting
Oops: kernel access of bad area, sig: 11
Hi,
This small patch fixes a compilation warning due to a
duplicate definition of MMCR0_PMXE.
The definition comes in perfctr-ppc.patch, but was
recently introduced too in Linus tree.
Cheers,
Albert
__
Renovamos el Correo Yahoo!: ¡
11 matches
Mail list logo
