Re: any real documentation of the boot2 prompt?
In <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote: >Václav Haisman wrote: >> What does lsdev or whatever it was say? Does it show any devices besides >> the raw disks? > >So I booted from CD and ran lsdev, and showed something like this (from >memory) > >0: Drive A >2: Disk 0 > 1: FFS You need to get into your SCSI BIOS (don't know what the key sequence is for 3ware, it's ^A for Adaptec) at the correct time and enable the disk for booting. As shown here, there's no chance of it being bootable. -- Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.5" / 37N 20' 15.3" Internet: steve @ Watt.COM Whois: SW32-ARIN Free time? There's no such thing. It just comes in varying prices... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.2-prerelease from 8 jan crash
uname -a :
FreeBSD xxx 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #21: Mon Jan 8 14:37:57 CET
2007
kgdb backtrace :
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 06
fault virtual address = 0x104
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06efa29
stack pointer = 0x28:0xe538cc60
frame pointer = 0x28:0xe538cc74
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 5 (thread taskq)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 8d10h42m51s
Dumping 2047 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935 1919
1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695
1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471
1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247
1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023
1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735
719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447
431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159
143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc06fa662 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:409
#2 0xc06faa13 in panic (fmt=0xc0996d81 "%s") at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0xc0936c1d in trap_fatal (frame=0xe538cc20, eva=0) at
/usr/src/sys/i386/i386/trap.c:837
#4 0xc09362bd in trap (frame=
{tf_fs = 8, tf_es = -964755416, tf_ds = -449314776, tf_edi =
-964734208, tf_esi = 4, tf_ebp = -449262476, tf_isp = -449262516, tf_ebx
= -848968900, tf_edx = 6, tf_ecx = -964734208, tf_eax = 1, tf_trapno =
12, tf_err = 0, tf_eip = -1066468823, tf_cs = 32, tf_eflags = 65538,
tf_esp = -848968900, tf_ss = -933423232}) at
/usr/src/sys/i386/i386/trap.c:270
#5 0xc092004a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc06efa29 in _mtx_lock_sleep (m=0xcd65c33c, tid=3330233088, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:546
#7 0xc074cfd4 in unp_gc (arg=0x0, pending=2) at
/usr/src/sys/kern/uipc_usrreq.c:1714
#8 0xc07209d1 in taskqueue_run (queue=0xc6848200) at
/usr/src/sys/kern/subr_taskqueue.c:257
#9 0xc0721000 in taskqueue_thread_loop (arg=0x1) at
/usr/src/sys/kern/subr_taskqueue.c:376
#10 0xc06df223 in fork_exit (callout=0xc0720f40 ,
arg=0x1, frame=0x1) at /usr/src/sys/kern/kern_fork.c:821
#11 0xc09200ac in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:208
Any idea what happened ?
Cédric
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal trap while configuring re0 (Realtek 8136)
Hi, I have a Notebook[1] with a Realtek 8136 chipset. While trying to install FreeBSD or running a LiveCD like Freesbie or DesktopBSD it results in a fatal trap. This is the output of a running Kubuntu installation of lspci: 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Unknown device 8136 (rev 01) (whole output at: http://zeus.crashmail.de/nopaste/?494) I got this error message: NMI ISA b0, EISA ff RAM parity error, likely hardware failure. Fatal trap 19: non-maskable interrupt trap while in kernel mode instruction pointer = 0x20:0xc06021ed stack pointer = 0x28:0xe9452bbc frame pointer = 0x28:0xe9452be0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, IOPL = 0 current process = 312 (ifconfig) trap number = 19 panic: non-maskable interrupt trap When I try to Configure -> Networking with the FreeBSD installer, it crashes after choosing "DCHP?" -> yes ... Any hints? Known behavior? What information do you need? -- [1] = Medion MD 98000 -- By(t)e, Stefan 'Steve' Tell | http://blog.crashmail.de ---| http://www.freebsd.org Powered by FreeBSD/i386| http://www.naturefund.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Cannot start install cd of 6.2-R at all
Mark Kirkwood wrote: Artem Kuchin wrote: Hello! I am having a VERY weird problem. The pc config is: 1) Celeron 1+ GHZ 2) Intel PCI ethernet nic 3) Fasttrak TX2000 raid + 2 mirrored disks (seagate 80gb) 4) teac dvd driver 5) 512 MB ram 6) Chaintech montherboard (old one) also tried on gigabyte motherboard I insert boot cd and when it starts loading a get a dump of cpu register scrolling crazy on the screen. If i delete TX2000 the installer loads fine. Any idea what is happening and how to SOLVE it? I have seen this with a Tyan PIII board + TX2000. In my case re-trying the boot from cd several times would *eventually* get a working installer session. (If you search the archives you'll see several cases of folks encountering this). Unfortunately I don't know of any solution. A (tedious) workaround (in case repeated attempts always fail for you), is to install a minimal system off an earlier version of FreeBSD and run the installer off the installed system - or just src upgrade to the version you want. I found that the 4.x, 5.0, 5.1 and 5.2 cd's all worked fine - but 5.3 onwards and 6.x would register dump. There is a better workaround which i used. A simple start of installer from 4 floppies. Then install the whole system from CD-ROM. It does work but insolved copying of floppy images onto the disks. However is it a very annoying problem which i have been encountering since 5.0-RELEASE. The bootloader failed when trying to load installed from CD-ROM on pretty much every PIII and old Celeron pc which i tried. (it is about 6 machines by now). Very weird and i have no idea to how help to solve the problem. -- Regards Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tcpdump, rl, sis, fxp and multicast problems
Matthew X. Economou wrote: not very important but wouldn't it be better to set the checksum to 0 instead of some arbitrary (?) and confusing value then ? No, as not setting the checksum is a (minor) optimization. Setting that field to any arbitrary constant means at least one completely unnecessary CPU instruction per datagram. Best wishes, Matthew However, since it is a 1's complement checksum, there is a distinguished value (all zero bits) that you could set the checksum field to that wouldn't occur for a normal computed checksum. Since the presence of a checksum is mandatory for TCP, you can use this trick and external software could "know" that it's a distinguished value. This is similar to UDP, where the protocol allows the "no checksum present" case by setting the checksum field to all zero bits. I suspect the overhead isn't the CPU instruction, but the memory reference. If you manipulate the checksum field to the distinguished value at the time the other fields are written, they they'll all get written out to memory when the cache line is flushed. You've already got to initialize the Urgent Pointer field, which is the other 16 bits in the same 32 bit word. If you were really clever, you could make a union to cover both fields and zero both out in the same store instruction. louie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Firefox keeps beeping at me ...
All - I've been away from FreeBSD for some time and have been updating my installation, getting used to the ways of portupgrade, etc. Have noticed that Firefox keeps emitting what sound like console beeps - I haven't established much of a pattern for these though it always happens when I close the app. Is there a way to kill these? Apologies in advance if this is a dopey question. Obviously more an annoyance than anything. Thanks, Glenn +-+ Glenn Becker - [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org +-+ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BTX issues when booting from a USB CD-ROM
Peter Losher wrote: I have a Matushita based USB CD/DVD-ROM drive that I have been using to install FreeBSD with for the better part of the last year. I just took delivery yesterday of both a HP Proliant 1450 G3 and a generic 1U server based on a Tyan Tomcat i845GV S3098 MB. In both cases, once the USB CD-ROM started loading either 6.1 or 6.2, I get a BTX halt: -=- from CD : CD Loader 1.2 Building the boot loader arguments Looking up /BOOT/LOADER... Found Relocating the loader and the BTX Starting the BTX loader BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard int=000d err= efl=00030206 eip=37d0 eax=8001 ebx= ecx=a391 edx=009f esi=0b32 edi= ebp= esp=03d2 cs=f000 ds=3eca es=3eacfs= gs= ss=97fc cs:eip=2e 0f 01 16 f8 38 0f 20-c0 0c 01 0f 22 c0 b8 30 00 8e c0 0f 20 c0 24 fe-0f 22 c0 eb 00 66 58 c3 ss:esp=01 80 00 00 db 36 00 00-00 00 32 0b 00 00 00 00 00 00 f8 03 00 00 00 00-00 00 9f 00 00 00 01 00 BTX halted -=- Opening up the cases and plugging in a EIDE CD-ROM, the installer CD's work just fine. So it looks like perhaps there is some new BIOS instruction set that's causing the BTX loader some pain with a USB device. Anyone encounter similar issues recently? Best Wishes - Peter Hi, this is well known problem discussed a few months ago: http://lists.freebsd.org/pipermail/freebsd-stable/2006-November/030897.html sterted at semptember http://lists.freebsd.org/pipermail/freebsd-qa/2006-September/000783.html Partial fix could be to use GRUB (it helps me on Sun, but does not help on HP servers) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: any real documentation of the boot2 prompt?
Steve Watt wrote: > You need to get into your SCSI BIOS (don't know what the key > sequence is for 3ware, it's ^A for Adaptec) Alt-F3 funnily enough... Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Firefox keeps beeping at me ...
Glenn Becker wrote: All - I've been away from FreeBSD for some time and have been updating my installation, getting used to the ways of portupgrade, etc. Have noticed that Firefox keeps emitting what sound like console beeps - I haven't established much of a pattern for these though it always happens when I close the app. Is there a way to kill these? Apologies in advance if this is a dopey question. Obviously more an annoyance than anything. perhaps -questions is more appropriate... Anyway, that makes two of us - mine beeps too - when sending and reading mails. No idea why though, sorry. Anyone? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap while configuring re0 (Realtek 8136)
* Stefan 'Steve' Tell <[EMAIL PROTECTED]> wrote: > 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Unknown device > 8136 (rev 01) (whole output at: http://zeus.crashmail.de/nopaste/?494) pciconf -vl [EMAIL PROTECTED]:0:0: class=0x02 card=0x105317c0 chip=0x813610ec rev=0x01 hdr=0x00 class = network subclass = ethernet [EMAIL PROTECTED]:0:0: class=0x028000 card=0x10018086 chip=0x42228086 rev=0x02 hdr=0x00 class = network -- By(t)e, Stefan 'Steve' Tell | http://blog.crashmail.de ---| http://www.freebsd.org Powered by FreeBSD/i386| http://www.naturefund.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPv6 problems with 6.2-RELEASE ?
> 2) rtsol(8) is used to initiate stateless autoconfiguration. You might=20 > want to try "rtsol -d interface". Aha... this does not work... > 3) Check the net.inet6.ip6.accept_rtadv sysctl. ipv6_enable should take=20 > care of this. ...because this is 0 All of which appears to be because a spurious 'ipv6_gateway_enable="YES"' has found it's way into my rc.conf due to cut-n-paste. Which is interesting though, since even when I spotted it, it hadn;'t occurred to me that it would prevent the auto configuration working. Thnaks for the help, all works fine now. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: any real documentation of the boot2 prompt?
On Sun, January 21, 2007 8:47 am, Matthew Seaman wrote: > Steve Watt wrote: >> You need to get into your SCSI BIOS (don't know what the key >> sequence is for 3ware, it's ^A for Adaptec) > > Alt-F3 > funnily enough... It's ALT+3 for all our 3Ware Escalade cards (PATA/SATA). Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPv6 over gif(4) broken in 6.2-RELEASE?
Bruce A. Mah wrote: >> I remember Dimitry Andric reported the same problem on -stable on 30 >> Dec, and after he reverted rev.1.48.2.16 it worked fine again. Do >> you have the symptom even on 6.2-RELEASE? Since RELENG_6_2_0_RELEASE >> did not have the change, I thought there was no problem. ... > On my 6-STABLE system (which appears to be working fine), I still have > the change from 1.48.2.16, I only backed out .15 and .14. I didn't try > my diff on the 6.2-RC2 and 6.2-RELEASE machines yet. > > Hmmm...I was looking for that bug report before, but I couldn't find it. > It's not clear to me how 1.48.2.16 is involved...hmmm... I originally reported this here: http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031809.html and later I found out it was caused by commit 1.48.2.16: http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031853.html I'll shoot in a regular PR later tonight... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2-prerelease from 8 jan crash
> Date: Sun, 21 Jan 2007 11:02:20 +0100 > From: Cedric Tabary <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > > uname -a : > FreeBSD xxx 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #21: Mon Jan 8 14:37:57 CET > 2007 > > kgdb backtrace : > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 06 > fault virtual address = 0x104 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc06efa29 > stack pointer = 0x28:0xe538cc60 > frame pointer = 0x28:0xe538cc74 > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags= resume, IOPL = 0 > current process = 5 (thread taskq) > trap number = 12 > panic: page fault > cpuid = 1 John Baldwin committed a fix to -stable a week or two ago that fixed this for me. It was MFCed on Jan. 12, so you don't have it. Patches to: /sys/kern/kern_descrip.c /sys/kern/uipc_syscalls.c -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpzeGsxnQU3D.pgp Description: PGP signature
Re: BTX issues when booting from a USB CD-ROM
Peter Losher wrote: In both cases, once the USB CD-ROM started loading either 6.1 or 6.2, I get a BTX halt: Known issue. The btx code can't deal with BIOSes which want to enter protected mode to service the I/Os. USB support in most BIOSen generally does this. I see the same issue with FreeBSD's pxeboot and the PXE client in Etherboot. Regards, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Harddisk gone.
HI, I am a user of freebsd for couple of year now and had recently made a fresh install with 6.2. Everything worked as it always did but as i booted the system today it seems that the kernel couldnt find my harddisk. Strange thing is: - I get the bootloader (dual boot with windows) - windows works just fine - I can access all my files on the hd through the bootloader - the kernel boots of the harddisk and finds the (s)ata-controllers - it finds the cdrom attachet to the ata0 - it finds my sata disk but my first pata disk seems to be gone. The bootscript ends because there is no ad0 (dev isnt created so cant do manualy) I tried to boot 2 live-cdroms (freesbie and frenzy) with the same result. System: Nforce 4 motherboard AMD X2 4600+ 1GB ram GF 7900tgo PATA Maxtor hd (which is gone) SATA WD (works fine) Anyone got any idea whay might cause this? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Failover-HA-Setup
Ulrich Spoerlein wrote: > Only two options remain: modify existing mysql-server script (bad idea, > will be overwritten on update) or go through a proxy script which > "transforms" start|stop -> onestart|onestop > > You could also alter the environment of heartbeat (it's really just a > bunch of poorly written shell scripts) and set mysql_enable=YES there, > but that'd be just as fragile as rewriting the existing mysql-server > script. Yeah, I thin we're definitely in territory that is not covered by the boot scripts as written here. This thread has got me thinking though, how useful would something like 'foo_enable=conditional' be? What I'm thinking is that you could define a script in foo_condition that rc.d would run. We could either do a straight yes/no, where if the script exits successfully (exit code 0) then we run the service, and if it fails (non-zero exit code) we don't. OR, we could have the script return the argument we want to feed that service's startup script. I think that may have some utility here, what do y'all think? Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap while configuring re0 (Realtek 8136)
On Sun, Jan 21, 2007 at 06:36:00PM +0100, Stefan 'Steve' Tell wrote: > * Stefan 'Steve' Tell <[EMAIL PROTECTED]> wrote: > > > 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Unknown device > > 8136 (rev 01) (whole output at: http://zeus.crashmail.de/nopaste/?494) > > pciconf -vl > > [EMAIL PROTECTED]:0:0: class=0x02 card=0x105317c0 chip=0x813610ec > rev=0x01 hdr=0x00 > class = network > subclass = ethernet > [EMAIL PROTECTED]:0:0: class=0x028000 card=0x10018086 chip=0x42228086 > rev=0x02 hdr=0x00 > class = network > How about attached one? -- Regards, Pyun YongHyeon Index: if_re.c === RCS file: /home/ncvs/src/sys/dev/re/if_re.c,v retrieving revision 1.82 diff -u -r1.82 if_re.c --- if_re.c 16 Jan 2007 20:35:23 - 1.82 +++ if_re.c 22 Jan 2007 01:32:23 - @@ -2319,6 +2319,20 @@ re_tx_list_init(sc); /* +* Load the addresses of the RX and TX lists into the chip. +*/ + + CSR_WRITE_4(sc, RL_RXLIST_ADDR_HI, + RL_ADDR_HI(sc->rl_ldata.rl_rx_list_addr)); + CSR_WRITE_4(sc, RL_RXLIST_ADDR_LO, + RL_ADDR_LO(sc->rl_ldata.rl_rx_list_addr)); + + CSR_WRITE_4(sc, RL_TXLIST_ADDR_HI, + RL_ADDR_HI(sc->rl_ldata.rl_tx_list_addr)); + CSR_WRITE_4(sc, RL_TXLIST_ADDR_LO, + RL_ADDR_LO(sc->rl_ldata.rl_tx_list_addr)); + + /* * Enable transmit and receive. */ CSR_WRITE_1(sc, RL_COMMAND, RL_CMD_TX_ENB|RL_CMD_RX_ENB); @@ -2335,6 +2349,9 @@ RL_TXCFG_CONFIG|RL_LOOPTEST_ON_CPLUS); } else CSR_WRITE_4(sc, RL_TXCFG, RL_TXCFG_CONFIG); + + CSR_WRITE_1(sc, RL_EARLY_TX_THRESH, 16); + CSR_WRITE_4(sc, RL_RXCFG, RL_RXCFG_CONFIG); /* Set the individual bit to receive frames for this host only. */ @@ -2389,21 +2406,6 @@ /* Enable receiver and transmitter. */ CSR_WRITE_1(sc, RL_COMMAND, RL_CMD_TX_ENB|RL_CMD_RX_ENB); #endif - /* -* Load the addresses of the RX and TX lists into the chip. -*/ - - CSR_WRITE_4(sc, RL_RXLIST_ADDR_HI, - RL_ADDR_HI(sc->rl_ldata.rl_rx_list_addr)); - CSR_WRITE_4(sc, RL_RXLIST_ADDR_LO, - RL_ADDR_LO(sc->rl_ldata.rl_rx_list_addr)); - - CSR_WRITE_4(sc, RL_TXLIST_ADDR_HI, - RL_ADDR_HI(sc->rl_ldata.rl_tx_list_addr)); - CSR_WRITE_4(sc, RL_TXLIST_ADDR_LO, - RL_ADDR_LO(sc->rl_ldata.rl_tx_list_addr)); - - CSR_WRITE_1(sc, RL_EARLY_TX_THRESH, 16); #ifdef RE_TX_MODERATION /* ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Fwd: Re: Harddisk gone.]
-- Georg 'Therion' Bege http://coruscant.info http://www.ninth-art.de [EMAIL PROTECTED] GnuPG-Key-ID: 0x5717E214 FingerPrint: A8EC B4B2 C9A9 483B CC87 56EE 07A1 C78E 5717 E214 --- Begin Message --- Moin Obviously it is a driver/chipset problem - Maybe printing dmesg output helps. So your FBSD is located on the pata hdd? If you could boot with the previous 6.1 release then you might install 6.1 and then checkout 6.2 and compile a custom kernel. Or did you install already? Am Montag, den 22.01.2007, 00:58 +0100 schrieb Matthias Gamsjäger: > HI, > > I am a user of freebsd for couple of year now and had recently made a fresh > install with 6.2. Everything worked as it always did but as i booted the > system today it seems that the kernel couldnt find my harddisk. > > Strange thing is: > - I get the bootloader (dual boot with windows) > - windows works just fine > - I can access all my files on the hd through the bootloader > - the kernel boots of the harddisk and finds the (s)ata-controllers > - it finds the cdrom attachet to the ata0 > - it finds my sata disk > > but my first pata disk seems to be gone. The bootscript ends because there > is no ad0 (dev isnt created so cant do manualy) > > > I tried to boot 2 live-cdroms (freesbie and frenzy) with the same result. > > System: > Nforce 4 motherboard > AMD X2 4600+ > 1GB ram > GF 7900tgo > PATA Maxtor hd (which is gone) > SATA WD (works fine) > > Anyone got any idea whay might cause this? > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > !DSPAM:45b404ee896261676220417! > > -- Georg 'Therion' Bege http://coruscant.info http://www.ninth-art.de [EMAIL PROTECTED] GnuPG-Key-ID: 0x5717E214 FingerPrint: A8EC B4B2 C9A9 483B CC87 56EE 07A1 C78E 5717 E214 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil --- End Message --- signature.asc Description: Dies ist ein digital signierter Nachrichtenteil !DSPAM:45b416f2896269661917265!___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPv6 over gif(4) broken in 6.2-RELEASE?
If memory serves me right, Dimitry Andric wrote: > Bruce A. Mah wrote: >>> I remember Dimitry Andric reported the same problem on -stable on 30 >>> Dec, and after he reverted rev.1.48.2.16 it worked fine again. Do >>> you have the symptom even on 6.2-RELEASE? Since RELENG_6_2_0_RELEASE >>> did not have the change, I thought there was no problem. > ... >> On my 6-STABLE system (which appears to be working fine), I still have >> the change from 1.48.2.16, I only backed out .15 and .14. I didn't try >> my diff on the 6.2-RC2 and 6.2-RELEASE machines yet. >> >> Hmmm...I was looking for that bug report before, but I couldn't find it. >> It's not clear to me how 1.48.2.16 is involved...hmmm... > > I originally reported this here: > http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031809.html > > and later I found out it was caused by commit 1.48.2.16: > http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031853.html > > I'll shoot in a regular PR later tonight... Hi Dimitry-- This isn't consistent with what I'm finding. For one thing, rev. 1.48.2.16 of nd6.c isn't in 6.2-RELEASE but I saw the problem there anyways. Also, that's not the change I made to my local sources to get my gif(4) tunnel working. Are you sure about this? :-) Thanks! Bruce. signature.asc Description: OpenPGP digital signature
Re: tcpdump, rl, sis, fxp and multicast problems
On Sun, 2007-Jan-21 09:32:10 -0500, Louis Mamakos wrote: >However, since it is a 1's complement checksum, there is a distinguished >value (all zero bits) that you could set the checksum field to that >wouldn't occur for a normal computed checksum. That's a useful idea. > Since the presence of a >checksum is mandatory for TCP, you can use this trick and external >software could "know" that it's a distinguished value. Keep in mind that tcpdump/libpcap in contributed software so making local changes is frowned upon. >I suspect the overhead isn't the CPU instruction, but the memory >reference. If you manipulate the checksum field to the distinguished >value at the time the other fields are written, they they'll all get >written out to memory when the cache line is flushed. You've already >got to initialize the Urgent Pointer field, which is the other 16 bits >in the same 32 bit word. If you were really clever, you could make a >union to cover both fields and zero both out in the same store instruction. And given that a 16-bit update is no faster (and typically slower) than a 32-bit update on all supported architectures, this may even be faster. Feel free to come up with a patch. -- Peter Jeremy pgpsNM4cAl6HT.pgp Description: PGP signature
