Re: Asunto relacionado con 'kernel panic'
On Sun, Jun 14, 2015 at 04:19:12PM +, Camaleón wrote: En cuanto al kernel panic quizá lo que se cae es el entorno gráfico, Eso es *imposible*. En un kernel panic el que se cae es el núcleo, por definición. Después de un kernel panic no hay ssh que valga. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150614201220.ga6...@cantor.unex.es
Asunto relacionado con 'kernel panic'
Saludos a la lista. Quise aprovechar esta ventana para lanzar esta duda que me atosiga sin par. En mi laptop tengo instalado Debian Jessie con 3 entornos de escritorio: GNOME, LXDE y Openbox (openbox, pero, usando la barra de tareas estilo lxde porque es la que se acopla mejor). Como sea, el asunto es este: a veces, en GNOME todo se congela, excepto el ratón... ¡pero exaspera y creo que se da cuenta!, y al rato, ¡KABOM! Me sale una BSOD con un montón de texto que no entiendo, sólo reconozco el modelo de mi ordenador y el mensaje kernel panic. Ahora, esta es mi duda: ¿esto dónde se guarda para compartirlo, por qué sucede sólo con GNOME3 y cómo se descifra lo que muestra? -- Ayuda para hacer preguntas inteligentes: http://is.gd/NJIwRz
Re: Asunto relacionado con 'kernel panic'
¿esto dónde se guarda para compartirlo? Por defecto no se guardan en ninguna parte, pero puedes probar una cosa que se llama netconsole y a lo mejor consigues registrarlo de forma remota. ¿por qué sucede sólo con GNOME3? Seguramente porque GNOME le pide cosas a la tarjeta gráfica que la tarjeta gráfica no es capaz de dar (por un error en la programación del controlador de vídeo). ¿y cómo se descifra lo que muestra? Necesitarás conocimientos avanzados de ensamblador, no creo que te compense. Imagina que en caso de cuelgue saliera un mensaje en suajili. Suponiendo que no tienes ningún viaje previsto a Tanzania: ¿Te pondrías a estudiar suajili *solamente* para entender esos mensajes? Yo creo que no, y no es que quiera desanimarte, pero en casos como este se debe hacer un pequeño análisis de coste/beneficio. Los programadores del núcleo saben de estas cosas porque les gusta y se dedican a ello, pero un usuario normal no tiene por qué saber ensamblador (que luego nos critican diciendo que para usar Linux en el escritorio hay que saber mucho). Pero si tienes tiempo y ganas, pues a ello, que el saber no ocupa lugar. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150613182225.gb25...@cantor.unex.es
causa de kernel panic
hola! esta mañana, al arrancar el sistema Debian de mi portátil me ha anunciado que debido a un kernel panic no podía montar el disco donde está linux instalado. Concretamente después de acceder al sistema mediante Grub de la manera habitual, en la pantalla aparecía una serie de lineas inintiligibles para mi terminando esa serie con una un poco más familiar: end Kernel Panic - not syncing : VFS : Unable to mount root fs on unknown-block(0,0) He buscado por internet esa frase y por suerte alguien supo resolverlo para ubuntu[1], lo he aplicado y ya está todo funcionando perfectamente :D Pero me quedo con la duda de que ha podido pasar, puesto que ayer no instalé nada, apagué el ordenador con normalidad y esta mañana me sale con un kernel panic :-( . No se si hay explicación para una cosa así, pero si la sabéis... por fa, contádmela, al menos para evitar que vuelva a pasar si es que se puede evitar, claro. En fin, gracias! [1] http://ubuntuforums.org/showthread.php?t=1769102 Laura
Re: causa de kernel panic
El Thu, 11 Jun 2015 16:20:53 +0200, laura escribió: hola! (ese html...) esta mañana, al arrancar el sistema Debian de mi portátil me ha anunciado que debido a un kernel panic no podía montar el disco donde está linux instalado. Concretamente después de acceder al sistema mediante Grub de la manera habitual, en la pantalla aparecía una serie de lineas inintiligibles para mi terminando esa serie con una un poco más familiar: end Kernel Panic - not syncing : VFS : Unable to mount root fs on unknown-block(0,0) He buscado por internet esa frase y por suerte alguien supo resolverlo para ubuntu[1], lo he aplicado y ya está todo funcionando perfectamente :D Pero me quedo con la duda de que ha podido pasar, puesto que ayer no instalé nada, apagué el ordenador con normalidad y esta mañana me sale con un kernel panic :-( . No se si hay explicación para una cosa así, pero si la sabéis... por fa, contádmela, al menos para evitar que vuelva a pasar si es que se puede evitar, claro. Quizá realizaste alguna actualización del sistema y no apagaste el equipo hasta ayer, o también es posible que el disco duro te esté dando un aviso de algo malo o que la partición está con poco espacio... en cualquier caso vigila los registros por si vieras alguna cosa extraña. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2015.06.11.16.26...@gmail.com
Kernel panic and shutdown
I have an i7-3612Qe system that has been giving kernel panics when running a
custom video streaming application pretty consistently after a couple minutes.
After the kernel panic, the machine reboots. When I turn off turbo mode in the
BIOS, the panics happen less frequently. Other BIOS settings are all default,
no overclocking or anything fancy.
-Can be reproduced by running streaming application using ~250% CPU, temps are
a little high, they float around 68-71 degrees
-sysbench runs fine with 8 threads, throttles CPU up to ~800%, no kernel
panics, temps remain below 70 degrees
-MemTest did not report any errors
-Intel Processor Diagnotic tool passed
-Tried swapping RAM
-Reproducible on multiple machines, not just a single processor (possibly
eliminates it being a bad single proc)
-Able to mitigate most of the kernel panics and reboots by disabling Turbo mode
(this is unacceptable, just including this for debugging purposes)
-Also able to mitigate kernel panics and reboots by changing the cpu frequency
sacling_governor to conservative, from ondemand. Conservative should
gracefully increase and decreases the CPU speed rather than jumping to max
speed the moment there is any load on the CPU
(https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt)
Here is what I could copy down from the kernel panic on the monitor, sometimes
the messages vary slightly, bu the TSC and PROCESSOR messages are almost always
the same.
[Hardware Error]: TSC 6e496d96062
[Hardware Error]: PROCESSOR 0:306a9 TIME 1418929330 SOCKET 0 APIC 3 microcode
12
[Hardware Error]: Run the above through 'mcelog --ascii'
[Hardware Error]: CPU 0: Machine Check Exception: 5 Bank 4: b2100402
[Hardware Error]: RIP !INEXACT! 10:811ee04c {intel_idle+0xb9/0x119}
[Hardware Error]: TSC 148c99828a0
[Hardware Error]: PROCESSOR 0:306a9 TIME 1418929330 SOCKET 0 APIC 3 microcode
12
[Hardware Error]: Run the above through 'mcelog --ascii'
[Hardware Error]: Some CPUs didn't answer in synchronization
[Hardware Error]: Machine check: Processor context corrupt
Kernel panic - not synching: Fatal machine check on current CPU
Pid: 0, comm: swapper/3 Tained: P M 0 3.2.0-4-amd64 #1 Debian 3.2.51-1
Call Trace: ...
Also, here is a post from superuser on some suggestions that I tried: cpu -
Kernel Panic from overheating? - Super
Userhttp://superuser.com/questions/854199/kernel-panic-from-overheating?noredirect=1#comment1130272_854199
Here is my discussion on intel where someone recommended I post to the debian
list https://communities.intel.com/thread/58372?sr=stream
I am looking to actually debug and fix this, but not finding a lot out there.
Any ideas for what to try next?
Kernel panic
Bonjour, Sur un portable, j'ai un kernel panic: kernel panic - not syncing: No init found. try passing init= option to kernel J'arrive a me logger en passant par mon CD rescue. J'ai essayé de faire un update-initramfs, mais rien n'y fait. :-( Je ne sais pas trop quoi faire, et j'hésite à reprendre l'installation à 0 Si vous aviez une petite idée de comment me sortir de l'impasse... Merci d'avance -- Le travail est l'opium du peuple et je ne veux pas mourir drogué. -+- Boris Vian -+- -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/d87b1e42258504d7cd26d519c350027c.squirrel@bureau
Re: Kernel panic
Hello, il me semble que update-initramfs ne modifie pas le grub. As-tu essayé 'grub-update' ? Il régénère le fichier grub.cfg . Sinon une autre solution est d'éditer l'entrée du grub manuellement avant de boot en appuyant sur 'E' dans le menu au démarrage , puis essayes de modifier la ligne 'initrd' en ajoutant un bon path de type '/boot/initrd.img...' Une fois booté, faire un 'grub-update'. Bon courage! Le 30/11/2014 11:19, Zuthos Oddy a écrit : Bonjour, Sur un portable, j'ai un kernel panic: kernel panic - not syncing: No init found. try passing init= option to kernel J'arrive a me logger en passant par mon CD rescue. J'ai essayé de faire un update-initramfs, mais rien n'y fait. :-( Je ne sais pas trop quoi faire, et j'hésite à reprendre l'installation à 0 Si vous aviez une petite idée de comment me sortir de l'impasse... Merci d'avance -- RHATAY Sami IUT Vannes - INFO2 ––– .--. / |o_o | |:_/ | // \ \ (| | ) /'\_ _/`\ \___)=(___/ signature.asc Description: OpenPGP digital signature
Re: Kernel panic
bonsoir, quels sont les arguments de boot du noyau que tu as utilisé ? (en appuyant sur 'e' dans le menu grub) Le 30 nov. 2014 11:19, Zuthos Oddy zut...@laposte.net a écrit : Bonjour, Sur un portable, j'ai un kernel panic: kernel panic - not syncing: No init found. try passing init= option to kernel J'arrive a me logger en passant par mon CD rescue. J'ai essayé de faire un update-initramfs, mais rien n'y fait. :-( Je ne sais pas trop quoi faire, et j'hésite à reprendre l'installation à 0 Si vous aviez une petite idée de comment me sortir de l'impasse... Merci d'avance -- Le travail est l'opium du peuple et je ne veux pas mourir drogué. -+- Boris Vian -+- -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/d87b1e42258504d7cd26d519c350027c.squirrel@bureau
Re: Extraños kernel panic en Debian Jessie
yo tengo el mismo problema. con el kernel 3.2.0-4 (32 bits) o inferior se resuelve tu problema, por cierto este fallo creo que tiene relación con el chip gráfico nVidia, ahun no descubro (en mis ratos libres ) el por que de la falla, con el driver privativo y el libre (nouveau) es el mismo problema la ultima investigación q le di a Xorg fue que el grafico dejo de responder si, kieres evitar bajar el kernel, puedes usar Opera (explota cada 10 minutos) epiphany-browser saludos jose maldonado -- ** software libre no significa gratis: richard m. stallman http://wiki.debian.org/es/NormasLista#resumen http://wiki.debian.org/es/NormasLista/Gmail http://es.wikipedia.org/wiki/Top-posting -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/530c36ba.5060...@gmail.com
Re: Extraños kernel panic en Debian Jessie
El Tue, 11 Feb 2014 23:32:51 -0430, José Maldonado escribió: El día 11 de febrero de 2014, 14:07, Camaleón noela...@gmail.com escribió: (...) Bueno hace unos dias compre una maquina sencilla para volver a andar con Debian a nivel personal, una AMD Sempron 140 + ECS Nvidia 6100 - M2 a la que le instale Debian Testing como tengo costumbre de hacer hace mucho tiempo, el problema es que cada vez que ejecutaba Iceweasel el sistema se congelaba de tal manera que ni las Magic Keys funcionaba, un kernel panic en toda regla. (...) ¿Quien de ustedes ha pasado por esto? ¿Alguna sugerencia? Que otras distribuciones funcionen sin problemas parece descartar un error de hardware ¿no? :-? Lo primero que probaría sería con otro kernel (superior o inferior al que tienes), posiblemente Debian wheezy (estable, versión LiveCD) o compilando el último kernel estable desde las fuentes. Otra cosa que probaría sería descartar el servidor X, intentando acceder desde ssh al equipo cuando se queda congelado, a ver si es posible. Justo ahora estoy probando Debian Wheezy en AMD64 y va bien sin problemas incluso con el Iceweasel 24 que esta en Wheezy-updates, lo del kernel en Jessie lo probe, incluso probe actualizando las X directamente desde SID. En el caso del kernel probe las versiones de SID 3.12 y Experimental 3.13-trunk pero seguía pasando el mismo problema, al menos con Iceweasel 24 y 27. El kernel que incluye testing/sid/experimental son muy parecidos por lo que en el caso de probar alguno distinto te recomendaría, como te dije antes, el de Wheezy (que es lo que estás probando ahora) o descargar las fuentes desde kernel.org y compilarlo a mano. En cuanto a probar desde un ssh para ver si X funciona, no se si eso resulte ya que las X se congelan por completo, incluso el monitor solo muestra gráficos deformados y no reacciona para nada. Pues para eso sirve, precisamente ;-) Si las X están muertas, podrás conectarte sin problemas mediante una sesión ssh. Si el sistema rechaza la conexión ssh es que el kernel está ko. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2014.02.12.14.41...@gmail.com
Extraños kernel panic en Debian Jessie
Hola a todos los que estan en la lista, Bueno hace unos dias compre una maquina sencilla para volver a andar con Debian a nivel personal, una AMD Sempron 140 + ECS Nvidia 6100 - M2 a la que le instale Debian Testing como tengo costumbre de hacer hace mucho tiempo, el problema es que cada vez que ejecutaba Iceweasel el sistema se congelaba de tal manera que ni las Magic Keys funcionaba, un kernel panic en toda regla. El problema en principio parecia ser Iceweasel, que tiene ya varios bugs reportados con el mismo comportamiento de simplemente congelar la maquina completamente y estaban relacionados con la verison 17 cuando estaba en testing, 24esr y 27 ahora en experimental. Pero sorpresa mia comenzo a pasar hasta con las cosas mas sencillas como abrir Thunar, rxvt, hasta el ncmpcpp. Busque en los logs de kern.log, syslog, dmesg, bootlog, y nada. Hice pruebas de memtest y la memoria bien, demas esta decir que la tarjeta es nueva y que ademas la inombrable, Sabayon y Canaima funcionan sin problemas. ¿Quien de ustedes ha pasado por esto? ¿Alguna sugerencia? Desde ya gracias por sus respuestas. -- Dios en su Cielo, todo bien en la Tierra *** -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGGkdu=oq5832OgUghuQJpsUaK6j1Dib=i_3pxz+4osetfg...@mail.gmail.com
Re: Extraños kernel panic en Debian Jessie
El Tue, 11 Feb 2014 11:51:06 -0400, José Maldonado escribió: Hola a todos los que estan en la lista, Bueno hace unos dias compre una maquina sencilla para volver a andar con Debian a nivel personal, una AMD Sempron 140 + ECS Nvidia 6100 - M2 a la que le instale Debian Testing como tengo costumbre de hacer hace mucho tiempo, el problema es que cada vez que ejecutaba Iceweasel el sistema se congelaba de tal manera que ni las Magic Keys funcionaba, un kernel panic en toda regla. (...) ¿Quien de ustedes ha pasado por esto? ¿Alguna sugerencia? Que otras distribuciones funcionen sin problemas parece descartar un error de hardware ¿no? :-? Lo primero que probaría sería con otro kernel (superior o inferior al que tienes), posiblemente Debian wheezy (estable, versión LiveCD) o compilando el último kernel estable desde las fuentes. Otra cosa que probaría sería descartar el servidor X, intentando acceder desde ssh al equipo cuando se queda congelado, a ver si es posible. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2014.02.11.18.37...@gmail.com
Re: Extraños kernel panic en Debian Jessie
El día 11 de febrero de 2014, 14:07, Camaleón noela...@gmail.com escribió: El Tue, 11 Feb 2014 11:51:06 -0400, José Maldonado escribió: Hola a todos los que estan en la lista, Bueno hace unos dias compre una maquina sencilla para volver a andar con Debian a nivel personal, una AMD Sempron 140 + ECS Nvidia 6100 - M2 a la que le instale Debian Testing como tengo costumbre de hacer hace mucho tiempo, el problema es que cada vez que ejecutaba Iceweasel el sistema se congelaba de tal manera que ni las Magic Keys funcionaba, un kernel panic en toda regla. (...) ¿Quien de ustedes ha pasado por esto? ¿Alguna sugerencia? Que otras distribuciones funcionen sin problemas parece descartar un error de hardware ¿no? :-? Lo primero que probaría sería con otro kernel (superior o inferior al que tienes), posiblemente Debian wheezy (estable, versión LiveCD) o compilando el último kernel estable desde las fuentes. Otra cosa que probaría sería descartar el servidor X, intentando acceder desde ssh al equipo cuando se queda congelado, a ver si es posible. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2014.02.11.18.37...@gmail.com Justo ahora estoy probando Debian Wheezy en AMD64 y va bien sin problemas incluso con el Iceweasel 24 que esta en Wheezy-updates, lo del kernel en Jessie lo probe, incluso probe actualizando las X directamente desde SID. En el caso del kernel probe las versiones de SID 3.12 y Experimental 3.13-trunk pero seguía pasando el mismo problema, al menos con Iceweasel 24 y 27. En cuanto a probar desde un ssh para ver si X funciona, no se si eso resulte ya que las X se congelan por completo, incluso el monitor solo muestra gráficos deformados y no reacciona para nada. -- Dios en su Cielo, todo bien en la Tierra *** -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGGkdumxpqqRjwwt_FR70L9-i+TTP5Kct1-4uCrrp+sFpm=w...@mail.gmail.com
Kernel panic - 2.6.32, tcp_keepalive_timer
Good day! I am getting kernel panic with the kernel version 2.6.32 - call trace is available here: http://i.imgur.com/kHfhRy9.jpg Is there any ideas how to deal with this? Thank you! -- Vladimir Zagaychuk (VZ485-RIPE)
Re: Kernel panic - 2.6.32, tcp_keepalive_timer
Hi On Wed, Nov 06, 2013 at 12:39:42PM +0200, Vladimir Zagaychuk wrote: Good day! I am getting kernel panic with the kernel version 2.6.32 - call trace is available here: http://i.imgur.com/kHfhRy9.jpg Is there any ideas how to deal with this? Thank you! Not really - to make sense of it, the whole trace would be needed (probably about 50-100 lines or so), rather than just the last 24 lines... If the kernel panic made it to disk, have a look in /var/log/kern.log.. Hope this helps -- Karl E. Jorgensen -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131106122853.GA5700@hawking
Re: Cambio de memorias y Kernel panic [SOLUCIONADO]
El Sun, 04 Aug 2013 10:30:14 -0300, Debian GMail escribió: (...) Lecciones aprendidas: 1 - Intel es poco claro al momento de especificar la aparatología (hardware) compatible. Supongo que cuando dices Intel te refieres al fabricante de la placa base, que en tu caso (y si mal no recuerdo) era también Intel. La tabla de compatibilidad de memorias hay que buscarla ex-professo, es decir, no es un apartado en el que el fabricante de la placa base suele hacer hincapié pero conviene revisar esa tabla y comprar módulos que haya sido probados y certificados... menos problemas. 2 - Antes de comprar memorias, fijarse en la página del fabricante si están probadas con las placas donde uno piensa instalarlas. Completamente de acuerdo. Yo antes (años 2000-2005) no lo hacía y tampoco creo que hiciera falta más allá de mirar el tipo de RAM compatible (PC-100, 133 y máximo permitido por módulo), al menos no tuve ningún problema con eso... hasta que empecé a instalar placas base de Supermicro y me enteré de lo que se puede complicar una simple elección de módulos de memoria :-P 3 - Que una máquina de 64 bits funcione con un sistema operativo de 32, no quiere decir que funcione con uno de 64, pues puede tener ensamblados componentes externos de la placa que al ser exigidos no respondan. Correcto. Hay dispositivos externos (impresoras, escáneres...) que obviamente no disponen de drivers para sistemas de 64 bits y por lo tanto no funcionan salvo que uses los de 32 bits, esto pasa en windows, en linux y en todos los sistemas operativos. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2013.08.05.13.56...@gmail.com
Re: Cambio de memorias y Kernel panic [SOLUCIONADO]
El 19/06/13 10:32, Camaleón escribió: El Tue, 18 Jun 2013 17:24:37 -0300, Javier ArgentinaBBAR escribió: Estimados: Ya busqué por todas partes, y se me han quemado los papeles, por lo solicito vuestra ayuda. Me gasté unos pesos en un par de memorias de 4Gb para usar la capacidad dual channel de la placa, por lo que instalé 2 x 4 GB RAM http://www.ec.kingston.com/ecom/configurator_new/PartsInfo_ar.asp? root=latamLinkBack=http://www.kingston.com/LatAmktcpartno=KVR13N9S8/4 Para tu placa, Kingston recomienda KVR1333D3N9HK2/8G. Parece una tontería pero más de una placa base moderna (de hace 4 años) me ha dado problemas al pincharle memoria elegida al azar como se hacía antaño, atendiendo únicamente a las características técnicas. Resultado: arranco el sistema, carga GRUB, y luego me pasa a una pantalla con el siguiente mensaje: Panic: early exception 08 rip 202:10 error 811b2418 cr2 88022840 (...) Bien. La solución ha sido fácil. Como Camaleón dijo, utilizo a partir de hoy dos bancos de memorias Kingston KVR1333D3N9H/4G. Es el tiempo que me costó poderlas encontrar por los serios problemas de importaciones, y el inmenso favor que me hizo una empresa que accedió a vendérmelas de un lote que ellos tienen guardado para atender las máquinas que tienen consignadas a sus clientes, a pesar que no venden insumos ni repuestos. GNU/Linux tuvo mucho que ver en la solución, pues fue en base a algunos contactos del ambiente linuxero que pude dar con las memorias. Gracias al NacPop de Willy Brown, me siento como si viviera en un very grosso paraíso. Lástima que acá hace frío. Lecciones aprendidas: 1 - Intel es poco claro al momento de especificar la aparatología (hardware) compatible. 2 - Antes de comprar memorias, fijarse en la página del fabricante si están probadas con las placas donde uno piensa instalarlas. 3 - Que una máquina de 64 bits funcione con un sistema operativo de 32, no quiere decir que funcione con uno de 64, pues puede tener ensamblados componentes externos de la placa que al ser exigidos no respondan. Gracias a todos. JAP -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51fe5766.2010...@gmail.com
Re: Cambio de memorias y Kernel panic [SOLUCIONADO]
El 04/08/13 15:30, Debian GMail escribió: Bien. La solución ha sido fácil. Como Camaleón dijo, utilizo a partir de hoy dos bancos de memorias Kingston KVR1333D3N9H/4G. Es el tiempo que me costó poderlas encontrar por los serios problemas de importaciones, y el inmenso favor que me hizo una empresa que accedió a vendérmelas de un lote que ellos tienen guardado para atender las máquinas que tienen consignadas a sus clientes, a pesar que no venden insumos ni repuestos. GNU/Linux tuvo mucho que ver en la solución, pues fue en base a algunos contactos del ambiente linuxero que pude dar con las memorias. Gracias al NacPop de Willy Brown, me siento como si viviera en un very grosso paraíso. Lástima que acá hace frío. Lecciones aprendidas: 1 - Intel es poco claro al momento de especificar la aparatología (hardware) compatible. 2 - Antes de comprar memorias, fijarse en la página del fabricante si están probadas con las placas donde uno piensa instalarlas. 3 - Que una máquina de 64 bits funcione con un sistema operativo de 32, no quiere decir que funcione con uno de 64, pues puede tener ensamblados componentes externos de la placa que al ser exigidos no respondan. Gracias a todos. JAP Me alegro que se haya solucionado :) Mi portátil venía con un módulo de 4 GB de marca Micron (no recuerdo el modelo exacto), y quise ampliarlo a 8 GB. Como no tenía idea, y por aquél entonces sólo usaba Windows, miré con el programa Everest a ver que careacteristicas me daba de la RAM. En base a esa información, y teniendo claro que quería memoria Kingston (por ser la más recomendada en relación calidad/precio), compré dos módulos de esta, un poco a ciegas y a corazonada, en base a las características de la Micron que tenía: http://www.valueram.com/datasheets/KVR1333D3S9_4G.pdf Y acerté. Perfecta, tanto en Windows como en Debian :) -- www.LinuxCounter.net Registered user #558467 has 1 linux machines Registered Linux machine #2003003 -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ktlrih$sf9$1...@ger.gmane.org
Re: Cambio de memorias y Kernel panic.
El día martes, 18 de junio de 2013, a las 17:24:37, Javier escribió: JA Tengo una máquina con las siguiente características: JA Desktop Board Intel® DH55PJ Intel® Core™ i3-540 Processor 1 x 2 GB RAM JA Linux jap 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux JA Me gasté unos pesos en un par de memorias de 4Gb para usar la JA capacidad dual channel de la placa, por lo que instalé JA 2 x 4 GB RAM. Resultado: arranco el sistema, carga GRUB, y luego me pasa a una JA pantalla con el siguiente mensaje: Panic: early exception 08 rip 202:10 error Hay veces que las memorias dan problemas... y muchas veces más cuando se trabaja a 64 bits. Si las memorias NO están apareadas también puede haber problemas... Para usar dual Channel los fabricantes de memoria aconsejan que las memorias sean además de iguales también de la misma partida. Muchas veces me ha ocurrido a mi y en máquinas de clientes... se soluciona cambiando las memorias. Tambien hay que considerar la velocidad de memoria y la compatibilidad con la Motherboard NOTA: En sistemas de 32 bits no hay tato problema. -- Saludos, GamlaUppsala mailto:gamlaupps...@yahoo.com.ar -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/243082106.20130620215...@yahoo.com.ar
Re: Cambio de memorias y Kernel panic.
Repito: no anda con el núcleo de 64 bits de Linux. Me queda hacer una prueba con un núcleo x86 para ver si hay variación, pero eso implica bajar el live-cd que aún no he tenido tiempo. Pues no te va a quedar más remedio que probar vía x86, a ver... no lo creo, hay otra solucion. si es un BUG del kernel posiblemente ya lo solucionaron en los siguinetes versiones , (despues del tuyo 3.2.0-4) varios amigos han instalado el 3.9 y anda muy bien , te lo recomiendo ;-) -- ** software libre no significa gratis: richard m. stallman http://wiki.debian.org/es/NormasLista#resumen http://wiki.debian.org/es/NormasLista/Gmail http://es.wikipedia.org/wiki/Top-posting -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c3e90b.8080...@gmail.com
Re: Cambio de memorias y Kernel panic.
El Tue, 18 Jun 2013 17:24:37 -0300, Javier ArgentinaBBAR escribió: Estimados: Ya busqué por todas partes, y se me han quemado los papeles, por lo solicito vuestra ayuda. (...) Me gasté unos pesos en un par de memorias de 4Gb para usar la capacidad dual channel de la placa, por lo que instalé 2 x 4 GB RAM http://www.ec.kingston.com/ecom/configurator_new/PartsInfo_ar.asp? root=latamLinkBack=http://www.kingston.com/LatAmktcpartno=KVR13N9S8/4 Para tu placa, Kingston recomienda KVR1333D3N9HK2/8G. Parece una tontería pero más de una placa base moderna (de hace 4 años) me ha dado problemas al pincharle memoria elegida al azar como se hacía antaño, atendiendo únicamente a las características técnicas. Resultado: arranco el sistema, carga GRUB, y luego me pasa a una pantalla con el siguiente mensaje: Panic: early exception 08 rip 202:10 error 811b2418 cr2 88022840 Ese mensaje debe venir del kernel. ¿Has probado con alguna versión LiveCD que monte un kernel distinto? Buscado este error en san Google, existen no más de 5 reportes, uno de ellos en ruso (gracias Google translator), y básicamente, lo que infiero de lo que encontré, es que los núcleos de 64 bits de Linux no funcionan en placas Intel con más de 4GB. ¿Cómo es eso posible? Encontré algunos errores parecidos (varía el 202:10 por algún 202:xx), y todos atribuyen a ciertos problemas de BIOS o incompatibilidades del núcleo de 64 bits de Linux con las placas Intel. Actualicé el BIOS a la última versión, pero el problema subsiste. Contacta con Intel (soporte técnico en inglés), como mucho vas a perder unos minutos de tu tiempo y quizá te den alguna pista. También falla con sólo insertar una sola memoria de 4 GB, aunque aquí el mensaje de error es infernalmente largo. Cualquiera de las dos memorias en cualquiera de los dos bancos. Las memorias fueron probadas y están bien. Al parecer, sólo se puede manejar hasta 3GB de memoria (hay gente de +buntu que lo menciona). Con 4 o más, falla. Hum... entonces entiendo que el kernel i486 no te dará problemas. Por curiosidad, ¿has probado con el kernel PAE? La bronca más grande: con Win7 32bit, funciona sin problemas, por lo que infiero que no es problema de los fierros (hardware). Hombre, ese error es muy gordo, si es un error de hardware se debería resolver con una actualización de la BIOS pero me da la nariz que el problema será combinado (kernel+placa base). Y aquí va mi pregunta: ¿Alguno tuvo un problema similar? Se agradece cualquier ayuda. En alguna ocasión el kernel me ha jugado una mala pasada nada más instalar un sistema pero nada que no se pudiera solucionar pasándole algún parámetro al iniciar el equipo. Sólo hay que saber cuál, exactamente ;-) Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2013.06.19.13.32...@gmail.com
Re: Cambio de memorias y Kernel panic.
El 19/06/13 10:32, Camaleón escribió: Me gasté unos pesos en un par de memorias de 4Gb para usar la capacidad dual channel de la placa, por lo que instalé 2 x 4 GB RAM http://www.ec.kingston.com/ecom/configurator_new/PartsInfo_ar.asp? root=latamLinkBack=http://www.kingston.com/LatAmktcpartno=KVR13N9S8/4 Para tu placa, Kingston recomienda KVR1333D3N9HK2/8G. Parece una tontería pero más de una placa base moderna (de hace 4 años) me ha dado problemas al pincharle memoria elegida al azar como se hacía antaño, atendiendo únicamente a las características técnicas. No sabía del buscador de compatibilidad de Kingston, que me ha devuelta la siguiente consulta: Resultados de la Búsqueda por: Intel DH55PJ Motherboard KVR1333D3S8N9H/2G 2GB 1333MHz DDR3 Non-ECC CL9 DIMM Single Rank STD Height 30mm KVR1333D3N9H/4G 4GB 1333MHz DDR3 Non-ECC CL9 DIMM STD Height 30mm KVR1333D3S8N9HK2/4G 4GB 1333MHz DDR3 Non-ECC CL9 DIMM SR (Kit of 2) STD Height 30mm KVR1333D3N9HK2/8G 8GB 1333MHz DDR3 Non-ECC CL9 DIMM (Kit of 2) STD Height 30mm Como se ve, ninguna es las que me vendieron KVR13N9S8/4 4GB 1333MHz DDR3 Non-ECC CL9 DIMM SR x8 La diferencia que alcanzo a ver es el x8 del final en la identificación. Tendré que ver qué significa. Mal por el manual de la placa madre de Intel, dado que las pedí con exactamente las especificaciones que indica. He mandado cambiar las memorias. La semana que viene actualizaré novedades. Muchas gracias. JAP -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c1c182.8090...@gmail.com
Re: Cambio de memorias y Kernel panic.
El Wed, 19 Jun 2013 11:34:42 -0300, Debian GMail escribió: El 19/06/13 10:32, Camaleón escribió: Me gasté unos pesos en un par de memorias de 4Gb para usar la capacidad dual channel de la placa, por lo que instalé 2 x 4 GB RAM http://www.ec.kingston.com/ecom/configurator_new/PartsInfo_ar.asp? root=latamLinkBack=http://www.kingston.com/LatAmktcpartno=KVR13N9S8/4 Para tu placa, Kingston recomienda KVR1333D3N9HK2/8G. Parece una tontería pero más de una placa base moderna (de hace 4 años) me ha dado problemas al pincharle memoria elegida al azar como se hacía antaño, atendiendo únicamente a las características técnicas. No sabía del buscador de compatibilidad de Kingston, que me ha devuelta la siguiente consulta: Sí, la verdad es que es muy práctico, la mayoría de las empresas fabricantes de memoria tiene uno (corsair, apacer...). Y en la página del fabricante de la placa base también debería aparecer un listado de, al menos, las memorias con las que se ha probado y verificado. Resultados de la Búsqueda por: Intel DH55PJ Motherboard (...) Como se ve, ninguna es las que me vendieron KVR13N9S8/4 4GB 1333MHz DDR3 Non-ECC CL9 DIMM SR x8 La diferencia que alcanzo a ver es el x8 del final en la identificación. Tendré que ver qué significa. Ese x8 debe ser la cantidad total de RAM cuando se compra un kit de 2 unidades. Mal por el manual de la placa madre de Intel, dado que las pedí con exactamente las especificaciones que indica. Bueno, tienes una tabla aquí: Tested memory Third-party tested memory http://www.intel.com/support/motherboards/desktop/dh55pj/sb/ CS-031469.htm#tested He mandado cambiar las memorias. La semana que viene actualizaré novedades. Muchas gracias. Aunque no creo que te ayude con el problema del kernel, hoy en día conviene usar la memoria recomendada para evitar problemas. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2013.06.19.14.55...@gmail.com
Cambio de memorias y Kernel panic.
Estimados: Ya busqué por todas partes, y se me han quemado los papeles, por lo solicito vuestra ayuda. Tengo una máquina con las siguiente características: Desktop Board Intel® DH55PJ http://www.intel.la/content/www/xl/es/motherboards/desktop-motherboards/desktop-board-dh55pj.html Intel® Core™ i3-540 Processor http://ark.intel.com/es/products/46473/Intel-Core-i3-540-Processor-4M-Cache-3_06-GHz 1 x 2 GB RAM http://www.ec.kingston.com/ecom/configurator_new/PartsInfo_ar.asp?root=latamLinkBack=http://www.kingston.com/LatAmktcpartno=KVR1333D3S8N9/2G $ uname -a Linux jap 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux Me gasté unos pesos en un par de memorias de 4Gb para usar la capacidad dual channel de la placa, por lo que instalé 2 x 4 GB RAM http://www.ec.kingston.com/ecom/configurator_new/PartsInfo_ar.asp?root=latamLinkBack=http://www.kingston.com/LatAmktcpartno=KVR13N9S8/4 Resultado: arranco el sistema, carga GRUB, y luego me pasa a una pantalla con el siguiente mensaje: Panic: early exception 08 rip 202:10 error 811b2418 cr2 88022840 Buscado este error en san Google, existen no más de 5 reportes, uno de ellos en ruso (gracias Google translator), y básicamente, lo que infiero de lo que encontré, es que los núcleos de 64 bits de Linux no funcionan en placas Intel con más de 4GB. Encontré algunos errores parecidos (varía el 202:10 por algún 202:xx), y todos atribuyen a ciertos problemas de BIOS o incompatibilidades del núcleo de 64 bits de Linux con las placas Intel. Actualicé el BIOS a la última versión, pero el problema subsiste. También falla con sólo insertar una sola memoria de 4 GB, aunque aquí el mensaje de error es infernalmente largo. Cualquiera de las dos memorias en cualquiera de los dos bancos. Las memorias fueron probadas y están bien. Al parecer, sólo se puede manejar hasta 3GB de memoria (hay gente de +buntu que lo menciona). Con 4 o más, falla. La bronca más grande: con Win7 32bit, funciona sin problemas, por lo que infiero que no es problema de los fierros (hardware). Y aquí va mi pregunta: ¿Alguno tuvo un problema similar? Se agradece cualquier ayuda. Muchas gracias a todos. JAP -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cag0od5chwngulp5_3hfej2jcwwfzhgyqdk426dq8vlm4s8_...@mail.gmail.com
Re: Cambio de memorias y Kernel panic.
On Tue, 18 Jun 2013 17:24:37 -0300 Javier ArgentinaBBAR javier.debian.bb...@gmail.com wrote: Le pasaste el memtest para empezar a descartar ? Saludos -- BSS Servicio :. $telnet bayresmail.com.ar 2323 MamaLibre Reader :. http://mamalibre.com.ar/reader/ Buscador del Sur :. http://buscar.mamalibre.com.ar/ Voip Mumble :. http://mumble.com.ar Web Hosting :. http://mamalibre.com.ar Red Social :. http://legadolibre.com.ar Jabber/XMPP :. http://mamalibre.com.ar/xmpp/ MamaLibre, Casa en Lincoln, Ituzaingo 1085 CP6070, Buenos Aires, Argentina pgpkW2nwkgtec.pgp Description: PGP signature
Re: Cambio de memorias y Kernel panic.
Hola Javier: El 18/06/13 17:24, Javier ArgentinaBBAR escribió: Estimados: Ya busqué por todas partes, y se me han quemado los papeles, por lo solicito vuestra ayuda. Tengo una máquina con las siguiente caracterÃsticas: Desktop Board Intel® DH55PJ http://www.intel.la/content/www/xl/es/motherboards/desktop-motherboards/desktop-board-dh55pj.html Intel® Coreâ„¢ i3-540 Processor http://ark.intel.com/es/products/46473/Intel-Core-i3-540-Processor-4M-Cache-3_06-GHz 1 x 2 GB RAM http://www.ec.kingston.com/ecom/configurator_new/PartsInfo_ar.asp?root=latamLinkBack=http://www.kingston.com/LatAmktcpartno=KVR1333D3S8N9/2G $ uname -a Linux jap 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux Me gasté unos pesos en un par de memorias de 4Gb para usar la capacidad dual channel de la placa, por lo que instalé 2 x 4 GB RAM http://www.ec.kingston.com/ecom/configurator_new/PartsInfo_ar.asp?root=latamLinkBack=http://www.kingston.com/LatAmktcpartno=KVR13N9S8/4 Resultado: arranco el sistema, carga GRUB, y luego me pasa a una pantalla con el siguiente mensaje: Panic: early exception 08 rip 202:10 error 811b2418 cr2 88022840 Buscado este error en san Google, existen no más de 5 reportes, uno de ellos en ruso (gracias Google translator), y básicamente, lo que infiero de lo que encontré, es que los núcleos de 64 bits de Linux no funcionan en placas Intel con más de 4GB. Encontré algunos errores parecidos (varÃa el 202:10 por algún 202:xx), y todos atribuyen a ciertos problemas de BIOS o incompatibilidades del núcleo de 64 bits de Linux con las placas Intel. Actualicé el BIOS a la última versión, pero el problema subsiste. También falla con sólo insertar una sola memoria de 4 GB, aunque aquà el mensaje de error es infernalmente largo. Cualquiera de las dos memorias en cualquiera de los dos bancos. Las memorias fueron probadas y están bien. Al parecer, sólo se puede manejar hasta 3GB de memoria (hay gente de +buntu que lo menciona). Con 4 o más, falla. La bronca más grande: con Win7 32bit, funciona sin problemas, por lo que infiero que no es problema de los fierros (hardware). Y aquà va mi pregunta: ¿Alguno tuvo un problema similar? Supongo que ya lo habrás visto, pero no tendrá que ver con la velocidad de las memorias ? Me ha pasado con algunas PM Intel de cambiarle la configuración auto en la velocidad de la memoria, colocarle la de la memoria (por ej. 1333) y que directamente no me booteen. Al volver a dejarle auto arrancaban sin problemas. Se agradece cualquier ayuda. Muchas gracias a todos. Saludos, JAP -- Walter O. Dari http://swcomputacion.com/ skype: waomda -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c0cb6c.3000...@gmail.com
Re: Cambio de memorias y Kernel panic.
El día 18 de junio de 2013 17:39, Fabián Bonetti mama21mama2...@yahoo.com.ar escribió: Le pasaste el memtest para empezar a descartar ? Saludos Las memorias fueron probadas y están bien. JAP -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAG0od5e-S=jrvumecx38+j9fakmpdow4+9fc0_b5kr8c9zs...@mail.gmail.com
Re: Cambio de memorias y Kernel panic.
El día 18 de junio de 2013 18:04, Walter O. Dari wlin...@gmail.com escribió: Hola Javier: Supongo que ya lo habrás visto, pero no tendrá que ver con la velocidad de las memorias ? Me ha pasado con algunas PM Intel de cambiarle la configuración auto en la velocidad de la memoria, colocarle la de la memoria (por ej. 1333) y que directamente no me booteen. Al volver a dejarle auto arrancaban sin problemas. Walter O. Dari La placa no tiene forma de cambiar la velocidad de las memorias, pues las reconoce automáticamente. Y las está reconociendo bien. Repito: no anda con el núcleo de 64 bits de Linux. Me queda hacer una prueba con un núcleo x86 para ver si hay variación, pero eso implica bajar el live-cd que aún no he tenido tiempo. JAP -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAG0od5dSDfDP2ye2wQfqW4koRHUiabOGOZ0igis=m+soxl-...@mail.gmail.com
Re: Cambio de memorias y Kernel panic.
El 18/06/13 23:17, Javier ArgentinaBBAR escribió: La placa no tiene forma de cambiar la velocidad de las memorias, pues las reconoce automáticamente. Y las está reconociendo bien. Repito: no anda con el núcleo de 64 bits de Linux. Me queda hacer una prueba con un núcleo x86 para ver si hay variación, pero eso implica bajar el live-cd que aún no he tenido tiempo. Pues no te va a quedar más remedio que probar vía x86, a ver... -- Saludos de Santiago José López Borrazás. signature.asc Description: OpenPGP digital signature
Re: Cambio de memorias y Kernel panic.
Recuerdo que hace 2 meses atrás instale debian en un equipo core 2 quad que trae 4 gb en memoria si no me equivoco unas DDR2 PC2-5300 y también medio un error de kernel panic, y la iso que habia bajado era una AMD64 al final recuerdo que baje la iso para x86 El 18 de junio de 2013 17:25, Santiago José López Borrazás sjlop...@gmail.com escribió: El 18/06/13 23:17, Javier ArgentinaBBAR escribió: La placa no tiene forma de cambiar la velocidad de las memorias, pues las reconoce automáticamente. Y las está reconociendo bien. Repito: no anda con el núcleo de 64 bits de Linux. Me queda hacer una prueba con un núcleo x86 para ver si hay variación, pero eso implica bajar el live-cd que aún no he tenido tiempo. Pues no te va a quedar más remedio que probar vía x86, a ver... -- Saludos de Santiago José López Borrazás. -- Roberto Quiñones Owner - Service Manager and System ACShell.NET – Internet Services robe...@acshell.net - www.acshell.net San Martin #311 Santiago – CL (Chile) +560981361713
Re: Diagnosing kernel panic involving fglrx
One change I made shortly before the problems started that might be relevant: I enabled i386 architecture support (it's amd64 laptop). On Tue, Jun 4, 2013 at 7:36 AM, Ari Epstein aepstein...@gmail.com wrote: Hi all, Got a new laptop and installed wheezy a few weeks ago. I noticed the HDMI audio was not working, and figured it was a limitation in the fglrx driver and it seemed otherwise to run well. Starting yesterday, however, I have frequent but not consistent kernel panics during the boot process that seem to involve support for that feature. Sometimes it boots without any audio (there is another integrated audio device), sometimes with, sometimes it does not boot at all. Never had to debug something like this before so some pointers about how to go about it are appreciated! dmesg logs attached for occassions that it booted with audio and without audio. -- Ari Epstein 311 W Buffalo St Ithaca, NY 14850-4123 aepstein...@gmail.com 607.222.5116
Re: BTRFS Kernel Panic
I was able to copy almost everything from dd images to a new set of filesystems. The only thing that was excluded from the transfer was /var/cache/apt, because something in there was causing the problem. I performed the transfer by booting to a second system. Interestingly, when this problem arose during the transfer, which was being run from this other system, the problem was not as serious. The program that triggered the problem died and a call stack was printed by the kernel, but apparently everything else continued to work. I don't know why the problem was less serious when it occurred on the transfer system, as the filesystem with a problem was not the / of any system, it was /var (and therefore no more important to the first system as it was to the system performing the transfer). In any case, all appears to be well; I can run both aptitude update and updatedb, and it hasn't crashed since. Thank you for your help. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/516b5c2b.10...@gmail.com
Re: BTRFS Kernel Panic
On Thursday 11 April 2013 23:23:30 Roger Leigh wrote: You could also try upgrading to a newer kernel e.g. 3.8.x. I've done this myself due to btrfs issues with older kernels; you might need to hand-build it though since Debian doesn't yet have it. See kernel-package. Debian has it in experimental: martin@merkaba:~ rmadison linux-image-3.8-trunk-amd64 linux-image-3.8-trunk-amd64 | 3.8.5-1~experimental.1 | experimental | amd64, i386 ;) I also recommend running current kernels with BTRFS. -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/29696065.TvIoNG5Q5r@merkaba
BTRFS Kernel Panic
So it looks like btrfs really is still experimental. I have / and /var on two separate btrfs partitions and I consistently get a kernel panic when I run aptitude update (see the end). I also managed to get the same results by using find and dd to read every file in /var. Although my oops output does have RIP: btrfs_num_copies, I do not think that I need to use btrfs-zero-log because (1) I am using a 3.2 series kernel, (2) my panic callstack does not have a function that begins with replay_one_, and (3) I am able to mount the partitions (and boot) just fine. It is only when some process such as aptitude or updatedb (indexing for the locate command) tries to read something in the filesystem. I tried scrubbing the filesystems, but no errors were found (and somehow no panics occured). Finally, I can't really see what's going on with an strace or anything because the panic happens before anything gets written to the disk (even if I do an emergency sync and remount-ro with sysrq before rebooting), and I *really* don't want to install netconsole because I am worried that any package management will cause a panic during an installation which could make my situation much worse. I have run out of ideas and am looking for suggestions. The panic from /var/log/kern.log: Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.632188] parent transid verify failed on 18446277369678266402 wanted 18446277756225214326 found 0 Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.632203] parent transid verify failed on 18446277369678266402 wanted 18446277756225214326 found 0 Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.632278] [ cut here ] Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.632331] kernel BUG at /build/buildd-linux_3.2.39-2-amd64-G5_nN0/linux-3.2.39/fs/btrfs/volumes.c:2860! Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.632412] invalid opcode: [#1] SMP Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.632458] CPU 0 Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.632478] Modules linked in: hidp cryptd aes_x86_64 aes_generic nbd ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables parport_pc ppdev lp parport rfcomm bnep cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_conservative pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc uinput fuse nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop dm_crypt sg uvcvideo videodev v4l2_compat_ioctl32 media btusb bluetooth crc16 joydev ata_generic acpi_cpufreq i915 mperf r592 dell_laptop ata_piix coretemp drm_kms_helper dcdbas drm i2c_algo_bit memstick snd_hda_codec_idt snd_hda_codec_hdmi pcspkr arc4 firewire_ohci firewire_core crc_itu_t iwl3945 iwl_legacy snd_hda_intel mac80211 snd_hda_codec sky2 snd_hwdep snd_pcm snd_page_alloc psmouse serio_raw cfg80211 rfkill r852 sm_common nand nand_ecc nand_ids mtd dell_wmi snd_seq snd_seq_device sparse_keymap snd_timer sdhci_pci sdhci snd iTCO_wdt iTCO_vendor_support wmi soundcore processor mm Apr 7 17:39:29 alexdell2-wheezy kernel: c_core i2c_i801 video battery ac i2c_core evdev power_supply button btrfs crc32c libcrc32c zlib_deflate dm_mod usb_storage usbhid hid sl811_hcd ohci_hcd sr_mod cdrom sd_mod crc_t10dif thermal ahci libahci libata thermal_sys uhci_hcd scsi_mod ehci_hcd usbcore usb_common Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.633954] Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.633972] Pid: 6448, comm: aptitude Tainted: G O 3.2.0-4-amd64 #1 Debian 3.2.39-2 Dell Inc. Inspiron 1525 /0WP007 Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634090] RIP: 0010:[a016d594] [a016d594] btrfs_num_copies+0x3f/0x89 [btrfs] Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634196] RSP: 0018:88004dd1d9b8 EFLAGS: 00010246 Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634244] RAX: RBX: fffe57890022 RCX: 0001 Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634304] RDX: RSI: fffe57890022 RDI: 880115079110 Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634363] RBP: 880115079110 R08: R09: Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634424] R10: 88007972a6d8 R11: 88007972a6d8 R12: Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634484] R13: R14: fffe57e2fffe5776 R15: 880116877820 Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634545] FS: 7f2b8c238760() GS:88011fc0() knlGS: Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634615] CS: 0010 DS: ES: CR0: 80050033 Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634664] CR2: 7f2b8a913f50 CR3: 4dd1a000 CR4: 06f0 Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634724] DR0: DR1: DR2: Apr 7 17:39:29 alexdell2-wheezy kernel: [ 7290.634784] DR3
Re: BTRFS Kernel Panic
On Thu, Apr 11, 2013 at 03:50:19PM -0500, Alex Robbins wrote: So it looks like btrfs really is still experimental. I have / and /var on two separate btrfs partitions and I consistently get a kernel panic when I run aptitude update (see the end). I also managed to get the same results by using find and dd to read every file in /var. Although my oops output does have RIP: btrfs_num_copies, I do not think that I need to use btrfs-zero-log because (1) I am using a 3.2 series kernel, (2) my panic callstack does not have a function that begins with replay_one_, and (3) I am able to mount the partitions (and boot) just fine. It is only when some process such as aptitude or updatedb (indexing for the locate command) tries to read something in the filesystem. I'd suggest that you firstly: 1) take a full image of the raw devices containing these filesystems with dd in case of further damage 2) try to backup the filesystems with tar If you get a backup, you could then reformat the partitions and restore the backups. I'd definitely recommend looking at the changelog for newer versions of the linux kernel to see if this has fixed. It also might be worth contacting the brtfs developers' mailing list to see if they have seen this issue before--the BUG alone might be useful. You could also try upgrading to a newer kernel e.g. 3.8.x. I've done this myself due to btrfs issues with older kernels; you might need to hand-build it though since Debian doesn't yet have it. See kernel-package. [I've previously lost a large raid-1 btrfs filesystem--both copies completely trashed after a SATA glitch, including the good copy which was corrupted entirely by btrfs... Currently using it on an SSH for testing purposes as my rootfs, but don't use it for user data, which is on ext4 on LVM RAID.] Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130411222330.ga23...@codelibre.net
Error en debian etch kernel panic - not syncing: No init found. Try passing init = option to kernel
Hola muy buenas, al arrancar un debian un pelín antiguo que tenemos un proxy http montado, me ha reportado el siguiente error... Según he leído, puede deberse a que el initrd esté dañado. Alguien ha tenido el mismo error?? Saludos y gracias de antemano. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/99f246844d11d1bb44bfb7f5fc6a5...@maykel.sytes.net
Re: Problemas com kernel panic. [Resolvido]
Boa tarde a todos, Em primeiro lugar gostaria de agradecer a todos, pois o problema foi resolvido de maneira adequada. Quanto ao problema : Depois que retirei as hds e instalei em outra maquina, consegui dar o boot normalmente (o que me espantou, pois já considerava um caso quase perdido), usei o systemrescue cd (muito bom por sinal) e fiz cópias dos discos e efetuei o backup necessário dos arquivos. Após uma olhada minuciosa no hardware, em especial na placa mãe, pude perceber uma leve ondulação em um dos capacitores (e nada mais que fosse perceptível). Troquei a placa e todos os demais componentes e estou configurando o samba novamente. Mais uma vez obrigado a todos. Atte, -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5058c42a.3050...@hutaubate.com.br
Re: Problemas com kernel panic. [Resolvido]
Congratulations =D Em 18 de setembro de 2012 14:57, Informática HUT c...@hutaubate.com.brescreveu: Boa tarde a todos, Em primeiro lugar gostaria de agradecer a todos, pois o problema foi resolvido de maneira adequada. Quanto ao problema : Depois que retirei as hds e instalei em outra maquina, consegui dar o boot normalmente (o que me espantou, pois já considerava um caso quase perdido), usei o systemrescue cd (muito bom por sinal) e fiz cópias dos discos e efetuei o backup necessário dos arquivos. Após uma olhada minuciosa no hardware, em especial na placa mãe, pude perceber uma leve ondulação em um dos capacitores (e nada mais que fosse perceptível). Troquei a placa e todos os demais componentes e estou configurando o samba novamente. Mais uma vez obrigado a todos. Atte, -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-**requ...@lists.debian.orgdebian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/**5058C42A.3050006@hutaubate.**com.brhttp://lists.debian.org/5058c42a.3050...@hutaubate.com.br
Re: Problemas com kernel panic. [Resolvido]
Bem lembrado, Boa parte dos kernel panic que eu presenciei tinha sido hardware, principalmente memórias... testar o hardware é uma das coisas a se fazer nessas ocasiões... [ ] 's -- | .''`. A fé não dá respostas. Só impede perguntas. | : :' : | `. `'` | `- Je vois tout -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CACnf0pg91Efq0igEx3aMFCXodg-Limy=ox5ea2-kuyyxus-...@mail.gmail.com
Problemas com kernel panic.
Bom dia a todos, Estou com uma situação complicada por aqui, no fim de semana minha máquina de backup apresentou a seguinte mensagem de erro: [0.220408] initramfs unpacking failed : junk in compressed archive [0.720799] kernel panic - not syncing : VFS : unable to mount root fs on unknown-block (254,4) Não consigo entrar no single-mode, na verdade a unica coisa que consigo é entrar no prompt do grub (teclando c ao escolher o kernel. Essa máquina é usada para backup de arquivos e , preciso muito dos dados... Tenho 2 hd's de 250GB em raid 0. Tentei ligar com somente uma hd e não inicia nada. Não consigo rodar nem live cd para tentar uma recuperação. Alguém poderia me ajudar? Desde já agradeço. -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50571afa.6000...@hutaubate.com.br
Re: Problemas com kernel panic.
Seg, 17.09.2012, Informática HUT disse: Bom dia a todos, Estou com uma situação complicada por aqui, no fim de semana minha máquina de backup apresentou a seguinte mensagem de erro: [0.220408] initramfs unpacking failed : junk in compressed archive Aparentemente o arquivo initramfs está corrompido (lixo no arquivo comprimido). Não sei como isso pode ter acontecido. [0.720799] kernel panic - not syncing : VFS : unable to mount root fs on unknown-block (254,4) Não consigo entrar no single-mode, na verdade a unica coisa que consigo é entrar no prompt do grub (teclando c ao escolher o kernel. pergunta-desencargo-de-consciência: tem algum outro kernel instalado? Essa máquina é usada para backup de arquivos e , preciso muito dos dados... Tenho 2 hd's de 250GB em raid 0. Tentei ligar com somente uma hd e não inicia nada. Não consigo rodar nem live cd para tentar uma recuperação. Com quais cds vc já tentou? Qual erro dá? Lembrando que para fazer chroot com lvm é meio chatinho... não lembro de cabeça, mas tem no oráculo. Alguém poderia me ajudar? Desde já agradeço. -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50571afa.6000...@hutaubate.com.br -- Cuando la guática pide comídica Pone al cristiánico firme y guerrérico Por sus poróticos y sus cebóllicas, No hay regimiéntico que los deténguica Si tienen hámbrica los populáricos. Violeta Parra Gunther Furtado Curitiba - Paraná - Brasil gunfurt...@gmail.com skype:gunfurtado -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120917100953.1dd8f...@shrknemo.gbmc.net
Re: Problemas com kernel panic.
Bom dia, A corrupção do arquivo, pode ter sido por falta de energia? O gerador foi desligado no fim de semana e, não avisaram ninguém.. Só possuo o kernel 2.6... instalado nada mais... Já tentei com o dvd do debian squeeze, ubuntu 10.04 e 12.04 (os que eu tenho em mãos). Por desencargo de consciência vou colocar as hds em outro maquina, pois pude perceber que, ao tentar instalar o debian em uma terceira hd para tentar fazer a recuperação, ele apresentou erro também, mesmo com as hds em raid desconectadas... Poderia ser algum erro da hardware, não relacionado as hds... talvez eu deva torcer por isso. atte, Em 17-09-2012 10:09, Gunther Furtado escreveu: Seg, 17.09.2012, Informática HUT disse: Bom dia a todos, Estou com uma situação complicada por aqui, no fim de semana minha máquina de backup apresentou a seguinte mensagem de erro: [0.220408] initramfs unpacking failed : junk in compressed archive Aparentemente o arquivo initramfs está corrompido (lixo no arquivo comprimido). Não sei como isso pode ter acontecido. [0.720799] kernel panic - not syncing : VFS : unable to mount root fs on unknown-block (254,4) Não consigo entrar no single-mode, na verdade a unica coisa que consigo é entrar no prompt do grub (teclando c ao escolher o kernel. pergunta-desencargo-de-consciência: tem algum outro kernel instalado? Essa máquina é usada para backup de arquivos e , preciso muito dos dados... Tenho 2 hd's de 250GB em raid 0. Tentei ligar com somente uma hd e não inicia nada. Não consigo rodar nem live cd para tentar uma recuperação. Com quais cds vc já tentou? Qual erro dá? Lembrando que para fazer chroot com lvm é meio chatinho... não lembro de cabeça, mas tem no oráculo. Alguém poderia me ajudar? Desde já agradeço. -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50571afa.6000...@hutaubate.com.br -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5057236d.8030...@hutaubate.com.br
Re: Problemas com kernel panic.
Abaixe o SysRescueCD, tenho usado ele para as mais diversas situações, no mínimo v. vai poder verificar o estado do sistema de arquivos. Para maior segurança, faça antes uma cópia física dos HDs com o DD (ou o Clonezilla, muito bom) e trabalhe com as cópias, preserve os HDs originais. Vinicius Em 17-09-2012 10:19, Informática HUT escreveu: Bom dia, A corrupção do arquivo, pode ter sido por falta de energia? O gerador foi desligado no fim de semana e, não avisaram ninguém.. Só possuo o kernel 2.6... instalado nada mais... Já tentei com o dvd do debian squeeze, ubuntu 10.04 e 12.04 (os que eu tenho em mãos). Por desencargo de consciência vou colocar as hds em outro maquina, pois pude perceber que, ao tentar instalar o debian em uma terceira hd para tentar fazer a recuperação, ele apresentou erro também, mesmo com as hds em raid desconectadas... Poderia ser algum erro da hardware, não relacionado as hds... talvez eu deva torcer por isso. atte, Em 17-09-2012 10:09, Gunther Furtado escreveu: Seg, 17.09.2012, Informática HUT disse: Bom dia a todos, Estou com uma situação complicada por aqui, no fim de semana minha máquina de backup apresentou a seguinte mensagem de erro: [0.220408] initramfs unpacking failed : junk in compressed archive Aparentemente o arquivo initramfs está corrompido (lixo no arquivo comprimido). Não sei como isso pode ter acontecido. [0.720799] kernel panic - not syncing : VFS : unable to mount root fs on unknown-block (254,4) Não consigo entrar no single-mode, na verdade a unica coisa que consigo é entrar no prompt do grub (teclando c ao escolher o kernel. pergunta-desencargo-de-consciência: tem algum outro kernel instalado? Essa máquina é usada para backup de arquivos e , preciso muito dos dados... Tenho 2 hd's de 250GB em raid 0. Tentei ligar com somente uma hd e não inicia nada. Não consigo rodar nem live cd para tentar uma recuperação. Com quais cds vc já tentou? Qual erro dá? Lembrando que para fazer chroot com lvm é meio chatinho... não lembro de cabeça, mas tem no oráculo. Alguém poderia me ajudar? Desde já agradeço. -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50571afa.6000...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5057330a.6090...@uol.com.br
Re: Problemas com kernel panic.
Seg, 17.09.2012, Informática HUT disse: Bom dia, A corrupção do arquivo, pode ter sido por falta de energia? O gerador foi desligado no fim de semana e, não avisaram ninguém.. não sei, mas a coincidência já é um indício. Só possuo o kernel 2.6... instalado nada mais... Já tentei com o dvd do debian squeeze, ubuntu 10.04 e 12.04 (os que eu tenho em mãos). que erros aparecem, o que impede a máquina de bootar por estes CDs/DVDs? Por desencargo de consciência vou colocar as hds em outro maquina, pois pude perceber que, ao tentar instalar o debian em uma terceira hd para tentar fazer a recuperação, ele apresentou erro também, mesmo com as hds em raid desconectadas... Poderia ser algum erro da hardware, não relacionado as hds... talvez eu deva torcer por isso. A ideia do Vinícius (fazer copia dos CDs e preservar os originais) é bem sensata. att., atte, Em 17-09-2012 10:09, Gunther Furtado escreveu: Seg, 17.09.2012, Informática HUT disse: Bom dia a todos, Estou com uma situação complicada por aqui, no fim de semana minha máquina de backup apresentou a seguinte mensagem de erro: [0.220408] initramfs unpacking failed : junk in compressed archive Aparentemente o arquivo initramfs está corrompido (lixo no arquivo comprimido). Não sei como isso pode ter acontecido. [0.720799] kernel panic - not syncing : VFS : unable to mount root fs on unknown-block (254,4) Não consigo entrar no single-mode, na verdade a unica coisa que consigo é entrar no prompt do grub (teclando c ao escolher o kernel. pergunta-desencargo-de-consciência: tem algum outro kernel instalado? Essa máquina é usada para backup de arquivos e , preciso muito dos dados... Tenho 2 hd's de 250GB em raid 0. Tentei ligar com somente uma hd e não inicia nada. Não consigo rodar nem live cd para tentar uma recuperação. Com quais cds vc já tentou? Qual erro dá? Lembrando que para fazer chroot com lvm é meio chatinho... não lembro de cabeça, mas tem no oráculo. Alguém poderia me ajudar? Desde já agradeço. -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50571afa.6000...@hutaubate.com.br -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5057236d.8030...@hutaubate.com.br -- Cuando la guática pide comídica Pone al cristiánico firme y guerrérico Por sus poróticos y sus cebóllicas, No hay regimiéntico que los deténguica Si tienen hámbrica los populáricos. Violeta Parra Gunther Furtado Curitiba - Paraná - Brasil gunfurt...@gmail.com skype:gunfurtado -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120917121838.5a56b...@shrknemo.gbmc.net
Re: Problemas com kernel panic.
Tente iniciar a máquina com o cd de instalação do Debian, depois escolha a opção de recuperação. Nela depois que passarem os menus para escolher teclado, rede, etc, escolhar ir para o shel do computador, veja se as partições estão desmontadas e passe um fsck -y nelas, após isso monte o /usr e o /var, depois instale um outro kernel com o apt-get. On Mon, 2012-09-17 at 10:19 -0300, Informática HUT wrote: Bom dia, A corrupção do arquivo, pode ter sido por falta de energia? O gerador foi desligado no fim de semana e, não avisaram ninguém.. Só possuo o kernel 2.6... instalado nada mais... Já tentei com o dvd do debian squeeze, ubuntu 10.04 e 12.04 (os que eu tenho em mãos). Por desencargo de consciência vou colocar as hds em outro maquina, pois pude perceber que, ao tentar instalar o debian em uma terceira hd para tentar fazer a recuperação, ele apresentou erro também, mesmo com as hds em raid desconectadas... Poderia ser algum erro da hardware, não relacionado as hds... talvez eu deva torcer por isso. atte, Em 17-09-2012 10:09, Gunther Furtado escreveu: Seg, 17.09.2012, Informática HUT disse: Bom dia a todos, Estou com uma situação complicada por aqui, no fim de semana minha máquina de backup apresentou a seguinte mensagem de erro: [0.220408] initramfs unpacking failed : junk in compressed archive Aparentemente o arquivo initramfs está corrompido (lixo no arquivo comprimido). Não sei como isso pode ter acontecido. [0.720799] kernel panic - not syncing : VFS : unable to mount root fs on unknown-block (254,4) Não consigo entrar no single-mode, na verdade a unica coisa que consigo é entrar no prompt do grub (teclando c ao escolher o kernel. pergunta-desencargo-de-consciência: tem algum outro kernel instalado? Essa máquina é usada para backup de arquivos e , preciso muito dos dados... Tenho 2 hd's de 250GB em raid 0. Tentei ligar com somente uma hd e não inicia nada. Não consigo rodar nem live cd para tentar uma recuperação. Com quais cds vc já tentou? Qual erro dá? Lembrando que para fazer chroot com lvm é meio chatinho... não lembro de cabeça, mas tem no oráculo. Alguém poderia me ajudar? Desde já agradeço. -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50571afa.6000...@hutaubate.com.br -- Leandro M. Pereira Informática HUT (12) 3625-7605 | c...@hutaubate.com.br -- Adiel de Lima Ribeiro facebook.com/sembr.dyndns.info
Kernel panic une fois sur deux
Bonjour à tous, J'ai mis sur mon PC les répertoires /boot et /usr sur un disque SSD, les autres répertoires sur un disque dur SATA. Une fois sur deux, au boot, j'ai droit à un Kernel panic. J'éteins le PC, le relance et 3 à 4 fois à nouveau un Kernel panic. Puis enfin, au prochain reboot, tout marche bien, le système ne montrant plus aucune vélléité. Le PC boote du premier coup environ 1 fois sur 2. Je me demande si il ne s'agit pas d'une lenteur du disque SSD qui se met en marche après le disque dur SATA sinon, une défaillance du disque SSD. Mon OS est Debian-Squeeze, 32 bits, avec noyau bigmem. Merci par avance de votre aide. André -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/201209162223.40872.andre_deb...@numericable.fr
Re: Kernel panic une fois sur deux
On Sun, 16 Sep 2012 22:23:40 +0200 andre_deb...@numericable.fr wrote: J'ai mis sur mon PC les répertoires /boot et /usr sur un disque SSD, les autres répertoires sur un disque dur SATA. Ben déjà avoir une copie des 2 dirs sur chaque HD, puis tester lequel pose PB (SI c'est réellement un PB de HD [¯doutes¯]). -- Gui_ Eh post-it ? Tu serais pas asiat ? post-it si comen tu sé on se conné? Gui_ Non non, mais j't'imagine petite jaune et collante. post-it hein ? -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120916230242.61fcbdfb@anubis.defcon1
Kernel panic após compilação.
Pessoal, obrigado pelas respostas, achei a solução, agora meu singelo notebook está bala. No meu caso eu estava desabilitando algum módulo necessário para montar as partições do HD, mesmo elas sendo reconhecidas. Utilizei o make localmodconfig (excelente). Aí depois dele dei uma tunada nas opções que queria desabilitadas. Segue uma página com a explicação dele. http://www.h-online.com/open/features/Good-and-quick-kernel-configuration-creation-1403046.html -- Adiel de Lima Ribeiro facebook.com/sembr.dyndns.info
Re: Kernel panic.
Pessoal, resumindo meu problema, depois de recompilar o Kernel meu sistema não inicia, fiz um teste para ver se era algum módulo faltando e não era, pois no teste recompilei o Kernel com as configurações antigas e retirei apenas o suporte a virtualização. Na minha compilação utilizei o fonte do debian, no qual foi gerado um binário em /usr/src/linux-source-2.6.32 no diretório arch/x86/boot, este binário se chama bzImage, o qual copio para o diretório /boot com o nome vmlinuz-modificado. Depois eu rodo o update-grub e ele reconhece tudo direitinho. Uma coisa que notei, é que não é gerada a linha initrd para a imagem vmlinuz-modificado, sendo que existe a linha nas imagens antigas. Tem alguma coisa a ver o initrd ? O que posso estar fazendo de errado? -- Adiel de Lima Ribeiro facebook.com/sembr.dyndns.info
Re: Kernel panic.
faltou vc gera a imagem na pasta /lib/module digite mkinitramfs -o /boot/initrd-kernel versao do kernel Ai pode reiniciar. Em 1 de agosto de 2012 15:31, Adiel de Lima Ribeiro adiel.netad...@gmail.com escreveu: Pessoal, resumindo meu problema, depois de recompilar o Kernel meu sistema não inicia, fiz um teste para ver se era algum módulo faltando e não era, pois no teste recompilei o Kernel com as configurações antigas e retirei apenas o suporte a virtualização. Na minha compilação utilizei o fonte do debian, no qual foi gerado um binário em /usr/src/linux-source-2.6.32 no diretório arch/x86/boot, este binário se chama bzImage, o qual copio para o diretório /boot com o nome vmlinuz-modificado. Depois eu rodo o update-grub e ele reconhece tudo direitinho. Uma coisa que notei, é que não é gerada a linha initrd para a imagem vmlinuz-modificado, sendo que existe a linha nas imagens antigas. Tem alguma coisa a ver o initrd ? O que posso estar fazendo de errado? -- Adiel de Lima Ribeirofacebook.com/sembr.dyndns.info -- Alcione Ferreira Sombra® 101080 [http://www.alcionesytes.net/] --- Liberdade e conhecimento ao alcance de todos. Office Escritório - http://www.openoffice.org.br/ Navegador Firefox - http://www.mozilla.org.br/ Email Thunderbird - http://www.mozilla.org.br/ --- Linux user number 432030 of http://counter.li.org/ --- ICQ: 377035698 Jabber: ksomb...@jabber.org MSN: alcione.som...@hotmail.com --- Curriculum: http://lattes.cnpq.br/0545256741852110
Re: Kernel panic.
Tenta fazer assim. apt-get install kernel-package libncurses5-dev fakeroot wget bzip2 build-essential cd /usr/src wget http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.4.7.tar.bz2 tar jxvf linux-3.4.7.tar.bz2 rm -rf linux ln -s linux-3.4.7 linux cd linux cp /boot/config-SEU_KERNEL_DO_DEBIAN .config Faça suas customizações make menuconfig make-kpkg clean fakeroot make-kpkg --initrd --append-to-version=-meukernelcompilado kernel_image kernel_headers Nesse caso estou usando a ultima versão estável Abraço, Rafael Bedendo Em 01-08-2012 16:31, Adiel de Lima Ribeiro escreveu: Pessoal, resumindo meu problema, depois de recompilar o Kernel meu sistema não inicia, fiz um teste para ver se era algum módulo faltando e não era, pois no teste recompilei o Kernel com as configurações antigas e retirei apenas o suporte a virtualização. Na minha compilação utilizei o fonte do debian, no qual foi gerado um binário em /usr/src/linux-source-2.6.32 no diretório arch/x86/boot, este binário se chama bzImage, o qual copio para o diretório /boot com o nome vmlinuz-modificado. Depois eu rodo o update-grub e ele reconhece tudo direitinho. Uma coisa que notei, é que não é gerada a linha initrd para a imagem vmlinuz-modificado, sendo que existe a linha nas imagens antigas. Tem alguma coisa a ver o initrd ? O que posso estar fazendo de errado? -- Adiel de Lima Ribeiro facebook.com/sembr.dyndns.info
Re: Kernel panic.
Bom dia! Alguns pontos que vc tem que observar: - source: baixou do kernel.org ou usou do repositório? - no processo de configuração vc usou a ultima config do kernel que tá rodando? - na parte de devices vc modificou alguma coisa? Se está tentando usar uma versão mais nova do kernel, tente não adicionar muitos módulos novos até seu novo kernel estar funcionando. Sobre o que vc reportou: isso geralmente ocorre por que o kernel não consegue montar o dispositivo de armazenamento. espero ter ajudado! Rotina que utilizo: - source na pasta /usr/src - linkagem do source com a pasta linux - make mrproper - cp config-antigo . - make menuconfig - carrego o config-antigo - reviso drivers, filesystem e segurança em geral - salvo como .config - antigamente compilava com o make bzImage modules, agora estou optando pelo make-kpkg Abraços Em 29 de julho de 2012 21:49, Adiel de Lima Ribeiro adiel.netad...@gmail.com escreveu: Pessoal, boa noite. Após recompilar meu kernel, quando inicio o sistema com o kernel recompilado estou tendo os seguintes problemas: O sistema não boot e me retorna as seguintes mensagens de erro: No filesystem could mount root, tried: cramfs vfat sysv v7 romfs Kernel panic - not syncing: VFS: unable to mount rootfs on unknow block Estou usando o Debian amd64, o sistema de arquivos é ext4 e está habilitado no kernel, o método de compressão dele é lzma, também habilitei o ROM filesystem support, o squash fs 4.0, o cramfs e o partition type msdos. As partições são reconhecidas, mas não consigo bootar o sitema. Existe alguma opção que estou deixando passar em branco no make menuconfig ? -- Adiel de Lima Ribeirofacebook.com/sembr.dyndns.info -- Alcione Ferreira Sombra® 101080 [http://www.alcionesytes.net/] --- Liberdade e conhecimento ao alcance de todos. Office Escritório - http://www.openoffice.org.br/ Navegador Firefox - http://www.mozilla.org.br/ Email Thunderbird - http://www.mozilla.org.br/ --- Linux user number 432030 of http://counter.li.org/ --- ICQ: 377035698 Jabber: ksomb...@jabber.org MSN: alcione.som...@hotmail.com --- Curriculum: http://lattes.cnpq.br/0545256741852110
Re: Kernel panic.
Obrigado pela resposta Alcione. Então, vamos la: Baixei o source do repositório com o apt-get. Utilizei a última configuração do kernel atual, copiando o vmlinuz-2.6.32-5-amd64 de /boot para o diretório que estou utilizando para compilar com o nome de .config. make oldconfig make menuconfig Copio o bzImage gerado no diretório de compilação em arch/x86_64/boot para com o nome de vmlinuz+meu-complemento para /boot. Deposi rodo o update-grub. No caso de novos módulos não estou adicionando, e sim retirando os desnecessários, pensei que poderia ter tirado algum driver, mas o boot reconhece as partições. Notei que a entrada para o novo kernel não tem a linha do initrd, qual o propósito dele afinal ? Faz alguma diferença não compilar em /usr/src ? On Mon, 2012-07-30 at 07:36 -0400, Alcione Ferreira wrote: Bom dia! Alguns pontos que vc tem que observar: - source: baixou do kernel.org ou usou do repositório? - no processo de configuração vc usou a ultima config do kernel que tá rodando? - na parte de devices vc modificou alguma coisa? Se está tentando usar uma versão mais nova do kernel, tente não adicionar muitos módulos novos até seu novo kernel estar funcionando. Sobre o que vc reportou: isso geralmente ocorre por que o kernel não consegue montar o dispositivo de armazenamento. espero ter ajudado! Rotina que utilizo: - source na pasta /usr/src - linkagem do source com a pasta linux - make mrproper - cp config-antigo . - make menuconfig - carrego o config-antigo - reviso drivers, filesystem e segurança em geral - salvo como .config - antigamente compilava com o make bzImage modules, agora estou optando pelo make-kpkg Abraços Em 29 de julho de 2012 21:49, Adiel de Lima Ribeiro adiel.netad...@gmail.com escreveu: Pessoal, boa noite. Após recompilar meu kernel, quando inicio o sistema com o kernel recompilado estou tendo os seguintes problemas: O sistema não boot e me retorna as seguintes mensagens de erro: No filesystem could mount root, tried: cramfs vfat sysv v7 romfs Kernel panic - not syncing: VFS: unable to mount rootfs on unknow block Estou usando o Debian amd64, o sistema de arquivos é ext4 e está habilitado no kernel, o método de compressão dele é lzma, também habilitei o ROM filesystem support, o squash fs 4.0, o cramfs e o partition type msdos. As partições são reconhecidas, mas não consigo bootar o sitema. Existe alguma opção que estou deixando passar em branco no make menuconfig ? -- Adiel de Lima Ribeirofacebook.com/sembr.dyndns.info -- Adiel de Lima Ribeiro facebook.com/sembr.dyndns.info
Re: Kernel panic.
Faz sim, mas não muito, mas o arquivo que vc deve copiar é config-2.6.32-5-amd64 não o vmlinuz-2.6.32-5-amd64 Acho que ai está a diferença. Em 30 de julho de 2012 10:37, Adiel de Lima Ribeiro adiel.netad...@gmail.com escreveu: Obrigado pela resposta Alcione. Então, vamos la: Baixei o source do repositório com o apt-get. Utilizei a última configuração do kernel atual, copiando o vmlinuz-2.6.32-5-amd64 de /boot para o diretório que estou utilizando para compilar com o nome de .config. make oldconfig make menuconfig Copio o bzImage gerado no diretório de compilação em arch/x86_64/boot para com o nome de vmlinuz+meu-complemento para /boot. Deposi rodo o update-grub. No caso de novos módulos não estou adicionando, e sim retirando os desnecessários, pensei que poderia ter tirado algum driver, mas o boot reconhece as partições. Notei que a entrada para o novo kernel não tem a linha do initrd, qual o propósito dele afinal ? Faz alguma diferença não compilar em /usr/src ? On Mon, 2012-07-30 at 07:36 -0400, Alcione Ferreira wrote: Bom dia! Alguns pontos que vc tem que observar: - source: baixou do kernel.org ou usou do repositório? - no processo de configuração vc usou a ultima config do kernel que tá rodando? - na parte de devices vc modificou alguma coisa? Se está tentando usar uma versão mais nova do kernel, tente não adicionar muitos módulos novos até seu novo kernel estar funcionando. Sobre o que vc reportou: isso geralmente ocorre por que o kernel não consegue montar o dispositivo de armazenamento. espero ter ajudado! Rotina que utilizo: - source na pasta /usr/src - linkagem do source com a pasta linux - make mrproper - cp config-antigo . - make menuconfig - carrego o config-antigo - reviso drivers, filesystem e segurança em geral - salvo como .config - antigamente compilava com o make bzImage modules, agora estou optando pelo make-kpkg Abraços Em 29 de julho de 2012 21:49, Adiel de Lima Ribeiro adiel.netad...@gmail.com escreveu: Pessoal, boa noite. Após recompilar meu kernel, quando inicio o sistema com o kernel recompilado estou tendo os seguintes problemas: O sistema não boot e me retorna as seguintes mensagens de erro: No filesystem could mount root, tried: cramfs vfat sysv v7 romfs Kernel panic - not syncing: VFS: unable to mount rootfs on unknow block Estou usando o Debian amd64, o sistema de arquivos é ext4 e está habilitado no kernel, o método de compressão dele é lzma, também habilitei o ROM filesystem support, o squash fs 4.0, o cramfs e o partition type msdos. As partições são reconhecidas, mas não consigo bootar o sitema. Existe alguma opção que estou deixando passar em branco no make menuconfig ? -- Adiel de Lima Ribeirofacebook.com/sembr.dyndns.info -- Adiel de Lima Ribeirofacebook.com/sembr.dyndns.info -- Alcione Ferreira Sombra® 101080 [http://www.alcionesytes.net/] --- Liberdade e conhecimento ao alcance de todos. Office Escritório - http://www.openoffice.org.br/ Navegador Firefox - http://www.mozilla.org.br/ Email Thunderbird - http://www.mozilla.org.br/ --- Linux user number 432030 of http://counter.li.org/ --- ICQ: 377035698 Jabber: ksomb...@jabber.org MSN: alcione.som...@hotmail.com --- Curriculum: http://lattes.cnpq.br/0545256741852110
Re: Kernel panic.
Sim, o arquivo que estou copiando é o config ..., mas depois de compilado é gerado um arquivo binario em arch/x86/boot com nome de bzImage, este compilado devemos copiar para /boot com o nome vmlinuz + seu complemento. On Mon, 2012-07-30 at 10:45 -0400, Alcione Ferreira wrote: Faz sim, mas não muito, mas o arquivo que vc deve copiar é config-2.6.32-5-amd64 não o vmlinuz-2.6.32-5-amd64 Acho que ai está a diferença. Em 30 de julho de 2012 10:37, Adiel de Lima Ribeiro adiel.netad...@gmail.com escreveu: Obrigado pela resposta Alcione. Então, vamos la: Baixei o source do repositório com o apt-get. Utilizei a última configuração do kernel atual, copiando o vmlinuz-2.6.32-5-amd64 de /boot para o diretório que estou utilizando para compilar com o nome de .config. make oldconfig make menuconfig Copio o bzImage gerado no diretório de compilação em arch/x86_64/boot para com o nome de vmlinuz+meu-complemento para /boot. Deposi rodo o update-grub. No caso de novos módulos não estou adicionando, e sim retirando os desnecessários, pensei que poderia ter tirado algum driver, mas o boot reconhece as partições. Notei que a entrada para o novo kernel não tem a linha do initrd, qual o propósito dele afinal ? Faz alguma diferença não compilar em /usr/src ? On Mon, 2012-07-30 at 07:36 -0400, Alcione Ferreira wrote: Bom dia! Alguns pontos que vc tem que observar: - source: baixou do kernel.org ou usou do repositório? - no processo de configuração vc usou a ultima config do kernel que tá rodando? - na parte de devices vc modificou alguma coisa? Se está tentando usar uma versão mais nova do kernel, tente não adicionar muitos módulos novos até seu novo kernel estar funcionando. Sobre o que vc reportou: isso geralmente ocorre por que o kernel não consegue montar o dispositivo de armazenamento. espero ter ajudado! Rotina que utilizo: - source na pasta /usr/src - linkagem do source com a pasta linux - make mrproper - cp config-antigo . - make menuconfig - carrego o config-antigo - reviso drivers, filesystem e segurança em geral - salvo como .config - antigamente compilava com o make bzImage modules, agora estou optando pelo make-kpkg Abraços Em 29 de julho de 2012 21:49, Adiel de Lima Ribeiro adiel.netad...@gmail.com escreveu: Pessoal, boa noite. Após recompilar meu kernel, quando inicio o sistema com o kernel recompilado estou tendo os seguintes problemas: O sistema não boot e me retorna as seguintes mensagens de erro: No filesystem could mount root, tried: cramfs vfat sysv v7 romfs Kernel panic - not syncing: VFS: unable to mount rootfs on unknow block Estou usando o Debian amd64, o sistema de arquivos é ext4 e está habilitado no kernel, o método de compressão dele é lzma, também habilitei o ROM filesystem support, o squash fs 4.0, o cramfs e o partition type msdos. As partições são reconhecidas, mas não consigo bootar o sitema. Existe alguma opção que estou deixando passar em branco no make menuconfig ? -- Adiel de Lima Ribeirofacebook.com/sembr.dyndns.info -- Adiel de Lima Ribeirofacebook.com/sembr.dyndns.info -- Adiel de Lima Ribeiro facebook.com/sembr.dyndns.info
Re: Kernel panic.
vc está gerando o initrd.img corretamente? tente gerar a imagem usando o make-kpkg, instale o pacote kernel-package é assim vc não precisa mudar nada no que vc já fez só vai na pasta onde está o source e digita: make-kpkg --us --uc --append-to-version -meu_kernel --bzimage kernel_image kernel_source só esperar terminar ele vai gerar os pacotes do kernel na pasta /usr/src ai vc instala usando o dpkg --install Tente ai. Em 30 de julho de 2012 15:05, Adiel de Lima Ribeiro adiel.netad...@gmail.com escreveu: Sim, o arquivo que estou copiando é o config ..., mas depois de compilado é gerado um arquivo binario em arch/x86/boot com nome de bzImage, este compilado devemos copiar para /boot com o nome vmlinuz + seu complemento. On Mon, 2012-07-30 at 10:45 -0400, Alcione Ferreira wrote: Faz sim, mas não muito, mas o arquivo que vc deve copiar é config-2.6.32-5-amd64 não o vmlinuz-2.6.32-5-amd64 Acho que ai está a diferença. Em 30 de julho de 2012 10:37, Adiel de Lima Ribeiro adiel.netad...@gmail.com escreveu: Obrigado pela resposta Alcione. Então, vamos la: Baixei o source do repositório com o apt-get. Utilizei a última configuração do kernel atual, copiando o vmlinuz-2.6.32-5-amd64 de /boot para o diretório que estou utilizando para compilar com o nome de .config. make oldconfig make menuconfig Copio o bzImage gerado no diretório de compilação em arch/x86_64/boot para com o nome de vmlinuz+meu-complemento para /boot. Deposi rodo o update-grub. No caso de novos módulos não estou adicionando, e sim retirando os desnecessários, pensei que poderia ter tirado algum driver, mas o boot reconhece as partições. Notei que a entrada para o novo kernel não tem a linha do initrd, qual o propósito dele afinal ? Faz alguma diferença não compilar em /usr/src ? On Mon, 2012-07-30 at 07:36 -0400, Alcione Ferreira wrote: Bom dia! Alguns pontos que vc tem que observar: - source: baixou do kernel.org ou usou do repositório? - no processo de configuração vc usou a ultima config do kernel que tá rodando? - na parte de devices vc modificou alguma coisa? Se está tentando usar uma versão mais nova do kernel, tente não adicionar muitos módulos novos até seu novo kernel estar funcionando. Sobre o que vc reportou: isso geralmente ocorre por que o kernel não consegue montar o dispositivo de armazenamento. espero ter ajudado! Rotina que utilizo: - source na pasta /usr/src - linkagem do source com a pasta linux - make mrproper - cp config-antigo . - make menuconfig - carrego o config-antigo - reviso drivers, filesystem e segurança em geral - salvo como .config - antigamente compilava com o make bzImage modules, agora estou optando pelo make-kpkg Abraços Em 29 de julho de 2012 21:49, Adiel de Lima Ribeiro adiel.netad...@gmail.com escreveu: Pessoal, boa noite. Após recompilar meu kernel, quando inicio o sistema com o kernel recompilado estou tendo os seguintes problemas: O sistema não boot e me retorna as seguintes mensagens de erro: No filesystem could mount root, tried: cramfs vfat sysv v7 romfs Kernel panic - not syncing: VFS: unable to mount rootfs on unknow block Estou usando o Debian amd64, o sistema de arquivos é ext4 e está habilitado no kernel, o método de compressão dele é lzma, também habilitei o ROM filesystem support, o squash fs 4.0, o cramfs e o partition type msdos. As partições são reconhecidas, mas não consigo bootar o sitema. Existe alguma opção que estou deixando passar em branco no make menuconfig ? -- Adiel de Lima Ribeirofacebook.com/sembr.dyndns.info -- Adiel de Lima Ribeirofacebook.com/sembr.dyndns.info -- Adiel de Lima Ribeirofacebook.com/sembr.dyndns.info -- Alcione Ferreira Sombra® 101080 [http://www.alcionesytes.net/] --- Liberdade e conhecimento ao alcance de todos. Office Escritório - http://www.openoffice.org.br/ Navegador Firefox - http://www.mozilla.org.br/ Email Thunderbird - http://www.mozilla.org.br/ --- Linux user number 432030 of http://counter.li.org/ --- ICQ: 377035698 Jabber: ksomb...@jabber.org MSN: alcione.som...@hotmail.com --- Curriculum: http://lattes.cnpq.br/0545256741852110
Kernel panic.
Pessoal, boa noite. Após recompilar meu kernel, quando inicio o sistema com o kernel recompilado estou tendo os seguintes problemas: O sistema não boot e me retorna as seguintes mensagens de erro: No filesystem could mount root, tried: cramfs vfat sysv v7 romfs Kernel panic - not syncing: VFS: unable to mount rootfs on unknow block Estou usando o Debian amd64, o sistema de arquivos é ext4 e está habilitado no kernel, o método de compressão dele é lzma, também habilitei o ROM filesystem support, o squash fs 4.0, o cramfs e o partition type msdos. As partições são reconhecidas, mas não consigo bootar o sitema. Existe alguma opção que estou deixando passar em branco no make menuconfig ? -- Adiel de Lima Ribeiro facebook.com/sembr.dyndns.info
Kernel Panic
I saw a very strange error while installing debian cd - kernel panic - not syncing vfs unable to mount root fs on unknown block (254,6) What might be the reason for this error? !!! -- Harshad Joshi
Re: Kernel Panic
i am testing it on a dell vostro running Ubuntu 10.10 and Oracle Virtualbox..i havent tested it on real machine as yet.. the same iso runs well on older debian lenny and Virtualbox On Fri, Jul 6, 2012 at 4:09 PM, Kirill Sotnikov kirill.sotni...@maxifier.com wrote: What motherboard do u use? Kirill Sotnikov Maxifier, Inc. phone: +79179468634 skype: wlan1024 On Fri, Jul 6, 2012 at 1:38 PM, Harshad Joshi firewal...@gmail.comwrote: I saw a very strange error while installing debian cd - kernel panic - not syncing vfs unable to mount root fs on unknown block (254,6) What might be the reason for this error? !!! -- Harshad Joshi -- Harshad Joshi
Re: Kernel Panic
On Fri, 06 Jul 2012 15:08:18 +0530, Harshad Joshi wrote: (please, no html posts, thanks...) I saw a very strange error while installing debian cd - kernel panic - not syncing vfs unable to mount root fs on unknown block (254,6) What might be the reason for this error? !!! I've never seen it before :-? You can: 1/ Check the validity of the original ISO file checksum 2/ Try to install from USB stick instead Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jt70pg$339$1...@dough.gmane.org
3.2.0-3-686-pae kernel doesn't boot, kernel panic
Hi, I just installed 3.2.0-3-686-pae, but got a kernel panic when trying to boot with it. As transcribed from my phone-camera screenshot (there are 10 more lines of output I can transcribe if that'd help): [ 0.987169] Kernel panic - not syncing : VFS: Unable to mount root fs on unknown block(0,0) Any thoughts on why this kernel isn't working? Fortunately I was able to re-boot by selecting 3.2.0-2-686-pae from the Grub menu. This kernel had been installed explicitly by name: # aptitude install linux-image-3.2.0-2-686-pae Whereas 3.2.0-3-686-pae was installed using the linux-image-686-pae meta-package: # aptitude install linux-image-686-pae So something else I'm wondering...if I had initially installed 3.2.0-2-686-pae using the meta-package instead, would my recent upgrade to 3.2.0-3-686-pae using that same meta-package have removed 3.2.0-2-686-pae? % apt-show-versions linux-image-3.2.0-2-686-pae linux-image-3.2.0-2-686-pae 3.2.20-1 installed: No available version in archive % apt-show-versions linux-image-3.2.0-3-rt-686-pae linux-image-3.2.0-3-rt-686-pae/sid uptodate 3.2.21-3 % apt-show-versions linux-image-686-pae linux-image-686-pae/sid uptodate 3.2+45 This is up-to-date Sid on an X200s ThinkPad. John -- John Magolske http://B79.net/contact -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120706102333.gb10...@s70206.gridserver.com
Re: 3.2.0-3-686-pae kernel doesn't boot, kernel panic
On Fri 06 Jul 2012 at 03:23:33 -0700, John Magolske wrote: I just installed 3.2.0-3-686-pae, but got a kernel panic when trying to boot with it. As transcribed from my phone-camera screenshot (there are 10 more lines of output I can transcribe if that'd help): [ 0.987169] Kernel panic - not syncing : VFS: Unable to mount root fs on unknown block(0,0) Any thoughts on why this kernel isn't working? Not any more than might come from a search with the error message you have. Purge and reinstall the new kernel? Generate a new initrd? Have a look and see what you think. Fortunately I was able to re-boot by selecting 3.2.0-2-686-pae from the Grub menu. This kernel had been installed explicitly by name: # aptitude install linux-image-3.2.0-2-686-pae Whereas 3.2.0-3-686-pae was installed using the linux-image-686-pae meta-package: # aptitude install linux-image-686-pae So something else I'm wondering...if I had initially installed 3.2.0-2-686-pae using the meta-package instead, would my recent upgrade to 3.2.0-3-686-pae using that same meta-package have removed 3.2.0-2-686-pae? No. Which was fortunate for you. :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120705204002.GG28931@desktop
Re: How do I debug kernel panic that occurs while running X?
On 4 March 2012 01:28, Brendon Higgins blhigg...@gmail.com wrote: Any more ideas? As I said, I tried getting kdump working but have been having trouble getting it to behave. One more thought, but it's a bit of a long shot as to whether you have the equipment. The most watertight way I know of to capture kernel output is a serial port and another computer. If, by any chance, you have one on your machine, edit /etc/defaults/grub to include console=ttyS0,155200n1 (or whatever speed you like) on the kernel boot line. You'll also need another machine with either a serial port or a USB-serial adapter, making it half as likely that this will help you :P Of course, most computers these days (*ahem*) don't have serial ports. *Maybe* a USB-serial adapter will work for the target machine too... although this requires an extra level of redirection on the part of the kernel, and may not be as foolproof, so I wouldn't spend the money if you don't already have one (or, in fact, two). Other than that, I'm out of ideas. Hopefully someone else on this list has an idea that doesn't require technology that was rendered obsolete for most people by 1995... — Jason -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CA+Zd3Fc6Y7SjN_RafobOV4NJ819wR=6kjg0jaf2kxzbysfg...@mail.gmail.com
Re: How do I debug kernel panic that occurs while running X?
On 2012-03-04 09:16 +0100, Jason Heeris wrote: On 4 March 2012 01:28, Brendon Higgins blhigg...@gmail.com wrote: Any more ideas? As I said, I tried getting kdump working but have been having trouble getting it to behave. One more thought, but it's a bit of a long shot as to whether you have the equipment. The most watertight way I know of to capture kernel output is a serial port and another computer. If, by any chance, you have one on your machine, edit /etc/defaults/grub to include console=ttyS0,155200n1 (or whatever speed you like) on the kernel boot line. You'll also need another machine with either a serial port or a USB-serial adapter, making it half as likely that this will help you :P Of course, most computers these days (*ahem*) don't have serial ports. *Maybe* a USB-serial adapter will work for the target machine too... although this requires an extra level of redirection on the part of the kernel, and may not be as foolproof, so I wouldn't spend the money if you don't already have one (or, in fact, two). Other than that, I'm out of ideas. Hopefully someone else on this list has an idea that doesn't require technology that was rendered obsolete for most people by 1995... Either log in via ssh if that is still possible, or use netconsole to capture kernel messages. Sven http://www.kernel.org/doc/Documentation/networking/netconsole.txt http://blog.mraw.org/2010/11/08/Debugging_using_netconsole/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87eht84p3v@turtle.gmx.de
Re: How do I debug kernel panic that occurs while running X?
Hi, Jason Heeris wrote (Sun March 4, 2012): The most watertight way I know of to capture kernel output is a serial port and another computer. If, by any chance, you have one on your machine Not really an option (at least, not an easy one), I'm afraid. I only have two machines, and neither of them have serial ports. Rendered obsolete, indeed. Sven Joachim wrote (Sun March 4, 2012): Either log in via ssh if that is still possible, The computer has gone well beyond the point of responding to anything coming in over the network by the time it has frozen. or use netconsole to capture kernel messages. Thanks for the links. This looked promising, but I cannot get it to function. I can get the problem machine connected to a netbook successfully (I can talk between them over UDP using netcat). However, netconsole refuses to transmit any messages. I install the module just as the article you linked to suggests, and it appears to be correct when I see it logged in dmesg: [103337.293616] netconsole: local port 6665 [103337.293626] netconsole: local IP 0.0.0.0 [103337.293632] netconsole: interface 'eth0' [103337.293637] netconsole: remote port [103337.293642] netconsole: remote IP 192.168.0.1 [103337.293646] netconsole: remote ethernet address ff:ff:ff:ff:ff:ff [103337.293654] netconsole: local IP 192.168.0.2 [103337.293754] console [netcon0] enabled [103337.293762] netconsole: network logging started But this doesn't seem to work - there's just nothing transmitted. I can't even get it to send messages to a netcat listener on the same machine. Have you (or anyone) found this approach works? Is there something I'm missing? Thanks for your help so far. Peace, Brendon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201203041717.11587.blhigg...@gmail.com
Re: How do I debug kernel panic that occurs while running X?
Hi again, Charles Krinke wrote (Thu March 1, 2012): On the next boot, /var/log/messages shoild contain the last printk's from the kernel which would include any panic. Thanks. I'd already checked there, though, and no dice. The log just skips from the last innocuous kernel message to messages about the next boot. Nothing about what caused the reboot to be necessary. Jason Heeris wrote (Fri March 2, 2012): I've had problems with write caching causing the last few messages to be lost after a panic*, so if you don't see anything suspicious, maybe turn off write caching with 'hdparm -W 0 /dev/whatever' for long enough to reproduce the crash. Just in case. Thanks for the tip. I gave that a try using the manual invocation of a kernel panic (i.e., echo c /proc/sysrq-trigger) but I still get nothing in /var/log/messages about this event. So, I'm doubtful this'll work when a real panic strikes, unfortunately. FWIW, at the moment I'm running the kernel in testing, but this has been a problem since back about 2.6.38 or 39. (I even tried doing a git bisection at one point, but being an intermittent problem it's difficult to determine when a particular commit doesn't exhibit it - I think I screwed it up at some point.) Any more ideas? As I said, I tried getting kdump working but have been having trouble getting it to behave. Peace, Brendon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201203031228.44898.blhigg...@gmail.com
How do I debug kernel panic that occurs while running X?
Hi list, For the better part of a year, now, something has been causing my machine to freeze. The mouse stops moving on the screen, pressing any key (including keys that should toggle lights) does nothing. The freezes are intermittent, without warning, and I've been unable to determine if there is any particular cause. I think the kernel is panicking, but I can't tell for sure. I don't think it caused by my hardware, either, because a Windows 7 install (Wintendo) seems to operate fine. The problem has never happened while I've been using the console, mostly because I'm there very rarely and I do the vast majority of my work in X. It's a desktop machine, after all. If it weren't for the fact of X being in the way when this happens, I might be far closer to finding the root cause of the problem I'm seeing. But the fact that I am unable to get any information at all from the kernel when the freeze occurs means I haven't been able to get anywhere with it in all this time. And yet it happens about once every few days. It's terrifically frustrating. I tried to get kdump working. I got as far as getting kexec running, and kdump claims to successfully load its kernel, but when I either manually cause a test panic or the bug happens, the kernel fails to start new, and so kdump never gets a chance to do its thing. kexec works fine to perform a regular restart the machine, though - which is irritating, actually, because it gets in the way when I wish to reboot into Wintendo. This issue is actually beginning to cause me some distress. There must be a way to extract panic info when X is running - how would the graphics driver writers debug things, otherwise? So does anyone have any suggestions as to how I can make some progress on diagnosing this? I'd appreciate being CC'd on replies, as I'm not sub'd to the list. Thanks! Peace, Brendon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201203012323.50867.blhigg...@gmail.com
Re: How do I debug kernel panic that occurs while running X?
On the next boot, /var/log/messages shoild contain the last printk's from the kernel which would include any panic. So, one should be able to tail /var/log messages and see what the kernel did at the time of the freeze. Remembdr that the fresh boot is appendex to /var/log/messages, so you need to scroll back a hundred lines or so. Charles On Mar 1, 2012 8:41 PM, Brendon Higgins blhigg...@gmail.com wrote: Hi list, For the better part of a year, now, something has been causing my machine to freeze. The mouse stops moving on the screen, pressing any key (including keys that should toggle lights) does nothing. The freezes are intermittent, without warning, and I've been unable to determine if there is any particular cause. I think the kernel is panicking, but I can't tell for sure. I don't think it caused by my hardware, either, because a Windows 7 install (Wintendo) seems to operate fine. The problem has never happened while I've been using the console, mostly because I'm there very rarely and I do the vast majority of my work in X. It's a desktop machine, after all. If it weren't for the fact of X being in the way when this happens, I might be far closer to finding the root cause of the problem I'm seeing. But the fact that I am unable to get any information at all from the kernel when the freeze occurs means I haven't been able to get anywhere with it in all this time. And yet it happens about once every few days. It's terrifically frustrating. I tried to get kdump working. I got as far as getting kexec running, and kdump claims to successfully load its kernel, but when I either manually cause a test panic or the bug happens, the kernel fails to start new, and so kdump never gets a chance to do its thing. kexec works fine to perform a regular restart the machine, though - which is irritating, actually, because it gets in the way when I wish to reboot into Wintendo. This issue is actually beginning to cause me some distress. There must be a way to extract panic info when X is running - how would the graphics driver writers debug things, otherwise? So does anyone have any suggestions as to how I can make some progress on diagnosing this? I'd appreciate being CC'd on replies, as I'm not sub'd to the list. Thanks! Peace, Brendon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201203012323.50867.blhigg...@gmail.com
Re: How do I debug kernel panic that occurs while running X?
On 2 March 2012 12:50, Charles Krinke charles.kri...@gmail.com wrote: So, one should be able to tail /var/log messages and see what the kernel did at the time of the freeze. I've had problems with write caching causing the last few messages to be lost after a panic*, so if you don't see anything suspicious, maybe turn off write caching with 'hdparm -W 0 /dev/whatever' for long enough to reproduce the crash. Just in case. * This was really only a problem because I was using a flash-based drive (not USB, but for an embedded system) with *really* aggressive caching. I don't know how bad the problem might be on a more ordinary drive. — Jason -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca+zd3fewattbjkp1km6armnkuhjmqfqce8cj3aaurf2dbjb...@mail.gmail.com
Kernel panic... something not syncing avec noyau 2.6.32-5-bigmem
Salut. Je me suis racheté deux barrettes de 2G pour mon PC, portant ma mémoire totale à 8G. J'ai donc changé de noyau et installé le noyau bigmem. Depuis, je rencontre des soucis du genre de ceux mentionnés dans le titre : le PC plante (une fois par mois, en gros), et quand j'essaye de rebooter, j'obtiens immédiatement un plantage juste après grub : Kernel panic... gnagna ... not syncing. J'ai un peu vadrouillé sur les bigs reports, je ne semble pas être le seul dans ce cas, mais je ne sais pas trop comment résoudre le problème : je ne sais pas afficher les messages d'erreur au boot (je n'arrive pas à faire défiler l'écran avec Shift Pg. Préc/Pg. Suiv). Avez-vous des choses à me conseiller pour résoudre ce problème ? Ah, oui, au fait, Debian Squeeze, sans diableries (sauf Iceweasel en backports). \bye -- Nicolas FRANCOIS | /\ http://nicolas.francois.free.fr | |__| X--/\\ We are the Micro$oft. _\_V Resistance is futile. You will be assimilated. darthvader penguin -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120228190626.6b255b1a@gaston
Re: Kernel panic... something not syncing avec noyau 2.6.32-5-bigmem
Le Tue, 28 Feb 2012 19:06:26 +0100, Nicolas FRANCOIS nicolas.franc...@free.fr a écrit : Salut. Je me suis racheté deux barrettes de 2G pour mon PC, portant ma mémoire totale à 8G. J'ai donc changé de noyau et installé le noyau bigmem. Depuis, je rencontre des soucis du genre de ceux mentionnés dans le titre : le PC plante (une fois par mois, en gros), et quand j'essaye de rebooter, j'obtiens immédiatement un plantage juste après grub : Kernel panic... gnagna ... not syncing. J'ai un peu vadrouillé sur les bigs reports, je ne semble pas être le seul dans ce cas, mais je ne sais pas trop comment résoudre le problème : je ne sais pas afficher les messages d'erreur au boot (je n'arrive pas à faire défiler l'écran avec Shift Pg. Préc/Pg. Suiv). Avez-vous des choses à me conseiller pour résoudre ce problème ? Ah, oui, au fait, Debian Squeeze, sans diableries (sauf Iceweasel en backports). \bye bonjour, serait il possible de modifier le fichier de conf : cat /etc/default/bootlogd # Run bootlogd at startup ? BOOTLOGD_ENABLE=Yes en pager : most pour lire les journaux, il est possible de renbooter sur un noyau viable ou de les consulter via un live cdrom ... slt bernard -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120228191239.313e89b7.bernard.schoenac...@free.fr
Re: Kernel panic... something not syncing avec noyau 2.6.32-5-bigmem
On Tue, 28 Feb 2012 19:06:26 +0100 Nicolas FRANCOIS nicolas.franc...@free.fr wrote: Vérifier si la RAM est en auto pour les timings. Si c'est le cas, l'analyser avec un utilitaire et la régler manuellement. -- First Corollary of Taber's Second Law: Machines that piss people off get murdered. -- Pat Taber -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120228191807.7d908940@anubis.defcon1
Re: Kernel panic... something not syncing avec noyau 2.6.32-5-bigmem
Le Tue, 28 Feb 2012 19:18:07 +0100, Bzzz lazyvi...@gmx.com a écrit : On Tue, 28 Feb 2012 19:06:26 +0100 Nicolas FRANCOIS nicolas.franc...@free.fr wrote: Vérifier si la RAM est en auto pour les timings. Si c'est le cas, l'analyser avec un utilitaire et la régler manuellement. Memtest va me dire cela ? Si oui, que dois-je guetter dans les affichages ? Quels sont les paramètres primordiaux ? Le CAS ? Autre chose ? \bye -- Nicolas FRANCOIS | /\ http://nicolas.francois.free.fr | |__| X--/\\ We are the Micro$oft. _\_V Resistance is futile. You will be assimilated. darthvader penguin -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120228203238.73903bbf@gaston
Re: Kernel panic... something not syncing avec noyau 2.6.32-5-bigmem
On Tue, 28 Feb 2012 20:32:38 +0100 Nicolas FRANCOIS nicolas.franc...@free.fr wrote: Memtest va me dire cela ? Pour le CAS vi, mais le RAS c'est moins sur; mais il-y-a des tas d'utilitaires sur le net qui font ça très bien. Si oui, que dois-je guetter dans les affichages ? Quels sont les paramètres primordiaux ? Le CAS ? Autre chose ? Palement CAS (CL) RAS; mais il-y-a aussi trcd, trp tras. Note également qu'en Gal la carte mère n'aime pas des CAS différents suivant les barrettes. -- What a COINCIDENCE! I'm an authorized SNOOTS OF THE STARS dealer!! -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120228204112.21b63770@anubis.defcon1
Re: Kernel panic... something not syncing avec noyau 2.6.32-5-bigmem
Le Tue, 28 Feb 2012 19:12:39 +0100, Bernard Schoenacker bernard.schoenac...@free.fr a écrit : bonjour, serait il possible de modifier le fichier de conf : cat /etc/default/bootlogd # Run bootlogd at startup ? BOOTLOGD_ENABLE=Yes en pager : most pour lire les journaux, il est possible de renbooter sur un noyau viable ou de les consulter via un live cdrom ... Je boote normalement sur un noyau non-bigmem, et c'est sur ce noyau que j'avais posté les messages précédents (amputé que j'étais de 4Go, ce qui n'a, pour une session de moins d'une journée, pas de conséquence abominable). Évidemment, après avoir rebooté, j'ai pu lancer le noyau bigmem sans aucun message d'erreur !!! Au fait, en pager : most, c'est bienune ligne du fichier bootlogd ? Et où lit-on les bootlogs ? Dans /var/log ? Bon, attendons le prochain plantage. \bye -- Nicolas FRANCOIS | /\ http://nicolas.francois.free.fr | |__| X--/\\ We are the Micro$oft. _\_V Resistance is futile. You will be assimilated. darthvader penguin -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120228205009.413b7890@gaston
Re: Kernel panic... something not syncing avec noyau 2.6.32-5-bigmem
Le Tue, 28 Feb 2012 19:12:39 +0100, Bernard Schoenacker bernard.schoenac...@free.fr a écrit : bonjour, serait il possible de modifier le fichier de conf : cat /etc/default/bootlogd # Run bootlogd at startup ? BOOTLOGD_ENABLE=Yes en pager : most pour lire les journaux, il est possible de renbooter sur un noyau viable ou de les consulter via un live cdrom ... Je boote normalement sur un noyau non-bigmem, et c'est sur ce noyau que j'avais posté les messages précédents (amputé que j'étais de 4Go, ce qui n'a, pour une session de moins d'une journée, pas de conséquence abominable). Évidemment, après avoir rebooté, j'ai pu lancer le noyau bigmem sans aucun message d'erreur !!! Au fait, en pager : most, c'est bienune ligne du fichier bootlogd ? Et où lit-on les bootlogs ? Dans /var/log ? Sinon, je n'ai pas trouvé l'option memtest dans le boot, comme j'en avais une sous Ubuntu. C'est exprès ? Bon, attendons le prochain plantage. \bye -- Nicolas FRANCOIS | /\ http://nicolas.francois.free.fr | |__| X--/\\ We are the Micro$oft. _\_V Resistance is futile. You will be assimilated. darthvader penguin -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120228205042.1d8d62a0@gaston
Re: Kernel panic... something not syncing avec noyau 2.6.32-5-bigmem
On Tue, 28 Feb 2012 20:50:09 +0100 Nicolas FRANCOIS nicolas.franc...@free.fr wrote: Et où lit-on les bootlogs ? Dans /var/log ? /var/log/messages -- Darth Vader sleeps with a Teddywookie. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120228205733.340c5914@anubis.defcon1
Re: Kernel panic... something not syncing avec noyau 2.6.32-5-bigmem
On Tue, 28 Feb 2012 20:50:42 +0100 Nicolas FRANCOIS nicolas.franc...@free.fr wrote: Sinon, je n'ai pas trouvé l'option memtest dans le boot, comme j'en avais une sous Ubuntu. C'est exprès ? Contrairement à trudububu, Debian considère que l'admin est un adulte qualifié; il est donc de sa responsabilité d'installer les packages voulus. -- Darth Vader sleeps with a Teddywookie. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20120228205922.370d00c2@anubis.defcon1
Re: Kernel panic... something not syncing avec noyau 2.6.32-5-bigmem
Le Tue, 28 Feb 2012 20:50:42 +0100,
Nicolas FRANCOIS nicolas.franc...@free.fr a écrit :
Le Tue, 28 Feb 2012 19:12:39 +0100,
Bernard Schoenacker bernard.schoenac...@free.fr a écrit :
bonjour,
serait il possible de modifier le fichier de conf :
cat /etc/default/bootlogd
# Run bootlogd at startup ?
BOOTLOGD_ENABLE=Yes
en pager : most
pour lire les journaux, il est possible de renbooter sur un
noyau viable ou de les consulter via un live cdrom ...
Je boote normalement sur un noyau non-bigmem, et c'est sur ce noyau
que j'avais posté les messages précédents (amputé que j'étais de 4Go,
ce qui n'a, pour une session de moins d'une journée, pas de
conséquence abominable).
Évidemment, après avoir rebooté, j'ai pu lancer le noyau bigmem sans
aucun message d'erreur !!!
Au fait, en pager : most, c'est bienune ligne du fichier bootlogd ? Et
où lit-on les bootlogs ? Dans /var/log ?
Sinon, je n'ai pas trouvé l'option memtest dans le boot, comme j'en
avais une sous Ubuntu. C'est exprès ?
Bon, attendons le prochain plantage.
\bye
bonjour,
le pager most est un paquet qui permet de mieux lire les fichiers
en lecture seule avec une sytaxe proche de vim ...
les logs : /var/log/boot
autre outil (exemple) : dmegs |most
concernant l'option indiquée au boot, il suffit de vérifier
la présence des paquets installés :
dpkg -l | awk '/memt/ {print $2}'
memtest86
memtest86+
autrement, prière d'utiliser abracadabra
slt
bernard
--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists
Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive:
http://lists.debian.org/20120228210900.3bcf174d.bernard.schoenac...@free.fr
Kernel panic sur testing
Bonjour, Suite à une mise à jour hier soir, j'ai eu quelques kernel panic de façon relativement aléatoire sur l'installation de testing sur mon macbook. C'est la première fois que je suis confronté à des kernel panic et je ne sais pas trop comment interpréter ces choses là. J'ai fais une photo (désolé pour la qualité qui n'est pas fameuse, mais c'est lisible) http://furry.goldenfish.info/kernel_panic.jpeg J'ai essayé de changer de noyaux (en repassant à la version 3.0), mais le problème s'est produit une nouvelle fois (la photo correspond à cette version du noyaux). Pour l'instant je touche du bois, mais je pense que ça va se produire à nouveau. Je ne sais pas trop comment faire un rapport de bug pour ce problème, si quelqu'un pouvait m'aider pour ça, ça serait l'idéal. Merci d'avance Christophe -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/4ef885ef.4050...@goldenfish.info
Re: Kernel panic sur testing
On Mon, 26 Dec 2011 15:34:23 +0100 Goldy go...@goldenfish.info wrote: C'est la première fois que je suis confronté à des kernel panic et je ne sais pas trop comment interpréter ces choses là. Il faut en faire une mauvaise interprétation. J'ai essayé de changer de noyaux (en repassant à la version 3.0), mais le problème s'est produit une nouvelle fois (la photo correspond à cette version du noyaux). Les kworkers sont des placeholders pour les threads du kernel,soit la majorité de ses traitements (c'est pour cette raison qu'un KP provoque un trace, sinon on ne saurait pas où donner de la tête). Apparemment quelque chose ayant trait au WiFi (IEEE802.11) a fait capoter le thread. Il faut que tu vérifies: * s'il faut un firmware pour ta Cte, * s'il est chargé, * s'il est à jour, * quel est le driver chargé, et s'il ne peut pas y avoir un conflit entre 2 drivers différents, * quels sont les switches du driver nécessaires au chipset de ta Cte, en commençant par 'gader s'il n'y en a pas un pour le debugging histoire d'avoir des traces dans les logs, * que ton macbook n'a pas ses règles. Pour l'instant je touche du bois, mais je pense que ça va se produire à nouveau. Le don de double-vue, c'est courant... surtout le lendemain de noël. Je ne sais pas trop comment faire un rapport de bug pour ce problème, si quelqu'un pouvait m'aider pour ça, ça serait l'idéal. Avant de considérer que c'est un bug il faut vérifier que tout est fait dans les règles. -- Lavish spending can be disastrous. Don't buy any lavishes for a while. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20111226171140.7a1286a0@anubis.defcon1
Recent update of Xen packages causes kernel panic with HVM domU
Recently I lost power (along with much of New England) for eight days. When the juice started flowing again, I restarted my Xen server (Debian Squeeze, dual Xeon (8 cores), 16GB RAM), which came up fine but had a pile of package updates pending... === [UPGRADE] libavcodec52 4:0.5.4-1 - 4:0.5.5-1 [UPGRADE] libavformat52 4:0.5.4-1 - 4:0.5.5-1 [UPGRADE] libavutil49 4:0.5.4-1 - 4:0.5.5-1 [UPGRADE] libnss3-1d 3.12.8-1+squeeze3 - 3.12.8-1+squeeze4 [UPGRADE] libpostproc51 4:0.5.4-1 - 4:0.5.5-1 [UPGRADE] libpq5 8.4.8-0squeeze2 - 8.4.9-0squeeze1+b1 [UPGRADE] libswscale0 4:0.5.4-1 - 4:0.5.5-1 [UPGRADE] libxenstore3.0 4.0.1-2 - 4.0.1-4 [UPGRADE] postgresql 8.4.8-0squeeze2 - 8.4.9-0squeeze1 [UPGRADE] postgresql-8.4 8.4.8-0squeeze2 - 8.4.9-0squeeze1+b1 [UPGRADE] postgresql-client 8.4.8-0squeeze2 - 8.4.9-0squeeze1 [UPGRADE] postgresql-client-8.4 8.4.8-0squeeze2 - 8.4.9-0squeeze1+b1 [UPGRADE] postgresql-contrib 8.4.8-0squeeze2 - 8.4.9-0squeeze1 [UPGRADE] postgresql-contrib-8.4 8.4.8-0squeeze2 - 8.4.9-0squeeze1+b1 [UPGRADE] postgresql-doc 8.4.8-0squeeze2 - 8.4.9-0squeeze1 [UPGRADE] postgresql-doc-8.4 8.4.8-0squeeze2 - 8.4.9-0squeeze1 [UPGRADE] tzdata 2011m-0squeeze1 - 2011n-0squeeze1 [UPGRADE] tzdata-java 2011m-0squeeze1 - 2011n-0squeeze1 [UPGRADE] xen-hypervisor-4.0-amd64 4.0.1-2 - 4.0.1-4 [UPGRADE] xen-utils-4.0 4.0.1-2 - 4.0.1-4 [UPGRADE] xenstore-utils 4.0.1-2 - 4.0.1-4 === I did an aptitude safe-upgrade without even really looking at it. At the time, I had an HVM domU running. The upgrade crashed the system. I'm pretty sure it crashed while configuring the xen-hypervisor-4.0-amd64 package. When I brought it back up, I ran a dpkg --configure -a to finish the job. However, now, when I try to use my Windows HVM, I always get a kernel panic dealing with the vbd. For example... 8= kernel:[ 1919.981706] general protection fault: [#1] SMP kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent kernel:[ 1919.981870] Stack: kernel:[ 1919.981893] Call Trace: kernel:[ 1919.982020] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00 00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db 74 0c 8b 42 14 48 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44 89 ee 83 kernel:[ 1920.014542] general protection fault: [#2] SMP kernel:[ 1920.014550] last sysfs file: /sys/devices/vbd-3-832/uevent kernel:[ 1920.014729] Stack: kernel:[ 1920.014752] Call Trace: kernel:[ 1920.014836] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00 00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db 74 0c 8b 42 14 48 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44 89 ee 83 8= Then the system destabilizes. I have a pretty common setup. I can't be the only one! What the heck happened with those updates?!? Please help me out! thanks, -d -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebb2f08.4060...@fastmail.fm
Re: Recent update of Xen packages causes kernel panic with HVM domU
On 11/9/2011 7:55 PM, David Howland wrote: Recently I lost power (along with much of New England) for eight days. When the juice started flowing again, I restarted my Xen server (Debian Squeeze, dual Xeon (8 cores), 16GB RAM), which came up fine but had a pile of package updates pending... snip 8= kernel:[ 1919.981706] general protection fault: [#1] SMP kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent kernel:[ 1919.981870] Stack: kernel:[ 1919.981893] Call Trace: kernel:[ 1919.982020] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00 00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db 74 0c 8b 42 14 48 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44 89 ee 83 Where's the call trace? -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebb4248.9010...@hardwarefreak.com
Re: Recent update of Xen packages causes kernel panic with HVM domU
On 11/9/2011 10:17 PM, Stan Hoeppner wrote: On 11/9/2011 7:55 PM, David Howland wrote: 8= kernel:[ 1919.981706] general protection fault: [#1] SMP kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent kernel:[ 1919.981870] Stack: kernel:[ 1919.981893] Call Trace: kernel:[ 1919.982020] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00 00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db 74 0c 8b 42 1448 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44 89 ee 83 Where's the call trace? Here's the full syslog dump: Nov 9 16:45:32 rackable kernel: [ 1919.981706] general protection fault: [#1] SMP Nov 9 16:45:32 rackable kernel: [ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent Nov 9 16:45:32 rackable kernel: [ 1919.981717] CPU 2 Nov 9 16:45:32 rackable kernel: [ 1919.981720] Modules linked in: tun nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_physdev ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative parport_pc ppdev lp parport nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs xen_evtchn xenfs binfmt_misc bridge stp fuse loop ioatdma radeon ttm drm_kms_helper i2c_i801 drm i2c_algo_bit rng_core pcspkr dca evdev i2c_core i5000_edac edac_core i5k_amb psmouse serio_raw processor button acpi_processor shpchp pci_hotplug ext3 jbd mbcache dm_mod sd_mod crc_t10dif uhci_hcd ata_generic ata_piix ehci_hcd libata scsi_mod usbcore nls_base e1000e thermal thermal_sys [last unloaded: scsi_wait_scan] Nov 9 16:45:32 rackable kernel: [ 1919.981816] Pid: 24, comm: xenwatch Not tainted 2.6.32-5-xen-amd64 #1 S5000PSL Nov 9 16:45:32 rackable kernel: [ 1919.981819] RIP: e030:[810e8a40] [810e8a40] __kmalloc_track_caller+0xcd/0x13c Nov 9 16:45:32 rackable kernel: [ 1919.981829] RSP: e02b:8803ea52bb10 EFLAGS: 00010002 Nov 9 16:45:32 rackable kernel: [ 1919.981832] RAX: RBX: 331474c384d0f7d9 RCX: 0008 Nov 9 16:45:32 rackable kernel: [ 1919.981835] RDX: 880013216090 RSI: 00d0 RDI: 0003 Nov 9 16:45:32 rackable kernel: [ 1919.981838] RBP: 0200 R08: 80d0 R09: 8803ea52bdd7 Nov 9 16:45:32 rackable kernel: [ 1919.981841] R10: R11: 000186a0 R12: 8146bf10 Nov 9 16:45:32 rackable kernel: [ 1919.981843] R13: 00d0 R14: 00d0 R15: 0008 Nov 9 16:45:32 rackable kernel: [ 1919.981851] FS: 7fbc8fe9d700() GS:880013204000() knlGS: Nov 9 16:45:32 rackable kernel: [ 1919.981854] CS: e033 DS: ES: CR0: 8005003b Nov 9 16:45:32 rackable kernel: [ 1919.981857] CR2: 7fbc8f747000 CR3: 00030f11a000 CR4: 2660 Nov 9 16:45:32 rackable kernel: [ 1919.981861] DR0: DR1: DR2: Nov 9 16:45:32 rackable kernel: [ 1919.981864] DR3: DR6: 0ff0 DR7: 0400 Nov 9 16:45:32 rackable kernel: [ 1919.981868] Process xenwatch (pid: 24, threadinfo 8803ea52a000, task 8803ea4f3880) Nov 9 16:45:32 rackable kernel: [ 1919.981870] Stack: Nov 9 16:45:32 rackable kernel: [ 1919.981872] 8803ea4f3880 81141305 000881044ced 0008 Nov 9 16:45:32 rackable kernel: [ 1919.981878] 0 8803 8803 0001 8803ea52bc28 Nov 9 16:45:32 rackable kernel: [ 1919.981885] 0 41ed 810c846f 0004 Nov 9 16:45:32 rackable kernel: [ 1919.981893] Call Trace: Nov 9 16:45:32 rackable kernel: [ 1919.981900] [81141305] ? sysfs_new_dirent+0x2a/0xf7 Nov 9 16:45:32 rackable kernel: [ 1919.981906] [810c846f] ? kstrdup+0x2b/0x40 Nov 9 16:45:32 rackable kernel: [ 1919.981910] [81141305] ? sysfs_new_dirent+0x2a/0xf7 Nov 9 16:45:32 rackable kernel: [ 1919.981914] [8114177d] ? create_dir+0x2d/0x7c Nov 9 16:45:32 rackable kernel: [ 1919.981918] [81141801] ? sysfs_create_dir+0x35/0x4a Nov 9 16:45:32 rackable kernel: [ 1919.981924] [81190767] ? kobject_get+0x12/0x17 Nov 9 16:45:32 rackable kernel: [ 1919.981928] [8119089d] ? kobject_add_internal+0xcb/0x181 Nov 9 16:45:32 rackable kernel: [ 1919.981932] [81190aff] ? kobject_add+0x74/0x7c Nov 9 16:45:32 rackable kernel: [ 1919.981943] [8100e635] ? xen_force_evtchn_callback+0x9/0xa Nov 9 16:45:32 rackable kernel: [ 1919.981948] [8100ecf2] ? check_events+0x12/0x20 Nov 9 16:45:32 rackable kernel: [ 1919.981952] [810e9201] ? __kmalloc+0x12f/0x141 Nov 9 16:45:32 rackable kernel: [ 1919.981958] [8122e60c] ? device_private_init+0x13/0x45 Nov 9 16:45:32 rackable kernel: [ 1919.981963] [8122eaae] ? device_add+0xce/0x537 Nov 9 16:45:32 rackable
Re: Recent update of Xen packages causes kernel panic with HVM domU
On 11/9/2011 9:56 PM, David Howland wrote: On 11/9/2011 10:17 PM, Stan Hoeppner wrote: On 11/9/2011 7:55 PM, David Howland wrote: 8= kernel:[ 1919.981706] general protection fault: [#1] SMP kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent kernel:[ 1919.981870] Stack: kernel:[ 1919.981893] Call Trace: kernel:[ 1919.982020] Code: ff 14 25 40 eb 47 81 65 8b 04 25 a8 e3 00 00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db 74 0c 8b 42 1448 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44 89 ee 83 Where's the call trace? Here's the full syslog dump: snipped log See if you can fix it by backing these 3 out to the previous version you had installed: [UPGRADE] xen-hypervisor-4.0-amd64 4.0.1-2 - 4.0.1-4 [UPGRADE] xen-utils-4.0 4.0.1-2 - 4.0.1-4 [UPGRADE] xenstore-utils 4.0.1-2 - 4.0.1-4 Post the circumstances/history and a copy of the error log to LKML and the Xen list. In the mean time, check your filesystems to make sure none of your VM image files (or anyhting else) didn't get corrupted when the power died, or as a result of the upgrade. It would probably be a good idea to check out your hardware as well. Power outages often included spikes and surges before it completely goes dark. Assuming you're jacked into a good quality known-to-be-working UPS, damage to the machine, or storage array, is less likely to be a factor here. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebb50a0.30...@hardwarefreak.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
Stephen Powell wrote: On Tue, 01 Nov 2011 21:02:56 -0400 (EDT), Sian Mountbatten wrote: Thank you all for your helpful advice and info. I am giving up on squeeze because I get so many problems with building a series 3 kernel. I tried to download a kernel image from wheezy, but got problems when I tried to install the Debian package. I tried downloading and installing the dependencies, but putting a wheezy kernel onto a squeeze system did not work. So I have now downloaded the first DVD iso for wheeze and I shall try to install a series 3 kernel for that release. Again, thank you all for your help. I hope you have better luck with Wheezy. I am running a custom-built 3.0.0 kernel on Wheezy right now, and I am not having any problems. There are often dependencies between the kernel releases and some other packages closely related to the kernel, such as initramfs- tools, libc*, udev, etc. I suspect you will do better with Wheezy. I have now successfully installed wheezy on both my desktop and my laptop. I am more than satisfied with the KDE desktop and all the apps which are available. Thank you all for your time and interest. -- Sian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j917ug$c88$1...@speranza.aioe.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
Arnt Karlsen wrote: On Mon, 31 Oct 2011 13:56:46 -0700 (PDT), poenik...@operamail.com wrote in message 6a9c6581-5fbb-4848-9d92-81bf0dbce...@j36g2000prh.googlegroups.com: On Oct 31, 7:20 pm, poenik...@operamail.com poenik...@operamail.com wrote: On Oct 31, 12:40 am, Stephen Powell zlinux...@wowway.com wrote: Also, I recommend that you read http://users.wowway.com/~zlinuxman/Kernel.htm for a fairly comprehensive tutorial on kernel building in Debian which documents many common gotchas in kernel building. For example, there is a patch to kernel-package which is needed in some circumstances when building a version 3 kernel with make-kpkg. The patch is documented on the above web page. And, depending on which boot loader you use, you may need to install some hook scripts when using a custom kernel with Squeeze and later releases. This is also documented on the above web page. -- .''`. Stephen Powell : :' : `. `'` I followed the instructions given in Kernel.htm and built a kernel from the source tree I had downloaded fromwww.kernel.orgafter issuing make-kpkg debian. I also patched kernel-package using the patch file (linuxv3.diff) mentioned on the web page. I also used make localmodconfig to greatly reduce the number of modules actually compiled. Compiling the kernel took 34 mins on my 1.6GHz laptop. I installed the kernel using dpkg as root, checked that an initramfs image had been created, closed down and rebooted. The kernel loaded, entered runlevel 2, but commands that tried to write to the fs failed because it was still readonly. The kernel finally hung with nfsd. ctrl-alt-del successfully rebooted. I shall recompile the kernel without NFS support because I don't need it. I removed NFS stuff and recompiled the kernel. I also removed the packages nfs-kernel-server and nfs-common. After rebooting with the new kernel, it loaded, hung at points and eventually gave me a tty login prompt. I could login as sian as well as root, but the file system was still read-only. I suspect that GNOME has to be able to write to the fs so that is why I only got a tty prompt. Some messages emitted by the kernel when loading: - Can't open or create /var/run/syslogd.pid Unknown hardware ThinkPad EC touch: setting times of /var/lib/sudo: Read-only file system -- What do I do next? ..remount your disk read-write. At least the kernel loads and gives me a prompt. I don't understand why the file system is still read-only. ..could be _anything_ from a bad disk to a kernel config bug. My reading of your NFS hang is you should have patient enough to give it time to time out, at least once. (5 or 15 minutes?) ..try set up a syslog host on your lan and point your 3.0.4 box' syslog there, and post the url to it if you find funny errors etc things that warrants further fun. Problem solved by installing wheezy. -- Sian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j91811$c88$2...@speranza.aioe.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
poenik...@operamail.com wrote: On Oct 30, 8:10 pm, Hugo Vanwoerkom hvw59...@care2.com wrote: snip I suspect that my configuration of the kernel is at fault, but where should I start looking for problems? Problem solved by installing wheezy which comes with a 3.0.0 kernel. Thank you all for your time and patience. -- Sian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j91888$c88$3...@speranza.aioe.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Mon, 31 Oct 2011 13:56:46 -0700 (PDT), poenik...@operamail.com wrote in message 6a9c6581-5fbb-4848-9d92-81bf0dbce...@j36g2000prh.googlegroups.com: On Oct 31, 7:20 pm, poenik...@operamail.com poenik...@operamail.com wrote: On Oct 31, 12:40 am, Stephen Powell zlinux...@wowway.com wrote: Also, I recommend that you read http://users.wowway.com/~zlinuxman/Kernel.htm for a fairly comprehensive tutorial on kernel building in Debian which documents many common gotchas in kernel building. For example, there is a patch to kernel-package which is needed in some circumstances when building a version 3 kernel with make-kpkg. The patch is documented on the above web page. And, depending on which boot loader you use, you may need to install some hook scripts when using a custom kernel with Squeeze and later releases. This is also documented on the above web page. -- .''`. Stephen Powell : :' : `. `'` I followed the instructions given in Kernel.htm and built a kernel from the source tree I had downloaded fromwww.kernel.orgafter issuing make-kpkg debian. I also patched kernel-package using the patch file (linuxv3.diff) mentioned on the web page. I also used make localmodconfig to greatly reduce the number of modules actually compiled. Compiling the kernel took 34 mins on my 1.6GHz laptop. I installed the kernel using dpkg as root, checked that an initramfs image had been created, closed down and rebooted. The kernel loaded, entered runlevel 2, but commands that tried to write to the fs failed because it was still readonly. The kernel finally hung with nfsd. ctrl-alt-del successfully rebooted. I shall recompile the kernel without NFS support because I don't need it. I removed NFS stuff and recompiled the kernel. I also removed the packages nfs-kernel-server and nfs-common. After rebooting with the new kernel, it loaded, hung at points and eventually gave me a tty login prompt. I could login as sian as well as root, but the file system was still read-only. I suspect that GNOME has to be able to write to the fs so that is why I only got a tty prompt. Some messages emitted by the kernel when loading: - Can't open or create /var/run/syslogd.pid Unknown hardware ThinkPad EC touch: setting times of /var/lib/sudo: Read-only file system -- What do I do next? ..remount your disk read-write. At least the kernel loads and gives me a prompt. I don't understand why the file system is still read-only. ..could be _anything_ from a bad disk to a kernel config bug. My reading of your NFS hang is you should have patient enough to give it time to time out, at least once. (5 or 15 minutes?) ..try set up a syslog host on your lan and point your 3.0.4 box' syslog there, and post the url to it if you find funny errors etc things that warrants further fun. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2001151717.1dc35...@nb6.lan
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Mon, 31 Oct 2011 10:25:04 -0400 (EDT), Hugo Vanwoerkom wrote: Stephen Powell wrote: I would recommend using something like make localmodconfig to strip out drivers your hardware doesn't need. There are many hidden dependencies, such as SCSI support, that are not obvious. ... That will definitely give you a bootable kernel but with the stock Debian config, which is huge and gives you way more than you really need. IMO to get just the right kernel config is very tricky because it is an trial and error thing. What would be handy is an IDE that records what change you made and for what reason, so that it can be removed when your hardware changes. Perhaps you're thinking of make oldconfig or some other configuration target. make localmodconfig will definitely strip out modules that are not in use by the current hardware. There may be a few things that are built-in to the kernel that could be eliminated, but most stuff that is hardware-related is in a module by default, and make localmodconfig will get you 99% of the way (or better) toward the minimal kernel configuration for the current hardware. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1875441311.476634.1320189198947.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Mon, 31 Oct 2011 14:54:37 -0400 (EDT), poenik...@operamail.com wrote: I followed the instructions given in Kernel.htm and built a kernel from the source tree I had downloaded from www.kernel.org after issuing make-kpkg debian. I also patched kernel-package using the patch file (linuxv3.diff) mentioned on the web page. I also used make localmodconfig to greatly reduce the number of modules actually compiled. Compiling the kernel took 34 mins on my 1.6GHz laptop. I installed the kernel using dpkg as root, checked that an initramfs image had been created, closed down and rebooted. The kernel loaded, entered runlevel 2, but commands that tried to write to the fs failed because it was still readonly. The kernel finally hung with nfsd. ctrl-alt-del successfully rebooted. I shall recompile the kernel without NFS support because I don't need it. In a typical Debian boot, there are three stages for the root file system. In stage 1, the initial RAM file system is mounted as the root (/) file system. The boot loader loads the (mostly) compressed kernel image and the compressed initial RAM file system image into memory, then passes control to the kernel. The boot loader tells the kernel where the compressed initial RAM file system image is by passing it's address to the kernel. The kernel decompresses itself, decompresses the initial RAM file system image, frees the memory associated with the compressed version of the initial RAM file system, then mounts the uncompressed version of the initial RAM file system as the root (/) file system. For LILO, the image and initrd boot loader configuration records specify the kernel image and initial RAM file system image to be used, respectively. In stage 2, once all modules needed to do I/O to the disk have been loaded, as well as all modules needed to interpret the file system, the permanent root file system is mounted. Typically, it is mounted read-only. The location of the permanent root file system is passed to the kernel via the kernel command line from parameters specified in the boot loader configuration file. For LILO, the read-only and root boot loader configuration records specify this information. The corresponding options passed on the kernel command line are ro and root. Once the permanent root file system has been mounted read-only, the uncompressed initial RAM file system image is freed from memory. Additional kernel modules are loaded at this stage, including those specified in /etc/modules. They are loaded from the permanent root file system, still mounted read-only. In stage 3, the permanent root file system is mounted read-write. At this stage, the file system to use is specified by /etc/fstab. Obviously, you must make sure that your boot loader configuration file and /etc/fstab specify the same root file system. It is important that you *not* use traditional device nomenclature, such as /dev/hda1 /dev/sda1 etc. Generally, the newer the kernel, the less likely this is to work. You should specify the root file system, both in the boot loader configuration file and in /etc/fstab by using UUID=xxx... or LABEL=xxx specifications. Since you seem to be having trouble at stage 3, the first thing I would look at is /etc/fstab. If you don't find any errors there, please post your boot loader configuration file, /etc/fstab, and the kernel boot messages. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391569326.477490.1320191000468.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote: It is important that you *not* use traditional device nomenclature, such as /dev/hda1 /dev/sda1 Why? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j8q0c5$noi$1...@dough.gmane.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote: On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote: It is important that you *not* use traditional device nomenclature, such as /dev/hda1 /dev/sda1 Why? Two reasons. First, whether an IDE hard disk shows up as /dev/hda, /dev/hdb, etc. or /dev/sda, /dev/sdb, etc. depends on which drivers are being used. For example, the 2.6.32-3-686 kernel and earlier ones use the traditional IDE drivers, with device names /dev/hda, /dev/hdb, etc. The 2.6.32-5-686 and later kernels use the libata SCSI emulation drivers, with device names /dev/sda, /dev/sdb, etc. Second, the devices are not necessarily discovered in the same order every time with newer kernels. Let's say you have a system with one hard disk and one CD-ROM drive. On one boot, your hard disk may be assigned device name /dev/sda and the CD-ROM drive may be assigned the device name /dev/sdb. But on the next boot, it is possible that the CD-ROM drive may be assigned the device name /dev/sda and the hard disk may be assigned the device name /dev/sdb. You can never be sure. By using UUIDs or LABELs, you will always get the same physical partition mounted as the root file system every time, regardless of what its device name happens to be in the current boot. The same applies to non-root file sytems in /etc/fstab (i.e. /boot, /home, etc.) -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/544765130.478134.1320192054767.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Tue, 01 Nov 2011 20:00:54 -0400, Stephen Powell wrote: On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote: On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote: It is important that you *not* use traditional device nomenclature, such as /dev/hda1 /dev/sda1 Why? Two reasons. First, whether an IDE hard disk shows up as /dev/hda, /dev/hdb, etc. or /dev/sda, /dev/sdb, etc. depends on which drivers are being used. For example, the 2.6.32-3-686 kernel and earlier ones use the traditional IDE drivers, with device names /dev/hda, /dev/hdb, etc. The 2.6.32-5-686 and later kernels use the libata SCSI emulation drivers, with device names /dev/sda, /dev/sdb, etc. Second, the devices are not necessarily discovered in the same order every time with newer kernels. Let's say you have a system with one hard disk and one CD-ROM drive. On one boot, your hard disk may be assigned device name /dev/sda and the CD-ROM drive may be assigned the device name /dev/sdb. But on the next boot, it is possible that the CD-ROM drive may be assigned the device name /dev/sda and the hard disk may be assigned the device name /dev/sdb. You can never be sure. By using UUIDs or LABELs, you will always get the same physical partition mounted as the root file system every time, regardless of what its device name happens to be in the current boot. The same applies to non-root file sytems in /etc/fstab (i.e. /boot, /home, etc.) But my (single internal) hard disk is always /dev/sda, and my two external USB disks are always /dev/sdb and /dev/sdc. So what difference does it make? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j8q3n0$eor$1...@dough.gmane.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Wed, 02 Nov 2011 01:10:02 +0100, Stephen Powell wrote: On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote: On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote: It is important that you *not* use traditional device nomenclature, such as /dev/hda1 /dev/sda1 Why? Two reasons. First, whether an IDE hard disk shows up as /dev/hda, /dev/hdb, etc. or /dev/sda, /dev/sdb, etc. depends on which drivers are being used. For example, the 2.6.32-3-686 kernel and earlier ones use the traditional IDE drivers, with device names /dev/hda, /dev/hdb, etc. The 2.6.32-5-686 and later kernels use the libata SCSI emulation drivers, with device names /dev/sda, /dev/sdb, etc. Second, the devices are not necessarily discovered in the same order every time with newer kernels. Let's say you have a system with one hard disk and one CD-ROM drive. On one boot, your hard disk may be assigned device name /dev/sda and the CD-ROM drive may be assigned the device name /dev/sdb. But on the next boot, it is possible that the CD-ROM drive may be assigned the device name /dev/sda and the hard disk may be assigned the device name /dev/sdb. You can never be sure. By using UUIDs or LABELs, you will always get the same physical partition mounted as the root file system every time, regardless of what its device name happens to be in the current boot. The same applies to non-root file sytems in /etc/fstab (i.e. /boot, /home, etc.) -- .''`. Stephen Powell : :' : `. `'` `- Thank you all for your helpful advice and info. I am giving up on squeeze because I get so many problems with building a series 3 kernel. I tried to download a kernel image from wheezy, but got problems when I tried to install the Debian package. I tried downloading and installing the dependencies, but putting a wheezy kernel onto a squeeze system did not work. So I have now downloaded the first DVD iso for wheeze and I shall try to install a series 3 kernel for that release. Again, thank you all for your help. -- Sian Mountbatten -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j8q4s0$m0k$1...@dont-email.me
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Tue, 01 Nov 2011 20:43:12 -0400 (EDT), Walter Hurry wrote: But my (single internal) hard disk is always /dev/sda, and my two external USB disks are always /dev/sdb and /dev/sdc. So what difference does it make? You mean that *so far* your internal hard disk is always /dev/sda and *so far* your external USB disks are always /dev/sdb and /dev/sdc. There are no guarantees that it will always be so. On my system, I've noticed that my single internal hard disk is usually /dev/sda and my CD-ROM drive is usually /dev/sdb. But if I boot my system from a rescue CD, the CD-ROM drive is usually /dev/sda and the hard disk is usually /dev/sdb. But I cannot guarantee that the hard disk will always be /dev/sda even if I boot from the hard disk every time. It's all timing dependent. Devices are not necessarily discovered in any particular order anymore. It is safest to use UUIDs or LABELs. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1532239075.481697.1320198540616.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Tue, 01 Nov 2011 21:02:56 -0400 (EDT), Sian Mountbatten wrote: Thank you all for your helpful advice and info. I am giving up on squeeze because I get so many problems with building a series 3 kernel. I tried to download a kernel image from wheezy, but got problems when I tried to install the Debian package. I tried downloading and installing the dependencies, but putting a wheezy kernel onto a squeeze system did not work. So I have now downloaded the first DVD iso for wheeze and I shall try to install a series 3 kernel for that release. Again, thank you all for your help. I hope you have better luck with Wheezy. I am running a custom-built 3.0.0 kernel on Wheezy right now, and I am not having any problems. There are often dependencies between the kernel releases and some other packages closely related to the kernel, such as initramfs-tools, libc*, udev, etc. I suspect you will do better with Wheezy. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/332873274.481855.1320198967497.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
Stephen Powell wrote: On Sun, 30 Oct 2011 14:24:28 -0400 (EDT), poenik...@operamail.com wrote: I downloaded the source for kernel version 3.0.4 from www.kernel.org. ... I then ploughed through all the options, removing modules where I was sure I did not have the relevant hardware. ... I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It displayed an error message (kernel panic) to the effect that it could not load the root fs. What have I done wrong? I would recommend using something like make localmodconfig to strip out drivers your hardware doesn't need. There are many hidden dependencies, such as SCSI support, that are not obvious. Also, I recommend that you read http://users.wowway.com/~zlinuxman/Kernel.htm snip That will definitely give you a bootable kernel but with the stock Debian config, which is huge and gives you way more than you really need. IMO to get just the right kernel config is very tricky because it is an trial and error thing. What would be handy is an IDE that records what change you made and for what reason, so that it can be removed when your hardware changes. Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j8mb41$4jj$1...@dough.gmane.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Oct 31, 12:40 am, Stephen Powell zlinux...@wowway.com wrote: On Sun, 30 Oct 2011 14:24:28 -0400 (EDT), poenik...@operamail.com wrote: I downloaded the source for kernel version 3.0.4 fromwww.kernel.org. ... I then ploughed through all the options, removing modules where I was sure I did not have the relevant hardware. ... I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It displayed an error message (kernel panic) to the effect that it could not load the root fs. What have I done wrong? I would recommend using something like make localmodconfig to strip out drivers your hardware doesn't need. There are many hidden dependencies, such as SCSI support, that are not obvious. Also, I recommend that you read http://users.wowway.com/~zlinuxman/Kernel.htm for a fairly comprehensive tutorial on kernel building in Debian which documents many common gotchas in kernel building. For example, there is a patch to kernel-package which is needed in some circumstances when building a version 3 kernel with make-kpkg. The patch is documented on the above web page. And, depending on which boot loader you use, you may need to install some hook scripts when using a custom kernel with Squeeze and later releases. This is also documented on the above web page. -- .''`. Stephen Powell : :' : `. `'` I followed the instructions given in Kernel.htm and built a kernel from the source tree I had downloaded from www.kernel.org after issuing make-kpkg debian. I also patched kernel-package using the patch file (linuxv3.diff) mentioned on the web page. I also used make localmodconfig to greatly reduce the number of modules actually compiled. Compiling the kernel took 34 mins on my 1.6GHz laptop. I installed the kernel using dpkg as root, checked that an initramfs image had been created, closed down and rebooted. The kernel loaded, entered runlevel 2, but commands that tried to write to the fs failed because it was still readonly. The kernel finally hung with nfsd. ctrl-alt-del successfully rebooted. I shall recompile the kernel without NFS support because I don't need it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20a54e07-8ae8-4781-9d05-05ff49ec6...@q35g2000prh.googlegroups.com
