[Bug 363478] Re: WARNING: at /build/buildd/linux-rt-2.6.28/arch/x86/kernel/signal_32.c:608 do_signal+0x171/0x180()

I have seen this error as well when I switched over to linux-rt (as part of Ubuntu Studio), using 32-bit ubuntu. dmesg stack trace reads: [3.836907] [ cut here ] [3.836968] WARNING: at /build/buildd/linux-rt-2.6.28/arch/x86/kernel/signal_32.c:608 do_signal+0x171/0

Re: [Bug 111406] Old standing report

I haven't run into this problem since. Greg -Original Message- >From: Andreas Moog <[EMAIL PROTECTED]> >Sent: Aug 21, 2008 5:55 PM >To: [EMAIL PROTECTED] >Subject: [Bug 111406] Old standing report > >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >Thank you for taking the time to report

[Bug 68405] I've seen this problem as well

When I installed using this mechanism, I had the same problem with LILO and had to install it manually. It appears that the installation shell uses a terminal mode called "BRTERM". The LILO post-installation script doesn't like that and raises an error after installing everything correctly. This is

[Bug 111406] Detailed LILO output

I re-reran LILO with "-v5" to get more details about this failure to run on Feisty. [code] [EMAIL PROTECTED]:/boot$ sudo lilo -v5 LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2004 John Coffman Released 17-Nov-2004, and compiled at

[Bug 111406] LILO not working with root-LVM-RAID setup

Public bug reported: Binary package hint: lilo I am running Feisty on a 32-bit system, with root-on-LVM2-on-RAID1. A detailed description is located at http://ubuntuforums.org/showthread.php?p=2560360#post2560360. It lists various checks I have done. Though the problem is manifested through LILO

[Bug 82987] Re: Edgy amd64 kernel lockup

Had another lockup. It seemed to be pretty stable for several days. I had upgraded to: $ uname -a Linux stargate 2.6.17-11-generic #2 SMP Thu Feb 1 18:03:05 UTC 2007 x86_64 GNU/Linux I was hoping this had caused the issue to vanish. Unfortunately, not the case. Attached is the segment from /var/

[Bug 82987] Re: Edgy amd64 kernel lockup

0. Please update BIOS. > Need clearer direction why this is necessary. 1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture. > Already did that ea

[Bug 82987] Re: Edgy amd64 kernel lockup

** Attachment added: "lspci" http://librarian.launchpad.net/6488811/lspci.log -- Edgy amd64 kernel lockup https://launchpad.net/bugs/82987 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82987] Re: Edgy amd64 kernel lockup

** Attachment added: "dmidecode" http://librarian.launchpad.net/6488802/dmidecode.log -- Edgy amd64 kernel lockup https://launchpad.net/bugs/82987 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82987] Re: Edgy amd64 kernel lockup

** Attachment added: "dmesg" http://librarian.launchpad.net/6488801/dmesg.log -- Edgy amd64 kernel lockup https://launchpad.net/bugs/82987 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82987] Re: Edgy amd64 kernel lockup

** Attachment added: "Another kernel crash" http://librarian.launchpad.net/6268308/crash_kern3.log -- Edgy amd64 kernel lockup https://launchpad.net/bugs/82987 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82987] Another instance occurred

** Attachment added: "Another instance of the kernel freezing up the whole system" http://librarian.launchpad.net/6219851/crash_kern2.log -- Edgy amd64 kernel lockup https://launchpad.net/bugs/82987 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/

[Bug 82987] Re: Edgy amd64 kernel lockup

** Attachment added: "Lines from /var/log/kern.log when problem occurred until lockup." http://librarian.launchpad.net/6155803/crash_kern.log -- Edgy amd64 kernel lockup https://launchpad.net/bugs/82987 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mail

[Bug 82987] uname -a

Linux stargate 2.6.17-10-generic #2 SMP Tue Dec 5 21:16:35 UTC 2006 x86_64 GNU/Linux ** Description changed: Binary package hint: linux-image-2.6.17-10-generic I have an edgy eft amd64 server running MythTV all the time. Usually within 24-48 hours of bootup, when I turn on the TV, the e

[Bug 82987] Edgy amd64 kernel lockup

Public bug reported: Binary package hint: linux-image-2.6.17-10-generic I have an edgy eft amd64 server running MythTV all the time. Usually within 24-48 hours of bootup, when I turn on the TV, the entire system is frozen. I managed to reboot and harvest a kern.log file and capture the lines wher

[Bug 69794] Re: kernel panics at begining of installation on Mini-itx EN15000 m/b

I can read off this much information from an edgy boot job on an EN15000, if it is helpful for the kernel team: esi: db941f84 edi: ebp: esp: db941f34 ds: 007b es: 007b ss: 0068 Process swapper (pid: 1, threadinfo=db94 task=db960a50) Stack: 205d3036 c0369a00 0097