Built kernel today. Running fine. Must have been something in the 20th
snaps.
Thanks,
T
OpenBSD 6.2-current (GENERIC.MP) #0: Sun Jan 21 20:37:23 MST 2018
basepr...@chester.traceyemery.net:/sys/arch/amd64/compile/GENERIC.MP
real mem = 16951357440 (16166MB)
avail mem = 16430694400 (15669MB
Hello,
TLDR
I just wanted to send a quick message to say that the Jan 21 snapshot fixed
a kernel issue for me on amd64. The Intel firmware was installed. It also
seems faster than 6.2. Thank you!
Background:
I have a mini PC for testing Elastic. I decided to use it as my desktop.
With 6.1 the
PM, Stuart Henderson wrote:
On 2018-01-21, Base Pr1me wrote:
I'll try. Not sure I can keep it running long enough to get dmesg lol. Last
upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
and get dmesg this week, when I have more time ... Or wait until newer
s
get dmesg this week, when I have more time ... Or wait until newer
snaps and try again.
On Jan 21, 2018 10:37, "Sebastien Marie" wrote:
On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
Anyone else's system hanging randomly after upgrading to yesterday's
snapshot? Th
Cool, thanks. I'll check this out this week. Much gratitude. I'm far too
'ginned' up at the moment. ;)
On Jan 21, 2018 16:13, "Stuart Henderson" wrote:
> On 2018-01-21, Base Pr1me wrote:
> > I'll try. Not sure I can keep it running long enough to
On 2018-01-21, Base Pr1me wrote:
> I'll try. Not sure I can keep it running long enough to get dmesg lol. Last
> upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
> and get dmesg this week, when I have more time ... Or wait until newer
> snaps and tr
Ok, thanks.
On Jan 21, 2018 11:02, "Sebastien Marie" wrote:
> On Sun, Jan 21, 2018 at 06:44:56PM +0100, Adam Wolk wrote:
> > On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> > > Anyone else's system hanging randomly after upgrading to yesterday
On Sun, Jan 21, 2018 at 06:44:56PM +0100, Adam Wolk wrote:
> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> > Anyone else's system hanging randomly after upgrading to yesterday's
> > snapshot? This isn't a panic that drops to ddb. It's just freezi
Ty.
On Jan 21, 2018 10:45, "Adam Wolk" wrote:
> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> > Anyone else's system hanging randomly after upgrading to yesterday's
> > snapshot? This isn't a panic that drops to ddb. It's just freez
I'll try. Not sure I can keep it running long enough to get dmesg lol. Last
upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try
and get dmesg this week, when I have more time ... Or wait until newer
snaps and try again.
On Jan 21, 2018 10:37, "Sebastien Marie
On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> Anyone else's system hanging randomly after upgrading to yesterday's
> snapshot? This isn't a panic that drops to ddb. It's just freezing with no
> response to anything.
I haven't notice any probl
On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote:
> Anyone else's system hanging randomly after upgrading to yesterday's
> snapshot? This isn't a panic that drops to ddb. It's just freezing with no
> response to anything.
A full dmesg would be welcome
Anyone else's system hanging randomly after upgrading to yesterday's
snapshot? This isn't a panic that drops to ddb. It's just freezing with no
response to anything.
Hi!
I write here for the record so possible arvhive readers know that this
thread ended in couple of private emails with developer and he fixed
this problem. Short version and what i can narrate is that i used
GENERIC i.e. single cpu kernel and my situation was specific to this
kernel. Had i
erted right x axis y axis)
0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
HDMI and VGA is connected.
bsd.sp :
OpenBSD 5.9-beta (GENERIC.MP) #1850: Mon Jan 18 13:38:16 M
Hello !
Maybe someone is interested. I tried today to boot the Snapshot #1850
from January 18 on a MacBook 4.1 and it fails duribg boot with the
following message.
The install59.fs file works without problems and is also used before
to setup a ThinkPad and a Shuttle XS35V4.
Message :
probing: p
Hi,
Thanks for taking your time to test and write a report. I've fixed
a few issues since then and was going to ask you to test a -current
kernel. Could you also please send bug reports like this to bugs@
rather than misc@.
Thank you!
Cheers,
Mike
On Sat, Jan 16, 2016 at 20:56 +0200,
Hi!
I read a news today about Xen being enabled and tried it out with the
Jan 15th snapshot
SHA256 (install59.iso) =
8d16aeb686a1dcc3ce6e8c5192f8708d3878f7690429c843176c5e755386e4f9
on Xen v. 4.5.1 compiled from Xen sources on Debian v. 8 Jessie running
on an ordinary amd64 Intel platform
Hello
I am not sure if this is the correct list, but...
I recently installed courier from packages.
After installing courier-imap; I tried to start it with "rcctl start
courier_imap", and it seemed to hang.
So, I tried running /usr/local/libexec/imapd.rc directly, and saw an endless
loop of "-".
E
Markus Lude wrote:
> since updating to the latest snapshot on sparc64 from 22nd january ntpd
> switches back and forth between synced and unsynced clock every few
> minutes. Does anyone notice similar behavior?
Yes, I see the same on -current (amd64, sparc64).
--
Christian "naddy" Weisgerber
On Tue, 28 Jan 2014 23:32:30 +0100,
Markus Lude wrote:
> Hello,
>
> since updating to the latest snapshot on sparc64 from 22nd january
> ntpd switches back and forth between synced and unsynced clock every
> few minutes. Does anyone notice similar behavior?
I have the same o
Hello,
since updating to the latest snapshot on sparc64 from 22nd january ntpd
switches back and forth between synced and unsynced clock every few
minutes. Does anyone notice similar behavior?
my ntpd.conf:
servers de.pool.ntp.org
Regards,
Markus
On Wed, 30 Jan 2013 12:07:05 +0100
mxb wrote:
> Yasuoka forgot to commit his fix.
> I have it working.
Oops, I forgot about that fix...
I've commited. Also here is the diff. Thanks,
Index: npppd_auth.c
===
RCS fil
Yasuoka forgot to commit his fix.
I have it working.
//maxim
On 30 jan 2013, at 11:54, Robert Blacquiere wrote:
> Hi,
>
> I run in to a issue using npppd with radius. It look to me the parsing
> of radius port info is not working.
>
> I have: authentication section:
&
Hi,
I run in to a issue using npppd with radius. It look to me the parsing
of radius port info is not working.
I have: authentication section:
authentication RADIUS type radius {
authentication-server {
address 192.168.0.1 port 1812 secret "hogehoge"
}
accou
- Original Message -
| On Fri, Jan 04, 2013 at 02:10:02PM -0800, James A. Peltier wrote:
| > - Original Message -
| > | On Jan 04 12:05:53, jpelt...@sfu.ca wrote:
| > | > I just tried to use the latest amd64 snapshot to prepare for an
| > | > upgrade to our fire
On Fri, Jan 04, 2013 at 02:10:02PM -0800, James A. Peltier wrote:
> - Original Message -
> | On Jan 04 12:05:53, jpelt...@sfu.ca wrote:
> | > I just tried to use the latest amd64 snapshot to prepare for an
> | > upgrade to our firewall. We use DHCP during initial install
- Original Message -
| On Jan 04 12:05:53, jpelt...@sfu.ca wrote:
| > I just tried to use the latest amd64 snapshot to prepare for an
| > upgrade to our firewall. We use DHCP during initial installation
| > to PXE boot and perform the install at which point we configure
| > th
On Jan 04 12:05:53, jpelt...@sfu.ca wrote:
> I just tried to use the latest amd64 snapshot to prepare for an upgrade to
> our firewall. We use DHCP during initial installation to PXE boot and
> perform the install at which point we configure through site52.tgz. However,
> during
I just tried to use the latest amd64 snapshot to prepare for an upgrade to our
firewall. We use DHCP during initial installation to PXE boot and perform the
install at which point we configure through site52.tgz. However, during
installation and after boot DHCP reports the following error
C
Hi,
On Wed, Jan 11, 2012 at 12:27:56PM +0100, Simon Kuhnle wrote:
> openbsd.cs.fau.de will be down on January 14th,
> from 08:00 to approximately 12:00 o'clock
> due to yearly power system maintenance works.
Same problem I had last year:
the RAID controller forgot his setup again a
.
POD
POL
Carrier
20GP
40GP
40HQ
LCL<3 CBM
T/T
Validity
SURABAYA
DALIAN
APL
460
670
670
29
17
25TH,JAN
TIANJIN
PAN
380
650
650
17
16
QINGDAO
SINO
355
620
620
19
13
LIANYUNGANG
MCC
420
760
760
26
15
SHANGHAI
MCC
310
620
620
18
13
NINGBO
YML
310
that is sage advice for any of us.
I, myself got more than a little help here and got some good suggestions
(including some hardware I forgot about). I think next month, I will get a
framegrabber device with built-in ethernet port and can also manage BIOS and
PCU tasks).
reading never hurts and i
John Tate,
Consider living a life of service, instead of complaining that the
list has not helped you enough, try to figure out what you can do to
better serve the list. So, work more before hitting the list, don't
panic, give it a day or two. Read the archives and relevant man pages
always, then
I guess you will have to learn the hardest and best way then. On your own
John Tate wrote:
> I will also add that if I am asking stupid questions then by axiom (look it
> up in a dictionary) I AM SAYING I AM LEARNING. You tool!
>
> On Mon, Dec 12, 2011 at 9:17 AM, John Tate wrote:
>
>
>> I n
On Mon, 12 Dec 2011 10:54:36 +1100, richo wrote:
Quoting the current resident full-of-himself little shit.
I have a filter that sends stuff from him to /dev/null but he keeps
getting answers that raise his google rating because you all go on
quoting him.
He is an oxygen thief - don't give him an
>> On Mon, Dec 12, 2011 at 9:17 AM, John Tate wrote:
>>> I never claimed to be an OpenBSD guru. Ever. I am an OpenBSD n00b. Here,
>>> I'll put this on the list.
>>> ^^
On 12/12/11 09:21 +1100, John Tate wrote:
>Whoops, I hate gmai
I will also add that if I am asking stupid questions then by axiom (look it
up in a dictionary) I AM SAYING I AM LEARNING. You tool!
On Mon, Dec 12, 2011 at 9:17 AM, John Tate wrote:
> I never claimed to be an OpenBSD guru. Ever. I am an OpenBSD n00b. Here,
> I'll put this on the list.
>
> I am
Whoops, I hate gmail sometimes. That was for Jan
On Mon, Dec 12, 2011 at 9:21 AM, John Tate wrote:
> In other words: stop wasting your breath I'm never leaving. If they kick
> me out, well, I'll use seven proxies!
>
>
> On Mon, Dec 12, 2011 at 9:17 AM, John Tate wrote
In other words: stop wasting your breath I'm never leaving. If they kick me
out, well, I'll use seven proxies!
On Mon, Dec 12, 2011 at 9:17 AM, John Tate wrote:
> I never claimed to be an OpenBSD guru. Ever. I am an OpenBSD n00b. Here,
> I'll put this on the list.
>
> I am John Norman Tate born
I never claimed to be an OpenBSD guru. Ever. I am an OpenBSD n00b. Here,
I'll put this on the list.
I am John Norman Tate born September 1987 to two loving parents and the
only part of OpenBSD I think I am good with is using it in accordance to
the manuals when I read them properly. I also underst
On Thu, Jan 13, 2011 at 1:15 PM, Dragos wrote:
> On 2011-01-13, at 7:31 AM, valdis.kletni...@vt.edu wrote:
>
> It was my (apparently) lame attempt at being whimsical. Should have made it
>
I found it amusing. In fact I intend to steal it for my own uses. But maybe
"postpenu
On 2011-01-13, at 7:31 AM, valdis.kletni...@vt.edu wrote:
> On Thu, 13 Jan 2011 03:23:49 PST, Dragos Ruiu said:
>
>> It's been up on the site for a while with a Dec 29 deadline,
>> but this is the real last call for submissions.
>
>
>
> If it's the real l
On Thu, Jan 13, 2011 at 5:02 PM, Randal L. Schwartz
wrote:
>>>>>> "Dragos" == Dragos Ruiu writes:
>
> Dragos> It's been up on the site for a while with a Dec 29 deadline,
> Dragos> but this is the real last call for submissions.
>
> Really?
> "Dragos" == Dragos Ruiu writes:
Dragos> It's been up on the site for a while with a Dec 29 deadline,
Dragos> but this is the real last call for submissions.
Really? Then why did you use "Penultimate" (which means "next to last")
instead of "Ultimate" in the subject line?
Yours for a more
"First they ignore you, then they ridicule you,
then they fight you, then you win." -- Mahatma Ghandi.
Well if Fox's new comedy show "Breaking In" is any
indication, infosec has now entered Ghandi's second
stage. http://goo.gl/ZpLDp [youtube] (hat tip to Adam
O'Donnell for this humorous find, and
I have the same thing on a GENERIC.MP i386
I will send a dmesg shortly.
I am on a really crappy connection here, so I would prefer to fix this over
downloading another snap, if possible.
I can only get another install48.iso through SFTP from my server. All FTP and
HTTP connections stall from he
Just upgraded an amd64 system from the Nov.11 snap to Jan. 8th and now X
freezes the system. Tried again with a clean install of the Jan 9th
snap, thinking it might have been a fluke, but I'm still getting
freezes. It had been working fine with the Nov. 11 snap; no xorg.conf
needed.
s
orts.
I went from:
OpenBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009
to
OpenBSD 4.7-beta (GENERIC.MP) #402: Wed Jan 27 19:29:54 MST 2010
I am getting an error in the dmesg, and em0 no longer appears in
ifconfig:
em0 at pci0 dev 25 function 0 "Intel ICH9 IGP AMT" rev 0x02: apic 8
int
On Mon, Feb 01, 2010 at 11:33:49AM +0100, Rogier Krieger wrote:
> On Mon, Feb 1, 2010 at 07:32, Steve Williams
> wrote:
> > I have downloaded the current cvs code and compiled it. It exhibits the
> > same problem, missing em0.
>
> It seems to nicely detect the hardware, just not liking its EEPRO
On Mon, Feb 1, 2010 at 07:32, Steve Williams
wrote:
> I have downloaded the current cvs code and compiled it. It exhibits the
> same problem, missing em0.
It seems to nicely detect the hardware, just not liking its EEPROM
contents and stopping initialisation there. While you should take a
develo
ously a
snapshot or actually 4.6. Regardless, I upgraded it to the snapshot
from January 28. I booted the snapshot iso and did an upgrade. Ran
sysmerge & slowly working my way through all the ports.
I went from:
OpenBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009
to
OpenBSD 4.7-beta
enBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009
to
OpenBSD 4.7-beta (GENERIC.MP) #402: Wed Jan 27 19:29:54 MST 2010
I am getting an error in the dmesg, and em0 no longer appears in ifconfig:
em0 at pci0 dev 25 function 0 "Intel ICH9 IGP AMT" rev 0x02: apic 8 int
21 (irq 3)em0: The EEP
0
hw.physmem=4117725184
hw.usermem=4117712896
hw.ncpufound=4
and dmesg is
OpenBSD 4.6-current (GENERIC) #59: Wed Jan 20 06:45:07 MST 2010
t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 4117725184 (3926MB)
avail mem = 4002447360 (3817MB)
mainbus0 at root
bios0 at main
On Sat, Jan 23, 2010 at 6:43 PM, Marco Peereboom wrote:
> This is exactly what was predicted what would happen.
>
> No benefit to publish the digests minus a bunch of people whining that
> the damn digests are off for obvious reasons.
i am not sure if i would categorize these
This is exactly what was predicted what would happen.
No benefit to publish the digests minus a bunch of people whining that
the damn digests are off for obvious reasons.
On Sun, Jan 24, 2010 at 12:30:35AM +, Mikolaj Kucharski wrote:
> Hi,
>
> On all mirrors and on main openb
If you don't have time to search the archives, you could at least
check today's mail.
On Sat, Jan 23, 2010 at 7:30 PM, Mikolaj Kucharski
wrote:
> Hi,
>
> On all mirrors and on main openbsd server base46.tgz is giving failed
> cksum error. Not sure is that random error, as I
Jan 20 06:46:42 MST 2010
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
$ cksum -c SHA256
(SHA256) INSTALL.i386: OK
(SHA256) INSTALL.linux: OK
(SHA256) base46.tgz: FAILED
(SHA256) bsd: OK
(SHA256) bsd.mp: OK
(SHA256) bsd.rd: OK
(SHA256) cd46.iso: OK
(SHA256) cdboot: OK
(SHA256
Julian Leyh wrote:
> Am 23.01.10 07:05, schrieb James Hartley:
>> A quick search in the misc@ archives& PR database didn't reveal that anyone
>> has mentioned this before.
>>
>> In installing the 20 January (#511) i386 snapshot, I received a SHA256
>> mismatch on base46.tgz. Otherwise, the snapsh
On Fri, Jan 22, 2010 at 10:05:13PM -0800, James Hartley wrote:
> A quick search in the misc@ archives & PR database didn't reveal that anyone
> has mentioned this before.
>
> In installing the 20 January (#511) i386 snapshot, I received a SHA256
> mismatch on base46.tgz.
Am 23.01.10 07:05, schrieb James Hartley:
A quick search in the misc@ archives& PR database didn't reveal that anyone
has mentioned this before.
In installing the 20 January (#511) i386 snapshot, I received a SHA256
mismatch on base46.tgz. Otherwise, the snapshot installs as expected.
Why ch
On Fri, Jan 22, 2010 at 10:05:13PM -0800, James Hartley wrote:
> A quick search in the misc@ archives & PR database didn't reveal that anyone
> has mentioned this before.
>
> In installing the 20 January (#511) i386 snapshot, I received a SHA256
> mismatch on base46.tgz.
A quick search in the misc@ archives & PR database didn't reveal that anyone
has mentioned this before.
In installing the 20 January (#511) i386 snapshot, I received a SHA256
mismatch on base46.tgz. Otherwise, the snapshot installs as expected.
FYI & FWIW.
Jim
I just installed the newest amd64 snapshot, and pkg_add installs
quirks-1.6 and then fails, complaining about not being able to load
OpenBSD/LibSpec.pm.
Installing pkg_add (only) from /usr/src seems to solve the issue.
If this has been reported before, sorry!
Joachim
On Wed, Jan 21, 2009 at 6:08 AM, Stuart Henderson wrote:
> On 2009-01-19, Bryan wrote:
>> Greetings,
>>
>>
>> I am still having issues with the re(4) interface on my server. I
>> mentioned this on the list, and was told that the re(4) fix was in. I
>> am
On 2009-01-19, Bryan wrote:
> Greetings,
>
>
> I am still having issues with the re(4) interface on my server. I
> mentioned this on the list, and was told that the re(4) fix was in. I
> am running the 13 Jan 2009 snapshot, and I can still reproduce the
> error on a regular
I don't disable apm at boot. Have you done so ?
Regards.
hyjial
2009/1/19 Bryan :
> Greetings,
>
>
> I am still having issues with the re(4) interface on my server. I
> mentioned this on the list, and was told that the re(4) fix was in. I
> am running the 13 Jan 2009 sn
Greetings,
I am still having issues with the re(4) interface on my server. I
mentioned this on the list, and was told that the re(4) fix was in. I
am running the 13 Jan 2009 snapshot, and I can still reproduce the
error on a regular basis. It goes like this...
1. push the power button
2
On Fri, Jan 09, 2009 at 09:26:00PM -0800, Bryan wrote:
> On Fri, Jan 9, 2009 at 9:16 PM, Bryan wrote:
> > Greetings,
> >
> > previous snapshots were able to boot with no issues. I'm using
> > GENERIC.MP, and the panic occurs when using GENERIC.SP.
be sure to
On Fri, Jan 9, 2009 at 9:16 PM, Bryan wrote:
> Greetings,
>
> previous snapshots were able to boot with no issues. I'm using
> GENERIC.MP, and the panic occurs when using GENERIC.SP.
>
> here is the panic message: (typed)
>
>
> npx0 at isa0 port 0xf0/16: repor
lbum:
http://picasaweb.google.com/brakeb/CrashUsing08jan2009Snapshot?feat=directlink
please advise. I originally thought that this panic was due to the
re(4) that was not reset.
I can reproduce this. I first received this error right after I did
the 08 jan 2009 snapshot. I did mention this ear
ERIC) #651: Tue Jan 22 17:34:45 MST 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 498 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 536358912 (511MB)
avail mem = 5
Many thanks for your note. I am out of the office until Tuesday, January 2. I
will be checking email infrequently during this time, but will return your
message on my return.
best wishes for a happy new year.
CanSecWest 2007 CALL FOR PAPERS
VANCOUVER, Canada -- The eighth annual CanSecWest applied technical security
conference - where the eminent figures in the international security industry
will get together share best practices and technology - will be held in
downtown Vancouver at the the Mariot
hello,
i think i saw something similar on the list a bit earlier.
tried nForce4 mobo with amd64 x2 cpu and bsd.mp (jan 30 snapshot).
have got lotsa wd problems so serious so the system even drops to ddb
(see below). yeah, and there are problems besides wdX - i could not
login to the system
Hi,
For those who have time to swing by, have a talk with us or even better
help out, for the rest of the week, OpenBSD will be at Solutions Linux
in the CNIT, Paris la Defense
http://www.solutionslinux.fr/fr/index.php
Booth slaves welcome
Wim.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
76 matches
Mail list logo
