Bug 7077
Summary: | SIS630: Old IDE driver does not support swsusp | ||
---|---|---|---|
Product: | Power Management | Reporter: | Patrizio Bassi (patrizio.bassi) |
Component: | Hibernation/Suspend | Assignee: | Rafael J. Wysocki (rjwysocki) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | bzolnier, lenb, pavel, protasnb, rjwysocki, rui.zhang, vojtech, yakui.zhao |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.21.x | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 7216 | ||
Attachments: |
the kernel panic with 2.6.18-rc5-git1
config file sis5513-add-proper-pci-pm-support.patch |
Description
Patrizio Bassi
2006-08-30 02:55:54 UTC
Created attachment 8903 [details]
the kernel panic with 2.6.18-rc5-git1
Created attachment 8904 [details]
config file
That call trace in Oops is a bit strange - psmouse_reconnect never calls bus_for_each_dev, it shoudl go straght intto synaptics_reconnect and synaptics_reconnect does not use memcpy... Dmitry it's a *really* vanilla kernel used with the attached config file. I am not saying it isn't, just that the oops trace looks wierd. The stack may be corrupted or something. Can your box resume if you unload psmouse module (or not compile it in)? i remember i tried on 2.6.17 to add a return in a synaptics detection routine. this made the kernel to suspend, but with the bug of IRQ 14 (the main subject of this bug) i didn't think about using psmouse module..../me stupid. i'll try this night and report tomorrow. any other hints? The IRQ 14 is probably a pending IDE IRQ left by the resume. The kernel IDE layer (drivers/ide) does not support suspend/resume fully and cannot handle this case. Clearing the drive status very early during resume (before IRQs are re-enabled) might do the trick i just tested 2.6.18-rc5-git1 using the psmouse as module. unloading it didn't fix the problem...i have the same issue as mm3: i see immediatly "disabling irq #14" and after that system hangs. i waiting more than 3 mins...so i had to power down manually. i suppose i should open another bug for psmouse problem, do i? alan you talked about clearing the drive during resume, but i have the problem during the suspend. The suspend is not working...the resume...i don't know because i never got it suspended! i'm not an expert...maybe i missed the point...sorry if so. Thanks for clarifying. I wonder where that IRQ comes from then. if i remember good, bypassing psmouse troubles, i could suspend with 2.6.17 but waiting for irq to be lost and so waiting for lots of time.. ...and...it just came into my mind....once i had the irq 14 problems but the suspend worked perfectly. i remember it was an old live cd...maybe 2.6.10-2.6.12 period i'm sorry but i can't bisect nor recover those infos :( Referring to Comment #10: I think it comes from the resume-during-suspend phase which is right after the image has been created. The original trace shows that probably the image cannot be saved for some reason. Patrizio, can you try 2.6.18-mm1 with "echo 8 > /proc/sys/kernel/printk" before the suspend? ok. i tried 2.6.18 (vanilla) and it still has both bugs (psmouse and suspend) for psmouse, i compiled as module and i removed it, so this bug is bypassed. for the irq 14, nothing to do. This night i'll try new mm1 and report asap. i just saw mm2 isout, do you want me to check it instead of mm1? ok i tested mm2. Report: the screen becomes black and kernel writes it's freeing memory (0 pages in my case) after some seconds the screen comes back to the normal shell and i see errors about hda losing interrupt. the problem is that this cycles...keeps losing interrupts and i can't use the shell. so i need to reset the pc, i can't check the dmesg. i remember same issue on older kernel (the ones on live cd), but waiting some seconds, after the fist lost interrupt, i could suspend it. Thanks.
Have you tried to boot with init=/bin/bash and suspend? If not, please do
(ie. boot with init=/bin/bash, mount /sys, mount /proc, do "echo 8
> /proc/sys/kernel/printk" and "echo disk > /sys/power/state").
i just tested and got the same problem... black screen with some prints about suspending, after it cames back to the console, but it's locked and prints 0x24 dma interrupt lost problems. same as before...i did the test but i didn't expected different results, i know you asked me for that just to know if my distro was doing something weird in startup scripts... Reassigning to legacy IDE maintainer as thats the original source. Looks more like a swsusp bug tho i tried with 2.6.19 and got same issue tried to compile only the new ATA layer, adding SIS and generic (P)ATA support, but i get error on irq #14 immediatly on startup. Any progress with this bug? can we use new pata-scsi interface? I guess so. I haven't tried it myself, though. i tried the new pata interface setting PATA generic and SIS support: doesn't boot irq14 problem, nobody cared. i must stay back with old config, with no suspend. i used 2.6.21.3 I think you should report the PATA boot problem to the PATA developers. Also, please try the newest -rc or -git kernel and see if the problem is still present in there. Patrizio, please check if the bug is still present in the newest kernels. Also, when you test recent kernels, please use the "old" IDE driver and make sure that you have BLK_DEV_IDEACPI set in the .config . tried against 2.6.22.6 with no changes :( Please try 2.3.23 when it's out. There will be some important suspend-related fixes in there. ok. here i get the usual Disabling IRQ #14 but suspend is not performed....stay there endlessy :( i will try 2.6.23 as soon as it hits the mirrors with 2.6.23 i still see the IRQ 14 msg (after 2-3 minutes...) linux turns on/off the cpu fan in 1 second, then blanks the screen...than nothing happens... Is the libata/PATA driver still failing for you? yes libata cannot work, i cannot bootup :( Have you tried to boot with noapic or noacpi? i tried with pci=noacpi (are we talking about the libata driver right?) Yes. pci=noacpi is equivalent to noacpi, AFAICS. Please try with noapic . You can also try with libata.noacpi=0, OTOH. oki tomorrow i'll try. any idea how to fix the old ide driver? does libata team use bugzilla? because we're going OT here. (In reply to comment #37) > oki tomorrow i'll try. > > any idea how to fix the old ide driver? Nope, CCing Alan. > does libata team use bugzilla? because we're going OT here. Yes, we are, but it's important to verify if suspend also breaks with the libata driver. i can only add that long time ago (more 1 year ) i could get suspend working perfectly. i think it was 2.6.14 or .12 but i'm not sure... libata team does indeed follow bugzilla Alan i just added a new bug http://bugzilla.kernel.org/show_bug.cgi?id=9157 Rafael i didn't CC you there, i didn't know if you were still interested. Rafael, we keep this bug to track the old IDE suspend issue, is it ok for you? (In reply to comment #41) > Alan i just added a new bug > http://bugzilla.kernel.org/show_bug.cgi?id=9157 > > Rafael i didn't CC you there, i didn't know if you were still interested. I've added my address to the CC list in there, thanks. > Rafael, we keep this bug to track the old IDE suspend issue, is it ok for > you? Yes, it is. CCing Bart, perhaps he can help us here. Are there any updates on this problem? Is it still being tracked/worked on? Thanks. I'm - I've seen no other similar reports, I can't reproduce it and it really someone with the exact h.w to fix it i'm still here, i attached all requested i don't know what else to do. Created attachment 15511 [details]
sis5513-add-proper-pci-pm-support.patch
Could you try the attached patch for 2.6.25-rc7 which adds proper PCI PM support to sis5513?
If it doesn't help I guess that bisecting the problem between 2.6.10?-2.6.17 would be the best option...
2.6.26 doesn't work as well....but now i'm not sure if it's ide issue only as i see not irq#14 print...just flashing cursor... Patrizio, you said in bug #9157 that you managed to make the pata/libata driver work for you. Did you also try to suspend/resume using this driver instead of the IDE one? Hi Rafael, this is the first thing i tried and unfortunatly doesn't work. screen becomes black, with a flashing cursors. i can wait minutes but no change. i have a big swap partition (600mb, while 300 mb ram). as said in previous comment #47 (with old ide stack enabled) i don't have anymore the irq 14 print. can i try anything to have this fixed? i'm thinking to try tuxonice sources as well. ps. hw is ok, winxp hibernate and puts in standby without any issue. however this bug says "old ide driver". Rafael, do you think i should open a new bug entry? If the in-kernel hibernation doesn't work for you, it's a little chance tuxonice will. As far as the handling of devices is concerned, Nigel uses pretty much the same code as we do. I think you can open a new bug entry for this problem w/ the pata/libata driver. yes i agree there should be no big change, and i hate the idea of not-vanilla kernels.... i will open a new bug as soon i find a moment. i guess this one will get fixed at the same time the libata one will...seems not related to ide at all... patrizio, what's the status of this bug? can you laptop work in the latest mainline kernel? Hi Rui, this bug is related to IDE driver and, as suggested, i switched to sis_pata driver now. however i cannot suspend anymore even with pata driver. Hi, Patrizio Will you please try the latest upstream kernel and see whether the issue still exists? It seems that OS won't use the swsusp partition in course of S3. And the swsusp partition is required in course of hibernation. thanks. i switched to the new pata interface and hibernation is working great! I can't test now with the old IDE driver, but...is this of any interest? no. it's good to know the libata driver is working well. close this bug. |