Re: [kde-freebsd] problem hal - k3b ?
Zoran Kolic said the following on 26.04.2007 17:24: >> Along with update all my system and kernel to 6.2-STABLE on Fri, Apr 6, >> I have this error message in dmesg output: >> acd0: DVDR at ata1-master UDMA33 >> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 >> 0x01 >> And writing by k3b freeze ALL system, not only k3b. > > Beni confirmed that he could use command line and write a cd. That > post to mean that the problem is in k3b itself. Or not? > As for me, this is a atapi-cam problem, not k3b. (kern/112119) -- Best regards, Simon Phoenix (Phoenix Lab.) --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
Mark Linimon said the following on 26.04.2007 10:56: -- > I believe that this problem is now in kern/112119, which I am trying to > attract developer attention to. Yes, thanks, Mark. -- Best regards, Simon Phoenix (Phoenix Lab.) --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
Beni said the following on 25.04.2007 22:22: > On Tuesday 24 April 2007 16:49:28 Zoran Kolic wrote: >>> This problem appear in my system after updating system and ports on >>> April, 06. >>> K3b hangs either after loading splash screen or after eject wrote media >>> from device. >> Aside that new atapi-cam.c is proven to work, I'd like to know if command >> line works or not? K3b needs cdrtools in background. What if you make iso >> file using mkisofs and burn it with cdrecord? Along with update all my system and kernel to 6.2-STABLE on Fri, Apr 6, I have this error message in dmesg output: acd0: DVDR at ata1-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 0x01 And writing by k3b freeze ALL system, not only k3b. Old kernel with atapi-cam.c 1.42.2.2 revision (beginning of March) works fine without any error messages or freezes. K3B, cdrecord, hal and others works without any visible problems. -- Best regards, Simon Phoenix (Phoenix Lab.) --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [kde-freebsd] problem hal - k3b ?
>> haven't seen in happening on 5.5. >>>>> >>>> This should have been fixed a while ago by jylefort when he set the >>>> default device for ATAPI access to be the ATAPICAM device (as >>>> opposed to >>>> the ATA device). Assuming you have not undone that change, and are >>>> running the latest version of HAL, these panics should not be >>>> occurring. >>>> >>>> Even still, you're right that these are not HAL bugs, but rather an >>>> issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, >>>> and >>>> I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, >>>> and dvd-utils under the covers to do the actual device work. Not sure >>>> what k3b is using, but maybe it diddles something it shouldn't. >>>> >>>> Joe >>>> >> >> >> Could it all be related to this : >> http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034553.html >> and the "solution" from Shane Bell in >> http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034602.html >> : >> >> "I believe the culprit is somewhere in a recent MFC to atapi-cam.c >> (rev 1.42.2.3) reverting to rev 1.42.2.2 fixes both the k3b system >> hangs and "INQUIRY ILLEGAL REQUEST" errors here." >> > > > Most probably. I updated everything, including source and ports on April > 22nd and > the problem still exists. k3b hangs after loading splash screen and I > had to use > power button on my laptop to power down and up the system. > > I will try to revert rev 1.42.2.2 and see what will happen. > This problem appear in my system after updating system and ports on April, 06. K3b hangs either after loading splash screen or after eject wrote media from device. - -- Best regards, Simon Phoenix (Phoenix Lab.) - --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGLLT3hLjVFCVp0wsRCoOgAKDaxr6MetMDwjUBu4e69jSHx+FShwCg46rL dHdm6m1QDH3Xv3nfetI7bTY= =WVjD -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Andrei V. Lavreniyuk said the following on 20.04.2007 10:10: > Hi! > > >>> ipfw2 (+ipv6) initialized, divert enabled, rule-based forwarding enabled, >>> default to deny, logging limited to 100 packets/entry by default >>> ad0: 114473MB at ata0-master UDMA100 >>> acd0: DVDR at ata1-master UDMA33 >>> ad4: 152627MB at ata2-master SATA150 >>> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 >>> 0x01 >>> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 >>> 0x01 >>> >>> ^ ??? >>> >> >> i assume you are asking what those errors mean >> >> you most likely have a bad cdrom in there, or the drive has an error. >> try a different disk, and if that fails try another drive. > > >> Are you sure the ATAPI command used at that time is attempting to read >> disc information and not, say, try to get drive capabilities? I'm lead >> to believe that the DVD drive he has doesn't support a particular ATAPI >> function (long reads comes to mind). ASC 0x24 ASCQ 0x00 is "Illegal >> field in CDB" for most ATAPI operatons... > > > Kernel from March works normally... > I have the same problem on my 6.2-STABLE box: acd0: DVDR at ata1-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x48 0x00 0x01 And kernel from beginning of March works normally too. - -- Best regards, Simon Phoenix (Phoenix Lab.) - --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGLIkVhLjVFCVp0wsRCkKiAKCb3K/5u/60mYr3TJZW5r6BbFU72gCg6iMG Ckb0FZGCE5QkqGZeltPA1Vs= =vUJq -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Andrei V. Lavreniyuk said the following on 20.04.2007 12:27: > Hi! > >> On Thu, Apr 19, 2007 at 12:37:08PM -0700, pete wright wrote: >>>> ipfw2 (+ipv6) initialized, divert enabled, rule-based forwarding >>>> enabled, default to deny, logging limited to 100 packets/entry by >>>> default ad0: 114473MB at ata0-master >>>> UDMA100 acd0: DVDR at ata1-master >>>> UDMA33 ad4: 152627MB at ata2-master >>>> SATA150 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 >>>> sks=0x40 0x00 0x01 >>>> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 >>>> 0x01 >>>> >>>> ^ ??? >>> i assume you are asking what those errors mean >>> >>> you most likely have a bad cdrom in there, or the drive has an error. >>> try a different disk, and if that fails try another drive. >> Are you sure the ATAPI command used at that time is attempting to read >> disc information and not, say, try to get drive capabilities? I'm lead >> to believe that the DVD drive he has doesn't support a particular ATAPI >> function (long reads comes to mind). ASC 0x24 ASCQ 0x00 is "Illegal >> field in CDB" for most ATAPI operatons... > > > Adding to my report: > > > Test 1: > > To start k3b with a disk in the device of reading/record. A start takes a > place normally. > > Test 2: > > To start k3b without a disk in the device of reading/record. At a start the > k3b system hangs up and overloaded. > After writing a disk with k3b and eject media from device - system freeze without any response. - -- Best regards, Simon Phoenix (Phoenix Lab.) - --- KeyID: 0x2569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B - --- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGLItAhLjVFCVp0wsRCg12AJwKvkPdR/ByCCBDSIS9J6k/tcxI5wCglUPG UxuVBFv7UoZJcKEK9nhafBs= =XvA5 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Monitoring temperature with acpi (sysctls)
O. Hartmann wrote: > > I need to be able to get the cpu and fan information from my > > motherboard, however none of the monitoring utilities in the ports > > seems to support my motherboard (Supermicro PDSMi, Intel E7230 > > (Mukilteo) Chipset). On my older VIA based motherboards and some > > Nvidia, i can get this information using ACPI and the hw.acpi.thermal > > sysctl. This however is not available on this motherboard. Would this > > be a shortcoming of the motherboards ACPI implementation, or a lack of > > support by freebsd? > > > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > Similar problem to me here with a ASUS A8N32-SLI Deluxe. The older > versions of this motherboard type like A8N-SLI Deluxe and maybe A8N-SLI > Premium had thermal zones in ACPI output, but not the A8N32-SLI. No > temperature, no fanspeed, no thermal zones. ASUS P800 SE i865e chipset - problems too. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
