Just to add to what I wrote at the end of October:
> Anyway, under FreeBSD-4 with kernel modules built 10.August
> from source that I believe is based on FreeBSD-5-current of
> that era, I'm seeing corruption of data read from umass
> devices attached to an OHCI controller card. Use of a UHCI
>
Hi Guys;
As always, if this list is not the right place, please forgive me.
I have two machines:
1) Free 4.10 / mysql (5.0.0) listening on port 5006
2) Free 5.3 Release / mysql (5.0.0) listening on port 5007
On both, no firewalls, blocks or anything of that sort. Both machines have the
same c
Hello,
I am not aware whether this is the right mailing list -so pl. advise
where to send in my request if it isn't. I am running Freebsd 5.2.1
I have sources from CD on my /usr/src -and want to upgrade to Stable 5.3.
I downloaded CVSup and the supfile to get RELENG_5_3. I found that it
does no
Yeah, it is the only one on that port. The worst part is that the connection
attempt doesn´t even
generates a log entry !! I looked into the log also !!
netstat -an | grep LIST
tcp4 0 0 *.5007 *.*LISTEN
tcp4 0 0 *.199 *
Hi,
I've got a new USB driver (with OHCI isoc fixed). You need FreeBSD 5.2/5.3 to
get it compiled.
You might be able to get it compiled on FreeBSD 4.x, but you will need to to
some hacking.
For example you need to add to dev/usb2/usb_port.h :
#ifndef MTX
#define MTX
struct mtx { int s; u_int8_t
Just for the record, the problem is solved. It was indeed a
misconfiguration at the next hop, at the provider.
Thank you.
With respect,
--
Claudiu Dragalina-Paraipan
[EMAIL PROTECTED]
signature.asc
Description: OpenPGP digital signature
Sorry for this :( . Correction marked with " <= "
I typed a my.cnf from another machine. only the port differs.
==
Yeah, it is the only one on that port. The worst part is that the connection
attempt doesn´t even
generates a log entry !! I looked into the log also !!
netsta
hrmm.
Can you try switching the port to another port number? Perhaps a lower port
number?
See if you can get it to connect in that way?
In your log file, does it print messages about having successfully started
up?
Do you have ipfw or any other packet filter on your machine?
- Original Messa
Hi Arun;
> hrmm.
> Can you try switching the port to another port number? Perhaps a lower port
> number?
> See if you can get it to connect in that way?
Makes no difference
> In your log file, does it print messages about having successfully started
> up?
Yes, it does. Like I said, if I use mys
On Mon, Nov 29, 2004 at 08:05:39PM -0500, [EMAIL PROTECTED] wrote..
> After a bunch of frustrating debugging, I've tenatively come to the
> conclusion that the isp(4) driver is not 64 bit safe --- at the very
> least insofar as the amd64 platform is concerned.
Side note: isp(4) has been in use fo
On Tuesday 30 November 2004 11:39 am, Wilko Bulte wrote:
> On Mon, Nov 29, 2004 at 08:05:39PM -0500, [EMAIL PROTECTED]
> wrote..
>
> > After a bunch of frustrating debugging, I've tenatively come to the
> > conclusion that the isp(4) driver is not 64 bit safe --- at the
> > very least insofar as th
On Tue, Nov 30, 2004 at 12:22:23PM -0800, Peter Wemm wrote..
> On Tuesday 30 November 2004 11:39 am, Wilko Bulte wrote:
> > On Mon, Nov 29, 2004 at 08:05:39PM -0500, [EMAIL PROTECTED]
> > wrote..
> >
> > > After a bunch of frustrating debugging, I've tenatively come to the
> > > conclusion that the
> "Wilko" == Wilko Bulte <[EMAIL PROTECTED]> writes:
Wilko> On Tue, Nov 30, 2004 at 12:22:23PM -0800, Peter Wemm wrote..
>> On Tuesday 30 November 2004 11:39 am, Wilko Bulte wrote: > On Mon,
>> Nov 29, 2004 at 08:05:39PM -0500, [EMAIL PROTECTED] > wrote..
>> >
>> > > After a bunch of frustrati
> "Peter" == Peter Wemm <[EMAIL PROTECTED]> writes:
Peter> On Tuesday 30 November 2004 11:39 am, Wilko Bulte wrote:
>> On Mon, Nov 29, 2004 at 08:05:39PM -0500, [EMAIL PROTECTED]
>> wrote..
>>
>> > After a bunch of frustrating debugging, I've tenatively come to
>> the > conclusion that the is
> "Wilko" == Wilko Bulte <[EMAIL PROTECTED]> writes:
Wilko> On Mon, Nov 29, 2004 at 08:05:39PM -0500, [EMAIL PROTECTED]
Wilko> wrote..
>> After a bunch of frustrating debugging, I've tenatively come to the
>> conclusion that the isp(4) driver is not 64 bit safe --- at the
>> very least insofar
On Tue, Nov 30, 2004 at 03:42:55PM -0500, David Gilbert wrote:
> I just heard back from some people still onsite. The ISP driver
> booted with everything the same except hw.physmem=2g works. It's a
> memory issue.
Try hw.physmem=4g. It should be the 4GB boundary, not 2GB boundary that
is causin
On Tuesday 30 November 2004 02:54 pm, David O'Brien wrote:
> On Tue, Nov 30, 2004 at 03:42:55PM -0500, David Gilbert wrote:
> > I just heard back from some people still onsite. The ISP driver
> > booted with everything the same except hw.physmem=2g works. It's a
> > memory issue.
>
> Try hw.physm
On Tue, 30 Nov 2004 23:40, Barry Bouwsma wrote:
> In addition, I've connected a uaudio sound device, which
> works to play audio for between 10 and 13 minutes, before
> bombing out with an error in ohci_device_isoc_enter(),
> tripping over one of the two
On a side note..
How are you testing it?
La
> "David" == David O'Brien <[EMAIL PROTECTED]> writes:
David> On Tue, Nov 30, 2004 at 03:42:55PM -0500, David Gilbert wrote:
>> I just heard back from some people still onsite. The ISP driver
>> booted with everything the same except hw.physmem=2g works. It's a
>> memory issue.
David> Try h
19 matches
Mail list logo
