I have this kernel bug when I update to kernel 2.6.17 I have no problem with 2.6.16 Thanks. Jose Alberto
I have problems with kernels newer that 2.6.16 and vdr. With kernel 2.6.17.9 see atached log1. With kernel 2.6.18-rc4 with kernels drivers and with last mercurial drivers see log2. After that errors I need to reboot. Thanks. Jose Alberto
El Lunes, 3 de Julio de 2006 18:44, Jose Alberto Reguero escribió:
I have this kernel bug when I update to kernel 2.6.17 I have no problem with 2.6.16 Thanks. Jose Alberto
I demand that Jose Alberto Reguero may or may not have written...
I have problems with kernels newer that 2.6.16 and vdr. With kernel 2.6.17.9 see atached log1. With kernel 2.6.18-rc4 with kernels drivers and with last mercurial drivers see log2. After that errors I need to reboot.
[snip]
Does this happen without the proprietary graphics card taintware?
El Lunes, 21 de Agosto de 2006 22:26, Darren Salt escribió:
I demand that Jose Alberto Reguero may or may not have written...
I have problems with kernels newer that 2.6.16 and vdr. With kernel 2.6.17.9 see atached log1. With kernel 2.6.18-rc4 with kernels drivers and with last mercurial drivers see log2. After that errors I need to reboot.
[snip]
Does this happen without the proprietary graphics card taintware?
Yes. I atach the log. Thanks. Jose Alberto
El Martes, 22 de Agosto de 2006 01:59, Jose Alberto Reguero escribió:
El Lunes, 21 de Agosto de 2006 22:26, Darren Salt escribió:
I demand that Jose Alberto Reguero may or may not have written...
I have problems with kernels newer that 2.6.16 and vdr. With kernel 2.6.17.9 see atached log1. With kernel 2.6.18-rc4 with kernels drivers and with last mercurial drivers see log2. After that errors I need to reboot.
[snip]
Does this happen without the proprietary graphics card taintware?
Yes. I atach the log. Thanks. Jose Alberto
Another log with kernel 2.6.27.11 What poison_obj means? What can produce Slab corruption? How I can debug it? Thanks. Jose Alberto
-
Darren Salt -
Jose Alberto Reguero