Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-22 Thread Josef Karthauser
On Sat, Nov 22, 2003 at 08:08:29AM -0500, Brian F. Feldman wrote: > > > > We never did any page crossing on ohci/ehci bevor the newbus change > > took place. > > Found it!!! Definitely a problem created then... > > --- ohci.c 12 Nov 2003 01:40:11 - 1.138 > +++ ohci.c 22 Nov 2

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-22 Thread Bernd Walter
On Sat, Nov 22, 2003 at 08:08:29AM -0500, Brian F. Feldman wrote: > Found it!!! Definitely a problem created then... > > --- ohci.c 12 Nov 2003 01:40:11 - 1.138 > +++ ohci.c 22 Nov 2003 03:28:42 - > @@ -569,7 +569,7 @@ > cur->td.td_cbp = htole32(dataphys); >

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-22 Thread Brian F. Feldman
Bernd Walter <[EMAIL PROTECTED]> wrote: > On Fri, Nov 21, 2003 at 12:35:50PM -0500, Brian F. Feldman wrote: > > Doug White <[EMAIL PROTECTED]> wrote: > > > The OHCI driver is largely synced with NetBSD so you might see if they > > > have the same bug. > > > > I'll look around for a bootable NetBSD

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-21 Thread Brian F. Feldman
Bernd Walter <[EMAIL PROTECTED]> wrote: > On Fri, Nov 21, 2003 at 12:35:50PM -0500, Brian F. Feldman wrote: > > Doug White <[EMAIL PROTECTED]> wrote: > > > The OHCI driver is largely synced with NetBSD so you might see if they > > > have the same bug. > > > > I'll look around for a bootable NetBSD

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-21 Thread Bernd Walter
On Fri, Nov 21, 2003 at 12:35:50PM -0500, Brian F. Feldman wrote: > Doug White <[EMAIL PROTECTED]> wrote: > > The OHCI driver is largely synced with NetBSD so you might see if they > > have the same bug. > > I'll look around for a bootable NetBSD CD. NetBSD is different in that point. > > This m

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-21 Thread Bruce M Simpson
On Fri, Nov 21, 2003 at 09:11:33AM -0800, Doug White wrote: > The OHCI driver is largely synced with NetBSD so you might see if they > have the same bug. > > This might be the underlying wierdness we were seeing in gtetlow's > microdrive with transfers over 8k. The one-page-crossing ohci limitati

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-21 Thread Bruce M Simpson
Whoops. http://damien.bergamini.free.fr/ueagle/download.html. BMS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-21 Thread Brian F. Feldman
Doug White <[EMAIL PROTECTED]> wrote: > The OHCI driver is largely synced with NetBSD so you might see if they > have the same bug. I'll look around for a bootable NetBSD CD. > This might be the underlying wierdness we were seeing in gtetlow's > microdrive with transfers over 8k. The one-page-cr

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-21 Thread Doug White
The OHCI driver is largely synced with NetBSD so you might see if they have the same bug. This might be the underlying wierdness we were seeing in gtetlow's microdrive with transfers over 8k. The one-page-crossing ohci limitation is really annoying. On Thu, 20 Nov 2003, Brian F. Feldman wrote:

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Brian F. Feldman
"Brian F. Feldman" <[EMAIL PROTECTED]> wrote: > Thanks for the patches to try! They unfortunately didn't fix the crash I > have, but I found out why it's occurring. > > See ohci.c:1389: > if (std->td.td_cbp != 0) > len -= le32toh(std->td.td_be) - >

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Brian F. Feldman
Thanks for the patches to try! They unfortunately didn't fix the crash I have, but I found out why it's occurring. See ohci.c:1389: if (std->td.td_cbp != 0) len -= le32toh(std->td.td_be) - le32toh(std->td.td_cbp) + 1; In one

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Scott Lambert
On Thu, Nov 20, 2003 at 11:20:18AM +0100, Dag-Erling Smørgrav wrote: > Alexander Leidinger <[EMAIL PROTECTED]> writes: > > I have no problem using my printer: > > [...] > > ulpt0: Hewlett-Packard DeskJet 895C, rev 1.00/1.00, addr 4, iclass 7/1 > > ulpt0: using uni-directional mode > > Sure, I can

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Buki
On Thu, Nov 20, 2003 at 11:20:18AM +0100, Dag-Erling Sm?rgrav wrote: [snip] > > ulpt0: Hewlett-Packard officejet d series, rev 1.10/1.00, addr 3, iclass 7/1 > ulpt0: using bi-directional mode > > but it still won't print. Sometimes it works (albeit very, very > slowly) but most of the time the p

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Dag-Erling Smørgrav
Mark Dixon <[EMAIL PROTECTED]> writes: > When it works, is that when you have been using it in another operating > system, and then reboot into FreeBSD and try it? I don't think so. BTW, I just reinstalled cups to give the printer another try, and it now seems to work in -CURRENT (knock on wood)

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Mark Dixon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 20 Nov 2003 10:20, Dag-Erling Smørgrav wrote: > > Sure, I can do that: > > ulpt0: Hewlett-Packard officejet d series, rev 1.10/1.00, addr 3, iclass > 7/1 ulpt0: using bi-directional mode > > but it still won't print. Sometimes it works (al

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Dag-Erling Smørgrav
Alexander Leidinger <[EMAIL PROTECTED]> writes: > I have no problem using my printer: > [...] > ulpt0: Hewlett-Packard DeskJet 895C, rev 1.00/1.00, addr 4, iclass 7/1 > ulpt0: using uni-directional mode Sure, I can do that: ulpt0: Hewlett-Packard officejet d series, rev 1.10/1.00, addr 3, iclass

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Michel TALON
> Jeez, it's been broken a year and it's almost 5.2-RELEASE now. See for example the page for the FreeBSD eagle driver: http://damien.bergamini.free.fr/ueagle/ end notably the OHCI patches in http://damien.bergamini.free.fr/ueagle/download.html At least for the eagle USB ADSL modem, these patches

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Alexander Leidinger
On Thu, 20 Nov 2003 09:20:06 +0100 [EMAIL PROTECTED] (Dag-Erling Smørgrav) wrote: > *shrug* I have never been able to get my USB printer to work with > FreeBSD, and I gave up writing drivers for USB crypto tokens because I have no problem using my printer: ---snip--- % dmesg |grep -E '(usb|ulpt|u

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, "Brian F. Feldman" writes: >Jeez, it's been broken a year and it's almost 5.2-RELEASE now. Does anyone >have ANY leads on these problems? I know precisely nothing about how my USB >hardware is supposed to work, but this OHCI+EHCI stuff definitely doesn't, >and

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-20 Thread Dag-Erling Smørgrav
"Brian F. Feldman" <[EMAIL PROTECTED]> writes: > Jeez, it's been broken a year and it's almost 5.2-RELEASE now. Does anyone > have ANY leads on these problems? I know precisely nothing about how my USB > hardware is supposed to work, but this OHCI+EHCI stuff definitely doesn't, > and it's real

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2003-11-19 Thread Brian F. Feldman
Josef Karthauser <[EMAIL PROTECTED]> wrote: > On Sun, Nov 17, 2002 at 01:18:00PM -0500, Brian F. Feldman wrote: > > > > > ohci_alloc_std_chain+0xf5 (calling a DMAADDR() function, I believe) > > > ohci_device_bulk_start+0x0d > > > ohci_device_bulk_transfer+0x27 > > > usbd_transfer+0xc0 > > > umass_

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2002-12-19 Thread Matthew Dillon
I fixed a serious DMA physical address translation bug in OHCI today. Look on the lists today for this message. Message and patch enclosed. Note that this fixes one bug in FreeBSD's implementation and a second bug that is NetBSD/OpenBSD specific. I would appreciate it if someone w

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2002-11-17 Thread Josef Karthauser
On Sun, Nov 17, 2002 at 01:18:00PM -0500, Brian F. Feldman wrote: > > > ohci_alloc_std_chain+0xf5 (calling a DMAADDR() function, I believe) > > ohci_device_bulk_start+0x0d > > ohci_device_bulk_transfer+0x27 > > usbd_transfer+0xc0 > > umass_setup_transfer+0x4f > > umass_bbb_state > > usb_transfer_c

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2002-11-17 Thread Brian F. Feldman
Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote: > I can't get more info because crash dumps don't work when this happens, but > for what it's worth, here's a traceback which shows what happens when I > attempt to use my da0: Removable Direct Access > SCSI-2 device on an OHCI-based controlle

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2002-10-18 Thread Brian F. Feldman
Josef Karthauser <[EMAIL PROTECTED]> wrote: > Does this happen on a current with this patch applied too? I'm certain I tried this already :( -- Brian Fundakowski Feldman \'[ FreeBSD ]''\ <> [EMAIL PROTECTED] <> [EMAIL PROTECTED] \ The Power to Serve! \

Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2002-10-18 Thread Josef Karthauser
Does this happen on a current with this patch applied too? Index: usb_port.h === RCS file: /home/ncvs/src/sys/dev/usb/usb_port.h,v retrieving revision 1.58 diff -u -r1.58 usb_port.h --- usb_port.h 2 Oct 2002 07:44:20 - 1.58

kernel panic trying to utilize a da(4)/umass(4) device with ohci(4)

2002-10-06 Thread Brian Fundakowski Feldman
I can't get more info because crash dumps don't work when this happens, but for what it's worth, here's a traceback which shows what happens when I attempt to use my da0: Removable Direct Access SCSI-2 device on an OHCI-based controller. This was working just a few days ago with a UHCI contro