Bug 85981

Summary:	schedule_work() missing in 2.4.20-2.24
Product:	[Retired] Red Hat Linux	Reporter:	Vasile Gaburici <gaburici>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	mkanat
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-30 15:40:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vasile Gaburici 2003-03-11 21:28:11 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030120

Description of problem:
ALSA from CVS fails to insmod snd.o due to unresolved symbol schedule_work.

It turns out that schedule_work() implementation is missing from
kernel 2.4.20-2.24 from phoebe, athough the prototype is in workqueue.h...

BTW, is there no way to report bugs for phoebe? Bugzilla only lets me choose
phoebe for queries, but not for bug submission...


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


How reproducible:
Always

Steps to Reproduce:
1. get latest alsa from cvs
2. compile
3. try to insmod snd


Additional info:

Comment 1 Max Kanat-Alexander 2003-11-11 07:12:42 UTC

I thought I should note that ALSA has to do a specific workaround in
order to compile on Red Hat, because of this.

They check versions, which means that ALSA refuses to compile on new
versions of Red Hat until a new version of ALSA is released, unless
you hack the build scripts.

Is this going to be resolved, or is it somehow NOTABUG?

-M

Comment 2 Bugzilla owner 2004-09-30 15:40:38 UTC

Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/