Hi,
>FreeBSD bart 5.1-CURRENT FreeBSD 5.1-CURRENT #2: Sat Sep 20 20:34:05 PDT
>2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BART i386
>
>I am having problems running staroffice under current. My question is is
>anyone else eperiencing this problem?
>
>The initial ports install runs fine but whe
On Sun, Sep 21, 2003 at 02:12:55AM -0400, Daniel Eischen wrote:
> On Sat, 20 Sep 2003, Kris Kennaway wrote:
>
> > On Sun, Sep 21, 2003 at 01:44:35AM -0400, Daniel Eischen wrote:
> > > > What, precisely, do you object to in the above proposal?
> > >
> > > 1, 2, and 3. I don't think backing out -p
In message: <[EMAIL PROTECTED]>
Daniel Eischen <[EMAIL PROTECTED]> writes:
: It's just a joke at my own expense. Sorry to imply otherwise.
Yea. My snapping at you was out of line. I'm just a little
frustrated and let it get the better of me. Please forgive me.
Warner
_
On Sun, 21 Sep 2003, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Daniel Eischen <[EMAIL PROTECTED]> writes:
> : Can you add a "no -pthread" symbol to it?
>
> Can you give it a rest? You made a bad call, people are giving you
> grief for it. That is not a bikeshed.
It'
On Sun, Sep 21, 2003 at 02:12:55AM -0400, Daniel Eischen wrote:
> Because when things break, people fix them. There is no
> motivation (as seen in the last 2+ years) to fix something
> that isn't broken.
>
> Please also see:
>
>
> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=321307+0+archive/
On Sat, 20 Sep 2003, Kris Kennaway wrote:
> On Sun, Sep 21, 2003 at 01:44:35AM -0400, Daniel Eischen wrote:
> > > What, precisely, do you object to in the above proposal?
> >
> > 1, 2, and 3. I don't think backing out -pthread change helps
> > much in fixing ports...
>
> Again, why? Please exp
In message: <[EMAIL PROTECTED]>
Daniel Eischen <[EMAIL PROTECTED]> writes:
: Can you add a "no -pthread" symbol to it?
Can you give it a rest? You made a bad call, people are giving you
grief for it. That is not a bikeshed.
Warner
___
[EMA
Running a recent current, I got a recursive lock panic with the lock
first acquired in net80211/ieee80211_node.c:525 and reacquired in 547.
The machine in question uses the following wi0 in hostap mode:
wi0: mem 0xcecff000-0xcecf irq 11 at device 17.0 on pci0
wi0: 802.11 address: 00:05:5d:ee
On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote:
> OK, here's what we can do to fix this:
>
> 1) Put back -pthread in -current so all the ports don't fail
>
> 2) I will build a full set of -current packages with the -pthread
> error still in place, to determine the list of packages
On Sat, 20 Sep 2003, Pawel Worach wrote:
> Hi!
>
> Last if_sk update broke buildkernel
>
> ===> sk
> rm -f .depend
> mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@
> -I@/../include /usr/src/sys/modules/sk/../../pci/if_sk.c
> /usr/src/sys/pci/if_sk.c:129:26: pci/yukonreg.h: No
On Sat, 20 Sep 2003, Bruce Mackay wrote:
>
> Hey all,
>
> I get the following hang up when I try booting up, here's the problem area...
>
> pcm0: at device 31.5 on pci0
> pcm0: unable to map IO port space
> device_probe_and_attach: pcm0 attach returned 6
>
> I'm running a CVSUP -curr
In message: <[EMAIL PROTECTED]>
John Birrell <[EMAIL PROTECTED]> writes:
: On Sun, Sep 21, 2003 at 01:07:15AM -0400, Daniel Eischen wrote:
: > But you seem to thing -pthread == NOOP unbreaks ports ;-)
:
: Warner might
It appreas to unbreak one port: icecast. It was the first port I
f
On Sun, Sep 21, 2003 at 01:44:35AM -0400, Daniel Eischen wrote:
> I don't think committing fixes for -current breakages should cause
> problems for 4.9-RELEASE (especially with the caveat that they be
> compile tested on -stable). Out of curiosity, what's the reason
> the tag can't be laid now?
FreeBSD bart 5.1-CURRENT FreeBSD 5.1-CURRENT #2: Sat Sep 20 20:34:05 PDT
2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BART i386
I am having problems running staroffice under current. My question is is
anyone else eperiencing this problem?
The initial ports install runs fine but when running s
On Sun, 21 Sep 2003, Brad Knowles wrote:
> At 1:29 AM -0400 2003/09/21, Daniel Eischen wrote:
>
> > Can you add a "no -pthread" symbol to it?
>
> I could do up an ash grey t-shirt with slightly modified graphics.
>
> What would a "no -pthread" symbol look like?
I'd imagine a threa
On Sun, Sep 21, 2003 at 03:15:25PM +1000, John Birrell wrote:
> On Sun, Sep 21, 2003 at 01:07:15AM -0400, Daniel Eischen wrote:
> > But you seem to thing -pthread == NOOP unbreaks ports ;-)
>
> Warner might, but Kris doesn't. Kris is asking for the -pthread option
> to be restored to let -current
On Sat, 20 Sep 2003, Kris Kennaway wrote:
> On Sun, Sep 21, 2003 at 01:04:49AM -0400, Daniel Eischen wrote:
> > On Sat, 20 Sep 2003, Kris Kennaway wrote:
> >
> > > On Sat, Sep 20, 2003 at 08:43:18PM -0400, Daniel Eischen wrote:
> > > > On Sat, 20 Sep 2003, M. Warner Losh wrote:
> > > >
> > > > >
On Sun, Sep 21, 2003 at 12:46:30AM -0400, Daniel Eischen wrote:
> This is the longest ports freeze that I can remember
I can only suppose that you haven't been paying attention to other
release cycles, because this one is shorter than usual.
> I wasn't
> expecting it to last long. Not to chan
At 1:29 AM -0400 2003/09/21, Daniel Eischen wrote:
Can you add a "no -pthread" symbol to it?
I could do up an ash grey t-shirt with slightly modified graphics.
What would a "no -pthread" symbol look like?
--
Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain
On Sun, Sep 21, 2003 at 01:04:49AM -0400, Daniel Eischen wrote:
> On Sat, 20 Sep 2003, Kris Kennaway wrote:
>
> > On Sat, Sep 20, 2003 at 08:43:18PM -0400, Daniel Eischen wrote:
> > > On Sat, 20 Sep 2003, M. Warner Losh wrote:
> > >
> > > > In message: <[EMAIL PROTECTED]>
> > > > Hara
On Sun, 21 Sep 2003, Brad Knowles wrote:
> At 1:05 AM +0200 2003/09/12, Poul-Henning Kamp wrote:
>
> > I don't want to get into the clothing business, so if you want one,
> > you'll probably have to make it yourself. I can ask the company
> > which produced them if they will be willing to sh
On Sat, 20 Sep 2003, Kris Kennaway wrote:
> On Sun, Sep 21, 2003 at 02:03:40PM +1000, John Birrell wrote:
> > On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote:
> > > 3) You, John Birrell, and whoever else is interested in fixing these
> > > ports can work on them at your own pace with
At 1:05 AM +0200 2003/09/12, Poul-Henning Kamp wrote:
I don't want to get into the clothing business, so if you want one,
you'll probably have to make it yourself. I can ask the company
which produced them if they will be willing to ship abroad, but I
doubt they are set up for that sort of t
On Sat, 20 Sep 2003, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Daniel Eischen <[EMAIL PROTECTED]> writes:
> : I'd like to see some barking up the other tree. Why should fixes
> : to unbreak ports be held up by the freeze?
>
> Because the ports folks do not want random
On Sun, Sep 21, 2003 at 01:07:15AM -0400, Daniel Eischen wrote:
> But you seem to thing -pthread == NOOP unbreaks ports ;-)
Warner might, but Kris doesn't. Kris is asking for the -pthread option
to be restored to let -current users breath easy while the task of updating
the ports goes on. Then he'
On Sat, 20 Sep 2003, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> John Birrell <[EMAIL PROTECTED]> writes:
> : On Sat, Sep 20, 2003 at 08:06:25PM -0600, M. Warner Losh wrote:
> : > But it was completely removed. That sounds like the consensus wasn't
> : > followed. Why w
On Sat, 20 Sep 2003, Kris Kennaway wrote:
> On Sat, Sep 20, 2003 at 08:43:18PM -0400, Daniel Eischen wrote:
> > On Sat, 20 Sep 2003, M. Warner Losh wrote:
> >
> > > In message: <[EMAIL PROTECTED]>
> > > Harald Schmalzbauer <[EMAIL PROTECTED]> writes:
> > > : Not only the -pthread remo
On Sat, 20 Sep 2003, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> John Birrell <[EMAIL PROTECTED]> writes:
> : On Sat, Sep 20, 2003 at 07:05:33PM -0600, M. Warner Losh wrote:
> : > Why does -pthread necessarily force selection of one specific
> : > threading library? All
In message: <[EMAIL PROTECTED]>
Daniel Eischen <[EMAIL PROTECTED]> writes:
: I'd like to see some barking up the other tree. Why should fixes
: to unbreak ports be held up by the freeze?
Because the ports folks do not want random changes going into the tree
right now given that they h
On Sun, 21 Sep 2003, John Birrell wrote:
> On Sat, Sep 20, 2003 at 07:05:33PM -0600, M. Warner Losh wrote:
> > Why does -pthread necessarily force selection of one specific
> > threading library? All it means is that it is that the program uses
> > posix threads, at least traditionally. How Free
On Sat, 20 Sep 2003, Doug Barton wrote:
> On Sat, 20 Sep 2003, Daniel Eischen wrote:
>
> > On Sat, 20 Sep 2003, M. Warner Losh wrote:
> >
> > > In message: <[EMAIL PROTECTED]>
> > > Harald Schmalzbauer <[EMAIL PROTECTED]> writes:
> > > : Not only the -pthread removement broke countles
On Sat, 20 Sep 2003, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Daniel Eischen <[EMAIL PROTECTED]> writes:
> : On Sat, 20 Sep 2003, M. Warner Losh wrote:
> :
> : > In message: <[EMAIL PROTECTED]>
> : > Harald Schmalzbauer <[EMAIL PROTECTED]> writes:
> : > :
On Sun, 2003-09-21 at 00:22, Kris Kennaway wrote:
> On Sun, Sep 21, 2003 at 02:03:40PM +1000, John Birrell wrote:
> > On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote:
> > > 3) You, John Birrell, and whoever else is interested in fixing these
> > > ports can work on them at your own pa
On Sun, Sep 21, 2003 at 02:03:40PM +1000, John Birrell wrote:
> On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote:
> > 3) You, John Birrell, and whoever else is interested in fixing these
> > ports can work on them at your own pace without disrupting life for
> > the rest of the users.
On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote:
> 3) You, John Birrell, and whoever else is interested in fixing these
> ports can work on them at your own pace without disrupting life for
> the rest of the users. Once they're all fixed, we can turn the error
> back on or make it a
In message: <[EMAIL PROTECTED]>
Cameron Murdoch <[EMAIL PROTECTED]> writes:
: As Warner said in another email, this card normally works flawlessly. I
: have many pci versions of it in other machines running current which do
: not have this problem, so it could be hardware, but it seems
In message: <[EMAIL PROTECTED]>
Frank Mayhar <[EMAIL PROTECTED]> writes:
: Everything has been rock-solid, no problems at all. Were it not for
: PAE, I would say to go ahead and release it.
That's good to hear. The re@ folks at devsummit had said that even
w/o PAE enabled, bad things
M. Warner Losh wrote:
> FWIW, I'm running today's RELENG_4 w/o PAE. I'll see if there are big
> issues.
FYI, I've been running 4.9-prerelease since last week, all without PAE.
Booted it on all my boxen (including a web server and a database server)
as well as doing hardware reconfigurations and t
In message: <[EMAIL PROTECTED]>
John Birrell <[EMAIL PROTECTED]> writes:
: On Sat, Sep 20, 2003 at 08:06:25PM -0600, M. Warner Losh wrote:
: > But it was completely removed. That sounds like the consensus wasn't
: > followed. Why was it then removed?
:
: It got discussed a bit more a
In message: <[EMAIL PROTECTED]>
Kris Kennaway <[EMAIL PROTECTED]> writes:
: 1) Put back -pthread in -current so all the ports don't fail
I've been thinking about just doing that, but was holding off to make
sure people had a chance to do this in the absense of dragging out a
big stick.
On Sat, Sep 20, 2003 at 08:43:18PM -0400, Daniel Eischen wrote:
> On Sat, 20 Sep 2003, M. Warner Losh wrote:
>
> > In message: <[EMAIL PROTECTED]>
> > Harald Schmalzbauer <[EMAIL PROTECTED]> writes:
> > : Not only the -pthread removement broke countless ports (some of them are
> >
>
On Sat, Sep 20, 2003 at 08:06:25PM -0600, M. Warner Losh wrote:
> But it was completely removed. That sounds like the consensus wasn't
> followed. Why was it then removed?
It got discussed a bit more after the removal. That was the time when the
GCC people got involved. The discussions where on
In message: <[EMAIL PROTECTED]>
John Birrell <[EMAIL PROTECTED]> writes:
: On Sat, Sep 20, 2003 at 07:05:33PM -0600, M. Warner Losh wrote:
: > Why does -pthread necessarily force selection of one specific
: > threading library? All it means is that it is that the program uses
: > posix
On Sat, Sep 20, 2003 at 07:05:33PM -0600, M. Warner Losh wrote:
> Why does -pthread necessarily force selection of one specific
> threading library? All it means is that it is that the program uses
> posix threads, at least traditionally. How FreeBSD causes that to
> happen is an interesting impl
On Sun, 2003-09-21 at 04:09, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Doug Barton <[EMAIL PROTECTED]> writes:
> : I'd really like to see this change backed out, at minimum until the
> : ports freeze is over.
My thoughts exactly.
Sincerely,
Dan Naumov
--
In message: <[EMAIL PROTECTED]>
Doug Barton <[EMAIL PROTECTED]> writes:
: I'd really like to see this change backed out, at minimum until the
: ports freeze is over.
Me too. I'd like to see a discussion of this in arch@ as well. I
know that people have a low bikeshed tolerance these
In message: <[EMAIL PROTECTED]>
Daniel Eischen <[EMAIL PROTECTED]> writes:
: On Sat, 20 Sep 2003, M. Warner Losh wrote:
:
: > In message: <[EMAIL PROTECTED]>
: > Harald Schmalzbauer <[EMAIL PROTECTED]> writes:
: > : Not only the -pthread removement broke countless ports (so
From: "Scot W. Hetzel" <[EMAIL PROTECTED]>
> From: "Dan Naumov" <[EMAIL PROTECTED]>
> > Seeing as -pthread support has been removed from -CURRENT breaking
> > _LOTS_ of ports, is it possible to "get it back" into a local source
> > tree ? If so, how ? Thanks in advance.
> >
> All you need to do is
On Sat, 20 Sep 2003, Daniel Eischen wrote:
> On Sat, 20 Sep 2003, M. Warner Losh wrote:
>
> > In message: <[EMAIL PROTECTED]>
> > Harald Schmalzbauer <[EMAIL PROTECTED]> writes:
> > : Not only the -pthread removement broke countless ports (some of them are
> >
> > Maybe I missed the re
On Sat, 20 Sep 2003, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Harald Schmalzbauer <[EMAIL PROTECTED]> writes:
> : Not only the -pthread removement broke countless ports (some of them are
>
> Maybe I missed the reason why FreeBSD needs to be unique wrt threading
> pro
From: "Dan Naumov" <[EMAIL PROTECTED]>
> Seeing as -pthread support has been removed from -CURRENT breaking
> _LOTS_ of ports, is it possible to "get it back" into a local source
> tree ? If so, how ? Thanks in advance.
>
All you need to do is add:
CONFIGURE_ENV+=PTHREAD_LIBS=${PTHREAD_LIB
Hello
Seeing as -pthread support has been removed from -CURRENT breaking
_LOTS_ of ports, is it possible to "get it back" into a local source
tree ? If so, how ? Thanks in advance.
Sincerely,
Dan Naumov
___
[EMAIL PROTECTED] mailing list
http://lists.f
On Sun, 2003-09-21 at 00:16, Scott Likens wrote:
> On Sat, 2003-09-20 at 16:04, Cameron Murdoch wrote:
> > On Sat, 2003-09-20 at 23:50, Scott Likens wrote:
> > > First, do you use DHCP?
> >
> > No, not on this laptop.
> >
> > > What are you doing exactly when it looses 'net or 'ip?
> >
> > Nothi
On Sat, 20 Sep 2003, Thomas Quinot wrote:
> Le 2003-09-20, Daniel Eischen écrivait :
>
> > No, using latest sources, with or without atapicam, does
> > not solve the problem. It still hangs.
>
> Please try the patch below, it should at least work around the problem.
>
> > http://people.freebsd.
On Sat, 2003-09-20 at 16:04, Cameron Murdoch wrote:
> On Sat, 2003-09-20 at 23:50, Scott Likens wrote:
> *snip*
> > First, do you use DHCP?
>
> No, not on this laptop.
>
> > What are you doing exactly when it looses 'net or 'ip?
>
> Nothing specific that I can see. Sometimes nothing, sometimes
Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt,
On Sun, 21 Sep 2003 00:23:36 +0200, Thomas Quinot wrote:
> Can you get a backtrace at that point?
I could not get a backtrace because infinite loop occured like this:
[snip]
ata0-master: pio=0x0c wdma=0x22 udma=0x46
On Sat, 2003-09-20 at 23:50, Scott Likens wrote:
*snip*
> First, do you use DHCP?
No, not on this laptop.
> What are you doing exactly when it looses 'net or 'ip?
Nothing specific that I can see. Sometimes nothing, sometimes an nfs
installworld, which was a bit dangerous seeing as the connectio
In message: <[EMAIL PROTECTED]>
Derek Ragona <[EMAIL PROTECTED]> writes:
: try to get a diagnostic program from dell or the card maker. If the
: diagnostics are fine, it may be power management, you will need to check
: and reset to off any power management that effects the NIC.
The
On Sat, 2003-09-20 at 15:10, Cameron Murdoch wrote:
> I have a strange problem with my Dell Inspiron Laptop. The network card
> will stop responding to all network traffic. This happens very
> regulally, though without any obvious pattern. Sometimes it only
> appears as slight packet lose though
In message: <[EMAIL PROTECTED]>
Harald Schmalzbauer <[EMAIL PROTECTED]> writes:
: Not only the -pthread removement broke countless ports (some of them are
Maybe I missed the reason why FreeBSD needs to be unique wrt threading
programs and not have -pthread...
Warner
_
On Sat, 2003-09-20 at 15:10, Cameron Murdoch wrote:
> I have a strange problem with my Dell Inspiron Laptop. The network card
> will stop responding to all network traffic. This happens very
> regulally, though without any obvious pattern. Sometimes it only
> appears as slight packet lose though
try to get a diagnostic program from dell or the card maker. If the
diagnostics are fine, it may be power management, you will need to check
and reset to off any power management that effects the NIC.
-Derek
At 11:18 PM 9/20/2003 +0100, you wrote:
I have a strange problem with my Dell
On Sat, 2003-09-20 at 23:10, Cameron Murdoch wrote:
> When the connection gets dropped doing an ifconfig down/up on the
> interface does ?
This was supposed to say that ifconfig down/up does not help, only
removing/inserting the network cable.
Also, sorry about the wrong email address in the pri
Le 2003-09-20, Shin-ichi Yoshimoto écrivait :
> > acd0: WARNING - REQUEST_SENSE recovered from missing interrupt
> This message disappeared, but It still hang
Can you get a backtrace at that point?
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] maili
I have a strange problem with my Dell Inspiron Laptop. The network card
will stop responding to all network traffic. This happens very
regulally, though without any obvious pattern. Sometimes it only
appears as slight packet lose though normally the network connection
goes completly. But then a
Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing
interrupt,
On Sat, 20 Sep 2003 21:53:11 +0200, Thomas Quinot wrote:
> Please try the patch below, it should at least work around the problem.
I tried your patch.
> acd0: WARNING - REQUEST_SENSE recovered from missing interru
The system died in buildworld, this time it fell into the debugger.
spec_getpages(ad4s1d) I/O read failure (error=5)
-Derek
At 02:53 PM 9/20/2003 -0500, Derek Ragona wrote:
The 9/19 snapshot has the same issues.
I will try to cvsup it and build a new kernel, if I can.
-Derek
A
Le 2003-09-19, Dan Naumov écrivait :
> Disabling atapicam in the kernel or detaching the drive from the system
> works around the problem.
Please try the patch I posted a few moments ago under "ATAng no good for
me/REQUEST_SENSE recovered from missing interrupt".
Thomas.
--
[EMAIL PROTECTE
Le 2003-09-20, David R. Colyer écrivait :
> Is atapicam a kernel config option?
It is a device (cf. man atapicam): you can enable it with
"device atapicam" in your kernel config file.
> I can't seem to find it, and now since a cvsup up on the 17h, my plextor scsi
> cdrw locks my system and then
The 9/19 snapshot has the same issues.
I will try to cvsup it and build a new kernel, if I can.
-Derek
At 05:36 AM 9/20/2003 -0500, Derek Ragona wrote:
This was using the 9/18 snapshot, I tried to cvsup it to the most current,
but the drive errors prevent the update.
I just reloaded wi
Le 2003-09-20, Daniel Eischen écrivait :
> No, using latest sources, with or without atapicam, does
> not solve the problem. It still hangs.
Please try the patch below, it should at least work around the problem.
> http://people.freebsd.org/~deischen/ata_hang.091903
Interesting, the last 2 l
Maksim Yevmenkin wrote in message ID
<[EMAIL PROTECTED]>:
> i just quickly checked the CVS. according to your -current date you should
> have this fix. can you double check? perhaps there is another bug somewhere.
>
> i will take close look at ng_ubt(4) today once again.
>
> =
On Sat, 20 Sep 2003, Lars Eggert wrote:
> Daniel Eischen wrote:
> > On Sat, 20 Sep 2003, Soren Schmidt wrote:
> >>It seems Daniel Eischen wrote:
> >>
> >>>On a kernel built just a few hours ago, it hangs on boot
> >>>right after:
> >>>
> >>>acd0: CDROM at ata0-master PIO4
> >>
> >>Get atapicam ou
Daniel Eischen wrote:
On Sat, 20 Sep 2003, Soren Schmidt wrote:
It seems Daniel Eischen wrote:
On a kernel built just a few hours ago, it hangs on boot
right after:
acd0: CDROM at ata0-master PIO4
Get atapicam out and see if that helps..
No, using latest sources, with or without atapicam, does
no
It seems Daniel Eischen wrote:
> > It seems Daniel Eischen wrote:
> > > On a kernel built just a few hours ago, it hangs on boot
> > > right after:
> > >
> > > acd0: CDROM at ata0-master PIO4
> >
> > Get atapicam out and see if that helps..
>
> No, using latest sources, with or without atapicam
On Sat, 20 Sep 2003, Soren Schmidt wrote:
> It seems Daniel Eischen wrote:
> > On a kernel built just a few hours ago, it hangs on boot
> > right after:
> >
> > acd0: CDROM at ata0-master PIO4
>
> Get atapicam out and see if that helps..
No, using latest sources, with or without atapicam, does
On Sat, 30 Aug 2003 17:56:43 +0200
"Julian St." <[EMAIL PROTECTED]> wrote:
> Hello,
>
> some people reported strange behavior of nvidia-driver: after starting
> X the screen flickers shortly and then displays gibberish in
> text-mode. The system is still responsive, as one can login via serial
>
Hello Gary,
> It seems when using rfcomm_pppd (at least) as a Bluetooth <-> LAN
> gateway there is a fairly large memory leak which eventually crashes
> the box running the ppp server. To track down where, I recorded the
> output of kern.malloc every minute until the box crashed. At the
> start
Hi,
It seems when using rfcomm_pppd (at least) as a Bluetooth <-> LAN
gateway there is a fairly large memory leak which eventually crashes
the box running the ppp server. To track down where, I recorded the
output of kern.malloc every minute until the box crashed. At the
start of the debugging
On Sat, 15 Nov 2003, Philipp Westphal wrote:
> Hi today, cvsup'ed my source and build world ...
> and now get an so called
>
> Bus error
>
> while i want to su, anyone know about it (or fixed it)
1) Adjust your system clock so that it's set to something reasonable.
2) What CFLAGS do you have in
Hi!
Last if_sk update broke buildkernel
===> sk
rm -f .depend
mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@
-I@/../include /usr/src/sys/modules/sk/../../pci/if_sk.c
/usr/src/sys/pci/if_sk.c:129:26: pci/yukonreg.h: No such file or directory
mkdep: compile failed
missed to c
Hey all,
I get the following hang up when I try booting up, here's the problem area...
pcm0: at device 31.5 on pci0
pcm0: unable to map IO port space
device_probe_and_attach: pcm0 attach returned 6
I'm running a CVSUP -current from Thu Sep 18 12:34:00 EDT 2003, I have a
Yama
On Sat, 2003-09-20 at 12:32, David R. Colyer wrote:
> Is atapicam a kernel config option?
[14:11]-[jago]-[~]: cat /usr/src/sys/i386/conf/JAGO | grep atapicam
#device atapicam# BROKEN in -CURRENT !!!
Hope this helps.
Sincerely,
Dan Naumov
Harald Schmalzbauer wrote:
Oh I see. Thats a reason. If I only knew about that freeze before my
"pkg_delete -a" but that's just my problem
Thanks,
-Harry
I unfortunatly did the same thing. I wanted to upgrade to gnome 2.4 and
seeing as this box really doesn't have any ports installed other
This was using the 9/18 snapshot, I tried to cvsup it to the most current,
but the drive errors prevent the update.
I just reloaded with the 9/19 snapshot, and will report if the error still
exists.
As for the hardware, it is all brand new hardware, and the system dual
boots, the other OS has
Kris Kennaway wrote:
On Sat, Sep 20, 2003 at 08:14:07AM +0200, Harald Schmalzbauer wrote:
Well, for weeks now I couldn't compile (almost) any port. It seems that
ports aren't tested against -current. Is that true?
No.
Not only the -pthread removement broke countless ports (some of them are
e
Is atapicam a kernel config option?
I can't seem to find it, and now since a cvsup up on the 17h, my plextor scsi
cdrw locks my system and then reboots immediately after a burning program,
(i've tried several) initializes the drive. It worked several weeks ago just
fine. Any suggestions would
Since Adapted 1210SA is based on Sil3112A controller I still also have same problem
what I reported few weeks before with my onboard sil3112a controller.
tested tonight with fresh kernel
- Original Message -
From: "Soren Schmidt" <[EMAIL PROTECTED]>
To: "Derek Ragona" <[EMAIL PROTECTED]
It seems Derek Ragona wrote:
> I have a single SATA drive on an Adaptec 1210SA card.
>
> The drive will give a write error warning a few times, then will repeatedly
> give:
> ad4: timeout sending command=ca
>
> The only recovery is the reset switch, reboot single-user fsck, and then
> come back
It seems Vladimir Kushnir wrote:
>
> > > Together with sys/cdio.h, where both ioc_read_audio and CDIOCREADAUDIO are
> > > declared
> >
> > I'll get rid of those...
> >
> Again, a pity. What benefits do we gain here? Speed? CDDA extraction never
> required all that much of it, and to be honest the
It seems Daniel Eischen wrote:
> On a kernel built just a few hours ago, it hangs on boot
> right after:
>
> acd0: CDROM at ata0-master PIO4
Get atapicam out and see if that helps..
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/ma
Today's kernel with atapicam said:
acd0: WARNING - REQUEST_SENCE record from missing interrupt
and can not boot. Without one is OK.
--
Shin-ichi YOSHIMOTO <[EMAIL PROTECTED]>
http://diary.waishi.jp/~yosimoto/diary/
___
[EMAIL PROTECTED] mailing list
h
92 matches
Mail list logo
