Bug 534161 - Unloading sym53c8xx driver causes ___free_dma_mem_cluster warnings
Summary: Unloading sym53c8xx driver causes ___free_dma_mem_cluster warnings
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-10 18:58 UTC by Wolfgang Denk
Modified: 2012-06-04 14:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-04 14:45:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Log file with Fedora 13 - 2.6.33.5-112.fc13.i686.PAE (14.16 KB, text/plain)
2010-06-29 08:45 UTC, Wolfgang Denk
no flags Details

Description Wolfgang Denk 2009-11-10 18:58:14 UTC
Description of problem:

When unloading the sym53c8xx driver a number of kernel warning messages are printed.

Version-Release number of selected component (if applicable):

2.6.30.8-64.fc11.i686.PAE

How reproducible:

Always.

Steps to Reproduce:
1. modprobe  sym53c8xx
2. rmmod sym53c8xx
3.
  
Actual results:

see attached log file

Expected results:

no such warnings

Additional info:

Comment 1 Bug Zapper 2010-04-28 11:12:37 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2010-06-28 15:26:10 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Wolfgang Denk 2010-06-29 08:45:43 UTC
Created attachment 427610 [details]
Log file with Fedora 13 - 2.6.33.5-112.fc13.i686.PAE

The problem has always been present since I reported it, and is still present even in the most recent kernel versions.

Comment 4 Wolfgang Denk 2010-06-29 08:46:58 UTC
Update for Fedora 13 - problem is NOT solved.

Comment 5 Stanislaw Gruszka 2010-10-03 13:37:31 UTC
I looked at the code (gash, the sym53c8xx_2 is one big mess).

First in __sym_mfree_dma we take spin_lock_irqsave(&sym53c8xx_lock, flags) then after some complex logic call dma_free_coherent(). Since interrupts are disabled WARN_ON(irqs_disabled()) print a message and call trace.

I don't know how to solve it. One solution is move dma_free_coherent after spin_lock_irqrestore in __sys_mfree_dma, but as told logic is quite complex. Second is remove WARN_ON from dma_free_coherent. I have no idea why this warning is there - free_something functions should be callable from any context.

Anyway this is not fixed mainline. Wolfgang, please report problem to proper upstream maintainers. If we get upstream solution, we can put it in fedora then.

Comment 6 Wolfgang Denk 2010-11-16 20:06:25 UTC
I reported it. Seems there is no intention to fix it, though. Please see
http://article.gmane.org/gmane.linux.scsi/63662

Comment 7 Bug Zapper 2011-06-02 17:29:19 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.