nvidia (GPU) panic and BOOT_COMCONSOLE_SPEED not working anymore

From: Emanuel Strobl <Emanuel.strobl_at_gmx.net>
Date: Thu, 11 Aug 2005 21:25:35 +0200
Hello,

I'd like to report a panic I get when loading the nvidia (GPU) module with 
a kernel with debug features invariants and witness enabled.

The it seems that the BOOT_COMCONSOLE_SPEED doesn't work for the kernel 
anymore, the boot bits respect that setting, but kernel console is always 
9600. Also setting machdep.conspeed in /boot/loader.conf doesn't change 
the console speed.

Thanks,

-Harry

FreeBSD 6.0-BETA2 #2: Thu Aug 11 19:12:44 CEST 2005
    root_at_cale.flintsbach.schmalzbauer.de:/usr/obj/usr/src/sys/CALE
WARNING: WITNESS option enabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Celeron(TM) CPU                1100MHz (1095.94-MHz 686-class 
CPU)
  Origin = "GenuineIntel"  Id = 0x6b1  Stepping = 1
  
Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory  = 536608768 (511 MB)
avail memory = 511528960 (487 MB)
ACPI APIC Table: <D815EA EA81510A>
ioapic0: Changing APIC ID to 1
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ichwd module loaded
panic: spin lock rm.mutex_mtx not in order list
KDB: stack backtrace:
kdb_backtrace(c078e43b,c07fd420,c079205e,c1020c54,100) at 
kdb_backtrace+0x2e
panic(c079205e,c0bb37d6,c07919de,512,c1e4e6c0) at panic+0xb7
enroll(c0bb37d6,c07ce28c,c07919de,226,c1e4e6c0) at enroll+0x13a
witness_init(c1e4e6c0,24,c0b879f5,30,c1e6c800) at witness_init+0x17a
mtx_init(c1e4e6c0,c0bb37d6,0,5,c1e4e6c0) at mtx_init+0xe4
os_alloc_sema(c1dcc2e8,c1dcc000,c1020cec,c099d8ff,c0c9d4e8) at 
os_alloc_sema+0x4a
_nv001647rm(c1dcc2e8,4,0,c1020d24,c1dd89c0) at _nv001647rm+0xe
_nv007848rm(c0bb394f,c1dd89c0,c1020d28,c0b89d99,0) at _nv007848rm+0x6b
rm_init_rm(0,c1020d48,c05b90a6,c1d83d40,0) at rm_init_rm+0x11
nvidia_modevent(c1d83d40,0,0,c1d83d40,c0c9d4fc) at nvidia_modevent+0x19
driver_module_handler(c1d83d40,0,c0c9d4e8,0,0) at 
driver_module_handler+0x76
module_register_init(c0c9d4fc,101e000,101ec00,101e000,0) at 
module_register_init+0x81
mi_startup() at mi_startup+0xb5
begin() at begin+0x2c
KDB: enter: panic
[thread pid 0 tid 0 ]
Stopped at      kdb_enter+0x30: leave   
db> trace
Tracing pid 0 tid 0 td 0xc07fade0
kdb_enter(c078e264,c07fd420,c079205e,c1020c54,100) at kdb_enter+0x30
panic(c079205e,c0bb37d6,c07919de,512,c1e4e6c0) at panic+0xd5
enroll(c0bb37d6,c07ce28c,c07919de,226,c1e4e6c0) at enroll+0x13a
witness_init(c1e4e6c0,24,c0b879f5,30,c1e6c800) at witness_init+0x17a
mtx_init(c1e4e6c0,c0bb37d6,0,5,c1e4e6c0) at mtx_init+0xe4
os_alloc_sema(c1dcc2e8,c1dcc000,c1020cec,c099d8ff,c0c9d4e8) at 
os_alloc_sema+0x4a
_nv001647rm(c1dcc2e8,4,0,c1020d24,c1dd89c0) at _nv001647rm+0xe
_nv007848rm(c0bb394f,c1dd89c0,c1020d28,c0b89d99,0) at _nv007848rm+0x6b
rm_init_rm(0,c1020d48,c05b90a6,c1d83d40,0) at rm_init_rm+0x11
nvidia_modevent(c1d83d40,0,0,c1d83d40,c0c9d4fc) at nvidia_modevent+0x19
driver_module_handler(c1d83d40,0,c0c9d4e8,0,0) at 
driver_module_handler+0x76
module_register_init(c0c9d4fc,101e000,101ec00,101e000,0) at 
module_register_init+0x81
mi_startup() at mi_startup+0xb5
begin() at begin+0x2c
db> reset

Received on Thu Aug 11 2005 - 17:25:48 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:41 UTC