Re: [panic] "Cheetah error trap taken" with Debian 2.6.24 kernel
From: Frans Pop <[EMAIL PROTECTED]> Date: Tue, 10 Jun 2008 01:03:48 +0200 > Given that the screenshot shows that the line just before the crash > is "radeonfb (0001:02:00.0): ATI Radeon [d" which looks truncated the > most likely candidate looks to be drivers/video/aty/radeon_base.c (in > __devinit radeon_map_ROM). > That function even has some suspicious looking comments immediately above > the call. > > Finding out for sure would probably require building a custom installer > using a kernel with some added debugging statements. Is that needed? Since the pci_map_rom() call done by the Radeon driver will be done long before it registers itself as a console framebuffer device, we would not see the penguin on the screen and the framebuffer console output if it's invocation of pci_map_rom() were the cause. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [panic] "Cheetah error trap taken" with Debian 2.6.24 kernel
On Tuesday 10 June 2008, David Miller wrote: > From: Frans Pop <[EMAIL PROTECTED]> > Date: Tue, 10 Jun 2008 00:03:53 +0200 > > > Cheetah error trap taken afsr[001008000500] afar > > [07f90080] TPC[553f94] TNPC[553f98] O7[554274] > > TSTATE[9980001606] > > TPC > > pci_get_rom_size() is being called with an I/O address that > isn't responding. It is being called via pci_map_rom() because > I see no drivers directly calling pci_get_rom_size(). > > Find out what device driver is calling this routine. Given that the screenshot shows that the line just before the crash is "radeonfb (0001:02:00.0): ATI Radeon [d" which looks truncated the most likely candidate looks to be drivers/video/aty/radeon_base.c (in __devinit radeon_map_ROM). That function even has some suspicious looking comments immediately above the call. Finding out for sure would probably require building a custom installer using a kernel with some added debugging statements. Is that needed? Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [panic] "Cheetah error trap taken" with Debian 2.6.24 kernel
From: Frans Pop <[EMAIL PROTECTED]> Date: Tue, 10 Jun 2008 00:03:53 +0200 > Cheetah error trap taken afsr[001008000500] afar [07f90080] > TPC[553f94] TNPC[553f98] O7[554274] TSTATE[9980001606] > TPC pci_get_rom_size() is being called with an I/O address that isn't responding. It is being called via pci_map_rom() because I see no drivers directly calling pci_get_rom_size(). Find out what device driver is calling this routine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[panic] "Cheetah error trap taken" with Debian 2.6.24 kernel
Hi sparclinux devs (AKA David), We got a report on the Debian Sparc list of an installation issue involving a kernel panic. The thread so far is here: - http://lists.debian.org/debian-sparc/2008/05/msg00020.html - http://lists.debian.org/debian-sparc/2008/06/msg0.html (month split; both have follow-ups) Alexander Vlasov wrote: > Frans Pop planet.nl> writes: >> You could also try booting with BOOT_DEBUG=3. That will give you a >> debug shell at the earliest possible point. If the crash still happens, >> it's definitely a kernel or hardware issue. > > Haven't tried BOOT_DEBUG=3, but finally screenshoted the problem via KVM > Here is it: http://zulu.in.ua/screenshot.png OK, that seems pretty clear. This is still with the daily installer image, correct? Let's ask the kernel developers for advice as this panic comes from there (arch/sparc64/kernel/traps.c). First lines of the trap (see screenshot linked above for rest!): Cheetah error trap taken afsr[001008000500] afar [07f90080] TPC[553f94] TNPC[553f98] O7[554274] TSTATE[9980001606] TPC The kernel is either Debian kernel based on 2.6.24.4 (if the installer image is an older daily build) or 2.6.24.7 (if it is a current daily). Exact version can be checked if needed. I've added the original reporter in CC for easier follow-up. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help for a FTBFS on sparc
On Mon, Jun 09, 2008 at 01:46:23PM +0200, Matthias Klose wrote: > tag 479185 + moreinfo > severity 479185 important > thanks > > this fails with 4.1, 4.2 and 4.3. At least 4.1 wasn't changed at all, > so I assume the main reason is not GCC, but something else. The > configury of this package uses the running kernel, which is > 64bit. Does this lead to some wrong assumptions? It's been known to happen... if you can try it on sperger, the developer-accessible sparc machine, you could maybe get more information? -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux boot hangs
Frans Pop planet.nl> writes: > You could also try booting with BOOT_DEBUG=3. That will give you a debug > shell at the earliest possible point. If the crash still happens, it's > definitely a kernel or hardware issue. Haven't tried BOOT_DEBUG=3, but finally screenshoted the problem via KVM Here is it: http://zulu.in.ua/screenshot.png -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help for a FTBFS on sparc
tag 479185 + moreinfo severity 479185 important thanks this fails with 4.1, 4.2 and 4.3. At least 4.1 wasn't changed at all, so I assume the main reason is not GCC, but something else. The configury of this package uses the running kernel, which is 64bit. Does this lead to some wrong assumptions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: test
Yes. -Mensaje original- De: Angelo Rossi [mailto:[EMAIL PROTECTED] Enviado el: sábado, 07 de junio de 2008 20:22 Para: debian-sparc@lists.debian.org Asunto: test Please do you read me? tx Angelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
