Please use subject lines. Thanks.
On Mon, 29 Sep 2003, Tomi Vainio - Sun Finland wrote:
Dag-Erling Smørgrav writes:
An NMI almost certainly indicates a hardware failure.
Lucas James writes:
It could be a power supply on the way out. I had an old dual P-166 that
rebooted
In message [EMAIL PROTECTED], Doug White writes:
Well this might be the source of problems. I've expressed caution at
doing this sorrt of thing before since getting the grounds equallized can
be tricky. If the ground levels become unequalized, or worse you get some
sort of ground loop going,
Did you look at M. Warner Losh's commits in cbb framework?
They seem to be relevant to me.
Having a look at it now, seems that yes pccbb.c has been updated and
could be the cause of my problems, unfortunately my c is abysmal so bar
rolling back to the previous version of this file I'll just
Hi,
Argh, sorry about loosing the subject. Unfortunately messages from my
normal ISP are't getting through to freebsd.org mailng lists (I've
contacted them about it) and I'm having to use a crappy uni web mail
system) which I'm not used to, so forgot the subject
--- reply
On Wed, 20 Nov 2002, Chris Howells wrote:
Hi,
On Wednesday 20 November 2002 5:08 pm, Robert Watson wrote:
dmesg is a command that dumps the kernel message buffer. You can
redirect
the output to a file:
dmesg fileofchoice
Sure. This bit is sufficiently similar to
On Mon, 29 Jul 2002, Tzouris,M wrote:
?? can read questions fine, but won't allow me to answer any of
them
Bob
Many thanks to everybody that send their feedback on this matter.
I have now uploaded a text based questionnaire that can be found at:
On 18:24+0300, May 3, 2002, Radoslav Vasilev wrote:
unsuscribe freebsd-current
use [EMAIL PROTECTED] instead of [EMAIL PROTECTED] Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Maxim Konovalov, MAcomnet, Internet
On Wed, Nov 29, 2000 at 07:41:14PM -0600, Mike Meyer wrote:
Hmm - what's the stupidity? I have a test machine running both
-current and -stable
Do you have the two FreeBSD installations on the same disk? If so, I'd
love to hear how you did it. I spoke with others and they also had
problems
David O'Brien [EMAIL PROTECTED] types:
On Wed, Nov 29, 2000 at 07:41:14PM -0600, Mike Meyer wrote:
Hmm - what's the stupidity? I have a test machine running both
-current and -stable
Do you have the two FreeBSD installations on the same disk? If so, I'd
love to hear how you did it. I
In message [EMAIL PROTECTED] "David O'Brien" writes:
: Except for stupidity in libdisk(I believe) and thus sysinstall, there is
: no, none, zero reason why one cannot have two installations of FreeBSD in
: two different slices on the same disk.
I've done make buildworld/installworld of both
Warner Losh [EMAIL PROTECTED] types:
In message [EMAIL PROTECTED] "David O'Brien" writes:
: Except for stupidity in libdisk(I believe) and thus sysinstall, there is
: no, none, zero reason why one cannot have two installations of FreeBSD in
: two different slices on the same disk.
I've done
On Wed, Nov 29, 2000 at 08:06:14AM +0100, News User wrote:
I'm building news machines with two partitions for OSen, to allow
me to boot into my choice, where my choice has been FreeBSD-STABLE
or FreeBSD-CURRENT to see how the two compare, and if there are any
significant improvements in
David O'Brien [EMAIL PROTECTED] types:
On Wed, Nov 29, 2000 at 08:06:14AM +0100, News User wrote:
I'm building news machines with two partitions for OSen, to allow
me to boot into my choice, where my choice has been FreeBSD-STABLE
or FreeBSD-CURRENT to see how the two compare, and if there
Already told him. It is.
On Sun, 20 Aug 2000, Tony Fleisher wrote:
Not sure if this is related to the recent commit of DEVFS code, but a
build of both the GERNERIC kernel and a custom kernel from a very recent
(last few hours) cvsup of -current failed during the 'make depend' with
an
Someone can this idiot.
On Fri, Mar 31, 2000 at 05:11:34PM +0200, Charlie Root wrote:
Subject: Mail::Internet test subject
This is a test message that was sent by the test suite of
Mail::Internet.
Testing.
one
From foo
four
From bar
seven
To Unsubscribe: send mail to
Actually, I don't think so. I'm not 100% sure, but I think that you end
up in the interrupt handler for the card that's going away, but with tty
interrupts masked so you can't get back into DDB. If it's a modem card,
then you'll have them masked as well.
I'm _fairly_ sure that you'll
There are other contexts for the same issues anyway. USB has devices
that go away suddenly, and it _is_ designed to be hot-removable, so
people are going to be pulling the plug on network adapters, ZIP
drives, etc. We need drivers that are capable of going away cleanly,
or at least without
On Thu, 2 Dec 1999, Nick Hibma wrote:
PCMCIA has the problem that the hardware register you are talking to can
disappear on the spot, between 2 outb()s.
Can't we do something about this using bus_space? This would give us a
fair bit of overhead for PCMCIA devices as well as require us to more
In message [EMAIL PROTECTED] Nick Hibma writes:
: PCMCIA has the problem that the hardware register you are talking to can
: disappear on the spot, between 2 outb()s.
Yes. That's why one must poll the device, from time to time, to see
if it is gone. Yucky-poo.
Warner
To Unsubscribe: send
In message [EMAIL PROTECTED] "Matthew N.
Dodd" writes:
: On Thu, 2 Dec 1999, Nick Hibma wrote:
: PCMCIA has the problem that the hardware register you are talking to can
: disappear on the spot, between 2 outb()s.
:
: Can't we do something about this using bus_space? This would give us a
:
In message [EMAIL PROTECTED] "Matthew N.
Dodd" writes:
: On Thu, 2 Dec 1999, Nick Hibma wrote:
: PCMCIA has the problem that the hardware register you are talking to can
: disappear on the spot, between 2 outb()s.
:
: Can't we do something about this using bus_space? This would give us
In message [EMAIL PROTECTED] Christopher Masto writes:
: On Tue, Nov 30, 1999 at 04:52:33PM -0700, Warner Losh wrote:
: It would help me if you could send me your patches...
:
: Well, here's all I've got. It's basically just a sloppy version of
: what you suggested.
OK. This should
With freeze I meant, freeze. Rock solid. Nothing to be done. Stepping
through the code the laptop freezes in the second putb in pcic_disable.
As in stepping the assembler to that outb does never return the prompt.
Actually, I don't think so. I'm not 100% sure, but I think that you end
up
In message [EMAIL PROTECTED] Mike Smith writes:
: The only "right" solution is for us to mandate that people down cards
: before ejecting them. The physical design of pccards basically gives us
: no other option. No matter how hard we try to get it "right" for
: spontaneous removal, we can't
On Wed, Dec 01, 1999 at 09:05:38AM -0700, Warner Losh wrote:
In message [EMAIL PROTECTED] Mike Smith writes:
: The only "right" solution is for us to mandate that people down cards
: before ejecting them. The physical design of pccards basically gives us
: no other option. No matter how
--- Blind-Carbon-Copy
To: Christopher Masto [EMAIL PROTECTED]
Subject: Re: PCCARD eject freeze (was Re: your mail)
Cc: [EMAIL PROTECTED]
In-reply-to: Your message of "Wed, 01 Dec 1999 12:36:29 EST."
[EMAIL PROTECTED]
References: [EMAIL PROTECTED]
[EMAIL PROTECT
On Wed, Dec 01, 1999 at 09:05:38AM -0700, Warner Losh wrote:
In message [EMAIL PROTECTED] Mike Smith writes:
: The only "right" solution is for us to mandate that people down cards
: before ejecting them.
...
I would like to see that something along the lines of a method to shut
down
On Tue, 30 Nov 1999, Mike Smith wrote:
Hmmm... That's something... How do you know that the delete_child is
failing? An if printing that it failed or conjecture based on the
insertion results?
You should definitely check the delete result, yes.
Also, are you calling
On Tue, 30 Nov 1999, Warner Losh wrote:
In message [EMAIL PROTECTED] Christopher Masto writes:
: Hey, we're getting somewhere. It works, in that it stops the panic.
: I get the "ed0: unloaded" message, and the machine doesn't panic, but
: there are still some problems. It seems that
On Wed, Dec 01, 1999 at 12:02:54PM -0800, Mike Smith wrote:
On Wed, Dec 01, 1999 at 09:05:38AM -0700, Warner Losh wrote:
In message [EMAIL PROTECTED] Mike Smith writes:
: The only "right" solution is for us to mandate that people down cards
: before ejecting them.
...
I would like
: Hey, we're getting somewhere. It works, in that it stops the panic.
: I get the "ed0: unloaded" message, and the machine doesn't panic, but
: there are still some problems. It seems that device_delete_child
: is failing (I forgot to print the return code, but it is not zero),
: and
With freeze I meant, freeze. Rock solid. Nothing to be done. Stepping
through the code the laptop freezes in the second putb in pcic_disable.
As in stepping the assembler to that outb does never return the prompt.
Nick
From some very brief testing here, the problem is that the card's
In message [EMAIL PROTECTED] Christopher Masto writes:
: I noticed that the "new" code does the power off before the
: reset.. dunno if this is significant.
Shouldn't be... I gotta get a bouncer system that I can plug a bridge
into to see if I can get this problem to happen for me (which i
In message [EMAIL PROTECTED] Christopher Masto writes:
: I found that the only message printed was "ready to power off".
bingo. looks like we're not deleting the child. Try replacing that
for loop with something like:
pccarddev = devclass_get_device(pccard_devclass, slt-slot);
On Tue, Nov 30, 1999 at 02:59:10PM -0700, Warner Losh wrote:
In message [EMAIL PROTECTED] Christopher Masto writes:
: I found that the only message printed was "ready to power off".
bingo. looks like we're not deleting the child. Try replacing that
for loop with something like:
Christopher Masto wrote:
On Tue, Nov 30, 1999 at 02:59:10PM -0700, Warner Losh wrote:
In message [EMAIL PROTECTED] Christopher Masto writes:
: I found that the only message printed was "ready to power off".
bingo. looks like we're not deleting the child. Try replacing that
for loop
In message [EMAIL PROTECTED] Christopher Masto writes:
: Hey, we're getting somewhere. It works, in that it stops the panic.
: I get the "ed0: unloaded" message, and the machine doesn't panic, but
: there are still some problems. It seems that device_delete_child
: is failing (I forgot to print
On Tue, Nov 30, 1999 at 02:54:28PM -0800, Frank Mayhar wrote:
On Tue, Nov 30, 1999 at 02:59:10PM -0700, Warner Losh wrote:
pccarddev = devclass_get_device(pccard_devclass, slt-slot);
device_get_children(pccarddev, kids, nkids)
for (i = 0; i nkids; i++)
In message [EMAIL PROTECTED] Frank Mayhar writes:
: I'll bet Warner meant
: device_delete_child(pccarddev, kid[i]);
: up there, and not
: device_delete_child(pccarddev, kid[0]);
:
: Did you try that?
Yes. He did. Likely won't make a difference here because we don't
In message [EMAIL PROTECTED] Christopher Masto writes:
: It's not quite working. I think I got away ok with the ethernet card
: because it wasn't being accessed, but my CDPD card with a running PPP
: session pretty reliably still freezes up. Hrm. No, it's not freezing
: up, it's a panic, but
On Tue, Nov 30, 1999 at 04:04:40PM -0700, Warner Losh wrote:
In message [EMAIL PROTECTED] Christopher Masto writes:
: Hey, we're getting somewhere. It works, in that it stops the panic.
: I get the "ed0: unloaded" message, and the machine doesn't panic, but
: there are still some problems.
In message [EMAIL PROTECTED] Christopher Masto writes:
: I added a check of the return value. It seemed to be returning 12
: (ENOMEM), but I'm not sure if that's real or garbage, since I'm having
: trouble finding a code path that would return that.
You might want to make ed_pccard_detach
I'm on my way out for dinner, just thought I'd mention the latest
experiment results.
On Tue, Nov 30, 1999 at 04:19:18PM -0700, Warner Losh wrote:
: And further data on the CDPD card.. removing it while PPP is still
: running just paniced in sioioctl. However, the delete_child didn't
: fail
In message [EMAIL PROTECTED] Mike Smith writes:
: You should definitely check the delete result, yes.
:
: Also, are you calling bus_generic_detach() after deleting the child?
: I got the impression from Doug that this is required...
In the child? device_delete_child() already calls
In message [EMAIL PROTECTED] Christopher Masto writes:
: Ho hum. sio_pccard_detach also needs to be fixed to return 0, but I
: don't think that explains the freeze. Unfortunately, while I can
: sometimes squeeze in a few minutes to try quick fixes, my current
: job doesn't leave me with time to
On Tue, Nov 30, 1999 at 04:52:33PM -0700, Warner Losh wrote:
It would help me if you could send me your patches...
Well, here's all I've got. It's basically just a sloppy version of
what you suggested.
Index: pccard.c
===
RCS
In message [EMAIL PROTECTED] Christopher Masto writes:
: On Tue, Nov 30, 1999 at 04:52:33PM -0700, Warner Losh wrote:
: It would help me if you could send me your patches...
:
: Well, here's all I've got. It's basically just a sloppy version of
: what you suggested.
OK. This should help.
In message [EMAIL PROTECTED] Christopher Masto writes:
: Well, here's all I've got. It's basically just a sloppy version of
: what you suggested.
I've cleaned this up, worked it around, and managed to insert and
eject my ep card 5 times in a row on my desktop kludge environment.
It even
Try sending the command to [EMAIL PROTECTED]
Nick
On Thu, 29 Jul 1999, Joachim Kuebart wrote:
unsubscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra,
On Thu, 6 May 1999, Tomer Weller wrote:
whenever i try to compile KDE software (ports also) i get this error, though
packages install fine.
i installed KDE from packages, i suspect that's the problem.
I didn't see a response to this as I was going through my inbox, so apologies
if this has
50 matches
Mail list logo
