Re: [Bug 95143] Re: BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

2008-08-29 Thread gashad
I no longer use Ubuntu, so I cannot perform this test now. When I was still using Ubuntu, it seems like 8.04 fixed my "soft lockup detected" bug anyway. On Thu, Aug 28, 2008 at 7:38 PM, Leann Ogasawara <[EMAIL PROTECTED]> wrote: > The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel f

[Bug 148958] Re: window title bar disappears completely on all windows

2007-10-22 Thread gashad
>From Macobas' suggestion, I tried adding these to the display driver section >of /etc/X11/xorg.conf: Option "AllowGLXWithComposite" "true" Option "RenderAccel" "true" Option "AddARGBGLXVisuals" "True" Then I restarted X (CTRL+ALT+BACKSPACE) and it seems to work. I'm running a G

[Bug 95143] Re: BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

2007-10-09 Thread gashad
I noticed that when I get the error, a bunch of references to "tg3" are made... For example: [ 1104.512000] [] tg3_timer+0x0/0x810 [tg3] [ 1104.512000] [] do_IRQ+0x40/0x80 [ 1104.512000] [] tg3_timer+0x0/0x810 [tg3] [ 1104.512000] [] common_interrupt+0x23/0x30 [ 1104.512000] [] tg3_timer+0x0/0x81

[Bug 95143] Re: BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

2007-06-25 Thread gashad
I get this problem without inserting or ejecting a PCMCIA card, but my dmesg log would suggest otherwise: [19919.104000] pccard: PCMCIA card inserted into slot 1 [19919.104000] pcmcia: registering new device pcmcia1.0 [19919.464000] input: Lid Switch as /class/input/input13 [19919.48] ACPI: Li

[Bug 95143] Re: BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

2007-06-25 Thread gashad
** Attachment added: "lspci.txt" http://launchpadlibrarian.net/8189978/lspci.txt -- BUG: soft lockup detected on CPU#0! (on PCMCIA eject) https://bugs.launchpad.net/bugs/95143 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 95143] Re: BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

2007-06-25 Thread gashad
** Attachment added: "lsmod.txt" http://launchpadlibrarian.net/8189979/lsmod.txt -- BUG: soft lockup detected on CPU#0! (on PCMCIA eject) https://bugs.launchpad.net/bugs/95143 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 95143] Re: BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

2007-06-25 Thread gashad
Oh, and just so you know, this is a Dell Inspiron 600m with ipw2100 wireless card, and ati radeon mobility 9000 (using the software "ati" driver in my xorg configuration... I'm /NOT/ running fglrx. When I was running ubuntu 6.10 and had this problem, blacklisting the ipw2100 did not fix the proble

[Bug 95143] Re: BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

2007-06-25 Thread gashad
It just happened about 1/3 of the way through rebooting into recovery mode... see attached dmesg log ** Attachment added: "dmesg output when bug occured while rebooting into recovery mode." http://launchpadlibrarian.net/8190188/dmesg.log5.startup.txt -- BUG: soft lockup detected on CPU#0! (o

[Bug 95143] Re: BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

2007-06-28 Thread gashad
** Attachment added: "lsmod.livecd.txt" http://launchpadlibrarian.net/8227235/lsmod.livecd.txt -- BUG: soft lockup detected on CPU#0! (on PCMCIA eject) https://bugs.launchpad.net/bugs/95143 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact fo

[Bug 95143] Re: BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

2007-06-28 Thread gashad
I rebooted my machine using the Ubuntu 7.04 LiveCD, connected to a wireless network, surfed for a while... then the "BUG: Soft Lockup on CPU#0!" messages came... If i'm reading things right, the dmesg log would suggest it may be a problem with ipw2100: [ 848.528000] ADDRCONF(NETDEV_UP): eth0: link

[Bug 95143] Re: BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

2007-06-28 Thread gashad
I have started a related thread on the ubuntu forums: http://ubuntuforums.org/showthread.php?t=483444 So far, nothing is fixing this problem... Please let me know what I can do to help resolve this problem ASAP... Unfortunately, I might have to switch distros if I can't this figured out reasonab