Current problem reports assigned to freebsd-stable@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Reproducable Infiniband panic
On 06/07/2013 06:06 PM, John Baldwin wrote: > On Friday, June 07, 2013 5:07:34 am Julian Stecklina wrote: >> On 06/06/2013 08:57 PM, John Baldwin wrote: >>> On Thursday, June 06, 2013 9:54:35 am Andriy Gapon wrote: >> [...] The problem seems to be in incorrect interaction between devfs_close_f > and linux_file_dtor. The latter expects curthread->td_fpop to have a valid > reasonable value. But the former sets curthread->td_fpop to fp only around > vnops.fo_close() call and then restores it back to some (what?) previous value before > calling devfs_fpdrop->devfs_destroy_cdevpriv. In this case the previous value is > NULL. >>> >>> It is normally NULL in this case. Why does linux_file_dtor even look at >>> td_fpop? >>> >>> Ah. I think it should not do that and make the data it uses in the dtor > more >>> self-contained: [...] Seems to fix my panic. Thanks! Julian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Error in make buildkernel `
Hi,
I'm trying to build a stable kernle on a freshly build 8.4-Stable i386
system.
And I get:
MAKE=make sh /usr/srcs/src9/src/sys/conf/newvers.sh GENERIC
/usr/local/bin/svnversion
cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
-Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I.
-I/usr/srcs/src9/src/sys -I/usr/srcs/src9/src/sys/contrib/altq -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
-finline-limit=8000 --param inline-unit-growth=100 --param
large-function-growth=1000 -mno-align-long-strings
-mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float
-ffreestanding -fstack-protector -Werror vers.c
ctfconvert -L VERSION -g vers.o
linking kernel.debug
ld:/usr/srcs/src9/src/sys/conf/ldscript.i386:66: syntax error
*** Error code 1
Stop in /usr/obj/usr/srcs/src9/src/sys/GENERIC.
*** Error code 1
Stop in /usr/srcs/src9/src.
*** Error code 1
Line 66 is: .eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
The piece of "code" around line 66 looks like:
PROVIDE (__etext = .);
PROVIDE (_etext = .);
PROVIDE (etext = .);
.rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
.rodata1: { *(.rodata1) }
.eh_frame_hdr : { *(.eh_frame_hdr) }
.eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
.gcc_except_table : ONLY_IF_RO { *(.gcc_except_table
.gcc_except_table.*) }
/* Adjust the address for the data segment. We want to adjust up to
the same address within the page on the next page up. */
. = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) &
(CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT
(MAXPAGESIZE), CONSTANT (COMMONPAGESI
ZE));
/* Exception handling */
Any suggestions on how to fix this??
Thanx,
--WjW
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error in make buildkernel `
On Mon, Jun 10, 2013 at 02:04:59PM +0200, Willem Jan Withagen wrote:
> I'm trying to build a stable kernle on a freshly build 8.4-Stable i386
> system.
>
> And I get:
> MAKE=make sh /usr/srcs/src9/src/sys/conf/newvers.sh GENERIC
> /usr/local/bin/svnversion
> cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
> -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
> -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I.
> -I/usr/srcs/src9/src/sys -I/usr/srcs/src9/src/sys/contrib/altq -D_KERNEL
> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
> -finline-limit=8000 --param inline-unit-growth=100 --param
> large-function-growth=1000 -mno-align-long-strings
> -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float
> -ffreestanding -fstack-protector -Werror vers.c
> ctfconvert -L VERSION -g vers.o
> linking kernel.debug
> ld:/usr/srcs/src9/src/sys/conf/ldscript.i386:66: syntax error
> *** Error code 1
>
> Stop in /usr/obj/usr/srcs/src9/src/sys/GENERIC.
> *** Error code 1
>
> Stop in /usr/srcs/src9/src.
> *** Error code 1
>
> Line 66 is: .eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
> The piece of "code" around line 66 looks like:
>
> PROVIDE (__etext = .);
> PROVIDE (_etext = .);
> PROVIDE (etext = .);
> .rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
> .rodata1: { *(.rodata1) }
> .eh_frame_hdr : { *(.eh_frame_hdr) }
> .eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
> .gcc_except_table : ONLY_IF_RO { *(.gcc_except_table
> .gcc_except_table.*) }
> /* Adjust the address for the data segment. We want to adjust up to
> the same address within the page on the next page up. */
> . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) &
> (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT
> (MAXPAGESIZE), CONSTANT (COMMONPAGESI
> ZE));
> /* Exception handling */
>
> Any suggestions on how to fix this??
I can't help with the actual syntax error, but from the path names
involved here, it looks like you:
1) are using an alternate location for src (/usr/srcs not /usr/src),
2) are trying to build FreeBSD 9.x on an 8.4-STABLE box
(/usr/obj/usr/srcs/src9)
Is that correct? You might want to provide /etc/make.conf and
/etc/src.conf from this system or other details of the "build framework"
you might be using. That might help/pertain to the situation.
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error in make buildkernel `
Le 10/06/2013 14:14, Jeremy Chadwick a écrit :
> On Mon, Jun 10, 2013 at 02:04:59PM +0200, Willem Jan Withagen wrote:
>> I'm trying to build a stable kernle on a freshly build 8.4-Stable i386
>> system.
>>
>> And I get:
>> MAKE=make sh /usr/srcs/src9/src/sys/conf/newvers.sh GENERIC
>> /usr/local/bin/svnversion
>> cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
>> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
>> -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
>> -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I.
>> -I/usr/srcs/src9/src/sys -I/usr/srcs/src9/src/sys/contrib/altq -D_KERNEL
>> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
>> -finline-limit=8000 --param inline-unit-growth=100 --param
>> large-function-growth=1000 -mno-align-long-strings
>> -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float
>> -ffreestanding -fstack-protector -Werror vers.c
>> ctfconvert -L VERSION -g vers.o
>> linking kernel.debug
>> ld:/usr/srcs/src9/src/sys/conf/ldscript.i386:66: syntax error
>> *** Error code 1
>>
>> Stop in /usr/obj/usr/srcs/src9/src/sys/GENERIC.
>> *** Error code 1
>>
>> Stop in /usr/srcs/src9/src.
>> *** Error code 1
>>
>> Line 66 is: .eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
>> The piece of "code" around line 66 looks like:
>>
>> PROVIDE (__etext = .);
>> PROVIDE (_etext = .);
>> PROVIDE (etext = .);
>> .rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
>> .rodata1: { *(.rodata1) }
>> .eh_frame_hdr : { *(.eh_frame_hdr) }
>> .eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
>> .gcc_except_table : ONLY_IF_RO { *(.gcc_except_table
>> .gcc_except_table.*) }
>> /* Adjust the address for the data segment. We want to adjust up to
>> the same address within the page on the next page up. */
>> . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) &
>> (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT
>> (MAXPAGESIZE), CONSTANT (COMMONPAGESI
>> ZE));
>> /* Exception handling */
>>
>> Any suggestions on how to fix this??
>
> I can't help with the actual syntax error, but from the path names
> involved here, it looks like you:
>
> 1) are using an alternate location for src (/usr/srcs not /usr/src),
For that we can do:
SRC_BASE=/usr/srcs/src9/src make
But it shouldn't be a problem to build base system, it should occur only
with ports.
--
Florent Peterschmitt | Please:
flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail
+33 (0)6 64 33 97 92 | * PDF for documents
http://florent.peterschmitt.fr | Thank you :)
signature.asc
Description: OpenPGP digital signature
Re: Error in make buildkernel `
On 2013-06-10 14:14, Jeremy Chadwick wrote:
> On Mon, Jun 10, 2013 at 02:04:59PM +0200, Willem Jan Withagen wrote:
>> I'm trying to build a stable kernle on a freshly build 8.4-Stable i386
>> system.
>>
>> And I get:
>> MAKE=make sh /usr/srcs/src9/src/sys/conf/newvers.sh GENERIC
>> /usr/local/bin/svnversion
>> cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
>> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
>> -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
>> -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I.
>> -I/usr/srcs/src9/src/sys -I/usr/srcs/src9/src/sys/contrib/altq -D_KERNEL
>> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
>> -finline-limit=8000 --param inline-unit-growth=100 --param
>> large-function-growth=1000 -mno-align-long-strings
>> -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float
>> -ffreestanding -fstack-protector -Werror vers.c
>> ctfconvert -L VERSION -g vers.o
>> linking kernel.debug
>> ld:/usr/srcs/src9/src/sys/conf/ldscript.i386:66: syntax error
>> *** Error code 1
>>
>> Stop in /usr/obj/usr/srcs/src9/src/sys/GENERIC.
>> *** Error code 1
>>
>> Stop in /usr/srcs/src9/src.
>> *** Error code 1
>>
>> Line 66 is: .eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
>> The piece of "code" around line 66 looks like:
>>
>> PROVIDE (__etext = .);
>> PROVIDE (_etext = .);
>> PROVIDE (etext = .);
>> .rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
>> .rodata1: { *(.rodata1) }
>> .eh_frame_hdr : { *(.eh_frame_hdr) }
>> .eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
>> .gcc_except_table : ONLY_IF_RO { *(.gcc_except_table
>> .gcc_except_table.*) }
>> /* Adjust the address for the data segment. We want to adjust up to
>> the same address within the page on the next page up. */
>> . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) &
>> (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT
>> (MAXPAGESIZE), CONSTANT (COMMONPAGESI
>> ZE));
>> /* Exception handling */
>>
>> Any suggestions on how to fix this??
>
> I can't help with the actual syntax error, but from the path names
> involved here, it looks like you:
>
> 1) are using an alternate location for src (/usr/srcs not /usr/src),
Correct.
That's where I store all revisions on my file-server and then build to a
local /usr/obj.
Each system has a soft-link pointing to the place where it's sources are
stored.
> 2) are trying to build FreeBSD 9.x on an 8.4-STABLE box
> (/usr/obj/usr/srcs/src9)
>
> Is that correct? You might want to provide /etc/make.conf and
> /etc/src.conf from this system or other details of the "build framework"
> you might be using. That might help/pertain to the situation.
Good point. Did not think of those...
--WjW
make.conf:
# To build ppp with normal permissions
PPP_NOSUID= true
#
# To avoid building various parts of the base system:
NO_FORTRAN= true# do not build g77 and related libraries
NO_LPR= true# do not build lpr and related programs
NO_OBJC=true# do not build Objective C support
NO_GAMES=true# do not build games (games/ subdir)
NO_PROFILE= true# Avoid compiling profiled libraries
NO_UUCP= true# do not build uucp related programs
NO_SENDMAIL=true
#
COMPAT22= yes
COMPAT3X= yes
COMPAT4X= yes
COMPAT5X= yes
#
PRINTERDEVICE= ps
#
# The list of languages and encodings to build and install
#
DOC_LANG= en_US.ISO_8859-1
#
MODULES_OVERRIDE=splash geom ipfw ipdivert libalias acpi nfsserver
coretemp nfsclient nfscl aio
KERNCONF=RACK1
BATCH=yes
WITHOUT_X11=yes
# added by use.perl 2013-04-18 15:28:08
PERL_VERSION=5.16.2
src.conf:
# To avoid building various parts of the base system:
WITHOUT_FORTRAN = true# do not build g77 and related libraries
WITHOUT_LPR = true# do not build lpr and related programs
WITHOUT_OBJC= true# do not build Objective C support
WITHOUT_GAMES = true# do not build games (games/ subdir)
WITHOUT_PROFILE = true# Avoid compiling profiled libraries
WITHOUT_UUCP= true# do not build uucp related programs
WITHOUT_SENDMAIL= true
WITHOUT_X11 = true
WITHOUT_ATM = true
WITHOUT_AUDIT = true
WITHOUT_AUTHPF = true
WITHOUT_BLUETOOTH=true
WITHOUT_GPIB= true
WITHOUT_I4B = true
WITHOUT_IPFILTER= true
WITHOUT_IPX = true
WITHOUT_NCP = true
WITHOUT_PF = true
WITHOUT_RESUE = true
WITHOUT_CALENDAR = true
WITH_IDEA = true
WITHOUT_KERBEROS = true
WITHOUT_MAILWRAPPER = true
# without NIS this jdk does not compile.
# WITHOUT_NIS = true
WITHOUT_RCMDS = true
WITHOUT_RESCUE = true
WITHOUT_BIND= true
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error in make buildkernel `
On 2013-06-10 14:19, Florent Peterschmitt wrote:
> Le 10/06/2013 14:14, Jeremy Chadwick a écrit :
>> On Mon, Jun 10, 2013 at 02:04:59PM +0200, Willem Jan Withagen wrote:
>>> I'm trying to build a stable kernle on a freshly build 8.4-Stable i386
>>> system.
>>>
>>> And I get:
>>> MAKE=make sh /usr/srcs/src9/src/sys/conf/newvers.sh GENERIC
>>> /usr/local/bin/svnversion
>>> cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
>>> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
>>> -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
>>> -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I.
>>> -I/usr/srcs/src9/src/sys -I/usr/srcs/src9/src/sys/contrib/altq -D_KERNEL
>>> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
>>> -finline-limit=8000 --param inline-unit-growth=100 --param
>>> large-function-growth=1000 -mno-align-long-strings
>>> -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float
>>> -ffreestanding -fstack-protector -Werror vers.c
>>> ctfconvert -L VERSION -g vers.o
>>> linking kernel.debug
>>> ld:/usr/srcs/src9/src/sys/conf/ldscript.i386:66: syntax error
>>> *** Error code 1
>>>
>>> Stop in /usr/obj/usr/srcs/src9/src/sys/GENERIC.
>>> *** Error code 1
>>>
>>> Stop in /usr/srcs/src9/src.
>>> *** Error code 1
>>>
>>> Line 66 is: .eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
>>> The piece of "code" around line 66 looks like:
>>>
>>> PROVIDE (__etext = .);
>>> PROVIDE (_etext = .);
>>> PROVIDE (etext = .);
>>> .rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
>>> .rodata1: { *(.rodata1) }
>>> .eh_frame_hdr : { *(.eh_frame_hdr) }
>>> .eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
>>> .gcc_except_table : ONLY_IF_RO { *(.gcc_except_table
>>> .gcc_except_table.*) }
>>> /* Adjust the address for the data segment. We want to adjust up to
>>> the same address within the page on the next page up. */
>>> . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) &
>>> (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT
>>> (MAXPAGESIZE), CONSTANT (COMMONPAGESI
>>> ZE));
>>> /* Exception handling */
>>>
>>> Any suggestions on how to fix this??
>>
>> I can't help with the actual syntax error, but from the path names
>> involved here, it looks like you:
>>
>> 1) are using an alternate location for src (/usr/srcs not /usr/src),
>
> For that we can do:
>
> SRC_BASE=/usr/srcs/src9/src make
>
> But it shouldn't be a problem to build base system, it should occur only
> with ports.
Even though it might not have been supported, but it has worked in this
way for longer than I can remember
Will give it a shot with SRC_BASE.
--WjW
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ACPI Warning, then hang
I'm getting the following warning, and then the system locks: ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29, should be 0x48 Here's a pic: http://db.tt/O6dxONzI System is on a SuperMicro C7X58 motherboard that I just upgraded to BIOS 2.0a, which I would like to stay on if possible. I tried adjusting all the ACPI related BIOS settings without success. Bryce ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ACPI Warning, then hang
On Mon, Jun 10, 2013 at 09:18:14AM -0500, Bryce Edwards wrote: > I'm getting the following warning, and then the system locks: > > ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29, > should be 0x48 > > Here's a pic: http://db.tt/O6dxONzI > > System is on a SuperMicro C7X58 motherboard that I just upgraded to > BIOS 2.0a, which I would like to stay on if possible. I tried > adjusting all the ACPI related BIOS settings without success. The message in question refers to hard-coded data in one of the many ACPI tables (see acpidump(8) for the list -- there are many). ACPI tables are stored within the BIOS -- the motherboard/BIOS vendor has full control over all of them and is fully 100% responsible for their content. It looks to me like they severely botched their BIOS, or somehow it got flashed wrong. You need to contact Supermicro Technical Support and tell them of the problem. They need to either fix their BIOS, or help figure out what's become corrupted. You can point them to this thread if you'd like. I should note that the corruption/issue is major enough that you are missing very key/important lines from your dmesg (after "avail memory" but before "kdbX at kdbmuxX", which come from pure reliance upon ACPI. Lines such as: Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard In the meantime, you can try booting without ACPI support (there should be a boot-up menu option for that) and pray that works. If it doesn't, then your workaround is to roll back to an older BIOS version and/or put pressure on Supermicro. You will find their Technical Support folks are quite helpful/responsive to technical issues. Good luck and keep us posted on what transpires. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Reproducable Infiniband panic
On Monday, June 10, 2013 8:04:12 am Julian Stecklina wrote:
> On 06/07/2013 06:06 PM, John Baldwin wrote:
> > On Friday, June 07, 2013 5:07:34 am Julian Stecklina wrote:
> >> On 06/06/2013 08:57 PM, John Baldwin wrote:
> >>> On Thursday, June 06, 2013 9:54:35 am Andriy Gapon wrote:
> >> [...]
> The problem seems to be in incorrect interaction between devfs_close_f
> > and
> linux_file_dtor. The latter expects curthread->td_fpop to have a valid
> > reasonable
> value. But the former sets curthread->td_fpop to fp only around
> > vnops.fo_close()
> call and then restores it back to some (what?) previous value before
> > calling
> devfs_fpdrop->devfs_destroy_cdevpriv. In this case the previous value
> is
> > NULL.
> >>>
> >>> It is normally NULL in this case. Why does linux_file_dtor even look at
> >>> td_fpop?
> >>>
> >>> Ah. I think it should not do that and make the data it uses in the dtor
> > more
> >>> self-contained:
> [...]
>
> Seems to fix my panic. Thanks!
Can you please retest this updated version? I had thought that I didn't need
a reference count on the vnode, but devfs drops its reference count before the
cdevpriv destructor is called.
Index: sys/ofed/include/linux/fs.h
===
--- sys/ofed/include/linux/fs.h (revision 251604)
+++ sys/ofed/include/linux/fs.h (working copy)
@@ -73,6 +73,7 @@
struct dentry f_dentry_store;
struct selinfo f_selinfo;
struct sigio*f_sigio;
+ struct vnode*f_vnode;
};
#definefilelinux_file
Index: sys/ofed/include/linux/linux_compat.c
===
--- sys/ofed/include/linux/linux_compat.c (revision 251604)
+++ sys/ofed/include/linux/linux_compat.c (working copy)
@@ -212,7 +212,8 @@
struct linux_file *filp;
filp = cdp;
- filp->f_op->release(curthread->td_fpop->f_vnode, filp);
+ filp->f_op->release(filp->f_vnode, filp);
+ vdrop(filp->f_vnode);
kfree(filp);
}
@@ -232,6 +233,8 @@
filp->f_dentry = &filp->f_dentry_store;
filp->f_op = ldev->ops;
filp->f_flags = file->f_flag;
+ vhold(file->f_vnode);
+ filp->f_vnode = file->f_vnode;
if (filp->f_op->open) {
error = -filp->f_op->open(file->f_vnode, filp);
if (error) {
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ACPI Warning, then hang
On Monday, June 10, 2013 10:35:07 am Jeremy Chadwick wrote: > On Mon, Jun 10, 2013 at 09:18:14AM -0500, Bryce Edwards wrote: > > I'm getting the following warning, and then the system locks: > > > > ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29, > > should be 0x48 > > > > Here's a pic: http://db.tt/O6dxONzI > > > > System is on a SuperMicro C7X58 motherboard that I just upgraded to > > BIOS 2.0a, which I would like to stay on if possible. I tried > > adjusting all the ACPI related BIOS settings without success. > > The message in question refers to hard-coded data in one of the many > ACPI tables (see acpidump(8) for the list -- there are many). ACPI > tables are stored within the BIOS -- the motherboard/BIOS vendor has > full control over all of them and is fully 100% responsible for their > content. > > It looks to me like they severely botched their BIOS, or somehow it got > flashed wrong. > > You need to contact Supermicro Technical Support and tell them of the > problem. They need to either fix their BIOS, or help figure out what's > become corrupted. You can point them to this thread if you'd like. > > I should note that the corruption/issue is major enough that you are > missing very key/important lines from your dmesg (after "avail memory" > but before "kdbX at kdbmuxX", which come from pure reliance upon ACPI. > Lines such as: > > Event timer "LAPIC" quality 400 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > > In the meantime, you can try booting without ACPI support (there should > be a boot-up menu option for that) and pray that works. If it doesn't, > then your workaround is to roll back to an older BIOS version and/or put > pressure on Supermicro. You will find their Technical Support folks are > quite helpful/responsive to technical issues. > > Good luck and keep us posted on what transpires. Actually, that message is mostly harmless. All sorts of vendors ship tables with busted checksums that are in fact fine. :( However, the table name looks very odd which is more worrying. Booting without ACPI enabled would be a good first step. Trying a verbose boot to capture the last message before the hang would also be useful. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ACPI Warning, then hang
On Mon, Jun 10, 2013 at 11:19 AM, John Baldwin wrote: > On Monday, June 10, 2013 10:35:07 am Jeremy Chadwick wrote: >> On Mon, Jun 10, 2013 at 09:18:14AM -0500, Bryce Edwards wrote: >> > I'm getting the following warning, and then the system locks: >> > >> > ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29, >> > should be 0x48 >> > >> > Here's a pic: http://db.tt/O6dxONzI >> > >> > System is on a SuperMicro C7X58 motherboard that I just upgraded to >> > BIOS 2.0a, which I would like to stay on if possible. I tried >> > adjusting all the ACPI related BIOS settings without success. >> >> The message in question refers to hard-coded data in one of the many >> ACPI tables (see acpidump(8) for the list -- there are many). ACPI >> tables are stored within the BIOS -- the motherboard/BIOS vendor has >> full control over all of them and is fully 100% responsible for their >> content. >> >> It looks to me like they severely botched their BIOS, or somehow it got >> flashed wrong. >> >> You need to contact Supermicro Technical Support and tell them of the >> problem. They need to either fix their BIOS, or help figure out what's >> become corrupted. You can point them to this thread if you'd like. >> >> I should note that the corruption/issue is major enough that you are >> missing very key/important lines from your dmesg (after "avail memory" >> but before "kdbX at kdbmuxX", which come from pure reliance upon ACPI. >> Lines such as: >> >> Event timer "LAPIC" quality 400 >> ACPI APIC Table: >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> FreeBSD/SMP: 1 package(s) x 4 core(s) >> cpu0 (BSP): APIC ID: 0 >> cpu1 (AP): APIC ID: 1 >> cpu2 (AP): APIC ID: 2 >> cpu3 (AP): APIC ID: 3 >> ioapic0 irqs 0-23 on motherboard >> ioapic1 irqs 24-47 on motherboard >> >> In the meantime, you can try booting without ACPI support (there should >> be a boot-up menu option for that) and pray that works. If it doesn't, >> then your workaround is to roll back to an older BIOS version and/or put >> pressure on Supermicro. You will find their Technical Support folks are >> quite helpful/responsive to technical issues. >> >> Good luck and keep us posted on what transpires. > > Actually, that message is mostly harmless. All sorts of vendors ship > tables with busted checksums that are in fact fine. :( However, the table > name looks very odd which is more worrying. Booting without ACPI enabled > would be a good first step. Trying a verbose boot to capture the last > message before the hang would also be useful. > > -- > John Baldwin Booting without ACPI did not work for me, although I might be able to hack away at lots of BIOS setting to make it work. It didn't assign IRQ's to things like the storage controller, etc. soI thought it was probably not worth the effort. I did contact SuperMicro support as well, so we'll see what they have to say. I'll get a verbose boot posted up in a bit. Bryce ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error in make buildkernel `
On Jun 10, 2013, at 14:04, Willem Jan Withagen wrote: > I'm trying to build a stable kernle on a freshly build 8.4-Stable i386 > system. > > And I get: > MAKE=make sh /usr/srcs/src9/src/sys/conf/newvers.sh GENERIC > /usr/local/bin/svnversion > cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions > -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. > -I/usr/srcs/src9/src/sys -I/usr/srcs/src9/src/sys/contrib/altq -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common > -finline-limit=8000 --param inline-unit-growth=100 --param > large-function-growth=1000 -mno-align-long-strings > -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float > -ffreestanding -fstack-protector -Werror vers.c > ctfconvert -L VERSION -g vers.o > linking kernel.debug > ld:/usr/srcs/src9/src/sys/conf/ldscript.i386:66: syntax error > *** Error code 1 You must run "make kernel-toolchain" first. Alternatively, run "make buildworld", but that is more work. -Dimitry ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error in make buildkernel `
Op 10 jun. 2013 om 19:27 heeft Dimitry Andric het volgende geschreven: > On Jun 10, 2013, at 14:04, Willem Jan Withagen wrote: >> I'm trying to build a stable kernle on a freshly build 8.4-Stable i386 >> system. >> >> And I get: >> MAKE=make sh /usr/srcs/src9/src/sys/conf/newvers.sh GENERIC >> /usr/local/bin/svnversion >> cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs >> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline >> -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions >> -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. >> -I/usr/srcs/src9/src/sys -I/usr/srcs/src9/src/sys/contrib/altq -D_KERNEL >> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common >> -finline-limit=8000 --param inline-unit-growth=100 --param >> large-function-growth=1000 -mno-align-long-strings >> -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float >> -ffreestanding -fstack-protector -Werror vers.c >> ctfconvert -L VERSION -g vers.o >> linking kernel.debug >> ld:/usr/srcs/src9/src/sys/conf/ldscript.i386:66: syntax error >> *** Error code 1 > > You must run "make kernel-toolchain" first. Alternatively, run "make > buildworld", but that is more work. I usually run buildworld from crontab first, and then builkernel. But things might have gone wrong. Thank for the tip. --WjW ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error in make buildkernel `
On Jun 10, 2013, at 20:39, Willem Jan Withagen wrote: > Op 10 jun. 2013 om 19:27 heeft Dimitry Andric het volgende > geschreven: >> On Jun 10, 2013, at 14:04, Willem Jan Withagen wrote: >>> I'm trying to build a stable kernle on a freshly build 8.4-Stable i386 >>> system. >>> >>> And I get: >>> MAKE=make sh /usr/srcs/src9/src/sys/conf/newvers.sh GENERIC >>> /usr/local/bin/svnversion >>> cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs >>> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline >>> -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions >>> -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. >>> -I/usr/srcs/src9/src/sys -I/usr/srcs/src9/src/sys/contrib/altq -D_KERNEL >>> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common >>> -finline-limit=8000 --param inline-unit-growth=100 --param >>> large-function-growth=1000 -mno-align-long-strings >>> -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float >>> -ffreestanding -fstack-protector -Werror vers.c >>> ctfconvert -L VERSION -g vers.o >>> linking kernel.debug >>> ld:/usr/srcs/src9/src/sys/conf/ldscript.i386:66: syntax error >>> *** Error code 1 >> >> You must run "make kernel-toolchain" first. Alternatively, run "make >> buildworld", but that is more work. > > I usually run buildworld from crontab first, and then builkernel. > But things might have gone wrong. To explain this a bit more: FreeBSD 9.x and later have binutils 2.17.50, FreeBSD 8.x has binutils 2.15. The kernels for 9.x and later use a bit of linker script syntax that is not understood by the older ld in 8.x, so you cannot link the 9.x kernel with /usr/bin/ld on 8.x. Therefore, you have to build the newer linker as part of buildworld, or by using the kernel-toolchain target. -Dimitry ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Reproducable Infiniband panic
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/10/2013 06:15 PM, John Baldwin wrote: > Can you please retest this updated version? I had thought that I > didn't need a reference count on the vnode, but devfs drops its > reference count before the cdevpriv destructor is called. Works for me. Julian -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG2QhMACgkQ2EtjUdW3H9nLnQCfcX0+h5PiypoIFGewe40uOh0c Jh4AoLhx1eORFAZB3RPsiL/tT6yXlqbF =9I3M -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error in make buildkernel `
On 10-6-2013 21:57, Dimitry Andric wrote: On Jun 10, 2013, at 20:39, Willem Jan Withagen wrote: Op 10 jun. 2013 om 19:27 heeft Dimitry Andric het volgende geschreven: On Jun 10, 2013, at 14:04, Willem Jan Withagen wrote: I'm trying to build a stable kernle on a freshly build 8.4-Stable i386 system. And I get: MAKE=make sh /usr/srcs/src9/src/sys/conf/newvers.sh GENERIC /usr/local/bin/svnversion cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/srcs/src9/src/sys -I/usr/srcs/src9/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror vers.c ctfconvert -L VERSION -g vers.o linking kernel.debug ld:/usr/srcs/src9/src/sys/conf/ldscript.i386:66: syntax error *** Error code 1 You must run "make kernel-toolchain" first. Alternatively, run "make buildworld", but that is more work. I usually run buildworld from crontab first, and then builkernel. But things might have gone wrong. To explain this a bit more: FreeBSD 9.x and later have binutils 2.17.50, FreeBSD 8.x has binutils 2.15. The kernels for 9.x and later use a bit of linker script syntax that is not understood by the older ld in 8.x, so you cannot link the 9.x kernel with /usr/bin/ld on 8.x. Therefore, you have to build the newer linker as part of buildworld, or by using the kernel-toolchain target. Ah, oke, So there could be a very small chance that the 8.x ld is used? But it did the job. Thanx, --WjW ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ACPI Warning, then hang
Verbose boot: https://www.dropbox.com/s/obm8rtavro68ea8/acpi-verbose.jpg On Mon, Jun 10, 2013 at 11:27 AM, Bryce Edwards wrote: > On Mon, Jun 10, 2013 at 11:19 AM, John Baldwin wrote: >> On Monday, June 10, 2013 10:35:07 am Jeremy Chadwick wrote: >>> On Mon, Jun 10, 2013 at 09:18:14AM -0500, Bryce Edwards wrote: >>> > I'm getting the following warning, and then the system locks: >>> > >>> > ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29, >>> > should be 0x48 >>> > >>> > Here's a pic: http://db.tt/O6dxONzI >>> > >>> > System is on a SuperMicro C7X58 motherboard that I just upgraded to >>> > BIOS 2.0a, which I would like to stay on if possible. I tried >>> > adjusting all the ACPI related BIOS settings without success. >>> >>> The message in question refers to hard-coded data in one of the many >>> ACPI tables (see acpidump(8) for the list -- there are many). ACPI >>> tables are stored within the BIOS -- the motherboard/BIOS vendor has >>> full control over all of them and is fully 100% responsible for their >>> content. >>> >>> It looks to me like they severely botched their BIOS, or somehow it got >>> flashed wrong. >>> >>> You need to contact Supermicro Technical Support and tell them of the >>> problem. They need to either fix their BIOS, or help figure out what's >>> become corrupted. You can point them to this thread if you'd like. >>> >>> I should note that the corruption/issue is major enough that you are >>> missing very key/important lines from your dmesg (after "avail memory" >>> but before "kdbX at kdbmuxX", which come from pure reliance upon ACPI. >>> Lines such as: >>> >>> Event timer "LAPIC" quality 400 >>> ACPI APIC Table: >>> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >>> FreeBSD/SMP: 1 package(s) x 4 core(s) >>> cpu0 (BSP): APIC ID: 0 >>> cpu1 (AP): APIC ID: 1 >>> cpu2 (AP): APIC ID: 2 >>> cpu3 (AP): APIC ID: 3 >>> ioapic0 irqs 0-23 on motherboard >>> ioapic1 irqs 24-47 on motherboard >>> >>> In the meantime, you can try booting without ACPI support (there should >>> be a boot-up menu option for that) and pray that works. If it doesn't, >>> then your workaround is to roll back to an older BIOS version and/or put >>> pressure on Supermicro. You will find their Technical Support folks are >>> quite helpful/responsive to technical issues. >>> >>> Good luck and keep us posted on what transpires. >> >> Actually, that message is mostly harmless. All sorts of vendors ship >> tables with busted checksums that are in fact fine. :( However, the table >> name looks very odd which is more worrying. Booting without ACPI enabled >> would be a good first step. Trying a verbose boot to capture the last >> message before the hang would also be useful. >> >> -- >> John Baldwin > > Booting without ACPI did not work for me, although I might be able to > hack away at lots of BIOS setting to make it work. It didn't assign > IRQ's to things like the storage controller, etc. soI thought it was > probably not worth the effort. > > I did contact SuperMicro support as well, so we'll see what they have to say. > > I'll get a verbose boot posted up in a bit. > > Bryce ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ACPI Warning, then hang
On Mon, Jun 10, 2013 at 09:18:47PM -0500, Bryce Edwards wrote:
> Verbose boot:
>
> https://www.dropbox.com/s/obm8rtavro68ea8/acpi-verbose.jpg
>
>
> On Mon, Jun 10, 2013 at 11:27 AM, Bryce Edwards wrote:
> > On Mon, Jun 10, 2013 at 11:19 AM, John Baldwin wrote:
> >> On Monday, June 10, 2013 10:35:07 am Jeremy Chadwick wrote:
> >>> On Mon, Jun 10, 2013 at 09:18:14AM -0500, Bryce Edwards wrote:
> >>> > I'm getting the following warning, and then the system locks:
> >>> >
> >>> > ACPI Warning: Incorrect checksum in table [(bunch of spaces)] - 0x29,
> >>> > should be 0x48
> >>> >
> >>> > Here's a pic: http://db.tt/O6dxONzI
> >>> >
> >>> > System is on a SuperMicro C7X58 motherboard that I just upgraded to
> >>> > BIOS 2.0a, which I would like to stay on if possible. I tried
> >>> > adjusting all the ACPI related BIOS settings without success.
> >>>
> >>> The message in question refers to hard-coded data in one of the many
> >>> ACPI tables (see acpidump(8) for the list -- there are many). ACPI
> >>> tables are stored within the BIOS -- the motherboard/BIOS vendor has
> >>> full control over all of them and is fully 100% responsible for their
> >>> content.
> >>>
> >>> It looks to me like they severely botched their BIOS, or somehow it got
> >>> flashed wrong.
> >>>
> >>> You need to contact Supermicro Technical Support and tell them of the
> >>> problem. They need to either fix their BIOS, or help figure out what's
> >>> become corrupted. You can point them to this thread if you'd like.
> >>>
> >>> I should note that the corruption/issue is major enough that you are
> >>> missing very key/important lines from your dmesg (after "avail memory"
> >>> but before "kdbX at kdbmuxX", which come from pure reliance upon ACPI.
> >>> Lines such as:
> >>>
> >>> Event timer "LAPIC" quality 400
> >>> ACPI APIC Table:
> >>> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
> >>> FreeBSD/SMP: 1 package(s) x 4 core(s)
> >>> cpu0 (BSP): APIC ID: 0
> >>> cpu1 (AP): APIC ID: 1
> >>> cpu2 (AP): APIC ID: 2
> >>> cpu3 (AP): APIC ID: 3
> >>> ioapic0 irqs 0-23 on motherboard
> >>> ioapic1 irqs 24-47 on motherboard
> >>>
> >>> In the meantime, you can try booting without ACPI support (there should
> >>> be a boot-up menu option for that) and pray that works. If it doesn't,
> >>> then your workaround is to roll back to an older BIOS version and/or put
> >>> pressure on Supermicro. You will find their Technical Support folks are
> >>> quite helpful/responsive to technical issues.
> >>>
> >>> Good luck and keep us posted on what transpires.
> >>
> >> Actually, that message is mostly harmless. All sorts of vendors ship
> >> tables with busted checksums that are in fact fine. :( However, the table
> >> name looks very odd which is more worrying. Booting without ACPI enabled
> >> would be a good first step. Trying a verbose boot to capture the last
> >> message before the hang would also be useful.
> >>
> >> --
> >> John Baldwin
> >
> > Booting without ACPI did not work for me, although I might be able to
> > hack away at lots of BIOS setting to make it work. It didn't assign
> > IRQ's to things like the storage controller, etc. soI thought it was
> > probably not worth the effort.
> >
> > I did contact SuperMicro support as well, so we'll see what they have to
> > say.
> >
> > I'll get a verbose boot posted up in a bit.
A screenshot of a verbose boot is insufficient; as I'm sure you noticed
there are pages upon pages of information before the lock-up/crash.
Those pages are what folks are interested in.
Because the system is hung, I doubt hitting Scroll Lock + using
PageUp/PageDown to go through the kernel message scrollback will work.
You're going to need a serial-based console (i.e. hook something up to
COM1 on the motherboard, and get a null modem cable to connect to
another system where you use a serial port/terminal emulator (ex. PuTTY
for Windows, etc.) that has a scrollback buffer which you can copy-paste
or save. Set your serial port for 9600 baud, 8 bits, no parity, and 1
stop bit (9600bps, 8N1). You'll need to have physical access to both
systems simultaneously.
At the VGA console, boot FreeBSD then escape to the loader prompt
("ok") and issue the following commands:
set boot_multicons="YES"
set boot_serial="YES"
set console="comconsole,vidconsole"
boot
You should begin seeing output on the serial port, and the system will
eventually hang/etc.. Then provide the captured output from the serial
port here. :-)
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
