On Sat, Oct 24, 2020 at 2:38 PM Mark Johnston wrote:
> On Fri, Oct 23, 2020 at 06:32:25PM +0200, Michal Meloun wrote:
> >
> >
> > On 19.10.2020 22:39, Mark Johnston wrote:
> > > On Fri, Oct 16, 2020 at 11:53:56AM +0200, Michal Meloun wrote:
> > >>
> > >>
> > >> On 06.10.2020 15:37, Mark Johnston
On Fri, Oct 23, 2020 at 06:32:25PM +0200, Michal Meloun wrote:
>
>
> On 19.10.2020 22:39, Mark Johnston wrote:
> > On Fri, Oct 16, 2020 at 11:53:56AM +0200, Michal Meloun wrote:
> >>
> >>
> >> On 06.10.2020 15:37, Mark Johnston wrote:
> >>> On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska
On 19.10.2020 22:39, Mark Johnston wrote:
> On Fri, Oct 16, 2020 at 11:53:56AM +0200, Michal Meloun wrote:
>>
>>
>> On 06.10.2020 15:37, Mark Johnston wrote:
>>> On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote:
Still seeing non-current pmap panics on the Pi3, this time a B+
On Tue, Oct 20, 2020 at 11:55:30AM -0700, bob prohaska wrote:
> On Tue, Oct 20, 2020 at 12:30:05PM -0400, Mark Johnston wrote:
> >
> > I set up a RPi3 to try and repro this and have so far managed to trigger
> > it once using Peter Holm's stress2 suite, so I'll keep investigating. I
> > hadn't
On Tue, Oct 20, 2020 at 12:30:05PM -0400, Mark Johnston wrote:
>
> I set up a RPi3 to try and repro this and have so far managed to trigger
> it once using Peter Holm's stress2 suite, so I'll keep investigating. I
> hadn't configured a dump device, but I was able to confirm from DDB that
>
On Mon, Oct 19, 2020 at 04:09:09PM -0700, bob prohaska wrote:
> On Mon, Oct 19, 2020 at 04:39:54PM -0400, Mark Johnston wrote:
> >
> > I think vmspace_exit() should issue a release fence with the cmpset and
> > an acquire fence when handling the refcnt == 1 case, but I don't see why
> > that
On Mon, Oct 19, 2020 at 04:39:54PM -0400, Mark Johnston wrote:
>
> I think vmspace_exit() should issue a release fence with the cmpset and
> an acquire fence when handling the refcnt == 1 case, but I don't see why
> that would make a difference here. So, if you can test a debug patch,
> this one
On Fri, Oct 16, 2020 at 11:53:56AM +0200, Michal Meloun wrote:
>
>
> On 06.10.2020 15:37, Mark Johnston wrote:
> > On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote:
> >> Still seeing non-current pmap panics on the Pi3, this time a B+ running
> >> 13.0-CURRENT (GENERIC-MMCCAM) #0
On 06.10.2020 15:37, Mark Johnston wrote:
> On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote:
>> Still seeing non-current pmap panics on the Pi3, this time a B+ running
>> 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master)
>> during a -j4 buildworld. The backtrace reports
On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote:
> Still seeing non-current pmap panics on the Pi3, this time a B+ running
> 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master)
> during a -j4 buildworld. The backtrace reports
>
> panic: non-current pmap 0xa00020eab8f0
On 9/8/19 6:03 PM, Curtis Hamilton wrote:
I'm encountering (randomly) the below error when trying to install
351901 from CD/DVD.
On what type of system ?
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
On 20/01/2017 02:09, Larry Rosenman wrote:
> Thu Jan 19 18:03:38 CST 2017
>
> FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #13 r311997: Sat Jan
> 14 22:35:29 CST 2017 r...@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER
> amd64
>
> panic: racct_adjust_resource: resource 4 usage <
On 03/31/15 02:15, Konstantin Belousov wrote:
On Tue, Mar 31, 2015 at 02:51:47AM +0300, Konstantin Belousov wrote:
On Tue, Mar 31, 2015 at 01:41:04AM +0300, Gleb Smirnoff wrote:
On Tue, Mar 31, 2015 at 12:30:04AM +0200, Hans Petter Selasky wrote:
H On 03/30/15 23:19, Gleb Smirnoff wrote:
H On
On Mon, Mar 30, 2015 at 02:30:04PM -0700, Adrian Chadd wrote:
A Would you mind filing a PR for it so it isn't forgotten?
If I could provide enough information to fix that, I would either
fix myself or forward information to someone confident in build.
Creating PR with what I have now means
On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote:
M I get the following panic on current svn ver r280793:
M
M Sat Mar 28 14:41:28 PDT 2015
M
M FreeBSD/amd64 (pozo.com) (ttyu0)
M
M panic: Invalid CPU in callout 16
The same happened to me in the OFED code. After investigation
it
On 03/30/15 23:19, Gleb Smirnoff wrote:
On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote:
M I get the following panic on current svn ver r280793:
M
M Sat Mar 28 14:41:28 PDT 2015
M
M FreeBSD/amd64 (pozo.com) (ttyu0)
M
M panic: Invalid CPU in callout 16
The same happened to me in
On Tue, Mar 31, 2015 at 12:30:04AM +0200, Hans Petter Selasky wrote:
H On 03/30/15 23:19, Gleb Smirnoff wrote:
H On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote:
H M I get the following panic on current svn ver r280793:
H M
H M Sat Mar 28 14:41:28 PDT 2015
H M
H M
Hi,
Would you mind filing a PR for it so it isn't forgotten?
-a
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
On Tue, Mar 31, 2015 at 01:41:04AM +0300, Gleb Smirnoff wrote:
On Tue, Mar 31, 2015 at 12:30:04AM +0200, Hans Petter Selasky wrote:
H On 03/30/15 23:19, Gleb Smirnoff wrote:
H On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote:
H M I get the following panic on current svn ver
On Tue, Mar 31, 2015 at 02:51:47AM +0300, Konstantin Belousov wrote:
On Tue, Mar 31, 2015 at 01:41:04AM +0300, Gleb Smirnoff wrote:
On Tue, Mar 31, 2015 at 12:30:04AM +0200, Hans Petter Selasky wrote:
H On 03/30/15 23:19, Gleb Smirnoff wrote:
H On Sat, Mar 28, 2015 at 03:02:28PM -0700,
On Sat, Mar 28, 2015 at 3:02 PM, Manfred Antar n...@pozo.com wrote:
I get the following panic on current svn ver r280793:
Revert to r280784. This should fix.
___
freebsd-current@freebsd.org mailing list
At 03:06 PM 3/28/2015, Davide Italiano wrote:
On Sat, Mar 28, 2015 at 3:02 PM, Manfred Antar n...@pozo.com wrote:
I get the following panic on current svn ver r280793:
Revert to r280784. This should fix.
That works
Thanks
|| n...@pozo.com ||
||
On 10.12.13 03:52, Larry Rosenman wrote:
On 2013-12-09 16:04, Aleksandr Rybalko wrote:
On Mon, 9 Dec 2013 10:36:34 -0600
Larry Rosenman l...@lerctr.org wrote:
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root:
On Mon, 9 Dec 2013 10:36:34 -0600
Larry Rosenman l...@lerctr.org wrote:
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 259130
On 2013-12-09 16:04, Aleksandr Rybalko wrote:
On Mon, 9 Dec 2013 10:36:34 -0600
Larry Rosenman l...@lerctr.org wrote:
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/base
Repository UUID:
On Tue, Sep 11, 2012 at 6:32 PM, Glen Barber g...@freebsd.org wrote:
I'd blame this one:
http://lists.freebsd.org/pipermail/svn-src-head/2012-September/040236.html
Yes, reverting that commit allows the system to boot.
Hi,
Same problem on my side (under Virtualbox or on an IBM 3550 M2).
Am 09/12/12 09:30, schrieb Olivier Cochard-Labbé:
On Tue, Sep 11, 2012 at 6:32 PM, Glen Barber g...@freebsd.org wrote:
I'd blame this one:
http://lists.freebsd.org/pipermail/svn-src-head/2012-September/040236.html
Yes, reverting that commit allows the system to boot.
Hi,
Same
on 12/09/2012 10:30 Olivier Cochard-Labbé said the following:
On Tue, Sep 11, 2012 at 6:32 PM, Glen Barber g...@freebsd.org wrote:
I'd blame this one:
http://lists.freebsd.org/pipermail/svn-src-head/2012-September/040236.html
Yes, reverting that commit allows the system to boot.
Hi,
On Tue, Sep 11, 2012 at 12:12:34PM -0400, Glen Barber wrote:
G Hi,
G
G I upgraded to head/ r239865 (Last Changed Date: 2012-09-11 09:29:50).
G
G My laptop now panics with on boot with the new kernel.
G
G Backtrace (and hopefully some useful) information is attached. I can
G provide any
Hi,
On Tue, Sep 11, 2012 at 08:19:54PM +0400, Gleb Smirnoff wrote:
G I upgraded to head/ r239865 (Last Changed Date: 2012-09-11 09:29:50).
G
G My laptop now panics with on boot with the new kernel.
G
I'd blame this one:
on 27/06/2012 08:27 Andrey Fesenko said the following:
On Wed, Jun 27, 2012 at 9:06 AM, Erich Dollansky
erichfreebsdl...@ovitrap.com wrote:
Hi,
I am getting a panix when I boot a newly compiled system with sources
downloaded yesterday. The panic was still there with the sources from three
Hi,
On Wednesday 27 June 2012 13:20:10 Andriy Gapon wrote:
on 27/06/2012 08:27 Andrey Fesenko said the following:
On Wed, Jun 27, 2012 at 9:06 AM, Erich Dollansky
erichfreebsdl...@ovitrap.com wrote:
Hi,
I am getting a panix when I boot a newly compiled system with sources
downloaded
on 27/06/2012 11:39 Erich Dollansky said the following:
Anyway, What would be a save way to get a trace to a disk as I do not have a
backup system with me?
Assuming I understand the question correctly your options are:
- remote console (serial/firewire/etc) from another machine
- digital camera
Hi,
On Wednesday 27 June 2012 15:42:43 Andriy Gapon wrote:
on 27/06/2012 11:39 Erich Dollansky said the following:
Anyway, What would be a save way to get a trace to a disk as I do not have a
backup system with me?
Assuming I understand the question correctly your options are:
- remote
On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon a...@freebsd.org wrote:
on 27/06/2012 11:39 Erich Dollansky said the following:
Anyway, What would be a save way to get a trace to a disk as I do not have a
backup system with me?
Assuming I understand the question correctly your options are:
-
on 27/06/2012 11:49 Erich Dollansky said the following:
Hi,
On Wednesday 27 June 2012 15:42:43 Andriy Gapon wrote:
on 27/06/2012 11:39 Erich Dollansky said the following:
Anyway, What would be a save way to get a trace to a disk as I do not have a
backup system with me?
Assuming I
On Wed, Jun 27, 2012 at 1:26 PM, Andrey Fesenko f0and...@gmail.com wrote:
On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon a...@freebsd.org wrote:
on 27/06/2012 11:39 Erich Dollansky said the following:
Anyway, What would be a save way to get a trace to a disk as I do not have a
backup system
on 27/06/2012 13:44 Andrey Fesenko said the following:
On Wed, Jun 27, 2012 at 1:26 PM, Andrey Fesenko f0and...@gmail.com wrote:
On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon a...@freebsd.org wrote:
on 27/06/2012 11:39 Erich Dollansky said the following:
Anyway, What would be a save way to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-27 07:07:40 -0400, Andriy Gapon wrote:
on 27/06/2012 13:44 Andrey Fesenko said the following:
On Wed, Jun 27, 2012 at 1:26 PM, Andrey Fesenko
f0and...@gmail.com wrote:
On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon
a...@freebsd.org
Hi,
On Wednesday 27 June 2012 23:20:09 Jung-uk Kim wrote:
On 2012-06-27 07:07:40 -0400, Andriy Gapon wrote:
on 27/06/2012 13:44 Andrey Fesenko said the following:
On Wed, Jun 27, 2012 at 1:26 PM, Andrey Fesenko
f0and...@gmail.com wrote:
On Wed, Jun 27, 2012 at 12:42 PM, Andriy Gapon
On Wed, Jun 27, 2012 at 9:06 AM, Erich Dollansky
erichfreebsdl...@ovitrap.com wrote:
Hi,
I am getting a panix when I boot a newly compiled system with sources
downloaded yesterday. The panic was still there with the sources from three
days ago.
The panic regards /usr/src/sys/vm/uma_core/c
On Thu, 3 Jun 2010, John Doe wrote:
Boot into single user-mode
# tunefs -j enable /
# tunefs -j enable /usr
# tunefs -j enable /tmp
# tunefs -j enable /var
# reboot
The machine then panics.
Looks like the machine is trying to write to a read-only filesystem.
Can you please give me
From: Jeff Roberson jrober...@jroberson.net
To: John Doe lex...@ymail.com
Cc: curr...@freebsd.org
Sent: Thu, June 3, 2010 7:19:59 PM
Subject: Re: Panic on current when enabling SUJ
On Thu, 3 Jun 2010, John Doe wrote:
Boot into single user-mode
# tunefs -j
On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote:
Could you please try with 207902?
...
I saved that environment (documented elsewhere ini the thread), then
performed the normal (for me) daily update, this time, to r207911.
Again, I see a panic during transition from single-user mode to
Please try 207949
Thanks,
Kip
On Tue, May 11, 2010 at 6:18 AM, David Wolfskill da...@catwhisker.org wrote:
On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote:
Could you please try with 207902?
...
I saved that environment (documented elsewhere ini the thread), then
performed
On Tue, May 11, 2010 at 08:30:09PM -0700, K. Macy wrote:
Please try 207949
...
The panic (this time) didn't show up until about 10 seconds after the
login: prompt showed up on the serial console. Here's what it looks
like:
...
3 Select option, [Enter] for default 3
3 or [Space]
On Tue, May 11, 2010 at 9:24 PM, David Wolfskill da...@catwhisker.org wrote:
On Tue, May 11, 2010 at 08:30:09PM -0700, K. Macy wrote:
Please try 207949
...
The panic (this time) didn't show up until about 10 seconds after the
login: prompt showed up on the serial console. Here's what
On Mon, May 10, 2010 at 08:22:43PM +0200, Ed Schouten wrote:
...
You don't happen to have a backtrace?
Oops -- sorry; got caught up in getting ready to head in to work:
db bt
Tracing pid 20 tid 100067 td 0xc5a19000
_mtx_lock_flags(58,0,c0cd2d5b,570,80,...) at _mtx_lock_flags+0x46
Subject: Re: Panic @r207844;current process: flowcleaner Fatal trap
12:
page fault while inkernel mode
On Mon, May 10, 2010 at 08:22:43PM +0200, Ed Schouten wrote:
...
You don't happen to have a backtrace?
Oops -- sorry; got caught up in getting ready to head in to work:
db bt
Tracing
Could you please try with 207902?
Thanks,
Kip
On Mon, May 10, 2010 at 11:26 AM, David Wolfskill da...@catwhisker.org wrote:
On Mon, May 10, 2010 at 08:22:43PM +0200, Ed Schouten wrote:
...
You don't happen to have a backtrace?
Oops -- sorry; got caught up in getting ready to head in to
On Mon, May 10, 2010 at 2:32 PM, K. Macy km...@freebsd.org wrote:
Could you please try with 207902?
And if not, please get a coredump with a backtrace with symbols.
Thanks
___
freebsd-current@freebsd.org mailing list
On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote:
Could you please try with 207902?
...
First, thanks for the response.
OK; I grabbed r207902 applied it (via patch -p1), then rebuilt the
kernel rebooted; here's the panic now:
3 Select option, [Enter] for default 3
3 or
Are you not able to dump core?
Thanks,
Kip
On Mon, May 10, 2010 at 3:08 PM, David Wolfskill da...@catwhisker.org wrote:
On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote:
Could you please try with 207902?
...
First, thanks for the response.
OK; I grabbed r207902 applied it (via
On Mon, May 10, 2010 at 03:52:07PM -0700, David Wolfskill wrote:
On Mon, May 10, 2010 at 03:39:11PM -0700, K. Macy wrote:
Are you not able to dump core?
Here's the crash summary; I can put the dump on my Web server on request.
(It weighs in at 89MB.)
Compression reduced the
On Tue, Oct 14, 2003 at 10:14:37PM +0200, Soren Schmidt wrote:
It seems Christoph P. Kukulies wrote:
Help! Am I alone with this? I cvsuped again today built world,kernel.
Still this panic. Soeren, do you get this also? You have the Motherboard
P4S8X which I donated a couple of months ago.
On Tue, Oct 14, 2003 at 10:14:37PM +0200, Soren Schmidt wrote:
It seems Christoph P. Kukulies wrote:
Help! Am I alone with this? I cvsuped again today built world,kernel.
Still this panic. Soeren, do you get this also? You have the Motherboard
P4S8X which I donated a couple of months ago.
Help! Am I alone with this? I cvsuped again today built world,kernel.
Still this panic. Soeren, do you get this also? You have the Motherboard
P4S8X which I donated a couple of months ago.
It does not happen with an Oct 5 kernel.
On Sun, Oct 12, 2003 at 01:52:40PM +0200, C. Kukulies wrote:
with
It seems Christoph P. Kukulies wrote:
Help! Am I alone with this? I cvsuped again today built world,kernel.
Still this panic. Soeren, do you get this also? You have the Motherboard
P4S8X which I donated a couple of months ago.
Nope, I dont see this at all. No problems whatsoever with the
On 27-Jul-2002 Arun Sharma wrote:
This is with the GENERIC kernel. Known problem ? How can I get a
-current kernel that boots to multiuser so that I can tinker around with
it ? Are there any magic config files that suppress these panics ?
db trace
_mtx_lock_flags(7069307e,0,c03ff2e0,530)
On Sat, Jul 27, 2002 at 05:15:08PM -0400, John Baldwin wrote:
Knowing the actual panic message would help. :)
My bad. I was loading the wrong version of a kernel module (ipfw).
-Arun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the
On Sun, 21 Jul 2002, Mark Peek wrote:
There is a reproducible panic in -current after using
i386_set_ioperm(). The extended pcb is attempted to be freed in
cpu_thread_exit() using kmem_free(). Via private mail, Alan Cox
explained it to me as such:
The problem runs deeper than Giant
On Sat, Sep 01, 2001 at 11:25:04PM +0900, Mitsuru IWASAKI wrote:
Hi, I've noticed that the recent CURRENT got panic on some machines
if we have `device acpica' in kernel config.
ata0: at 0x1f0 irq 14 on atapci0
Fatal trap 12: page fault while in kernel mode
fault virtual address
Hi, I've noticed that the recent CURRENT got panic on some machines
if we have `device acpica' in kernel config.
You've loaded the ACPI module as well as compiling it into the kernel.
Don't do that.
I hope more proper fixes would be made...
Peter has suggested that properly versioning the
Date: Mon, 28 May 2001 10:46:53 -0700 (PDT)
From: David Wolfskill [EMAIL PROTECTED]
This is on a system (my laptop):
FreeBSD localhost 5.0-CURRENT FreeBSD 5.0-CURRENT #13: Sun May 27 23:44:24 PDT 2001
[EMAIL PROTECTED]:/common/C/obj/usr/src/sys/LAPTOP_30W i386 Mon May 28
07:27:59 PDT 2001
On Fri, May 18, 2001 at 09:25:59PM -0700, David Wolfskill wrote:
I haven't seen anyone else reporting any problems similar to what I
experienced, so I'm not about to claim there's something that's
definitely broken
I have seen exactly the same - the machine (IBM thinkpad T21)
freezes
Panic w/ softupdate disappears after I grab this revision of
ffs_softdep.c:
ident /usr/src/sys/ufs/ffs/ffs_softdep.c
/usr/src/sys/ufs/ffs/ffs_softdep.c:
$FreeBSD: src/sys/ufs/ffs/ffs_softdep.c,v 1.97 2001/05/19 19:24:26 mckusick Exp $
Now it's fairly smooth to buildworld, installworld,
Hello everybody,
attention! pure speculation and unprofessional comments follow!
These problems with the alternate superblock remind me... there were
reports about the same when fsck had problems some time ago.
But there was a common theme to all of them: The fsck raves were a whole
lot more
Date: Fri, 18 May 2001 10:48:19 -0700 (PDT)
From: David Wolfskill [EMAIL PROTECTED]
[Excruciatingly long narrative of panic during buildworld for today's
-CURRENT elided; it's in the archives. dhw]
Reporting back after getting today's -CURRENT built:
FreeBSD dhcp-140.catwhisker.org 5.0-CURRENT
I would like to see full dump of 'vidcontrol -i adapter',
'vidcontrol -i mode' and dmesg after the vesa module is loaded
(you get very verbose output from the vesa module init code
if you boot the kernel with 'boot -v').
I think this is what you asked for, otherwise please let me know.
Bye,
Andrea Campi [EMAIL PROTECTED] writes:
Ok, I will try each one. At the moment, I'm using logo_saver.
I will let you know.
Take a long hard look at vesa_set_mode() and vesa_set_origin() in
sys/i386/isa/vesa.c. If the panic occurs while the console is still in
text mode, the bug is in
Andrea Campi [EMAIL PROTECTED] writes:
Ok, I will try each one. At the moment, I'm using logo_saver.
I will let you know.
Take a long hard look at vesa_set_mode() and vesa_set_origin() in
sys/i386/isa/vesa.c. If the panic occurs while the console is still in
text mode, the bug is in
db x/i,10 0xc025ad3c
scrn_timer: pushl %ebp
[...]
nm just confirmed this, so it definitely looks like scrn_timer is to blame
here. Any other instructions? ;-) For the time being, vidcontrol -t off
(seems to) keep the machine up.
Bye,
Andrea
Weird, I don't see
On 05-Dec-00 Andrea Campi wrote:
db x/i,10 0xc025ad3c
scrn_timer: pushl %ebp
[...]
nm just confirmed this, so it definitely looks like scrn_timer is to blame
here. Any other instructions? ;-) For the time being, vidcontrol -t off
(seems to) keep the machine up.
Bye,
More details: this is an IBM Thinkpad laptop with APM enabled and in the
kernel.
As usual, any hint is more than welcome. This used to work...
Which screen saver? Does it do it with all of them? Just graphical ones, just
text ones, just green_saver, etc.?
Rrrright... I can assure you
On 05-Dec-00 Andrea Campi wrote:
More details: this is an IBM Thinkpad laptop with APM enabled and in the
kernel.
As usual, any hint is more than welcome. This used to work...
Which screen saver? Does it do it with all of them? Just graphical ones,
just
text ones, just green_saver,
Just as a data point, I just tried this as well... The daemon saver was ok,
the fire saver was ok, but as soon as I loaded logo_saver and it activated,
I got a 'dc0 timeout'(?) and I was unable to access any of the vtys after
that... I could switch vtys, but could not type anything.
The
Sorry, I guess I should specify that this is a desktop with APM enabled in
the BIOS, but not being used otherwise... VESA module loaded.
#uname -a
FreeBSD cae88-102-101.sc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Dec 2
16:07:54 EST 2000 [EMAIL
Bad callout handler: c_func = 0xc025ad3c, c_arg=0xc0338460, c_flags=7
First I tried a
db x/i,10 0xc025ad3c
scrn_timer: pushl %ebp
[...]
nm just confirmed this, so it definitely looks like scrn_timer is to blame
here. Any other instructions? ;-) For the time being,
We want mtxd_file and mtxd_line. If you look at the output of the last
command, it will probably look something like this:
../../kern/kern_timeout.c, line 139
Hope it helps,
Andrea
--
Andrea Campi mailto:[EMAIL PROTECTED]
I.NET S.p.A.
On 29-Nov-00 Andrea Campi wrote:
We want mtxd_file and mtxd_line. If you look at the output of the last
command, it will probably look something like this:
../../kern/kern_timeout.c, line 139
Hmm, and the failed assertion was:
panic: mutex Giant owned at ../../kern/kern_intr.c:238
So
Then when it panics write down the values that get printed out. Next,
do 'nm /sys/compile/MYKERNEL/kernel.debug | sort' and look for the function
whose address matches the c_func address printed out, then send this info back
please. :)
This time it took me 1 hour to get the panic, compared
On 29-Nov-00 Andrea Campi wrote:
Then when it panics write down the values that get printed out. Next,
do 'nm /sys/compile/MYKERNEL/kernel.debug | sort' and look for the function
whose address matches the c_func address printed out, then send this info
back
please. :)
This time it took
On 28-Nov-00 Andrea Campi wrote:
Latest (this night) current, no system activity:
panic: mutex Giant owned at ../../kern/kern_intr.c:238
I can sen you kernel conf if needed.
Is this known or should I invest some time to debug it?
Eek! I haven't seen this. If you can reproduce this,
Hi ...
Without starting the racoon daemon and doing a secure connect
everything works fine without a problem. If I start racoon,
do a tunnel connection and then run daily, the machine panics ..
Reinier
On 16-Sep-00 Shoichi 'Ne' Sakane wrote:
I'm running a current machine of 12 Sept although
As far as I recall ... the first kernel was before any of the SMP
commits ... but in case it was not ... how do I go about
going back to a "coarse grain lock" kernel ... can I set
something in the config file or do I have to checkout old
sources ??
Reinier
On 17-Sep-00 [EMAIL PROTECTED] wrote:
"current machine" meaning FreeBSD-current? if so, are there any
locking behavior changes due to the introduction of fine grain locks?
what happens if you go back to coarse grain lock kernel?
As far as I recall ... the first kernel was before any of the SMP
commits ... but
Without starting the racoon daemon and doing a secure connect
everything works fine without a problem. If I start racoon,
do a tunnel connection and then run daily, the machine panics ..
I bet you can panic the kernel with setkey(8) in that case. am I
correct? if so,
On Mon, 18 Sep 2000 10:00:53 +0200 (SAST)
Reinier Bezuidenhout [EMAIL PROTECTED] said:
rbezuide As far as I recall ... the first kernel was before any of the SMP
rbezuide commits ... but in case it was not ... how do I go about
rbezuide going back to a "coarse grain lock" kernel ... can I set
I'm running a current machine of 12 Sept although this problem
also occured on a current of a few days earlier ...
"current machine" meaning FreeBSD-current? if so, are there any
locking behavior changes due to the introduction of fine grain locks?
what happens if
89 matches
Mail list logo
