from:"Lee Damon"

Re: My wi(4) ate itself (or Fun with no memory).

2002-12-30 Thread Lee Damon

I have the same problems on an IBM T30 with integrated wi running 4.7-STABLE.
In fact, I've had this problem since 4.5 (which is where I started on
this system.)

nomad

> On Mon, Dec 30, 2002 at 11:36:45AM -0800, Juli Mallett wrote:
> > Hey,
> >=20
> > I ran some stuff overnight which exhausted my system's memory fairly well,
> > and was also thrashing around on my network, and I woke up to find that my
> > wi(4) blew up more or less:
> >=20
> > wi0: watchdog timeout
> > wi0: timeout in wi_cmd 0x0002; event status 0x8000
> > wi0: timeout in wi_cmd 0x; event status 0x8000
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: init failed
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: failed to allocate 1594 bytes on NIC
> > wi0: tx buffer allocation failed
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: failed to allocate 1594 bytes on NIC
> > wi0: mgmt. buffer allocation failed
> > Expensive timeout(9) function: 0xc02aefa0(0) 127.445894221
> > wi0: timeout in wi_seek to 0/0; last status 4000
> > wi0: timeout in wi_seek to 0/44; last status 4044
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: xmit failed
> > Expensive timeout(9) function: 0xc02cfde0(0xc1a08ccc) 7.384429976
> > wi0: watchdog timeout
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: init failed
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: failed to allocate 1594 bytes on NIC
> > wi0: tx buffer allocation failed
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: failed to allocate 1594 bytes on NIC
> > wi0: mgmt. buffer allocation failed
> > Expensive timeout(9) function: 0xc02aefa0(0) 135.098850348
> > wi0: timeout in wi_seek to 0/0; last status 4000
> > wi0: timeout in wi_seek to 0/44; last status 4044
> > wi0: wi_cmd: busy bit won't clear.
> > wi0: xmit failed
> >=20
> > Was how it started, and then a lot more of the 'busy bit won't clear'
> > messages.  I ejected the card after de-b0rking the rest of the system, and
> > was able to bring it back up fine, but thought maybe someone might have s=
> ome
> > insight into how exactly my wi(4) blew up, and whether this is an accepta=
> ble
> > failure case :)
> >=20
> > Thanx,
> > juli.
> > --=20
> > Juli Mallett <[EMAIL PROTECTED]>
> > AIM: BSDFlata IRC: juli@EFnet#flata
> > OpenDarwin, Mono, FreeBSD Developer.
> > ircd-hybrid Developer, EFnet addict.
> > FreeBSD on MIPS-Anything on FreeBSD.
> >=20
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> >=20
> >=20
> 
> I get those messages when running dstumbler and then trying to do other stu=
> ff
> with the device.
> The bad thing is, that the chip is integrated in my notebook so i can't sim=
> ply
> take it out and back in again :-)
> Is there any other way to reinitialize the card?
> 
> - Christian
> 
> --=20

nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /

5.0 on IBM T30: X11 failure

2003-02-04 Thread Lee Damon

I have just scratch installed 5.0 from CD.  (By scratch install
I mean I told it to delete and recreate all partitions except
/users, so none of my old OS configurations should have been
preseved.)

When I installed 5.0 X11 worked.  After turning off ACPI the built-in
trackpoint mouse started working.  I installed the XFConfig86 that was
running on the portable from 4.7 and it came up without much trouble. 

However, after doing a cvsup, make buildkernel, make buildworld, 
mergemaster -v, installkernel and installworld, X no longer works.  It 
seems to get a SIGABRT (signal 6) before it even paints the screen.
Booting from kernel.generic (a complete copy of the initial kernel
directory) and kernel.old does not fix it.

Someone reported problems earlier and the suggested fix was to
portupgrade -f wrapper.  I tried this, but it did not help.

I removed and reinstalled X from /stand/sysinstall (using FTP,
not CD. Hmm.. maybe I should try pulling it from CD again?) and
still have the same exit.

I am attaching the output of dmesg, the XFree86 session log,
my kernel configuration and the cvsupfile that I used.

A couple things I have noticed that might or might not have
bearing: 
dmesg shows realmem at 255MB when the box has over 700MB
(top shows all of the memory, though)

In dmesg, right after vga0 there are several unknown: lines

The lock order reversal that is so popular in this list is
showing up here. (It also shows up on the desktop
system I'm using, but that box isn't running X.)

apmd still isn't running (it stars then exits quietly)
/dev/apm isn't being created
(I'm sure this isn't relevant, but thought I'd mention it)

probe complains about cardbus.  I recall email about this
topic earlier and expect it is irrelevant to the
current problem.

Any hints, tips, or pointers at documentation I've missed would be
greatly appreciated.

thanks,
nomad

-- dmesg
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.0-CURRENT #2: Tue Feb  4 09:17:29 PST 2003
[EMAIL PROTECTED]:/users/FreeBSD-5.0/obj/users/FreeBSD-5.0/src/sys/T
YLENDEL
Preloaded elf kernel "/boot/kernel/kernel" at 0xc067c000.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 1798479664 Hz
CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.80GHz (1798.48-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf24  Stepping = 4
  Features=0x3febf9ff
real memory  = 267780096 (255 MB)
avail memory = 253177856 (241 MB)
Initializing GEOMetry subsystem
Pentium Pro MTRR support enabled
npx0:  on motherboard
npx0: INT 16 interface
Using $PIR table, 14 entries at 0xc00fdeb0
pcib0:  at pcibus 0 on motherboard
pci0:  on pcib0
agp0:  mem 0xe000-0xe3ff at device 0.0 
on pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at device 0.0 (no driver attached)
uhci0:  port 0x1800-0x181f irq 
11 at device 29.0 on pci0
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0x1820-0x183f irq 
11 at device 29.1 on pci0
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0x1840-0x185f irq 
11 at device 29.2 on pci0
usb2:  on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
pcib2:  at device 30.0 on pci0
pci2:  on pcib2
cbb0:  mem 0x5000-0x5fff irq 11 at device 
0.0 on pci2
cbb0: Could not map register memory
device_probe_and_attach: cbb0 attach returned 12
cbb0:  mem 0x5100-0x51000fff irq 11 at device 
0.1 on pci2
cbb0: Could not map register memory
device_probe_and_attach: cbb0 attach returned 12
wi0:  mem 0xf800-0xf8000fff irq 11 at device 2.0 on pci2
wi0: 802.11 address: 00:05:3c:03:84:79
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary (1.0.7), Station (1.3.6)
wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
fxp0:  port 0x8000-0x803f mem 0xd020-0xd0200fff 
irq 11 at device 8.0 on pci2
fxp0: Ethernet address 00:09:6b:50:2c:01
inphy0:  on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port 0x1860-0x186f,0x374-0x377,0x170-0x
177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0:  at device 31.3 (no driver attached)
pci0:  at device 31.5 (no driver attached)
pci0:  at device 31.6 (no driver attached)
eisa0:  on motherboard
eisa0: unknown card @@@ (0x) at slot 1
orm0:  at iomem 0xe-0xe,0xd1000-0xd1fff,0xd-0xd0fff,0x
c-0xc on isa0
pmti

Re: IBM T30 bluetooth - success (fwd)

2003-08-25 Thread Lee Damon

Does anyone have an estimate of when this patch will be checked in?

Please?

thanks,
nomad

--- Forwarded Messages

Date: Mon, 16 Jun 2003 23:37:38 +0200
From: Tobias Roth <[EMAIL PROTECTED]>
To: Lee Damon <[EMAIL PROTECTED]>
Subject: Re: IBM T30 bluetooth - success
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>


--PNTmBPCT7hxwcZjr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Jun 16, 2003 at 02:22:02PM -0700, Lee Damon wrote:
> What did you do?

in short, whining to some people about usb being broken until
someone (Bernd Walter) came up with a patch :-)

Other than that, I just followed Pavs tutorials at

http://www.oook.cz/bsd

good luck, t.

--PNTmBPCT7hxwcZjr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="usb_working.diff"

Index: usb_subr.c
===
RCS file: /home/ncvs/src/sys/dev/usb/usb_subr.c,v
retrieving revision 1.54
diff -u -r1.54 usb_subr.c
--- usb_subr.c  14 Jan 2003 23:07:43 -  1.54
+++ usb_subr.c  14 Jun 2003 16:01:38 -
@@ -964,6 +964,7 @@
usbd_device_handle dev;
struct usbd_device *hub;
usb_device_descriptor_t *dd;
+   usb_port_status_t ps;
usbd_status err;
int addr;
int i;
@@ -1020,12 +1021,14 @@
up->device = dev;
dd = &dev->ddesc;
/* Try a few times in case the device is slow (i.e. outside specs.) */
-   for (i = 0; i < 3; i++) {
+   for (i = 0; i < 15; i++) {
/* Get the first 8 bytes of the device descriptor. */
err = usbd_get_desc(dev, UDESC_DEVICE, 0, USB_MAX_IPACKET, dd);
if (!err)
break;
usbd_delay_ms(dev, 200);
+   if ((i & 3) == 3)
+   usbd_reset_port(up->parent, port, &ps);
}
if (err) {
DPRINTFN(-1, ("usbd_new_device: addr=%d, getting first desc "

--PNTmBPCT7hxwcZjr--

--- Message 2

Date: Tue, 17 Jun 2003 07:07:25 +0200
From: Bernd Walter <[EMAIL PROTECTED]>
To: Lee Damon <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: IBM T30 bluetooth - success
Message-ID: <[EMAIL PROTECTED]>

On Mon, Jun 16, 2003 at 04:31:25PM -0700, Lee Damon wrote:
> I can second that success.  Any chance of getting this patch checked in?

I just wait on a review.

- -- 
B.Walter   BWCThttp://www.bwct.de
[EMAIL PROTECTED]  [EMAIL PROTECTED]


--- End of Forwarded Messages



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

recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30laptop

2003-08-27 Thread Lee Damon

: || tylendel.castle.org [10] ; uname -a
FreeBSD tylendel.castle.org 5.1-CURRENT FreeBSD 5.1-CURRENT #38: Wed Aug 27 09:05:21 
PDT 2003 [EMAIL 
PROTECTED]:/users/FreeBSD-5.0/obj/users/FreeBSD-5.0/src/sys/TYLENDEL  i386

The kernel I compiled on 20 AUG recognizes acd0 and loggs the following:

Aug 27 08:24:10 tylendel kernel: acd0: CD-RW  at ata1-master U
DMA33
Aug 27 08:24:10 tylendel kernel: cd0 at ata1 bus 0 target 0 lun 0
Aug 27 08:24:10 tylendel kernel: cd0:  Removable
 CD-ROM SCSI-0 device 
Aug 27 08:24:10 tylendel kernel: cd0: 33.000MB/s transfers
Aug 27 08:24:10 tylendel kernel: cd0: Attempt to query device size failed: NOT R
EADY, Medium not present - tray closed

However, kernels compiled since Monday's SUP get as far as the initial
discovery of the acd0 device and then panic with:

fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x0
fault code  = supervisor write, page not present
instruction pointer = 0x8 :0xc015ca8e
stack pointer   = 0x10 :0xdd79aaac
frame pointer   = 0x10 :0xdd79aab8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def 32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL=0
current process = 19 (swi 3: cambio)
kernel: type 12 trap, code=0
Stopped at  free_hcb+0x2e:  mov1%eax,0(xedx)

When I remove the DVD/CDRW from the system it boots.

Kernel configuration is the one from R. Kevin Oberman with firewire
turned on.

--cut here for kernel conf--
#
# TYLENDEL -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files. 
# If you are in doubt as to the purpose or necessity of a line, check first 
# in NOTES.
#

machine i386
#cpuI486_CPU
#cpuI586_CPU
cpu I686_CPU
ident   TYLENDEL
maxusers0

#To statically compile in device wiring instead of /boot/device.hints
#hints  "GENERIC.hints" #Default places to look for devices.

makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols

options SCHED_4BSD  #4BSD scheduler
options INET#InterNETworking
options INET6   #IPv6 communications protocols
options FFS #Berkeley Fast Filesystem
options SOFTUPDATES #Enable FFS soft updates support
options UFS_ACL #Support for access control lists
options UFS_DIRHASH #Improve performance on big directories
#optionsMD_ROOT #MD is a potential root device
#optionsNFSCLIENT   #Network Filesystem Client
#optionsNFSSERVER   #Network Filesystem Server
#optionsNFS_ROOT#NFS usable as /, requires NFSCLIENT
options MSDOSFS #MSDOS Filesystem
options CD9660  #ISO 9660 Filesystem
options PROCFS  #Process filesystem (requires PSEUDOFS)
options PSEUDOFS#Pseudo-filesystem framework
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options COMPAT_FREEBSD4 #Compatible with FreeBSD4
options SCSI_DELAY=5000 #Delay (in ms) before probing SCSI
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
#optionsAHC_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~128k to driver.
#optionsAHD_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~215k to driver.
options CPU_ENABLE_SSE  # For MPlayer and others
options GEOM_BDE# Enable encrypted partitions

# Debugging for use in -current
options DDB #Enable the kernel debugger
#optionsINVARIANTS  #Enable calls of extra sanity

Re: recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30

2003-08-27 Thread Lee Damon

The fun of getting digests.  Roughly 30 seconds after sending my
email I saw the message about atapicam from Kenneth to Martin.

Removing atapicam from my kernel configuration fixed the problem
for me as well.

nomad

>Subject: Re: Kernel panic with CAM on current (fatal trap 12)
>From: "Kenneth D. Merry" <[EMAIL PROTECTED]>
>Date: Wed, 27 Aug 2003 11:53:28 -0600 (10:53 PDT)
>To: Martin <[EMAIL PROTECTED]>
>Cc: FreeBSD Current <[EMAIL PROTECTED]>
>
>On Wed, Aug 27, 2003 at 16:54:05 +0200, Martin wrote:
>> On Wed, 2003-08-27 at 02:27, Kenneth D. Merry wrote:
>> > There are known problems with atapicam.
>> > 
>> > Try enabling DDB in your kernel config, and get a stack trace.  If you're
>> > panicing in free_hcb(), disable atapicam and try again.
>> 
>> Yes. I did exactly as you said and I got panic in free_hcb(). I disabled
>> atapicam and now it does not panic anymore.
>> 
>> And now? :)
>
>Wait for Thomas or someone else to fix the problem.
>
>Ken
>-- 
>Kenneth Merry
>[EMAIL PROTECTED]
>
>3.31.  recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30
>Subject: recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30
>   laptop
>From: Lee Damon <[EMAIL PROTECTED]>
>Date: Wed, 27 Aug 2003 10:55:05 -0700
>To: [EMAIL PROTECTED]
>
>: || tylendel.castle.org [10] ; uname -a
>FreeBSD tylendel.castle.org 5.1-CURRENT FreeBSD 5.1-CURRENT #38: Wed Aug 27 09:05:21 
>PDT 2003 [EMAIL 
>PROTECTED]:/users/FreeBSD-5.0/obj/users/FreeBSD-5.0/src/sys/TYLENDEL  i386
>
>The kernel I compiled on 20 AUG recognizes acd0 and loggs the following:
>
>Aug 27 08:24:10 tylendel kernel: acd0: CD-RW  at ata1-master U
>DMA33
>Aug 27 08:24:10 tylendel kernel: cd0 at ata1 bus 0 target 0 lun 0
>Aug 27 08:24:10 tylendel kernel: cd0:  Removable
> CD-ROM SCSI-0 device 
>Aug 27 08:24:10 tylendel kernel: cd0: 33.000MB/s transfers
>Aug 27 08:24:10 tylendel kernel: cd0: Attempt to query device size failed: NOT R
>EADY, Medium not present - tray closed
>
>However, kernels compiled since Monday's SUP get as far as the initial
>discovery of the acd0 device and then panic with:
>
>   fatal trap 12: page fault while in kernel mode
>   fault virtual address   = 0x0
>   fault code  = supervisor write, page not present
>   instruction pointer = 0x8 :0xc015ca8e
>   stack pointer   = 0x10 :0xdd79aaac
>   frame pointer   = 0x10 :0xdd79aab8
>   code segment= base 0x0, limit 0xf, type 0x1b
>   = DPL 0, pres 1, def 32 1, gran 1
>   processor eflags= interrupt enabled, resume, IOPL=0
>   current process = 19 (swi 3: cambio)
>   kernel: type 12 trap, code=0
>   Stopped at  free_hcb+0x2e:  mov1%eax,0(xedx)
>   
>When I remove the DVD/CDRW from the system it boots.
>
>Kernel configuration is the one from R. Kevin Oberman with firewire
>turned on.

nomad
 ---
The cry has been that when war is declared, all opposition should
therefore be hushed.  A sentiment more unworthy of a free country could
hardly be propagated.  If the doctrine be admitted, rulers have only to
declare war and they are screened at once from scrutiny ...  In war,
then, as in peace, assert the freedom of speech and of the press.
Cling to this as the bulwark of all our rights and privileges.
-- William Ellery Channing

 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\

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

Re: recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30

2003-08-28 Thread Lee Damon

> > Removing atapicam from my kernel configuration fixed the problem
> > for me as well.
> Please try the patch I posted on -current under "HEADS UP! ATAng
> committed".

I just finished a new CVSup and kernel/world compile, rebooted and
everything is happy, including reading CDs and data DVDs.  I haven't
tried a movie yet because I don't have any in my office.

nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\


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

atapicam0: timeout waiting for ATAPI ready (5.1-CURRENT, IBM T30)

2003-09-05 Thread Lee Damon

Yesterday's cvsup'd and compiled kernel hung at
acd0: CDRW  at ata1-master UDMA33
atapicam0: timeout waiting for ATAPI ready (5.1-current, IBM T30)

I waited until today and did another cvsup, same problem.

What I expect to see is:

acd0: CDRW  at ata1-master UDMA33
Mounting root from ufs:/dev/ad0s1a

It does this if there is a CD in the drive as well as when there isn't.

Removing atapicam from the kernel def and recompile removed the hang.

: || tylendel.castle.org [4] ; uname -a
FreeBSD tylendel.castle.org 5.1-CURRENT FreeBSD 5.1-CURRENT #48: Fri Sep  5 
10:53:09 PDT 2003 [EMAIL PROTECTED]:/users/FreeBSD-5.0/obj/users/Fre
eBSD-5.0/src/sys/TYLENDEL  i386

nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\


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

system hang on boot w/ "atapicam0: timeout waiting for ATAPI ready" (5.1-CURRENT, IBM T30)

2003-09-15 Thread Lee Damon

As reported on Fri, 05 Sep 2003, I am seeing a hang on boot when I
have the CD-RW/DVD installed in my T30's ultrabay.  When I remove
the drive the system boots fine.  Having a CD in the drive does not
help.  The system hangs hard enough that I have to hit the power
button to get it's attention.

Is anyone else seeing this?

: || tylendel.castle.org [2] ; uname -a
FreeBSD tylendel.castle.org 5.1-CURRENT FreeBSD 5.1-CURRENT #56: Mon Sep 15 09:00:54 
PDT 2003 [EMAIL 
PROTECTED]:/users/FreeBSD-5.0/obj/users/FreeBSD-5.0/src/sys/TYLENDEL  i386


thanks,
nomad

>Yesterday's cvsup'd and compiled kernel hung at
>   acd0: CDRW  at ata1-master UDMA33
>   atapicam0: timeout waiting for ATAPI ready
>
>I waited until today and did another cvsup, same problem.
>
>What I expect to see is:
>
>   acd0: CDRW  at ata1-master UDMA33
>   Mounting root from ufs:/dev/ad0s1a
>
>It does this if there is a CD in the drive as well as when there isn't.
>
>Removing atapicam from the kernel def and recompile removed the hang.
>
>: || tylendel.castle.org [4] ; uname -a
>FreeBSD tylendel.castle.org 5.1-CURRENT FreeBSD 5.1-CURRENT #48: Fri Sep  5 
>10:53:09 PDT 2003 [EMAIL 
>PROTECTED]:/users/FreeBSD-5.0/obj/users/FreeBSD-5.0/src/sys/TYLENDEL  i386

nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: system hang on boot w/ "atapicam0: timeout waiting for ATAPI ready" (5.1-CURRENT, IBM T30)

2003-09-16 Thread Lee Damon

>> >Yesterday's cvsup'd and compiled kernel hung at
>> >acd0: CDRW  at ata1-master UDMA33
>> >atapicam0: timeout waiting for ATAPI ready
>
>This is from the low-level ATA layer. Do you see the same message if you
>disable ATAPICAM?

If I remove ATAPICAM from the kernel the system boots normally with
no timeout messages.

nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

boot hang: "ata1: resetting devices .. done" (5.1-CURRENT, IBM T30)

2003-10-07 Thread Lee Damon

Recently I posted about boot hangs if I have atapicam defined in the
kernel and a DVD/CD-RW drive in the ultrabay on my T30.

As of today's CVSup, I get a hang on boot if the drive is in there
regardless of atapicam being defined or not.

ad0: 38154MB  [77520/16/63] at ata0-master UDMA100
ata1: resetting devices ..
done

Then it hangs so hard I have to power cycle it to get the system to notice
me.

The hang does not happen if the DVD/CD-RW drive is pulled from the system.

Booting an old kernel (previous to this problem) and searching the logs, I see:
Oct  7 12:46:24 tylendel kernel: atapci0:  
port 0x1860-0x186f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 
31.1 on pci0
Oct  7 12:46:24 tylendel kernel: ata0: at 0x1f0 irq 14 on atapci0
Oct  7 12:46:24 tylendel kernel: ata0: [MPSAFE]
Oct  7 12:46:24 tylendel kernel: ata1: at 0x170 irq 15 on atapci0
Oct  7 12:46:24 tylendel kernel: ata1: [MPSAFE]

and
Oct  7 12:46:24 tylendel kernel: GEOM: create disk ad0 dp=0xc5beb670
Oct  7 12:46:24 tylendel kernel: ad0: 38154MB  
[77520/16/63] at ata0-master UDMA100
Oct  7 12:46:24 tylendel kernel: acd0: CDRW  at ata1-master 
UDMA33

I'd really appreciate any help that could be tossed my direction.

thanks,
nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\


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

Re: Locks up with CURRENT

2003-10-11 Thread Lee Damon

I'm having exactly the same hang on my IBM T30.  I just tried sos' patch
to ata-lowlevel.c but the result was no change - it still hangs after the 
  ata1: resetting devices..
  done
message.  In the recent past I was able to boot if atapicam was
not configured in the kernel, but now I can't boot regardless of
the configuration of atapicam.  I have to remove the CD-RW/DVD ROM
drive from the system to boot.  The drive label says it's a Panasonic
UJDA720 (probably IBM's part number).

nomad

>Subject: Re: Locks up with CURRENT
>From: Sam Leffler <[EMAIL PROTECTED]>
>Date: Sat, 11 Oct 2003 10:31:19 -0700
>To: Antony T Curtis <[EMAIL PROTECTED]>,
>   [EMAIL PROTECTED]
>
>On Saturday 11 October 2003 03:20 am, Antony T Curtis wrote:
>> On Sat, 2003-10-11 at 10:36, Antony T Curtis wrote:
>> > Hi, I cvsuped at about 10/10/03 11PM GMT and rebuilt world and kernel.
>> >
>> > It locks up after displaying:
>> >
>> > GEOM: create disk ad0 dp=0xc456d370
>> > ad0: 28615MB  [58140/16/63] at ata0-master UDMA100
>> > ata1: resetting devices ..
>> > done
>> >
>> > System is a Toshiba Satellite 2455 notebook.
>>
>> Removing the CDRW drive allowed it to boot
>
>I suspect this is the same problem I've encountered with a Toshiba DVD/CDRW
>drive on a ServerWorks CSB5 controller.  The following change re-enables some
>code to workaround a missed interrupt and allows my system to boot::
>
>diff ./ata-queue.c /data/devel/netperf/dev/ata/ata-queue.c
>319c319
>< #if 0
>---
>> #if 1
>
>However the Toshiba drive is not recognized.  If after booting I do:
>
>atacontrol reinit 1
>
>I sometimes get the drive properly probed.  sos sent me the following change
>to try but I still haven't gotten to it.  Beware that it's probably out of
>date wrt current source:
>
>Index: ata-lowlevel.c
>===
>RCS file: /home/ncvs/src/sys/dev/ata/ata-lowlevel.c,v
>retrieving revision 1.16
>diff -u -r1.16 ata-lowlevel.c
>--- ata-lowlevel.c  20 Sep 2003 08:38:33 -  1.16
>+++ ata-lowlevel.c  26 Sep 2003 06:50:29 -
>@@ -527,7 +527,8 @@
> ATA_IDX_OUTB(ch, ATA_ALTSTAT, ATA_A_IDS | ATA_A_RESET);
> DELAY(1);
> ATA_IDX_OUTB(ch, ATA_ALTSTAT, ATA_A_IDS);
>-DELAY(1);
>+DELAY(10);
>+ATA_IDX_INB(ch, ATA_ERROR);
>
> /* wait for BUSY to go inactive */
> for (timeout = 0; timeout < 310; timeout++) {
>
>   Sam


nomad
 ---
The cry has been that when war is declared, all opposition should
therefore be hushed.  A sentiment more unworthy of a free country could
hardly be propagated.  If the doctrine be admitted, rulers have only to
declare war and they are screened at once from scrutiny ...  In war,
then, as in peace, assert the freedom of speech and of the press.
Cling to this as the bulwark of all our rights and privileges.
-- William Ellery Channing

 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\



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

Re: boot hang: "ata1: resetting devices .. done" (5.1-CURRENT, IBMT30)

2003-10-13 Thread Lee Damon

> > > > Backing out the most recent checkin to sys/dev/ata/ata-queue.c (i.e.
> > > > reverting to version 1.6) makes the problem go away.
> > > I upgraded from an Oct 1 -> Oct 12 kernel and saw the same hang.
> > > Backing out r1.6 fixed it for me too.
> Anyone tried going forward to 1.8?

I just tried 1.8, it did not fix the problem.  Symtoms are still the same,

> > ad0: 35174MB  [71465/16/63] at ata0-master UDMA100
> > ata1: resetting devices ..
> > done

Going back to 1.6 (apparently) does fix the problem.

nomad
 ---
The cry has been that when war is declared, all opposition should
therefore be hushed.  A sentiment more unworthy of a free country could
hardly be propagated.  If the doctrine be admitted, rulers have only to
declare war and they are screened at once from scrutiny ...  In war,
then, as in peace, assert the freedom of speech and of the press.
Cling to this as the bulwark of all our rights and privileges.
-- William Ellery Channing

 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\



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

Re: boot hang: "ata1: resetting devices .. done" (5.1-CURRENT, IBMT30)

2003-10-14 Thread Lee Damon

> > > Anyone tried going forward to 1.8?
> > I just tried 1.8, it did not fix the problem.  Symtoms are still the same,

I noticed that ata-queue.c had a .rej so in a fit of "lets make sure
everything is valid"ness I deleted my /usr/src tree and re-sup'd the
entire thing, then built.

Between that and the 1.9 version of ata-queue.c, both of the problems
(the hang with ata1: resetting and the hang if atapicam is defined
in the kernel) I had been reporting have been cleared up.

Now if I could just get this darned T30 to sleep properly, all would be
wonderful. :)

nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\


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

Re: Bluetooth on IBM T30 (USB device problem)

2003-03-26 Thread Lee Damon

Hi Max,

Kernel recompiled and now no more "_mtx_assert undefined" errors. 
Continuing with the directions at <http://www.oook.cz/bsd/bluetooth.html>:

When I press the T30's bluetooth button I get the known USB problem, 
but never see the ubt0 device defined.  Instead of getting

ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2
ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3;
  wMaxPacketSize=49; nframes=6, buffer size=294

I get dead silence.  Grep'ing for it in dmesg renders:

: || tylendel.castle.org [8] ; dmesg | grep ubt
Preloaded elf module "/boot/kernel/ng_ubt.ko" at 0xc06e60a8.

I am presuming pressing the bluetooth button is like adding a bluetooth
USB device but I am lacking in actual real knowledge here.  Their
documentation has things like "Power on the BDC by pressing Bluetooth power 
switch if the Bluetooth LED is off." (BDC = Bluetooth Daughter Card).
When I press the button the LED does not come on.  If I press and
hold the button the LED will eventually flash once and then I get the
"uhub2: device problem, disabling port 1" message on the console yet again.

In searching IBM's documentation I found that they have updated firmware 
for the BDC, but you have to be running windows to install it. :/  

Kernel source was sup'd Monday evening, US Pacific time.  Bluetooth
bundle is ngbt-fbsd-20030305.tar.gz.

I went ahead and tried to run rc.bluetooth start ubt0 in debug mode
and got pretty much what you'd expect when the device isn't there:

+ logger=/usr/bin/logger -i -s -p user.err
+ kldstat=/sbin/kldstat
+ kldload=/sbin/kldload
+ sysctl=/sbin/sysctl
+ ngctl=/usr/sbin/ngctl
+ hcseriald=/usr/sbin/hcseriald
+ hccontrol=/usr/sbin/hccontrol
+ hci_debug_level=3
+ l2cap_debug_level=3
+ [ 2 -lt 2 ]
+ startstop=start
+ shift
+ dev=ubt0
+ shift
+ load_module ng_bluetooth
+ module=ng_bluetooth
+ shift
+ /sbin/kldstat -n ng_bluetooth
+ [ 1 -ne 0 ]
+ /sbin/kldload ng_bluetooth
+ [ 0 -ne 0 ]
+ load_module ng_hci
+ module=ng_hci
+ shift
+ /sbin/kldstat -n ng_hci
+ [ 1 -ne 0 ]
+ /sbin/kldload ng_hci
+ [ 0 -ne 0 ]
+ load_module ng_l2cap
+ module=ng_l2cap
+ shift
+ /sbin/kldstat -n ng_l2cap
+ [ 1 -ne 0 ]
+ /sbin/kldload ng_l2cap
+ [ 0 -ne 0 ]
+ load_module ng_btsocket
+ module=ng_btsocket
+ shift
+ /sbin/kldstat -n ng_btsocket
+ [ 1 -ne 0 ]
+ /sbin/kldload ng_btsocket
+ [ 0 -ne 0 ]
+ ./src/share/examples/netgraph/bluetooth/rc.bluetooth stop ubt0
+ hook=hook
+ expr ubt0 : ubt\([0-9]\{1,\}\)
+ unit=0
+ [ -z 0 ]
+ setup_stack ubt0 hook
+ dev=ubt0
+ shift
+ hook=hook
+ shift
+ /usr/sbin/ngctl mkpeer ubt0: hci hook drv
ngctl: send msg: No such file or directory
+ exit 1

nomad

> Lee Damon wrote:
> > first pass at trying to follow Pav's directions.  I get as far as trying
> > to run rc.bluetooth and get the following in syslog:
> > 
> > Mar 26 11:18:34 tylendel kernel: link_elf: symbol _mtx_assert undefined
> > Mar 26 11:18:34 tylendel nomad[576]: Failed to load ng_btsocket
> 
> your kernel options do not match options in Makefile. please
> 
> 1) edit snapshot Makefile's for the modules and remove
> -DWITNESSxxx and -DINVARIANTxxx
> 
> or
> 
> 2) add options WITNESS, options WITNESS_SKIPSPIN,
> options INVARIANTS and options INVARIANTS_SUPPORT to
> your kernel config.
> 
> this is an intergration issue. i use this option to catch
> locking bugs. once code is commited this will be resolved
> automatically. some people choose to disable them because
> it improves performance.
> 
> thanks,
> max
> 
nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\

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

Re: Bluetooth on IBM T30 (USB device problem)

2003-03-26 Thread Lee Damon

Max,
(Copied to current as Max requests)

ugen is loaded at boot by default.  When I try to manually load it I get the
(expected) response:

Mar 26 16:46:47 tylendel kernel: module_register: module uhub/ugen already 
exists!
Mar 26 16:46:47 tylendel kernel: Module uhub/ugen failed to register: 17

However, the BDC isn't attaching when I press the bluetooth button.

: || tylendel.castle.org [17] ; sudo usbdevs -v -d
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), 
Intel(0x), rev 1.00
  uhub0
 port 1 powered
 port 2 powered
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), 
Intel(0x), rev 1.00
  uhub1
 port 1 powered
 port 2 powered
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), 
Intel(0x), rev 1.00
  uhub2
 port 1 powered
 port 2 powered


So, we're back to the USB problem.  I think maybe I should table this for a
while in the hopes that someone, somewhere, looks at and fixes the USB
problem.  (I'll be happy to help run tests and such, but I am *not* a kernel
hacker.)

nomad

> Lee,
> 
> > Kernel recompiled and now no more "_mtx_assert undefined" errors. 
> > Continuing with the directions at :
> > 
> > When I press the T30's bluetooth button I get the known USB problem, 
> > but never see the ubt0 device defined.  Instead of getting
> > 
> > ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2
> > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3;
> >   wMaxPacketSize=49; nframes=6, buffer size=294
> > 
> > I get dead silence.  Grep'ing for it in dmesg renders:
> > 
> > : || tylendel.castle.org [8] ; dmesg | grep ubt
> > Preloaded elf module "/boot/kernel/ng_ubt.ko" at 0xc06e60a8.
> 
> Of course. Because ng_ubt(4) driver *does not* know about Bluetooth
> device inside your T30. That is why you need to find out VendorID and
> Product ID for the Bluetooth device inside your T30. You can use
> ugen(4) for that. ugen(4) driver *must* be loaded *before* you press
> the Bluetooth button. Once you press the Bluetooth button ugen(4)
> driver *must* attach to it, because it is the default driver for
> the USB devices. That is *if* USB will attach the device and you
> do not get "device problem, disabling port 1" error.
> 
> Once you have ugen(4) attached to the device run
> 
> # usbdevs -v -d
> 
> This will give you VendorID/ProductID pair. Now you are ready to
> patch ng_ubt(4) driver. Just add VendorID/ProductID to the list
> of supported devices inside USB_MATCH function (in ng_ubt.c file).
> 
> Now
> 
> 1) Recompile ng_ubt(4) module
> 2) Turn off your Bluetooth device
> 3) unload ng_ubt(4) (and ugen(4) if you loaded it by hand)
> 4) load *new* ng_ubt(4) driver
> 5) Press the Bluetooth button to activate device
> 
> If everything is working then you should get the messages from the
> ng_ubt(4) driver.
> 
> > I am presuming pressing the bluetooth button is like adding a bluetooth
> > USB device but I am lacking in actual real knowledge here.  Their
> 
> right, i think it more like plugging a new USB device.
> 
> > documentation has things like "Power on the BDC by pressing Bluetooth power 
> > switch if the Bluetooth LED is off." (BDC = Bluetooth Daughter Card).
> > When I press the button the LED does not come on.  If I press and
> > hold the button the LED will eventually flash once and then I get the
> > "uhub2: device problem, disabling port 1" message on the console yet again.
> 
> Well, it seem like when LED is on then the device is plugged, but you
> still getting the "device problem, disabling port 1" message and that
> means USB stack/hub *did not* attach/activate the device and hence no
> driver was attached to it.
> 
> You *must* get the device to attach, otherwise you can not use the
> driver. For now just try to make ugen(4) attach to the device. Once
> you get the ugen(4) to recognize the device then you should move to
> ng_ubt(4).
> 
> > In searching IBM's documentation I found that they have updated firmware 
> > for the BDC, but you have to be running windows to install it. :/  
> > 
> > Kernel source was sup'd Monday evening, US Pacific time.  Bluetooth
> > bundle is ngbt-fbsd-20030305.tar.gz.
> 
> It all does not matter at this point. Again USB *did not* attach (and
> activate) the device. The firmware inside the card and other stuff does
> not event come into play.  The simple fact that you have plugged device
> into hub does not indicate that device is working.
> 
> > I went ahead and tried to run rc.bluetooth start ubt0 in debug mode
> > and got pretty much what you'd expect when the device isn't there:
> 
> [...]
> 
> > + setup_stack ubt0 hook
> > + dev=ubt0
> > + shift
> > + hook=hook
> > + shift
> > + /usr/sbin/ngctl mkpeer ubt0: hci hook drv
> > ngctl: send msg: No such file or directory
> > + exit 1
> 
> No devic

Re: Bluetooth on IBM T30 (USB device problem)

2003-03-26 Thread Lee Damon

I'm playing with Bluetooth on my T30 as well.  I've activated legacy
USB support in BIOS, but still get

   Mar 26 08:41:03 tylendel kernel: uhub2: device problem, disabling port 1

maybe 45-60 seconds after pressing the Bluetooth button.

I'm running a kernel and world sup'd yesterday afternoon.  ugen is
included in the kernel config.   I will be heading to the archives 
of the mobile list in a second to see if I'm missing anything else.

nomad

> --On Tuesday, March 25, 2003 13:25:47 -0800 Maksim Yevmenkin 
> <[EMAIL PROTECTED]> wrote:
> 
> > Tobias,
> >
> >>> yes it is a CSR chip based device. can you tell if its a USB device?
> >>
> >> yes, it is usb. windows clearly states it as usb.
> >
> > good. then you will most likely get it to work. if you
> > get it to attach (see below).
> >
> >>> 1) at loader prompt type (without quotes) "boot -v"
> >>> 2) do not press the Bluetooth button just yet
> >>> 3) wait until system is fully loaded
> >>> 4) kldload ugen (this is only required if you do not have
> >>>   "device ugen" the in the kernel config file)
> >>> 5) press the Bluetooth button
> >>
> >> did 1), then 5)
> >>
> >> ugen did not attach, instead I got an error. see the attached
> >> files, the error is at the bottom of dmesg.
> >
> > Mar 25 21:59:36 angel5 kernel: uhub2: device problem, disabling port 1
> I had a similar (USB) issue on my Fujitsu Laptop, until I **ENABLED** the 
> USB Floppy
> option in my BIOS.  Don't ask me why that fixed it, but ANY USB device I 
> plugged in would
> garner the above response without that option being set.
> 
> Just another data point.  (BTW, 4-STABLE, if it matters).
> 
> 
> 
> 
> 
> -- 
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
> US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
> 
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\


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

IBM T30 USB issue: kernel: uhub2: device problem, disabling port 1

2003-04-01 Thread Lee Damon

I've just sup'd a completely clean source tree and compiled a new
kernel and world.  My kernconf is the generic one with pcm and apm
turned on.  apci is turned off in the hints file (because it breaks
the mouse).  I have INVARIANTS, DDB, and WITNESS turned off right now, for
speed.

When I try to activate a Bluetooth USB device, I get the following error:
  Apr  1 09:57:26 tylendel kernel: uhub2: device problem, disabling port 1

I am reasonably convinced it isn't a problem with the bluetooth daughter
card (but can be convinced otherwise, of course).

I'd be happy to work with any USB/Kernel experts to try to get this working.
Just let me know what you need me to do.  (I am not now, and never have been,
a kernel hacker.)  I can recompile the kernel with INVARIANTS &co turned
on if that would be helpful.

thanks,
nomad
 ---
The cry has been that when war is declared, all opposition should
therefore be hushed.  A sentiment more unworthy of a free country could
hardly be propagated.  If the doctrine be admitted, rulers have only to
declare war and they are screened at once from scrutiny ...  In war,
then, as in peace, assert the freedom of speech and of the press.
Cling to this as the bulwark of all our rights and privileges.
-- William Ellery Channing

 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\



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

Re: IBM T30 USB issue: kernel: uhub2: device problem, disabling port 1

2003-04-05 Thread Lee Damon

I just doubled USB_PORT_POWERUP_DELAY from 300 to 600.  Same problem when
I hit the bluetooth button.   All tests have been done with the laptop
running on AC line feed.  I doubt it's related, but this system is
using APM because ACPI doesn't work right yet.


Apr  5 11:32:17 tylendel kernel: uhub2: device problem, disabling port 1

FreeBSD tylendel.castle.org 5.0-CURRENT FreeBSD 5.0-CURRENT #4: Sat Apr  5 
10:07:16 PST 2003 [EMAIL PROTECTED]:/users/FreeBSD-5.0/obj/users/Fre
eBSD-5.0/src/sys/TYLENDEL  i386

Sources were sup'd 3 APR, 15:53 PST

nomad

> On Tue, Apr 01, 2003 at 10:02:47AM -0800, Lee Damon wrote:
> > I've just sup'd a completely clean source tree and compiled a new
> > kernel and world.  My kernconf is the generic one with pcm and apm
> > turned on.  apci is turned off in the hints file (because it breaks
> > the mouse).  I have INVARIANTS, DDB, and WITNESS turned off right now, for
> > speed.
> > 
> > When I try to activate a Bluetooth USB device, I get the following error:
> >   Apr  1 09:57:26 tylendel kernel: uhub2: device problem, disabling port 1
> > 
> > I am reasonably convinced it isn't a problem with the bluetooth daughter
> > card (but can be convinced otherwise, of course).
> 
> This is a problem with the connected device.
> My expirience about this is that such devices have bad oscillator
> designs and notebooks tend to have a worse power quality - especialy
> when running on batteries.
> I asume that most of this device work if you give them more time to
> get ready after connecting than required by specs.
> It seems that we already wait longer than required, but you can try
> to increase USB_PORT_POWERUP_DELAY in src/sys/dev/usb/usb.h a bit more.
> 
> -- 
> B.Walter   BWCThttp://www.bwct.de
> [EMAIL PROTECTED]  [EMAIL PROTECTED]
> 
nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\


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

Re: IBM T30 bluetooth - success

2003-06-16 Thread Lee Damon

I can second that success.  Any chance of getting this patch checked in?

thanks,
nomad

Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), 
Intel(0x), rev 1.00
  uhub2
 port 1 addr 2: full speed, power 200 mA, config 1, IBM Integrated 
Bluetooth(0x0310), TDK(0x04bf), rev 1.15
   ubt0
 port 2 powered


> Index: usb_subr.c
> ===
> RCS file: /home/ncvs/src/sys/dev/usb/usb_subr.c,v
> retrieving revision 1.54
> diff -u -r1.54 usb_subr.c
> --- usb_subr.c14 Jan 2003 23:07:43 -  1.54
> +++ usb_subr.c14 Jun 2003 16:01:38 -
> @@ -964,6 +964,7 @@
>   usbd_device_handle dev;
>   struct usbd_device *hub;
>   usb_device_descriptor_t *dd;
> + usb_port_status_t ps;
>   usbd_status err;
>   int addr;
>   int i;
> @@ -1020,12 +1021,14 @@
>   up->device = dev;
>   dd = &dev->ddesc;
>   /* Try a few times in case the device is slow (i.e. outside specs.) */
> - for (i = 0; i < 3; i++) {
> + for (i = 0; i < 15; i++) {
>   /* Get the first 8 bytes of the device descriptor. */
>   err = usbd_get_desc(dev, UDESC_DEVICE, 0, USB_MAX_IPACKET, dd);
>   if (!err)
>   break;
>   usbd_delay_ms(dev, 200);
> + if ((i & 3) == 3)
> + usbd_reset_port(up->parent, port, &ps);
>   }
>   if (err) {
>   DPRINTFN(-1, ("usbd_new_device: addr=%d, getting first desc "
> 
nomad
 ---   - Lee "nomad" Damon -  \
play: [EMAIL PROTECTED]or castle!nomad  \
work: [EMAIL PROTECTED]   \
/\
Seneschal, Castle PAUS./  \
"Celebrate Diversity" /\


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

Re: My wi(4) ate itself (or Fun with no memory).

5.0 on IBM T30: X11 failure

Re: IBM T30 bluetooth - success (fwd)

recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30laptop

Re: recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30

Re: recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30

atapicam0: timeout waiting for ATAPI ready (5.1-CURRENT, IBM T30)

system hang on boot w/ "atapicam0: timeout waiting for ATAPI ready" (5.1-CURRENT, IBM T30)

Re: system hang on boot w/ "atapicam0: timeout waiting for ATAPI ready" (5.1-CURRENT, IBM T30)

boot hang: "ata1: resetting devices .. done" (5.1-CURRENT, IBM T30)

Re: Locks up with CURRENT

Re: boot hang: "ata1: resetting devices .. done" (5.1-CURRENT, IBMT30)

Re: boot hang: "ata1: resetting devices .. done" (5.1-CURRENT, IBMT30)

Re: Bluetooth on IBM T30 (USB device problem)

Re: Bluetooth on IBM T30 (USB device problem)

Re: Bluetooth on IBM T30 (USB device problem)

IBM T30 USB issue: kernel: uhub2: device problem, disabling port 1

Re: IBM T30 USB issue: kernel: uhub2: device problem, disabling port 1

Re: IBM T30 bluetooth - success

19 matches

Site Navigation

Mail list logo

Footer information