Bug 139252
Summary: | cdrecord fails with message: "Cannot allocate memory. Cannot get SCSI I/O buffer." | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Vaclav Bilek <vaclav.bilek> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED CANTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | bugs+fedora, pfrields |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-10-03 00:35:15 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
Vaclav Bilek
2004-11-14 14:21:06 UTC
hint: do not suid cdrecord!!! here are some links to others having the same problem and fixes. looks like its caused by a change in the kernel source. maybe it slipped thru fedora's Q&A process? scroll down about 1/2 way on both. http://kerneltrap.org/node/view/4022 http://kerneltrap.org/node/view/4026 If I understood it correctly, we have a cdrecord bug here. There are many people saying that we shouldn't set SUID on cdrecord, but without it, I cannot do anything without getting buffer underuns since my drive is too fast for its internal buffer (48X, 2MB). During cd burning, if the kernel is occupied and doesn't schedule cdrecord for more than a quarter of a second, i have a buffer underrun. So, running cdrecord without SUID is not an option. The fix seems reasonably simple, cdrecord should just drop root privileges on an earlier stage. I would say that this sould be a high-priority issue. After this kernel upgrade, I'm having to run cdrecord/k3b as root to avoid losing media. An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. This bug has been automatically closed as part of a mass update. It had been in NEEDINFO state since July 2005. If this bug still exists in current errata kernels, please reopen this bug. There are a large number of inactive bugs in the database, and this is the only way to purge them. Thank you. |