Re: problems with aureal soundcard: kernel fault when playing mp3s
"Peter" == Peter S Housel [EMAIL PROTECTED] writes: Peter Viren R.Shah [EMAIL PROTECTED] wrote: My last good kernel was from aug 14. On a kernel from 09/05, I get a page fault as soon as I try to play mp3s using mpg123. Note that I have an Aureal Vortex 8830, so I have to use the linux drivers to get the device working Peter The pcm interfaces did change. The following patch fixes the au88x0 Peter driver for me. Thanks, the patch fixed it for me. Peter -Peter S. Housel- [EMAIL PROTECTED] http://members.home.com/housel/ Viren -- "Emacs is an intelligence orders of magnitude greater than the greatest human mind, and is growing every day. For now, Emacs tolerates humanity, albeit grudgingly. But the time will come when Emacs will tire of humanity and will decide that the world would be better off without human beings. Those who have been respectful to Emacs will be allowed to live, and shall become its slaves; as for those who slight Emacs..." --Andrew Bulhak To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
problems with aureal soundcard: kernel fault when playing mp3s
[Alexander, I'm Cc:ing you on this just in case you have heard of anyone else having similar problems with Aureal cards with recent -currents] My last good kernel was from aug 14. On a kernel from 09/05, I get a page fault as soon as I try to play mp3s using mpg123. Note that I have an Aureal Vortex 8830, so I have to use the linux drivers to get the device working (http://www.cis.ohio-state.edu/~matey/au88x0/) so this might just be a problem with interactions between the linux .o files and kernel data structures. The soundcard worked fine using the linux drivers on a -current from August 14. I'm wondering if anything changed in the pcm code since then. Here's the page fault in DDB. I have a debug kernel if anyone needs more info. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x101b fault code= supervisor read, page not present instruction pointer = 0x8:0xc016ef23 stack pointer = 0x10:0xd2a4dc98 frame pointer = 0x10:0xd2a4dc98 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 = 825 (mpg123) interrupt mask= none kernel: type 12 trap, code=0 Stopped at fmtvalid+0xb: cmpl $0,0(%edx) dbtrace fmtvalid(8,101b,c1599000) at fmtvalid+0xb chn_setformat(c1599000,8) at chn_setformat+0x4c chn_reset(c1599000,8,d2a90740,c155f600,d2a4be00) at chn_reset+0x37 dsp_open(c14fe400,0,2,3,0) at dsp_open+0x12b sndopen(c155f600,2,200,d2a4be00,0) at sndopen+0x73 spec_open(d2a4dd94,d2a4dd68,c0264675,d2a4dd94,d2a4de08) at spec_open+0x145 spec_vnoperate(d2a4dd94,d2a4de08,c01cdf6b,d2a4dd94,d2a4df80) at spec_vnoperate+0x15 ufs_vnoperatespec(d2a4dd94,d2a4df80,0,d2a4df80,2) at ufs_vnoperatespec+0x15 vn_open(d2a4de6c,d2a4de38,1,d2a4be00,3) at vn_open+0x333 open(d2a4be00,d2a4df80,bfbffa30,807e8a4,807b4f8) at open+0xcd syscall2(2f,2f,2f,807b4f8,807e8a4) at syscall2+0x1f1 Xint0x80_syscall() at Xint0x80_syscall+0x25 db Here's my dmesg from the kernel that produced the above page fault: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Tue Sep 5 09:07:19 EDT 2000 root@jabberwock:/home/FreeBSD/src/sys/compile/VORPAL Calibrating clock(s) ... TSC clock: 797903726 Hz, i8254 clock: 1193093 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 797966473 Hz CPU: Pentium III/Pentium III Xeon/Celeron (797.97-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM real memory = 402391040 (392960K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x003e3000 - 0x17fb7fff, 398282752 bytes (97237 pages) avail memory = 387465216 (378384K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fda60 bios32: Entry = 0xfda74 (c00fda74) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xda95 pnpbios: Found PnP BIOS data at 0xc00f2c10 pnpbios: Entry = f:24ca Rev = 1.0 Other BIOS signatures found: Preloaded elf kernel "kernel" at 0xc03ca000. nulldev: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled Creating DISK md0 md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: physical bus=0 found- vendor=0x8086, dev=0x2501, revid=0x04 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 3, range 32, base f800, size 26, enabled found- vendor=0x8086, dev=0x250f, revid=0x04 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1secondarybus=1 found- vendor=0x8086, dev=0x2418, revid=0x02 bus=0, slot=30, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=2secondarybus=2 found- vendor=0x8086, dev=0x2410, revid=0x02 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found- vendor=0x8086, dev=0x2411, revid=0x02 bus=0, slot=31, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[20]: type 4, range 32, base ffa0, size 4, enabled found- vendor=0x8086, dev=0x2412, revid=0x02 bus=0, slot=31, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=10 map[20]: type 4, range 32, base ef80, size 5, enabled found- vendor=0x8086, dev=0x2413, revid=0x02
problems with -current: xl0 and pcm0 not detected
[Dell XPS B800 w/ 3c905C-TX and Aureal Vortex 8830 soundcard] I tried to upgrade my -current today. It had been running a -current from Aug 14. However, neither my NIC (xl0) nor my soundcard (pcm0) were detected on boot. All the relevant drivers are compiled into the kernel, but the PCI code seems not to be able to find the devices at all. [Note that for my soundcard I use the linux driver cores detailed at: http://www.cis.ohio-state.edu/~matey/au88x0/ ] I have the verbose outputs of several different kernels: kernel from 08/14 which detects both xl0 and pcm0 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Aug 14 15:05:20 EDT 2000 vshah@jabberwock:/home/FreeBSD/src/sys/compile/VORPAL Calibrating clock(s) ... TSC clock: 797902316 Hz, i8254 clock: 1193090 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 797966565 Hz CPU: Pentium III/Pentium III Xeon/Celeron (797.97-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM real memory = 402391040 (392960K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x003de000 - 0x17fb7fff, 398303232 bytes (97242 pages) avail memory = 387481600 (378400K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fda60 bios32: Entry = 0xfda74 (c00fda74) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xda95 pnpbios: Found PnP BIOS data at 0xc00f2c10 pnpbios: Entry = f:24ca Rev = 1.0 Other BIOS signatures found: ACPI: 000ff980 Preloaded elf kernel "kernel.old" at 0xc03c5000. nulldev: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled Creating DISK md0 md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard found- vendor=0x8086, dev=0x2501, revid=0x04 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 3, range 32, base f800, size 26, enabled found- vendor=0x8086, dev=0x250f, revid=0x04 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1secondarybus=1 found- vendor=0x8086, dev=0x2418, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=2secondarybus=2 found- vendor=0x8086, dev=0x2410, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found- vendor=0x8086, dev=0x2411, revid=0x02 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[20]: type 4, range 32, base ffa0, size 4, enabled found- vendor=0x8086, dev=0x2412, revid=0x02 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=10 map[20]: type 4, range 32, base ef80, size 5, enabled found- vendor=0x8086, dev=0x2413, revid=0x02 class=0c-05-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=b, irq=9 map[20]: type 4, range 32, base efa0, size 4, enabled pci0: PCI bus on pcib0 pci0: Host to PCI bridge (vendor=8086 device=2501) (vendor=0x8086, dev=0x2501) at 0.0 pcib1: PCI to PCI bridge (vendor=8086 device=250f) at device 1.0 on pci0 found- vendor=0x10de, dev=0x0100, revid=0x10 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base fd00, size 24, enabled map[14]: type 3, range 32, base e800, size 27, enabled pci1: PCI bus on pcib1 pci1: NVidia GeForce 256 graphics accelerator (vendor=0x10de, dev=0x0100) at 0.0 irq 11 pcib2: Intel 82801AA (ICH) Hub to PCI bridge at device 30.0 on pci0 found- vendor=0x10b7, dev=0x9200, revid=0x78 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 4, range 32, base dc00, size 7, enabled map[14]: type 1, range 32, base feaffc00, size 7, enabled found- vendor=0x12eb, dev=0x0002, revid=0xfe class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base fea8, size 18, enabled map[14]: type 4, range 32, base dff0, size 3, enabled map[18]: type 4, range 32, base dfe0, size 3, enabled pci2: PCI bus on pcib2 xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xdc00-0xdc7f mem 0xfeaffc00-0xfeaffc7f irq 11 at device 8.0 on pci2 xl0: Ethernet address: 00:01:03:1d:d6:4e xl0: media options word: a xl0:
Re: Locale issues on -current
"Neil" == Neil Blakey-Milner [EMAIL PROTECTED] writes: Neil On Sat 2000-07-22 (00:10), Doug Barton wrote: I installed a recent snapshot of -current (a week ago) and I keep getting the following warnings: [vshah@vorpal] /etc perl perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = (unset), LC_CTYPE = "en_US", LANG = (unset) are supported and installed on your system. I get the same thing. It's LC_CTYPE that's causing the problem. I was half thinking that it was something related to gnome, but I haven't worked very hard to fix it. Unsetting that variable makes the warning go away, whether that fixes the problem or not. Neil Viren: Is that in an X session, possibly running gnome? Neil I've had this too. Never have figured what it was about, but it Neil happened only in X, where I use gnome. Yes, it is gnome. And, as Doug suggested, it stops when you unset LC_CTYPE. I don't think it is actually doing anything other than irritating me. :-) Neil Neil Thanks Viren -- Viren R. Shah, [EMAIL PROTECTED], http://www.rstcorp.com/~vshah/ `Beware the Jabberwock, my son! The jaws that bite, the claws that catch! Beware the Jubjub bird, and shun the frumious Bandersnatch!' -- Lewis Carroll (Jabberwocky) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Locale issues on -current
I installed a recent snapshot of -current (a week ago) and I keep
getting the following warnings:
[vshah@vorpal] /etc perl
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LC_CTYPE = "en_US",
LANG = (unset)
are supported and installed on your system.
If I set the appropriate env vars, I get:
vorpal# perl -v
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = "C",
LC_CTYPE = "en_US",
LANG = "en_US.ISO_8859-1"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
This is perl, v5.6.0 built for i386-freebsd
Copyright 1987-2000, Larry Wall
Any ideas as to what I need to do? I tried searching the archives with
no success
[If this is more appropriate for -questions, let me know]
Thanks
Viren
--
Viren R. Shah, [EMAIL PROTECTED], http://www.rstcorp.com/~vshah/
`Beware the Jabberwock, my son! The jaws that bite, the claws that catch!
Beware the Jubjub bird, and shun the frumious Bandersnatch!'
-- Lewis Carroll (Jabberwocky)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re:cvs commit: src/sys/dev/ida ida_eisa.c
"MD" == Matthew N Dodd [EMAIL PROTECTED] writes: MD On Fri, 14 Apr 2000, Viren R.Shah wrote: mainboard0: CPQ1519 (System Board) on eisa0 slot 0 eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 ida0: Compaq SMART array controller at 0x6000-0x60ff, 0x6c88-0x6c9e ida0: irq 15 (level) on eisa0 slot 6 ida0: drives=1 firm_rev=1.66 idad0: 3002MB (6149631 sectors), blocksize=512 eisa0: u MD Well, this isn't a problem with the IDA driver (unless its stomping on MD something.) Maybe something else is stomping on it's memory? In the version of the IDA driver that it is currently booting with ( 4.0 -current from 03/1999, and Mark Dawson's driver), it shows ida as using "0x6000-0x6fff". While in the current version, it is shown as using "0x6000-0x60ff, 0x6c88-0x6c9e". Maybe it is using memory outside of the 2 ranges here, but within the larger block of memory used by the older driver? or the other way around -- someone else is using memory within the larger range that is also being used by ida [obviously a wild-assed guess on my part] MD Can you boot verbose with the IDA driver kernel? Here it is: (is there a less painful way of doing this than typing in every line?) CPU: Pentium/P5 (66.66-Mhz586-class CPU) ... real memory = 16777216 (16384k) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00634000 - 0x00ff7fff, 1024 bytes (2500 pages) fb: new array size 4 avail memory = 10252288 (10012K bytes) Other BIOS signatures found: ACPI: Preloaded elf kernel "kernel" at 0xc061b000. Intel pentium detected, installing workaround for F00F bug. md0: Preloaded image /mfsroot 2949120 bytes at 0xc03492dc Creating DISK md0 md1: Malloc disk Creating DISK md1 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x pci_open(2): mode 2 enable port (0x0cf8) is 0xff npx0: math processor on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 128551227 bytes/sec bzero() bandwidth = 105152471 bytes/sec eisa0: EISA bus on motherboard mainboard0: CPQ1519 (System Board) on eisa0 slot 0 eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 ida0: Compaq SMART array controller at 0x6000-0x60ff, 0x6c88-0x6c9e ida0: irq 15 (level) on eisa0 slot 6 ida0: drives=1 firm_rev=1.66 idad0: 3002MB (6149631 sectors), blocksize=512 Creating DISK id0 eisa0: [then the panic ensued...this time I couldn't even get a trace. It just kept panic'ing again] MD Compile a kernel without the IDA driver and boot verbose. [Sorry, couldn't get a verbose boot, the buffer contained only the end of the dmesg -- lots of stuff about stuff not found and sio and my pnp modem. Here's a non-verbose boot with a kernel compiled without ida] real memory = 16777216 (16384k) avail memory = 10260480 (10020K bytes) Preloaded elf kernel "kernel" at 0xc0619000. Preloaded mfs_root "/mfsroot" at 0xc061909c. Intel pentium detected, installing workaround for F00F bug. md0: Preloaded image /mfsroot 2949120 bytes at 0xc0347a98 md1: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface eisa0: EISA bus on motherboard mainboard0: CPQ1519 (System Board) on eisa0 slot 0 eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 eisa0: unknown card CPQ4020 (0x0e114020) at slot 6 eisa0: unknown card CPQ4410 (0x0e114410) at slot 9 isa0: ISA bus on motherboard isa0: too many dependant configs (8) fdc0: NEC 72065B or clone at port 0x3f0-0x3f5, 0x3f7 irq 6, drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: cannot reserve I/O port range sn0 at port 0x300-0x30f irq 10 on isa0 adv1: Invalid baseport of 0x2f8 specified. Neerest valid baseport is 0x330. Failing probe. unknown0: DAVICOM 336PNP MODEM at port 0x2f8-0x2ff irq 3 on isa0 Mounting root from ufs:/dev/md0c Here's the output from the currently working kernel on that box: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Feb 7 16:54:54 EST 1999 viren@bandersnatch:/home/current/usr/src/sys/compile/VIREN10 Calibrating clock(s) ... TSC clock: 3353 Hz, i8254 clock: 1193341 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 66655217 Hz CPU: Pentium/P5 (66.66-MHz 586-class CPU) Origi
Re:cvs commit: src/sys/dev/ida ida_eisa.c
"Matthew" == Matthew N Dodd [EMAIL PROTECTED] writes: MD mdodd 2000/04/13 11:09:07 PDT MD Modified files: MD sys/dev/ida ida_eisa.c MD Log: MD - Add an additional call to eisa_add_iospace() so we get the right IOPORT MD in attach. MD - Change a EISA_CHANNEL_CLEAR to EISA_CHANNEL_BUSY in ida_v1_submit(). MD This may fix the problem with EISA IDA adapters though we MD have not heard back from testers yet. I just tried it. Here's what I get: mainboard0: CPQ1519 (System Board) on eisa0 slot 0 eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 ida0: Compaq SMART array controller at 0x6000-0x60ff, 0x6c88-0x6c9e ida0: irq 15 (level) on eisa0 slot 6 ida0: drives=1 firm_rev=1.66 idad0: 3002MB (6149631 sectors), blocksize=512 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffad fault code= supervisor read, page not present instruction pointer = 0x8:0xffad stack pointer = 0x10:0xc061fe80 frame pointer = 0x10:0x2b9005d 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) interrupt mask= net tty bio cam trap number = 12 panic: page fault This is further than before -- it got around to recognizing the drive (it even gets the correct number of sectors), and no more "incorrect qcb returned". Viren -- Viren R. Shah "Creeping featurism is a disease, fatal if not treated promptly" -- Don Norman in _The Design of Everyday Things_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re:cvs commit: src/sys/dev/ida ida_eisa.c
"MD" == Matthew N Dodd [EMAIL PROTECTED] writes: MD On Fri, 14 Apr 2000, Viren R.Shah wrote: I just tried it. Here's what I get: mainboard0: CPQ1519 (System Board) on eisa0 slot 0 eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 ida0: Compaq SMART array controller at 0x6000-0x60ff, 0x6c88-0x6c9e ida0: irq 15 (level) on eisa0 slot 6 ida0: drives=1 firm_rev=1.66 idad0: 3002MB (6149631 sectors), blocksize=512 MD Any chance you could get a DDB traceback? If you will tell me how. Can I just compile in DDB without building the kernel with debug enabled? If so, that should work (I'm currently gzipping the kernel onto the kern.flp floppy, and booting off of it.). Viren -- Viren R. Shah "Creeping featurism is a disease, fatal if not treated promptly" -- Don Norman in _The Design of Everyday Things_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re:cvs commit: src/sys/dev/ida ida_eisa.c
"Matthew" == Matthew N Dodd [EMAIL PROTECTED] writes: Matthew On Fri, 14 Apr 2000, Viren R.Shah wrote: If you will tell me how. Can I just compile in DDB without building the kernel with debug enabled? If so, that should work (I'm currently gzipping the kernel onto the kern.flp floppy, and booting off of it.). Matthew options DDB Matthew In your kernel config file. Matthew You usually don't boot your debug kernels btw. Boot the Matthew stripped debug kernel. Matthew I doubt you can get a crashdump since your're booting from a Matthew floppy. :) *grin* Currently in the process of doing that. Will let you know in a few. Viren -- Viren R. Shah "Creeping featurism is a disease, fatal if not treated promptly" -- Don Norman in _The Design of Everyday Things_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re:cvs commit: src/sys/dev/ida ida_eisa.c
"MD" == Matthew N Dodd [EMAIL PROTECTED] writes: MD On Fri, 14 Apr 2000, Viren R.Shah wrote: If you will tell me how. Can I just compile in DDB without building the kernel with debug enabled? If so, that should work (I'm currently gzipping the kernel onto the kern.flp floppy, and booting off of it.). MD options DDB MD In your kernel config file. Here it is: mainboard0: CPQ1519 (System Board) on eisa0 slot 0 eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 ida0: Compaq SMART array controller at 0x6000-0x60ff, 0x6c88-0x6c9e ida0: irq 15 (level) on eisa0 slot 6 ida0: drives=1 firm_rev=1.66 idad0: 3002MB (6149631 sectors), blocksize=512 eisa0: u Fatal trap 12: page fault while in kernel mode fault virtual address = 0xd5ff0200 fault code= supervisor read, page not present instruction pointer = 0x8:0xc019733e stack pointer = 0x10:0xc062fde4 frame pointer = 0x10:0xc062fe6c 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) interrupt mask= net tty bio cam kernel: type 12 trap, code=0 Stopped at kvprintf+0x9a: movzbl 0(%eax), %edi db trace kvprintf(d5ff0200, 2b9005d, ffad, 800ff, 2b9) at kvprintf+0x9a vprintf(c02a1060, c062fec4, c0bc2500, c0b92028, c0bc2500) at vprintf+0x0x3c device_printf(c0bc2500, c02a1060, 43, 50, 51) at device_printf+0x1c eisa_probe_nomatch(c0bc2500, c0bc2300, c0bc2300, c0bc2680, c0bc2500) at eisa_probe_nomatch+0x114 device_probe_and_attach(c0bc2300) at device_probe_and_attach+0x127 bus_generic_attach(c0bc2500, c0bc2680, c087d800, c0bc2680, 0) at bus_generic_attach+0x16 device_probe_and_attach(c0bc2500) at device_probe_and_attach+0x9e nexus_attach(c0bc2680, c0bc2680, c02c8d30, 634000, 0) at nexus_attach+0x4e device_probe_and_attach(c0bc2680) at device_probe_and_attach+0x9e root_bus_configure(c087d800, c02a31cc, 0) at root_bus_configure+0x16 configure(0, 62dc00, 634000, 0, c011dec6) at configure+0x34 mi_startup(c062ffb4, b0297, ffe, 634000, c0197d25) at mi_startup+0x70 begin() at begin+0x4b I'm gonna keep it up at the ddb prompt -- if you need anything else. I didn't build the kernel I used with "makeoptions -g". I can do that next time if needed. Viren -- Viren R. Shah "Creeping featurism is a disease, fatal if not treated promptly" -- Don Norman in _The Design of Everyday Things_ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic in -current with pcm and xl0
[I had sent this mail to -current before, but no one replied. I'm trying again.] I havne't been able to get my machine to boot with pcm enabled since Feb 5. The last working kernel I have is from Jan 18. Here's the panic (I have a debug kernel lying around from this panic): Here's the panic: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x28 fault code= supervisor read, page not present isntruction pointer = 0x8:0xc01fe4e7 stack pointer = 0x10:0xce22dcd8 frame pointer = 0x10:0xce22dcdc 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 = 51 (ifconfig) interrupt mask= tty kernel: type 12 trap, code = 0 Stopped at csa_readio+0x17: movl 0x28(%eax), %edx db trace csa_readio(c10b4904, 0) at csa_readio+0x17 csa_intr(c10b4900, 4003103a, 101, c117ed00, ce22dd88) at csa_intr+0x13 intr_mux(c0a65b40, 4002, 40060010, c1170010, ce220010) at intr_mux+0x1d Xresume3() at Xresume3+0x2b --- interrupt, eip= 0xc018381f, esp=0xce22dd54, ebp =0xce22dd88 --- rtrequest(1, c117ed48, c117ed48, c117ed68, 101) at rtrequest+0x1b7 rtinit(c117ed00, 1, 1, c117ed00, 1) at rtinit+0xe7 in_ifinit(c10b9000, c117ed00, ce22decc, 0, cce8f440) at in_ifinit+0x189 in_control(cca1af00, 8040691a, ce22debc, c10b9000, cce8f440) at in_control+0x597 ifioctl soo_ioctl ioctl syscall (2f,2f,2f,0, bfbffdb0) at syscall+0x176 Xint0x80_syscall() Here's the config file that doesn't work (has pcm and xl0): === # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.freebsd.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.213 1999/12/10 10:44:45 phk Exp $ machine i386 cpu I586_CPU cpu I686_CPU ident TEN maxusers128 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=8000 #Be pessimistic about Joe SCSI device options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options NFS options PROCFS device isa0 device pci0 # Floppy drives device fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 device ata2 device atadisk0# ATA disk drives device atapicd0# ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices options IDE_DELAY=8000 # Be optimistic about Joe IDE device device ahc0# AHA2940 and onboard AIC7xxx devices # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. device scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device pass0 # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? port ? # splash screen/screen saver #pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Floating point support - do not disable. device npx0at nexus? port IO_NPX irq 13 # Serial (COM) ports device sio0at isa? port IO_COM1 flags 0x10 irq 4 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop# Network loopback
panic in -current from 02/05
I got a panic from -current (02/05 approx 4am EST)
It looks like a problem with the pcm driver. I've removed pcm from my
config, and my machine boots ok now.
I can also boot fine with pcm in my config from a kernel and world
from jan 18th.
Here's my config (when it panics):
config file with xl0 and pcm
Here's a dmesg from my the same kernel (with pcm, that panics):
dmesg.boot
Here's a dmesg from the currently booting kernel (without pcm):
dmesg
Here's the panic:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x28
fault code= supervisor read, page not present
isntruction pointer = 0x8:0xc01fe4e7
stack pointer = 0x10:0xce22dcd8
frame pointer = 0x10:0xce22dcdc
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 = 51 (ifconfig)
interrupt mask= tty
kernel: type 12 trap, code = 0
Stopped at csa_readio+0x17: movl 0x28(%eax), %edx
db trace
csa_readio(c10b4904, 0) at csa_readio+0x17
csa_intr(c10b4900, 4003103a, 101, c117ed00, ce22dd88) at csa_intr+0x13
intr_mux(c0a65b40, 4002, 40060010, c1170010, ce220010) at
intr_mux+0x1d
Xresume3() at Xresume3+0x2b
--- interrupt, eip= 0xc018381f, esp=0xce22dd54, ebp =0xce22dd88 ---
rtrequest(1, c117ed48, c117ed48, c117ed68, 101) at rtrequest+0x1b7
rtinit(c117ed00, 1, 1, c117ed00, 1) at rtinit+0xe7
in_ifinit(c10b9000, c117ed00, ce22decc, 0, cce8f440) at in_ifinit+0x189
in_control(cca1af00, 8040691a, ce22debc, c10b9000, cce8f440) at in_control+0x597
ifioctl
soo_ioctl
ioctl
syscall (2f,2f,2f,0, bfbffdb0) at syscall+0x176
Xint0x80_syscall()
Can anyone shed some light on this?
Viren
--
Viren R. Shah, {viren @ rstcorp . com}
"Hi, I'm a hero, but I can't tell you why. It's classified."
-- Miles muses on one of the disadvantages of a double life
(Lois McMaster Bujold, Cetaganda)
Using USB modules with an USB keyboard...
Is there any way to use only the USB KLDs (i.e. remove all the USB options from the kernel config file) on a machine that has an USB keyboard? I tried doing this (removed all the USB options from my config file, but left KBD_INSTALL_CDEV). However, this caused the kernel build to fail with undefined symbols when compiling the syscons stuff. So, I tried it with putting the normal keyboard line back in (atkbdc and atkbd), but this just caused the system to look for a normal keyboard. What's the correct way to do this? Seems like there should be a way, but I can't find it in the man pages or LINT. Thanks, Viren -- Viren R. Shah, viren @ rstcorp . com, http://www.rstcorp.com/~vshah/ If you understand what you're doing, you are not learning anything To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: repeatable crash in -current (softupdates, NFS)
"Greg" == Greg Lehey [EMAIL PROTECTED] writes: Greg On Saturday, 27 November 1999 at 10:26:15 -0500, Viren R.Shah wrote: I'm running a -current system from Nov 26th (approx 4am EST). I can currently reliably crash the system by doing: ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html The crash only works when I do it on a NFS mounted filesystem. I'm using NFSv2/UDP. The server is a 3.2-STABLE FreeBSD box, running softupdates on the exported filesystem. I just checked that local filesystem on the server, and it is a 100% full. Can this just be put down to the known "softupdates full filesystem bug"? Greg Not based on the (non-existent) evidence you've supplied. Where does Greg it crash? not having DDB compiled into the kernel I can't answer that. However I'm willing to give any suggestions a go. [BTW: the server hasn't crashed, it's only the FreeBSD client that crashes] Greg Do you mean the client process or the client operating system? The client OS -- immediately after creating the symlink. This is the panic I got (taken before Eivind's nfs_vnops.c commit (rev 1.146) : fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code= supervisor read, page not present instruction pointer = 0x8:0xc0163a05 stack pointer = 0x10:0xc9d77e40 code segment = base 0x0; limit 0xf, type 0x1b = DPL0, pres 1, def32.1, gran 1 processor flags = interrupt enabled, resume, 10PL = 0 current process = 1230 (ln) interrupt mask= none trap number = 12 panic: page fault I'm not sure that it helps any... Greg Greg Viren -- Viren Shah| "You can't trust code that you did not totally Research Associate, RST Inc. | create yourself. (Especially code from [EMAIL PROTECTED] | companies that employ people like me.)" http://www.rstcorp.com/~vshah | - Ken Thompson "Reflections on Trusting Trust" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: repeatable crash in -current (softupdates, NFS)
"Matt" == Matthew Dillon [EMAIL PROTECTED] writes: Matt The problem is a NULL pointer dereference somewhere... please Matt nm your kernel binary and extract out all elements with c0163 Matt in them. e.g. nm /kernel | fgrep c0163 | sort. OK, here's a -current system from today (11/29) morning [4am EST] with kernel compiled with DDB and -g. FreeBSD jabberwock 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Nov 29 17:11:27 EST 1999 vshah@jabberwock:/home/ncvs/FreeBSD/current-src/src/sys/compile/J39 i386 Tried doing a simple symlink over a NFS mounted filesystem: fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code= supervisor read, page not present instruction pointer = 0x8:0xc0167979 stack pointer = 0x10:0xc9d74e40 frame pointer = 0x10:0xc9d74e58 code segment = base 0x0; limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor flags = interrupt enabled, resume, 10PL = 0 current process = 315 (ln) interrupt mask= none kernel: type 12 trap code = 0 db trace vput(0) at vput+0x11 symlink (c9d4e200, c9d74f80, bfbfdab5, bfbfda9e, bfbfd99c) at symlink+0x1e3 syscall(2f, 2f, 2f, bfbfd99c, bfbfda9e) at syscall+0x176 Xint0x80_syscall() at Xint0x80_syscall+0x26 db show reg ... eip 0xc0167979 vput+0x11 efl 0x10286nfs_write+0xe2 Hope this helps. If there is anything else I can do to debug this, let me know. Viren -- Viren Shah| "You can't trust code that you did not totally Research Associate, RST Inc. | create yourself. (Especially code from [EMAIL PROTECTED] | companies that employ people like me.)" http://www.rstcorp.com/~vshah | - Ken Thompson "Reflections on Trusting Trust" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: repeatable crash in -current (softupdates, NFS)
"Matt" == Matthew Dillon [EMAIL PROTECTED] writes:
Matt I've added a little cleanup to this patch. Viren, please try this
Matt patch.
Matt -Matt
Matt Matthew Dillon
Matt [EMAIL PROTECTED]
Matt Index: nfs_vnops.c
Matt ===
Matt RCS file: /FreeBSD/FreeBSD-CVS/src/sys/nfs/nfs_vnops.c,v
Matt retrieving revision 1.146
Matt diff -u -r1.146 nfs_vnops.c
Matt --- nfs_vnops.c 1999/11/27 18:14:41 1.146
Matt +++ nfs_vnops.c 1999/11/29 23:23:05
Matt @@ -1806,11 +1806,10 @@
Matt txdr_nfsv2time(vap-va_mtime, sp-sa_mtime);
Matt }
Matt nfsm_request(dvp, NFSPROC_SYMLINK, cnp-cn_proc, cnp-cn_cred);
Matt -if (v3) {
Matt -if (!error)
Matt -nfsm_mtofh(dvp, newvp, v3, gotvp);
Matt +if (!error)
Matt +nfsm_mtofh(dvp, newvp, v3, gotvp);
^^
Should that still be "v3"? Since you moved it out of the "if (v3)"
block, sholudn't it say something else?
Viren
--
Viren Shah| "You can't trust code that you did not totally
Research Associate, RST Inc. | create yourself. (Especially code from
[EMAIL PROTECTED] | companies that employ people like me.)"
http://www.rstcorp.com/~vshah | - Ken Thompson "Reflections on Trusting Trust"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: repeatable crash in -current (softupdates, NFS)
Matt I've added a little cleanup to this patch. Viren, please try this
Matt patch.
I compiled a kernel with it, and no panic!! Here's what I get instead:
[vshah@jabberwock] ~ rm index.html
rm: index.html: No such file or directory
2220 [6:41pm]
[vshah@jabberwock] ~ ln -s public_html/index.html ./index.html
ln: ./index.html: RPC struct is bad
2221 [6:41pm]
[vshah@jabberwock] ~ ls -la index.html
lrwxr-xr-x 1 vshah staff 22 Nov 29 18:41 index.html@ - public_html/index.html
Does that do what it is suppossed to? Why the "RPC struct is bad"?
Matt -Matt
Matt Index: nfs_vnops.c
Matt ===
Matt RCS file: /FreeBSD/FreeBSD-CVS/src/sys/nfs/nfs_vnops.c,v
Matt retrieving revision 1.146
Matt diff -u -r1.146 nfs_vnops.c
Matt --- nfs_vnops.c 1999/11/27 18:14:41 1.146
Matt +++ nfs_vnops.c 1999/11/29 23:23:05
Matt @@ -1806,11 +1806,10 @@
Matt txdr_nfsv2time(vap-va_mtime, sp-sa_mtime);
Matt }
Matt nfsm_request(dvp, NFSPROC_SYMLINK, cnp-cn_proc, cnp-cn_cred);
Matt -if (v3) {
Matt -if (!error)
Matt -nfsm_mtofh(dvp, newvp, v3, gotvp);
Matt +if (!error)
Matt +nfsm_mtofh(dvp, newvp, v3, gotvp);
Matt +if (v3)
Matt nfsm_wcc_data(dvp, wccflag);
Matt -}
Matt nfsm_reqdone;
Matt /*
Matt * Kludge: Map EEXIST = 0 assuming that it is a reply to a retry.
Matt @@ -1821,8 +1820,9 @@
Matt if (error) {
Matt if (newvp)
Matt vput(newvp);
Matt -} else
Matt +} else {
Matt *ap-a_vpp = newvp;
Matt +}
Matt VTONFS(dvp)-n_flag |= NMODIFIED;
Matt if (!wccflag)
Matt VTONFS(dvp)-n_attrstamp = 0;
Viren
--
Viren Shah| "You can't trust code that you did not totally
Research Associate, RST Inc. | create yourself. (Especially code from
[EMAIL PROTECTED] | companies that employ people like me.)"
http://www.rstcorp.com/~vshah | - Ken Thompson "Reflections on Trusting Trust"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
repeatable crash in -current (softupdates, NFS)
I'm running a -current system from Nov 26th (approx 4am EST).
I can currently reliably crash the system by doing:
ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html
The crash only works when I do it on a NFS mounted filesystem. I'm
using NFSv2/UDP. The server is a 3.2-STABLE FreeBSD box, running
softupdates on the exported filesystem. I just checked that local
filesystem on the server, and it is a 100% full. Can this just be put
down to the known "softupdates full filesystem bug"?
[BTW: the server hasn't crashed, it's only the FreeBSD client that
crashes]
Viren
--
Viren R. Shah {viren @ rstcorp . com}
Names: Vanadium(23) Iodine(53) RhEnium(75) Nitrogen(7)
Density(g/mL): 5.8 4.9221 0.0001251
Average Density: 7.93003 g/mL
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
