[Bug 290219] New: intel: closing the lid on a hp nx5000 hangs the machine hard
https://bugzilla.novell.com/show_bug.cgi?id=290219 Summary: intel: closing the lid on a hp nx5000 hangs the machine hard Product: openSUSE 10.3 Version: Alpha 5plus Platform: i586 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: seife@novell.com QAContact: sndirsch@novell.com CC: eich@novell.com, mhopf@novell.com Found By: Component Test I am using the intel X driver on a hp nx5000 and am very impressed by the new features. However, i encountered one problem: If i close the lid (or press the lid switch manually), the machine hangs hard. No magic sysrq possible, nothing. Switching to the i810 driver makes this work fine. Also, if i switch to a text console before closing the lid, the machine also does not hang. Egbert should be able to reproduce this easily, since he has exactly the same machine. I can also provide a spare nx5000 for reproducing / fixing the bug. I updated the BIOS to the latest version F.0D (from F.05) today and it did not change anyhting. Sometimes the machines hangs with the backlight still on, sometimes it hangs with the backlight already switched off. 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c1 --- Comment #1 from Stefan Seyfried <seife@novell.com> 2007-07-07 13:59:00 MST --- Note that this seems a pretty machine-specific problem, i did not encounter it on my toughbook with similar hardware. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c2 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |seife@novell.com --- Comment #2 from Stefan Dirsch <sndirsch@novell.com> 2007-07-08 02:46:33 MST --- What will be triggered when you close the lid? STR? STD? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c3 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|seife@novell.com | --- Comment #3 from Stefan Seyfried <seife@novell.com> 2007-07-09 16:59:49 MST --- nothing should be triggered (i explicitly disabled all triggers). A machine hang is triggered, however ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c4 --- Comment #4 from Stefan Dirsch <sndirsch@novell.com> 2007-07-09 19:47:30 MST --- Ok. I need the spare nx5000 on my desktop to reproduce this. Something must be triggered when the lid get closed before the machine - *before* the machine hangs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c5 --- Comment #5 from Stefan Dirsch <sndirsch@novell.com> 2007-07-11 03:26:08 MST --- /var/log/{warn,messages}: Jul 11 11:45:56 linux-lgsc powersaved[3220]: ERROR (handleHWEventRequest:202) Could not determine lid state Jul 11 11:45:57 linux-lgsc powersaved[3220]: ERROR (handleHWEventRequest:202) Could not determine lid state # acpi_listen [...] button/lid C13C 00000080 00000001 button/lid C13C 00000080 00000002 /var/log/Xorg.0.log: [...] <lid event> (EE) intel(0): present: FALSE (11 of 49) at 780 desired 779 temp 0 (II) intel(0): Output VGA disconnected (II) intel(0): EDID for output VGA (II) intel(0): Output LVDS connected (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0. (II) intel(0): I2C device "LVDSDDC_C:ddc2" removed. (II) intel(0): EDID for output LVDS (II) intel(0): Manufacturer: LGP Model: 557 Serial#: 0 (II) intel(0): Year: 2003 Week: 0 (II) intel(0): EDID Version: 1.3 (II) intel(0): Digital Display Input (II) intel(0): Max H-Image Size [cm]: horiz.: 30 vert.: 23 (II) intel(0): Gamma: 2.20 (II) intel(0): No DPMS capabilities specified; RGB/Color Display (II) intel(0): First detailed timing is preferred mode (II) intel(0): redX: 0.587 redY: 0.343 greenX: 0.320 greenY: 0.529 (II) intel(0): blueX: 0.158 blueY: 0.140 whiteX: 0.312 whiteY: 0.328 (II) intel(0): Manufacturer's mask: 0 (II) intel(0): Supported additional Video Mode: (II) intel(0): clock: 65.0 MHz Image Size: 304 x 228 mm (II) intel(0): h_active: 1024 h_sync: 1048 h_sync_end 1184 h_blank_end 1344 h_border: 0 (II) intel(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 806 v_border: 0 (II) intel(0): EDID (in hex): (II) intel(0): 00ffffffffffff0030f0570500000000 (II) intel(0): 000d0103801e17780a72b09657528728 (II) intel(0): 23505400000001010101010101010101 (II) intel(0): 01010101010164190040410026301888 (II) intel(0): 360030e4100000180000000000000000 (II) intel(0): 0000000000000000000000000000004c (II) intel(0): 475068696c6970734c43440a00000000 (II) intel(0): 004c503135305830382d41334d31009b (II) intel(0): Printing DDC gathered Modelines: (II) intel(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (II) intel(0): EDID vendor "LGP", prod id 1367 (II) intel(0): Not using default mode "640x350" (vrefresh out of range) (II) intel(0): Not using default mode "640x400" (vrefresh out of range) (II) intel(0): Not using default mode "720x400" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (width too large for virtual size) (II) intel(0): Not using default mode "1280x960" (width too large for virtual size) (II) intel(0): Not using default mode "1280x960" (width too large for virtual size) (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size) (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size) (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (height too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (height too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (height too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (height too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (height too large for virtual size) (II) intel(0): Not using default mode "1792x1344" (height too large for virtual size) (II) intel(0): Not using default mode "1792x1344" (height too large for virtual size) (II) intel(0): Not using default mode "1856x1392" (height too large for virtual size) (II) intel(0): Not using default mode "1856x1392" (height too large for virtual size) (II) intel(0): Not using default mode "1920x1440" (height too large for virtual size) (II) intel(0): Not using default mode "1920x1440" (height too large for virtual size) (II) intel(0): Not using default mode "832x624" (vrefresh out of range) (II) intel(0): Not using default mode "1152x768" (width too large for virtual size) (II) intel(0): Not using default mode "1400x1050" (height too large for virtual size) (II) intel(0): Not using default mode "1400x1050" (height too large for virtual size) (II) intel(0): Not using default mode "1600x1024" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1440" (height too large for virtual size) (II) intel(0): Not using default mode "2048x1536" (height too large for virtual size) (II) intel(0): Not using default mode "2048x1536" (height too large for virtual size) (II) intel(0): Not using default mode "2048x1536" (height too large for virtual size) (II) intel(0): Printing probed modes for output LVDS (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) SetClientVersion: 0 9 SetGrabKeysState - disabled (EE) intel(0): present: FALSE (11 of 49) at 780 desired 779 temp 0 (II) intel(0): Output VGA disconnected (II) intel(0): EDID for output VGA (II) intel(0): Output LVDS connected (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0. (II) intel(0): I2C device "LVDSDDC_C:ddc2" removed. (II) intel(0): EDID for output LVDS (II) intel(0): Manufacturer: LGP Model: 557 Serial#: 0 (II) intel(0): Year: 2003 Week: 0 (II) intel(0): EDID Version: 1.3 (II) intel(0): Digital Display Input (II) intel(0): Max H-Image Size [cm]: horiz.: 30 vert.: 23 (II) intel(0): Gamma: 2.20 (II) intel(0): No DPMS capabilities specified; RGB/Color Display (II) intel(0): First detailed timing is preferred mode (II) intel(0): redX: 0.587 redY: 0.343 greenX: 0.320 greenY: 0.529 (II) intel(0): blueX: 0.158 blueY: 0.140 whiteX: 0.312 whiteY: 0.328 (II) intel(0): Manufacturer's mask: 0 (II) intel(0): Supported additional Video Mode: (II) intel(0): clock: 65.0 MHz Image Size: 304 x 228 mm (II) intel(0): h_active: 1024 h_sync: 1048 h_sync_end 1184 h_blank_end 1344 h_border: 0 (II) intel(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 806 v_border: 0 (II) intel(0): EDID (in hex): (II) intel(0): 00ffffffffffff0030f0570500000000 (II) intel(0): 000d0103801e17780a72b09657528728 (II) intel(0): 23505400000001010101010101010101 (II) intel(0): 01010101010164190040410026301888 (II) intel(0): 360030e4100000180000000000000000 (II) intel(0): 0000000000000000000000000000004c (II) intel(0): 475068696c6970734c43440a00000000 (II) intel(0): 004c503135305830382d41334d31009b (II) intel(0): Printing DDC gathered Modelines: (II) intel(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (II) intel(0): EDID vendor "LGP", prod id 1367 (II) intel(0): Not using default mode "640x350" (vrefresh out of range) (II) intel(0): Not using default mode "640x400" (vrefresh out of range) (II) intel(0): Not using default mode "720x400" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (width too large for virtual size) (II) intel(0): Not using default mode "1280x960" (width too large for virtual size) (II) intel(0): Not using default mode "1280x960" (width too large for virtual size) (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size) (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size) (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (height too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (height too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (height too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (height too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (height too large for virtual size) (II) intel(0): Not using default mode "1792x1344" (height too large for virtual size) (II) intel(0): Not using default mode "1792x1344" (height too large for virtual size) (II) intel(0): Not using default mode "1856x1392" (height too large for virtual size) (II) intel(0): Not using default mode "1856x1392" (height too large for virtual size) (II) intel(0): Not using default mode "1920x1440" (height too large for virtual size) (II) intel(0): Not using default mode "1920x1440" (height too large for virtual size) (II) intel(0): Not using default mode "832x624" (vrefresh out of range) (II) intel(0): Not using default mode "1152x768" (width too large for virtual size) (II) intel(0): Not using default mode "1400x1050" (height too large for virtual size) (II) intel(0): Not using default mode "1400x1050" (height too large for virtual size) (II) intel(0): Not using default mode "1600x1024" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1440" (height too large for virtual size) (II) intel(0): Not using default mode "2048x1536" (height too large for virtual size) (II) intel(0): Not using default mode "2048x1536" (height too large for virtual size) (II) intel(0): Not using default mode "2048x1536" (height too large for virtual size) (II) intel(0): Printing probed modes for output LVDS (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c6 Egbert Eich <eich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sndirsch@novell.com |eich@novell.com --- Comment #6 from Egbert Eich <eich@novell.com> 2007-07-12 04:03:38 MST --- I've got such a beast. Let me look into it. I had plans to look into this driver this week anyhow. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c7 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com --- Comment #7 from Stefan Dirsch <sndirsch@novell.com> 2007-07-12 04:18:43 MST --- Thanks for taking over. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QAContact|sndirsch@novell.com |xorg-maintainer-bugs@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c9 Dirk Mueller <dmueller@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmueller@novell.com --- Comment #9 from Dirk Mueller <dmueller@novell.com> 2007-09-05 06:51:27 MST --- samsung x20 seems to be affected by this bug as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c10 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com --- Comment #10 from Stephan Kulow <coolo@novell.com> 2007-09-08 01:12:35 MST --- any update? The week mentioned in #6 is finished :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c11 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com --- Comment #11 from Stefan Dirsch <sndirsch@novell.com> 2007-09-08 01:19:39 MST --- Egbert's weeks are different. :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c12 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER- --- Comment #12 from Stephan Kulow <coolo@novell.com> 2007-09-14 07:12:56 MST --- Egbert? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c13 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kent.liu@intel.com, trenn@novell.com --- Comment #13 from Stefan Dirsch <sndirsch@novell.com> 2007-09-21 03:07:36 MST --- This issue is not ACPI related at all. Even disabling ACPI does not help. So it is likely something deep below in hardware system management. :-( The issue did not happen with the old i810 driver, since this was still heavily BIOS based (BIOS set the appropriate registers correctly). Figuring out to set which register(s) in which way can take a long time. Estimation by Egbert. 1 day up to 1 week. Adding Kent. Maybe he has a clue, which registers need to be set to fix this issue. Affected Laptops so far: - HP NX 5000 - Samsung X20 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c14 --- Comment #14 from Thomas Renninger <trenn@novell.com> 2007-09-21 03:50:43 MST --- Can you attach acpidump pls. There is a device that gets notified on Lid switch that has some video related functions. To server this notify a specifi ACPI driver must run which does not exist in the linux kernel. It also must work without serving this notify event, because it also works with native graphics drivers. All I could do from ACPI point of view is to have a look which SystemMemory or IO/ports this devide accesses through ACPI variables, maybe this can help... Getting acpidump from several affected machines might help. Especially the hp machines' acpidump does not help that much because the functions there are generated. Hopefully e.g. the Samsung has some more meaningful ACPI variables from which we could guess what the hardware behind ports/memory is used for. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
To server this notify a specifi ACPI driver must run which does not exist in the linux kernel. To serv this notify a specific ACPI driver must run which does not exist in the linux kernel. Hmm, but at this point the machine is already dead? So probably some registers must be initialised (in another way?) as it is done with the native graphics card drivers... What was the name of the new driver? Could this be mentioned in the subject of
https://bugzilla.novell.com/show_bug.cgi?id=290219#c15 --- Comment #15 from Thomas Renninger <trenn@novell.com> 2007-09-21 03:55:08 MST --- this bug, pls. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c16 --- Comment #16 from Kent Liu <kent.liu@intel.com> 2007-09-21 03:57:04 MST --- Can you provide a full Xorg.0.log? Since this is a mainline driver issue, we can report this to freedesktop bugzilla (https://bugs.freedesktop.org/. Intel upstream developer would able to look at this and help. Please select the Product as xorg, and the Component as Driver/Intel. Add me into the bug cc list would be useful since I can help you to push the progress. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c17 --- Comment #17 from Egbert Eich <eich@novell.com> 2007-09-21 04:09:51 MST --- (In reply to comment #13 from Stefan Dirsch)
This issue is not ACPI related at all. Even disabling ACPI does not help. So it is likely something deep below in hardware system management. :-( The issue did not happen with the old i810 driver, since this was still heavily BIOS based (BIOS set the appropriate registers correctly).
Figuring out to set which register(s) in which way can take a long time. Estimation by Egbert. 1 day up to 1 week.
Not quite a week. I'd say a day or two. This sort of thing used to be my everyday trade in the past. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c18 --- Comment #18 from Stefan Dirsch <sndirsch@novell.com> 2007-09-21 04:11:28 MST ---
What was the name of the new driver? Could this be mentioned in the subject of this bug, pls. The new driver name is "intel". It's already part of the bugreport summary. :-)
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c19 --- Comment #19 from Egbert Eich <eich@novell.com> 2007-09-21 04:17:34 MST --- (In reply to comment #14 from Thomas Renninger)
Can you attach acpidump pls. There is a device that gets notified on Lid switch that has some video related functions. To server this notify a specifi ACPI driver must run which does not exist in the linux kernel. It also must work without serving this notify event, because it also works with native graphics drivers.
All I could do from ACPI point of view is to have a look which SystemMemory or IO/ports this devide accesses through ACPI variables, maybe this can help...
Getting acpidump from several affected machines might help. Especially the hp machines' acpidump does not help that much because the functions there are generated. Hopefully e.g. the Samsung has some more meaningful ACPI variables from which we could guess what the hardware behind ports/memory is used for.
As far as I remember from discussions with Alan Hourihane who used to the the 2D intel driver lid switch is a very system specific thing. What happens on lid switch and how lid switch events are propagated seems to be entirely up to the oem. If this was a problem on more intel based laptops seife would have not left our office until it had gotten fixed :P -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c20 Egbert Eich <eich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Normal Status|ASSIGNED |RESOLVED Resolution| |LATER --- Comment #20 from Egbert Eich <eich@novell.com> 2007-09-24 10:43:06 MST --- I agree that this needs to be fixed. however the severity is not really critical as this problem seems to be limited to this very model. I will still look into this as I've also got such a laptop. Lowering severity marking LATER. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c22 --- Comment #22 from Stefan Dirsch <sndirsch@novell.com> 2007-10-22 17:36:12 MST --- This seems to be a known issue upstream. http://bugs.freedesktop.org/show_bug.cgi?id=11432 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219#c23 --- Comment #23 from Stefan Dirsch <sndirsch@novell.com> 2007-10-24 11:29:43 MST --- Another reference: http://lists.freedesktop.org/archives/xorg/2007-October/029604.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=290219#c24 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pavel@novell.com --- Comment #24 from Stefan Dirsch <sndirsch@novell.com> 2008-06-25 08:32:11 MDT --- *** Bug 403736 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=403736 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=290219#c25 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|LATER | --- Comment #25 from Stefan Dirsch <sndirsch@novell.com> 2008-06-25 08:39:36 MDT --- reopen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=290219#c26 --- Comment #26 from Stefan Seyfried <seife@novell.com> 2008-06-25 11:27:22 MDT --- i can reproduce this. On 11.0, echoing "1" into /proc/acpi/video/*/DOS keeps the machine from crashing, it does, however impact the lid button functionality badly. So in 11.0 it might be related to Bug 403736. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=290219#c27 Pavel Machek <pavel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major Component|X.Org |X.Org Product|openSUSE 10.3 |openSUSE 11.0 Version|Alpha 5plus |Final --- Comment #27 from Pavel Machek <pavel@novell.com> 2008-06-27 04:44:23 MDT --- Bug is still in 11.0. And yes, it can be worked around by echo 1 > DOS... What can be done to get this fixed in 11.1? 1) we could use Xfbdev on nx5000. Still better than machine dying every time you close the lid. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 Egbert Eich <eich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Minor -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 User pavel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=290219#c28 --- Comment #28 from Pavel Machek <pavel@novell.com> 2008-10-09 03:03:51 MDT --- I don't agree with severity=minor. It makes machine completely unusable in default install. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 User eich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=290219#c29 --- Comment #29 from Egbert Eich <eich@novell.com> 2008-10-13 05:49:14 MDT --- (In reply to comment #28 from Pavel Machek)
I don't agree with severity=minor. It makes machine completely unusable in default install.
Pavel, this bug had already disappeared from the surface of the earth noone cared and noone complained as noone seems to own such a laptop any more. Stefan Dirsch resurrected it as I was unable to find it so that I can work on it once i can find the time. If you think it's really relevant in real world feel free to work on it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=290219#c30 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|eich@novell.com |sndirsch@novell.com Severity|Minor |Major Status|REOPENED |NEW Priority|P5 - None |P2 - High --- Comment #30 from Thomas Renninger <trenn@novell.com> 2008-10-23 04:28:20 MDT --- Sounds related to this one: http://bugzilla.kernel.org/show_bug.cgi?id=6001 (AFAIK much more are affected and the _DOS=0/1 workaround does not work anymore). They describe a solution here: https://bugs.launchpad.net/xorg-server/+bug/138256 Section "Device" ... Option "ForceEnablePipeA" "true" EndSection added in xorg.conf seem to help/workaround this issue. Can someone try it, pls. Xorg+Intel graphics is Stefan AFAIK? -> Reassigning. As we have something to fix this IMO not minor bug -> increasing severity. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=290219#c31 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |pavel@novell.com --- Comment #31 from Stefan Dirsch <sndirsch@novell.com> 2008-10-23 05:07:59 MDT --- I cannot reproduce this issue any longer. Pavel should test this option. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=290219#c32 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|pavel@novell.com | Resolution| |DUPLICATE --- Comment #32 from Thomas Renninger <trenn@novell.com> 2008-10-24 03:44:03 MDT --- Not 100% sure whether it really is a duplicate. Still marking as such to not have the work of double writing. Please reopen if it comes out that this one is not a duplicate. *** This bug has been marked as a duplicate of bug 378917 *** https://bugzilla.novell.com/show_bug.cgi?id=378917 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=290219 User eich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=290219#c33 Egbert Eich <eich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |FIXED --- Comment #33 from Egbert Eich <eich@novell.com> 2008-10-28 11:58:24 MDT --- This is no longer a duplicate of bug 378917 as the symptoms are different. The system doesn't freeze any more with Beta 3 (according the Stefan Dirsch's tests on 11.0 it didn't even freeze there any more). The remaining problem is that as soon as the lid switch is hit the screen turns white as the chip stops driving the panel but the backlight stays on. This should be looked into separately. As far as the freeze topic is concerned we can probably close the ticket. https://bugzilla.novell.com/show_bug.cgi?id=378917 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com