Couple of weird messages in logs, and crashing to debuggier.
After finally getting machine to stop crashing, I noticed these, no clue what they mean Any ideas acpi_cpu: CPU throttling enabled, 16 steps from 100% to 6.2% link_elf: symbol pfil_add_hook undefined I had to remove the following lines, they kept causing the machine to drop to the db prompt. #device vt #optionsXSERVER # support for X server on a vt console #optionsFAT_CURSOR # start with block cursor Below is the contents of my kernel config, if that will make any diff, I also get random drops to db with SMP turned on, does not seem to happen with SMP disabled. Btw, anyone know where I can find info on how to get some usefull info when the machine drops to the db prompt, all I can do is reset the machine. (I would like to be able to dump all the info to somewhere, sort of like in solaris where you can dump the data etc to the swap file) Jason KERNEL machine i386 cpu I586_CPU cpu I686_CPU ident GENERIC maxusers0 #To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints #Default places to look for devices. makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols #optionsIPSEC_ESP #optionsIPSEC_DEBUG #optionsGDB_REMOTE_CHAT options INET#InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories #optionsUFS_EXTATTR #optionsUFS_EXTATTR_AUTOSTART #optionsUFS_ACL #optionsGPL_MATH_EMULATE options NFSCLIENT #Network Filesystem Client options NFSSERVER #Network Filesystem Server options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS#Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options INCLUDE_CONFIG_FILE #optionsUSERCONFIG #boot -c editor #optionsVISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV# install a CDEV entry in /dev # Debugging for use in -current options DDB #Enable the kernel debugger # The following options were disabled for 5.0 DP1 to make a more # usable system for early adopters. options INVARIANTS #Enable calls of extra sanity checking options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS #optionsWITNESS #Enable mutex checks to detects deadlocks and cycles #optionsWITNESS_SKIPSPIN#Don't run witness on spinlocks for speed # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa device eisa device pci #optionsPCI_ENABLE_IO_MODES # Enable pci resources left off by a lazy BIOS # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 # At keyboard controller device atkbd # at keyboard device psm # psm mouse device vga # VGA screen # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 # Enable this for the pcvt (VT220 compatible) console driver #device vt #optionsXSERVER # support for X server on a vt console #optionsFAT_CURSOR # start with block cursor # Floating point support - do not disable. device npx # PCCARD (PCMCIA) support device card# pccard bus device pcic# PCMCIA bridge # Serial (COM) ports device sio
pam_unix.so error and lock order reversal
Hello, I have three issues. 1) When logging in, the following appears in messages: Apr 13 12:18:37 laptop login: in openpam_dispatch(): pam_unix.so: no pam_sm_open_session() Apr 13 12:18:38 laptop login: in openpam_dispatch(): pam_unix.so: no pam_sm_close_session() 2) When logged in as root, and su'd to a non-root user, I cannot ssh to a 4.5-STABLE machine.. It just hangs. But when logged in as non-root, it works fine. Is this somekind of security feature? :-) 3) lock order reversal when for instance doing a cvsup Apr 13 12:16:58 laptop kernel: lock order reversal Apr 13 12:16:58 laptop kernel: 1st 0xcc5928e4 KNOTE (UMA zone) @ /usr/src/sys/vm/uma_core.c:491 Apr 13 12:16:58 laptop kernel: 2nd 0xc082a724 PCPU KMAP ENTRY (UMA cpu) @ /usr/src/sys/vm/uma_core.c:1264 I'm running 5.0-CURRENT two hours old. Thanks! Best regards, Rasmus Skaarup To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pam_unix.so error and lock order reversal
Rasmus Skaarup wrote: 2) When logged in as root, and su'd to a non-root user, I cannot ssh to a 4.5-STABLE machine.. It just hangs. But when logged in as non-root, it works fine. Is this somekind of security feature? :-) Pretty much. The user it attempts to log you in as is still root, because that's still your identity, even if it's not your current credential. But your current credential does not have access to the files for the remote system which are necessary for your identity (~root/.ssh). Ideally, identity would be handled by a session manager, which was created at login time, which would maintain its priviledges to these resources. You might want to try using su - instead of su, in order to actually *become* the other person. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
plug aue ethernet goes to panic
Following are observed with 5-current kernel as of Apr/13/2002. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0189b4a stack pointer = 0x10:0xc03f5180 frame pointer = 0x10:0xc03f5180 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 12 panic: page fault Loading kernel is OK, it boots fine if my 'aue' ethernet is not plugged. When I plug aue to the PC, kernel panic with messages above. Also, kernel panics after usb0, uhub0 is attached (same reason). Does anybody have aue see this?, or I'm alone? -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: plug aue ethernet goes to panic
On 13-Apr-2002 Makoto Matsushita wrote: Following are observed with 5-current kernel as of Apr/13/2002. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code= supervisor read, page not present instruction pointer = 0x8:0xc0189b4a stack pointer = 0x10:0xc03f5180 frame pointer = 0x10:0xc03f5180 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 12 panic: page fault Loading kernel is OK, it boots fine if my 'aue' ethernet is not plugged. When I plug aue to the PC, kernel panic with messages above. Also, kernel panics after usb0, uhub0 is attached (same reason). Does anybody have aue see this?, or I'm alone? Can you get a backtrace in ddb? It looks like a null pointer dereference, and knowing where it happened would help. Finding the file and line of the instruction pointer using addr2line on kernel.debug would be helpful as well. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: plug aue ethernet goes to panic
On Sat, Apr 13, 2002 at 12:44:36PM -0400, John Baldwin wrote: Can you get a backtrace in ddb? It looks like a null pointer dereference, and knowing where it happened would help. Finding the file and line of the instruction pointer using addr2line on kernel.debug would be helpful as well. It *is* a null pointer deref. Joe and I looked at this problem, and it seems a function called device_get_ivars() isn't doing its job in sys/dev/usb/usb_port.h. So the variable is getting filled with a NULL pointer for the iface element and is later deref'd. That's the limit of my debugging, and Joe is looking into the problem actively. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum problems
On Fri, Apr 12, 2002 at 05:46:29PM -0500, Patrick Hartling wrote: I suffered a system crash earlier today running -current from April 10. I have a Vinum volume set up as a mirror, and during the reboot, I had to fsck it. Everything seemed normal (at least that's what I thought), but now my volume cannot be mounted. The output from 'vinum list' is as follows: 2 drives: D a State: up /dev/da3s1e A: 0/12288 MB (0%) D b State: up /dev/da4s1e A: 0/12288 MB (0%) 1 volumes: V mirrorState: down Plexes: 2 Size: 11 GB 2 plexes: P mirror.p0 C State: faulty Subdisks: 1 Size: 11 GB P mirror.p1 C State: faulty Subdisks: 1 Size: 11 GB 2 subdisks: S mirror.p0.s0 State: crashed D: aSize: 11 GB S mirror.p1.s0 State: crashed D: bSize: 11 GB The fact that it says the drives have 0% used greatly concerns me. Before I delve into this any further, is that a sign that everything I had is just gone? Or is there some hope of recovery? There is nothing in /var/log/vinum_hitsory or /var/log/messages that gives me any insight into what went wrong. You have *both* plexes faulty which means that you either have waited too long running with only one disk left or that both failed a once. For the second point can be channel or power supply issues if they share a single resource in common. You will find it out by reading your log files. Of course you should fix the failure reason before doing anything else. I have made a bad expirience once in that if you revive one plex now you will get zeros written because there is no reference plex left. Greg: It's long ago but I forgot to tell you. Do you remember anything about such a bug got fixed? The shure way is to store the vinum printconfig output and then remove both plexes. finaly reconfigure them both beginning using the values from printconfig and start with the drive which run at last, because it has the most recent data. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
swi_net: unregistered isr number: 18
cvsup and make world sequence from this morning (0841 PDT) yields the following warning at boot swi_net: unregistered isr number: 18. System appears to be running fine. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with rl
Elric of Melnibone wrote: When you say not installed you mean not getting an IP address or not being active on your net? In case 2 check your ifconfig arguments and make sure that the media type is specified. I also had a problem like this with an rl card in -current. George -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of John Angelmo Sent: Friday, April 12, 2002 8:32 PM To: [EMAIL PROTECTED] Subject: Problem with rl Hello I just installed FreeBSD 5.0-DP1 and for some reason my rl (ethernet device rl) card is detected but not installed, is this a known problem? perhaps theres something missing in device.hints? I'll give it a try to paste info from my dmesg but it's hard to write down with pencil/paper ;) /John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message The errormessage I get is: rl0: RealTek 8139 10/100 Irq 5 at device 2.0 pci 1 Couldn't map ports/memory device_probe_and_attatch( rl0 attatch retuned 6) /John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: plug aue ethernet goes to panic
On 13-Apr-2002 Will Andrews wrote: On Sat, Apr 13, 2002 at 12:44:36PM -0400, John Baldwin wrote: Can you get a backtrace in ddb? It looks like a null pointer dereference, and knowing where it happened would help. Finding the file and line of the instruction pointer using addr2line on kernel.debug would be helpful as well. It *is* a null pointer deref. Joe and I looked at this problem, and it seems a function called device_get_ivars() isn't doing its job in sys/dev/usb/usb_port.h. So the variable is getting filled with a NULL pointer for the iface element and is later deref'd. That's the limit of my debugging, and Joe is looking into the problem actively. Well, if device_get_ivars() is returning a NULL pointer, then it probably means its parent bus device isn't setting up the ivars for the child device properly. As far as I understand, you can think of ivars as being per-device variables or state often used by a parent bus to set bus-specific information for a child device. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Unable to start bochs
I'm trying to run bochs without success. I'd like to know if is a -CURRENT or -PORTS issue. I have an Asus P2B-DS with dual pIII/500. Is crash related? # bochs [...] Event type: PANIC Device: [APIC0] Message: [APIC0] failed assertion irr[vector] == 1 at apic.cc:573 Riccardo. dmesg.gz Description: dmesg.gz
DP 1 hates my ACPI timers
grep -i acpi /var/run/dmesg.boot Preloaded elf module /boot/kernel/acpi.ko at 0xc06021fc. acpi0: ASUS P2B on motherboard acpi0: power button is handled as a fixed feature programming model. ACPI timer looks BAD min = 1, max = 5, width = 5 ACPI timer looks BAD min = 2, max = 16776739, width = 16776738 ACPI timer looks BAD min = 2, max = 5, width = 4 ACPI timer looks BAD min = 2, max = 6, width = 5 ACPI timer looks BAD min = 1, max = 16777214, width = 16777214 ACPI timer looks BAD min = 2, max = 6, width = 5 ACPI timer looks BAD min = 2, max = 16777214, width = 16777213 ACPI timer looks BAD min = 1, max = 5, width = 5 ACPI timer looks BAD min = 1, max = 6, width = 6 ACPI timer looks BAD min = 2, max = 16777211, width = 16777210 Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_pcib0: Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: PCI bus on acpi_pcib0 fdc0: enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 irq 6 on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio1 port 0x2f8-0x2ff irq 3 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
PAM error messages
I'm seeing this a lot on a recent 4.5-STABLE to -current upgrade, is this a problem or something I did wrong? dwcjr login: in openpam_dispatch(): pam_unix.so: no pam_sm_close_session() dwcjr login: in openpam_dispatch(): pam_unix.so: no pam_sm_open_session() -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
-current breakage
I'm getting this on a recent machine that has been upgraded from 4.5 to a -current today o over.o text.o script.o mark.o other.o delim.o sqrt.o pile.o special.o /usr/obj /usr/src/i386/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../src/libs/libgro ff/libgroff.a make: don't know how to make neqn. Stop *** Error code 2 I'm not getting this on a machine that's been running -current for a while. I was able to do one buildworld from 4.5-STABLE to -current, but after that I keep getting this? Let me know if anyone else has seen this. About 2 hours after I started seeing this, I removed /usr/src and cvsup'd and I still get it. Any ideas? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ATA errors on recent -current
I updated to -current today and am now getting these errors ad0: READ command timeout tag=1 serv=1 - resetting ata0: resetting devices .. ad0: invalidating queued requests done -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
