Am 06.06.2012 17:09, schrieb Henning Brauer:
> * Andre Keller [2012-06-06 16:05]:
>> is any body running OpenBSD as a XEN HVM guest?
> nobody sane.
I hope on someone as insane as me then... :-)
>
>> ddb> trace
>> ddb> dmesg
> the actual panic is missing.
>
Hmm, ist it possible to get that from
* Andre Keller [2012-06-06 16:05]:
> is any body running OpenBSD as a XEN HVM guest?
nobody sane.
> ddb> trace
> ddb> dmesg
the actual panic is missing.
--
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services, http://bsws.de, Full-Service ISP
Secure Hosting, Mail and DNS Services
Hi
is any body running OpenBSD as a XEN HVM guest? I have a difficult time
accomplish that...
The XEN guest does boot up and is usable. When f.e. do a cvs checkout of
ports the machine panics about every other time.
I know that is not really a supported configuration but if someone
managed to ge
;>>> On Mon, May 14, 2012 at 5:56 PM, Marcin Markowski
>>>> wrote:
>>>>>
>>>>>
>>>>> B Hi,
>>>>>
>>>>> I have a problem running a freshly installed OpenBSD 5.1 amd64 on
>>>>> Intel'
Hi,
I have a problem running a freshly installed OpenBSD 5.1 amd64 on
Intel's server platform. During boot kernel panic occurs, and the only
way to boot is to disable ACPI.
System: OpenBSD 5.1 amd64
Server: Intel SR2600URBRP, 2x Xeon X5650, 6GB RAM
Attachment contains panic message, k
On Thu, Apr 12, 2012 at 1:00 PM, Mihai Popescu wrote:
> Hmm, I see in the text that should be True/False value, is it working
> with on and off ?
>
>From xorg.conf(5):
The following boolean option values are recognised as TRUE:
1, on, true, yes
and the following boolean option valu
Hmm, I see in the text that should be True/False value, is it
working with on and off ?
Hello.
I tried to turn off the hardware acceleration with DRI, NoAccel & Accel
xorg.conf options but without success - in the /var/log/Xorg.0.log
I found messages about unused NoAccel & Accel options and activated
DRI driver.
The fragment from my /etc/X11/xorg.conf on i386 OpenBSD-4.9:
...
Secti
00, Alexei Malinin wrote:
>>>> Hello.
>>>>
>>>> Can anybody comment this kernel panic event?
>>>
>>> I will look into it.
>>>
>>> What were you doing at the time?
>>
>> rdesktop was running, I moved cursor from rdesk
Good morning,
I have a Sun Ultra 5 with 256 MB RAM and 40 GB IDE drive running OpenBSD
5.0-release (no patches). It is a testing server with no confidential or
sensitive information. I also have a Proxim "Silver" 802.11b/g wireless
card that uses the ath0 driver and it has worked flawlessly in t
Thank you very much.
It works, i can now use bge0 on the mac mini.
(OpenBSD 4.9)
Wesley.
thank's, small forget ;-)
I will try it .
On Fri, 23 Dec 2011 11:51:33 +0100, Mike Belopuhov
wrote:
> On Fri, Dec 23, 2011 at 11:43 AM, Wesley M.
wrote:
>> Hi,
>>
>> So i installed a fresh OpenBSD 4.9 to try to patch the files : brgphy.c
>> and miidevs
>> I have the following error when compilin
On 2011/12/19 17:43, Wesley M. wrote:
> Ok, thank's.
> Therefore, i have a problem. I use mailserv project, and it works only on
> 4.8; 4.9 RELEASE. Not on 5.0
> Is there a way for me to have a 4.9 with patches ?
> In short, is it possible to have a patch to use with 4.9-stable ?
>
> Thank you ver
md word write error" just after.
>> And i can't use keyboard at UKC Prompt :(
>>
>> Wesley.
>>
>> On Mon, 19 Dec 2011 12:51:58 +, Stuart Henderson
>>
>> wrote:
>> > On 2011/12/19 16:10, Wesley M. wrote:
>> >> So i
>>
yboard at UKC Prompt :(
>
> Wesley.
>
> On Mon, 19 Dec 2011 12:51:58 +, Stuart Henderson
> wrote:
> > On 2011/12/19 16:10, Wesley M. wrote:
> >> So i
> >> tried to use 5.0 RELEASE.
> >> This time, it formats quickly. But it is the same
> >>
gt; So i
>> tried to use 5.0 RELEASE.
>> This time, it formats quickly. But it is the same
>> way : kernel panic when it starts the network.
>>
>> The following message
>> appear :
>> Starting network
>> panic: mii_phy_setmedia
>>
Try this diff against -current. You'll have to apply
the patch from sys/dev/mii and run 'make' afterwards
to regenerate the headers.
Index: miidevs
===
RCS file: /cvs/src/sys/dev/mii/miidevs,v
retrieving revision 1.116
diff -u -p -r1
On 2011/12/19 16:10, Wesley M. wrote:
> So i
> tried to use 5.0 RELEASE.
> This time, it formats quickly. But it is the same
> way : kernel panic when it starts the network.
>
> The following message
> appear :
> Starting network
> panic: mii_phy_setmedia
> Stopp
ave you tried to disable whatever it is on boot>?
i tried disable bge0, boot, i still have a kernel panic just after
"Starting Network"
On Mon, Dec 19, 2011 at 04:10:16PM +0400, Wesley M. wrote:
>
> Here is the ps message : http://i43.tinypic.com/mkufyo.jpg
> Here is the
> trace message : http://i40.tinypic.com/25syfxf.jpg
Have you tried to disable whatever it is on boot>?
--
This message has been scanned for viruses and
dange
Hi,
I tried to install OpenBSD 4.9 on an Apple mac mini (new
generation).
Model : A1347 ;
Core i5, thunderbolt Technology, HD 500Go
At
installation using 4.9 RELEASE :
It takes a long time to format slides.
At the reboot : i have a kernel panic just after "starting network"
So
Hi,
I tried to install OpenBSD 4.9 on an Apple mac mini (new
generation).
Model : A1347
Core i5, thunderbolt Technology, HD 500Go
At
installation using 4.9 RELEASE :
It takes a long time to format slides.
At the reboot : i have a kernel panic just after "starting network"
So i
tr
Hi!
Am 09.11.2011 18:05, schrieb Brynet:
> The previous patch avoids touching the msr at all if ACPI indicates speed
> scaling is unavailable, this should prevent your panic.
>
> Both i386/amd64(..fixed) patches attached below.
Your patch works! Thanks a lot!
Also installed 5.0/i386 on the mach
On Thu, Nov 10, 2011 at 11:45:06AM +1100, Jonathan Gray wrote:
> > > On 09.11.2011 14:40, Avi Kivity wrote:
> > > > Actually, it looks like an OpenBSD bug. According to the AMD
> > > > documentation:
> > > >> "The current P-state value can be read using the P-State Status
> > > >> Register. The P-
On Wed, Nov 09, 2011 at 12:05:04PM -0500, Brynet wrote:
> On Wed, Nov 09, 2011 at 03:35:01PM +0100, Walter Haidinger wrote:
> > Does the patch fix the following?
> >
> > I've forwarding the bug report to the Linux KVM developers.
> > The response:
>
> The patch in my first email should be enough
> On Mon, Nov 07, 2011 at 03:51:50PM +0100, Walter Haidinger wrote:
> > cpu0: AMD Phenom(tm) II X6 1100T Processor ("AuthenticAMD" 686-class, 512KB
> > L2 cache) 3.31 GHz
> > cpu0:
> > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,POPCN
Am 09.11.2011 18:16, schrieb Brynet:
>
> On Wed, Nov 09, 2011 at 08:38:01AM +0100, Walter Haidinger wrote:
>> I did run i386 bsd.
>> /usr/src/sys/arch/i386/i386/k1x-pstate.c also has
>> k1x_acpi_init(cstate, msr);
>> in line 193 of 5.0's k1x_init().
>> Can you send me the patch below for i386 to
On Wed, Nov 09, 2011 at 08:38:01AM +0100, Walter Haidinger wrote:
> I did run i386 bsd.
> /usr/src/sys/arch/i386/i386/k1x-pstate.c also has
> k1x_acpi_init(cstate, msr);
> in line 193 of 5.0's k1x_init().
> Can you send me the patch below for i386 to test?
>
> Thanks,
> Walter
What?
Apply the
> They're pretending to be an AMD K10 processor.
Exactly. What they are doing is wrong.
They are pretending to be a AMD K10 processor _badly_, and then they
think they can say "oh, but you need to check all these other registers
too".
A machine with that setup has never physically existed.
On Wed, Nov 09, 2011 at 03:35:01PM +0100, Walter Haidinger wrote:
> Does the patch fix the following?
>
> I've forwarding the bug report to the Linux KVM developers.
> The response:
The patch in my first email should be enough to avoid the issue, the i386
patch was fine, only the amd64 patch was
Am 09.11.2011 16:04, schrieb Theo de Raadt:
>> EDX is zero in a Linux guest (i386 and x86_64).
>
> So?
>
> What is it on the real hardware?
0x3f9
However, they asked me to test inside a Linux guest.
On the host itself, the x86info tool shows for all cores:
eax in: 0x8007, eax = eb
Hi!
Am 08.11.2011 19:33, schrieb Brynet:
On Tue, Nov 08, 2011 at 01:27:37PM -0500, Brynet wrote:
@@ -190,7 +190,7 @@ k1x_init(struct cpu_info *ci)
#if NACPICPU> 0
msr = rdmsr(MSR_K1X_STATUS);
- k1x_acpi_init(cstate, msr);
+ k1x_acpi_init(cstate);
Whoops, fixed patch f
Am 08.11.2011 10:32, schrieb Walter Haidinger:
> I also got informed that is a VM emulator bug and
> have therefore forwarded the bug to "upstream"
> k...@vger.kernel.org.
FYI, more evidence. Linux dmesg shows:
kvm: cpu0 unhandled rdmsr: 0xc0010063
Walter
Am 08.11.2011 19:33, schrieb Brynet:
>
> On Tue, Nov 08, 2011 at 01:27:37PM -0500, Brynet wrote:
>> @@ -190,7 +190,7 @@ k1x_init(struct cpu_info *ci)
>>
>> #if NACPICPU > 0
>> msr = rdmsr(MSR_K1X_STATUS);
>> -k1x_acpi_init(cstate, msr);
>> +k1x_acpi_init(cstate);
>
> Whoops, fixed
Am 08.11.2011 19:27, schrieb Brynet:
>
> On Mon, Nov 07, 2011 at 03:51:50PM +0100, Walter Haidinger wrote:
>> cpu0: AMD Phenom(tm) II X6 1100T Processor ("AuthenticAMD" 686-class, 512KB
>> L2 cache) 3.31 GHz
>> cpu0:
>> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLU
On Tue, Nov 08, 2011 at 01:27:37PM -0500, Brynet wrote:
> @@ -190,7 +190,7 @@ k1x_init(struct cpu_info *ci)
>
> #if NACPICPU > 0
> msr = rdmsr(MSR_K1X_STATUS);
> - k1x_acpi_init(cstate, msr);
> + k1x_acpi_init(cstate);
Whoops, fixed patch for amd64.
-Bryan.
Index: amd64/amd64/k1
On Mon, Nov 07, 2011 at 03:51:50PM +0100, Walter Haidinger wrote:
> cpu0: AMD Phenom(tm) II X6 1100T Processor ("AuthenticAMD" 686-class, 512KB
> L2 cache) 3.31 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,POPCNT
> ...
>
Am 07.11.2011 16:06, schrieb Alexander Polakov:
> k1x_init() is not related to vmt, it is from k1x-pstate.c, which
> is cpu power state driver for K10 processors.
Because of this reference, I found a workaround:
Rather than running 5.0 under the host cpu (PhenomII),
I emulate an older cpu (e.g. a
Am 07.11.2011 16:06, schrieb Alexander Polakov:
> I don't know of an easy way to disable it but recompiling the kernel
> with this:
>
> Index: sys/arch/i386/i386/machdep.c
> ===
> RCS file: /cvs/src/sys/arch/i386/i386/machdep.c,v
> re
* Walter Haidinger [07 14:15]:
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins
> ioapic0: misconfigured as apic 0, remapped to apid 1
> bios0: ROM list: 0xc/0x9e00 0xca000/0xa00 0xcb000/0xa00 0xcc000/0x600
> 0xcc800/0x2400
> vmt0 at mainbus0
> vmware: open failed, eax=564
Am 07.11.2011 15:34, schrieb Norman Golisz:
> I don't know either. But, you could try to disable the vmt(4) driver at
> boot. At the boot prompt, type "boot -c" to trigger the UKC. At the UKC
> prompt,
> type "disable vmt". Then type "quit". If your system boots up without errors,
> you can preser
On Mon Nov 7 2011 11:10, Walter Haidinger wrote:
> Hi!
>
> Trying to upgrade to 5.0 fails with a kernel panic
> (vmt0, see dmesg below). Previous 4.9 worked fine,
> also 5.0 bsd.rd boots (dmesg below too).
>
> The VMware Tools driver seems to miss something -
> "
On 07/11/11 12:10, Walter Haidinger wrote:
Hi!
Trying to upgrade to 5.0 fails with a kernel panic
(vmt0, see dmesg below). Previous 4.9 worked fine,
also 5.0 bsd.rd boots (dmesg below too).
The VMware Tools driver seems to miss something -
"vmt0: failed to open backdoor RPC channel
Hi!
Trying to upgrade to 5.0 fails with a kernel panic
(vmt0, see dmesg below). Previous 4.9 worked fine,
also 5.0 bsd.rd boots (dmesg below too).
The VMware Tools driver seems to miss something -
"vmt0: failed to open backdoor RPC channel (TCLO protocol)" -
which is correct, as OpenBS
On Sat, Nov 5, 2011 at 10:29 AM, Norman Golisz wrote:
> On Sat Nov 5 2011 15:07, David Vasek wrote:
> > On Sat, 5 Nov 2011, Norman Golisz wrote:
> >
> > >On Sat Nov 5 2011 09:13, Forman, Jeffrey wrote:
> > >>Am I barking up the wrong tree trying to deduce if I really do have a
> > >>hardware pr
On Sat Nov 5 2011 15:07, David Vasek wrote:
> On Sat, 5 Nov 2011, Norman Golisz wrote:
>
> >On Sat Nov 5 2011 09:13, Forman, Jeffrey wrote:
> >>Am I barking up the wrong tree trying to deduce if I really do have a
> >>hardware problem? I am open to accepting diffs and compiling from source if
>
On Sat, 5 Nov 2011, Norman Golisz wrote:
On Sat Nov 5 2011 09:13, Forman, Jeffrey wrote:
Am I barking up the wrong tree trying to deduce if I really do have a
hardware problem? I am open to accepting diffs and compiling from source if
other developers think there might be a bug to fix here.
On Sat Nov 5 2011 09:13, Forman, Jeffrey wrote:
> Am I barking up the wrong tree trying to deduce if I really do have a
> hardware problem? I am open to accepting diffs and compiling from source if
> other developers think there might be a bug to fix here.
It seems to be a hardware fault. To trap
On Sat, Nov 5, 2011 at 8:29 AM, Norman Golisz wrote:
> Hi Jeffrey,
>
> On Sat Nov 5 2011 07:49, Forman, Jeffrey wrote:
> > I am in the process of building a new OpenBSD i386 5.0-release Intel Atom
> > D510-based fw/router. I was editing some config files on the box in emacs
> > when the process
Hi Jeffrey,
On Sat Nov 5 2011 07:49, Forman, Jeffrey wrote:
> I am in the process of building a new OpenBSD i386 5.0-release Intel Atom
> D510-based fw/router. I was editing some config files on the box in emacs
> when the process threw a core dump. Thinking perhaps it was just emacs, I
> went to
I am in the process of building a new OpenBSD i386 5.0-release Intel Atom
D510-based fw/router. I was editing some config files on the box in emacs
when the process threw a core dump. Thinking perhaps it was just emacs, I
went to do something else, 'sudo pkg_add -v mutt', and received a coredump
ag
2011/9/28 Alexei Malinin :
> Owain Ainsworth wrote:
>> On Tue, Sep 27, 2011 at 01:24:36PM +0400, Alexei Malinin wrote:
>>> Hello.
>>>
>>> Can anybody comment this kernel panic event?
>>
>> I will look into it.
>>
>> What were you doin
Owain Ainsworth wrote:
> On Tue, Sep 27, 2011 at 01:24:36PM +0400, Alexei Malinin wrote:
>> Hello.
>>
>> Can anybody comment this kernel panic event?
>
> I will look into it.
>
> What were you doing at the time?
rdesktop was running, I moved cursor from rdesktop
On Tue, Sep 27, 2011 at 01:24:36PM +0400, Alexei Malinin wrote:
> Hello.
>
> Can anybody comment this kernel panic event?
I will look into it.
What were you doing at the time? This is pure 4.9 yes?
-0-
--
It is now pitch dark. If you proceed, you will likely fall into a pit.
Hello.
Can anybody comment this kernel panic event?
--
Alexei Malinin
from syslog:
-
Sep 21 19:04:24 magc /bsd: inteldrm0: gpu hung!
Sep 21 19:04:24 magc /bsd: render error detected, EIR: 10
Sep 21 19:04:24 magc /bsd: IPEIR: 0x
Sep 21 19:04:24 magc /bsd: IPEHR
On Thu, Jun 23, 2011 at 5:16 PM, Matthew Dempsky wrote:
> Does it work if you try booting with "boot bsd -a" and manually tell
> it to use sd1a as the root device?
And if so, please include the output of running disklabel on each of your disks.
Also, what version of boot(8) do you have installed
On Thu, Jun 23, 2011 at 1:58 PM, Jens A. Griepentrog
wrote:
> In contrast to 4.8 (GENERIC.MP) #335 or 4.9 (GENERIC.MP) #819 kernels
> the snapshot 4.9-current (GENERIC) #47 kernel does not recognize sd1 as
> boot disk even when the MO drive sd0 is empty. The system ends up in ddb
> mode without ha
Dear [misc] mailing list(eners),
My amd64 system [4.8 (GENERIC.MP) #335] contains three sd? drives:
sd0: MO drive
sd1: boot disk
sd2: additional disk
In contrast to 4.8 (GENERIC.MP) #335 or 4.9 (GENERIC.MP) #819 kernels
the snapshot 4.9-current (GENERIC) #47 kernel does not recognize sd1 as
bo
On 2011-06-23, Raimo Niskanen wrote:
> On Thu, Jun 23, 2011 at 12:32:40AM +0200, ter Voorde Informatiesystemen wrote:
>> You are completely right.
>>
>> I was only wondering if I do not set the variable explicitly, the
>> default value would be 0 or 1.
>
> Ok, that I can not find from the docume
On Thu, 23 Jun 2011 11:27:09 +0200
Raimo Niskanen wrote:
> Ok, that I can not find from the documentation,
> only that setting it to 0 most probably is a change.
I believe the defaults are conveniently listed in the comments next to
the settings in sysctl.conf. I don't see why they'd change occas
wrote:
> >>>On Wed, 22 Jun 2011, ter Voorde Informatiesystemen wrote:
> >>>
> >>>
> >>>>In /etc/sysctl.conf I see the following commented line:
> >>>>
> >>>>#ddb.panic=0
> >>>>
> >>>>a
On 2011 Jun 23 (Thu) at 00:32:40 +0200 (+0200), ter Voorde Informatiesystemen
wrote:
:You are completely right.
:
:I was only wondering if I do not set the variable explicitly, the
:default value would be 0 or 1.
:
:Kind regards,
:
:Frank
:
For some sysctls, the default is 0, for others, the defa
onf I see the following commented line:
#ddb.panic=0
and nothing else about ddb.panic is present there. With other words,
I guess: 'ddb.panic=0' is the default boot time setting and does not
have to be set explicitly.
I now suppose: on a kernel panic, this system will not drop into ddb
(
On Wed, 22 Jun 2011 18:11:36 +0300
Gregory Edigarov wrote:
> On Wed, 22 Jun 2011 11:45:49 -0300
> Marcos Laufer wrote:
>
> > ddb.panic=0 will boot instead of dropping you into a ddb?
> greg@greg:~$ banner YES
> # # ### #
> # # # # #
> # # # #
>##
>>
> >> and nothing else about ddb.panic is present there. With other words,
> >> I guess: 'ddb.panic=0' is the default boot time setting and does not
> >> have to be set explicitly.
> >>
> >> I now suppose: on a kernel panic, this system will
On Wed, 22 Jun 2011 11:45:49 -0300
Marcos Laufer wrote:
> ddb.panic=0 will boot instead of dropping you into a ddb?
greg@greg:~$ banner YES
# # ### #
# # # # #
# # # #
###
## #
## # #
####
en wrote:
>
>
>> In /etc/sysctl.conf I see the following commented line:
>>
>> #ddb.panic=0
>>
>> and nothing else about ddb.panic is present there. With other words,
>> I guess: 'ddb.panic=0' is the default boot time setting and does not
>>
matiesystemen wrote:
In /etc/sysctl.conf I see the following commented line:
#ddb.panic=0
and nothing else about ddb.panic is present there. With other words,
I guess: 'ddb.panic=0' is the default boot time setting and does not
have to be set explicitly.
I now suppose: on a kernel p
ddb.panic=0' is the default boot time setting and does not
> have to be set explicitly.
you have wrong guess, go do
# sysctl ddb.panic
> I now suppose: on a kernel panic, this system will not drop into ddb
> (kind-of waiting for someone to retrieve useful information about the
>
nd does not
> have to be set explicitly.
>
> I now suppose: on a kernel panic, this system will not drop into ddb
> (kind-of waiting for someone to retrieve useful information about
> the panic) and is most likely to reboot. Is that correct?
Exactly the opposite:
$ sysctl ddb.panic
d
Hi there,
At first, I would like to apologize for the possibility that this e-mail
message might fatigue you, but I just want to be sure.
I would like to know if my machine automatically reboots at a kernel
panic (if it's not failing too much because of malfunctioning hardware,
Hi
While testing pfsync over IPsec I have spotted a bug. While it is
documented in man pfsync that enc0 should be used as syncdev when using
pfsync over ipsec IMHO the system should not crash when the physical
interface is used.
This bug can be spotted on 4.8/i386, 4.9/i386 and Current/i386. I ha
Thank you for the notification, I fixed the daily limit.
On 03/27/11 19:21, Sha'ul wrote:
At the boot> prompt I put bsd.rd and it probes and gives me the
install options (I)nstall (U)pgrade (S)hell, I went to shell and dmesg
worked, but how can I supply a copy of it here without net connection
and without OS login capabilities?
FYI, trying to h
On Sun, Mar 27, 2011 at 04:21:32PM -0700, Sha'ul wrote:
> >Dude,
> >
> >You need to give more info. How about the dmesg from the bsd.rd?
> >
> >Luis.
>
> At the boot> prompt I put bsd.rd and it probes and gives me the
> install options (I)nstall (U)pgrade (S)hell, I went to shell and
> dmesg worke
Dude,
You need to give more info. How about the dmesg from the bsd.rd?
Luis.
At the boot> prompt I put bsd.rd and it probes and gives me the install
options (I)nstall (U)pgrade (S)hell, I went to shell and dmesg worked,
but how can I supply a copy of it here without net connection and
witho
What exactly is the message during kernel panic? Are you able to use
keyboard to enter a few commands? If so you can check out
http://www.openbsd.org/faq/faq2.html#Bugs
See if this can also help
http://www.openbsd.org/faq/faq5.html#BootConfig
On Sun, Mar 27, 2011 at 4:11 PM, Sha'ul wrote
I was able to install 4.9-current with no problem, I typed reboot at the
command prompt after completion, the boot> prompt comes up and the
starts the usual probe and I get a kernal panic. So how do I report a
system bug if I've never been able to login? This is on a new laptop.
doing this, and got a
kernel panic ;-/
Steps to reproduce:
boot, provision network, and firewall config - bring up some services,
send some traffic, wait a few days for message to appear, run sendbug.
Crash.
2 Outcomes: Kernel panic/crash , or no network on interface (reboot
solves problem
Hi List,
on i386-current:
OpenBSD 4.8-current (GENERIC.MP) #18: Fri Jan 7 15:22:29 WIT 2011
r...@greenservicerouter-2g.mygreenlinks.net:/usr/src/sys/arch/i386/compile/GENERIC.MP
RTC BIOS diagnostic error e
cpu0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz ("GenuineIntel" 686-class) 2.41
GHz
cpu
Could this be indicative of something with my problem?
I can't seem to list a "re" interface with ifconfig.
# uptime
8:51PM up 1 day, 8:09, 1 user, load averages: 0.12, 0.09, 0.08
# ifconfig
lo0: flags=8049 mtu 33200
priority: 0
groups: lo
inet 127.0.0.1 netmask 0xff000
On Sun, 3 Oct 2010 22:24:18 +0200, you wrote:
>well, it is easy enough to verify - use something else but re. if it's
>stable, we have the guilty party, at least.
Yea, I'm sort of stuck with re. Here's a few quick images of these boxes. It's
a
Jetway NF76 board with a daughter card with 3 RTL8110
On Sun, 3 Oct 2010 22:41:50 +0200, you wrote:
>err... reading the trace first helps. this is actually pretty clearly a
>problem in re. I don't feel responsible for re tho :)
Is there something else I should do before submitting something to bugs?
Both of these source files haven't been modified
* Henning Brauer [2010-10-03 22:28]:
> * Steve W [2010-10-03 22:16]:
> > On Wed, 29 Sep 2010 11:57:10 +0200, you wrote:
> > >sigh. use-after-free (most likely, at least) somewhere. unlikely to be
> > >carp itself. might be re (wild guess).
> >
> > I think your "somewhere near re" theory might ha
* Steve W [2010-10-03 22:16]:
> On Wed, 29 Sep 2010 11:57:10 +0200, you wrote:
> >sigh. use-after-free (most likely, at least) somewhere. unlikely to be
> >carp itself. might be re (wild guess).
>
> I think your "somewhere near re" theory might have some merrit to it. :)
well, it is easy enough
On Wed, 29 Sep 2010 11:57:10 +0200, you wrote:
>sigh. use-after-free (most likely, at least) somewhere. unlikely to be
>carp itself. might be re (wild guess).
I think your "somewhere near re" theory might have some merrit to it. :)
I've had a number of crashes over the past couple days, but this
* Steve W [2010-09-26 18:46]:
> login: panic: pool_do_get(mcl2k): free list modified: page 0xd68bc000;; item
> addr 0xd68bc800; offset 0x0=0x2d304436
sigh. use-after-free (most likely, at least) somewhere. unlikely to be
carp itself. might be re (wild guess).
--
Henning Brauer, h...@bsws.de, he
* Stefan Unterweger on Tue, May 04, 2010 at 12:43:22AM +0200:
> However, if I do `shutdown -h -p` (thus power off), I get a
> kernel panic; specifically, "AML PARSE ERROR" (see below). This
> only happens when doing '-p' is involved somehow; rebooting
> works, and
* Mike Larkin on Wed, May 05, 2010 at 09:04:06PM -0700:
> If you haven't sent an acpidump yet, send it over.
/*
RSD PTR: Checksum=20, OEMID=PTLTD, RsdtAddress=0x3fefcf28
*/
/*
RSDT: Length=44, Revision=1, Checksum=13,
OEMID=PTLTD, OEM Table ID= RSDT, OEM Revision=0x604,
Creat
* Jan Stary on Tue, May 04, 2010 at 08:31:10AM +0200:
> > I've done some research, and it turns out that the motherboard
> > seems to a particularly buggy ACPI tables. And just as well, if I
> > disable ACPI, the kernel panic vanishes. However, the machine
> > doesn
* Aaron Mason on Tue, May 04, 2010 at 08:48:05PM +1000:
> When you get it out again, we'll also need to see an acpidump output.
Here is the output of both acpidump(8) and dmesg(8).
s//un
-8<-8<-8<-8<-8<-8<-8<-8<-
/*
RSD PTR: Checksum=20, OEMID=PTLTD, RsdtAdd
y just work).
>
> However, if I do `shutdown -h -p` (thus power off), I get a
> kernel panic; specifically, "AML PARSE ERROR" (see below). This
> only happens when doing '-p' is involved somehow; rebooting
> works, and just '-h' without '-p' doe
everything works fine, to some extent much smoother
than on Linux (especially getting the sensors to work back then
was a true nightmare, and I eventually gave up in defeat -- on
OpenBSD, they just work).
However, if I do `shutdown -h -p` (thus power off), I get a
kernel panic; specifically, "
[mailto:l...@animata.net]
Sent: Wednesday, November 18, 2009 01:04
To: Anders Pettersson
Cc: misc@openbsd.org
Subject: Re: OpenBSD 4.6 pfsync kernel panic
hi anders,
could you get me a full trace from ddb when the fault occurs? id also like the
output of 'cvs info if_pfsync.?' in src/sys/net i
en we reboot either one of our two OpenBSD 4.6
servers
> running pf. It seems that the kernel panic always happens at the point
where
> the pf sync state import happens. Sometimes we can reboot the servers, one
at
> the time, a number of times in a row without any problems. We have tr
Hi
We get kernel panics when we reboot either one of our two OpenBSD 4.6 servers
running pf. It seems that the kernel panic always happens at the point where
the pf sync state import happens. Sometimes we can reboot the servers, one at
the time, a number of times in a row without any problems
Hi
We get kernel panics when we reboot either one of our two OpenBSD 4.6 servers
running pf. It seems that the kernel panic always happens at the point where
the pf sync state import happens. Sometimes we can reboot the servers, one at
the time, a number of times in a row without any problems. We
seem very problematic. I know of people that have
> > abandoned it altogether.
> >
> > On Mon, Nov 16, 2009 at 08:31:59PM +0800, David S. wrote:
> >> Hello there,
> >>
> >> unfortunately my newly acquired Lenovo Desktop, Model Number A5790R
> >> will
d Lenovo Desktop, Model Number A5790R
>> will Kernel Panic before during boot. The install of i386 4.6 itself
>> goes fine. I tried to boot with acpi disabled, to no avail. Also i
>> played around with various settings in the BIOS pertaining to certain
>> CPU Features and S-A
These desktops seem very problematic. I know of people that have
abandoned it altogether.
On Mon, Nov 16, 2009 at 08:31:59PM +0800, David S. wrote:
> Hello there,
>
> unfortunately my newly acquired Lenovo Desktop, Model Number A5790R
> will Kernel Panic before during boot. The ins
301 - 400 of 562 matches
Mail list logo
