Bug#614515: Same crash on two different laptop systems after resume with 2.6.37 from unstable

2011-03-24 Thread Pedro Martínez Juliá
I think this bug is fixed in 2.6.38 but I'm not sure. Have anybody tested it? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#614515: Same crash on two different laptop systems after resume with 2.6.37 from unstable

2011-02-26 Thread Pedro Martínez Juliá
Hello, I'm having this same problem in my laptop (Samsung X360). At first I thought the problem was in the kernel but it works on console (both using echo mem... and pm-suspend). The problem is that sometimes, after resuming, the kernel oopses in the console and then, if I switch to VT7

Bug#614515: Same crash on two different laptop systems after resume with 2.6.37 from unstable

2011-02-26 Thread Jonathan Nieder
Hi, Pedro Martínez Juliá wrote: I'm having this same problem in my laptop (Samsung X360). Could you file a separate bug and include a copy of the Oops message and information that follows it (you can get this from dmesg)? That said, I think the problem is in xserver-xorg-video-intel package

Bug#614515: Same crash on two different laptop systems after resume with 2.6.37 from unstable

2011-02-23 Thread Raphael Plasson
Gasp... shouldn't have talked. It crashed again, same error, same symptom, but with experimental kernel this time. Raphaël

Bug#614515: Same crash on two different laptop systems after resume with 2.6.37 from unstable

2011-02-22 Thread Frederik Himpe
I'm having exactly the same problem on two different systems with Intel graphics (Samsung N210 with Atom N450 and Intel GMA3150 graphics and Dell Latitude E6400 with Intel Mobile 4 Series Chipset Integrated Graphics). Last log messages after resume on Latitude E6400: Feb 21 20:51:41 defected

Bug#614515: Same crash on two different laptop systems after resume with 2.6.37 from unstable

2011-02-22 Thread Raphael Plasson
Same configuration for xserver/intel x11 driver here (I noticed this information was missing in my first email). I confirm that the experimental kernel doesn't seem to be affected by the bug. Still no crash in 48h, while three crashes where obtained with the Sid package in the same laps time