On Sun, May 25, 2025, 06:40 Zbigniew Kossowski wrote:
> I have provided manual upgrade in a remote machine as in
> https://www.openbsd.org/faq/upgrade77.html
>
> I did it for several times before. After the first reboot I have got a
> kernel panic on bsd(.mp) and bsd(.sp). Older kernel (o)bsd 7.6
On Fri, Feb 28, 2025 at 01:22:20AM +, TSS wrote:
> Greetings from a noob,
>
> With my OpenBSD beginner's luck I am able to dependably panic my 7.6
> install if I enable a moderately elaborate tunnelling situation. I would
> love to follow the instructions at https://www.openbsd.org/ddb.html to
The issue is fixed now ..yay !
Thank you Jonathan for your super quick resolution of the bug.
regards
On Mon, Feb 24, 2025 at 3:07 AM Jonathan Gray wrote:
> On Sun, Feb 23, 2025 at 11:40:17AM +1100, Jonathan Gray wrote:
> > The patch to intel_dp_mst.c has not been committed.
>
> committed, will
On Sun, Feb 23, 2025 at 11:40:17AM +1100, Jonathan Gray wrote:
> The patch to intel_dp_mst.c has not been committed.
committed, will be in future snapshots
The patch to intel_dp_mst.c has not been committed.
You need to add the 'intel_connector->base.dev = mgr->dev;' line.
On Sat, Feb 22, 2025 at 11:21:29AM -0500, Johnny Epsom wrote:
> Thank you Jonathan for the detailed instructions to get src.
> I saw the patch was already in file intel_dp.c -- so
See https://www.openbsd.org/anoncvs.html
for example:
cd /usr
cvs -qd anon...@anoncvs4.usa.openbsd.org:/cvs co -P src/sys
then
cd /sys/arch/amd64/compile/GENERIC.MP/
make obj && make config && make
doas make install
On Fri, Feb 21, 2025 at 01:19:02PM -0500, Johnny Epsom wrote:
> My rookie mistak
My rookie mistake, doing this for the first time -- I did not have sys on
my machine and ftped it using uname -r and got the stable version.
I will figure the way for getting the -current snapshot version and then
apply the changes suggested and test.
regards
On Fri, Feb 21, 2025 at 8:39 AM Johnn
On Wed, Feb 19, 2025 at 07:53:15PM -0500, Johnny Epsom wrote:
> Hi Team
>
> I am running current 7.6 on a Thinkpad T14 (Gen1 - Intel) and when I
> connect the laptop to my Dell USB-C dock, I am getting a crash. The system
> drop into ddb and I need to restart the machine.
>
> The issue seems to h
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.
kernel: doub
Hi Visa,
On Sun, Jun 24, 2018 at 05:54:15PM +, Visa Hankala wrote:
> On Sun, Jun 24, 2018 at 12:37:45PM +0200, Walter Alejandro Iglesias wrote:
> > panic: mtx 0x81c86470: locking against myself
> > Stopped at db_enter+0x12: popq%r11
> > TIDPIDUID PRFLAGS P
On Sun, Jun 24, 2018 at 12:37:45PM +0200, Walter Alejandro Iglesias wrote:
> panic: mtx 0x81c86470: locking against myself
> Stopped at db_enter+0x12: popq%r11
> TIDPIDUID PRFLAGS PFLAGS CPU COMMAND
> 104021 96401 1000 0x3 0x4002 mpv
> *
Hardware was bad, now it's ok.
W dniu 17.02.2018 o 08:23, Krzysztof Strzeszewski pisze:
> Hi,
>
> I have kernel panic in OpenBSD 6.1 end 6.2 on the same machine. Command
> "cmp" is in my script , it starts every minute. When I don't use "cmp"
> command with my script, is ok. This kernel panic is
Hello lads,
I have about 15 OpenBSD 6.x servers 4x 6.2 servers on
Vmware and vmxnet net drivers,
Im running on Vmware 6.0 Update 2
( the earlier vmware 6.0 with out updates was very problmeatic)
I dont do much on Snapshots,
but I use a LSI Logic Paralell Storage Driver (SCSI)
and vmxnet3
I havent
esxi 5.5.0 dates back to 2013.
obsd runs better on qemu nowadays.
To avoid the mess with x86/amd64,
perhaps qemu-sparc with obsd-sparc
will serve you better.
Sent from ProtonMail Mobile
On Fri, Jan 19, 2018 at 21:50, Mik J wrote:
> Hello, I had many kernel panic these past days. This is a 6.2 o
On Thu, January 25, 2018 4:29 am, Maxim Bourmistrov wrote:
> As Stuart mentioned, em(4) on top of e1000 proven to be more stable.
> Even under higher load.
> Vmx starting to misbehave under high load, resulting for ex. with unstable
> CARP setup.
>
> //mxb
>
>> 25 jan. 2018 kl. 02:40 skrev trondd :
As Stuart mentioned, em(4) on top of e1000 proven to be more stable.
Even under higher load.
Vmx starting to misbehave under high load, resulting for ex. with unstable CARP
setup.
//mxb
> 25 jan. 2018 kl. 02:40 skrev trondd :
>
> On Mon, January 22, 2018 10:47 am, Mik J wrote:
>> Hello Stuart,
On Mon, January 22, 2018 10:47 am, Mik J wrote:
> Hello Stuart,
> For me it takes just a few days...
> I have a crash every 3/4 days maybe (2 crashes so far) and my server does
> not handle load.
> Yes I read your reports this morning, although you wrote that there was a
> combination with snmpd, I
On 2018-01-24, who one wrote:
> Could it be related to:
> https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/
No.
> ?
>
>> Sent: Friday, January 19, 2018 at 9:50 PM
>> From: "Mik J"
>> To: Misc
>> Subject: Kernel panic with openb
Could it be related to:
https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/
?
> Sent: Friday, January 19, 2018 at 9:50 PM
> From: "Mik J"
> To: Misc
> Subject: Kernel panic with openbsd 6.2
>
> Hello,
>
> I had many kernel panic t
Hello Stuart,
For me it takes just a few days...
I have a crash every 3/4 days maybe (2 crashes so far) and my server does not
handle load.
Yes I read your reports this morning, although you wrote that there was a
combination with snmpd, I have it with nginx on my side.
Regards
Le lundi 22
On 2018/01/22 00:22, Mik J wrote:
> Le dimanche 21 janvier 2018 à 11:48:00 UTC+1, Stuart Henderson
> a écrit :
> On 2018-01-19, Mik J wrote:
> > I had many kernel panic these past days. This is a 6.2 openbsd VM running o=
> > n esxi 5.5
> >
> > # grep "" /tmp/if_vmx.dis
>
> I've reported a lot
Hello Stuart,Thank you for your answer.I had my VM running for months in
version 6.1 and had not problem but I reinstalled it in version 6.2 and the
problem is happening.It seems to me that something in version 6.2 is producing
the error.One crash today again
Le dimanche 21 janvier 2018 à
On 2018-01-19, Mik J wrote:
> I had many kernel panic these past days. This is a 6.2 openbsd VM running o=
> n esxi 5.5
>
> # grep "" /tmp/if_vmx.dis
I've reported a lot of vmxnet3_getbuf panics, nobody seems interested.
I suggest switching to e1000 in the vmx file, this works with the em(4)
driv
On Sat, Oct 14, 2017 at 6:57 AM, Krzysztof Strzeszewski
wrote:
> This is very interested "the kernel did non panic".
panic() is an explicit call in the kernel, made when some sanity or
consistency check fails. Dereferencing a bogus pointer results in a failed
page fault trap and goes to ddb di
This is very interested "the kernel did non panic". Where is memcmp in
sys? When I run bsd.rd end mount filesystem I can't find memcmp.
http://wklej.org/hash/e5591ccc88f/
.
.
.
cpu0 at mainbus0: (uniprocessor)
mtrr: Pentium Pro MTRR support, 8 va
On Fri, Oct 13, 2017 at 12:21 PM, Krzysztof Strzeszewski
wrote:
> When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic.
>
It's unfortunate that no one has submitted to dm...@openbsd.org the dmesg
from that hardware since February 2016. Please consider doing so every
time you upgrade y
I changed only name kernel :)
W dniu 14.10.2017 o 01:13, Mike Larkin pisze:
On Fri, Oct 13, 2017 at 09:21:37PM +0200, Krzysztof Strzeszewski wrote:
Hi,
When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic.
Try 6.1 stock kernel and see if that works. Then at least we know if we
intr
On Fri, Oct 13, 2017 at 09:21:37PM +0200, Krzysztof Strzeszewski wrote:
> Hi,
> When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic.
>
Try 6.1 stock kernel and see if that works. Then at least we know if we
introduced a regression.
Nobody knows (or cares) what NROOT is.
-ml
> --
On Tue, May 02, 2017 at 05:03:20PM +, Stuart Henderson wrote:
> Probably the best thing to do at this point is to write a mail to bugs@:
>
> 1. describe what the machine is doing in detail. carp? ipsec? pfsync?
> what sort of relays? include config (sanitized if necessary, but do that
> consis
On 2017-05-02, Mathieu BLANC wrote:
> On Wed, Mar 29, 2017 at 02:06:23PM +0200, Mathieu BLANC wrote:
>> It also kernel panics with just this pf rules :
>> # cat pf_minimal.conf
>> set limit { states 10 }
>> set skip on lo
>> anchor "relayd/*"
On Tue, May 02, 2017 at 03:44:43PM +0200, Andre Ruppert wrote:
> Hi,
>
> Im running 6.0 amd64 on a pair of R210 with relayd, but these are R210 (II).
>
> No kernel panics at all, and these systems are working in a live
> environment...
>
> Regards
> Andre
Hi,
Yes, i have also several OpenBSD o
Hi,
Im running 6.0 amd64 on a pair of R210 with relayd, but these are R210 (II).
No kernel panics at all, and these systems are working in a live
environment...
Regards
Andre
Am 02.05.17 um 15:03 schrieb Mathieu BLANC:
On Wed, Mar 29, 2017 at 02:06:23PM +0200, Mathieu BLANC wrote:
It als
On Wed, Mar 29, 2017 at 02:06:23PM +0200, Mathieu BLANC wrote:
> It also kernel panics with just this pf rules :
> # cat pf_minimal.conf
> set limit { states 10 }
> set skip on lo
> anchor "relayd/*"
> pass
>
On 04/04/17 20:40, Stuart Henderson wrote:
>>> I have a case of OpenBSD-5.9 (i386) kernel panic.
> Upgrade.
I suspect that this kernel panic could be caused by hardware problems so
upgrade will not be a cure.
I sent the problem report to b...@openbsd.org
(http://marc.info/?l=openbsd-bugs&m=1491309
It looks more like a bug than a hw fault. Upgrading (preferably to a
-current snapshot) means we will know whether the problem still exists or
whether it has been fixed already and gives an easier base for anyone
trying to track it down if it's still there.
--
Sent from a phone, apologies for
>> I have a case of OpenBSD-5.9 (i386) kernel panic.
Upgrade.
On 2017-04-02, Niko Pavlinek wrote:
> On 2. 04. 2017 14:08, Stuart Henderson wrote:
>>
>> Please try a -current snapshot and report back. If you get it now (before
>> the kernel version moves to 6.1-current) you'll be able to safely update
>> to the proper 6.1 release when it's out.
>>
>> ACPI is
Is it a soekris? If so http://wiki.soekris.info/Installing_OpenBSD.
If not https://www.openbsd.org/report.html
Sent from my iPhone
> On Apr 3, 2017, at 8:34 AM, Alexei Malinin wrote:
>
> Hello.
>
> I have a case of OpenBSD-5.9 (i386) kernel panic. I'd like to be pointed
> out to possible caus
On 2. 04. 2017 14:08, Stuart Henderson wrote:
>
> Please try a -current snapshot and report back. If you get it now (before
> the kernel version moves to 6.1-current) you'll be able to safely update
> to the proper 6.1 release when it's out.
>
> ACPI is really required for modern PC hardware, it is
On 2017-03-31, Niko Pavlinek wrote:
> Hello,
>
> I am new to OpenBSD and am trying to install OpenBSD on my Dell laptop,
> specifically Dell Inspiron 15-5558. When I boot the installation, the
> kernel panics with pci_make_tag: bad request. I am able to install if I
> disable acpi during boot tho
On Wed, Mar 29, 2017 at 10:40:08AM +0200, Mathieu BLANC wrote:
> On Tue, Mar 28, 2017 at 05:58:02PM +0200, Hiltjo Posthuma wrote:
> > On Tue, Mar 28, 2017 at 02:39:44PM +0200, Mathieu BLANC wrote:
> > > On Tue, Mar 28, 2017 at 02:22:28PM +0200, Mathieu BLANC wrote:
> > > > I can reproduce the bug (
On Tue, Mar 28, 2017 at 05:58:02PM +0200, Hiltjo Posthuma wrote:
> On Tue, Mar 28, 2017 at 02:39:44PM +0200, Mathieu BLANC wrote:
> > On Tue, Mar 28, 2017 at 02:22:28PM +0200, Mathieu BLANC wrote:
> > > I can reproduce the bug (on the slave firewall) as many times as I want.
> > >
> >
> > I've ju
On Tue, Mar 28, 2017 at 02:39:44PM +0200, Mathieu BLANC wrote:
> On Tue, Mar 28, 2017 at 02:22:28PM +0200, Mathieu BLANC wrote:
> > I can reproduce the bug (on the slave firewall) as many times as I want.
> >
>
> I've just read https://www.openbsd.org/ddb.html and saw that you need a trace
> for
On Tue, Mar 28, 2017 at 02:22:28PM +0200, Mathieu BLANC wrote:
> I can reproduce the bug (on the slave firewall) as many times as I want.
>
I've just read https://www.openbsd.org/ddb.html and saw that you need a trace
for all cpu.
http://www.hostingpics.net/viewer.php?id=238876panic9.jpg
http://
On Tue, Mar 28, 2017 at 12:05:56PM +0300, Mihai Popescu wrote:
> Isn't there a CAPSLOOK written message at panic time on the screen?
> If not, look here:
> http://www.openbsd.org/report.html
>
I can reproduce the bug (on the slave firewall) as many times as I want.
I made some screenshots. Sorry
Isn't there a CAPSLOOK written message at panic time on the screen?
If not, look here:
http://www.openbsd.org/report.html
On Mon, Mar 27, 2017 at 02:42:23PM +0200, Mathieu BLANC wrote:
> Hello all,
>
> I have a pair of firewalls running 6.0 (patched with openup in october, no
> patch
> applied since then).
>
> Since the upgrade, this pair has some problem with kernel
> panics (4 times since the upgrade in october)
> 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 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 X3550 server (CPU: Intel(R) Xeon(R
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
On Sat, Jan 07, 2017 at 03:32:22PM -0800, Mike Larkin wrote:
> Also, this is the third time (that I recall) that HP has thrown us a curveball
> in their ACPI implementation (although at least this time they seem to be
> spec-compliant and it's us missing stuff). Toshiba is another vendor that
> ten
On Sat, Jan 07, 2017 at 03:32:22PM -0800, Mike Larkin wrote:
> On Mon, Jan 02, 2017 at 06:55:28AM +0900, Kyoung Jae Seo wrote:
> > On Sun, Jan 01, 2017 at 02:00:44PM +0300, Özgür Kazancci wrote:
> > > Hello,
> > >
> > > Mike, just wanted to ask if you've had any chance of committing anything
> > >
On Mon, Jan 02, 2017 at 06:55:28AM +0900, Kyoung Jae Seo wrote:
> On Sun, Jan 01, 2017 at 02:00:44PM +0300, Özgür Kazancci wrote:
> > Hello,
> >
> > Mike, just wanted to ask if you've had any chance of committing anything
> > regarding the issue? Few months have passed and I'm just curious about t
On Sun, Jan 01, 2017 at 02:00:44PM +0300, Özgür Kazancci wrote:
> Hello,
>
> Mike, just wanted to ask if you've had any chance of committing anything
> regarding the issue? Few months have passed and I'm just curious about the
> issue:
>
> http://marc.info/?l=openbsd-bugs&m=147626115403928&w=2
>
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 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) 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.
arrowscr...@mail.com [arrowscr...@mail.com] wrote:
> I login on root to restart the network and the system crashed.
> What I did:
> - Login with root on ttyC0
> - Tell dhcp that I wanted dns to localhost:
>
> # echo "supersede domain-name-servers 127.0.0.1;" >> /etc/dhclient.conf
>
> - Then resta
I am running OpenBSD 5.8 with a GENERIC SMP kernelon a Soekris 6501.
Here is the dmesg trace immediately following the kernel panic :
panic: kernel diagnostic assertion "(t->rn_flags & RNF_ROOT) == 0"
failed: file "../../../../net/radix.c", line 294
Stopped at
OpenBSD 5.8 (GENERIC.MP) #1236: Sun
On 20/03/16(Sun) 03:59, DarkSoul wrote:
> Hello list,
>
> I was testing out a beta IPv6 service over PPPoE that our ISP is
> developping,
> and playing around with kernel PPPoE.
>
> My configuration is as follows :
> - pppoe0 for IPv4 internet
> - gif0 for IPv6 internet (Hurricane Electric tunnel
Stuart Henderson wrote on Sat, Feb 13, 2016 at 08:45:35PM +:
> On 2016-02-12, Donald Allen wrote:
>> On Fri, Feb 12, 2016 at 3:42 PM, Stefan Sperling wrote:
>>> On Fri, Feb 12, 2016 at 03:03:46PM -0500, Donald Allen wrote:
I just used this exchange as an example to a friend who buys eve
On 2016-02-12, Donald Allen wrote:
> On Fri, Feb 12, 2016 at 3:42 PM, Stefan Sperling wrote:
>
>> On Fri, Feb 12, 2016 at 03:03:46PM -0500, Donald Allen wrote:
>> > I just used this exchange as an example to a friend who buys everything
>> > Apple and then complains when their software is buggy.
On Fri, Feb 12, 2016 at 3:42 PM, Stefan Sperling wrote:
> On Fri, Feb 12, 2016 at 03:03:46PM -0500, Donald Allen wrote:
> > I just used this exchange as an example to a friend who buys everything
> > Apple and then complains when their software is buggy. This is a perfect
> > example of how a dir
On Fri, Feb 12, 2016 at 03:03:46PM -0500, Donald Allen wrote:
> I just used this exchange as an example to a friend who buys everything
> Apple and then complains when their software is buggy. This is a perfect
> example of how a direct negative feedback path makes software converge
> quickly to co
On Fri, Feb 12, 2016 at 11:17 AM, Stefan Sperling wrote:
> On Fri, Feb 12, 2016 at 10:47:16AM -0500, Donald Allen wrote:
> > On Fri, Feb 12, 2016 at 10:45 AM, Chris Cappuccio
> wrote:
> >
> > > Donald Allen [donaldcal...@gmail.com] wrote:
> > > > On Feb 12, 2016 05:08, "Stefan Sperling" wrote:
On Fri, Feb 12, 2016 at 10:47:16AM -0500, Donald Allen wrote:
> On Fri, Feb 12, 2016 at 10:45 AM, Chris Cappuccio wrote:
>
> > Donald Allen [donaldcal...@gmail.com] wrote:
> > > On Feb 12, 2016 05:08, "Stefan Sperling" wrote:
> > > >
> > > > On Thu, Feb 11, 2016 at 08:42:21PM -0500, Donald Allen
On Fri, Feb 12, 2016 at 10:45 AM, Chris Cappuccio wrote:
> Donald Allen [donaldcal...@gmail.com] wrote:
> > On Feb 12, 2016 05:08, "Stefan Sperling" wrote:
> > >
> > > On Thu, Feb 11, 2016 at 08:42:21PM -0500, Donald Allen wrote:
> > > > When attempting to install the 2/8 snapshot on my Thinkpad
Donald Allen [donaldcal...@gmail.com] wrote:
> On Feb 12, 2016 05:08, "Stefan Sperling" wrote:
> >
> > On Thu, Feb 11, 2016 at 08:42:21PM -0500, Donald Allen wrote:
> > > When attempting to install the 2/8 snapshot on my Thinkpad x-250, I
> chose
> > > to configure the wireless network interface (
On Feb 12, 2016 05:08, "Stefan Sperling" wrote:
>
> On Thu, Feb 11, 2016 at 08:42:21PM -0500, Donald Allen wrote:
> > When attempting to install the 2/8 snapshot on my Thinkpad x-250, I
chose
> > to configure the wireless network interface (iwm). This resulted in the
> > following:
> >
> > iwm0: c
On Thu, Feb 11, 2016 at 08:42:21PM -0500, Donald Allen wrote:
> When attempting to install the 2/8 snapshot on my Thinkpad x-250, I chose
> to configure the wireless network interface (iwm). This resulted in the
> following:
>
> iwm0: could not read firmware iwm-7265-9 (error 2)
> panic: attempt t
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 cause is not known.
> >
> > I'm running
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 different USB ports with the
>
The crash I reported a few days ago is the same:
ehci_device_clear_toggle: queue active
> On 9 paź 2015, at 13:54, Mike Larkin wrote:
>
> On Fri, Oct 09, 2015 at 04:35:48AM -0700, Mike Larkin wrote:
>> On Fri, Oct 09, 2015 at 09:53:16AM +0200, Holger Glaess wrote:
On Fri, Oct 09, 2015 at 06:22:53AM +0200, Holger Glaess wrote:
> hi
>
> what kind of information you ne
On Fri, Oct 09, 2015 at 04:35:48AM -0700, Mike Larkin wrote:
> On Fri, Oct 09, 2015 at 09:53:16AM +0200, Holger Glaess wrote:
> > > On Fri, Oct 09, 2015 at 06:22:53AM +0200, Holger Glaess wrote:
> > >> hi
> > >>
> > >> what kind of information you need more ?
> > >>
> > >
> > > uhm. this machine is
On Fri, Oct 09, 2015 at 09:53:16AM +0200, Holger Glaess wrote:
> > On Fri, Oct 09, 2015 at 06:22:53AM +0200, Holger Glaess wrote:
> >> hi
> >>
> >> what kind of information you need more ?
> >>
> >
> > uhm. this machine is very very strange. It has devices I've never
> > seen before and many other
> On Fri, Oct 09, 2015 at 06:22:53AM +0200, Holger Glaess wrote:
>> hi
>>
>> what kind of information you need more ?
>>
>
> uhm. this machine is very very strange. It has devices I've never
> seen before and many other devices not even recognized. Without access
> to the hardware there's not much
On Fri, Oct 09, 2015 at 06:22:53AM +0200, Holger Glaess wrote:
> hi
>
> what kind of information you need more ?
>
uhm. this machine is very very strange. It has devices I've never
seen before and many other devices not even recognized. Without access
to the hardware there's not much we can do h
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
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*,
On Tue, Nov 11, 2014 at 1:04 PM, Stefan Sperling wrote:
> On Tue, Nov 11, 2014 at 01:44:57PM +0200, Alexey Kurinnij wrote:
>> Sorry, in first message ddb only for one processor. This is fresh for both:
>
> athn0 at pci3 dev 0 function 0 "Atheros AR9300" rev 0x01: apic 0 int 16
>
> Sorry, this chip
On Tue, Nov 11, 2014 at 01:44:57PM +0200, Alexey Kurinnij wrote:
> Sorry, in first message ddb only for one processor. This is fresh for both:
athn0 at pci3 dev 0 function 0 "Atheros AR9300" rev 0x01: apic 0 int 16
Sorry, this chip isn't supported. See the man page -- it's not listed.
Damien com
Sorry, in first message ddb only for one processor. This is fresh for both:
# ifconfig athn0 up
panic: kernel diagnostic assertion "pin < sc->ngpiopins" failed: file
"../../../../dev/ic/ar9003.c", line 512
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN
Hello,
On 4 September 2014 11:30, wrote:
> Hi all,
> ...
> [demime 1.01d removed an attachment of type image/png which had a name of
> PS_1_2014-09-01 15_14_25-UI-SRV-MCR-01-test-FC.PNG]
>
> [demime 1.01d removed an attachment of type image/png which had a name of
> PS_2_2014-09-01 15_14_25-UI
> Hello,
Hello
> When startig X on the latest snapshot the kernel paniced, I was stupid
enough not to run the suggested
> command at the ddb prompt because I forgot.
>
> Here's the error it reported:
>
> uvm_fault(0xfe823cb0c468, 0x278, 0, 1) -> e
> kernel: page fault trap, code=0
> Sto
On 6/27/14, Theo de Raadt wrote:
>> On 2014-06-26, Scott Vanderbilt wrote:
>> > Having done a little man page reading on boot-time configuration, I
>> > learned about the existence of ukc. I'm wondering whether something
>> > like
>> >
>> >ukc> disable acpi0
>> >
>> > might circumvent the ker
On Fri, Jun 27, 2014 at 12:37:33PM -0700, Scott Vanderbilt wrote:
> On 6/27/2014 12:10 PM, Stuart Henderson wrote:
> >On 2014-06-26, Scott Vanderbilt wrote:
> >>Having done a little man page reading on boot-time configuration, I
> >>learned about the existence of ukc. I'm wondering whether somethi
On Fri, Jun 27, 2014 at 01:15:59PM -0600, Theo de Raadt wrote:
> > On 2014-06-26, Scott Vanderbilt wrote:
> > > Having done a little man page reading on boot-time configuration, I
> > > learned about the existence of ukc. I'm wondering whether something like
> > >
> > >ukc> disable acpi0
> >
On 6/27/2014 12:10 PM, Stuart Henderson wrote:
On 2014-06-26, Scott Vanderbilt wrote:
Having done a little man page reading on boot-time configuration, I
learned about the existence of ukc. I'm wondering whether something like
ukc> disable acpi0
might circumvent the kernel panic and allow
> On 2014-06-26, Scott Vanderbilt wrote:
> > Having done a little man page reading on boot-time configuration, I
> > learned about the existence of ukc. I'm wondering whether something like
> >
> >ukc> disable acpi0
> >
> > might circumvent the kernel panic and allow the boot to successfully
On 2014-06-26, Scott Vanderbilt wrote:
> Having done a little man page reading on boot-time configuration, I
> learned about the existence of ukc. I'm wondering whether something like
>
>ukc> disable acpi0
>
> might circumvent the kernel panic and allow the boot to successfully
> complete. I
Unfortunately, not. It was a fresh install from a CD image to a hard
drive which I then shipped to the ISP for installation, which replaced a
failing drive in my machine co-located there.
In any event, bypassing acpi in ukc got the machine up again, and I was
able to upgrade to the latest snap
I know on my laptop no acpi meant doesn't work. My saving grace is I
always keep a kernel from the previous snapshot I tried as obsd. So if
bsd doesn't work, I just boot from that. Do you have an older snapshot
kernel you can tell tech support to boot into?
On Thu, Jun 26, 2014 at 7:36 PM, Scott V
I can also confirm that newest snapshot works now.
On Thu, Jun 26, 2014 at 7:45 AM, Nils R wrote:
> Works now with the latest snapshot (dsdt.c rev. 1.211), thanks!
Scott Vanderbilt [li...@datagenic.com] wrote:
> Having done a little man page reading on boot-time configuration, I learned
> about the existence of ukc. I'm wondering whether something like
>
> ukc> disable acpi0
>
That or disable acpi
> might circumvent the kernel panic and allow the boot t
Having done a little man page reading on boot-time configuration, I
learned about the existence of ukc. I'm wondering whether something like
ukc> disable acpi0
might circumvent the kernel panic and allow the boot to successfully
complete. I'm hoping that since this is a server, ACPI is non-e
I have this exact same kernel panic. Unfortunately, it's occurring on a
host at a remote co-lo. Does anyone know a way that I can get the
on-site tech to suppress the assertion by way of some boot-time
configuration? Then at least I can get this machine up and running so I
can immediately upgra
Works now with the latest snapshot (dsdt.c rev. 1.211), thanks!
Am 25.06.2014 17:05 schrieb Jason Crawford :
>
> My system panic's from the KASSERT() call at line 2269 after dsdt.c was
> updated to 1.210.
>
> All I have is the basic panic message and the dmesg from the last known
> working snapshot kernel. I tried to get more information but my USB
> keyboa
On Mon, Apr 7, 2014 at 9:49 AM, sangdrax8 wrote:
> I have had a kernel panic that took down my system, and I was wondering if
> someone
> can provide some insight into where I can begin with this. I had to reboot
> the machine
> to get it back up, but I did run a trace and grabbed the output fr
1 - 100 of 237 matches
Mail list logo