panic: blockable sleep lock (sleep mutex) UMA pcpu @vm/uma_core.c:1381
Hi I am running FreeBSD 5.1-CURRENT #4: Sat Aug 23 18:14:15 AST 2003. I have been trying to use the NVidia driver from the /usr/ports/x11/nvidia-driver but it causes random panics like this. The full backtrace is at http://196.12.160.4/~iceadmin/btfull If you need more information ask please. (kgdb) bt #0 doadump () at ../../../kern/kern_shutdown.c:240 #1 0xc031b04c in boot (howto=260) at ../../../kern/kern_shutdown.c:372 #2 0xc031b3d7 in panic () at ../../../kern/kern_shutdown.c:550 #3 0xc0322f65 in mi_switch () at ../../../kern/kern_synch.c:473 #4 0xc032285a in msleep (ident=0xc060e578, mtx=0xc060e580, priority=68, wmesg=0xc052bcab wdrain, timo=0) at ../../../kern/kern_synch.c:255 #5 0xc0361fd2 in bwrite (bp=0xc7a5ec08) at ../../../kern/vfs_bio.c:363 #6 0xc0363d81 in vfs_bio_awrite (bp=0xc7a5ec08) at ../../../kern/vfs_bio.c:1709 #7 0xc036b647 in vop_stdfsync (ap=0xcd849944) at ../../../kern/vfs_default.c:737 #8 0xc02e0c00 in spec_fsync (ap=0xcd849944) at ../../../fs/specfs/spec_vnops.c:417 #9 0xc02dfed8 in spec_vnoperate (ap=0x0) at ../../../fs/specfs/spec_vnops.c:122 #10 0xc0455047 in ffs_sync (mp=0xc2b5ea00, waitfor=2, cred=0xc12b8e80, td=0xc05e2120) at vnode_if.h:627 #11 0xc037795b in sync (td=0xc05e2120, uap=0x0) at ../../../kern/vfs_syscalls.c:142 #12 0xc031aba0 in boot (howto=256) at ../../../kern/kern_shutdown.c:281 #13 0xc031b3d7 in panic () at ../../../kern/kern_shutdown.c:550 #14 0xc033fff0 in witness_lock (lock=0xc061b820, flags=8, file=0xc053cdcf vm/uma_core.c, line=1381) ---Type return to continue, or q return to quit--- at ../../../kern/subr_witness.c:610 #15 0xc031144a in _mtx_lock_flags (m=0xc12cd130, opts=0, file=0xc0579fec \t?S?\t, line=-1067337696) at ../../../kern/kern_mutex.c:336 #16 0xc047dd96 in uma_zalloc_arg (zone=0xc061b820, udata=0x0, flags=257) at ../../../vm/uma_core.c:1381 #17 0xc030f8b3 in malloc (size=3234049760, type=0xc089b300, flags=257) at ../../../vm/uma.h:229 #18 0xc086ae87 in os_alloc_mem () from /boot/kernel/nvidia.ko #19 0xc074a7fc in __nvsym00027 () from /boot/kernel/nvidia.ko #20 0xc08551d9 in __nvsym04619 () from /boot/kernel/nvidia.ko #21 0xc0855025 in __nvsym00709 () from /boot/kernel/nvidia.ko #22 0xc07da74f in __nvsym03562 () from /boot/kernel/nvidia.ko #23 0xc07d9731 in __nvsym03559 () from /boot/kernel/nvidia.ko #24 0xc081af2a in __nvsym00646 () from /boot/kernel/nvidia.ko #25 0xc074cbf7 in __nvsym00752 () from /boot/kernel/nvidia.ko #26 0xc074d929 in rm_isr_bh () from /boot/kernel/nvidia.ko #27 0xc086c418 in nvidia_intr () from /boot/kernel/nvidia.ko #28 0xc03075b2 in ithread_loop (arg=0xc29fa080) at ../../../kern/kern_intr.c:534 #29 0xc03065bf in fork_exit (callout=0xc0307430 ithread_loop, arg=0x0, frame=0x0) at ../../../kern/kern_fork.c:796 Abel Alejandro. - This mail sent through IMP: http://horde.org/imp/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mksnap_ffs, snapshot issues, again
Would it not be possible to make the snapshot file not appear in a directory until it si finished? (I know that would be 'wierd' but it would give a guaranteed solution.. On Sat, 23 Aug 2003, Kirk McKusick wrote: Robert Watson forwarded your posting to me as I am not as current on current as I should be. -- Forwarded message -- Date: Mon, 18 Aug 2003 22:38:47 +0200 From: [iso-8859-2] Branko F. Graènar [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: mksnap_ffs, snapshot issues, again I have 900G array on a promise sx6000 controller This is freshly formatted filesystem (newfs -L export -O 2 -U -g 48000 -i 2048 -m 0 -o space /dev/pst0s2d) # df -i /export /dev/pst0s2d 778742004 216194 778525810 0% 2 4451592920% /export # mount | grep export /dev/pst0s2d on /export (ufs, local, soft-updates) let's try to create a snapshot of empty filesystem # cd /export # mksnap_ffs /export aaa.snap ... after 30 minutes ... snapshot was not created (!!! On a empty filesystem !!!)... Ok, long snapshot creation would be fine if it would not hang all processes, which would like to do something on /export (ls /export for example.). Filesystem cannot be unmounted. mksnap_ffs process cannot be killed. Reboot and foreground fsck helps. This is 5.1-RELEASE (without patches, with custom kernel - just picked up generic kernel and removed uneeded stuff.) Any ideas, why is this happening? As i mentioned before, this prevents background fsck to make his job done (machine hangs.) I would really like to solve this issue Brane Discussion - Paul Saab kindly arranged a machine (tank.freebsd.org) with a 2Tb disk array on it for me to test. I enclose a copy of the `sysctl kern' output at the end of this message. I first ran my own test which involved creating a default configuration filesystem, taking a snapshot, and removing the snapshot. The scripted result is below. It shows that it takes 48 minutes to create the snapshot and 15 minutes to remove it. But importantly, it shows that the filesystem is only locked down and inaccessible for 0.042 seconds of that 48 minutes. The problem is that the 77,000 indirect blocks needed by the snapshot do not fit in the 300 kernel buffers allotted to it. So, every indirect block needs to be read and written approximately three times. Just to be sure that there was not something weird about your configuration, I also ran the same set of tests using your newfs parameters. Other than creating more cylinder groups the result (e.g., running time) was about the same. But, to get to the problem that you are having with accessing your filesystem. The problem is that although the filesystem is only locked briefly, the snapshot file is locked for the entire 48 minutes. Thus, if you touch the snapshot file (by for example doing a stat on it), then the process doing the stat will hang for 48 minutes. The next process to try and touch the snapshot will lock /export while it waits for the lock on the snapshot to clear. And at that point you are hosed for 48 minutes on all access to /export :-( So, I think that the best solution for you would be to try creating a hidden directory for the snapshot file, e.g., create a /export/.snap directory mode 700 owned by root, then create the snapshot as say /export/.snap/snap1. This way, it will be out of the way of all snoopy programs except those walking the filetree as root. Kirk McKusick Results of my test - Script started on Fri Aug 22 17:18:34 2003 tank# newfs /dev/twed0 /dev/twed0: 2097152.0MB (4294967292 sectors) block size 16384, fragment size 2048 using 11413 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, 3387328, 3763680, 4140032, 4516384, 4892736, 5269088, 5645440, 6021792, 6398144, 6774496, 7150848, 7527200, 7903552, 8279904, 8656256, 9032608, 9408960, 9785312, 10161664, 10538016, 10914368, 11290720, 11667072, 12043424, 12419776, 12796128, 13172480, 13548832, 13925184, 14301536, 14677888, 15054240, 15430592, 15806944, 16183296, 16559648, 16936000, 17312352, 17688704, 18065056, 18441408, 18817760, 19194112, 19570464, 19946816, 20323168, 20699520, 21075872, 21452224, 21828576, 22204928, 22581280, etc, etc, etc 4283638624, 4284014976, 4284391328, 4284767680, 4285144032, 4285520384, 4285896736, 4286273088, 4286649440, 4287025792, 4287402144, 4287778496, 4288154848, 4288531200, 4288907552, 4289283904, 4289660256, 4290036608, 4290412960, 4290789312, 4291165664, 4291542016, 4291918368, 4292294720, 4292671072, 4293047424, 4293423776, 4293800128, 4294176480, 4294552832, 4294929184 tank# dumpfs /dev/twed0 | head -22 magic 19540119 (UFS2) timeSat Aug 23 01:18:55
Re: HTT on current
On Fri, Aug 22, 2003 at 10:23:52PM -0400, [EMAIL PROTECTED] wrote: Well i've enabled all SMP options, recompiled and rebooted. The CPUs now properly show up in dmesg and i can see the C header in top. However no processes seem to be being assigned to cpu 1. Why is the schedueler only using CPU 0? This wasnt the behaviour in stable. Which scheduler? Please try to be as explicit as you can when sending bug reports. Kris The default BSD schedueler. All processes seem to be on CPU0 according to top. options SCHED_4BSD #4BSD scheduler ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Top in jails
On Fri, 22 Aug 2003, Rus Foster wrote: I'm playing with jail on FBSD5 and wondered if there was anyway I could use top without have to create /dev/mem. ATM anyone in the jail could just do cat /dev/mem | grep for_intresting_stuff. Any ideas? Tried using devfs and still no luck top should run fine without /dev/mem -- by default, it will use sysctl(), and isn't setgid kmem, so can't access /dev/mem by default, so isn't using it even outside jail. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HTT on current
Did you do sysctl machdep.hlt_logical_cpus=0? Default setting halt logical CPUs, and won't start HTT. This is a kind of FAQ, and you will see a lot in the past mailing-list. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HTT on current
+--- On Saturday, August 23, 2003 21:18, | [EMAIL PROTECTED] proclaimed: | | On Fri, Aug 22, 2003 at 10:23:52PM -0400, [EMAIL PROTECTED] wrote: | Well i've enabled all SMP options, recompiled and rebooted. The CPUs | now properly show up in dmesg and i can see the C header in top. | However no processes seem to be being assigned to cpu 1. Why is the | schedueler only using CPU 0? This wasnt the behaviour in stable. | | Which scheduler? Please try to be as explicit as you can when sending | bug reports. | | Kris | | The default BSD schedueler. All processes seem to be on CPU0 according to | top. | | options SCHED_4BSD #4BSD scheduler | Check the -current archives, especially around 2003-08-12, for messages with the subject Dual P4 2.4Ghz Xeon With Hyperthreading enabled. HINT: machdep.hlt_logical_cpus (note - I don't have a HTT machine, so I can't speak from experience, just from the content of this mailing list, reading it every day) -- +-+--+ | Michael W. Oliver, CCNP | The tree of liberty must be | | IPv6 FreeBSD mark | refreshed from time to time | | [EMAIL PROTECTED]| with the blood of patriots | | http://michael.gargantuan.com/| and tyrants.| | ASpath-tree, Looking Glass, etc. | - President Thomas Jefferson | | +--+ | gpg key - http://michael.gargantuan.com/gnupg/pubkey.asc | ++ pgp0.pgp Description: signature
Re: When this panic will be fixed?
On Saturday, 23 August 2003 at 5:05:11 -0700, Rostislav Krasny wrote: When FreeBSD 5.0-RELEASE had been released I tried to install it from floppies. I got system panic and then reported this problem into [EMAIL PROTECTED] mailing list. You can find this report in http://www.atm.tut.fi/list-archive/freebsd-stable/msg08385.html or in http://docs.freebsd.org/cgi/getmsg.cgi?fetch=297316+0+archive/2003/freebsd-stable/20030126.freebsd-stable FreeBSD-CURRENT is a some assembly required list. If you have a panic, you should post a backtrace and ask specific questions. Pointing to mail messages which don't even identify the panic string are not going to get much in the way of response. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: No sound output for pcm
Harald Schmalzbauer wrote: --Boundary-02=_Nn+R/bAN6Fk+pt3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline Hi all, I can confirm something is wrongwith pcm. I have no sound output with todays kernel, the one some weeks ago I had no= =20 problems. My sound is already working again, is yours? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: No sound output for pcm
On Sunday 24 August 2003 00:25, Harald Schmalzbauer wrote: Hi all, I can confirm something is wrongwith pcm. I have no sound output with todays kernel, the one some weeks ago I had no problems. Ok, things are fine again. I just cvsupped and saw that something AC97 related has changed. With the new kernel everything is working fine again. Thank you very much -Harry Here's my dmesg: pcm0: Creative CT5880-C port 0xd400-0xd43f irq 5 at device 13.0 on pci2 pcm0: SigmaTel STAC9708/11 AC97 Codec In /dev I have: dsp0.0 dsp0.1 dspW0.0 dspW0.1 dspr0.0 and mixer0 Cvsupped today at about 20:00 UTC Please let me know how I can help testing. -Harry pgp0.pgp Description: signature
Re: System freezes with radeon 9100 graphics card
On Sat, Aug 23, 2003 at 02:11:15PM -0500, Glenn Johnson wrote: I have had an ongoing problem with -current freezing during a restart of the X serer. The graphics card is an ATI Radeon 9100. I am pretty sure this is related to DRI as I have not had it happen with DRI disabled. I am not sure if the problem is with the radeon kernel module, with XFree86-Server, or something else. The freezes totally lock up the machine, no ssh access is possible, no crash dumps are produced, I have to hit the reset button and run fsck in single user mode. Is anyone else seeing this with a radeon card? Any options I can set to alleviate the problem? I going to turn on DRM_DEBUG and see what that yields. Thanks. Some more info: I get the following error messages when the X server starts: drm0: ATI Radeon QM R200 9100 port 0x9000-0x90ff mem 0xf900-0xf900,0xe000-0xefff irq 2 at device 0.0 on pci1 info: [drm] Initialized radeon 1.9.0 20020828 on minor 0 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:radeon_unlock] *ERROR* Process 579 using kernel context 0 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:radeon_unlock] *ERROR* Process 738 using kernel context 0 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:radeon_unlock] *ERROR* Process 865 using kernel context 0 -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System freezes with radeon 9100 graphics card
On Sat, 2003-08-23 at 20:38, Glenn Johnson wrote: On Sat, Aug 23, 2003 at 02:11:15PM -0500, Glenn Johnson wrote: I have had an ongoing problem with -current freezing during a restart of the X serer. The graphics card is an ATI Radeon 9100. I am pretty sure this is related to DRI as I have not had it happen with DRI disabled. I am not sure if the problem is with the radeon kernel module, with XFree86-Server, or something else. The freezes totally lock up the machine, no ssh access is possible, no crash dumps are produced, I have to hit the reset button and run fsck in single user mode. Is anyone else seeing this with a radeon card? Any options I can set to alleviate the problem? I going to turn on DRM_DEBUG and see what that yields. Thanks. Some more info: I get the following error messages when the X server starts: drm0: ATI Radeon QM R200 9100 port 0x9000-0x90ff mem 0xf900-0xf900,0xe000-0xefff irq 2 at device 0.0 on pci1 info: [drm] Initialized radeon 1.9.0 20020828 on minor 0 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:radeon_unlock] *ERROR* Process 579 using kernel context 0 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:radeon_unlock] *ERROR* Process 738 using kernel context 0 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:radeon_unlock] *ERROR* Process 865 using kernel context 0 I might suggest to you that you try the DRI lists... see http://dri.sf.net or email [EMAIL PROTECTED] Also please teach your email client to word wrap. That's nasty. -- signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System freezes with radeon 9100 graphics card
On Sat, Aug 23, 2003 at 09:40:55PM -0700, Scott M. Likens wrote: On Sat, 2003-08-23 at 20:38, Glenn Johnson wrote: On Sat, Aug 23, 2003 at 02:11:15PM -0500, Glenn Johnson wrote: I have had an ongoing problem with -current freezing during a restart of the X serer. The graphics card is an ATI Radeon 9100. I am pretty sure this is related to DRI as I have not had it happen with DRI disabled. I am not sure if the problem is with the radeon kernel module, with XFree86-Server, or something else. The freezes totally lock up the machine, no ssh access is possible, no crash dumps are produced, I have to hit the reset button and run fsck in single user mode. Is anyone else seeing this with a radeon card? Any options I can set to alleviate the problem? I going to turn on DRM_DEBUG and see what that yields. Thanks. Some more info: I get the following error messages when the X server starts: drm0: ATI Radeon QM R200 9100 port 0x9000-0x90ff mem 0xf900-0xf900,0xe000-0xefff irq 2 at device 0.0 on pci1 info: [drm] Initialized radeon 1.9.0 20020828 on minor 0 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:radeon_unlock] *ERROR* Process 579 using kernel context 0 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:radeon_unlock] *ERROR* Process 738 using kernel context 0 error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:radeon_unlock] *ERROR* Process 865 using kernel context 0 I might suggest to you that you try the DRI lists... see http://dri.sf.net or email [EMAIL PROTECTED] I have, to the first. Also please teach your email client to word wrap. That's nasty. My e-mail client knows how to word wrap. The unwrapped part above was from command output, which should *not* be wrapped, to maintain integrity of the output. If you saw more than one line that was not wrapped then I submit that there is something wrong with your e-mail client. -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: access to snapshot?
snapshot.jp.freebsd.org and jp.freebsd.org do not permit anonymous logins. there is also snapshots.se.freebsd.org, although our current buildslave is currently under maintinance and will not be back up again until wednesday next week. and we do allow anonymous logins Matt www.fruitsalad.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System freezes with radeon 9100 graphics card
At 9:40 PM -0700 2003/08/23, Scott M. Likens wrote: Also please teach your email client to word wrap. That's nasty. According to your headers, you're using Ximian Evolution 1.4.4. According to his headers, he's running Mutt/1.5.4i. You tell me. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Are you running up do date -current, or is there anything strange about your setup at all? Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote: On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Right, that is a valuable datapoint. Are you running up do date -current, or is there anything strange about your setup at all? Not that I know, but given that it works for another P4P800 I can find out what is special locally. W/ -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
Stuart Walsh wrote: On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Hi Guys, I have 2 machines with P4P800-Deluxe with the 3C940. If phk@ could fix the swap-issue, so that I can reboot easily, I would test your patches, too. Jens ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
ATAng has just been committed. You need to make world after this update as atacontrol etc needs to pick up the changes. Coolness. Judging from the CVS log, it also gets ATA out under Giant? That should make ATA-run SMP boxes eligible for an impressive increase in I/O performance... has anyone noticed? Regards, Roderick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote: On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: ... Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Are you running up do date -current, or is there anything strange about your setup at all? I just did a buildworld on a freshly checked out tree, applied the patches and tried again. Unfortunately that did not help. I continue my investigation. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
It seems Roderick van Domburg wrote: ATAng has just been committed. You need to make world after this update as atacontrol etc needs to pick up the changes. Coolness. Judging from the CVS log, it also gets ATA out under Giant? Yes it does. That should make ATA-run SMP boxes eligible for an impressive increase in I/O performance... has anyone noticed? Depends alot on what you are doing.. -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
I have just cvsup'd and done a full buildworld/kernel and on reboot had a kernel panic. Unfortunatly I do not have ddb or anything compiled into the kernel but I can sort this out and get a proper backtrace etc if you don't immediatly know what's wrong. I have the following hardware: ad0: 76319MB ST380020A [155061/16/63] at ata0-master UDMA100 acd0: DVD-ROM Compaq DVD-ROM SD-616T at ata1-master PIO4 acd1: CD-RW SAMSUNG CD-R/RW SW-240B at ata1-slave PIO4 This did work perfectly with the old ATA, but the new ATA panic's. I have found that it is due to having device atapicam for the SCSI emulation. If I recompile the kernel with this option commented out the kernel boots and everything works normally (except the SCSI emulation). If you need a full panic message and backtrace then I will recompile it with debugging options enabled and get one for you. Matt. -- email: [EMAIL PROTECTED] - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
It seems Matt wrote: I have just cvsup'd and done a full buildworld/kernel and on reboot had a kernel panic. Unfortunatly I do not have ddb or anything compiled into the kernel but I can sort this out and get a proper backtrace etc if you don't immediatly know what's wrong. I have the following hardware: ad0: 76319MB ST380020A [155061/16/63] at ata0-master UDMA100 acd0: DVD-ROM Compaq DVD-ROM SD-616T at ata1-master PIO4 acd1: CD-RW SAMSUNG CD-R/RW SW-240B at ata1-slave PIO4 This did work perfectly with the old ATA, but the new ATA panic's. I have found that it is due to having device atapicam for the SCSI emulation. If I recompile the kernel with this option commented out the kernel boots and everything works normally (except the SCSI emulation). If you need a full panic message and backtrace then I will recompile it with debugging options enabled and get one for you. This is a case for Thomas I guess, atapicam is his baby I just allow it to be around :) -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
On Sun, 24 Aug 2003, Matt wrote: This did work perfectly with the old ATA, but the new ATA panic's. I have found that it is due to having device atapicam for the SCSI emulation. If I recompile the kernel with this option commented out the kernel boots and everything works normally (except the SCSI emulation). I can confirm that atapicam causes my system to hang, but not panic, on boot where the kernel would normally be detecting cd0. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
It seems Wesley Morgan wrote: On Sun, 24 Aug 2003, Matt wrote: This did work perfectly with the old ATA, but the new ATA panic's. I have found that it is due to having device atapicam for the SCSI emulation. If I recompile the kernel with this option commented out the kernel boots and everything works normally (except the SCSI emulation). I can confirm that atapicam causes my system to hang, but not panic, on boot where the kernel would normally be detecting cd0. As I said give Thomas a chance to get things sorted out with atapicam.. -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE Konsole, crashes, on a SIGABRT...
On Saturday 23 August 2003 18:03, Daniel Eischen wrote: On Sat, 23 Aug 2003, Larry Rosenman wrote: --On Saturday, August 23, 2003 10:27:59 -0400 Daniel Eischen (...) We (threads guys) think it's a problem with konsole. It is trying to change ownership of the pty and is failing to do so. We don't know why. Sometimes it works, sometimes it doesn't. konsole aborts itself when it can't change/open the pty, so SIGABRT is expected. Interestingly, if I use /etc/libmap.conf to map libc_r.(so|so.5) to libc_r.(so.4|so.4) it works starting from within an XTerm, but not from the bar at the bottom. Now, I have **NOT** rebooted yet. This seems to have started with thursday's world, the previous world was ~2 weeks ago. Prior to Thursday, it worked just fine. I can't explain it. Someone is going to have to debug konsole and figure out what is going on. It is a problem that has appeared in the last two weeks, and it was triggered by a change in (apparently) libc_r as well as libkse, as it doesn't start with both now. With the patch that Michael Nottebrock provided on this list, it was perfectly possible to run Konsole with libkse (and libc_r) on a -CURRENT from august 15. So something was broken in the threads code between august 15 and now. I don't think that we should point to Konsole here, something went wrong in the threads code. Best regards, Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
On Sun, Aug 24, 2003 at 11:27:05AM +0200, Soren Schmidt wrote: ATAng has just been committed. You need to make world after this update as atacontrol etc needs to pick up the changes. Does ATAng still kill various Seagate drives? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
On Sun, 24 Aug 2003, Soren Schmidt wrote: It seems Matt wrote: I have just cvsup'd and done a full buildworld/kernel and on reboot had a kernel panic. Unfortunatly I do not have ddb or anything compiled into the kernel but I can sort this out and get a proper backtrace etc if you don't immediatly know what's wrong. I have the following hardware: ad0: 76319MB ST380020A [155061/16/63] at ata0-master UDMA100 acd0: DVD-ROM Compaq DVD-ROM SD-616T at ata1-master PIO4 acd1: CD-RW SAMSUNG CD-R/RW SW-240B at ata1-slave PIO4 This did work perfectly with the old ATA, but the new ATA panic's. I have found that it is due to having device atapicam for the SCSI emulation. If I recompile the kernel with this option commented out the kernel boots and everything works normally (except the SCSI emulation). If you need a full panic message and backtrace then I will recompile it with debugging options enabled and get one for you. This is a case for Thomas I guess, atapicam is his baby I just allow it to be around :) I appreciate all the work you've done for ATA. But that said, atapicam has been present for a while, and it should have been tested and made to work -- at least so it doesn't panic the system -- before committing ATAng. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
It seems David O'Brien wrote: On Sun, Aug 24, 2003 at 11:27:05AM +0200, Soren Schmidt wrote: ATAng has just been committed. You need to make world after this update as atacontrol etc needs to pick up the changes. Does ATAng still kill various Seagate drives? Uhm ? what do you mean by that ? The only problem I know of with Seagates is with a certain 40G model and that I can't reproduce here with ATAng actually.. -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
It seems Daniel Eischen wrote: This is a case for Thomas I guess, atapicam is his baby I just allow it to be around :) I appreciate all the work you've done for ATA. But that said, atapicam has been present for a while, and it should have been tested and made to work -- at least so it doesn't panic the system -- before committing ATAng. And that is axactly the case, this is what I've got from Thomas and that should have been tested etc etc.. -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
On Sun, 24 Aug 2003, Soren Schmidt wrote: It seems Daniel Eischen wrote: This is a case for Thomas I guess, atapicam is his baby I just allow it to be around :) I appreciate all the work you've done for ATA. But that said, atapicam has been present for a while, and it should have been tested and made to work -- at least so it doesn't panic the system -- before committing ATAng. And that is axactly the case, this is what I've got from Thomas and that should have been tested etc etc.. OK, I guess I missed that. Sorry for the repeated response. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE Konsole, crashes, on a SIGABRT...
On Sun, 24 Aug 2003, Arjan van Leeuwen wrote: On Saturday 23 August 2003 18:03, Daniel Eischen wrote: On Sat, 23 Aug 2003, Larry Rosenman wrote: --On Saturday, August 23, 2003 10:27:59 -0400 Daniel Eischen (...) We (threads guys) think it's a problem with konsole. It is trying to change ownership of the pty and is failing to do so. We don't know why. Sometimes it works, sometimes it doesn't. konsole aborts itself when it can't change/open the pty, so SIGABRT is expected. Interestingly, if I use /etc/libmap.conf to map libc_r.(so|so.5) to libc_r.(so.4|so.4) it works starting from within an XTerm, but not from the bar at the bottom. Now, I have **NOT** rebooted yet. This seems to have started with thursday's world, the previous world was ~2 weeks ago. Prior to Thursday, it worked just fine. I can't explain it. Someone is going to have to debug konsole and figure out what is going on. It is a problem that has appeared in the last two weeks, and it was triggered by a change in (apparently) libc_r as well as libkse, as it doesn't start with both now. With the patch that Michael Nottebrock provided on this list, it was perfectly possible to run Konsole with libkse (and libc_r) on a -CURRENT from august 15. Are you saying that with Michael's patch and post August 15th libraries it doesn't work? So something was broken in the threads code between august 15 and now. I don't think that we should point to Konsole here, something went wrong in the threads code. Nothing has been touched in libc_r in over 4 weeks. I maintain that it is a konsole (grantpty) problem. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
In message [EMAIL PROTECTED], Jens Rehsack writes: I have 2 machines with P4P800-Deluxe with the 3C940. If phk@ could fix the swap-issue, so that I can reboot easily, I would test your patches, too. swap-issue ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HTT on current
On Sun, Aug 24, 2003 at 01:06:28PM -0300, Marc G. Fournier wrote: ganymede# sysctl machdep.hlt_logical_cpus sysctl: unknown oid 'machdep.hlt_logical_cpus' ganymede# uname -a FreeBSD ganymede.hub.org 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Sat Aug 23 00:08:54 ADT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/kernel i386 Is this a SMP kernel? ports-i386%uname -a FreeBSD dosirak.kr.freebsd.org 5.1-CURRENT FreeBSD 5.1-CURRENT #8: Sat Aug 9 15:43:12 KST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/DOSIRAK i386 ports-i386%sysctl machdep.hlt_logical_cpus machdep.hlt_logical_cpus: 1 Kris pgp0.pgp Description: PGP signature
Re: KDE Konsole, crashes, on a SIGABRT...
Arjan van Leeuwen wrote: On Saturday 23 August 2003 18:03, Daniel Eischen wrote: On Sat, 23 Aug 2003, Larry Rosenman wrote: --On Saturday, August 23, 2003 10:27:59 -0400 Daniel Eischen (...) We (threads guys) think it's a problem with konsole. It is trying to change ownership of the pty and is failing to do so. We don't know why. Sometimes it works, sometimes it doesn't. konsole aborts itself when it can't change/open the pty, so SIGABRT is expected. Interestingly, if I use /etc/libmap.conf to map libc_r.(so|so.5) to libc_r.(so.4|so.4) it works starting from within an XTerm, but not from the bar at the bottom. Now, I have **NOT** rebooted yet. This seems to have started with thursday's world, the previous world was ~2 weeks ago. Prior to Thursday, it worked just fine. I can't explain it. Someone is going to have to debug konsole and figure out what is going on. It is a problem that has appeared in the last two weeks, and it was triggered by a change in (apparently) libc_r as well as libkse, as it doesn't start with both now. With the patch that Michael Nottebrock provided on this list, it was perfectly possible to run Konsole with libkse (and libc_r) on a -CURRENT from august 15. So something was broken in the threads code between august 15 and now. I don't think that we should point to Konsole here, something went wrong in the threads code. Konsole_grantpty was using a buggy hack, which worked because of a bug in libc_r. Maybe the bug in libc_r was fixed, thereby making it work like libkse and libthr (ie, crashing konsole). Fix: remove konsole_grantpty. If that does not work, just tell me and I'll eat my own hat. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Steele: Aha! We've finally got you talking jargon too! Stallman: What did he say? Steele: Bob just used canonical in the canonical way. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GCC 3.3.1-RELEASE is coming
On Fri, Aug 22, 2003 at 06:59:20PM -0500, Loren James Rittle wrote:
Trying to consider how to best pull important differences back into
the FSF tree. Will this be true for all FreeBSD systems going forward?
%{!dynamic-linker:-dynamic-linker /usr/libexec/ld-elf.so.1}}
---
%{!dynamic-linker:-dynamic-linker /libexec/ld-elf.so.1}}
BTW, it seems to be inconsistent for the various CPUs in the system
compiler (e.g. missed in ia64).
Yes it will be true going forward. ia64 was skipped because it was on
the vendor branch and I haven't yet created a FSF submittable patch for
you. :-)
What is the official trigger point of
the change in the system? Given the nature of the change, may I
assume that a transition period exists during all of FreeBSD 5?
It will be in my patch to you.
Regarding this thunk, also in config/alpha/freebsd.h (not in FSF but
in my mainline tree with a slightly less hostile comment):
The FSF was hostile towards FreeBSD/alpha -- the favor is being
returned. I pointed out the problem and got I dont' care from them.
/* Reset our STARTFILE_SPEC which was properly set in config/freebsd.h
but trashed by config/cpu/file.h. */
#undef STARTFILE_SPEC
#define STARTFILE_SPEC FBSD_STARTFILE_SPEC
That said, good catch! I don't know why I didn't do it that way before.
Committed to FreeBSD tree.
I will install patches in the FSF tree for these issues to both
mainline and 3.3.X branch.
Thank you. Can you also sync up the code style from FreeBSD into the FSF
tree?
Speaking of config/i386/freebsd.h, the difference against the FSF tree
is quite large but most of it is not required anymore. The difference
in all other config/cpu/freebsd.h files is only a line or two. If I
proposed a /usr/src/contrib/gcc/ diff such that it produced the exact
same system compiler yet was the smallest delta from the FSF tree,
would you be interested? I'd like to get that difference down to make
it easiler to spot real differences going forward.
I would like the differences to be taken care of in the FSF tree. You
know the reason there is such a large diff (and it really irritates me).
Because of that reason committing the changes into the FSF tree has been
too high a PITA. I had hoped you would take a diff from FreeBSD's
src/contrib/gcc to the FSF tree and commit it to the FSF tree.
--
-- David ([EMAIL PROTECTED])
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE Konsole, crashes, on a SIGABRT...
On Sunday 24 August 2003 18:55, Daniel C. Sobral wrote: Arjan van Leeuwen wrote: On Saturday 23 August 2003 18:03, Daniel Eischen wrote: On Sat, 23 Aug 2003, Larry Rosenman wrote: --On Saturday, August 23, 2003 10:27:59 -0400 Daniel Eischen (...) We (threads guys) think it's a problem with konsole. It is trying to change ownership of the pty and is failing to do so. We don't know why. Sometimes it works, sometimes it doesn't. konsole aborts itself when it can't change/open the pty, so SIGABRT is expected. Interestingly, if I use /etc/libmap.conf to map libc_r.(so|so.5) to libc_r.(so.4|so.4) it works starting from within an XTerm, but not from the bar at the bottom. Now, I have **NOT** rebooted yet. This seems to have started with thursday's world, the previous world was ~2 weeks ago. Prior to Thursday, it worked just fine. I can't explain it. Someone is going to have to debug konsole and figure out what is going on. It is a problem that has appeared in the last two weeks, and it was triggered by a change in (apparently) libc_r as well as libkse, as it doesn't start with both now. With the patch that Michael Nottebrock provided on this list, it was perfectly possible to run Konsole with libkse (and libc_r) on a -CURRENT from august 15. So something was broken in the threads code between august 15 and now. I don't think that we should point to Konsole here, something went wrong in the threads code. Konsole_grantpty was using a buggy hack, which worked because of a bug in libc_r. Maybe the bug in libc_r was fixed, thereby making it work like libkse and libthr (ie, crashing konsole). Fix: remove konsole_grantpty. If that does not work, just tell me and I'll eat my own hat. kde@, has already found the problem. Turns out konsole will crash in recent -CURRENT (post-15 august) if you have a hostname longer than 16 characters because of a change in gethostname (I guess). Sorry to point at threads@ :). So, to have a working Konsole at this moment with libkse, you have to get Michael's patch and a hostname shorter than 16 characters. Best regards, Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[current tinderbox] failure on alpha/alpha
TB --- 2003-08-24 16:00:01 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-08-24 16:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-08-24 16:01:54 - building world TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. TB --- 2003-08-24 17:08:29 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Sun Aug 24 17:08:30 GMT 2003 [...] awk -f /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/tools/makeobjops.awk /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/alpha/alpha/clock_if.m -h awk -f /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/tools/makeobjops.awk /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/alpha/pci/alphapci_if.m -h awk -f /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/tools/makeobjops.awk /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/dec/mcclock_if.m -h if [ -f .olddep ]; then mv .olddep .depend; fi rm -f .newdep /usr/bin/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES | MKDEP_CPP=cc -E CC=cc xargs mkdep -a -f .newdep -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/dev/syscons/scgfbrndr.c:34:25: opt_creator.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. TB --- 2003-08-24 17:09:22 - /usr/bin/make returned exit code 1 TB --- 2003-08-24 17:09:22 - ERROR: failed to build generic kernel TB --- 2003-08-24 17:09:22 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE Konsole, crashes, on a SIGABRT...
--On Sunday, August 24, 2003 19:06:52 +0200 Arjan van Leeuwen [EMAIL PROTECTED] wrote: kde@, has already found the problem. Turns out konsole will crash in recent -CURRENT (post-15 august) if you have a hostname longer than 16 characters because of a change in gethostname (I guess). Sorry to point at threads@ :). So, to have a working Konsole at this moment with libkse, you have to get Michael's patch and a hostname shorter than 16 characters. Is there a patch for this? my hostname (lerlaptop.lerctr.org or lerlaptop.iadfw.net or lerlaptop-red.iadfw.net) are all too long :-(. Thanks for tracking this down. LER Best regards, Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE Konsole, crashes, on a SIGABRT...
--On Sunday, August 24, 2003 12:11:20 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: --On Sunday, August 24, 2003 19:06:52 +0200 Arjan van Leeuwen [EMAIL PROTECTED] wrote: kde@, has already found the problem. Turns out konsole will crash in recent -CURRENT (post-15 august) if you have a hostname longer than 16 characters because of a change in gethostname (I guess). Sorry to point at threads@ :). So, to have a working Konsole at this moment with libkse, you have to get Michael's patch and a hostname shorter than 16 characters. Is there a patch for this? my hostname (lerlaptop.lerctr.org or lerlaptop.iadfw.net or lerlaptop-red.iadfw.net) are all too long :-(. Thanks for tracking this down. Oh, and even without Michael's patch, changing my hostname to lerlaptop, allows Konsole to run. LER Best regards, Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE Konsole, crashes, on a SIGABRT...
On Sunday 24 August 2003 19:17, Larry Rosenman wrote: --On Sunday, August 24, 2003 12:11:20 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: --On Sunday, August 24, 2003 19:06:52 +0200 Arjan van Leeuwen [EMAIL PROTECTED] wrote: kde@, has already found the problem. Turns out konsole will crash in recent -CURRENT (post-15 august) if you have a hostname longer than 16 characters because of a change in gethostname (I guess). Sorry to point at threads@ :). So, to have a working Konsole at this moment with libkse, you have to get Michael's patch and a hostname shorter than 16 characters. Is there a patch for this? my hostname (lerlaptop.lerctr.org or lerlaptop.iadfw.net or lerlaptop-red.iadfw.net) are all too long :-(. Thanks for tracking this down. Oh, and even without Michael's patch, changing my hostname to lerlaptop, allows Konsole to run. With libc_r or with libkse? It used to crash with libkse without Michael's patch. LER Best regards, Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE Konsole, crashes, on a SIGABRT...
--On Sunday, August 24, 2003 19:20:07 +0200 Arjan van Leeuwen [EMAIL PROTECTED] wrote: On Sunday 24 August 2003 19:17, Larry Rosenman wrote: --On Sunday, August 24, 2003 12:11:20 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: --On Sunday, August 24, 2003 19:06:52 +0200 Arjan van Leeuwen [EMAIL PROTECTED] wrote: kde@, has already found the problem. Turns out konsole will crash in recent -CURRENT (post-15 august) if you have a hostname longer than 16 characters because of a change in gethostname (I guess). Sorry to point at threads@ :). So, to have a working Konsole at this moment with libkse, you have to get Michael's patch and a hostname shorter than 16 characters. Is there a patch for this? my hostname (lerlaptop.lerctr.org or lerlaptop.iadfw.net or lerlaptop-red.iadfw.net) are all too long :-(. Thanks for tracking this down. Oh, and even without Michael's patch, changing my hostname to lerlaptop, allows Konsole to run. With libc_r or with libkse? It used to crash with libkse without Michael's patch. libc_r. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
Hello. (B (BI was update 5-current and begin using with ATAng and ust view ata-pci.c. (BThen I found one question in the source code. (B (Bata-pci.c 462 line. (BDEVMETHOD(device_detach,ata_pci_attach), (B (BIs this right? (BI think, it should be use "ata_pci_dettach" or something, but I cannot found (Bthe function. (B (B-- (BHiroyuki Aizu (B (B (BOn Sun, 24 Aug 2003 11:27:05 +0200 (CEST) (BSoren Schmidt [EMAIL PROTECTED] wrote: (B (B (B ATAng has just been committed. You need to make world after this update (B as atacontrol etc needs to pick up the changes. (B (B -S$Bxr(Ben (B ___ (B [EMAIL PROTECTED] mailing list (B http://lists.freebsd.org/mailman/listinfo/freebsd-current (B To unsubscribe, send any mail to "[EMAIL PROTECTED]" (B (B (B (B (B (B___ (B[EMAIL PROTECTED] mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-current (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP! ATAng committed
It seems Hiroyuki Aizu wrote: Hello. I was update 5-current and begin using with ATAng and ust view ata-pci.c. Then I found one question in the source code. ata-pci.c 462 line. DEVMETHOD(device_detach,ata_pci_attach), Is this right? I think, it should be use ata_pci_dettach or something, but I cannot found the function. Just remove that line pci ATA device cannot be detached as is.. -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Ion startup error in 5.1-current
Every time I start up ion-devel I get an xmessage stating: Drawing Engine /usr/X11R6/lib/ion-devel/de.la not registered! Stack trace: 0 [C]: in 'gr_select_engine' 1 /usr/X11R6/etc/ion-devel/draw.lua:6 [Skipping unnamed C function.] I can click okay and everything seems fine, but when I set draw.lua as a link to another theme, the theme doesn't work. I am not sure if these two problems are connected, but I've done everything I can to fix this error and I can't get it to stop. Any suggestions? Mike Michael J. Goffin Computer Science House Applied Networking and System Administration Rochester Institute of Technology http://www.csh.rit.edu/~neo [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
recover superblock
Hi, I just lost all of my filesystems on my 5.1 box. I was running mnogosearch's indexer on my website while several errors occured. I guess there were 320 of these errors, cause the last message was last message repeated 320 times. Unfortunately /var is lost as well, so I don't have more error messages. kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 23536, size: 4096 kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting kernel: ata0: resetting devices .. kernel: done kernel: bad block 4190320178290426368, ino 402986 kernel: pid 42 (syncer), uid 0 inumber 402986 on /usr: bad block I decided to reboot into singleuser and run fsck. I noticed, that the buffers couldn't be flushed before restarting and the system couldn't boot. It said: not ufs I plugged the harddisk into another computer and tried to run fsck. It couldn't find a superblock, used an alternative one and coredumped while trying to repair the first error. Before dumping, it said something like Couldnt allocate 39 bytes for inoinfo. I can only remember the value of around 3.9G. This happened on all filesystems of ad0. I could mount the filesystem but not access it, but df said: Used: -2.8T (on a 40G disk). I surrendered on that and ran newfs. I don't know why, but fsck works on ad1. fsck said something like softupdate inconsistency while trying to repair the filesystem which obviously didn't completely work. # fsck /dev/ad1s1e ** /dev/ad1s1e Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19093 files, 42115174 used, 33631703 free (6471 frags, 4203154 blocks, 0.0% fragmentation) # mount /dev/ad1s1e /mnt/ mount: /dev/ad1s1e on /mnt: incorrect super block same thing using fsck -b 32 or any other alternative Google somewhere advised to use tunefs, but: # tunefs -A /dev/ad1s1e tunefs: /dev/ad1s1e: could not read superblock to fill out disk Even trying to copy an alternate superblock using dd faied. Do you have any ideas, how I could recover the data on this disk ? Cheers, Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
On Sun, 24 Aug 2003 21:26:11 +0200, Thomas Gutzler [EMAIL PROTECTED] wrote: Hi, I just lost all of my filesystems on my 5.1 box. I was running mnogosearch's indexer on my website while several errors occured. I guess there were 320 of these errors, cause the last message was last message repeated 320 times. Unfortunately /var is lost as well, so I don't have more error messages. kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 23536, size: 4096 kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting kernel: ata0: resetting devices .. kernel: done kernel: bad block 4190320178290426368, ino 402986 kernel: pid 42 (syncer), uid 0 inumber 402986 on /usr: bad block I decided to reboot into singleuser and run fsck. I noticed, that the buffers couldn't be flushed before restarting and the system couldn't boot. It said: not ufs I plugged the harddisk into another computer and tried to run fsck. It couldn't find a superblock, used an alternative one and coredumped while trying to repair the first error. Before dumping, it said something like Couldnt allocate 39 bytes for inoinfo. I can only remember the value of around 3.9G. This happened on all filesystems of ad0. I could mount the filesystem but not access it, but df said: Used: -2.8T (on a 40G disk). I surrendered on that and ran newfs. I don't know why, but fsck works on ad1. fsck said something like softupdate inconsistency while trying to repair the filesystem which obviously didn't completely work. I have lost over 1,000 to 2,000 emails like three times when the Nvidia driver crashed and had to do the power off and on to get it boot to let the fsck background do the job. Yesterday, I CVSup'ed and did the buildworld to update my -CURRENT. I got panic and reboot; first time I see the same message above, 'softupdate inconsistency' and I had to ran fsck by manual. After that, I discovered that my /var/, /compat/linux/ and very little stuff in my home directory have been destroyed. I can't produce the panic anymore so can't really give any help that much now; it was only panic at once for unknown reason. Just want to add in here that you aren't only person in here. Cheers, Mezz # fsck /dev/ad1s1e ** /dev/ad1s1e Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19093 files, 42115174 used, 33631703 free (6471 frags, 4203154 blocks, 0.0% fragmentation) # mount /dev/ad1s1e /mnt/ mount: /dev/ad1s1e on /mnt: incorrect super block same thing using fsck -b 32 or any other alternative Google somewhere advised to use tunefs, but: # tunefs -A /dev/ad1s1e tunefs: /dev/ad1s1e: could not read superblock to fill out disk Even trying to copy an alternate superblock using dd faied. Do you have any ideas, how I could recover the data on this disk ? Cheers, Tom -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
On Sun, 24 Aug 2003, Jeremy Messenger wrote: On Sun, 24 Aug 2003 21:26:11 +0200, Thomas Gutzler [EMAIL PROTECTED] wrote: I have lost over 1,000 to 2,000 emails like three times when the Nvidia driver crashed and had to do the power off and on to get it boot to let the fsck background do the job. Yesterday, I CVSup'ed and did the buildworld to update my -CURRENT. I got panic and reboot; first time I see the same message above, 'softupdate inconsistency' and I had to ran fsck by manual. After that, I discovered that my /var/, /compat/linux/ and very little stuff in my home directory have been destroyed. I can't produce the panic anymore so can't really give any help that much now; it was only panic at once for unknown reason. Just want to add in here that you aren't only person in here. I don't have a solution for you, but I have some sound advice: Don't run critical systems on -current. I consider email to fall in that category... Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recover superblock
On Sun, 24 Aug 2003 15:53:26 -0400 (EDT), Andre Guibert de Bruet [EMAIL PROTECTED] wrote: On Sun, 24 Aug 2003, Jeremy Messenger wrote: On Sun, 24 Aug 2003 21:26:11 +0200, Thomas Gutzler [EMAIL PROTECTED] wrote: I have lost over 1,000 to 2,000 emails like three times when the Nvidia driver crashed and had to do the power off and on to get it boot to let the fsck background do the job. Yesterday, I CVSup'ed and did the buildworld to update my -CURRENT. I got panic and reboot; first time I see the same message above, 'softupdate inconsistency' and I had to ran fsck by manual. After that, I discovered that my /var/, /compat/linux/ and very little stuff in my home directory have been destroyed. I can't produce the panic anymore so can't really give any help that much now; it was only panic at once for unknown reason. Just want to add in here that you aren't only person in here. I don't have a solution for you, but I have some sound advice: Don't run critical systems on -current. I consider email to fall in that category... I am pretty aware of it and I don't care of those are lost because I always backup my personal stuff daily. I run everything in bleed edge such as - CURRENT, Gnome 2.4, VIM-cvs and etc, so I know my risk. Cheers, Mezz Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ -- bsdforums.org 's moderator, mezz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System freezes with radeon 9100 graphics card
Brad Knowles wrote: At 9:40 PM -0700 2003/08/23, Scott M. Likens wrote: Also please teach your email client to word wrap. That's nasty. According to your headers, you're using Ximian Evolution 1.4.4. According to his headers, he's running Mutt/1.5.4i. You tell me. When Microsoft started shipping mail clients that didn't wrap words by default, I was also pissed. But that was many moons ago (10 years maybe?). But at this point, anyone still using a mail client that doesn't know how to deal with this is living in the past. And no amount of complaining that this isn't what was intended by the RFCs is going to change this. This is just my humble opinion. Richard Coleman [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
atang problem: my cdrw isn't detected
After I rebooted from a make world, I found that my dvdrom device now occupies /dev/acd0 instead of /dev/acd1 and my plextor 8/4/32A is nowhere to be seen. Here's a snippet from my last good boot: ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 29314MB IBM-DTLA-307030 [59560/16/63] at ata0-master UDMA100 acd0: CD-RW PLEXTOR CD-R PX-W8432T at ata1-master PIO4 acd1: DVD-ROM HITACHI DVD-ROM GD-7500 at ata1-slave PIO4 cd0 at ata1 bus 0 target 0 lun 0 cd0: PLEXTOR CD-R PX-W8432T 1.09 Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c losed cd1 at ata1 bus 0 target 1 lun 0 cd1: HITACHI DVD-ROM GD-7500 0005 Removable CD-ROM SCSI-0 device cd1: 16.000MB/s transfers cd1: cd present [263133 x 2048 byte records] After commenting out the atapicam and scsi devices and then upgrading, I booted up o.k, but this is what I'm left with: #atacontrol list ATA channel 0: Master: ad0 IBM-DTLA-307030/TX4OA5AA ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: \xff \xff \xff \xff \xff \xff \xff \xff \xff \xff \xff \xff \x ff \xff \xff \xff \xff \xff \xff \xff/\xff \xff \xff \xff ATA/ATAPI rev 15 Slave: acd0 HITACHI DVD-ROM GD-7500/0005 ATA/ATAPI rev 0 #dmesg Copyright (c) 1992-2003 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.1-CURRENT #17: Sun Aug 24 15:16:41 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARL5KERNEL Preloaded elf kernel /boot/kernel/kernel at 0xc04e2000. Preloaded elf module /boot/kernel/vesa.ko at 0xc04e221c. Preloaded elf module /boot/kernel/miibus.ko at 0xc04e22c8. Preloaded elf module /boot/kernel/if_sis.ko at 0xc04e2374. Preloaded elf module /boot/kernel/if_xl.ko at 0xc04e2420. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04e24cc. Preloaded elf module /boot/kernel/snd_es137x.ko at 0xc04e2578. Preloaded elf module /boot/kernel/usb.ko at 0xc04e2628. Preloaded elf module /boot/kernel/ums.ko at 0xc04e26d0. Preloaded elf module /boot/kernel/agp.ko at 0xc04e2778. Preloaded elf module /boot/kernel/acpi.ko at 0xc04e2820. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (737.02-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA T,PSE36,MMX,FXSR,SSE real memory = 535736320 (510 MB) avail memory = 515031040 (491 MB) Pentium Pro MTRR support enabled VESA: v3.0, 1024k memory, flags:0x1, mode table:0xc03fdc62 (122) VESA: Intel(R) 810, Intel(R) 815 Chipset Video BIOS npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS CUSL2on motherboard pcibios: BIOS version 2.10 Using $PIR table, 10 entries at 0xc00f1360 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 31 INTD is routed to irq 9 pcib0: slot 31 INTB is routed to irq 10 pcib0: slot 31 INTC is routed to irq 9 agp0: Intel 82815 (i815 GMCH) SVGA controller mem 0xf700-0xf707,0xf800 -0xfbff irq 11 at device 2.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib1: slot 9 INTA is routed to irq 9 pcib1: slot 12 INTA is routed to irq 9 pcib1: slot 14 INTA is routed to irq 5 sis0: NatSemi DP83815 10/100BaseTX port 0xd800-0xd8ff mem 0xf680-0xf6800ff f irq 9 at device 9.0 on pci1 sis0: Ethernet address: 00:02:e3:1c:cf:9e miibus0: MII bus on sis0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xd400-0xd47f mem 0xf600-0xf600 007f irq 9 at device 12.0 on pci1 xl0: Ethernet address: 00:01:02:73:ee:49 miibus1: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus1 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: Creative CT5880-C port 0xd000-0xd03f irq 5 at device 14.0 on pci1 pcm0: SigmaTel STAC9721/23 AC97 Codec isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0xb800-0xb80f at device 31.1 on pc i0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xb400-0xb41f irq 9 at device 31.2 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.00, addr 2, iclass 3/1 ums0: 3 buttons and Z
Re: KDE Konsole, crashes, on a SIGABRT...
On Saturday 23 August 2003 18:03, Daniel Eischen wrote: On Sat, 23 Aug 2003, Larry Rosenman wrote: Prior to Thursday, it worked just fine. I can't explain it. Someone is going to have to debug konsole and figure out what is going on. Done. Turns out this change ( http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/gen/gethostname.c.diff?r1=1.3r2=1.4f=h ) was the cause for Konsole to abort(). The case of gethostbyname returning ENOMEM is caught, ENAMETOOLONG isn't. A fix will go into the kdebase port in the next few days, along with a bunch of other fixes. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp0.pgp Description: signature
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 12:17:52PM +, Jens Rehsack wrote: Stuart Walsh wrote: On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Hi Guys, I have 2 machines with P4P800-Deluxe with the 3C940. If phk@ could fix the swap-issue, so that I can reboot easily, I would test your patches, too. Que? What swap issue? I can dual boot stable and current just fine on the P4P800. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 03:13:18PM +0200, Wilko Bulte wrote: On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote: On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: ... Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Are you running up do date -current, or is there anything strange about your setup at all? I just did a buildworld on a freshly checked out tree, applied the patches and tried again. Unfortunately that did not help. I continue my investigation. Going to the latest BIOS also did not make any difference (long shot, I know). Can someone with a P4P800 who has gotten it to work please post their dmesg? Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
