Re: sparc / Problems with 3.2-kernel
BERTRAND Joël wrote: Andreas Barth a écrit : Hi, today I tried to resurrect our buildd on schroeder (which is from architecture sparc). While trying to do so, I had a couple of strange behaviours like vi freezing after 20-30 seconds, or I couldn't about tail with ctrl+c or suspend with ctrl+z. This didn't change after a reboot. Machine was running our official 3.2-kernel. After Martin rebooted the machine into oldstables 2.6.32 kernel, things are working as they should, and the buildd is up again. Question: Is this a known issue? How can we get a fix for that? (I would assume DSA will consider it a non-option to not be able to upgrade to our default kernels.) Hello, I have seen same freezes on Blade 2000 (2 * US III+/900 Cu), on U5 (US IIi/440), but not on a server that run with four US IIIi and not on a T1000 (sun4v/US T1). I have tested 3.2 debian kernels and official ones and both hang. I suppose there is another strange bug with special MMU. 2.6.32 is stable but on sparc64, 3.2 is not. I have not tested newer kernels. I've got 3.2 grafted onto Squeeze or Lenny on various older systems (from memory: U1, T1, U60, E4500), and it appears stable. In case it's significant, in most cases it's been built on the machine it's to run on. -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/kohi0e$k7c$1...@pye-srv-01.telemetry.co.uk
Re: sparc / Problems with 3.2-kernel
On Sun, Jun 2, 2013 at 11:38 PM, BERTRAND Joël joel.bertr...@systella.fr wrote: Andreas Barth a écrit : Hi, today I tried to resurrect our buildd on schroeder (which is from architecture sparc). While trying to do so, I had a couple of strange behaviours like vi freezing after 20-30 seconds, or I couldn't about tail with ctrl+c or suspend with ctrl+z. This didn't change after a reboot. Machine was running our official 3.2-kernel. Was the machine available via the network at the time of freeze? After Martin rebooted the machine into oldstables 2.6.32 kernel, things are working as they should, and the buildd is up again. Question: Is this a known issue? How can we get a fix for that? (I would assume DSA will consider it a non-option to not be able to upgrade to our default kernels.) I have seen same freezes on Blade 2000 (2 * US III+/900 Cu), on U5 (US IIi/440), but not on a server that run with four US IIIi and not on a T1000 (sun4v/US T1). I have tested 3.2 debian kernels and official ones and both hang. I suppose there is another strange bug with special MMU. 2.6.32 is stable but on sparc64, 3.2 is not. I have not tested newer kernels. Bertrand, Andreas, can you please enable the magic SysRq key and try to see what is the kernel busy with when it hangs? It's also possible to do it via the serial console: send-break and then 't' (without quotes). -- Regards, Artyom Tarasenko linux/sparc and solaris/sparc under qemu blog: http://tyom.blogspot.com/search/label/qemu -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CACXAS8AqdW_3MqoyB=3OOU=Hk70xsDXnemvW6WN-txyt7=f...@mail.gmail.com
Re: sparc / Problems with 3.2-kernel
Artyom Tarasenko a écrit : On Sun, Jun 2, 2013 at 11:38 PM, BERTRAND Joël joel.bertr...@systella.fr wrote: Andreas Barth a écrit : Hi, today I tried to resurrect our buildd on schroeder (which is from architecture sparc). While trying to do so, I had a couple of strange behaviours like vi freezing after 20-30 seconds, or I couldn't about tail with ctrl+c or suspend with ctrl+z. This didn't change after a reboot. Machine was running our official 3.2-kernel. Was the machine available via the network at the time of freeze? After Martin rebooted the machine into oldstables 2.6.32 kernel, things are working as they should, and the buildd is up again. Question: Is this a known issue? How can we get a fix for that? (I would assume DSA will consider it a non-option to not be able to upgrade to our default kernels.) I have seen same freezes on Blade 2000 (2 * US III+/900 Cu), on U5 (US IIi/440), but not on a server that run with four US IIIi and not on a T1000 (sun4v/US T1). I have tested 3.2 debian kernels and official ones and both hang. I suppose there is another strange bug with special MMU. 2.6.32 is stable but on sparc64, 3.2 is not. I have not tested newer kernels. Bertrand, Andreas, can you please enable the magic SysRq key and try to see what is the kernel busy with when it hangs? When freeze occurs, workstation was totaly blocked. SysRq didn't work anymore. I have reinstalled my Blade 2000 with NetBSD but I can try to obtain more information in a couple of weeks. My U5 runs with jessie (and a 2.6.32 kernel). Regards, JKB -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51acd1b3.1020...@systella.fr
sparc / Problems with 3.2-kernel
Hi, today I tried to resurrect our buildd on schroeder (which is from architecture sparc). While trying to do so, I had a couple of strange behaviours like vi freezing after 20-30 seconds, or I couldn't about tail with ctrl+c or suspend with ctrl+z. This didn't change after a reboot. Machine was running our official 3.2-kernel. After Martin rebooted the machine into oldstables 2.6.32 kernel, things are working as they should, and the buildd is up again. Question: Is this a known issue? How can we get a fix for that? (I would assume DSA will consider it a non-option to not be able to upgrade to our default kernels.) Andi -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130602130209.gv28...@mails.so.argh.org
Re: sparc / Problems with 3.2-kernel
Andreas Barth a écrit : Hi, today I tried to resurrect our buildd on schroeder (which is from architecture sparc). While trying to do so, I had a couple of strange behaviours like vi freezing after 20-30 seconds, or I couldn't about tail with ctrl+c or suspend with ctrl+z. This didn't change after a reboot. Machine was running our official 3.2-kernel. After Martin rebooted the machine into oldstables 2.6.32 kernel, things are working as they should, and the buildd is up again. Question: Is this a known issue? How can we get a fix for that? (I would assume DSA will consider it a non-option to not be able to upgrade to our default kernels.) Hello, I have seen same freezes on Blade 2000 (2 * US III+/900 Cu), on U5 (US IIi/440), but not on a server that run with four US IIIi and not on a T1000 (sun4v/US T1). I have tested 3.2 debian kernels and official ones and both hang. I suppose there is another strange bug with special MMU. 2.6.32 is stable but on sparc64, 3.2 is not. I have not tested newer kernels. Regards, JKB -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51abbb4f.5010...@systella.fr
Re: sparc / Problems with 3.2-kernel
I have a dual US-III in a Sun Blade 2500 running 3.9 and it's stable for me, but I don't recall having any problems with 3.2 either. Patrick On Sun, Jun 2, 2013 at 4:38 PM, BERTRAND Joël joel.bertr...@systella.frwrote: Andreas Barth a écrit : Hi, today I tried to resurrect our buildd on schroeder (which is from architecture sparc). While trying to do so, I had a couple of strange behaviours like vi freezing after 20-30 seconds, or I couldn't about tail with ctrl+c or suspend with ctrl+z. This didn't change after a reboot. Machine was running our official 3.2-kernel. After Martin rebooted the machine into oldstables 2.6.32 kernel, things are working as they should, and the buildd is up again. Question: Is this a known issue? How can we get a fix for that? (I would assume DSA will consider it a non-option to not be able to upgrade to our default kernels.) Hello, I have seen same freezes on Blade 2000 (2 * US III+/900 Cu), on U5 (US IIi/440), but not on a server that run with four US IIIi and not on a T1000 (sun4v/US T1). I have tested 3.2 debian kernels and official ones and both hang. I suppose there is another strange bug with special MMU. 2.6.32 is stable but on sparc64, 3.2 is not. I have not tested newer kernels. Regards, JKB -- To UNSUBSCRIBE, email to debian-sparc-REQUEST@lists.**debian.orgdebian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/**51abbb4f.5010...@systella.frhttp://lists.debian.org/51abbb4f.5010...@systella.fr
