atapicam and dvd-r(w)

From: Sascha Holzleiter <sascha_at_root-login.org>
Date: Sun, 21 Sep 2003 23:51:15 +0200
Hi,

i still have problems with atapicam and atang, while booting with
atapicam i get these messages:

 Sep 21 23:30:17 dreamland kernel: atapci0: <Intel ICH4 UDMA100
 controller> port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 10 at device
 31.1 on pci0
 Sep 21 23:30:17 dreamland kernel: ata0: at 0x1f0 irq 14 on atapci0
 Sep 21 23:30:17 dreamland kernel: ata0: [MPSAFE]
 Sep 21 23:30:17 dreamland kernel: ata1: at 0x170 irq 15 on atapci0
 Sep 21 23:30:17 dreamland kernel: ata1: [MPSAFE]
 ...
 Sep 21 23:03:58 dreamland kernel: GEOM: create disk ad0 dp=0xc5bda970
 Sep 21 23:03:58 dreamland kernel: ad0: 78533MB <IC35L080AVVA07-0>
 [159560/16/63] at ata0-master UDMA100
 Sep 21 23:03:58 dreamland kernel: GEOM: create disk ad1 dp=0xc5bda870
 Sep 21 23:03:58 dreamland kernel: ad1: 58644MB <IC35L060AVVA07-0>
 [119150/16/63] at ata0-slave UDMA100
 Sep 21 23:03:58 dreamland kernel: acd0: DVDR <PIONEER DVD-RW DVR-106D>
 at ata1-master UDMA33
 Sep 21 23:03:58 dreamland kernel: Waiting 8 seconds for SCSI devices to
 settle
 (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: Command byte 1 bit 0 is
 invalid
 (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: Command byte 1 bit 0 is
 invalid
 Mounting root from ufs:/dev/ad0s2a 
 (cd2:ata1:0:0:0): Recovered Sense
 (cd2:ata1:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
 (cd2:ata1:0:0:0): CAM Status: SCSI Status Error
 (cd2:ata1:0:0:0): SCSI Status: Check Condition
 (cd2:ata1:0:0:0): NOT READY asc:3a,0
 (cd2:ata1:0:0:0): Medium not present
 Sep 21 23:03:58 dreamland kernel: cd2 at ata1 bus 0 target 0 lun 0
 Sep 21 23:03:58 dreamland kernel: cd2: <PIONEER DVD-RW  DVR-106D 1.06>
 Removable CD-ROM SCSI-0 device
 Sep 21 23:03:58 dreamland kernel: cd2: 33.000MB/s transfers
 Sep 21 23:03:58 dreamland kernel: cd2: cd present [1 x 2048 byte
 records]
 Sep 21 23:03:58 dreamland kernel: Mounting root from ufs:/dev/ad0s2a
 Sep 21 23:03:58 dreamland kernel: cd0 at ahc0 bus 0 target 2 lun 0
 Sep 21 23:03:58 dreamland kernel: cd0: <PIONEER DVD-ROM DVD-303 1.10>
 Removable CD-ROM SCSI-2 device
 Sep 21 23:03:58 dreamland kernel: cd0: 20.000MB/s transfers (20.000MHz,
 offset 8)
 Sep 21 23:03:58 dreamland kernel: cd0: Attempt to query device size
 failed: NOT READY, Medium not present
 Sep 21 23:03:58 dreamland kernel: WARNING: / was not properly
 dismounted
 Sep 21 23:03:58 dreamland kernel: cd1 at ahc0 bus 0 target 3 lun 0
 Sep 21 23:03:58 dreamland kernel: cd1: <PLEXTOR CD-ROM PX-40TS 1.05>
 Removable CD-ROM SCSI-2 device
 Sep 21 23:03:58 dreamland kernel: cd1: 20.000MB/s transfers (20.000MHz,
 offset 15)
 Sep 21 23:03:58 dreamland kernel: cd1: Attempt to query device size
 failed: NOT READY, Medium not present - tray closed
 
When trying to burn a disk with cdrecord i get the following panic:

  panic: mutex vm object not owned at /usr/src/sys/vm/vm_page.c:761
  
Is this related to the above failures or some issue with cdrecord?

The kernel is current:

  FreeBSD dreamland.chief.home 5.1-CURRENT FreeBSD 5.1-CURRENT #6: Sun
  Sep 21 23:20:12 CEST 2003
  
I also have a backtrace of this but it seems to show nothing I could
make any sense of:

  can not access 0xc04835a0, invalid address (c04835a0)
  can not access 0xc04835a0, invalid address (c04835a0)
  panic messages:
  ---
  dmesg: kvm_read: invalid address (c04de0bc)
  ---
  can not access 0xc048129c, invalid address (c048129c)
  can not access 0xc048129c, invalid address (c048129c)
  can not access 0xc04835e0, invalid address (c04835e0)
  can not access 0xc04835e0, invalid address (c04835e0)
  #0  0x00000000 in ?? ()
 
 
Regards,
  Sascha 
Received on Sun Sep 21 2003 - 12:51:22 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:23 UTC