[Fwd: Re: Still ATAPICAM Lockup/Slowdown]

2006-03-30 Thread Adam Retter
Soren,

I am using FreeBSD 6-STABLE and have a problem with the atapicam driver,
I have been in contact with Thomas Quinot through the FreeBSD stable
mailing list (his name was on the code for atapicam), I have sent him
boot -v -h output as suggested, but he is not sure whats wrong - he has
suggested that I contact you as you are responsible for the ATA
sub-system.

Would you be so good as to take a look at the attached forwarded message
please?

Thanks Adam.
---BeginMessage---
Attached is my output from boot -h -v for my kernel with atapicam
compiled in.

Hope it sheds some light on the problem...



On Wed, 2006-03-22 at 13:10 +0100, Thomas Quinot wrote:
 * Adam Retter, 2006-03-22 :
 
  For booting with or without the apaicam module compiled into the Kernel?
 
 With ATAPI/CAM would be more useful.
 
 Thanks,
 Thomas.
 
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]

SMAP type=01 base= len=0009fc00
SMAP type=02 base=0009fc00 len=0400
SMAP type=02 base=000f len=0001
SMAP type=01 base=0010 len=7fef
SMAP type=03 base=7fff len=8000
SMAP type=04 base=7fff8000 len=8000
SMAP type=02 base=fec0 len=1000
SMAP type=02 base=fee0 len=1000
SMAP type=02 base=fff0 len=0010
Copyright (c) 1992-2006 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 6.1-PRERELEASE #10: Wed Mar 22 15:20:54 GMT 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/funkalicious
Preloaded elf kernel /boot/kernel/kernel at 0xc0c96000.
Preloaded elf module /boot/kernel/linprocfs.ko at 0xc0c96198.
Preloaded elf module /boot/kernel/linux.ko at 0xc0c96248.
Preloaded elf module /boot/modules/hpt374.ko at 0xc0c962f4.
Preloaded elf module /boot/modules/nvidia.ko at 0xc0c963a0.
Preloaded elf module /boot/modules/kqemu.ko at 0xc0c9644c.
Preloaded elf module /boot/kernel/acpi.ko at 0xc0c964f8.
Calibrating clock(s) ... i8254 clock: 1193409 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter i8254 frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 3245465384 Hz
CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3245.47-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf29  Stepping = 9
  
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C 
MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
  Features2=0x4400CNTX-ID,b14
  Hyperthreading: 2 logical CPUs
real memory  = 2147418112 (2047 MB)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x0010 - 0x003f, 3145728 bytes (768 pages)
0x01025000 - 0x7dbb7fff, 2092511232 bytes (510867 pages)
avail memory = 2092376064 (1995 MB)
MP Configuration Table version 1.4 found at 0xc00f6170
Table 'FACP' at 0x7fff0030
Table 'APIC' at 0x7fff00c0
MADT: Found table at 0x7fff00c0
APIC: Using the MADT enumerator.
MADT: Found CPU APIC ID 0 ACPI ID 1: enabled
MADT: Found CPU APIC ID 1 ACPI ID 2: enabled
ACPI APIC Table: AMIINT INTEL865
bios32: Found BIOS32 Service Directory header at 0xc00fdb50
bios32: Entry = 0xfdb60 (c00fdb60)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xf+0xdb81
pnpbios: Found PnP BIOS data at 0xc00f75e0
pnpbios: Entry = f:63cf  Rev = 1.0
Other BIOS signatures found:
APIC: CPU 0 has ACPI ID 1
MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec0
ioapic0: Routing external 8259A's - intpin 0
ioapic0: intpin 0 - ExtINT (edge, high)
ioapic0: intpin 1 - ISA IRQ 1 (edge, high)
ioapic0: intpin 2 - ISA IRQ 2 (edge, high)
ioapic0: intpin 3 - ISA IRQ 3 (edge, high)
ioapic0: intpin 4 - ISA IRQ 4 (edge, high)
ioapic0: intpin 5 - ISA IRQ 5 (edge, high)
ioapic0: intpin 6 - ISA IRQ 6 (edge, high)
ioapic0: intpin 7 - ISA IRQ 7 (edge, high)
ioapic0: intpin 8 - ISA IRQ 8 (edge, high)
ioapic0: intpin 9 - ISA IRQ 9 (edge, high)
ioapic0: intpin 10 - ISA IRQ 10 (edge, high)
ioapic0: intpin 11 - ISA IRQ 11 (edge, high)
ioapic0: intpin 12 - ISA IRQ 12 (edge, high)
ioapic0: intpin 13 - ISA IRQ 13 (edge, high)
ioapic0: intpin 14 - ISA IRQ 14 (edge, high)
ioapic0: intpin 15 - ISA IRQ 15 (edge, high)
ioapic0: intpin 16 - PCI IRQ 16 (level, low)
ioapic0: intpin 17 - PCI IRQ 17 (level, low)
ioapic0: intpin 18 - PCI IRQ 18 (level, low)
ioapic0: intpin 19 - PCI IRQ 19 (level, low)
ioapic0: intpin 20 - PCI IRQ 20 (level, low)
ioapic0: intpin 21 - PCI IRQ 21 (level, low)
ioapic0: intpin 22 - PCI IRQ 22 (level, low)
ioapic0: intpin 23 - PCI IRQ 23 (level, low)
MADT: Interrupt override: source 0, irq 2
ioapic0: Routing IRQ 0 - intpin 2
ioapic0: intpin 2 trigger: edge
ioapic0: intpin 2 polarity: high
MADT: Interrupt 

Re: [Fwd: Re: Still ATAPICAM Lockup/Slowdown]

2006-03-30 Thread Søren Schmidt
On Tor, 2006-03-30 at 11:09 +0100, Adam Retter wrote:
 Soren,
 
 I am using FreeBSD 6-STABLE and have a problem with the atapicam driver,
 I have been in contact with Thomas Quinot through the FreeBSD stable
 mailing list (his name was on the code for atapicam), I have sent him
 boot -v -h output as suggested, but he is not sure whats wrong - he has
 suggested that I contact you as you are responsible for the ATA
 sub-system.
 
 Would you be so good as to take a look at the attached forwarded message
 please?

Looks like atapicam does some operation that locks/hangs the device(s)
causing endless resets/retry loops..
Does the system boot correctly without atapicam in the kernel and are
the devices accessible through the plain ATA/ATAPI devices ?

-Søren

 
 Thanks Adam.
 email message attachment, Forwarded message - Re: Still ATAPICAM
 Lockup/Slowdown
   Forwarded Message 
  From: Adam Retter [EMAIL PROTECTED]
  To: Thomas Quinot [EMAIL PROTECTED]
  Cc: freebsd-stable@freebsd.org
  Subject: Re: Still ATAPICAM Lockup/Slowdown
  Date: Wed, 22 Mar 2006 21:49:26 +
  
  Attached is my output from boot -h -v for my kernel with atapicam
  compiled in.
  
  Hope it sheds some light on the problem...
  
  
  
  On Wed, 2006-03-22 at 13:10 +0100, Thomas Quinot wrote:
   * Adam Retter, 2006-03-22 :
   
For booting with or without the apaicam module compiled into the Kernel?
   
   With ATAPI/CAM would be more useful.
   
   Thanks,
   Thomas.
   
   ___
   freebsd-stable@freebsd.org mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-stable
   To unsubscribe, send any mail to [EMAIL PROTECTED]
  ___
  freebsd-stable@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-stable
  To unsubscribe, send any mail to [EMAIL PROTECTED]

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [Fwd: Re: Still ATAPICAM Lockup/Slowdown]

2006-03-30 Thread Adam Retter
On Thu, 2006-03-30 at 12:42 +0200, Søren Schmidt wrote:
 On Tor, 2006-03-30 at 11:09 +0100, Adam Retter wrote:
  Soren,
  
  I am using FreeBSD 6-STABLE and have a problem with the atapicam driver,
  I have been in contact with Thomas Quinot through the FreeBSD stable
  mailing list (his name was on the code for atapicam), I have sent him
  boot -v -h output as suggested, but he is not sure whats wrong - he has
  suggested that I contact you as you are responsible for the ATA
  sub-system.
  
  Would you be so good as to take a look at the attached forwarded message
  please?
 
 Looks like atapicam does some operation that locks/hangs the device(s)
 causing endless resets/retry loops..
 Does the system boot correctly without atapicam in the kernel and are
 the devices accessible through the plain ATA/ATAPI devices ?

Yes the system will boot fine without atapicam in the kernel and all
devices are accessible. I only need atapicam for CD/DVD writting.

Whats the next move, do I take what you have said back to Thomas Quinot?

 
 -Søren
 
  
  Thanks Adam.
  email message attachment, Forwarded message - Re: Still ATAPICAM
  Lockup/Slowdown
    Forwarded Message 
   From: Adam Retter [EMAIL PROTECTED]
   To: Thomas Quinot [EMAIL PROTECTED]
   Cc: freebsd-stable@freebsd.org
   Subject: Re: Still ATAPICAM Lockup/Slowdown
   Date: Wed, 22 Mar 2006 21:49:26 +
   
   Attached is my output from boot -h -v for my kernel with atapicam
   compiled in.
   
   Hope it sheds some light on the problem...
   
   
   
   On Wed, 2006-03-22 at 13:10 +0100, Thomas Quinot wrote:
* Adam Retter, 2006-03-22 :

 For booting with or without the apaicam module compiled into the 
 Kernel?

With ATAPI/CAM would be more useful.

Thanks,
Thomas.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
   ___
   freebsd-stable@freebsd.org mailing list
   http://lists.freebsd.org/mailman/listinfo/freebsd-stable
   To unsubscribe, send any mail to [EMAIL PROTECTED]
 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [Fwd: Re: Still ATAPICAM Lockup/Slowdown]

2006-03-30 Thread Søren Schmidt
On Tor, 2006-03-30 at 12:07 +0100, Adam Retter wrote:
 On Thu, 2006-03-30 at 12:42 +0200, Søren Schmidt wrote:
  On Tor, 2006-03-30 at 11:09 +0100, Adam Retter wrote:
   Soren,
   
   I am using FreeBSD 6-STABLE and have a problem with the atapicam driver,
   I have been in contact with Thomas Quinot through the FreeBSD stable
   mailing list (his name was on the code for atapicam), I have sent him
   boot -v -h output as suggested, but he is not sure whats wrong - he has
   suggested that I contact you as you are responsible for the ATA
   sub-system.
   
   Would you be so good as to take a look at the attached forwarded message
   please?
  
  Looks like atapicam does some operation that locks/hangs the device(s)
  causing endless resets/retry loops..
  Does the system boot correctly without atapicam in the kernel and are
  the devices accessible through the plain ATA/ATAPI devices ?
 
 Yes the system will boot fine without atapicam in the kernel and all
 devices are accessible. I only need atapicam for CD/DVD writting.

OK, so the problem is in atapicam interaction somehow.

 Whats the next move, do I take what you have said back to Thomas Quinot?

Yes, Thomas is the way to go. If the problem(s) needs something specific
to be changed/fixed in ATA then is the time to get back to me so it can
be incorporated. Of course I'll answer questions as to how interaction
with ATA should be handled along the way if need be, but I dont have the
time nor motivation to dig into how/why/if atapicam works...
 

-Søren  

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


[Fwd: Re: [Fwd: Re: Still ATAPICAM Lockup/Slowdown]]

2006-03-30 Thread Adam Retter
Thomas,

Have spoken to Soren, from my bootlog he believes that the problem is in
atapicam causing the system to lock up. He is happy to answer some
questions but doesnt have time to delve into atapicam himself.

Did you author atapicam, I have seen your name on the sourcecode, can
you help me further? Whats next?

Thanks Adam.
---BeginMessage---
On Tor, 2006-03-30 at 12:07 +0100, Adam Retter wrote:
 On Thu, 2006-03-30 at 12:42 +0200, Søren Schmidt wrote:
  On Tor, 2006-03-30 at 11:09 +0100, Adam Retter wrote:
   Soren,
   
   I am using FreeBSD 6-STABLE and have a problem with the atapicam driver,
   I have been in contact with Thomas Quinot through the FreeBSD stable
   mailing list (his name was on the code for atapicam), I have sent him
   boot -v -h output as suggested, but he is not sure whats wrong - he has
   suggested that I contact you as you are responsible for the ATA
   sub-system.
   
   Would you be so good as to take a look at the attached forwarded message
   please?
  
  Looks like atapicam does some operation that locks/hangs the device(s)
  causing endless resets/retry loops..
  Does the system boot correctly without atapicam in the kernel and are
  the devices accessible through the plain ATA/ATAPI devices ?
 
 Yes the system will boot fine without atapicam in the kernel and all
 devices are accessible. I only need atapicam for CD/DVD writting.

OK, so the problem is in atapicam interaction somehow.

 Whats the next move, do I take what you have said back to Thomas Quinot?

Yes, Thomas is the way to go. If the problem(s) needs something specific
to be changed/fixed in ATA then is the time to get back to me so it can
be incorporated. Of course I'll answer questions as to how interaction
with ATA should be handled along the way if need be, but I dont have the
time nor motivation to dig into how/why/if atapicam works...
 

-Søren  

---End Message---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: [Fwd: Re: [Fwd: Re: Still ATAPICAM Lockup/Slowdown]]

2006-03-30 Thread Thomas Quinot
* Adam Retter, 2006-03-30 :

 Have spoken to Soren, from my bootlog he believes that the problem is in
 atapicam causing the system to lock up. He is happy to answer some
 questions but doesnt have time to delve into atapicam himself.

OK, fair enough. Next question is, where are we spending time? It would
be useful if you could enable CAM traces so we see what is going on
there. Can you send me a boot -v log with the following options in your
kernel config:

 options CAMDEBUG
 options CAM_DEBUG_BUS=-1
 options CAM_DEBUG_TARGET=-1
 options CAM_DEBUG_LUN=-1
 options CAM_DEBUG_FLAGS=CAM_DEBUG_INFO|CAM_DEBUG_CDB|CAM_DEBUG_TRACE

(note, this well be a VERY verbose kerne).

Thomas.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]