similar to: What could be causing unexpected reads to acd0?

Hi there, from time to time my PC panics when I insert an empty DVD or CD-R. The kernel locks up instantly after the DVD writer's tray is closed. It seems burning the first DVD isn't critical but inserting the second one seems susceptible. I use k3b as software, which polls the hardware while the tray is open, maybe it's something with hald. Don't know, just use this. I

Hello, I'm running 6.4-PRELEASE, last built on 2008-10-05 with /usr/src updated on the same day. I had a panic that looks to me very similiar to the one described here (hence the subject): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045405.html What caught my curiosity is the message: Unread portion of the kernel message buffer: acd0: WARNING - TEST_UNIT_READY read

Hi After my previous email about the SETFEATURES SET TRANSFER MODE timeout on (msgid 441AA807.5090100@wfeet.za.net , 17 March 14:18 GMT + 2 on freebsd-stable), I installed FreeBSD 6.1 BETA 4 and upgraded to a 6-STABLE kernel, running the box in 'safe' mode to do so. I now, however, get a slightly different error message: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout

I have committed a fix for the panic that happened with the da(4) or cd(4) drivers configured and INVARIANTS turned on. Let me know if there are any problems/comments/questions. Ken ----- Forwarded message from "Kenneth D. Merry" <ken@FreeBSD.org> ----- From: "Kenneth D. Merry" <ken@FreeBSD.org> Date: Tue, 9 Sep 2003 17:40:40 -0700 (PDT) To:

I've got a fix for the panic from the cd(4)/da(4) drivers when INVARIANTS is turned on in -stable. The fix is to create a task queue that runs in a thread context and use that to create the sysctl variables needed by cd(4) and da(4). The eventual fix will be to move the CAM transport layer probe code into a kernel thread. Anyway, these patches work for me, but if I could get some feedback

i cannot read or write any disk inserted in my acd0 <PIONEER DVD-RW DVR-111D/1.29> when this device in udma mode. kernel endlessly repeat that acd0: setting up DMA failed and I can access my data on dvd or cd only if I set atacontrol mode acd0 pio4 Does anybody have such a problem too? is there any ways to bring this device into udma mode again? dmesg: ... atapci1: <ATI IXP600

Is there anyone out there who has installed FreeBSD on the above Sony laptop ? Both ''cat filename > /dev/dsp0.0'' or ''vlc cdda:///dev/acd0@1 are OK. If I run ''cdcontrol -f /dev/acd0 play'', there is no sound. But the output of ''cdcontrol -f /dev/acd0 status audio'' is alright. (same behaviour for cd0 instead of acd0) And the output

On reboot, one out of 10 times, reboot (from hardware initialization) stops. Referring to this portion of the dmesg -v output, of a successful boot, where i have marked ">>>HERE<<<" is where the boot freezes on an unsuccessful boot. This is a constnat problem, on 6.2 as well as 6.3 unchanged. ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting

Hi, whenever I want to mount a DVD-RAM, I have a little problem because the corresponding device entry (eg cd0a, acd0a) does not exist. This will be created after trying to mount /dev/cd0 instead of /dev/cd0a, but I am not sure if this is the correct behaviour ;-) # ls /dev/acd* /dev/acd0 /dev/acd1 # mount /dev/acd0 /home/hk/mnt/ mount: /dev/acd0 on /usr/home/hk/mnt: incorrect super

Hello, while reading/writing dvd on 6-STABLE (can't remember on 7-STABLE right now), I'm getting the message buffer filled by errors. This is my dvd-rw $ sysctl dev.acd.0.%desc dev.acd.0.%desc: PIONEER DVD-RW DVR-109/1.58 attached to $ sysctl dev.atapci.1.%desc dev.atapci.1.%desc: VIA 8237A UDMA133 controller And the followings are some examples of the error:

Hello freebsd-stable, I've got FreeBSD 4.8R and CD-RW Asus CRW-4824a (master, ata1) but when boot process: acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting .. done It repeats 15 times, then all ok boot But I can't use acd0 Alexander Potapenko -- Best regards, Amber mailto:amber@arziz.uptel.net

Lately I have been trying to get Warcraft II BNE to work on my FreeBSD machine. I check the Application Database and Warcraft II BNE is supposed to work fine under Wine. I started out by updating my ports tree and installing Wine-20050524. I could not get the installer to run under that version, so I installed Wine-20041201. Under 20041201 I was able to install the game, but the game

I'm trying to install 4.8 from cdrom. I get to the kernel config menu, select the first option, install without configuring a kernel, and the boot process hangs accessing the cdrom. ad0 (the hard drive) is recognized fine. The cdrom does: acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done over and over. Finally I get to the screen "Probing devices, please

Hello, I have the following hardware configuration. Tyan 2466N motherboard, 1.03 BIOS, 2 Athlon-MP 1800+ CPUs, 512MB registered ECC DRAM, Onboard 3Com NIC (xl type) Radeon 8500 AGP video card Adaptec 3210S SCSI RAID controller Comtrol RocketPort 8 port PCI serial card I have started to experience some odd system lockups in the past couple months, and it seems to be getting worse. I particular,

Before reading below: I am considering a new install rather than an upgrade of our servers. However, now I just want to beat this problem. :) At 02:19 PM 7/8/2003 +0000, Phil Pennock wrote: >On 2003-07-08 at 14:09 +0000, Phil Pennock wrote: > > There was a fairly major update to the IDE disk device handlers which > > required new device nodes. Bringing in the new MAKEDEV script

I'm running: localhost(6.1-P)[21] uname -a FreeBSD localhost 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #19: Wed Mar 15 07:15:25 PST 2006 root@g1-18.catwhisker.org.:/common/S2/obj/usr/src/sys/LAPTOP_30W i386 localhost(6.1-P)[22] I figured I'd grab a copy of the recent 6.1-BETA4 (disc1) ISO to try it out & hand it out to folks.... It seems to have worked, but I got a bit of a whine

Hi, I am having trouble using my dvd drive in KDE, as it wont mount, using dvd, cd, cdrw. all I get is the error message saying: Could not mount device. The reported error was: cd9660: /dev/acd0: Invalid argument Has anyone got a solution for this? Thanks, Brian

Greetings, I have been looking for infomation on how Samba handle rude disconnects. Here is the test.... #1 - Login to Samba hosted Domain #2 - Turn off the computer; Turn the computer back on #3 - goto to step #1 and repeat Now at some point my login should fail...right? If I try the above steps, after the 5-6th power off I get 'XXXX' Domain not found! Questions.... Does Samba kill

On Thu, 2006-03-16 at 01:01 +0000, Guy Helmer <ghelmer@palisadesys.com> wrote: > David Wolfskill wrote: > > I'm running: > > > > localhost(6.1-P)[21] uname -a > > FreeBSD localhost 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #19: > Wed Mar 15 07:15:25 PST 2006 >

Hi, I am having some trouble with parked calls timing out. In features.conf: [general] parkext => 800 ; What extension to dial to park parkpos => 801-820 ; What extensions to park calls on context=parkedcalls parkingtime=120 After the Park timesout it calls the phone that the call was parked from. If the phone is BUSY the call just get dropped. (Call waiting