3c59x: Get rid of "Trying to free already-free IRQ"
Subsystems (2)
PATCH 1/1 3c59x: Get rid of "Trying to free already-free IRQ"
Following trace pops up if we try to suspend with 3c59x ethernet NIC brought down:
root@b1:~# ifconfig eth16 down root@b1:~# echo mem > /sys/power/state ... 3c59x 0000:00:10.0: suspend 3c59x 0000:00:10.0: PME# disabled Trying to free already-free IRQ 48 ------------[ cut here ]------------ Badness at c00554e4 [verbose debug info unavailable] NIP: c00554e4 LR: c00554e4 CTR: c019a098 REGS: c7975c60 TRAP: 0700 Not tainted (2.6.31-rc4) MSR: 00021032 <ME,CE,IR,DR> CR: 28242422 XER: 20000000 TASK = c79cb0c0[1746] 'bash' THREAD: c7974000 ... NIP [c00554e4] __free_irq+0x108/0x1b0 LR [c00554e4] __free_irq+0x108/0x1b0 Call Trace: [c7975d10] [c00554e4] __free_irq+0x108/0x1b0 (unreliable) [c7975d30] [c005559c] free_irq+0x10/0x24 [c7975d40] [c01e21ec] vortex_suspend+0x70/0xc4 [c7975d60] [c017e584] pci_legacy_suspend+0x58/0x100
This is because the driver manages interrupts without checking for netif_running().
Though, there are few other issues with suspend/resume in this driver. The intention of calling free_irq() in suspend() was to avoid any possible spurious interrupts (see commit 5b039e681b8c5f30aac9cc04385 "3c59x PM fixes"). But,
- On resume, the driver was requesting IRQ just after pci_set_master(), but before vortex_up() (which actually resets 3c59x chips).
- Issuing free_irq() on a shared IRQ doesn't guarantee that a buggy HW won't trigger spurious interrupts in another driver that requested the same interrupt. So, if we want to protect from unexpected interrupts, then on suspend we should issue disable_irq(), not free_irq().
--- drivers/net/3c59x.c | 12 +++--------- 1 files changed, 3 insertions(+), 9 deletions(-)
drivers/net/3c59x.c +3 -9
@@ -807,10 +807,10 @@ static int vortex_suspend(struct pci_dev *pdev, pm_message_t state)if (netif_running (dev)) {netif_device_detach (dev);vortex_down (dev,1 ); +disable_irq (dev->irq); }pci_save_state (pdev);pci_enable_wake (pdev,pci_choose_state (pdev, state),0 ); -free_irq (dev->irq, dev);pci_disable_device (pdev);pci_set_power_state (pdev,pci_choose_state (pdev, state)); }
@@ -833,18 +833,12 @@ static int vortex_resume(struct pci_dev *pdev)return err; }pci_set_master (pdev); -if (request_irq (dev->irq, vp->full_bus_master_rx ? - &boomerang_interrupt : &vortex_interrupt,IRQF_SHARED , dev->name, dev)) { -pr_warning ("%s: Could not reserve IRQ %d\n" , dev->name, dev->irq); -pci_disable_device (pdev); -return -EBUSY ; - }if (netif_running (dev)) { err =vortex_up (dev);if (err)return err; -else -netif_device_attach (dev); +enable_irq (dev->irq); +netif_device_attach (dev); } }return 0 ;
Signature · 1 line
1.6.3.3
Quoted 2 lines · Anton Vorontsov
Following trace pops up if we try to suspend with 3c59x ethernet NIC brought down:
Patch looks good, but IMO it'd be a little effort to convert the driver to dev_pm_ops while you're at it (please see r8169 for a working example).
Thanks,
Rafael
Quoted 80 lines
root@b1:~# ifconfig eth16 down root@b1:~# echo mem > /sys/power/state ... 3c59x 0000:00:10.0: suspend 3c59x 0000:00:10.0: PME# disabled Trying to free already-free IRQ 48 ------------[ cut here ]------------ Badness at c00554e4 [verbose debug info unavailable] NIP: c00554e4 LR: c00554e4 CTR: c019a098 REGS: c7975c60 TRAP: 0700 Not tainted (2.6.31-rc4) MSR: 00021032 <ME,CE,IR,DR> CR: 28242422 XER: 20000000 TASK = c79cb0c0[1746] 'bash' THREAD: c7974000 ... NIP [c00554e4] __free_irq+0x108/0x1b0 LR [c00554e4] __free_irq+0x108/0x1b0 Call Trace: [c7975d10] [c00554e4] __free_irq+0x108/0x1b0 (unreliable) [c7975d30] [c005559c] free_irq+0x10/0x24 [c7975d40] [c01e21ec] vortex_suspend+0x70/0xc4 [c7975d60] [c017e584] pci_legacy_suspend+0x58/0x100This is because the driver manages interrupts without checking for
netif_running().Though, there are few other issues with suspend/resume in this driver. The intention of calling
free_irq()insuspend()was to avoid any possible spurious interrupts (see commit5b039e681b8c5f30aac9cc04385"3c59x PM fixes"). But,- On resume, the driver was requesting IRQ just after
pci_set_master(), but beforevortex_up()(which actually resets 3c59x chips).- Issuing
free_irq()on a shared IRQ doesn't guarantee that a buggy HW won't trigger spurious interrupts in another driver that requested the same interrupt. So, if we want to protect from unexpected interrupts, then on suspend we should issuedisable_irq(), notfree_irq().Signed-off-by Anton Vorontsov <[email protected]>--- drivers/net/3c59x.c | 12 +++--------- 1 files changed, 3 insertions(+), 9 deletions(-)drivers/net/3c59x.c +3
-9@@ -807,10 +807,10 @@ static int vortex_suspend(struct pci_dev *pdev, pm_message_t state)if (netif_running (dev)) {netif_device_detach (dev);vortex_down (dev,1 ); +disable_irq (dev->irq); }pci_save_state (pdev);pci_enable_wake (pdev,pci_choose_state (pdev, state),0 ); -free_irq (dev->irq, dev);pci_disable_device (pdev);pci_set_power_state (pdev,pci_choose_state (pdev, state)); }@@ -833,18 +833,12 @@ static int vortex_resume(struct pci_dev *pdev)return err; }pci_set_master (pdev); -if (request_irq (dev->irq, vp->full_bus_master_rx ? - &boomerang_interrupt : &vortex_interrupt,IRQF_SHARED , dev->name, dev)) { -pr_warning ("%s: Could not reserve IRQ %d\n" , dev->name, dev->irq); -pci_disable_device (pdev); -return -EBUSY ; - }if (netif_running (dev)) { err =vortex_up (dev);if (err)return err; -else -netif_device_attach (dev); +enable_irq (dev->irq); +netif_device_attach (dev); } }return 0 ;
Quoted 6 lines · Rafael J. Wysocki
Quoted 2 lines · Anton Vorontsov
Following trace pops up if we try to suspend with 3c59x ethernet NIC brought down:
Patch looks good, but IMO it'd be a little effort to convert the driver to
dev_pm_opswhile you're at it (please see r8169 for a working example).
I'd like to avoid putting irrelevant stuff into bugfixes.
Apart from delights as bisecting and revert-only-offending-piece, keeping bugfixes small and self-sufficient helps to back-port the fixes to stable/distro kernels. Think of not so old kernels that don't have dev_pm_ops.
Converting this driver (and others that I'm interested in) to dev_pm_ops is on my todo list though.
Thanks,
Signature · 3 lines
Anton Vorontsov email: [email protected] irc://irc.freenode.net/bd2
Quoted 6 lines · Rafael J. Wysocki
Quoted 2 lines · Anton Vorontsov
Following trace pops up if we try to suspend with 3c59x ethernet NIC brought down:
Patch looks good, but IMO it'd be a little effort to convert the driver to
dev_pm_opswhile you're at it (please see r8169 for a working example).
I'd like to avoid putting irrelevant stuff into bugfixes.
Apart from delights as bisecting and revert-only-offending-piece, keeping bugfixes small and self-sufficient helps to back-port the fixes to stable/distro kernels. Think of not so old kernels that don't have dev_pm_ops.
Converting this driver (and others that I'm interested in) to dev_pm_ops is on my todo list though.
Thanks,
Signature · 3 lines
Anton Vorontsov email: [email protected] irc://irc.freenode.net/bd2
David Miller
maintainerFrom: Anton Vorontsov <[email protected]>
Date: Fri, 25 Sep 2009 01:30:39 +0400
Quoted 9 lines · Rafael J. Wysocki
Quoted 6 lines · Anton Vorontsov
Quoted 2 lines
Following trace pops up if we try to suspend with 3c59x ethernet NIC brought down:
Patch looks good, but IMO it'd be a little effort to convert the driver to
dev_pm_opswhile you're at it (please see r8169 for a working example).I'd like to avoid putting irrelevant stuff into bugfixes.
Agreed.
David Miller
maintainerFrom: Anton Vorontsov <[email protected]>
Date: Fri, 25 Sep 2009 01:30:39 +0400
Quoted 9 lines · Rafael J. Wysocki
Quoted 6 lines · Anton Vorontsov
Quoted 2 lines
Following trace pops up if we try to suspend with 3c59x ethernet NIC brought down:
Patch looks good, but IMO it'd be a little effort to convert the driver to
dev_pm_opswhile you're at it (please see r8169 for a working example).I'd like to avoid putting irrelevant stuff into bugfixes.
Agreed.
From: Anton Vorontsov <[email protected]>
Date: Thu, 24 Sep 2009 22:31:52 +0400
Quoted 2 lines
Following trace pops up if we try to suspend with 3c59x ethernet NIC brought down:
...
Quoted 1 line
Signed-off-by Anton Vorontsov <[email protected]>
Applied.
From: Anton Vorontsov <[email protected]>
Date: Thu, 24 Sep 2009 22:31:52 +0400
Quoted 2 lines
Following trace pops up if we try to suspend with 3c59x ethernet NIC brought down:
...
Quoted 1 line
Signed-off-by Anton Vorontsov <[email protected]>
Applied.
Quoted 7 lines · Anton Vorontsov
Though, there are few other issues with suspend/resume in this driver. The intention of calling
free_irq()insuspend()was to avoid any possible spurious interrupts (see commit5b039e681b8c5f30aac9cc04385"3c59x PM fixes"). But,- On resume, the driver was requesting IRQ just after
pci_set_master(), but beforevortex_up()(which actually resets 3c59x chips).
Shouldn't it be possible to reset the chip (or at least prevent it from generating spurious IRQs) during the early-resume phase?
Quoted 5 lines
- Issuing
free_irq()on a shared IRQ doesn't guarantee that a buggy HW won't trigger spurious interrupts in another driver that requested the same interrupt. So, if we want to protect from unexpected interrupts, then on suspend we should issuedisable_irq(), notfree_irq().
What if some other device shares the IRQ and still relies on receiving interrupts when this code runs? Won't disable_irq() mess up the other device?
Alan Stern
Quoted 7 lines · Anton Vorontsov
Though, there are few other issues with suspend/resume in this driver. The intention of calling
free_irq()insuspend()was to avoid any possible spurious interrupts (see commit5b039e681b8c5f30aac9cc04385"3c59x PM fixes"). But,- On resume, the driver was requesting IRQ just after
pci_set_master(), but beforevortex_up()(which actually resets 3c59x chips).
Shouldn't it be possible to reset the chip (or at least prevent it from generating spurious IRQs) during the early-resume phase?
Quoted 5 lines
- Issuing
free_irq()on a shared IRQ doesn't guarantee that a buggy HW won't trigger spurious interrupts in another driver that requested the same interrupt. So, if we want to protect from unexpected interrupts, then on suspend we should issuedisable_irq(), notfree_irq().
What if some other device shares the IRQ and still relies on receiving interrupts when this code runs? Won't disable_irq() mess up the other device?
Alan Stern
Quoted 19 lines · Alan Stern
Quoted 7 lines · Anton Vorontsov
Though, there are few other issues with suspend/resume in this driver. The intention of calling
free_irq()insuspend()was to avoid any possible spurious interrupts (see commit5b039e681b8c5f30aac9cc04385"3c59x PM fixes"). But,- On resume, the driver was requesting IRQ just after
pci_set_master(), but beforevortex_up()(which actually resets 3c59x chips).Shouldn't it be possible to reset the chip (or at least prevent it from generating spurious IRQs) during the early-resume phase?
Quoted 5 lines
- Issuing
free_irq()on a shared IRQ doesn't guarantee that a buggy HW won't trigger spurious interrupts in another driver that requested the same interrupt. So, if we want to protect from unexpected interrupts, then on suspend we should issuedisable_irq(), notfree_irq().
Quoted 3 lines
What if some other device shares the IRQ and still relies on receiving interrupts when this code runs? Won't
disable_irq()mess up the other device?
Ah, I overlooked the disable_irq()/enable_irq() part, which is not really necessary anyway.
Anton, have you tried without that?
Rafael
Quoted 19 lines · Alan Stern
Quoted 7 lines · Anton Vorontsov
Though, there are few other issues with suspend/resume in this driver. The intention of calling
free_irq()insuspend()was to avoid any possible spurious interrupts (see commit5b039e681b8c5f30aac9cc04385"3c59x PM fixes"). But,- On resume, the driver was requesting IRQ just after
pci_set_master(), but beforevortex_up()(which actually resets 3c59x chips).Shouldn't it be possible to reset the chip (or at least prevent it from generating spurious IRQs) during the early-resume phase?
Quoted 5 lines
- Issuing
free_irq()on a shared IRQ doesn't guarantee that a buggy HW won't trigger spurious interrupts in another driver that requested the same interrupt. So, if we want to protect from unexpected interrupts, then on suspend we should issuedisable_irq(), notfree_irq().
Quoted 3 lines
What if some other device shares the IRQ and still relies on receiving interrupts when this code runs? Won't
disable_irq()mess up the other device?
Ah, I overlooked the disable_irq()/enable_irq() part, which is not really necessary anyway.
Anton, have you tried without that?
Rafael
Quoted 8 lines · David Miller
From: Anton Vorontsov <[email protected]>
Date: Fri, 25 Sep 2009 01:30:39 +0400Quoted 5 lines · Rafael J. Wysocki
Quoted 4 lines · Anton Vorontsov
Quoted 2 lines
Following trace pops up if we try to suspend with 3c59x ethernet NIC brought down:
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Patch looks good, but IMO it'd be a little effort to convert the driver to
dev_pm_opswhile you're at it (please see r8169 for a working example).I'd like to avoid putting irrelevant stuff into bugfixes.
Agreed.
Well, the point is that all of the PCI core stuff the driver does is not necessary and should better be dropped along with the IRQ thing.
Best,
Rafael
Quoted 8 lines · David Miller
From: Anton Vorontsov <[email protected]>
Date: Fri, 25 Sep 2009 01:30:39 +0400Quoted 5 lines · Rafael J. Wysocki
Quoted 4 lines · Anton Vorontsov
Quoted 2 lines
Following trace pops up if we try to suspend with 3c59x ethernet NIC brought down:
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Patch looks good, but IMO it'd be a little effort to convert the driver to
dev_pm_opswhile you're at it (please see r8169 for a working example).I'd like to avoid putting irrelevant stuff into bugfixes.
Agreed.
Well, the point is that all of the PCI core stuff the driver does is not necessary and should better be dropped along with the IRQ thing.
Best,
Rafael
Quoted 20 lines · Rafael J. Wysocki
Quoted 19 lines · Alan Stern
Quoted 7 lines · Anton Vorontsov
Though, there are few other issues with suspend/resume in this driver. The intention of calling
free_irq()insuspend()was to avoid any possible spurious interrupts (see commit5b039e681b8c5f30aac9cc04385"3c59x PM fixes"). But,- On resume, the driver was requesting IRQ just after
pci_set_master(), but beforevortex_up()(which actually resets 3c59x chips).Shouldn't it be possible to reset the chip (or at least prevent it from generating spurious IRQs) during the early-resume phase?
Quoted 5 lines
- Issuing
free_irq()on a shared IRQ doesn't guarantee that a buggy HW won't trigger spurious interrupts in another driver that requested the same interrupt. So, if we want to protect from unexpected interrupts, then on suspend we should issuedisable_irq(), notfree_irq().
Quoted 6 lines
Quoted 3 lines
What if some other device shares the IRQ and still relies on receiving interrupts when this code runs? Won't
disable_irq()mess up the other device?Ah, I overlooked the disable_irq()/enable_irq() part, which is not really necessary anyway.
Well, it is necessary if 3c59x really throws spurious interrupts upon suspend (i.e. after pci_disable_device(pdev)). My first though was to just remove free/request_irq stuff, but then I could introduce a regression if 3c59x really throws unexpected IRQs and 3c59x was the only user of a PCI IRQ (in that case free_irq() would actually help).
Quoted 1 line
Anton, have you tried without that?
Yes, and there wasn't any issues for 3x59x I have. Alan raised a very good point, and converting to dev_pm_opsas as you've suggested would solve it in a nice way, since if we use the dev_pm_ops, PCI core will disable the device in _noirq suspend, after we quiesced the chip itself.
I'll send another patch that reworks PM stuff in the driver soon.
Thanks,
Signature · 3 lines
Anton Vorontsov email: [email protected] irc://irc.freenode.net/bd2
Quoted 20 lines · Rafael J. Wysocki
Quoted 19 lines · Alan Stern
Quoted 7 lines · Anton Vorontsov
Though, there are few other issues with suspend/resume in this driver. The intention of calling
free_irq()insuspend()was to avoid any possible spurious interrupts (see commit5b039e681b8c5f30aac9cc04385"3c59x PM fixes"). But,- On resume, the driver was requesting IRQ just after
pci_set_master(), but beforevortex_up()(which actually resets 3c59x chips).Shouldn't it be possible to reset the chip (or at least prevent it from generating spurious IRQs) during the early-resume phase?
Quoted 5 lines
- Issuing
free_irq()on a shared IRQ doesn't guarantee that a buggy HW won't trigger spurious interrupts in another driver that requested the same interrupt. So, if we want to protect from unexpected interrupts, then on suspend we should issuedisable_irq(), notfree_irq().
Quoted 6 lines
Quoted 3 lines
What if some other device shares the IRQ and still relies on receiving interrupts when this code runs? Won't
disable_irq()mess up the other device?Ah, I overlooked the disable_irq()/enable_irq() part, which is not really necessary anyway.
Well, it is necessary if 3c59x really throws spurious interrupts upon suspend (i.e. after pci_disable_device(pdev)). My first though was to just remove free/request_irq stuff, but then I could introduce a regression if 3c59x really throws unexpected IRQs and 3c59x was the only user of a PCI IRQ (in that case free_irq() would actually help).
Quoted 1 line
Anton, have you tried without that?
Yes, and there wasn't any issues for 3x59x I have. Alan raised a very good point, and converting to dev_pm_opsas as you've suggested would solve it in a nice way, since if we use the dev_pm_ops, PCI core will disable the device in _noirq suspend, after we quiesced the chip itself.
I'll send another patch that reworks PM stuff in the driver soon.
Thanks,
Signature · 3 lines
Anton Vorontsov email: [email protected] irc://irc.freenode.net/bd2
Quoted 35 lines · Anton Vorontsov
Quoted 20 lines · Rafael J. Wysocki
Quoted 19 lines · Alan Stern
Quoted 7 lines · Anton Vorontsov
Though, there are few other issues with suspend/resume in this driver. The intention of calling
free_irq()insuspend()was to avoid any possible spurious interrupts (see commit5b039e681b8c5f30aac9cc04385"3c59x PM fixes"). But,- On resume, the driver was requesting IRQ just after
pci_set_master(), but beforevortex_up()(which actually resets 3c59x chips).Shouldn't it be possible to reset the chip (or at least prevent it from generating spurious IRQs) during the early-resume phase?
Quoted 5 lines
- Issuing
free_irq()on a shared IRQ doesn't guarantee that a buggy HW won't trigger spurious interrupts in another driver that requested the same interrupt. So, if we want to protect from unexpected interrupts, then on suspend we should issuedisable_irq(), notfree_irq().Quoted 6 lines
Quoted 3 lines
What if some other device shares the IRQ and still relies on receiving interrupts when this code runs? Won't
disable_irq()mess up the other device?Ah, I overlooked the disable_irq()/enable_irq() part, which is not really necessary anyway.
Well, it is necessary if 3c59x really throws spurious interrupts upon suspend (i.e. after
pci_disable_device(pdev)). My first though was to just remove free/request_irq stuff, but then I could introduce a regression if 3c59x really throws unexpected IRQs and 3c59x was the only user of a PCI IRQ (in that casefree_irq()would actually help).
Quoted 7 lines
Quoted 1 line
Anton, have you tried without that?
Yes, and there wasn't any issues for 3x59x I have. Alan raised a very good point, and converting to
dev_pm_opsasas you've suggested would solve it in a nice way, since if we use thedev_pm_ops, PCI core will disable the device in_noirqsuspend, after we quiesced the chip itself.
That's exactly why I suggested to do that. :-)
Quoted 1 line
I'll send another patch that reworks PM stuff in the driver soon.
Thanks a lot for taking care of this!
Best,
Rafael
Quoted 35 lines · Anton Vorontsov
Quoted 20 lines · Rafael J. Wysocki
Quoted 19 lines · Alan Stern
Quoted 7 lines · Anton Vorontsov
Though, there are few other issues with suspend/resume in this driver. The intention of calling
free_irq()insuspend()was to avoid any possible spurious interrupts (see commit5b039e681b8c5f30aac9cc04385"3c59x PM fixes"). But,- On resume, the driver was requesting IRQ just after
pci_set_master(), but beforevortex_up()(which actually resets 3c59x chips).Shouldn't it be possible to reset the chip (or at least prevent it from generating spurious IRQs) during the early-resume phase?
Quoted 5 lines
- Issuing
free_irq()on a shared IRQ doesn't guarantee that a buggy HW won't trigger spurious interrupts in another driver that requested the same interrupt. So, if we want to protect from unexpected interrupts, then on suspend we should issuedisable_irq(), notfree_irq().Quoted 6 lines
Quoted 3 lines
What if some other device shares the IRQ and still relies on receiving interrupts when this code runs? Won't
disable_irq()mess up the other device?Ah, I overlooked the disable_irq()/enable_irq() part, which is not really necessary anyway.
Well, it is necessary if 3c59x really throws spurious interrupts upon suspend (i.e. after
pci_disable_device(pdev)). My first though was to just remove free/request_irq stuff, but then I could introduce a regression if 3c59x really throws unexpected IRQs and 3c59x was the only user of a PCI IRQ (in that casefree_irq()would actually help).
Quoted 7 lines
Quoted 1 line
Anton, have you tried without that?
Yes, and there wasn't any issues for 3x59x I have. Alan raised a very good point, and converting to
dev_pm_opsasas you've suggested would solve it in a nice way, since if we use thedev_pm_ops, PCI core will disable the device in_noirqsuspend, after we quiesced the chip itself.
That's exactly why I suggested to do that. :-)
Quoted 1 line
I'll send another patch that reworks PM stuff in the driver soon.
Thanks a lot for taking care of this!
Best,
Rafael