Bug 15297

Summary: system freezes when switching back and forth between tty1 and X
Product: Drivers Reporter: Carlos (erbrochendes)
Component: Video(Other)Assignee: drivers_video-other
Status: CLOSED OBSOLETE    
Severity: normal CC: alan, rui.zhang
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.32-trunk-amd64 Subsystem:
Regression: No Bisected commit-id:
Bug Depends on:    
Bug Blocks: 56331    
Attachments: dmesg before suspending
dmesg after suspending (and crash)
dmesg from wakeup with xserver restart and errors

Description Carlos 2010-02-14 10:16:59 UTC 
Created attachment 25039 [details]
dmesg before suspending

Hi there

I i try to wake the computer up from standby, i just get a black screen.
No keyboard inputs have any affect.
Ping from other computers get an timeout.

But it does NOT happen every time, sometime the wakeup works. I belief it happen more or less every time when the laptop is only on battery power on the wakeup.

Ones wakeup worked, but X restarted and i got this in all Terminals: BUG: unable to handle kernel NULL pointer dereference at 00000000000000de

I will upload the whole dmesg output.

For suspend i use this:
dmesg >dmesg_before; echo mem > /sys/power/state; dmesg >dmesg_after; sync;

I looks like that i sometimes geht dmesg_after, and somethimes i dont.
I will upload them both from my last wakeup attempt, you will se some errors (kernel panic?) in the dmesg_after file.

I use debian testing, for more information about my System visit: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566019
Comment 1 Carlos 2010-02-14 10:18:06 UTC 
Created attachment 25040 [details]
dmesg after suspending (and crash)
Comment 2 Carlos 2010-02-14 10:20:11 UTC 
Created attachment 25041 [details]
dmesg from wakeup with xserver restart and errors
Comment 3 Zhang Rui 2010-02-22 06:31:16 UTC 
this seems to be network driver problem to me.
please unload the rtl8187 driver manually before suspend and loaded it after resume. does the warning still exist?
Comment 4 Carlos 2010-02-22 13:11:23 UTC 
Mhh, rtl8187. That would me my external USB Wifi adabter. I dont use that regularly, that would explain why suspend somethime work, and sometimes it does not.
I will play around, see what i can find out.
Thanks
Comment 5 Carlos 2010-02-23 18:03:50 UTC 
Nope, i just had the power pluged in, and no rtl8187 driver loaded. I used KDE4 menu to suspend. I think it uses pm-suspend.

I can not find anything usefull in /var/log/syslog

As always, i got an blackscreen on wakeup.

One other thing, i am not sure of it is the same bug, but maybe it helps. Today i switches back and forth between tty1 and X, and after ~ 5 time switchen back i got an black screen und the system frooze. Just like on wakeup. 
Maybe it's an readon/X bug?
Comment 6 Zhang Rui 2010-02-24 01:28:53 UTC 
(In reply to comment #5)
> Nope, i just had the power pluged in, and no rtl8187 driver loaded. I used
> KDE4
> menu to suspend. I think it uses pm-suspend.
> 
> I can not find anything usefull in /var/log/syslog
> 
> As always, i got an blackscreen on wakeup.
> 
> One other thing, i am not sure of it is the same bug, but maybe it helps.
> Today
> i switches back and forth between tty1 and X, and after ~ 5 time switchen
> back
> i got an black screen und the system frooze. Just like on wakeup. 
> Maybe it's an readon/X bug?

Maybe we should fix this issue first and see if the problem still exists after S3 resume.
Comment 7 Carlos 2010-02-24 07:55:07 UTC 
Mhh, i am starting to think there is something wrong with my system. Yesterday Xserver restartet again after s3 resume, later that day i got an kernelpanic for no reason i could see (I was just browsing and in IRC). It was one of those kernelpanics where the screen froze and the keyboad LED where blinking.

And about 10 minutes ago my system froze on bootup. I could not even see the login screen, again just a blank black screen.

And yes, this morning the system also froze after s3 resume, here is an output of /var/log/messages.
You will see, the system gets in suspend on 07:12:46, and on 07:13:51 the system is booting up again after i did a hard reset.

How can i help you help me? Need more logs? just ask!

 Feb 24 07:12:46 bockwurst kernel: [  428.173546] PM: Syncing filesystems ... done.
Feb 24 07:12:46 bockwurst kernel: [  428.208087] Freezing user space processes ... (elapsed 0.00 seconds) done.
Feb 24 07:12:46 bockwurst kernel: [  428.209337] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Feb 24 07:12:46 bockwurst kernel: [  428.209427] Suspending console(s) (use no_console_suspend to debug)
Feb 24 07:12:46 bockwurst kernel: [  428.248049] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 24 07:12:46 bockwurst kernel: [  428.662285] sd 0:0:0:0: [sda] Stopping disk
Feb 24 07:12:46 bockwurst kernel: [  429.568652] rt61pci 0000:05:09.0: PCI INT A disabled
Feb 24 07:12:46 bockwurst kernel: [  429.584114] sdhci-pci 0000:05:04.2: PCI INT A disabled
Feb 24 07:12:46 bockwurst kernel: [  429.616031] pci 0000:01:05.0: PCI INT A disabled
Feb 24 07:12:46 bockwurst kernel: [  429.824113] HDA Intel 0000:00:14.2: PCI INT A disabled
Feb 24 07:12:46 bockwurst kernel: [  429.840067] ATIIXP_IDE 0000:00:14.1: PCI INT A disabled
Feb 24 07:12:46 bockwurst kernel: [  429.840087] ehci_hcd 0000:00:13.2: PCI INT A disabled
Feb 24 07:12:46 bockwurst kernel: [  429.840098] ohci_hcd 0000:00:13.1: PCI INT A disabled
Feb 24 07:12:46 bockwurst kernel: [  429.840107] ohci_hcd 0000:00:13.0: PCI INT A disabled
Feb 24 07:12:46 bockwurst kernel: [  429.840195] ACPI: Cannot set device to a higher-powered state than parent
Feb 24 07:12:46 bockwurst kernel: [  429.840449] sata_sil 0000:00:12.0: PCI INT A disabled
Feb 24 07:12:46 bockwurst kernel: [  429.840645] r8169 0000:04:00.0: PME# enabled
Feb 24 07:12:46 bockwurst kernel: [  429.872193] ACPI: Preparing to enter system sleep state S3
Feb 24 07:12:46 bockwurst kernel: [  429.888018] Disabling non-boot CPUs ...
Feb 24 07:12:46 bockwurst kernel: [  430.056024] CPU 1 is now offline
Feb 24 07:12:46 bockwurst kernel: [  430.056027] SMP alternatives: switching to UP code
Feb 24 07:12:46 bockwurst kernel: [  430.063694] CPU1 is down
Feb 24 07:12:46 bockwurst kernel: [  430.063711] Enabling non-boot CPUs ...
Feb 24 07:12:46 bockwurst kernel: [  430.064195] SMP alternatives: switching to SMP code
Feb 24 07:12:46 bockwurst kernel: [  430.070568] Booting processor 1 APIC 0x1 ip 0x6000
Feb 24 07:12:46 bockwurst kernel: [  430.062861] Initializing CPU#1
Feb 24 07:12:46 bockwurst kernel: [  430.062861] Calibrating delay using timer specific routine.. 3591.03 BogoMIPS (lpj=7182079)
Feb 24 07:12:46 bockwurst kernel: [  430.062861] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Feb 24 07:12:46 bockwurst kernel: [  430.062861] CPU: L2 Cache: 512K (64 bytes/line)
Feb 24 07:12:46 bockwurst kernel: [  430.062861] CPU 1/0x1 -> Node 0
Feb 24 07:12:46 bockwurst kernel: [  430.062861] CPU: Physical Processor ID: 0
Feb 24 07:12:46 bockwurst kernel: [  430.062861] CPU: Processor Core ID: 1
Feb 24 07:13:51 bockwurst kernel: imklog 4.4.2, log source = /proc/kmsg started.
Feb 24 07:13:51 bockwurst rsyslogd: [origin software="rsyslogd" swVersion="4.4.2" x-pid="1284" x-info="http://www.rsyslog.com"] (re)start
Feb 24 07:13:51 bockwurst kernel: [    0.000000] Initializing cgroup subsys cpuset
Feb 24 07:13:51 bockwurst kernel: [    0.000000] Initializing cgroup subsys cpu
Feb 24 07:13:51 bockwurst kernel: [    0.000000] Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-5) (ben@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 22:40:40 UTC 2010
Feb 24 07:13:51 bockwurst kernel: [    0.000000] Command line: BOOT_IMAGE=//vmlinuz-2.6.32-trunk-amd64 root=/dev/mapper/eins-root ro quiet fastboot pci=use_crs
Comment 8 Carlos 2010-02-24 08:17:18 UTC 
Ok, i did some more tty/X switching tests.
i switched from X to tty1 and back to X about ~ 5 times, = black screen, system froze
# restart
i switched from KDM to tty1 and back to KDM about 9 times, = nothing happens, everything works fine
# login
i switched from X to tty1 and back to X 1 time, = black screen, system froze
# restart
System froze on bootup, right there where KDM should have started.
Comment 9 Carlos 2010-03-03 08:26:01 UTC 
*bump*

Soo .. how can i debug this?
Comment 10 Alan 2012-06-14 17:10:21 UTC 
Is this still seen with modern kernels ?
Comment 11 Carlos 2012-06-14 17:32:58 UTC 
No idea, i switched hardware.
You can close this bug.

But thanks for your replay :D

o/
carlos

On Thursday 14 June 2012 19:10:22 bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=15297
> 
> 
> Alan <alan@lxorguk.ukuu.org.uk> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
> - CC|                            |alan@lxorguk.ukuu.org.uk
> 
> 
> 
> 
> --- Comment #10 from Alan <alan@lxorguk.ukuu.org.uk>  2012-06-14 17:10:21
> --- Is this still seen with modern kernels ?
Comment 12 Alan 2012-06-14 20:12:24 UTC 
thanks