On 20/11/16(Sun) 13:58, Frank Groeneveld wrote:
> A few week back there was an outage at my ISP. Afterwards, I kept
> getting crashed on igmpproxy after changing channels on the tv a few
> times:
This has been fixed in -current.
On Sun, Nov 20, 2016 at 03:21:32PM +0100, Martin Pieuchot wrote:
> On 20/11/16(Sun) 13:58, Frank Groeneveld wrote:
> > A few week back there was an outage at my ISP. Afterwards, I kept
> > getting crashed on igmpproxy after changing channels on the tv a few
> > times:
>
> This has been fixed in -c
On 20/11/16(Sun) 18:34, Frank Groeneveld wrote:
> On Sun, Nov 20, 2016 at 03:21:32PM +0100, Martin Pieuchot wrote:
> > On 20/11/16(Sun) 13:58, Frank Groeneveld wrote:
> > > A few week back there was an outage at my ISP. Afterwards, I kept
> > > getting crashed on igmpproxy after changing channels o
On 29.1.2017. 4:13, kayasaman wrote:
> Hi,
> A very strange issue...
> After the previous update of CURRENT I started to have issues with ftpproxy
> not loading some directories, an example being shrubbery.net rancid directory.
> Today I attempted an upgrade to see if that might kick things into g
Hi,
I have "managed" go get a kernel panic in OpenBSD 6.0 -stable (from
GENERIC.MP). Unfortunately I cannot provide you with lots of information, but
here is what I have:
The panic occured twice on an IBM X3550 server (CPU: Intel(R) Xeon(R) CPU
E5-2603 0 @ 1.80GHz, with 4GB RAM and
Hello,
1) If I run transmission-gtk with ex.: 20 torrent files and I'm on a
50 mbit/sec network, after ~10-15 minutes (network fully used,
ethernet, not wifi) my OpenBSD 5.6 64bit on a T61 will always crash
and brings up the gdb. Is that normal? How can I help debug it? I'm
not running it as root,
I got the following kernel panic:
panic: kernel diagnostic assertion "sotoinpcb(inp->inp_socket) == inp"
failed: file "../../../../netinet/tcp_input.c", line 640
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT
On Mon, 14 Apr 2008 08:57:55 -0700, Dag Richards wrote
> Then I performed a boot dump, I have
> drwxrwx--- 2 root wheel 512 Apr 14 07:53 ./
> drwxr-xr-x 25 root wheel 512 Aug 28 2007 ../
> -rw--- 1 root wheel 2 Apr 14 07:51 bounds
> -rw--- 1 root w
Josh Grosse wrote:
On Mon, 14 Apr 2008 08:57:55 -0700, Dag Richards wrote
Then I performed a boot dump, I have
drwxrwx--- 2 root wheel 512 Apr 14 07:53 ./
drwxr-xr-x 25 root wheel 512 Aug 28 2007 ../
-rw--- 1 root wheel 2 Apr 14 07:51 bounds
-rw---
to go terribly wrong, I can even scan
with `ifconfig -M uath0`. However, it cannot associate with any access
points. And if I have the device in at startup I get a pretty nasty
kernel panic. It is also worth noting that I am not actually detaching
the device when those events come up in the dmesg.
It
Hi,
I got a "bad ref count" panic message while trying to access a directory
on a 45 GB ext3 partition. Below is what I managed to salvage. Any
workarounds for this? Anyway, got GNOME on OpenBSD up and running, made
very easy, great!
Bill
-
x1948
pf_test_rule() at pf_test_rule+0x4d8
pf_test() at pf_test+0x944
ipv4_input() at ipv4_input+0x153
ipintr() at ipintr+0x6d
Xsoftnet() at Xsoftnet+0x4a
interrupt ---
end trace frame" 0x0, count: -10
0:
ddb{0}>
and this is the kernel panic before I update:
uvm_fault(0x 8
Yes I know its experimental... ;-)
I bought a ASUS WL-130N, installed the latest snapshot (from July 2nd)
and tried WPA
I build the pre-shared key
# wpa-psk ZELDA start123
0x763b94d25e9800f80f926fcc26d7fdf52b3b565209456bd0aa31973fbd8d5ce2
and put it in my /etc/hostname.ral0
# cat /etc/hostname
Hi again,
Michael schrieb:
I just had my v440 crash on me with a weird message (at the end of the
dmesg). Any ideas why that happened?
Noone? Wrong list? Would tech@ or sparc@ be better?
console is /[EMAIL PROTECTED],60/[EMAIL PROTECTED]/[EMAIL PROTECTED],3f8
Copyright (c) 1982, 1986,
SMP related inter-process-interrupts, likely your ATI Rage XL is causing the
problem,
but this is a very wilde guess, perhaps try to replace ands see if happens
again?
I've got a V440 running, however it headless.
ioan
>>> Michael <[EMAIL PROTECTED]> 30/07/2008 12:24:46 >>>
Hi all,
I just ha
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
[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
Hi List,
i am seeing kernel panics on a Lenovo L420 on 5.2 and -current from
28th, December. The machine freezes right at boot time, when acpi gets
loaded. Disabling acpi in UKC lets the system start. I photographed the
ddb, a trace, a ps and produced an acpidump and tarred it together with
a dmes
Hi,
I have a pair of OpenBSD 5.2 VMs running on KVM, they have a carp interface
and are running relayd to load balancer http traffic into two webservers
(also VMs). While benchmarking the setup with ab, I noticed that the
OpenBSD VMs panic'd, I can easily reproduce the panics. Here is a typical
st
Hi,
I had a kernel panic after upgrade to latest snapshot.
`trace` and `ps` follows, dmesg at bottom
OpenBSD/i386 (ns.bsdbg.net) (tty00)
login:pool_do_get: pfstatekeypl: curpage NULL, nitems 1
panic: pool_do_get: nitems inconsistent
Stopped at Debugger+0x4: popl%ebp
RUN AT LEAST
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
;>>> 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'
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
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
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
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, "
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
I got another kernel panic: free: non-malloced addr 0x10 type temp
Many programs seg fault with "Program terminated with signal 11,
Segmentation fault"
The memory has been tested with memtest86.
Any idees?
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[E
On 2006/05/30 20:39, Jerome Loyet wrote:
> I got another kernel panic: free: non-malloced addr 0x10 type temp
>
> Many programs seg fault with "Program terminated with signal 11,
> Segmentation fault"
>
> The memory has been tested with memtest86.
>
> Any id
From: [EMAIL PROTECTED]
> I got another kernel panic: free: non-malloced addr 0x10 type temp
>
> Many programs seg fault with "Program terminated with signal 11,
> Segmentation fault"
>
> The memory has been tested with memtest86.
>
> Any idees?
I've
?
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> De la part de Spruell, Darren-Perot
> Envoyi : mardi 30 mai 2006 23:06
> @ : misc@openbsd.org
> Objet : Re: Kernel panic "smashed stack in ufs_makeinode"
>
> From: [EMAIL PR
On 2006/05/30 23:28, Jirtme Loyet wrote:
> In fact this is not just a problem with my machine.
> I bought a dedicated server (www.dedibox.fr). I installed OpenBSD 3.9 on it.
> Other people did exactly the same and the have the same problem.
That means it's less likely to be a failure particular to
both crashed.
- Now we are just running the BACKUP (we didn't hookup MASTER to the
network again because these are production FWs)
Below the pictures of the traceback of the kernel panic:
http://img61.imageshack.us/img61/1840/photo0615060079iq.jpg
http://img83.imageshack.us/img83/9694/photo061506
I have seen no feedback on this kernel panic.
I'd like to know if this could be a kernel bug or it may be caused by
some hardware problem.
Thanks.
Original Message
Subject: Kernel Panic with 3.9-stable MP
Date: Tue, 04 Jul 2006 19:37:32 +0200
From: Federico Gia
Hello all,
We also faced similar problem several times after upgrading to 3.9.
What could be the problem?
regards
murthy
Federico Giannici wrote:
> It happened again: one of our servers with OpenBSD i386 3.9-current MP
> of a couple days ago crashed with the following kernel error:
>
I had almost the same problem here too.
Box is dell 1850 with MP-board, 1 CPU inside, running GENERIC.MP.
It stopped to accept any connections, but:
1. responded to ping very quickly
2. syn-scan gave out that ports were open (those which should be open)
4. no heavy traffic incoming
3. no dumps on c
Probably you already know it: the i386 snapshot of Jul 4 (both MP and
SP) made our system to freeze (usually after a few hours, sometime after
a few minutes) and a couple of time made the system crash with a page fault.
We downgraded to 3.9 and the problems disappeared.
Bye.
Federico Gianni
On 2006/07/12 11:59, Federico Giannici wrote:
> Probably you already know it: the i386 snapshot of Jul 4 (both MP and
> SP) made our system to freeze (usually after a few hours, sometime after
> a few minutes) and a couple of time made the system crash with a page fault.
>
> We downgraded to 3.9
Stuart Henderson wrote:
On 2006/07/12 11:59, Federico Giannici wrote:
Probably you already know it: the i386 snapshot of Jul 4 (both MP and
SP) made our system to freeze (usually after a few hours, sometime after
a few minutes) and a couple of time made the system crash with a page fault.
We
On 2006/07/13 10:09, Federico Giannici wrote:
> >When I had a bad cpu in May I hardly saw the problem with April 24
> >kernel (still available in snapshots/i386/non-pae) - I had to run
> >`stress' and `make build' together and wait a while to see it,
> >whereas the May 7 snapshot failed very quickl
Stuart Henderson wrote:
On 2006/07/13 10:09, Federico Giannici wrote:
When I had a bad cpu in May I hardly saw the problem with April 24
kernel (still available in snapshots/i386/non-pae) - I had to run
`stress' and `make build' together and wait a while to see it,
whereas the May 7 snapshot fai
On 2023-03-05, mabi wrote:
> Hello
>
> Is it possible to have OpenBSD 7.2 automatically reboot after a kernel panic
> happens?
>
> I tried setting:
>
> ddb.panic=0
>
> but it does not reboot automatically.
>
> As I am affected by the pfsync issue which leads
Ok, after further investigations, my problem does not seems to be linked
with inteldrm. The kernel panic seems to happen randomly with or without
inteldrm enabled.
Nevertheless, if I disable inteldrm, I can access ddb when the panic
happen (I don't know why, BTW) and I get this.
k
Le 07/09/2017 à 05:59, Maxim Bourmistrov a écrit :
Hey,
Got kernel panic on 6.1-stable during ’rcctl restart relayd’.
Sorry for PNG below.
Hi,
It has been fixed with this diff :
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/pf.c.diff?r1=1.1034&r2=1.1035
reproduce the problem to
find out what it is related to and managed to even make both firewalls kernel
panic at the same time. When this happens the hardware is frozen and won't take
any input and won't even reboot automatically. I need to power it off and on
again.
As I was logged into
The crash I reported a few days ago is the same:
ehci_device_clear_toggle: queue active
On 30/11/15(Mon) 18:28, Björn Ketelaars wrote:
> Hello,
>
> I repeatedly hit the kernel panic below. Easy to reproduce as it happens over
> and over again within 60 minutes after rebooting. Root cause is not known.
>
> I'm running snapshot on an USB stick. I tried diffe
On Thu 03/12/2015 09:54, Martin Pieuchot wrote:
> On 30/11/15(Mon) 18:28, Björn Ketelaars wrote:
> > Hello,
> >
> > I repeatedly hit the kernel panic below. Easy to reproduce as it happens
> > over
> > and over again within 60 minutes after rebooting. Root
Hello,
I had a kernel panic while reproducing a video with mpv.
It's my first kernel panic with OpenBSD, so I didn't know how to use
ddb(4). Since I'm running my http and smtp server in this machine I
cannot entertain myself too much reproducing the panic to get more info.
Tha
On 27/02/17(Mon) 19:36, Infoomatic wrote:
> Hi,
>
> I have "managed" go get a kernel panic in OpenBSD 6.0 -stable (from
> GENERIC.MP). Unfortunately I cannot provide you with lots of information, but
> here is what I have:
>
> The panic occured twice on an IBM X
> At least two bugs leading to this panic have been fixed post 6.0. I'd
> suggest you to upgrade to -current where it should work as expected. If
> not, please send a new bug report to bugs@.
Thanks a lot! This is awesome, you manage to fix bugs faster than I can report
them ;-)
I guess I won't
On 2015-03-03 11:37, someone wrote:
1) If I run transmission-gtk with ex.: 20 torrent files and I'm on a
50 mbit/sec network, after ~10-15 minutes (network fully used,
ethernet, not wifi) my OpenBSD 5.6 64bit on a T61 will always crash
and brings up the gdb. Is that normal?
Do you mean *ddb*,
Only running -release without patches. Ok, then I will try out newer
versions before reporting anything, thanks!
On Tue, Mar 3, 2015 at 5:56 PM, Josh Grosse wrote:
> On 2015-03-03 11:37, someone wrote:
>
> 1) If I run transmission-gtk with ex.: 20 torrent files and I'm on a
>> 50 mbit/sec netwo
Hi Misc@,
on a i386 kernel recent build (6th march), I got panic. It says:
uvm_fault(0xd08079c0, 0x0, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at pf_icmp_mapping+0x45: movw 0x4(%eax),%ax
ddb> trace
pf_icmp_mapping(dc2c5ba0,8,dc2c5b34,dc2c5b38,dc2c5b3c,dc2c5b3e,2) at
pf_icmp_mapping+0x4
Hi Misc@,
I currently caught a kernel panic that says:
uvm_fault(0x 80b7b0e0, 0x0, 0, 1) -> e
kernel : page fault trap, code=0
Stopped at pf_state_tree_RB_REMOVE_COLOR + 0x1C0: cmpl $0x1,0x40(%rsi)
ddb {0}> trace
pf_state_tree_RB_REMOVE_COLOR() at pf_state_tree_RB_REMOVE_COLOR
On Wed, 25 Jun 2008 20:47:50 +0700, Insan Praja SW <[EMAIL PROTECTED]>
wrote:
Sorry, the title should be "25 June AMD64 Snapshots Kernel Panic"
Thanks,
Insan
Hi Misc@,
This is a recent panic I got on "OpenBSD 4.3-current (GENERIC.MP) #8:
Wed Jun 25 09:55:34 WIT 2008&quo
giovanni schrieb:
well, I'm not alone
same behaviour as stated in:
http://marc.info/?l=openbsd-misc&m=121396323512149&w=2
moreover if I do not use any wpa it does not panic. did you try this?
Hi Giovanni,
no, I did not really tested it, I only tried out wpa and saw that it
worked with wpa
On Tue, 08 Jul 2008 21:59:43 +0700, David Krause <[EMAIL PROTECTED]>
wrote:
Hi Misc@,
Currently I am on AMD64 4.4-beta, and yes.. I got the latest source from
July 7, and yes, it is been a stable machine for about a day, no complains
or anything.
Thanks all,
Insan
* Insan Praja SW <[EMA
e command
`boot dump` would be nice.
the problem is solved for me, but i want to let you know. hope you guys can
do something with the infos i provide.
thanks for your great work,
sebastian.
>Synopsis: i got a kernel panic each time i run /etc/daily and have my ntfs
>parition mounted.
>C
name.on.internet 110" this on a workstation, i have a kernel panic
on my OpenBSD gateway :
uvm_fault(0xd0a51660,0x0, 0, 1) -> e
Kernel: page fault trap, code=0
Stopped at pf_purge_rule +0x11: mov 0x10(%ebx),%eax
my pf.conf :
ports_tcp="{80 25 443 587 995 21}"
set sk
Building a 5.3-beta template now, will let you know.
On 22 February 2013 15:26, Chris Cappuccio wrote:
> before you go much further, try openbsd 5.3-beta first
>
> ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/
>
> Peter Farmer [pfarmer...@gmail.com] wrote:
> > Hi,
> >
> > I have a pair of
Unfortunately now getting "em0: watchdog timeout -- resetting" on my VMs
(on 5.3-beta) , which also locks the terminal for me, so can't bring the
network up :(
On 22 February 2013 15:49, Peter Farmer wrote:
> Building a 5.3-beta template now, will let you know.
>
>
> On 22 February 2013 15:
That's a little tricky from a VNC console, so this is the best I can do:
http://habanero.projectchilli.com/~pfarmer/screens/
On 22 February 2013 17:26, Chris Cappuccio wrote:
> dmesg?
>
> Peter Farmer [pfarmer...@gmail.com] wrote:
> > Unfortunately now getting "em0: watchdog timeout -- resett
On 2013-02-22, Peter Farmer wrote:
> Unfortunately now getting "em0: watchdog timeout -- resetting" on my VMs
> (on 5.3-beta) , which also locks the terminal for me, so can't bring the
> network up :(
with -current you might want to try switching the network interface type
to virtio, using th
On Friday, February 22, 2013, Stuart Henderson wrote:
> On 2013-02-22, Peter Farmer > wrote:
> > Unfortunately now getting "em0: watchdog timeout -- resetting" on my VMs
> > (on 5.3-beta) , which also locks the terminal for me, so can't bring the
> > network up :(
>
> with -current you might w
On Wed, May 15, 2013 at 22:31, ?? ?? wrote:
> Hi,
> I had a kernel panic after upgrade to latest snapshot.
> `trace` and `ps` follows, dmesg at bottom
>
> OpenBSD/i386 (ns.bsdbg.net) (tty00)
>
> login:pool_do_get: pfstatekeypl: curpage NULL, nitems 1
There w
2013/5/15 Ted Unangst
> On Wed, May 15, 2013 at 22:31, ?? ?? wrote:
> > Hi,
> > I had a kernel panic after upgrade to latest snapshot.
> > `trace` and `ps` follows, dmesg at bottom
> >
> > OpenBSD/i386 (ns.bsdbg.net) (tty00)
> >
> >
?? ?? [don.na...@gmail.com] wrote:
>
> May I try to build and install a new kernel with that fix, or to wait for a
> new snapshot?
> Thank you.
>
That depends on your preference.
Hi,
I built a kernel that include the fix in pf.c and everything is fine now.
Thanks,
Atanas Vladimirov
[ns]~$ uptime
5:37PM up 3 days, 3:44, 1 user, load averages: 1.23, 0.74, 0.64
[ns]~$ dmesg
OpenBSD 5.3-current (GENERIC) #0: Wed May 15 23:59:01 EEST 2013
vl...@ns.bsdbg.net:/usr/src/sy
After successfully setting up an L2TP VPN with npppd and pppx, I tried
to add a second VPN subnet with a different authentication base. I was
working remotely, and after starting npppd in debug mode:
bash-4.2# npppd -d
2014-03-19 14:41:50:NOTICE: Starting npppd pid=32407 version=5.0.0
2014-03-19 1
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 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-
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
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
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
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, 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 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, 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 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
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 -
> "
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
* 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 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
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
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
> ...
>
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
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
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 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
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 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
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
> 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 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
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 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
* 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
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
OK I have another one:
kernel: type 269 trap, code=0
Stopped at 0: pushq %rbx
ddb> trace
end trace frame: 0x0, count: -1
This one is less verbose though...
g Andre
201 - 300 of 562 matches
Mail list logo
