retitle 272496 xserver-xfree86: [ati/radeon] power resume fails on iBook with Radeon Mobility M7 LW [regression from 4.3.0.dfsg.1-4] tag 272496 + upstream moreinfo thanks On Mon, Sep 20, 2004 at 02:12:18PM +0200, Christoph Hellwig wrote: > Package: xserver-xfree86 > Version: 4.3.0.dfsg.1-7 > > When suspending my iBook the resume fails after resuming the sungem > ethernet if I had been running X when suspending. Not runing X or > downgrading to xserver-xfree86-4.3.0.dfsg.1-4 from testing fixes the > problem. > > This is running various 2.6 kernels (kernel-image-2.6.8 from debian, > various homegrown recent 2.6 kernels). lspci output below: [...] > 0000:00:10.0 VGA compatible controller: ATI Technologies Inc Radeon > Mobility M7 LW [Radeon Mobility 7500] I don't experience any such problem on my iBook, but: * I run kernel 2.4. * I have an older iBook with a Radeon Mobility M3. Can you try kernel 2.4.27 and see if that works around the problem? I don't insist that you stay with that kernel -- I just want to know if it affects this bug. Also, please see the following: [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more information is required of you before this bug can be handled. Please run the following commands from a shell prompt to gather and deliver this information to us: $ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1 $ mailx -s "Re: Bug#272496" 272496@bugs.debian.org < /tmp/output If you do not have a "mailx" command on your system, you can get it by installing the "mailx" Debian package; for example, with the "aptitude install mailx" or "apt-get install mailx" commands as root. Alternatively, you can also use a mail command that is compatible with mailx's command-line syntax, such as "mutt". One very good way to file bugs with the Debian Bug Tracking System is to use the "reportbug" package and command of the same name. The reportbug program does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a "bounce" message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give "reportbug" a try as your primary bug reporting tool for the Debian System in the future. If you *did* use reportbug to file your report, then you're receiving this message because the information we expected to see was not present. If you deliberately deleted this information from the report, please don't do that in the future, even if it seems like it makes the mail too large. 50 kB (kilobytes) of configuration and log data is typical. Only if the included information greatly exceeds this amount (more than 100 kB) should you consider omitting it; instead, put it up on the World Wide Web somewhere and provide URLs to it in your report, or in subsequent followup by mailing <272496@bugs.debian.org>. Thank you! -- G. Branden Robinson | I'm not going to waste my precious Debian GNU/Linux | flash memory with Perl when I can branden@debian.org | do so much more with it. http://people.debian.org/~branden/ | -- Joey Hess
Attachment:
signature.asc
Description: Digital signature