Re: HEADS UP! ATAng committed

2003-09-04 Thread Lars Eggert
Hi,

Lars Eggert wrote:

Soren Schmidt wrote:

ATAng has just been committed. You need to make world after this update
as atacontrol etc needs to pick up the changes.
Funky boot messages, but the system is usable after. This is with 
today's -current:

atapci0: Intel ICH2 UDMA100 controller port 0xffa0-0xffaf at device 
31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
...
ad0: 78167MB Maxtor 4D080H4 [158816/16/63] at ata0-master UDMA100
ata1-slave: WARNING - ATA_IDENTIFY recovered from missing interrupt
acd0: CDRW PHILIPS DVD+RW-D28 at ata1-master UDMA33
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: WARNING - SET_MULTI recovered from missing interrupt
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: 3584MB p p p p p p p p p p p p p p p p p p p p [585/112/112] at 
ata1-slave PIO0
ad3: WARNING - READ_MUL recovered from missing interrupt
ad3: WARNING - READ_MUL recovered from missing interrupt
ad3: WARNING - READ_MUL recovered from missing interrupt

Note that I have no ad3, only ad0 and acd0, which are masters on the 
primary and secondary channels as probed above.
with today's -current (as opposed to 8/27, which was running when I sent 
the previous email), the system panics on boot:

GEOM: create disk ad0 dp=0xc63b9e70
ad0: 78167MB Maxtor 4D080H4 [158816/16/63] at ata0-master UDMA100
acd0: CDRW PHILIPS DVD+RW-D28 at ata1-master UDMA33
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: WARNING - SETFEATURES recovered from missing interrupt
GEOM: create disk ad3 dp=0xc64d6170
Fatal trap 18: integer divide fault while in kernel mode
cpuid = 0; lapic.id = 
instruction pointer = 0x8:0xc03067d0
stack pointer   = 0x10:0xc070fc1c
frame pointer   = 0x10:0xc070fcac
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 0 (swapper)
kernel: type 18 trap, code=0
Stopped at  __qdivrem+0x3e: divl%ecx,%eax
db
Lars
--
Lars Eggert [EMAIL PROTECTED]   USC Information Sciences Institute


smime.p7s
Description: S/MIME Cryptographic Signature


Re: HEADS UP! ATAng committed

2003-08-30 Thread Glenn Johnson
On Fri, Aug 29, 2003 at 06:41:17PM +0200, Thomas Quinot wrote:

 Le 2003-08-29, Glenn Johnson écrivait :

  When I have atapicam enabled in my kernel config (-current, as of
  Aug 28, 2003; 11:00 PM CDT), my system locks up when trying to load
  nautilus.  Nautilus loads fine after removing the atapicam option.
  Atapicam worked fine prior to ATAng.

 Strange. No messages on the system console?

Well, I did a fresh cvsup, re-enabled the atapicam bits in my kernel
config, rebuilt/reinstalled world and kernel.  I rebooted and started a
Gnome session and starting nautilus did *not* cause the system to hang.
The problem just went away.  I did see that there were some commits to
some ATA files so maybe that was it.

Thanks.

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


Re: HEADS UP! ATAng committed

2003-08-30 Thread Glenn Johnson
On Fri, Aug 29, 2003 at 11:02:13PM -0500, wrote:

 On Fri, Aug 29, 2003 at 06:41:17PM +0200, Thomas Quinot wrote:

  Le 2003-08-29, Glenn Johnson écrivait :
 
   When I have atapicam enabled in my kernel config (-current, as of
   Aug 28, 2003; 11:00 PM CDT), my system locks up when trying to
   load nautilus.  Nautilus loads fine after removing the atapicam
   option.  Atapicam worked fine prior to ATAng.
 
  Strange. No messages on the system console?

 Well, I did a fresh cvsup, re-enabled the atapicam bits in my kernel
 config, rebuilt/reinstalled world and kernel.  I rebooted and started
 a Gnome session and starting nautilus did *not* cause the system to
 hang.  The problem just went away.  I did see that there were some
 commits to some ATA files so maybe that was it.

I guess I wrote that too soon, it just locked up again.  This time
though, the machine rebooted after about 10 seconds so I could not get
to another machine to see if I could poke around.

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


Re: HEADS UP! ATAng committed

2003-08-30 Thread Glenn Johnson
On Fri, Aug 29, 2003 at 11:56:57PM -0500, Glenn Johnson wrote:

 On Fri, Aug 29, 2003 at 11:02:13PM -0500, wrote:

  On Fri, Aug 29, 2003 at 06:41:17PM +0200, Thomas Quinot wrote:
 
   Le 2003-08-29, Glenn Johnson écrivait :
  
When I have atapicam enabled in my kernel config (-current,
as of Aug 28, 2003; 11:00 PM CDT), my system locks up when
trying to load nautilus.  Nautilus loads fine after removing the
atapicam option.  Atapicam worked fine prior to ATAng.
  
   Strange. No messages on the system console?
 
  Well, I did a fresh cvsup, re-enabled the atapicam bits in my kernel
  config, rebuilt/reinstalled world and kernel.  I rebooted and
  started a Gnome session and starting nautilus did *not* cause the
  system to hang.  The problem just went away.  I did see that there
  were some commits to some ATA files so maybe that was it.

 I guess I wrote that too soon, it just locked up again.  This time
 though, the machine rebooted after about 10 seconds so I could not get
 to another machine to see if I could poke around.

Another data point: If I start a non-gnome session, and then launch
nautilus, it does not crash the system.  However, when I start a gnome
session, the machine crashes when nautilus loads.  If I take atapicam
out of my kernel config, rebuild/reinstall the kernel, I do not get any
crashes at all.  Why it worked a couple of times earlier this evening I
do not know.

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


Re: HEADS UP! ATAng committed

2003-08-30 Thread Thomas Quinot
Le 2003-08-30, Glenn Johnson écrivait :

 I guess I wrote that too soon, it just locked up again.  This time
 though, the machine rebooted after about 10 seconds so I could not get
 to another machine to see if I could poke around.

If it rebooted, then maybe it panic'd. Do you have a kernel core dump?

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


Re: HEADS UP! ATAng committed

2003-08-29 Thread Glenn Johnson
On Thu, Aug 28, 2003 at 12:39:59AM +0200, Thomas Quinot wrote:

 OK, trivial one. Thanks to all who contributed feedback on this issue.
 
 Thomas.
 
 Index: atapi-cam.c
 ===
 RCS file: /home/ncvs/src/sys/dev/ata/atapi-cam.c,v
 retrieving revision 1.20

...snip...

When I have atapicam enabled in my kernel config (-current, as of
Aug 28, 2003; 11:00 PM CDT), my system locks up when trying to load
nautilus.  Nautilus loads fine after removing the atapicam option.
Atapicam worked fine prior to ATAng.

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


Re: HEADS UP! ATAng committed

2003-08-29 Thread Thomas Quinot
Le 2003-08-29, Glenn Johnson écrivait :

 When I have atapicam enabled in my kernel config (-current, as of
 Aug 28, 2003; 11:00 PM CDT), my system locks up when trying to load
 nautilus.  Nautilus loads fine after removing the atapicam option.
 Atapicam worked fine prior to ATAng.

Strange. No messages on the system console?

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


Re: HEADS UP! ATAng committed

2003-08-29 Thread Glenn Johnson
On Fri, Aug 29, 2003 at 06:41:17PM +0200, Thomas Quinot wrote:

 Le 2003-08-29, Glenn Johnson écrivait :

  When I have atapicam enabled in my kernel config (-current, as of
  Aug 28, 2003; 11:00 PM CDT), my system locks up when trying to load
  nautilus.  Nautilus loads fine after removing the atapicam option.
  Atapicam worked fine prior to ATAng.

 Strange. No messages on the system console?

I do not really know.  Since the keyboard locks up I can not switch to a
console.  There was nothing written to the log file that I remember but
I should check that again tonight when I get home.  I will also try to
ssh in from another machine and see if the network is still up.

-- 
Glenn Johnson
USDA, ARS, SRRC  Phone: (504) 286-4252
New Orleans, LA 70124   e-mail: [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADS UP! ATAng committed

2003-08-29 Thread Thomas Quinot
Le 2003-08-29, Glenn Johnson écrivait :

 console.  There was nothing written to the log file that I remember but
 I should check that again tonight when I get home.  I will also try to
 ssh in from another machine and see if the network is still up.
 
Yes. A serial console could also perhaps provide some messages.

Thomas.

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


Re: HEADS UP! ATAng committed

2003-08-29 Thread Joe Marcus Clarke
On Fri, 2003-08-29 at 15:53, Glenn Johnson wrote:
 On Fri, Aug 29, 2003 at 06:41:17PM +0200, Thomas Quinot wrote:
 
  Le 2003-08-29, Glenn Johnson écrivait :
 
   When I have atapicam enabled in my kernel config (-current, as of
   Aug 28, 2003; 11:00 PM CDT), my system locks up when trying to load
   nautilus.  Nautilus loads fine after removing the atapicam option.
   Atapicam worked fine prior to ATAng.
 
  Strange. No messages on the system console?
 
 I do not really know.  Since the keyboard locks up I can not switch to a
 console.  There was nothing written to the log file that I remember but
 I should check that again tonight when I get home.  I will also try to
 ssh in from another machine and see if the network is still up.

If you're testing GNOME 2.3, this might be related to
nautilus-cd-burner.  If so, please try rebuilding it so that it can
compile with the new code.

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc


signature.asc
Description: This is a digitally signed message part


Re: HEADS UP! ATAng committed

2003-08-29 Thread Glenn Johnson
On Fri, Aug 29, 2003 at 04:17:33PM -0400, Joe Marcus Clarke wrote:

 On Fri, 2003-08-29 at 15:53, Glenn Johnson wrote:

  On Fri, Aug 29, 2003 at 06:41:17PM +0200, Thomas Quinot wrote:
 
   Le 2003-08-29, Glenn Johnson écrivait :
  
When I have atapicam enabled in my kernel config (-current,
as of Aug 28, 2003; 11:00 PM CDT), my system locks up when
trying to load nautilus.  Nautilus loads fine after removing the
atapicam option.  Atapicam worked fine prior to ATAng.
  
   Strange. No messages on the system console?
 
  I do not really know.  Since the keyboard locks up I can not switch
  to a console.  There was nothing written to the log file that I
  remember but I should check that again tonight when I get home.  I
  will also try to ssh in from another machine and see if the network
  is still up.

 If you're testing GNOME 2.3, this might be related to
 nautilus-cd-burner.  If so, please try rebuilding it so that it can
 compile with the new code.

No, I am not testing Gnome 2.3, I am using Gnome 2.2.2 on that machine.


-- 
Glenn Johnson
USDA, ARS, SRRC  Phone: (504) 286-4252
New Orleans, LA 70124   e-mail: [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADS UP! ATAng committed

2003-08-27 Thread Lars Eggert
Soren Schmidt wrote:
ATAng has just been committed. You need to make world after this update
as atacontrol etc needs to pick up the changes.
Funky boot messages, but the system is usable after. This is with 
today's -current:

atapci0: Intel ICH2 UDMA100 controller port 0xffa0-0xffaf at device 
31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
...
ad0: 78167MB Maxtor 4D080H4 [158816/16/63] at ata0-master UDMA100
ata1-slave: WARNING - ATA_IDENTIFY recovered from missing interrupt
acd0: CDRW PHILIPS DVD+RW-D28 at ata1-master UDMA33
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: WARNING - SET_MULTI recovered from missing interrupt
ad3: WARNING - SETFEATURES recovered from missing interrupt
ad3: 3584MB p p p p p p p p p p p p p p p p p p p p [585/112/112] at 
ata1-slave PIO0
ad3: WARNING - READ_MUL recovered from missing interrupt
ad3: WARNING - READ_MUL recovered from missing interrupt
ad3: WARNING - READ_MUL recovered from missing interrupt

Note that I have no ad3, only ad0 and acd0, which are masters on the 
primary and secondary channels as probed above.

Lars
--
Lars Eggert [EMAIL PROTECTED]   USC Information Sciences Institute


smime.p7s
Description: S/MIME Cryptographic Signature


Re: HEADS UP! ATAng committed

2003-08-27 Thread Thomas Quinot
Le 2003-08-25, Matt écrivait :

 Fatal trap 12: page fault while in kernel mode
 fault virtual address = 0x0
 fault code = supervisor write, page not present
 instruction pointer = 0x8:0xc015e59e
 stack pointer = 0x10:0xd717bac0
 frame pointer = 0x10:0xd717bacc
 code segment = base 0x0, limit 0xf, type 0x1b
  = DPL 0, pres 1, def32 1, gran 1
 processor eflags = interrupt enabled, resume, IOPL = 0
 current process = 18 (swi3: cambio)
 kernel: type 12 trap, code=0
 Stopped at  free_hcb+0x2e: movl %eax,0(%edx)

OK, trivial one. Thanks to all who contributed feedback on this issue.

Thomas.

Index: atapi-cam.c
===
RCS file: /home/ncvs/src/sys/dev/ata/atapi-cam.c,v
retrieving revision 1.20
diff -u -r1.20 atapi-cam.c
--- atapi-cam.c 24 Aug 2003 17:48:05 -  1.20
+++ atapi-cam.c 27 Aug 2003 22:35:56 -
@@ -465,9 +465,10 @@
if ((ccb_h-flags  CAM_DIR_MASK) == CAM_DIR_IN  (len  1)) {
/* ATA always transfers an even number of bytes */
if (!(buf = hcb-dxfer_alloc = malloc(++len, M_ATACAM,
- M_NOWAIT | M_ZERO)))
+ M_NOWAIT | M_ZERO))) {
printf(cannot allocate ATAPI/CAM buffer\n);
goto action_oom;
+   }
}
request-device = dev;
request-driver = hcb;

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


Re: HEADS UP! ATAng committed

2003-08-26 Thread Kenneth D. Merry
On Mon, Aug 25, 2003 at 19:25:42 +0200, Thomas Quinot wrote:
 Le 2003-08-25, Matt ?crivait :
 
  db trace
  free_hcb(c40f1040,c03c7e40,101,c41d5800,c1528130) at free_hcb+0x2e
  atapi_action(c40f1440,c41d5800,c0132b33,c41db000,c41d5800) at
  atapi_action+ox56c
 
 OK, so that presumably means we're going through action_oom, and so you
 should have had one of the following messages on the console:
 
 printf(cannot allocate ATAPI/CAM hcb\n);
 printf(cannot allocate ATAPI/CAM request\n);
 printf(cannot allocate ATAPI/CAM buffer\n);
 
 It would be interesting to know which, if any, of these messages you
 saw. Also, please try whether the following patch improves the
 situation:

I had the following panic (-current from today (Monday), in free_hcb()), and
didn't see either of those messages:

Timecounters tick every 10.000 msec
acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0%
acd0: DVDR SONY DVD RW DRU-500A at ata0-master UDMA33
Waiting 2 seconds for SCSI devices to settle


Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 
fault virtual address   = 0x0
fault code  = supervisor write, page not present
instruction pointer = 0x8:0xc019106e
stack pointer   = 0x10:0xe5e83a24
frame pointer   = 0x10:0xe5e83a30
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 19 (swi3: cambio)
kernel: type 12 trap, code=0
Stopped at  free_hcb+0x2e:  movl%eax,0(%edx)
db trace
free_hcb(cbd59000,c0407fe0,101,cb9d1c00,c048f880) at free_hcb+0x2e
atapi_action(cb9a2740,cb9d1c00,cb97ac18,cb97ac00,cb99cc30) at atapi_action+0xb53
xpt_run_dev_sendq(cb9a27c0,cb97ac18,5,c083ad14,c042c164) at xpt_run_dev_sendq+0x1fe
xpt_action(cb9d1c00,4,c013b720,20,cbd50600) at xpt_action+0x38c
probestart(cbd4ea80,cb9d1c00,5,c0138cb6,cb951780) at probestart+0x32f
xpt_run_dev_allocq(cb9a27c0,cb97ac08,5) at xpt_run_dev_allocq+0x1ca
xpt_schedule(cbd4ea80,5,c47aec14,c47af260,c0487720) at xpt_schedule+0x2ae
probedone(cbd4ea80,cb9d1c00,c03dfd02,0,c046f6ac) at probedone+0x55c
camisr(c046f6ac,0,c03dfcf9,215,c47aeb58) at camisr+0x2a3
ithread_loop(c47a5800,e5e83d48,c03dfb67,314,e77fffbf) at ithread_loop+0x182
fork_exit(c023b360,c47a5800,e5e83d48) at fork_exit+0xc0
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xe5e83d7c, ebp = 0 ---


 Index: atapi-cam.c
 ===
 RCS file: /home/ncvs/src/sys/dev/ata/atapi-cam.c,v
 retrieving revision 1.20
 diff -u -r1.20 atapi-cam.c
 --- atapi-cam.c   24 Aug 2003 17:48:05 -  1.20
 +++ atapi-cam.c   25 Aug 2003 17:24:44 -
 @@ -59,7 +59,7 @@
  int  lun;
  union ccb*ccb;
  int  flags;
 -#define DOING_AUTOSENSE 1
 +#define QUEUED   0x0001;

I had to remove the semicolon at the end of the line above in order for
things to compile.

Now with the patch, the probe hangs here:

acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0%
acd0: DVDR SONY DVD RW DRU-500A at ata0-master UDMA33
Waiting 2 seconds for SCSI devices to settle
(probe0:ata0:0:0:0): out of memory, freezing queue.

Breaking into the debugger doesn't show anything useful:

db trace
siointr1(c4788800,0,c03f4d5d,695,e5e39ce8) at siointr1+0xd5
siointr(c4788800) at siointr+0x35
Xfastintr4() at Xfastintr4+0xba
--- interrupt, eip = 0xc03980e4, esp = 0xe5e39ce8, ebp = 0xe5e39ce8 ---
cpu_idle(c0483b40,2,c03dfcf2,5f,1be) at cpu_idle+0x24
idle_proc(0,e5e39d48,c03dfba7,314,bb14d6e) at idle_proc+0x3c
fork_exit(c023a7a0,0,e5e39d48) at fork_exit+0xc0
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xe5e39d7c, ebp = 0 ---

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


Re: HEADS UP! ATAng committed

2003-08-26 Thread Wiktor Niesiobedzki
On Sun, Aug 24, 2003 at 11:27:05AM +0200, Soren Schmidt wrote:
 
 ATAng has just been committed. You need to make world after this update
 as atacontrol etc needs to pick up the changes.
 
After updating to ATAng my DVD drive isn't detected. I get following message:
ata1-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED

Before it was:
DVD-ROM LG DVD-ROM DRD-8120B at ata1-slave UDMA33

Is there anything I can do, to provide you more specific information, please
contact me.


Cheers,

Wiktor Niesiobedzki

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


Re: HEADS UP! ATAng committed

2003-08-26 Thread Jason Stone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


 ATAng has just been committed. You need to make world after this update
 as atacontrol etc needs to pick up the changes.

Just want to report initial success with this - my smp machine previously
would not recognize my offboard pci-based ide devices with an smp kernel,
but now it's working fine.  I'm getting some unpleasant-looking messages
when the drives get probed at boot-time, though:


FreeBSD 5.1-CURRENT #0: Sun Aug 24 06:20:33 PDT 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/JKERN
[...]
atapci1: Promise PDC20262 UDMA66 controller port 
0xef00-0xef3f,0xefa8-0xefab,0xefa0-0xefa7,0xefac-0xefaf,0xefe0-0xefe7 mem 
0xfebc-0xfebd irq 11 at device 13.0 on pci0
ata2: at 0xefe0 on atapci1
ata3: at 0xefa0 on atapci1
[...]
ata2-master: WARNING - ATA_IDENTIFY recovered from missing interrupt
ad0: WARNING - SETFEATURES recovered from missing interrupt
ad0: WARNING - SETFEATURES recovered from missing interrupt
ad0: WARNING - SET_MULTI recovered from missing interrupt
ad0: WARNING - SETFEATURES recovered from missing interrupt
ad0: 57241MB ST360021A [116301/16/63] at ata2-master UDMA66
ata3-master: WARNING - ATA_IDENTIFY recovered from missing interrupt
ad0: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - SETFEATURES recovered from missing interrupt
ad0: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - SETFEATURES recovered from missing interrupt
ad0: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - SET_MULTI recovered from missing interrupt
ad0: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - SETFEATURES recovered from missing interrupt
ad1: 25965MB Maxtor 92720U8 [52755/16/63] at ata3-master UDMA66
ad0: WARNING - READ_DMA recovered from missing interrupt
ad0: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - READ_DMA recovered from missing interrupt
ad0: WARNING - READ_DMA recovered from missing interrupt
ad0: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - WRITE_DMA recovered from missing interrupt
ad0: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - WRITE_DMA recovered from missing interrupt
ad1: WARNING - READ_DMA recovered from missing interrupt
ad1: WARNING - WRITE_DMA recovered from missing interrupt
ad0: WARNING - READ_DMA recovered from missing interrupt
ad0: WARNING - WRITE_DMA recovered from missing interrupt
ad1: WARNING - READ_DMA recovered from missing interrupt

etc.

Haven't seen any more of these messages since boot-time, and the
everything seems to be working fine, but I still wonder what that's all
about?


 -Jason

 --
 Freud himself was a bit of a cold fish, and one cannot avoid the suspicion
 that he was insufficiently fondled when he was an infant.
-- Ashley Montagu
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (FreeBSD)
Comment: See https://private.idealab.com/public/jason/jason.gpg

iD8DBQE/S1BXswXMWWtptckRAlEJAKCZ8VGpH70D6zdzPQiI4Dgc0yfjGQCgg9dm
/DsP4A5uLYEFBy7ZqiZID8k=
=STWA
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADS UP! ATAng committed

2003-08-26 Thread Greg J.
My DVD drive is no longer working.. anyway around this?

Before ATAng:
acd1: DVD-ROM HL-DT-STDVD-ROM GDR8160B at ata1-slave PIO4

After ATAng:
ata1-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR
error=4ABORTED
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADS UP! ATAng committed

2003-08-26 Thread Shizuka Kudo
Soren,

My machine panic when pax a directory to the software raid. The same step works just 
fine for an
older kernel before the ATAng commit. After this panic, the raid is broken and has to 
be created
manually. The controller is a Highpoint 370 with bios 2.34 with 2 IDE IBM DTLA-307030 
attached to
the two UDMA100 interfaces. I have been able to dump core and backtrace the panic as 
shown below.
Is it a unique problem on me? Thanks for any advice...

panic: initiate_write_inodeblock_ufs2: already started
panic: from debugger
Uptime: 2m45s
Dumping 511 MB
 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 
384 400 416
432 448 464 480 496
---
Reading symbols from
/usr/obj/usr/src/sys/SHIZUKA/modules/usr/src/sys/modules/acpi/acpi.ko.debug...done.
Loaded symbols for 
/usr/obj/usr/src/sys/SHIZUKA/modules/usr/src/sys/modules/acpi/acpi.ko.debug
Reading symbols from /boot/kernel/logo_saver.ko...done.
Loaded symbols for /boot/kernel/logo_saver.ko
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) where
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1  0xc0254380 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
#2  0xc0254768 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3  0xc014ba82 in db_panic () at /usr/src/sys/ddb/db_command.c:450
#4  0xc014b9e2 in db_command (last_cmdp=0xc046c120, cmd_table=0x0,
aux_cmd_tablep=0xc0422284, aux_cmd_tablep_end=0xc0422288)
at /usr/src/sys/ddb/db_command.c:346
#5  0xc014bb25 in db_command_loop () at /usr/src/sys/ddb/db_command.c:472
#6  0xc014eb45 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_trap.c:73
#7  0xc03b5d4c in kdb_trap (type=3, code=0, regs=0xdc39ea3c)
at /usr/src/sys/i386/i386/db_interface.c:171
#8  0xc03c75aa in trap (frame=
  {tf_fs = -831782888, tf_es = 16, tf_ds = 16, tf_edi = 1, tf_esi = -1069454141, 
tf_ebp =
-600184184, tf_isp = -600184216, tf_ebx = 0, tf_edx = 0, tf_ecx = -1068875680, tf_eax 
= 18,
tf_trapno = 3, tf_err = 0, tf_eip = -1069850620, tf_cs = 8, tf_eflags = 642, tf_esp = 
-1069434333,
tf_ss = -1069505986})
at /usr/src/sys/i386/i386/trap.c:577
#9  0xc03b76f8 in calltrap () at {standard input}:102
#10 0xc02546a5 in panic (
fmt=0xc0416cc3 initiate_write_inodeblock_ufs2: already started)
at /usr/src/sys/kern/kern_shutdown.c:534
#11 0xc035e2e6 in initiate_write_inodeblock_ufs2 (inodedep=0xc42b6800, bp=0x0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:3893
---Type return to continue, or q return to quit---
#12 0xc035d46d in softdep_disk_io_initiation (bp=0xce641830)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:3459
#13 0xc0214954 in spec_xstrategy (vp=0xc41dfdb0, bp=0xce641830)
at /usr/src/sys/sys/buf.h:413
#14 0xc0214aab in spec_specstrategy (ap=0x0)
at /usr/src/sys/fs/specfs/spec_vnops.c:529
#15 0xc0213c18 in spec_vnoperate (ap=0x0)
at /usr/src/sys/fs/specfs/spec_vnops.c:122
#16 0xc029da9b in bwrite (bp=0xce641830) at vnode_if.h:1141
#17 0xc029ffd9 in vfs_bio_awrite (bp=0xce641830)
at /usr/src/sys/kern/vfs_bio.c:1709
#18 0xc02a0e16 in flushbufqueues (flushdeps=0)
at /usr/src/sys/kern/vfs_bio.c:2171
#19 0xc02a097c in buf_daemon () at /usr/src/sys/kern/vfs_bio.c:2072
#20 0xc023d091 in fork_exit (callout=0xc02a0840 buf_daemon, arg=0x0,
frame=0x0) at /usr/src/sys/kern/kern_fork.c:796


__
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADS UP! ATAng committed

2003-08-26 Thread Bruce Evans
On Tue, 26 Aug 2003, Wiktor Niesiobedzki wrote:

 On Sun, Aug 24, 2003 at 11:27:05AM +0200, Soren Schmidt wrote:
 
  ATAng has just been committed. You need to make world after this update
  as atacontrol etc needs to pick up the changes.
 
 After updating to ATAng my DVD drive isn't detected. I get following message:
 ata1-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED

Try backing out rev.1.5 of ata-lowlevel.c.  It clobbers the signature of
all 3 atapi drives on one of my systems here.  This results the atapi
drives being further probed as ata drives and the probe soon fails with
the above error.

Output from ATAog for these atapi drives:

Aug 27 00:16:50 gamplex kernel: afd0: 96MB IOMEGA ZIP 100 ATAPI [96/64/32] at 
ata0-slave PIO0
Aug 27 00:16:50 gamplex kernel: acd0: CD-RW RICOH CD-RW MP7320A at ata1-slave UDMA33
Aug 27 00:16:50 gamplex kernel: acd1: CDROM ATAPI 44X CDROM at ata2-slave PIO4
Aug 27 00:16:50 gamplex kernel: cd1 at ata2 bus 0 target 1 lun 0
Aug 27 00:16:50 gamplex kernel: cd1: ATAPI 44X CDROM 3.40 Removable CD-ROM SCSI-0 
device
Aug 27 00:16:50 gamplex kernel: cd1: 16.000MB/s transfers
Aug 27 00:16:50 gamplex kernel: cd1: cd present [317714 x 2048 byte records]
Aug 27 00:16:50 gamplex kernel: cd0 at ata1 bus 0 target 1 lun 0
Aug 27 00:16:50 gamplex kernel: cd0: RICOH CD-RW MP7320A bp13 Removable CD-ROM 
SCSI-0 device
Aug 27 00:16:50 gamplex kernel: cd0: 33.000MB/s transfers
Aug 27 00:16:50 gamplex kernel: cd0: cd present [320930 x 2048 byte records]
Aug 27 00:16:50 gamplex kernel: da0 at ata0 bus 0 target 1 lun 0
Aug 27 00:16:50 gamplex kernel: da0: IOMEGA ZIP 100 14.A Removable Direct Access 
SCSI-0 device
Aug 27 00:16:50 gamplex kernel: da0: 3.300MB/s transfers
Aug 27 00:16:50 gamplex kernel: da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C)

ata0 and ata1 are on a BX chipset, and ata2 and ata3 are on an old highpoint
chipset.  ata0 has a working ata drive on the master.  ata1 has a broken
ata drive on the master (I keep it for debugging ata; it probes correctly
but recently became unreadable on block 0).  ata2 has no master.  ata3 has
no drives.

Breaking the probe of the atapi drives avoids some other bugs:
- a panic for atapicam (already reported).
- spurious interrupts on ata2.  -current somehow recovers after reporting
  about 10 such interrupts, but my -mycurrent spins endlessly on them.  I
  suspect Giant locking problems.

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


Re: HEADS UP! ATAng committed

2003-08-26 Thread Greg J.
On Wed, 27 Aug 2003 03:10:27 +1000 (EST)
Bruce Evans [EMAIL PROTECTED] wrote:

 On Tue, 26 Aug 2003, Wiktor Niesiobedzki wrote:
 
  On Sun, Aug 24, 2003 at 11:27:05AM +0200, Soren Schmidt wrote:
  
   ATAng has just been committed. You need to make world after this
   update as atacontrol etc needs to pick up the changes.
  
  After updating to ATAng my DVD drive isn't detected. I get following
  message: ata1-slave: FAILURE - ATA_IDENTIFY
  status=51READY,DSC,ERROR error=4ABORTED
 
 Try backing out rev.1.5 of ata-lowlevel.c.  It clobbers the signature
 of all 3 atapi drives on one of my systems here.  This results the
 atapi drives being further probed as ata drives and the probe soon
 fails with the above error.

Confirmed.. I went back to 'src/sys/dev/ata/ata-lowlevel.c,v 1.4' and
all is well again.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADS UP! ATAng committed

2003-08-25 Thread Thomas Quinot
Le 2003-08-24, Matt écrivait :

 This did work perfectly with the old ATA, but the new ATA panic's. I have
 found that it is due to having device atapicam for the SCSI emulation. If I

I'll need a backtrace please.

Thanks,
Thomas.

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


Re: HEADS UP! ATAng committed

2003-08-25 Thread HATANOU Tomomi
 Coolness. Judging from the CVS log, it also gets ATA out under Giant? 

Yes it does.

I've noticed that, in ata-raid.c:ar_rebuid(), Giant is
locked and never unlocked.  Is it ok?

% ident ata-raid.c
ata-raid.c:
 $FreeBSD: src/sys/dev/ata/ata-raid.c,v 1.67 2003/08/24 17:48:05 obrien Exp $
% grep Giant ata-raid.c
mtx_lock(Giant);
%

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


Re: HEADS UP! ATAng committed

2003-08-25 Thread Soren Schmidt
It seems HATANOU Tomomi wrote:
  Coolness. Judging from the CVS log, it also gets ATA out under Giant? 
 
 Yes it does.
 
 I've noticed that, in ata-raid.c:ar_rebuid(), Giant is
 locked and never unlocked.  Is it ok?

It is only locked in the rebuild thread, its not needed anymore actually.

Anyhow ata-raid is about to change radically to support the new chips
out there and to get rid of all the really bad/ugly diskdriver strategy 
calls which abuses bio structs and what not.

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


Re: HEADS UP! ATAng committed

2003-08-25 Thread Matt
Thomas Quinot [EMAIL PROTECTED] wrote:

 I'll need a backtrace please.
 
 Thanks,
 Thomas.

I recompiled the kernel with full debugging again. Unfortunatly all I can get
out of it is the ddb prompt trace as the system does not get far enough into
boot to configure swap and a dumpdevice etc so I have no core dump.

Apologies if I have typo'd anything in here but I transcribed this by hand off
the screen. If there is anything else you need from that prompt let me know
and I shall reboot with the new kernel again and get it.

Matt.

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc015e59e
stack pointer = 0x10:0xd717bac0
frame pointer = 0x10:0xd717bacc
code segment = base 0x0, limit 0xf, type 0x1b
 = DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 18 (swi3: cambio)
kernel: type 12 trap, code=0
Stopped at  free_hcb+0x2e: movl %eax,0(%edx)

db trace
free_hcb(c40f1040,c03c7e40,101,c41d5800,c1528130) at free_hcb+0x2e
atapi_action(c40f1440,c41d5800,c0132b33,c41db000,c41d5800) at
atapi_action+ox56c
xpt_run_dev_sendq(c40f1840,c41db018,5,ff,c013749d) at xpt_run_dev_sendq+0x192
xpt_action(c41d5800,4,c01350e0,20,c41ea300) at xpt_action+0x238
probestart(c41d3100,c41d5800,5,c41db030,c41db000) at probestart+0x2cb
xpt_run_dev_allocq(c40f1840,c41db008,5,c1505710,c41d5800) at
xpt_run_dev_allocq+0xab
xpt_schedule(c41d3100,5,c1527df8,c1528130,d717bc34) at xpt_schedule+0xca
probedone(c41d3100,c41d5800,c03a3b7d,0,c04074c0) at probedone+0x4df
camisr(c04074c0,0,c03a3b7d,215,c1527d3c) at camisr+0x23f
ithread_loop(c151e980,d717bd48,c03a39ef,314,38e86776) at ithread_loop+0x182
fork_exit(c0204e30,c151e980,d717bd48) at fork_exit+0xcf
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xd717bd7c, ebp = 0 ---
db 

--
email: [EMAIL PROTECTED] - web: http://xtaz.co.uk/
Hardware, n.: The parts of a computer system that can be kicked.


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


Re: HEADS UP! ATAng committed

2003-08-25 Thread Dimitry Andric
On 2003-08-24 at 11:27:05 Soren Schmidt wrote:

 ATAng has just been committed. You need to make world after this update
 as atacontrol etc needs to pick up the changes.

Building went fine here on my VMware test box, but the new kernel spat
out a warning (which wasn't fatal, as it doesn't panic):

ad0: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED
ad0: 16384MB VMware Virtual IDE Hard Drive [33288/16/63] at ata0-master UDMA33

See also attached dmesgs from before and after the ATAng update. This
is with VMware 4.01.5289 on Windows, btw.

Next I'm going to try this nice update on my crucial router box... see
you later, hopefully. ;)
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: Sat Aug 23 21:18:33 CEST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/VFBSD5
Preloaded elf kernel /boot/kernel.old/kernel at 0xc03f4000.
Preloaded elf module /boot/kernel.old/snd_es137x.ko at 0xc03f427c.
Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc03f4330.
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) XP 1700+ (1478.01-MHz 686-class CPU)
  Origin = AuthenticAMD  Id = 0x662  Stepping = 2
  
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
  AMD Features=0xc048MP,AMIE,DSP,3DNow!
real memory  = 268435456 (256 MB)
avail memory = 256348160 (244 MB)
npx0: math processor on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 9 entries at 0xc00fdf30
pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
pci_cfgintr: 0:7 INTD BIOS irq 9
pci_cfgintr: 0:16 INTA BIOS irq 11
pci_cfgintr: 0:17 INTA BIOS irq 10
agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xf800-0xfbff at device 
0.0 on pci0
pcib1: PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
isab0: PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel PIIX4 UDMA33 controller port 0x1050-0x105f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: serial bus, USB at device 7.2 (no driver attached)
pci0: bridge, PCI-unknown at device 7.3 (no driver attached)
pci0: display, VGA at device 15.0 (no driver attached)
lnc0: PCNet/PCI Ethernet adapter port 0x10c0-0x10df irq 11 at device 16.0 on pci0
lnc0: Attaching PCNet/PCI Ethernet adapter
lnc0: PCnet-PCI address 00:0c:29:79:75:a1
pcm0: AudioPCI ES1371-A port 0x1080-0x10bf irq 10 at device 17.0 on pci0
pcm0: Cirrus Logic CS4297A AC97 Codec
orm0: Option ROMs at iomem 0xe4000-0xe7fff,0xdc000-0xd,0xc-0xc7fff on isa0
atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: failed to get data.
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5 drive on fdc0 drive 0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown: PNP0303 can't assign resources (port)
unknown: PNP0c02 can't assign resources (memory)
unknown: PNP0c02 can't assign resources (port)
unknown: PNP0c02 can't assign resources (memory)
unknown: PNP0f13 can't assign resources (irq)
unknown: PNP0501 can't assign resources (port)
unknown: PNP0501 can't assign resources (port)
unknown: PNP0700 can't assign resources (port)
Timecounter TSC frequency 1478012117 Hz quality 800
Timecounters tick every 10.000 msec
ad0: 16384MB VMware Virtual IDE Hard Drive [33288/16/63] at ata0-master UDMA33
acd0: CDROM VMware Virtual IDE CDROM Drive at ata1-master PIO4
Mounting root from ufs:/dev/ad0s1a
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: Mon Aug 25 14:55:18 CEST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/VFBSD5
Preloaded elf kernel /boot/kernel/kernel at 0xc03ef000.
Preloaded elf module /boot/kernel/snd_es137x.ko at 0xc03ef278.
Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc03ef328.
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) XP 1700+ (1479.35-MHz 686-class CPU)
  Origin = AuthenticAMD  Id = 0x662  Stepping = 2
  
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
  AMD Features=0xc048MP,AMIE,DSP,3DNow!
real memory  = 268435456 (256 MB)
avail memory = 256368640 (244 MB)
npx0: math processor on motherboard
npx0: INT 16 interface

Re: HEADS UP! ATAng committed

2003-08-25 Thread Soren Schmidt
It seems Dimitry Andric wrote:
-- Start of PGP signed section.
 On 2003-08-24 at 11:27:05 Soren Schmidt wrote:
 
  ATAng has just been committed. You need to make world after this update
  as atacontrol etc needs to pick up the changes.
 
 Building went fine here on my VMware test box, but the new kernel spat
 out a warning (which wasn't fatal, as it doesn't panic):
 
 ad0: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED
 ad0: 16384MB VMware Virtual IDE Hard Drive [33288/16/63] at ata0-master UDMA33

Hmm WMware doesn't implement setting transfer mode (which kind of makes sense)..

 See also attached dmesgs from before and after the ATAng update. This
 is with VMware 4.01.5289 on Windows, btw.
 
 Next I'm going to try this nice update on my crucial router box... see
 you later, hopefully. ;)

I'm running it on mine for over a week :)

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


Re: HEADS UP! ATAng committed

2003-08-25 Thread Radko Keves
;), Sun, Aug 24, 2003 at 11:27:05AM +0200, Soren Schmidt said that
 
 ATAng has just been committed. You need to make world after this update
 as atacontrol etc needs to pick up the changes.
 
 -Søren
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]



hi 

i try ATAng from current cvs and have found old warnings:

ad4: WARNING-SETFEATURES recovered from missing interupt
ad4: WARNING-READ_DMA recovered from missing interupt
[..] 
ad4: 38166MB WDC WD400BB-00CLB0 [77545/16/63] at ata2-master UDMA100
[..]
ad4: WARNING-SETFEATURES recovered from missing interupt
ad4: WARNING-READ_DMA recovered from missing interupt
[..]

in circle longer than 5 minutes then i reboot box and use last kernel
which worked with my ATA from: May 19 2003   :(


it is old warning/error but nothing changed

dmesg attached


bye
-- 
-
Radko Keves
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-BETA #32: Mon May 19 15:01:33 CEST 2003
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/angel
Preloaded elf kernel /boot/kernel.old/kernel at 0xc04f8000.
Timecounter i8254  frequency 1193182 Hz
Timecounter TSC  frequency 927107442 Hz
CPU: Intel Pentium III (927.11-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x68a  Stepping = 10
  
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real memory  = 268435456 (256 MB)
avail memory = 255422464 (243 MB)
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 7 entries at 0xc00ede90
pcib0: ServerWorks NB6635 3.0LE host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
pcib1: PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
fxp0: Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet port 0x1800-0x183f mem 
0xb100-0xb10f,0xb110-0xb1100fff irq 11 at device 5.0 on pci1
fxp0: Ethernet address 00:50:8b:e9:e8:92
miibus0: MII bus on fxp0
inphy0: i82555 10/100 media interface on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci1: display, VGA at device 6.0 (no driver attached)
pci1: base peripheral at device 7.0 (no driver attached)
atapci0: CMD 649 UDMA100 controller port 
0x1840-0x184f,0x1864-0x1867,0x1858-0x185f,0x1860-0x1863,0x1850-0x1857 irq 10 at device 
8.0 on pci1
ata2: at 0x1850 on atapci0
ata3: at 0x1858 on atapci0
xl0: 3Com 3c905C-TX Fast Etherlink XL port 0x2000-0x207f mem 0xb150-0xb150007f 
irq 11 at device 4.0 on pci0
xl0: Ethernet address: 00:04:76:9d:0c:cd
miibus1: MII bus on xl0
ukphy0: Generic IEEE 802.3u media interface on miibus1
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0: PCI-ISA bridge port 0xfc00-0xfc0f at device 15.0 on pci0
isa0: ISA bus on isab0
atapci1: ServerWorks ROSB4 UDMA33 controller port 0x2080-0x208f at device 15.1 on 
pci0
ata0: at 0x1f0 irq 14 on atapci1
ata1: at 0x170 irq 15 on atapci1
pci0: serial bus, USB at device 15.2 (no driver attached)
pcib5: ServerWorks NB6635 3.0LE host to PCI bridge at pcibus 5 on motherboard
pci5: PCI bus on pcib5
orm0: Option ROMs at iomem 
0xe8000-0xe,0xd2000-0xdcfff,0xd-0xd07ff,0xc8000-0xc,0xc-0xc7fff on isa0
atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5 drive on fdc0 drive 0
pmtimer0 on isa0
ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppbus0: Parallel port bus on ppc0
plip0: PLIP network interface on ppbus0
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown: PNP0401 can't assign resources (port)
unknown: PNP0501 can't assign resources (port)
unknown: PNP0501 can't assign resources (port)
unknown: PNP0700 can't assign resources (port)
unknown: PNP0c01 can't assign resources (memory)
unknown: PNP0303 can't assign resources (port)
unknown: PNP0f13 can't assign resources (irq)
Timecounters tick every 10.000 msec
ata0-slave: timeout waiting for interrupt
ata0-slave: ATA identify failed
ad4: 38166MB WDC WD400BB-00CLB0 [77545/16/63] at ata2-master UDMA100
ad5: 38166MB WDC 

Re: HEADS UP! ATAng committed

2003-08-25 Thread Thomas Quinot
Le 2003-08-25, Matt écrivait :

 db trace
 free_hcb(c40f1040,c03c7e40,101,c41d5800,c1528130) at free_hcb+0x2e
 atapi_action(c40f1440,c41d5800,c0132b33,c41db000,c41d5800) at
 atapi_action+ox56c

OK, so that presumably means we're going through action_oom, and so you
should have had one of the following messages on the console:

printf(cannot allocate ATAPI/CAM hcb\n);
printf(cannot allocate ATAPI/CAM request\n);
printf(cannot allocate ATAPI/CAM buffer\n);

It would be interesting to know which, if any, of these messages you
saw. Also, please try whether the following patch improves the
situation:

Index: atapi-cam.c
===
RCS file: /home/ncvs/src/sys/dev/ata/atapi-cam.c,v
retrieving revision 1.20
diff -u -r1.20 atapi-cam.c
--- atapi-cam.c 24 Aug 2003 17:48:05 -  1.20
+++ atapi-cam.c 25 Aug 2003 17:24:44 -
@@ -59,7 +59,7 @@
 intlun;
 union ccb  *ccb;
 intflags;
-#define DOING_AUTOSENSE 1
+#define QUEUED 0x0001;
 
 char   *dxfer_alloc;
 TAILQ_ENTRY(atapi_hcb) chain;
@@ -394,7 +394,7 @@
/* scatter-gather not supported */
xpt_print_path(ccb_h-path);
printf(ATAPI/CAM does not support scatter-gather yet!\n);
-   break;
+   goto action_invalid;
}
 
if ((hcb = allocate_hcb(softc, unit, bus, ccb)) == NULL) {
@@ -464,8 +464,8 @@
 
if ((ccb_h-flags  CAM_DIR_MASK) == CAM_DIR_IN  (len  1)) {
/* ATA always transfers an even number of bytes */
-   if (!(buf = hcb-dxfer_alloc = malloc(++len, M_ATACAM,
- M_NOWAIT | M_ZERO)))
+   if ((buf = hcb-dxfer_alloc = malloc(++len, M_ATACAM,
+ M_NOWAIT | M_ZERO)) == NULL)
printf(cannot allocate ATAPI/CAM buffer\n);
goto action_oom;
}
@@ -494,6 +494,7 @@
 }
 
TAILQ_INSERT_TAIL(softc-pending_hcbs, hcb, chain);
+   hcb-flags |= QUEUED;
 
ata_queue_request(request);
return;
@@ -519,9 +520,13 @@
 return;
 
 action_invalid:
-   ccb_h-status = CAM_REQ_INVALID;
-   xpt_done(ccb);
-   return;
+if (request != NULL)
+   ata_free_request(request);
+if (hcb != NULL)
+   free_hcb(hcb);
+ccb_h-status = CAM_REQ_INVALID;
+xpt_done(ccb);
+return;
 }
 
 static void
@@ -686,7 +691,8 @@
 static void
 free_hcb(struct atapi_hcb *hcb)
 {
-TAILQ_REMOVE(hcb-softc-pending_hcbs, hcb, chain);
+if ((hcb-flags  QUEUED) != 0)
+TAILQ_REMOVE(hcb-softc-pending_hcbs, hcb, chain);
 if (hcb-dxfer_alloc != NULL)
free(hcb-dxfer_alloc, M_ATACAM);
 free(hcb, M_ATACAM);

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


Re: HEADS UP! ATAng committed

2003-08-24 Thread Roderick van Domburg
 ATAng has just been committed. You need to make world after this
 update as atacontrol etc needs to pick up the changes.
Coolness. Judging from the CVS log, it also gets ATA out under Giant? 
That should make ATA-run SMP boxes eligible for an impressive increase 
in I/O performance... has anyone noticed?

Regards,

Roderick

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


Re: HEADS UP! ATAng committed

2003-08-24 Thread Soren Schmidt
It seems Roderick van Domburg wrote:
   ATAng has just been committed. You need to make world after this
   update as atacontrol etc needs to pick up the changes.
 
 Coolness. Judging from the CVS log, it also gets ATA out under Giant? 

Yes it does.

 That should make ATA-run SMP boxes eligible for an impressive increase 
 in I/O performance... has anyone noticed?

Depends alot on what you are doing..

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


Re: HEADS UP! ATAng committed

2003-08-24 Thread Matt
I have just cvsup'd and done a full buildworld/kernel and on reboot had a
kernel panic. Unfortunatly I do not have ddb or anything compiled into the
kernel but I can sort this out and get a proper backtrace etc if you don't
immediatly know what's wrong.

I have the following hardware:

ad0: 76319MB ST380020A [155061/16/63] at ata0-master UDMA100
acd0: DVD-ROM Compaq DVD-ROM SD-616T at ata1-master PIO4
acd1: CD-RW SAMSUNG CD-R/RW SW-240B at ata1-slave PIO4

This did work perfectly with the old ATA, but the new ATA panic's. I have
found that it is due to having device atapicam for the SCSI emulation. If I
recompile the kernel with this option commented out the kernel boots and
everything works normally (except the SCSI emulation).

If you need a full panic message and backtrace then I will recompile it with
debugging options enabled and get one for you.

Matt.


--
email: [EMAIL PROTECTED] - web: http://xtaz.co.uk/
Hardware, n.: The parts of a computer system that can be kicked.


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


Re: HEADS UP! ATAng committed

2003-08-24 Thread Soren Schmidt
It seems Matt wrote:
 I have just cvsup'd and done a full buildworld/kernel and on reboot had a
 kernel panic. Unfortunatly I do not have ddb or anything compiled into the
 kernel but I can sort this out and get a proper backtrace etc if you don't
 immediatly know what's wrong.
 
 I have the following hardware:
 
 ad0: 76319MB ST380020A [155061/16/63] at ata0-master UDMA100
 acd0: DVD-ROM Compaq DVD-ROM SD-616T at ata1-master PIO4
 acd1: CD-RW SAMSUNG CD-R/RW SW-240B at ata1-slave PIO4
 
 This did work perfectly with the old ATA, but the new ATA panic's. I have
 found that it is due to having device atapicam for the SCSI emulation. If I
 recompile the kernel with this option commented out the kernel boots and
 everything works normally (except the SCSI emulation).
 
 If you need a full panic message and backtrace then I will recompile it with
 debugging options enabled and get one for you.

This is a case for Thomas I guess, atapicam is his baby I just allow it
to be around :)

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


Re: HEADS UP! ATAng committed

2003-08-24 Thread Wesley Morgan
On Sun, 24 Aug 2003, Matt wrote:

 This did work perfectly with the old ATA, but the new ATA panic's. I have
 found that it is due to having device atapicam for the SCSI emulation. If I
 recompile the kernel with this option commented out the kernel boots and
 everything works normally (except the SCSI emulation).

I can confirm that atapicam causes my system to hang, but not panic, on
boot where the kernel would normally be detecting cd0.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADS UP! ATAng committed

2003-08-24 Thread Soren Schmidt
It seems Wesley Morgan wrote:
 On Sun, 24 Aug 2003, Matt wrote:
 
  This did work perfectly with the old ATA, but the new ATA panic's. I have
  found that it is due to having device atapicam for the SCSI emulation. If I
  recompile the kernel with this option commented out the kernel boots and
  everything works normally (except the SCSI emulation).
 
 I can confirm that atapicam causes my system to hang, but not panic, on
 boot where the kernel would normally be detecting cd0.

As I said give Thomas a chance to get things sorted out with atapicam..

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


Re: HEADS UP! ATAng committed

2003-08-24 Thread David O'Brien
On Sun, Aug 24, 2003 at 11:27:05AM +0200, Soren Schmidt wrote:
 ATAng has just been committed. You need to make world after this update
 as atacontrol etc needs to pick up the changes.

Does ATAng still kill various Seagate drives?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: HEADS UP! ATAng committed

2003-08-24 Thread Daniel Eischen
On Sun, 24 Aug 2003, Soren Schmidt wrote:

 It seems Matt wrote:
  I have just cvsup'd and done a full buildworld/kernel and on reboot had a
  kernel panic. Unfortunatly I do not have ddb or anything compiled into the
  kernel but I can sort this out and get a proper backtrace etc if you don't
  immediatly know what's wrong.
  
  I have the following hardware:
  
  ad0: 76319MB ST380020A [155061/16/63] at ata0-master UDMA100
  acd0: DVD-ROM Compaq DVD-ROM SD-616T at ata1-master PIO4
  acd1: CD-RW SAMSUNG CD-R/RW SW-240B at ata1-slave PIO4
  
  This did work perfectly with the old ATA, but the new ATA panic's. I have
  found that it is due to having device atapicam for the SCSI emulation. If I
  recompile the kernel with this option commented out the kernel boots and
  everything works normally (except the SCSI emulation).
  
  If you need a full panic message and backtrace then I will recompile it with
  debugging options enabled and get one for you.
 
 This is a case for Thomas I guess, atapicam is his baby I just allow it
 to be around :)

I appreciate all the work you've done for ATA.  But that said, atapicam
has been present for a while, and it should have been tested and made
to work -- at least so it doesn't panic the system -- before committing
ATAng.

-- 
Dan Eischen

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


Re: HEADS UP! ATAng committed

2003-08-24 Thread Soren Schmidt
It seems David O'Brien wrote:
 On Sun, Aug 24, 2003 at 11:27:05AM +0200, Soren Schmidt wrote:
  ATAng has just been committed. You need to make world after this update
  as atacontrol etc needs to pick up the changes.
 
 Does ATAng still kill various Seagate drives?
 
Uhm ? what do you mean by that ?
The only problem I know of with Seagates is with a certain 40G model
and that I can't reproduce here with ATAng actually..

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


Re: HEADS UP! ATAng committed

2003-08-24 Thread Soren Schmidt
It seems Daniel Eischen wrote:
  This is a case for Thomas I guess, atapicam is his baby I just allow it
  to be around :)
 
 I appreciate all the work you've done for ATA.  But that said, atapicam
 has been present for a while, and it should have been tested and made
 to work -- at least so it doesn't panic the system -- before committing
 ATAng.

And that is axactly the case, this is what I've got from Thomas and that
should have been tested etc etc..

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


Re: HEADS UP! ATAng committed

2003-08-24 Thread Daniel Eischen
On Sun, 24 Aug 2003, Soren Schmidt wrote:

 It seems Daniel Eischen wrote:
   This is a case for Thomas I guess, atapicam is his baby I just allow it
   to be around :)
  
  I appreciate all the work you've done for ATA.  But that said, atapicam
  has been present for a while, and it should have been tested and made
  to work -- at least so it doesn't panic the system -- before committing
  ATAng.
 
 And that is axactly the case, this is what I've got from Thomas and that
 should have been tested etc etc..

OK, I guess I missed that.  Sorry for the repeated response.

-- 
Dan Eischen

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


Re: HEADS UP! ATAng committed

2003-08-24 Thread Hiroyuki Aizu
Hello.
(B
(BI was update 5-current and begin using with ATAng and ust view ata-pci.c.
(BThen I found one question in the source code.
(B
(Bata-pci.c 462 line.
(BDEVMETHOD(device_detach,ata_pci_attach),
(B
(BIs this  right?
(BI think, it should be use "ata_pci_dettach" or something, but I cannot found
(Bthe function.
(B
(B--
(BHiroyuki Aizu
(B
(B
(BOn Sun, 24 Aug 2003 11:27:05 +0200 (CEST)
(BSoren Schmidt [EMAIL PROTECTED] wrote:
(B
(B 
(B ATAng has just been committed. You need to make world after this update
(B as atacontrol etc needs to pick up the changes.
(B 
(B -S$Bxr(Ben
(B ___
(B [EMAIL PROTECTED] mailing list
(B http://lists.freebsd.org/mailman/listinfo/freebsd-current
(B To unsubscribe, send any mail to "[EMAIL PROTECTED]"
(B 
(B 
(B 
(B
(B
(B___
(B[EMAIL PROTECTED] mailing list
(Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-current
(BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: HEADS UP! ATAng committed

2003-08-24 Thread Soren Schmidt
It seems Hiroyuki Aizu wrote:
 Hello.
 
 I was update 5-current and begin using with ATAng and ust view ata-pci.c.
 Then I found one question in the source code.
 
 ata-pci.c 462 line.
 DEVMETHOD(device_detach,ata_pci_attach),
 
 Is this  right?
 I think, it should be use ata_pci_dettach or something, but I cannot found
 the function.

Just remove that line pci ATA device cannot be detached as is..

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