[PATCH] CREDITS: Update contact information

2020-07-30 Thread Neil Whelchel
Update my email address in driver, documentation, and add to credits.

diff --git a/CREDITS b/CREDITS
index 0787b5872906..65803e878c92 100644
--- a/CREDITS
+++ b/CREDITS
@@ -3957,6 +3957,14 @@ S: 820 4th St. N.
 S: Fargo, North Dakota 58122
 S: USA

+N: Neil Whelchel
+E: n...@goautomation.biz
+W: http://goautomation.biz
+S: Go Automation, LLC
+S: P.O. Box 2082
+S: Joshua Tree, Ca 92252
+S: USA
+
 N: Steven Whitehouse
 E: st...@chygwyn.com
 W: http://www.chygwyn.com/~steve
diff --git a/Documentation/usb/usb-serial.rst b/Documentation/usb/usb-serial.rst
index 8fa7dbd3da9a..f9ebfb1a60a3 100644
--- a/Documentation/usb/usb-serial.rst
+++ b/Documentation/usb/usb-serial.rst
@@ -231,7 +231,7 @@ ZyXEL omni.net lcd plus ISDN TA
 Cypress M8 CY4601 Family Serial Driver
 --

-  This driver was in most part developed by Neil "koyama" Whelchel.  It
+  This driver was in most part developed by Neil Whelchel.  It
   has been improved since that previous form to support dynamic serial
   line settings and improved line handling.  The driver is for the most
   part stable and has been tested on an smp machine. (dual p2)
diff --git a/drivers/usb/serial/cypress_m8.c b/drivers/usb/serial/cypress_m8.c
index ecda82198798..2b1d854645ed 100644
--- a/drivers/usb/serial/cypress_m8.c
+++ b/drivers/usb/serial/cypress_m8.c
@@ -5,7 +5,7 @@
  * Copyright (C) 2004
  * Lonnie Mendez (dign...@gmail.com)
  * Copyright (C) 2003,2004
- *     Neil Whelchel (koy...@firstlight.net)
+ *     Neil Whelchel (n...@goautomation.biz)
  *
  * See Documentation/usb/usb-serial.rst for more information on using this
  * driver
@@ -45,7 +45,7 @@ static bool stats;
 static int interval;
 static bool unstable_bauds;

-#define DRIVER_AUTHOR "Lonnie Mendez , Neil
Whelchel "
+#define DRIVER_AUTHOR "Lonnie Mendez , Neil
Whelchel "
 #define DRIVER_DESC "Cypress USB to Serial Driver"

 /* write buffer size defines */


Re: SATA Promise TX4 Crash

2005-03-27 Thread Neil Whelchel
On Sat, 26 Mar 2005, quasiben wrote:

> Dear Neil Whelchel,
>  I have been having very similar problems.  However, my setup is
> somewhat different.  I have a LVM logical volume that spans two disks
> (one PATA and one SATA).  Did you upgrade your PSU as one person
> suggested ? If so, did it work ?
>
> --Benji
>
> Neil Whelchel wrote:
> > Hello,
> > I have two Promise SATA TX4 cards connected to a total of 6 Maxtor
> 250 GB
> > drives (7Y250M0) configured into a RAID 5. All works well with small
> > disk load, but when a large number of requests are issued, it causes
> crash
> > similar to the attached, except that the errors before the crash are
> on a
> > different drive nearly every time. I have tried several different
> > motherboards with both Nvidia and Via chipsets, with Athlon and K6
> > CPUs, and the crash remains the same. I have also seen the same crash
> > with both a preemptable and a non-preemptable kernel, with kernel
> > versions 2.6.9, 2.6.10, 2.6.11, and 2.6.11.2 (this one).
> > Any suggestions, or is this a bug?
> >
> >
> > ata3: status=0x51 { DriveReady SeekComplete Error }
> > ata3: error=0x40 { UncorrectableError }
> > ata3: status=0x51 { DriveReady SeekComplete Error }
> > ata3: error=0x40 { UncorrectableError }
> > ata3: status=0x51 { DriveReady SeekComplete Error }
> > ata3: error=0x40 { UncorrectableError }
> > ata3: status=0x51 { DriveReady SeekComplete Error }
> > ata3: error=0x40 { UncorrectableError }
> > ata3: status=0x51 { DriveReady SeekComplete Error }
> > ata3: error=0x40 { UncorrectableError }
> > ata3: command timeout
> > Assertion failed! qc->flags &
> >
> ATA_QCFLAG_ACTIVE,drivers/scsi/libata-core.c,ata_qc_complete,line=2807
> > ata3: status=0x51 { DriveReady SeekComplete Error }
> > ata3: called with no error (51)!
> > [ cut here ]
> > kernel BUG at drivers/scsi/scsi.c:299!
> > invalid operand:  [#1]
> > PREEMPT
> > Modules linked in:
> > CPU:0
> > EIP:0060:[]Not tainted VLI
> > EFLAGS: 00010046   (2.6.11.2)
> > EIP is at scsi_put_command+0xbb/0x100
> > eax: 0001   ebx: c2f5e390   ecx: 0001   edx: c2f5e390
> > esi: c2f5e380   edi: 0246   ebp: c7c4beb4   esp: c7c4be9c
> > ds: 007b   es: 007b   ss: 0068
> > Process scsi_eh_2 (pid: 821, threadinfo=c7c4a000 task=c7c315b0)
> > Stack: 0296 c7c3 c7c26400 c7c23030 c2f5e380 0246 c7c4bec4
> c02ae9b3
> >c2f5e380 c44a1740 c7c4bee0 c02aeabc c2f5e380 c7c23030 c2f5e380
> 0802
> >c44a1740 c7c4bf28 c02aedd2 c2f5e380 0001  
> 
> > Call Trace:
> >  [] show_stack+0x72/0xa0
> >  [] show_registers+0x104/0x180
> >  [] die+0xd3/0x180
> >  [] do_invalid_op+0x90/0xa0
> >  [] error_code+0x2b/0x30
> >  [] scsi_next_command+0x13/0x20
> >  [] scsi_end_request+0xbc/0xe0
> >  [] scsi_io_completion+0x132/0x3c0
> >  [] sd_rw_intr+0xb8/0x2c0
> >  [] ata_scsi_qc_complete+0x20/0x40
> >  [] ata_qc_complete+0x2c/0xa0
> >  [] pdc_eng_timeout+0x93/0x120
> >  [] ata_scsi_error+0x14/0x40
> >  [] scsi_error_handler+0x5b/0xc0
> >  [] kernel_thread_helper+0x5/0x14
> > Code: ec 8b 42 08 ff 30 e8 e5 cd e8 ff 59 5b 8b 45 f0 05 84 01 00 00
> 89 45
> > 08 8d 65 f4 5b 5e 5f c9 e9 ac 41 fc ff e8 47 6c 13 00 eb ce <0f> 0b
> 2b 01
> > d6 e8 40 c0 e9 6c ff ff ff e8 33 6c 13 00 eb 8b 89
> >  <6>note: scsi_eh_2[821] exited with preempt_count 1
> >
> >
> > -Neil Whelchel-
> > First Light Internet Services
> > 760 366-0145
> > - We don't do Window$, that's what the janitor is for -
> >
> > Bubble Memory, n.:
> > A derogatory term, usually referring to a person's
> > intelligence.  See also "vacuum tube".
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> > the body of a message to [EMAIL PROTECTED]
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
>
Hello,
Yes, I did replace the PSU about 6 times. I had the same problem with 4
similar machines (all the same), and in one of them I tried two
other different power supplies, so there were a total of three completely
different supplies tested. All of them were 450 Watts, except for one 500
Watt that I tested..
While, my 'feelings' tell me that the PSU is the issue, I have been
looking more to grounding and SATA cable than anything else. But there is
one HUGE however here... If there is a communication failure, it should
not cause a crash in the kernel, this should be fixed!

-Neil Whelchel-
First Light Internet Services
760 366-0145
- We don't do Window$, that's what the janitor is for -

Bubble Memory, n.:
A derogatory term, usually referring to a person's
intelligence.  See also "vacuum tube".

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: SATA Promise TX4 Crash

2005-03-27 Thread Neil Whelchel
On Sat, 26 Mar 2005, quasiben wrote:

 Dear Neil Whelchel,
  I have been having very similar problems.  However, my setup is
 somewhat different.  I have a LVM logical volume that spans two disks
 (one PATA and one SATA).  Did you upgrade your PSU as one person
 suggested ? If so, did it work ?

 --Benji

 Neil Whelchel wrote:
  Hello,
  I have two Promise SATA TX4 cards connected to a total of 6 Maxtor
 250 GB
  drives (7Y250M0) configured into a RAID 5. All works well with small
  disk load, but when a large number of requests are issued, it causes
 crash
  similar to the attached, except that the errors before the crash are
 on a
  different drive nearly every time. I have tried several different
  motherboards with both Nvidia and Via chipsets, with Athlon and K6
  CPUs, and the crash remains the same. I have also seen the same crash
  with both a preemptable and a non-preemptable kernel, with kernel
  versions 2.6.9, 2.6.10, 2.6.11, and 2.6.11.2 (this one).
  Any suggestions, or is this a bug?
 
 
  ata3: status=0x51 { DriveReady SeekComplete Error }
  ata3: error=0x40 { UncorrectableError }
  ata3: status=0x51 { DriveReady SeekComplete Error }
  ata3: error=0x40 { UncorrectableError }
  ata3: status=0x51 { DriveReady SeekComplete Error }
  ata3: error=0x40 { UncorrectableError }
  ata3: status=0x51 { DriveReady SeekComplete Error }
  ata3: error=0x40 { UncorrectableError }
  ata3: status=0x51 { DriveReady SeekComplete Error }
  ata3: error=0x40 { UncorrectableError }
  ata3: command timeout
  Assertion failed! qc-flags 
 
 ATA_QCFLAG_ACTIVE,drivers/scsi/libata-core.c,ata_qc_complete,line=2807
  ata3: status=0x51 { DriveReady SeekComplete Error }
  ata3: called with no error (51)!
  [ cut here ]
  kernel BUG at drivers/scsi/scsi.c:299!
  invalid operand:  [#1]
  PREEMPT
  Modules linked in:
  CPU:0
  EIP:0060:[c02a9ddb]Not tainted VLI
  EFLAGS: 00010046   (2.6.11.2)
  EIP is at scsi_put_command+0xbb/0x100
  eax: 0001   ebx: c2f5e390   ecx: 0001   edx: c2f5e390
  esi: c2f5e380   edi: 0246   ebp: c7c4beb4   esp: c7c4be9c
  ds: 007b   es: 007b   ss: 0068
  Process scsi_eh_2 (pid: 821, threadinfo=c7c4a000 task=c7c315b0)
  Stack: 0296 c7c3 c7c26400 c7c23030 c2f5e380 0246 c7c4bec4
 c02ae9b3
 c2f5e380 c44a1740 c7c4bee0 c02aeabc c2f5e380 c7c23030 c2f5e380
 0802
 c44a1740 c7c4bf28 c02aedd2 c2f5e380 0001  
 
  Call Trace:
   [c0102c12] show_stack+0x72/0xa0
   [c0102d64] show_registers+0x104/0x180
   [c0102f53] die+0xd3/0x180
   [c0103330] do_invalid_op+0x90/0xa0
   [c010282b] error_code+0x2b/0x30
   [c02ae9b3] scsi_next_command+0x13/0x20
   [c02aeabc] scsi_end_request+0xbc/0xe0
   [c02aedd2] scsi_io_completion+0x132/0x3c0
   [c02ba698] sd_rw_intr+0xb8/0x2c0
   [c02b8420] ata_scsi_qc_complete+0x20/0x40
   [c02b658c] ata_qc_complete+0x2c/0xa0
   [c02b9473] pdc_eng_timeout+0x93/0x120
   [c02b7ef4] ata_scsi_error+0x14/0x40
   [c02add5b] scsi_error_handler+0x5b/0xc0
   [c0100811] kernel_thread_helper+0x5/0x14
  Code: ec 8b 42 08 ff 30 e8 e5 cd e8 ff 59 5b 8b 45 f0 05 84 01 00 00
 89 45
  08 8d 65 f4 5b 5e 5f c9 e9 ac 41 fc ff e8 47 6c 13 00 eb ce 0f 0b
 2b 01
  d6 e8 40 c0 e9 6c ff ff ff e8 33 6c 13 00 eb 8b 89
   6note: scsi_eh_2[821] exited with preempt_count 1
 
 
  -Neil Whelchel-
  First Light Internet Services
  760 366-0145
  - We don't do Window$, that's what the janitor is for -
 
  Bubble Memory, n.:
  A derogatory term, usually referring to a person's
  intelligence.  See also vacuum tube.
 
  -
  To unsubscribe from this list: send the line unsubscribe
 linux-kernel in
  the body of a message to [EMAIL PROTECTED]
  More majordomo info at  http://vger.kernel.org/majordomo-info.html
  Please read the FAQ at  http://www.tux.org/lkml/

Hello,
Yes, I did replace the PSU about 6 times. I had the same problem with 4
similar machines (all the same), and in one of them I tried two
other different power supplies, so there were a total of three completely
different supplies tested. All of them were 450 Watts, except for one 500
Watt that I tested..
While, my 'feelings' tell me that the PSU is the issue, I have been
looking more to grounding and SATA cable than anything else. But there is
one HUGE however here... If there is a communication failure, it should
not cause a crash in the kernel, this should be fixed!

-Neil Whelchel-
First Light Internet Services
760 366-0145
- We don't do Window$, that's what the janitor is for -

Bubble Memory, n.:
A derogatory term, usually referring to a person's
intelligence.  See also vacuum tube.

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


SATA Promise TX4 Crash

2005-03-20 Thread Neil Whelchel
Hello,
I have two Promise SATA TX4 cards connected to a total of 6 Maxtor 250 GB
drives (7Y250M0) configured into a RAID 5. All works well with small
disk load, but when a large number of requests are issued, it causes crash
similar to the attached, except that the errors before the crash are on a
different drive nearly every time. I have tried several different
motherboards with both Nvidia and Via chipsets, with Athlon and K6
CPUs, and the crash remains the same. I have also seen the same crash
with both a preemptable and a non-preemptable kernel, with kernel
versions 2.6.9, 2.6.10, 2.6.11, and 2.6.11.2 (this one).
Any suggestions, or is this a bug?


ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: command timeout
Assertion failed! qc->flags &
ATA_QCFLAG_ACTIVE,drivers/scsi/libata-core.c,ata_qc_complete,line=2807
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: called with no error (51)!
[ cut here ]
kernel BUG at drivers/scsi/scsi.c:299!
invalid operand:  [#1]
PREEMPT
Modules linked in:
CPU:0
EIP:0060:[]Not tainted VLI
EFLAGS: 00010046   (2.6.11.2)
EIP is at scsi_put_command+0xbb/0x100
eax: 0001   ebx: c2f5e390   ecx: 0001   edx: c2f5e390
esi: c2f5e380   edi: 0246   ebp: c7c4beb4   esp: c7c4be9c
ds: 007b   es: 007b   ss: 0068
Process scsi_eh_2 (pid: 821, threadinfo=c7c4a000 task=c7c315b0)
Stack: 0296 c7c3 c7c26400 c7c23030 c2f5e380 0246 c7c4bec4 c02ae9b3
   c2f5e380 c44a1740 c7c4bee0 c02aeabc c2f5e380 c7c23030 c2f5e380 0802
   c44a1740 c7c4bf28 c02aedd2 c2f5e380 0001   
Call Trace:
 [] show_stack+0x72/0xa0
 [] show_registers+0x104/0x180
 [] die+0xd3/0x180
 [] do_invalid_op+0x90/0xa0
 [] error_code+0x2b/0x30
 [] scsi_next_command+0x13/0x20
 [] scsi_end_request+0xbc/0xe0
 [] scsi_io_completion+0x132/0x3c0
 [] sd_rw_intr+0xb8/0x2c0
 [] ata_scsi_qc_complete+0x20/0x40
 [] ata_qc_complete+0x2c/0xa0
 [] pdc_eng_timeout+0x93/0x120
 [] ata_scsi_error+0x14/0x40
 [] scsi_error_handler+0x5b/0xc0
 [] kernel_thread_helper+0x5/0x14
Code: ec 8b 42 08 ff 30 e8 e5 cd e8 ff 59 5b 8b 45 f0 05 84 01 00 00 89 45
08 8d 65 f4 5b 5e 5f c9 e9 ac 41 fc ff e8 47 6c 13 00 eb ce <0f> 0b 2b 01
d6 e8 40 c0 e9 6c ff ff ff e8 33 6c 13 00 eb 8b 89
 <6>note: scsi_eh_2[821] exited with preempt_count 1


-Neil Whelchel-
First Light Internet Services
760 366-0145
- We don't do Window$, that's what the janitor is for -

Bubble Memory, n.:
A derogatory term, usually referring to a person's
intelligence.  See also "vacuum tube".

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


SATA Promise TX4 Crash

2005-03-20 Thread Neil Whelchel
Hello,
I have two Promise SATA TX4 cards connected to a total of 6 Maxtor 250 GB
drives (7Y250M0) configured into a RAID 5. All works well with small
disk load, but when a large number of requests are issued, it causes crash
similar to the attached, except that the errors before the crash are on a
different drive nearly every time. I have tried several different
motherboards with both Nvidia and Via chipsets, with Athlon and K6
CPUs, and the crash remains the same. I have also seen the same crash
with both a preemptable and a non-preemptable kernel, with kernel
versions 2.6.9, 2.6.10, 2.6.11, and 2.6.11.2 (this one).
Any suggestions, or is this a bug?


ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
ata3: command timeout
Assertion failed! qc-flags 
ATA_QCFLAG_ACTIVE,drivers/scsi/libata-core.c,ata_qc_complete,line=2807
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: called with no error (51)!
[ cut here ]
kernel BUG at drivers/scsi/scsi.c:299!
invalid operand:  [#1]
PREEMPT
Modules linked in:
CPU:0
EIP:0060:[c02a9ddb]Not tainted VLI
EFLAGS: 00010046   (2.6.11.2)
EIP is at scsi_put_command+0xbb/0x100
eax: 0001   ebx: c2f5e390   ecx: 0001   edx: c2f5e390
esi: c2f5e380   edi: 0246   ebp: c7c4beb4   esp: c7c4be9c
ds: 007b   es: 007b   ss: 0068
Process scsi_eh_2 (pid: 821, threadinfo=c7c4a000 task=c7c315b0)
Stack: 0296 c7c3 c7c26400 c7c23030 c2f5e380 0246 c7c4bec4 c02ae9b3
   c2f5e380 c44a1740 c7c4bee0 c02aeabc c2f5e380 c7c23030 c2f5e380 0802
   c44a1740 c7c4bf28 c02aedd2 c2f5e380 0001   
Call Trace:
 [c0102c12] show_stack+0x72/0xa0
 [c0102d64] show_registers+0x104/0x180
 [c0102f53] die+0xd3/0x180
 [c0103330] do_invalid_op+0x90/0xa0
 [c010282b] error_code+0x2b/0x30
 [c02ae9b3] scsi_next_command+0x13/0x20
 [c02aeabc] scsi_end_request+0xbc/0xe0
 [c02aedd2] scsi_io_completion+0x132/0x3c0
 [c02ba698] sd_rw_intr+0xb8/0x2c0
 [c02b8420] ata_scsi_qc_complete+0x20/0x40
 [c02b658c] ata_qc_complete+0x2c/0xa0
 [c02b9473] pdc_eng_timeout+0x93/0x120
 [c02b7ef4] ata_scsi_error+0x14/0x40
 [c02add5b] scsi_error_handler+0x5b/0xc0
 [c0100811] kernel_thread_helper+0x5/0x14
Code: ec 8b 42 08 ff 30 e8 e5 cd e8 ff 59 5b 8b 45 f0 05 84 01 00 00 89 45
08 8d 65 f4 5b 5e 5f c9 e9 ac 41 fc ff e8 47 6c 13 00 eb ce 0f 0b 2b 01
d6 e8 40 c0 e9 6c ff ff ff e8 33 6c 13 00 eb 8b 89
 6note: scsi_eh_2[821] exited with preempt_count 1


-Neil Whelchel-
First Light Internet Services
760 366-0145
- We don't do Window$, that's what the janitor is for -

Bubble Memory, n.:
A derogatory term, usually referring to a person's
intelligence.  See also vacuum tube.

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Crash V4L + SATA ?

2005-03-13 Thread Neil Whelchel
Hello,
I have ran into a crash that seems to occur when I use my BT848 card along
with a Promise TX4 SATA card. (I have not been able to reproduce the crash
when I don't use the drives that are attached to the TX4 card.)
The BT848 and the TX4 are the only add-on cards attached to the system
which is a VIA VT8377 / VT8237 based Athlon board. I have had similar
crashes since 2.6.8 (maybe even before), I am currently using 2.6.11.2
with RAID 5 on six drives. (Four on the TX4 and two more on the built-in
controller on the MB.)
Every crash that I am aware of occurs between 30 seconds and 2 minutes
after I see the following lines in the kernel message buffer.

bttv0: OCERR @ 0c0d3014,bits: HSYNC OFLOW OCERR*
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
bttv0: OCERR @ 0c0d3014,bits: HSYNC OFLOW OCERR*


Unable to handle kernel paging request at virtual address 10101010
 printing eip:
d0a816f6
*pde = 
Oops:  [#1]
PREEMPT
Modules linked in: bttv video_buf firmware_class btcx_risc tveeprom
CPU:0
EIP:0060:[]Not tainted VLI
EFLAGS: 00210202   (2.6.11.2)
EIP is at videobuf_dma_free+0x36/0xf0 [video_buf]
eax:    ebx: c97bf000   ecx: 0208   edx: 10101010
esi:    edi: cc63ed04   ebp: d0ac7e60   esp: c328bbec
ds: 007b   es: 007b   ss: 0068
Process mythbackend (pid: 1232, threadinfo=c328a000 task=cf1aa550)
Stack: d0ac7e60 d0a81670 c3ef8000 cc63ed04 cc63ece0 d0ac7e60 d0ab6630 cc63ed04
   cc63ed04  cc63ece0  cc63ca00 d0aaee44 d0ac7e60 cc63ece0
   0001 01e0 01e0 0004 cc63ca00 cc63e7e0 c1384a20 0008
Call Trace:
 [] videobuf_dma_pci_unmap+0x30/0x80 [video_buf]
 [] bttv_dma_free+0x60/0xa0 [bttv]
 [] bttv_do_ioctl+0x1214/0x1790 [bttv]
 [] recalc_task_prio+0x8c/0x160
 [] activate_task+0x64/0x80
 [] recalc_task_prio+0x8c/0x160
 [] activate_task+0x64/0x80
 [] try_to_wake_up+0x8a/0xc0
 [] __wake_up_common+0x38/0x60
 [] __wake_up+0x55/0x80
 [] del_timer+0x92/0xc0
 [] svc_sock_enqueue+0x14b/0x2d0
 [] scsi_delete_timer+0x13/0x30
 [] scsi_done+0x10/0x30
 [] ata_scsi_qc_complete+0x2b/0x50
 [] recalc_task_prio+0x8c/0x160
 [] activate_task+0x64/0x80
 [] try_to_wake_up+0x8a/0xc0
 [] recalc_task_prio+0x8c/0x160
 [] activate_task+0x64/0x80
 [] try_to_wake_up+0x8a/0xc0
 [] __wake_up_common+0x38/0x60
 [] recalc_task_prio+0x8c/0x160
 [] copy_from_user+0x46/0x80
 [] video_usercopy+0xf6/0x170
 [] __wake_up_common+0x38/0x60
 [] __wake_up+0x55/0x80
 [] recalc_task_prio+0x8c/0x160
 [] mark_offset_tsc+0x270/0x370
 [] bttv_ioctl+0x3b/0x60 [bttv]
 [] bttv_do_ioctl+0x0/0x1790 [bttv]
 [] do_ioctl+0x70/0xb0
 [] vfs_ioctl+0x65/0x200
 [] fget_light+0x89/0xa0
 [] sys_ioctl+0x45/0x70
 [] syscall_call+0x7/0xb
Code: 07 3d 12 11 72 19 0f 85 aa 00 00 00 8b 47 18 85 c0 0f 85 92 00 00 00
8b 5f 08 85 db 74 3f 8b 4f 1c 31 f6 83 f9 00 7e 26 8b 14 b3 <8b> 02 f6 c4
08 75 17 8b 42 04 40 74 67 83 42 04 ff 0f 98 c0 84


Any ideas or suggestions would be greatly appreciated.
-Neil Whelchel-
First Light Internet Services
760 366-0145
- We don't do Window$, that's what the janitor is for -

Bubble Memory, n.:
A derogatory term, usually referring to a person's
intelligence.  See also "vacuum tube".

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Crash V4L + SATA ?

2005-03-13 Thread Neil Whelchel
Hello,
I have ran into a crash that seems to occur when I use my BT848 card along
with a Promise TX4 SATA card. (I have not been able to reproduce the crash
when I don't use the drives that are attached to the TX4 card.)
The BT848 and the TX4 are the only add-on cards attached to the system
which is a VIA VT8377 / VT8237 based Athlon board. I have had similar
crashes since 2.6.8 (maybe even before), I am currently using 2.6.11.2
with RAID 5 on six drives. (Four on the TX4 and two more on the built-in
controller on the MB.)
Every crash that I am aware of occurs between 30 seconds and 2 minutes
after I see the following lines in the kernel message buffer.

bttv0: OCERR @ 0c0d3014,bits: HSYNC OFLOW OCERR*
ata3: status=0x51 { DriveReady SeekComplete Error }
ata3: error=0x40 { UncorrectableError }
bttv0: OCERR @ 0c0d3014,bits: HSYNC OFLOW OCERR*


Unable to handle kernel paging request at virtual address 10101010
 printing eip:
d0a816f6
*pde = 
Oops:  [#1]
PREEMPT
Modules linked in: bttv video_buf firmware_class btcx_risc tveeprom
CPU:0
EIP:0060:[d0a816f6]Not tainted VLI
EFLAGS: 00210202   (2.6.11.2)
EIP is at videobuf_dma_free+0x36/0xf0 [video_buf]
eax:    ebx: c97bf000   ecx: 0208   edx: 10101010
esi:    edi: cc63ed04   ebp: d0ac7e60   esp: c328bbec
ds: 007b   es: 007b   ss: 0068
Process mythbackend (pid: 1232, threadinfo=c328a000 task=cf1aa550)
Stack: d0ac7e60 d0a81670 c3ef8000 cc63ed04 cc63ece0 d0ac7e60 d0ab6630 cc63ed04
   cc63ed04  cc63ece0  cc63ca00 d0aaee44 d0ac7e60 cc63ece0
   0001 01e0 01e0 0004 cc63ca00 cc63e7e0 c1384a20 0008
Call Trace:
 [d0a81670] videobuf_dma_pci_unmap+0x30/0x80 [video_buf]
 [d0ab6630] bttv_dma_free+0x60/0xa0 [bttv]
 [d0aaee44] bttv_do_ioctl+0x1214/0x1790 [bttv]
 [c01156dc] recalc_task_prio+0x8c/0x160
 [c0115814] activate_task+0x64/0x80
 [c01156dc] recalc_task_prio+0x8c/0x160
 [c0115814] activate_task+0x64/0x80
 [c011590a] try_to_wake_up+0x8a/0xc0
 [c0116478] __wake_up_common+0x38/0x60
 [c01164f5] __wake_up+0x55/0x80
 [c01230d2] del_timer+0x92/0xc0
 [c041706b] svc_sock_enqueue+0x14b/0x2d0
 [c02d7943] scsi_delete_timer+0x13/0x30
 [c02d4f40] scsi_done+0x10/0x30
 [c02e46bb] ata_scsi_qc_complete+0x2b/0x50
 [c01156dc] recalc_task_prio+0x8c/0x160
 [c0115814] activate_task+0x64/0x80
 [c011590a] try_to_wake_up+0x8a/0xc0
 [c01156dc] recalc_task_prio+0x8c/0x160
 [c0115814] activate_task+0x64/0x80
 [c011590a] try_to_wake_up+0x8a/0xc0
 [c0116478] __wake_up_common+0x38/0x60
 [c01156dc] recalc_task_prio+0x8c/0x160
 [c0225db6] copy_from_user+0x46/0x80
 [c02add66] video_usercopy+0xf6/0x170
 [c0116478] __wake_up_common+0x38/0x60
 [c01164f5] __wake_up+0x55/0x80
 [c01156dc] recalc_task_prio+0x8c/0x160
 [c010e470] mark_offset_tsc+0x270/0x370
 [d0aaf3fb] bttv_ioctl+0x3b/0x60 [bttv]
 [d0aadc30] bttv_do_ioctl+0x0/0x1790 [bttv]
 [c016c7d0] do_ioctl+0x70/0xb0
 [c016ca25] vfs_ioctl+0x65/0x200
 [c0159a99] fget_light+0x89/0xa0
 [c016cc05] sys_ioctl+0x45/0x70
 [c010330f] syscall_call+0x7/0xb
Code: 07 3d 12 11 72 19 0f 85 aa 00 00 00 8b 47 18 85 c0 0f 85 92 00 00 00
8b 5f 08 85 db 74 3f 8b 4f 1c 31 f6 83 f9 00 7e 26 8b 14 b3 8b 02 f6 c4
08 75 17 8b 42 04 40 74 67 83 42 04 ff 0f 98 c0 84


Any ideas or suggestions would be greatly appreciated.
-Neil Whelchel-
First Light Internet Services
760 366-0145
- We don't do Window$, that's what the janitor is for -

Bubble Memory, n.:
A derogatory term, usually referring to a person's
intelligence.  See also vacuum tube.

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


CREDITS

2005-02-02 Thread Neil Whelchel
Hello,
I just thought that in case anyone wants to contact me it would be easier
if I was listed in the CREDITS file...

N: Neil Whelchel
E: [EMAIL PROTECTED]
W: http://firstlight.net/~koyama
D: Cypress M8 driver, PMD-1280LS driver, USB patches
S: P.O. Box 2082
S: Joshua Tree, CA 92252


-Neil Whelchel-
First Light Internet Services
760 366-0145
- We don't do Window$, that's what the janitor is for -

Bubble Memory, n.:
A derogatory term, usually referring to a person's
intelligence.  See also "vacuum tube".

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


CREDITS

2005-02-02 Thread Neil Whelchel
Hello,
I just thought that in case anyone wants to contact me it would be easier
if I was listed in the CREDITS file...

N: Neil Whelchel
E: [EMAIL PROTECTED]
W: http://firstlight.net/~koyama
D: Cypress M8 driver, PMD-1280LS driver, USB patches
S: P.O. Box 2082
S: Joshua Tree, CA 92252


-Neil Whelchel-
First Light Internet Services
760 366-0145
- We don't do Window$, that's what the janitor is for -

Bubble Memory, n.:
A derogatory term, usually referring to a person's
intelligence.  See also vacuum tube.

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/