Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Le 2003-09-22, Dan Naumov écrivait : Speaking of failing, should I completely disregard the probe2:ata1 warnings during boot which you saw in the dmesg output I sent you ? Yes, these messages are perfectly inocuous, they mean that your CD drive does not provide serial number information. You can safely ignore them. -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
On Sat, 2003-09-20 at 22:53, Thomas Quinot wrote: Le 2003-09-20, Daniel Eischen écrivait : No, using latest sources, with or without atapicam, does not solve the problem. It still hangs. Please try the patch below, it should at least work around the problem. I have rebuilt world after you have committed the patch and now the system boots properly with ATAPICAM enabled in the kernel. It no longer hangs at boot. I tried mounting /dev/cd0 and suceeded. However, not everything seems to be perfect, take a look at the bottom of the included dmesg output: === Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Sun Sep 21 15:44:22 EEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/JAGO Preloaded elf kernel /boot/kernel/kernel at 0xc04b6000. Preloaded elf module /boot/kernel/linux.ko at 0xc04b61f4. Preloaded elf module /boot/kernel/acpi.ko at 0xc04b62a0. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) processor (1400.06-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x644 Stepping = 4 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 536805376 (511 MB) avail memory = 516239360 (492 MB) Pentium Pro MTRR support enabled VESA: v3.0, 65536k memory, flags:0x1, mode table:0xc03c82c2 (122) VESA: NVidia npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: GBTAWRDACPI on motherboard pcibios: BIOS version 2.10 Using $PIR table, 10 entries at 0xc00fddb0 acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 acpi_cpu0: CPU port 0x530-0x537 on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 7 INTD is routed to irq 5 pcib0: slot 7 INTD is routed to irq 5 pcib0: slot 10 INTA is routed to irq 11 pcib0: slot 14 INTA is routed to irq 11 agp0: AMD 761 host to AGP bridge port 0xc000-0xc003 mem 0xe400-0xe4000fff,0xe000-0xe1ff at device 0.0 on pci0 pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci_cfgintr: 1:5 INTA BIOS irq 10 pci1: display, VGA at device 5.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686B UDMA100 controller port 0xc400-0xc40f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] uhci0: VIA 83C572 USB controller port 0xc800-0xc81f irq 5 at device 7.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xcc00-0xcc1f irq 5 at device 7.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: serial bus, SMBus at device 7.4 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xe000-0xe0ff mem 0xe4001000-0xe40010ff irq 11 at device 10.0 on pci0 rl0: Ethernet address: 00:e0:7d:9f:be:31 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: Creative CT5880-C port 0xe400-0xe43f irq 11 at device 14.0 on pci0 pcm0: SigmaTel STAC9708/11 AC97 Codec atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: Option ROM at iomem 0xc-0xcefff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 1400061468 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0% GEOM: create disk ad0 dp=0xc40a3a70 ad0: 38182MB MAXTOR 4K040H2 [77578/16/63] at ata0-master UDMA100 GEOM: create disk ad1 dp=0xc40a3070 ad1: 16446MB ST317221A [33416/16/63] at ata0-slave UDMA66 acd0: CDRW LITE-ON COMBO LTC-48161H at ata1-master PIO4 (probe2:ata1:0:0:0): Recovered Sense (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe2:ata1:0:0:0): CAM Status: SCSI Status Error (probe2:ata1:0:0:0): SCSI Status: Check Condition (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 (probe2:ata1:0:0:0): Invalid field in CDB (probe2:ata1:0:0:0): Recovered Sense (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Le 2003-09-21, Dan Naumov écrivait : (probe2:ata1:0:0:0): Recovered Sense (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe2:ata1:0:0:0): CAM Status: SCSI Status Error (probe2:ata1:0:0:0): SCSI Status: Check Condition (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 (probe2:ata1:0:0:0): Invalid field in CDB That's fine, it just means your drive does not provide serial number information. -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Le 2003-09-21, Bryan Liesner écrivait : The patch doesn't take care of the hang for me. Does it change anything, or do you still see the 'REQUEST_SENSE recovered from missing interrupt'? Is your source tree up-to-date? Several fixes have been committed to both the ATA and the CAM subsystems recently, that address problems uncovered by the transition to ATAng. Did anyone read _any_ of my previous posts? Certainly so, since you already received answers to some of them. If you'd like to help speed up the resolution of the problems you see, maybe you could provide a backtrace at the point where your system hangs, and a log of boot -v output, with the CAMDEBUG and CAM_DEBUG_FLAGS=CAM_DEBUG_CCB options. Thomas. -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Le 2003-09-21, Shin-ichi Yoshimoto écrivait : I could not get a backtrace because infinite loop occured like this: Can't you drop into DDB at that point? Also, do you have up-to-date sources? Thomas. -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
On Sun, 21 Sep 2003, Thomas Quinot wrote: Le 2003-09-21, Bryan Liesner écrivait : The patch doesn't take care of the hang for me. Does it change anything, or do you still see the 'REQUEST_SENSE recovered from missing interrupt'? Is your source tree up-to-date? Several fixes have been committed to both the ATA and the CAM subsystems recently, that address problems uncovered by the transition to ATAng. It slightly changes things for me; I can eventually get the system to boot, but I get a boatload of infinite messages: Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): Recovered Sense Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): Recovered Sense Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): Recovered Sense ... and I have to reboot. This is with atapicam in the kernel. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Le 2003-09-21, Daniel Eischen écrivait : Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): Recovered Sense Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Um, strange, this is exactly what cam_periph.c rev. 1.53 was supposed to fix. Thomas. -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
On Sun, 21 Sep 2003, Thomas Quinot wrote: Le 2003-09-21, Daniel Eischen écrivait : Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): Recovered Sense Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Um, strange, this is exactly what cam_periph.c rev. 1.53 was supposed to fix. I guess I didn't get that update; I'm still using 1.52. I'll try another cvsup and update. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt, On Sun, 21 Sep 2003 18:57:43 +0200, Thomas Quinot wrote: Can't you drop into DDB at that point? Ok, I will try it. Also, do you have up-to-date sources? Yes, of course. I have recent ones. -- Shin-ichi YOSHIMOTO [EMAIL PROTECTED] http://diary.waishi.jp/~yosimoto/diary/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
On Sun, 21 Sep 2003, Thomas Quinot wrote: Le 2003-09-21, Bryan Liesner écrivait : The patch doesn't take care of the hang for me. Does it change anything, or do you still see the 'REQUEST_SENSE recovered from missing interrupt'? Is your source tree up-to-date? Several fixes have been committed to both the ATA and the CAM subsystems recently, that address problems uncovered by the transition to ATAng. Did anyone read _any_ of my previous posts? Certainly so, since you already received answers to some of them. Thanks, the hang problems are fixed now. In an earlier post, I pointed out the commit that seemed to break things. Immediately after a commit to ata-queue.c, the hangs started. I was incorrectly thinking that this commit caused the problem, instead of uncovering a problem that was hiding somewhere else. No one told me that I was barking up the wrong tree... -Bryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt, On Mon, 22 Sep 2003 03:01:28 +0900, Shin-ichi Yoshimoto wrote: Ok, I will try it. I tried to cvsup and make build installkernel. This kernel said: [snip] acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0% GEOM: create disk ad0 dp=0xc63f6570 ad0: 239372MB Maxtor 7Y250P0 [486344/16/63] at ata0-master UDMA100 acd0: DVDR MATSHITADVD-RAM LF-D521 at ata1-master UDMA66 (probe2:ata1:0:0:0): Recovered Sense (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe2:ata1:0:0:0): CAM Status: SCSI Status Error (probe2:ata1:0:0:0): SCSI Status: Check Condition (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 (probe2:ata1:0:0:0): Invalid field in CDB (probe2:ata1:0:0:0): Recovered Sense (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe2:ata1:0:0:0): CAM Status: SCSI Status Error (probe2:ata1:0:0:0): SCSI Status: Check Condition (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 (probe2:ata1:0:0:0): Invalid field in CDB SMP: AP CPU #1 Launched! cd0 at ata1 bus 0 target 0 lun 0 cd0: MATSHITA DVD-RAM LF-D521 A111 Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: cd present [2236704 x 2048 byte records] Mounting root from ufs:/dev/ad0s1a [end] Thanks, Thomas !! -- Shin-ichi YOSHIMOTO [EMAIL PROTECTED] http://diary.waishi.jp/~yosimoto/diary/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
On Sun, 21 Sep 2003, Daniel Eischen wrote: On Sun, 21 Sep 2003, Thomas Quinot wrote: Le 2003-09-21, Daniel Eischen écrivait : Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): Recovered Sense Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error Um, strange, this is exactly what cam_periph.c rev. 1.53 was supposed to fix. I guess I didn't get that update; I'm still using 1.52. I'll try another cvsup and update. That seemed to do the trick. No hangs and no infinite loopy messages. Thanks! -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Le 2003-09-21, Bryan Liesner écrivait : Thanks, the hang problems are fixed now. That's great news! No one told me that I was barking up the wrong tree... Ah, computers are fragile and playful things that always find creative and unexcepted ways of failing... :) Thomas. -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
On Mon, 2003-09-22 at 00:07, Thomas Quinot wrote: Le 2003-09-21, Bryan Liesner écrivait : Thanks, the hang problems are fixed now. That's great news! I am also very grateful for your fix. I now seem to be able to run -CURRENT on my home desktop without any issues whatsoever :) No one told me that I was barking up the wrong tree... Ah, computers are fragile and playful things that always find creative and unexcepted ways of failing... :) Speaking of failing, should I completely disregard the probe2:ata1 warnings during boot which you saw in the dmesg output I sent you ? Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me
It seems Daniel Eischen wrote: On a kernel built just a few hours ago, it hangs on boot right after: acd0: CDROM CD-532E-B at ata0-master PIO4 Get atapicam out and see if that helps.. -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me
Is atapicam a kernel config option? I can't seem to find it, and now since a cvsup up on the 17h, my plextor scsi cdrw locks my system and then reboots immediately after a burning program, (i've tried several) initializes the drive. It worked several weeks ago just fine. Any suggestions would be greatly appreciated. Thanks in advance. David R. Colyer On Saturday 20 September 2003 01:55 am, Soren Schmidt wrote: It seems Daniel Eischen wrote: On a kernel built just a few hours ago, it hangs on boot right after: acd0: CDROM CD-532E-B at ata0-master PIO4 Get atapicam out and see if that helps.. -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- ActivatorMail(tm) ver.00811031 Scanned for all viruses by www.activatormail.com intelligent anti-virus anti-spam service ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me
On Sat, 2003-09-20 at 12:32, David R. Colyer wrote: Is atapicam a kernel config option? [14:11]-[jago]-[~]: cat /usr/src/sys/i386/conf/JAGO | grep atapicam #device atapicam# BROKEN in -CURRENT !!! Hope this helps. Sincerely, Dan Naumov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me
On Sat, 20 Sep 2003, Soren Schmidt wrote: It seems Daniel Eischen wrote: On a kernel built just a few hours ago, it hangs on boot right after: acd0: CDROM CD-532E-B at ata0-master PIO4 Get atapicam out and see if that helps.. No, using latest sources, with or without atapicam, does not solve the problem. It still hangs. Full verbose boot log at: http://people.freebsd.org/~deischen/ata_hang.091903 -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me
It seems Daniel Eischen wrote: It seems Daniel Eischen wrote: On a kernel built just a few hours ago, it hangs on boot right after: acd0: CDROM CD-532E-B at ata0-master PIO4 Get atapicam out and see if that helps.. No, using latest sources, with or without atapicam, does not solve the problem. It still hangs. Full verbose boot log at: http://people.freebsd.org/~deischen/ata_hang.091903 No idea, I cant get it to fail here -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me
Daniel Eischen wrote: On Sat, 20 Sep 2003, Soren Schmidt wrote: It seems Daniel Eischen wrote: On a kernel built just a few hours ago, it hangs on boot right after: acd0: CDROM CD-532E-B at ata0-master PIO4 Get atapicam out and see if that helps.. No, using latest sources, with or without atapicam, does not solve the problem. It still hangs. As a datapoint, I experienced the hang with atapicam, too. Removing it helped in my case. Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: ATAng no good for me
On Sat, 20 Sep 2003, Lars Eggert wrote: Daniel Eischen wrote: On Sat, 20 Sep 2003, Soren Schmidt wrote: It seems Daniel Eischen wrote: On a kernel built just a few hours ago, it hangs on boot right after: acd0: CDROM CD-532E-B at ata0-master PIO4 Get atapicam out and see if that helps.. No, using latest sources, with or without atapicam, does not solve the problem. It still hangs. As a datapoint, I experienced the hang with atapicam, too. Removing it helped in my case. I experienced the hang with atapicam, and removing it helps. These symptoms happened immediately after the commit of ata-queue.c v1.5. Reverting back to 1.4 removed the issue altogether. I tried to get a verbose boot message using ata-queue 1.5 and 1.6, but got way, way too many spurious interrupt messages to have anything useful to share... -Bryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Le 2003-09-20, Daniel Eischen écrivait :
No, using latest sources, with or without atapicam, does
not solve the problem. It still hangs.
Please try the patch below, it should at least work around the problem.
http://people.freebsd.org/~deischen/ata_hang.091903
Interesting, the last 2 lines are :
ata0: spurious interrupt - status=0x50 error=0x00
acd0: WARNING - REQUEST_SENSE recovered from missing interrupt
so I'd suspect there is some race condition between the interrupt
and the REQUEST_SENSE command. Søren, shouldn't ata_interrupt lock the
channel before copying ch-running?
Thomas.
Index: atapi-cam.c
===
RCS file: /home/ncvs/src/sys/dev/ata/atapi-cam.c,v
retrieving revision 1.23
diff -u -r1.23 atapi-cam.c
--- atapi-cam.c 19 Sep 2003 16:25:44 - 1.23
+++ atapi-cam.c 20 Sep 2003 19:29:41 -
@@ -561,6 +561,7 @@
#endif
if (hcb_status != 0) {
csio-scsi_status = SCSI_STATUS_CHECK_COND;
+#if 0
if ((csio-ccb_h.flags CAM_DIS_AUTOSENSE) == 0) {
int8_t ccb[16] = { ATAPI_REQUEST_SENSE, 0, 0, 0,
sizeof(struct atapi_sense), 0, 0, 0, 0, 0, 0,
@@ -572,6 +573,7 @@
csio-ccb_h.status |= CAM_AUTOSNS_VALID;
}
}
+#endif
free_hcb_and_ccb_done(hcb, CAM_SCSI_STATUS_ERROR);
}
else {
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me
Le 2003-09-20, David R. Colyer écrivait : Is atapicam a kernel config option? It is a device (cf. man atapicam): you can enable it with device atapicam in your kernel config file. I can't seem to find it, and now since a cvsup up on the 17h, my plextor scsi cdrw locks my system and then reboots immediately after a burning program, (i've tried several) initializes the drive. It worked several weeks ago just fine. Any suggestions would be greatly appreciated. Thanks in advance. If it is an SCSI (SPI) drive, then ATAPI/CAM is irrelevant. The purpose of ATAPI/CAM is to allow access to ATAPI drives through the CAM framework. Thomas. -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt, On Sat, 20 Sep 2003 21:53:11 +0200, Thomas Quinot wrote: Please try the patch below, it should at least work around the problem. I tried your patch. acd0: WARNING - REQUEST_SENSE recovered from missing interrupt This message disappeared, but It still hang -- Shin-ichi YOSHIMOTO [EMAIL PROTECTED] http://diary.waishi.jp/~yosimoto/diary/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Le 2003-09-20, Shin-ichi Yoshimoto écrivait : acd0: WARNING - REQUEST_SENSE recovered from missing interrupt This message disappeared, but It still hang Can you get a backtrace at that point? -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt, On Sun, 21 Sep 2003 00:23:36 +0200, Thomas Quinot wrote: Can you get a backtrace at that point? I could not get a backtrace because infinite loop occured like this: [snip] ata0-master: pio=0x0c wdma=0x22 udma=0x46 cable=80pin ad0: setting UDMA100 on Intel ICH4 chip GEOM: create disk ad0 dp=0xc6202e70 ad0: Maxtor 7Y250P0/YAR41BW0 ATA-7 disk at ata0-master ad0: 239372MB (490234752 sectors), 486344 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 GEOM: new disk ad0 ata1-master: pio=0x0c wdma=0x22 udma=0x44 cable=80pin acd0: setting UDMA66 on Intel ICH4 chip acd0: MATSHITADVD-RAM LF-D521/A111 DVDR drive at ata1 as master acd0: read 5512KB/s (5512KB/s) write 2067KB/s (2067KB/s), 2048KB buffer, UDMA66 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc pcm0: measured ac97 link rate at 47995 Hz, will use 48000 Hz bus_explore done sbp_post_explore (sbp_cold=2) [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:490223412 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 250994386944 end 250994419199 GEOM: Configure ad0s1a, start 0 length 1073741824 end 1073741823 GEOM: Configure ad0s1b, start 1073741824 length 2147483648 end 3221225471 GEOM: Configure ad0s1c, start 0 length 250994386944 end 250994386943 GEOM: Configure ad0s1d, start 3221225472 length 107374182400 end 110595407871 GEOM: Configure ad0s1e, start 110595407872 length 107374182400 end 217969590271 GEOM: Configure ad0s1f, start 217969590272 length 33024796672 end 250994386943 (probe0:ata0:0:0:0): error 22 (probe0:ata0:0:0:0): Unretryable Error (probe1:ata0:0:1:0): error 22 (probe1:ata0:0:1:0): Unretryable Error (probe3:ata1:0:1:0): error 22 (probe3:ata1:0:1:0): Unretryable Error (probe4:sbp0:0:0:0): error 22 (probe4:sbp0:0:0:0): Unretryable Error (probe5:sbp0:0:1:0): error 22 (probe5:sbp0:0:1:0): Unretryable Error (probe6:sbp0:0:2:0): error 22 (probe6:sbp0:0:2:0): Unretryable Error (probe7:sbp0:0:3:0): error 22 (probe7:sbp0:0:3:0): Unretryable Error (probe8:sbp0:0:4:0): error 22 (probe8:sbp0:0:4:0): Unretryable Error (probe9:sbp0:0:5:0): error 22 (probe9:sbp0:0:5:0): Unretryable Error (probe10:sbp0:0:6:0): error 22 (probe10:sbp0:0:6:0): Unretryable Error (probe0:ata0:0:0:0): error 22 (probe0:ata0:0:0:0): Unretryable Error (probe1:ata0:0:1:0): error 22 (probe1:ata0:0:1:0): Unretryable Error (probe3:ata1:0:1:0): error 22 (probe3:ata1:0:1:0): Unretryable Error (probe2:ata1:0:0:0): Retrying Command (probe2:ata1:0:0:0): Retrying Command (probe2:ata1:0:0:0): Retrying Command (probe2:ata1:0:0:0): Retrying Command (probe2:ata1:0:0:0): Retrying Command (probe2:ata1:0:0:0): Retrying Command (probe2:ata1:0:0:0): Retrying Command (probe2:ata1:0:0:0): Retrying Command (probe2:ata1:0:0:0): Retrying Command ..repeat.. .. .. -- Shin-ichi YOSHIMOTO [EMAIL PROTECTED] http://diary.waishi.jp/~yosimoto/diary/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt
On Sat, 20 Sep 2003, Thomas Quinot wrote: Le 2003-09-20, Daniel Eischen écrivait : No, using latest sources, with or without atapicam, does not solve the problem. It still hangs. Please try the patch below, it should at least work around the problem. http://people.freebsd.org/~deischen/ata_hang.091903 Interesting, the last 2 lines are : ata0: spurious interrupt - status=0x50 error=0x00 acd0: WARNING - REQUEST_SENSE recovered from missing interrupt so I'd suspect there is some race condition between the interrupt and the REQUEST_SENSE command. Søren, shouldn't ata_interrupt lock the channel before copying ch-running? Thomas. Index: atapi-cam.c === The patch doesn't take care of the hang for me. Did anyone read _any_ of my previous posts? Bryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ATAng no good for me
ATA (atapicam also in kernel) doesn't seem to work after the changes in the last 24 hours or so. I have a SCSI system with one ATAPI CD-ROM drive, which gets probed on a good kernel as: ata0-slave: timeout waiting for interrupt ata0-slave: ATAPI identify failed acd0: CDROM CD-532E-B at ata0-master PIO4 Waiting 5 seconds for SCSI devices to settle da0 at ahc0 bus 0 target 0 lun 0 da0: S7Z0 Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) cd0 at ata0 bus 0 target 0 lun 0 cd0: TEAC CD-532E-B 1.0B Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present On a kernel built just a few hours ago, it hangs on boot right after: acd0: CDROM CD-532E-B at ata0-master PIO4 -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng no good for me
On Fri, Sep 19, 2003 at 07:09:03PM -0400, Daniel Eischen wrote: ATA (atapicam also in kernel) doesn't seem to work after the changes in the last 24 hours or so. I have a SCSI system with one ATAPI CD-ROM drive, which gets probed on a good kernel as: sos will probably ask for boot -v output. Kris pgp0.pgp Description: PGP signature
Re: ATAng no good for me
On Fri, 19 Sep 2003, Kris Kennaway wrote: On Fri, Sep 19, 2003 at 07:09:03PM -0400, Daniel Eischen wrote: ATA (atapicam also in kernel) doesn't seem to work after the changes in the last 24 hours or so. I have a SCSI system with one ATAPI CD-ROM drive, which gets probed on a good kernel as: sos will probably ask for boot -v output. http://people.freebsd.org/~deischen/ata_hang.091903 -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
