Previously posted trap frame:
#5 0xc0691771 in trap (frame=
{tf_fs = -1068433384, tf_es = -989790192, tf_ds = 16, tf_edi = -106612473
6, tf_esi = -1066124736, tf_ebp = -323699844, tf_isp = -323699872, tf_ebx = -10
07063716, tf_edx = 528, tf_ecx = -1013235680, tf_eax = 307472464, tf_trapno =
On Thu, May 19, 2005 at 12:17:37AM -0500, Conrad J. Sabatier wrote:
> On Mon, 16 May 2005 20:39:32 + (GMT), [EMAIL PROTECTED] (Bill Paul)
> wrote:
>
> >
> > Ok everyone, PAY ATTENTION! Drop whatevery your doing for the next
> > five minutes and READ THIS!!
> >
[ ... ]
>
> Well, that
On 19/05/2005, at 2.20, Joe Rhett wrote:
Soren, I've just retested all of this with 5.4-REL and most of the
problems
listed here are solved. The only problems appear to be related to
these
ghost arrays that appear when it finds a drive that was taken offline
earlier. For example, pull a drive
Hi,
I've got a new machine and don't think I'm getting all
the speed out of it
that I should be. Any hints/ideas for what I can do
to make the most of my
new hardware?
FreeBSD 5.4-Release
Shuttle SN25P
Nvidia NForce 4 with SATA 150
WD Raptor HD
I ran atacontrol and it reports:
# atacontrol li
=== Conrad J. Sabatier escribía
(Thu, May 19, 2005 at 12:17:37AM -0500):
> Well, that's what you get for having a name that's made up of two first
> names. :-)
> Sorry, but I've no sympathy at all. Bloody double first-namers.
> You'll be the first against the wall when the revolution comes.
On Mon, 16 May 2005 20:39:32 + (GMT), [EMAIL PROTECTED] (Bill Paul)
wrote:
>
> Ok everyone, PAY ATTENTION! Drop whatevery your doing for the next
> five minutes and READ THIS!!
>
> You see that header on this e-mail? You see the "From:" line? Go and
> read it to yourself. Read the name. Say
Bruce Burden wrote:
Hi Doug,
well, pulling cards demonstrated where the problem lie, but it
was not a hardware problem. By chance, I happened upon the "options
ASR_COMPAT" directive, and that solved my problem. However, the
GENERIC kernel configuration for i386 does NOT have this op
Hi Doug,
well, pulling cards demonstrated where the problem lie, but it
was not a hardware problem. By chance, I happened upon the "options
ASR_COMPAT" directive, and that solved my problem. However, the
GENERIC kernel configuration for i386 does NOT have this option, but
Hi,
Is there any difference re-install FreeBSD-5.4?
Hello Sir,
Can you try to re-install FreeBSD5.4 from scratch with BIOS ACPI
enabled?
Thanks.
Best Regards!
Jerry
Technical Support
--
Super Micro Computer, Inc. (http://supermicro.com)
A Server Solutions Manu
--- Doug White <[EMAIL PROTECTED]> wrote:
> On Tue, 17 May 2005, Rob wrote:
>
> > The 'pciconf -lv' tells me:
> >
> > [EMAIL PROTECTED]:4:0: class=0x010400 card=0x80f51043
> >chip=0x3373105a rev=0x02 hdr=0x00
> > vendor = 'Promise Technology Inc'
> > device = 'PDC2037
Hi,
I sent following but no answer yet
Hi,
Existing BIOS version is 1.3a, which is same on web.
Balgaa
--- Support <[EMAIL PROTECTED]> wrote:
> Hi,
>
> did you have the latest bios for the board?
> http://www.supermicro.com/support/bios/
>
> thanks,
>
> john
===
In message <[EMAIL PROTECTED]>, Doug White writes:
>On Wed, 18 May 2005, Matthias Buelow wrote:
>> Obviously the Right Way of doing such things is to move this into the
>> 2nd stage boot loader... I can't think of any reason (except quick
>> hackery) why this hasn't been done that way. I mean, one
On 18 May, Scott Long wrote:
>
> Einstein Oliveira wrote:
>> Hi,
>>
>> I'm using FreeBSD 5.4-RELEASE-p1 and I found some messages about a
>> problem like this in freebsd-current a few months ago.
>>
>> The fact is that this problem has just ocurred (on 5.4-RELEASE-p1),
>> probably because of a
Soren, I've just retested all of this with 5.4-REL and most of the problems
listed here are solved. The only problems appear to be related to these
ghost arrays that appear when it finds a drive that was taken offline
earlier. For example, pull a drive and then reboot the system.
1. If you reboo
On 18 May, Einstein Oliveira wrote:
> Hi,
>
> I'm using FreeBSD 5.4-RELEASE-p1 and I found some messages about a
> problem like this in freebsd-current a few months ago.
>
> The fact is that this problem has just ocurred (on 5.4-RELEASE-p1),
> probably because of a power outage (I didn't find a
Doug White wrote:
> Then the space problem just migrates. There's a limited amount of space
> in the disklabel for bootblocks and I think we're pushing that.
Errm. /boot/loader doesn't reside in the 2nd stage, does it?
I mean, there is a boot menu (the Forth-run thing with the ASCII
daemon). If
On Wed, 18 May 2005, Matthias Buelow wrote:
> Dan Nelson wrote:
>
> > The next release should:
> > RCS file: /home/ncvs/src/sys/boot/i386/boot0/boot0.S,v
> [...]
>
> Obviously the Right Way of doing such things is to move this into the
> 2nd stage boot loader... I can't think of any reason (except
On Tue, 17 May 2005, Rob wrote:
>
> Hi,
>
> The 'pciconf -lv' tells me:
>
> [EMAIL PROTECTED]:4:0: class=0x010400 card=0x80f51043
> chip=0x3373105a rev=0x02 hdr=0x00
> vendor = 'Promise Technology Inc'
> device = 'PDC20378 FastTrak 378/SATA 378 RAID
>
On Wed, May 18, 2005 at 03:54:59PM -0700, Doug White wrote:
> On Wed, 18 May 2005, Jamie Heckford wrote:
>
> > Hi Peter,
> >
> > On Thu, May 19, 2005 at 05:53:12AM +1000, Peter Jeremy wrote:
> > > On Wed, 2005-May-18 16:03:16 +0100, Jamie Heckford wrote:
> > > >Managed to get a dump on our system
On Tue, 17 May 2005, Cedric Tabary wrote:
> On 17/05/2005 17:54, Cedric Tabary wrote:
> > FreeBSD 5.4-RC3 i386, no SMP compiled in kernel
> > dmesg atached
>
> Oops forgot the dmesg ;)
Panic & trap messages would be nice too, so we know what address is
exploded on.
>
> Copyright (c) 1992-2005 Th
On Wed, 18 May 2005, Todor Dragnev wrote:
> Hello,
>
> Before a couple of days ago I started /usr/local/sbin/cupsd manualy from
> console. When I press CTRL+C to interrupt a program, the system change
> runlevel and going to reboot. This was on FreeBSD V5.3, today I
> installed fresh new 5.4 but t
On Mon, 16 May 2005, Bruce Burden wrote:
>
>
> Hi folks,
>
> I am trying to get my Adaptec 3210S RAID running under 5.4,
> and all I get for my trouble is pmap_ errors. Sorry, no dumps at
> the moment.
>
> If I compile "device asr" into the kernel, I get a message
> about "cou
On Wed, May 11, 2005 at 08:36:08PM -0700, Doug White wrote:
> This is a problem mlaier and I may have fixed, at least against -CURRENT.
> It appears that the process group alias in struct tty is accessed without
> locking and its changing out from under us.
>
> Give this a try:
>
> http://people
On Mon, 16 May 2005, Holtor wrote:
> Does anyone know how to make a PS/2 keyboard work when plugged into a
> system booted without a keyboard on FreeBSD 5.x? It doesn't seem to
> work.
This is a system-specific thing. As noted previously clearing flag 0x1 on
atkbd0 can help this, but it doesn't a
On Wed, 18 May 2005, Jamie Heckford wrote:
> Hi Peter,
>
> On Thu, May 19, 2005 at 05:53:12AM +1000, Peter Jeremy wrote:
> > On Wed, 2005-May-18 16:03:16 +0100, Jamie Heckford wrote:
> > >Managed to get a dump on our system for a similar prob we are getting:
> >
> > That traceback looks like a pan
On Sun, 15 May 2005, Jeremie Le Hen wrote:
> Sorry, I couldn't get a dump.
>
> %%%
> obiwan:tataz$ uname -a
> FreeBSD obiwan.tataz.chchile.org 5.4-STABLE FreeBSD 5.4-STABLE #16: Fri
> May 13 01:01:50 CEST 2005 [EMAIL
> PROTECTED]:/usr/src/sys/i386/compile/OBIWAN i386
> %%%
>
> %%%
>
Einstein Oliveira wrote:
Hi,
I'm using FreeBSD 5.4-RELEASE-p1 and I found some messages about a
problem like this in freebsd-current a few months ago.
The fact is that this problem has just ocurred (on 5.4-RELEASE-p1),
probably because of a power outage (I didn't find anything in logs that
woul
Hi Peter,
On Thu, May 19, 2005 at 05:53:12AM +1000, Peter Jeremy wrote:
> On Wed, 2005-May-18 16:03:16 +0100, Jamie Heckford wrote:
> >Managed to get a dump on our system for a similar prob we are getting:
>
> That traceback looks like a panic, not a deadlock. What was the panic
> message?
Only
On Sun, 15 May 2005, Balgansuren.B wrote:
> Doug,
>
> I checked website for BIOS files and current loaded BIOS is latest
> version.
>
> If I to use continously ACPI aware=NO, is there any problem?
You can, but you may have reduced functionality (particularly if ACPI
supports thermal zones).
> Pr
Hi,
I'm using FreeBSD 5.4-RELEASE-p1 and I found some messages about a
problem like this in freebsd-current a few months ago.
The fact is that this problem has just ocurred (on 5.4-RELEASE-p1),
probably because of a power outage (I didn't find anything in logs that
would cause a forced reboot).
Dan Nelson wrote:
> The next release should:
> RCS file: /home/ncvs/src/sys/boot/i386/boot0/boot0.S,v
[...]
Obviously the Right Way of doing such things is to move this into the
2nd stage boot loader... I can't think of any reason (except quick
hackery) why this hasn't been done that way. I mean
On Wed, May 18, 2005 4:28 pm, Dan Nelson said:
> The next release should:
>
>
> RCS file: /home/ncvs/src/sys/boot/i386/boot0/boot0.S,v
>
>
> revision 1.14 date: 2005/02/08 20:43:04; author: des; state: Exp;
> lines: +2 -2
> Remove type 0x4 (FAT12 <32MB) to make room for type 0x7 (NTFS).
>
>
> re
On Wed, May 18, 2005 4:24 pm, Brooks Davis said:
> There isn't enough space to support all 256 partition types in the 512
> bytes of space available to the mbr. Fancy multi-sector options are
> available, but we don't provide them. Many people consider this a
> feature. :)
Well that sucks :P Ma
In the last episode (May 18), Mike Jakubik said:
> Could someone tell me why our bootloader still can not recognize a
> ntfs partition, and report it as Windows instead of displaying "??" ?
The next release should:
RCS file: /home/ncvs/src/sys/boot/i386/boot0/boot0.S,v
revision 1.14
date: 2005/0
On Wed, May 18, 2005 at 04:21:32PM -0400, Mike Jakubik wrote:
> Hello,
>
> Could someone tell me why our bootloader still can not recognize a ntfs
> partition, and report it as Windows instead of displaying "??" ?
There isn't enough space to support all 256 partition types in the 512
bytes of spa
Mike Jakubik wrote:
> Could someone tell me why our bootloader still can not recognize a ntfs
> partition, and report it as Windows instead of displaying "??" ?
no space (the code is in the 1st stage boot...)
mkb.
___
freebsd-stable@freebsd.org mailing
Hello,
Could someone tell me why our bootloader still can not recognize a ntfs
partition, and report it as Windows instead of displaying "??" ?
Thanks.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
On Wed, 2005-May-18 16:03:16 +0100, Jamie Heckford wrote:
>Managed to get a dump on our system for a similar prob we are getting:
That traceback looks like a panic, not a deadlock. What was the panic
message?
>#2 0xc0513474 in panic (fmt=0xc06c3da5 "%s") at
>/usr/src/sys/kern/kern_shutdown.c:5
On Wed, 2005-May-18 06:43:37 -0600, Elliot Finley wrote:
>Had the system lock up again. This is with the new ATA mkIII patches on
>http://people.freebsd.org/~sos/ATA.
>
>I didn't get the crashdump (forgot to set dumpdev), but I did get 'ps' and
>'show lockedvnods' output from DDB. The output is i
Tim Howe wrote:
> Might I suggest looking into rsync? It has excellent support for ssh
I recommend unison:
http://www.cis.upenn.edu/~bcpierce/unison/
(does two-way synchs, not just in one direction like rdist/rsync).
mkb.
___
freebsd-stable@freebs
Vivek Khera <[EMAIL PROTECTED]> writes:
> FreeBSD 5 doesn't include the stock rdist anymore, so I'm migrating my
> processes to use the rdist6 port. However, it seems that if you run
> rdist6 as root, it ignores the -P /usr/bin/ssh flag an tries to use
> rcmd directly, which fails since my target
I use rdist regularly to manage a rack full of systems' configuration
files. FreeBSD 5 doesn't include the stock rdist anymore, so I'm
migrating my processes to use the rdist6 port. However, it seems
that if you run rdist6 as root, it ignores the -P /usr/bin/ssh flag
an tries to use rcmd
On Wed, May 18, 2005 at 07:05:04PM +0400, Andrey Smirnov wrote:
> Gary Kline wrote:
> >
> > Well, (Gary said, ddeliberately changing the ^Subject:),
> > interesting. My mother's parents are from Hungary, two of my
> > dad's grandparents from Germany.
> >
> > Didn't know about Hun
On Wednesday 18 May 2005 17:03, Jamie Heckford wrote:
> On Mon, May 16, 2005 at 06:40:01AM -0600, Elliot Finley wrote:
> > This has been happening since 5.3-R, I've been tuning different
> > parameters to no avail. I've taken the disks off of the onboard ICH5
> > controller and put them a promise
On Wed, May 18, 2005 at 11:03:08AM -0400, Alec Berryman wrote:
> Kipp Holger on 2005-05-18 14:19:53 +0200:
>
> > - can I provide any additional data?
>
> Are you in a position to restart sshd with multiple debug flags and
> have it spew to the console? (see sshd man page, options '-D' and
> '-d')
Gary Kline wrote:
Well, (Gary said, ddeliberately changing the ^Subject:),
interesting. My mother's parents are from Hungary, two of my
dad's grandparents from Germany.
Didn't know about Hungary (or Japan). China, yes. Anybody
on this geek list know any other societies where the surname
On Mon, May 16, 2005 at 06:40:01AM -0600, Elliot Finley wrote:
> This has been happening since 5.3-R, I've been tuning different parameters
> to no avail. I've taken the disks off of the onboard ICH5 controller and
> put them a promise TX4 S150 controller, but still the same thing happens.
>
> Th
Kipp Holger on 2005-05-18 14:19:53 +0200:
> - can I provide any additional data?
Are you in a position to restart sshd with multiple debug flags and
have it spew to the console? (see sshd man page, options '-D' and
'-d'). That, and connecting with ssh's verbose flag (1-3 '-v's), will
probably gi
On вт, 2005-05-17 at 15:30 -0700, Kris Kennaway wrote:
> On Wed, May 18, 2005 at 01:59:09PM +0300, Todor Dragnev wrote:
> > Hello,
> >
> > Before a couple of days ago I started /usr/local/sbin/cupsd manualy from
> > console. When I press CTRL+C to interrupt a program, the system change
> > runlev
Erich Dollansky <[EMAIL PROTECTED]> wrote:
They are not allone. China also does it and the 'official' Germany,
but it is not commonly used.
In Germany it's
family_name, first_name
^
|
this is important
or
first_name family_name
^
|
only
> On Mon, May 16, 2005 at 06:40:01AM -0600, Elliot Finley wrote:
> >The system freezes, but isn't totally dead. It'll still respond to
pings,
> >the screensaver still functions, but it won't respond to a CAD at the
> >console. But if I press 'Enter' at the console, it'll give me a 'login:'
> >pro
Hi,
I am still having a problem with sshd-behaviour which
looks similar to bin/33155 or maybe it is related to
bin/74255?
- what am I doing wrong?
- is someone else experiencing the same behaviour?
- can I provide any additional data?
the systems in question are default installations with
only a
> Well make up you mind, roger or wilco, not both of them, jezz no wonder
> that modern communication only confuses if nobody uses the same
> [EMAIL PROTECTED] protocol!
Heh, yes, using that one would earn you a slap from air traffic control!
Though I have to admit I did go check CAP413 just to
Paig Chong Woo wrote:
>
> Le 18 mai 2005 à 09:11, Riv Octovahriz a écrit :
>
>> Hi,
>>
>> Is there any support yet for Logitech Cordless Internet Pro Desktop ?
>> My keyboard works perfectly, but my mouse didn't
>>
>> Here's the output of dmesg :
>>
>> ukbd0: Logitech USB Receiver, rev 1.10/17.21,
Le 18 mai 2005 à 09:11, Riv Octovahriz a écrit :
Hi,
Is there any support yet for Logitech Cordless Internet Pro Desktop ?
My keyboard works perfectly, but my mouse didn't
Here's the output of dmesg :
ukbd0: Logitech USB Receiver, rev 1.10/17.21, addr 2, iclass 3/1
kbd1 at ukbd0
ums0: Logitech USB
Hi,
Is there any support yet for Logitech Cordless Internet Pro Desktop ?
My keyboard works perfectly, but my mouse didn't
Here's the output of dmesg :
ukbd0: Logitech USB Receiver, rev 1.10/17.21, addr 2, iclass 3/1
kbd1 at ukbd0
ums0: Logitech USB Receiver, rev 1.10/17.21, addr 2, iclass 3/1
u
56 matches
Mail list logo
