panics during installation of -CURRENT on Thinkpad A31p
Hi, I just got a Thinkpad A31p on which I try to install -current. I've tried several snapshots: 5.1-RELEASE panics during kernel boot, while trying to create a firewire0 device. ACPI enabled or not makes no difference. A current snapshot, like 5.1-CURRENT-20031015-JPSNAP boots correctly and sysinstall starts. A trap is encountered as soon as I try to configure any of the two network interfaces. fxp0 and a wi0 are detected. ACPI enabled or not again makes no difference. If I try to configure them using DHCP or even manually configure them, I get traps like the following: [..] kernel: type 18 trap, code=0 stopped at cbb_intr+0x22: movl %eax,%esi db trace cbb_intr(c2114e00,0,c083b22c,230,c4bfd000) at cbb_intr+0x22 ithread_loop(c4c07980,d7963d48,c083b09e,314,0) at ithread_loop+0x192 fork_exit(c0623c60,c4c07980,d7963d48) at fork_exit+0xcf fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd7963d7c, ebp = 0 --- This one was encountered while trying to set up fxp0 with DHCP. 4.9-RC2 seems to work flawless on this hardware. I can use both fxp0 and wi0 interfaces. However I would prefer to run 5.x, and I guess you folks would like to have feedback about configurations resulting in panics. Thanks and best regards, Daniel -- IRCnet: Mr-Spock- Do you love yourself ? - Yes! (Isar 12) - Daniel Lang * [EMAIL PROTECTED] * +49 89 289 18532 * http://www.leo.org/~dl/ smime.p7s Description: S/MIME cryptographic signature
Re: panics during installation of -CURRENT on Thinkpad A31p
Hi Folks, Daniel Lang wrote on Thu, Oct 16, 2003 at 02:15:56PM +0200: [..] A current snapshot, like 5.1-CURRENT-20031015-JPSNAP boots correctly and sysinstall starts. A trap is encountered as soon as I try to configure any of the two network interfaces. fxp0 and a wi0 are detected. ACPI enabled or not again makes no difference. If I try to configure them using DHCP or even manually configure them, I get traps like the following: [..] kernel: type 18 trap, code=0 stopped at cbb_intr+0x22: movl %eax,%esi db trace cbb_intr(c2114e00,0,c083b22c,230,c4bfd000) at cbb_intr+0x22 ithread_loop(c4c07980,d7963d48,c083b09e,314,0) at ithread_loop+0x192 fork_exit(c0623c60,c4c07980,d7963d48) at fork_exit+0xcf fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd7963d7c, ebp = 0 --- This one was encountered while trying to set up fxp0 with DHCP. [..] I managed to install the snapshot from CD and provoke the panics with a manual ifconfig. Thus I could obtain crash dumps, which I have sort-of analysed. I've filed a PR with all the details (stack trace with symbols, analysed some variables, etc): kern/58139 Please check it out: http://www.freebsd.org/cgi/query-pr.cgi?pr=58139 Thanks for your help. Best regards, Daniel -- IRCnet: Mr-Spock - Burn them to ashes, then burn the ashes. - Daniel Lang * [EMAIL PROTECTED] * +49 89 289 18532 * http://www.leo.org/~dl/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keyboard not working with XFree86
Hi Again, Daniel Lang wrote on Wed, Jul 16, 2003 at 05:16:23PM +0200: [..] I've recently upgraded my Notebook to 5.1-CURRENT. One of the main problems I ran into, is, that the keyboard is not working when using X. [..] If I start up X, I cannot put in any key. The mouse works fine, though. I have to remote log into the box and kill xdm to get rid of the problem. The keyboard works perfectly on the console. [..] I could solve the problem. First to complete the symptoms: - Keyboard works on the console - Keyboard does not work using X (regardless of using 'xdm' oder 'startx') - ZapServer (Ctrl-Alt-Backspace) DOES work. This lead my investigation to a problem with the keymap, but the real cause turned out to be utterly obscure. The XKeysymDB file was missing! (And as I found out later, the XErrorDB file, as well). But, it was listed in the +CONTENTS file of the XFree86-libraries port. So apprently it has been installed? But maybe was removed by something else? I certainly did not remove these files. I could solve the problem easily by copying the files back into place, and I cannot rule out, that the files have been lost due to my fault. If any of the XFree port maintainers are aware of fiddling with XKeysymDB or the like, maybe there is indeed a problem. Best regards, Daniel -- IRCnet: Mr-Spock - In dieser Mail ist ein Geist, der Dich in den Hintern beisst - Daniel Lang * [EMAIL PROTECTED] * +49 89 289 18532 * http://www.leo.org/~dl/ smime.p7s Description: S/MIME cryptographic signature
Keyboard not working with XFree86
Hi Folks, I've recently upgraded my Notebook to 5.1-CURRENT. One of the main problems I ran into, is, that the keyboard is not working when using X. For the update from 4.8 to 5.1 I've followed the UPDATING procedure and was successful. After that I deleted all ports/packages and installed most of the ports fresh, including XFree86. Now I have XFree86-Server-4.3.0_8 installed. If I start up X, I cannot put in any key. The mouse works fine, though. I have to remote log into the box and kill xdm to get rid of the problem. The keyboard works perfectly on the console. I searched the mailing list archives and bug reports, but did not find anything. I also tried to create a fresh XF86Config file using xf86cfg (GUI based) and xf86config (text based). Both resulting config files had the same problem as the original config file, i.e. everything works except the keyboard. Now I've updated my 5.1-CURRENT to a snapshot from July 15, and tried to rebuild the XFree86-4-Server port. Now, the portbuild fails in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/GL/mesa/src/drv/radeon/ while trying to compile radeon_vtxtmp_x86.S error message are many lines of similar output, example: [..] radeon_vtxtmp_x86.S:400:34: pasting _x86_MultiTexCoord2fARB_2 and : does not give a valid preprocessing token. I don't think thats a problem, but due to the recent gcc import, since the portrevision has not changed, this probably wouldn't solve my problem anyway. But for the keyboard problem, any hints are appreciated. Best regards, Daniel -- IRCnet: Mr-Spock - signs of absurd developments in the net community: #42: - Wurstbrot gehoert m.E. zum Fruehstuecks-botnet von Cartoon - Daniel Lang * [EMAIL PROTECTED] * +49 89 289 18532 * http://www.leo.org/~dl/ smime.p7s Description: S/MIME cryptographic signature
make release fails
Hiho, I'm using a 3.1-STABLE system, up to date with a current CVS-tree. No I would like to install a few other boxes as well, so I thought 'make release' would be the thing. I set the RELEASETAG to RELENG_3, make release then seems to run fine, until it wants to build kerberosIV. This fails with 'don't know how to make k_getpwuid.c' (or similar). Now the thing is, I'm not USA_RESDIDENT, so I don't have Kerberos installed, and I don't want it in the release anyway. I tried to set 'NOKERBEROS', 'NOCRYPT', etc, but it doesn't seem to work. But I have to admit, that I made a 'make rerelease' after the build broke down. I didn't want it to remove the whole chroot-tree and check the whole stuff out again, since this takes AGES (even on my sort of fast machine). If anyone has any hints, how to avoid building kerberos, preferrably without having to do a 'make release' and set the trees up from scratch again, I would be grateful. Any other general hints for 'make release' or some more documentation apart from /usr/src/release/Makefile would be nice, as well. Btw, I'm not subscribed to any of the mailing-lists, I'd rather browse the archives. So if anyone likes to answer, please include a cc: to my personal address, or at least give me hint like 'Watch the ...-list' or 'You _should_ be subscribed to ...'. Cheers, Daniel -- IRCnet: Mr-Spock - Agartim billiard bumba m'abdul in papejim twista - rumba rock n rolla. Leik'ab mai. Spirzon Heroin se'osit gaula. - - Marijuana esit gaula. Haschisch. Opis. - RL: Daniel Lang * d...@leo.org * +49 89 8540017 * http://www.leo.org/~dl/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
