Re: Officially support for 4.7
On Mon, Nov 24, 2003 at 06:41:01AM -0800, Carol Overes wrote: Hi, Thanks for your help finding ISO images for 4.7. But does anyone know how long 4.7 will be supported and provided with security fixes ? I already answered that, but to repeat what I said in my previous reply: According to http://www.freebsd.org/security/index.html the RELENG_4_7 security branch is officially supported until 31 Dec. 2003 After that date you can no longer depend on security fixes being provided for 4.7. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hard error reading fsbn
no, i use the same cable, now i disconnect the drive ( ad2 ) and get the same errors for ad1. ad1 is on the primary controller. ad2 was on the secondary controller. ad1 is a brand new drive. regards Stefan On 23 Nov 2003 17:13:47 -0500 Lowell Gilbert [EMAIL PROTECTED] wrote: Stefan Knoblauch [EMAIL PROTECTED] writes: after upgrading from 4.8 to 4.9 i got mane hard error reading fsbn errors. ok i thougt that is a problem of the 2 years old 80 GB harddisk so i get a new 80 GB drive. after restoring the system to to the new drive, i get the same errors. the next step was to reformat the disk on a windows box. this works fine and the harddisk lokks good. i put the disk into my freebsd 4.9 system and do not have this read errors. after 1 week re errors come back. more than before. i do not have any errors with the 4.8 version, so i make a complete new installation with 4.9. yaeh, no errors. one week later the systemlog shows me the errors again. in my ear's the system is not stable. i use 1 maxtor and one IBM disk. does anyone know what the problem is ? No, but did you replace the drive cable when you replaced the drive itself? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hard error reading fsbn
oki, here a tail from the dmesg log ad1s1e: hard error reading fsbn 260800575 of 130400256-130400511 (ad1s1 bn 260800575; cn 16234 tn 21 sn 42) trying PIO mode ad1: DMA problem fallback to PIO mode ad1: DMA problem fallback to PIO mode ad1: DMA problem fallback to PIO mode ad1: DMA problem fallback to PIO mode ad1: DMA problem fallback to PIO mode ### no, i use the same cable, now i disconnect the drive ( ad2 ) and get the same errors for ad1. ad1 is on the primary controller. ad2 was on the secondary controller. ad1 is a brand new drive. regards Stefan On 23 Nov 2003 17:13:47 -0500 Lowell Gilbert [EMAIL PROTECTED] wrote: Stefan Knoblauch [EMAIL PROTECTED] writes: after upgrading from 4.8 to 4.9 i got mane hard error reading fsbn errors. ok i thougt that is a problem of the 2 years old 80 GB harddisk so i get a new 80 GB drive. after restoring the system to to the new drive, i get the same errors. the next step was to reformat the disk on a windows box. this works fine and the harddisk lokks good. i put the disk into my freebsd 4.9 system and do not have this read errors. after 1 week re errors come back. more than before. i do not have any errors with the 4.8 version, so i make a complete new installation with 4.9. yaeh, no errors. one week later the systemlog shows me the errors again. in my ear's the system is not stable. i use 1 maxtor and one IBM disk. does anyone know what the problem is ? No, but did you replace the drive cable when you replaced the drive itself? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
On Monday 24 November 2003 15:32, Mike Tancsa wrote: The problem is that LQR is agreed to with the ERX (the PPPoE terminating device on the other end), but it never works. Works for me. I guess there really are many providers with misconfigured equipment out there. Actually, I know people who cannot use lqr although they're using the same provider as I do (but they 'dial in' to a different AC). Trying to actually get such an obscure technical thing through any big telco/provider hotline to someone who can actually understand what you want is pretty futile, too. -- ,_, | 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: hard error reading fsbn
Well, the problem there is that your drive can't do UDMA at the speed it is trying to. Replace the cable, make sure it is an 80 conductor cable conforming to the standards for IDE cables, most specifically, it should not be longer than 45cm. If that doesn't help, try setting a lower UDMA mode with atacontrol(8) or disable it completely via sysctls. Will - Original Message - From: Stefan Knoblauch [EMAIL PROTECTED] To: Lowell Gilbert [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, November 24, 2003 5:17 PM Subject: Re: hard error reading fsbn oki, here a tail from the dmesg log ad1s1e: hard error reading fsbn 260800575 of 130400256-130400511 (ad1s1 bn 260800575; cn 16234 tn 21 sn 42) trying PIO mode ad1: DMA problem fallback to PIO mode ad1: DMA problem fallback to PIO mode ad1: DMA problem fallback to PIO mode ad1: DMA problem fallback to PIO mode ad1: DMA problem fallback to PIO mode ### no, i use the same cable, now i disconnect the drive ( ad2 ) and get the same errors for ad1. ad1 is on the primary controller. ad2 was on the secondary controller. ad1 is a brand new drive. regards Stefan On 23 Nov 2003 17:13:47 -0500 Lowell Gilbert [EMAIL PROTECTED] wrote: Stefan Knoblauch [EMAIL PROTECTED] writes: after upgrading from 4.8 to 4.9 i got mane hard error reading fsbn errors. ok i thougt that is a problem of the 2 years old 80 GB harddisk so i get a new 80 GB drive. after restoring the system to to the new drive, i get the same errors. the next step was to reformat the disk on a windows box. this works fine and the harddisk lokks good. i put the disk into my freebsd 4.9 system and do not have this read errors. after 1 week re errors come back. more than before. i do not have any errors with the 4.8 version, so i make a complete new installation with 4.9. yaeh, no errors. one week later the systemlog shows me the errors again. in my ear's the system is not stable. i use 1 maxtor and one IBM disk. does anyone know what the problem is ? No, but did you replace the drive cable when you replaced the drive itself? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
Are you sure you actually connect to an ERX on the other end, and its actually negotiating LQR ? e.g. if you add LQM to the logging section, do you see tun0: LQM: deflink: Will send LQR every 10.00 secs or do you see tun0: LQM: deflink: LQR/ECHO LQR not negotiated What do you have for your ppp.conf ? I have enable lqr accept lqr set lqrperiod 10 Like I said, its very possible the telco has the ERX misconfigured and yes, its impossible to get this level of detail out of them :-( ---Mike At 10:17 AM 24/11/2003, Michael Nottebrock wrote: On Monday 24 November 2003 15:32, Mike Tancsa wrote: The problem is that LQR is agreed to with the ERX (the PPPoE terminating device on the other end), but it never works. Works for me. I guess there really are many providers with misconfigured equipment out there. Actually, I know people who cannot use lqr although they're using the same provider as I do (but they 'dial in' to a different AC). Trying to actually get such an obscure technical thing through any big telco/provider hotline to someone who can actually understand what you want is pretty futile, too. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
On Monday 24 November 2003 16:46, Mike Tancsa wrote: Are you sure you actually connect to an ERX on the other end, and its actually negotiating LQR ? e.g. if you add LQM to the logging section, do you see tun0: LQM: deflink: Will send LQR every 10.00 secs or do you see tun0: LQM: deflink: LQR/ECHO LQR not negotiated Yes. LQM: deflink: Will send LQR every 30.00 secs I even found this way back in my ppp.log: Phase: deflink: ** Too many LQR packets lost ** So it's actually doing what it should. :) What do you have for your ppp.conf ? I have enable lqr accept lqr set lqrperiod 10 Just enable lqr. The default period of 30 seconds is quite reasonable IMHO. Like I said, its very possible the telco has the ERX misconfigured and yes, its impossible to get this level of detail out of them :-( C'est la vie. -- ,_, | 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: ppp(8) v. 3.1 : PPPoE lqr problem.
At 10:59 AM 24/11/2003, Michael Nottebrock wrote: On Monday 24 November 2003 16:46, Mike Tancsa wrote: Are you sure you actually connect to an ERX on the other end, and its actually negotiating LQR ? e.g. if you add LQM to the logging section, do you see tun0: LQM: deflink: Will send LQR every 10.00 secs or do you see tun0: LQM: deflink: LQR/ECHO LQR not negotiated Yes. LQM: deflink: Will send LQR every 30.00 secs I even found this way back in my ppp.log: Phase: deflink: ** Too many LQR packets lost ** So it's actually doing what it should. :) But is it doing that because its never hearing the LQR reply ? And for sure its an ERX on the other end ? ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hard error reading fsbn
hi, sorry that i do not send more information, this not happened again :) here a part of my dmesg bootup. i use FreeBSd 4.9 on a HP Vectra VL400. the problem comes up first, as i add the adaptec SCSI controller, but do not use a disk on it. and i replace both disks. as you can see the disks are Maxtor discs, and they are new. i do not change the cable, because it works perfectly before 4.9 from 3.5 to to to to to 4.8. regards Stefan FreeBSD 4.9-STABLE #0: Sun Nov 16 21:01:13 CET 2003 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 agp0: Intel 82815 (i815 GMCH) host to PCI bridge mem 0xec00-0xefff at device 0.0 on pci0 pcib1: Intel 82801BA/BAM (ICH2) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci2: PCI bus on pcib1 pci2: NVidia model 0172 graphics accelerator at 0.0 irq 10 pcib2: Intel 82801AA (ICH) Hub to PCI bridge at device 30.0 on pci0 pci1: PCI bus on pcib2 pci1: unknown card (vendor=0x109e, dev=0x034e) at 0.0 irq 11 pci1: unknown card (vendor=0x109e, dev=0x0858) at 0.1 irq 11 ahc0: Adaptec 2940 Ultra SCSI adapter port 0x2000-0x20ff mem 0xe900-0xe9000fff irq 5 at device 1.0 on pci1 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x2400-0x247f mem 0xe9001000-0xe900107f irq 9 at device 2.0 on pci1 xl0: Ethernet address: 00:50:04:65:69:3d miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: 3Com 3c905C-TX Fast Etherlink XL port 0x2480-0x24ff mem 0xe9001400-0xe900147f irq 5 at device 4.0 on pci1 xl1: Ethernet address: 00:01:03:07:85:d4 miibus1: MII bus on xl1 xlphy1: 3c905C 10/100 internal PHY on miibus1 xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: Intel 82801AA (ICH) PCI to LPC bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH ATA66 controller port 0x1800-0x180f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82801AA (ICH) USB controller port 0x1820-0x183f irq 11 at device 31.2 on pci0 usb0: Intel 82801AA (ICH) USB controller 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 pci0: unknown card (vendor=0x8086, dev=0x2413) at 31.3 irq 9 pcm0: Intel ICH (82801AA) port 0x1300-0x133f,0x1200-0x12ff irq 9 at device 31.5 on pci0 pcm0: Cirrus Logic CS4299 AC97 Codec default ad0: 29325MB Maxtor 2F030L0 [59582/16/63] at ata0-master UDMA66 ad1: 78167MB Maxtor 6Y080L0 [158816/16/63] at ata0-slave UDMA66 acd0: CD-RW HL-DT-ST RW/DVD GCC-4480B at ata1-slave PIO4 Waiting 10 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1a ad1: DMA problem fallback to PIO mode ad1: DMA problem fallback to PIO mode ad1s1e: hard error reading fsbn 257417487 of 128708640-128708895 (ad1s1 bn 257417487; cn 16023 tn 126 sn 54) status=59 error=40 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
On Monday 24 November 2003 17:07, Mike Tancsa wrote: At 10:59 AM 24/11/2003, Michael Nottebrock wrote: On Monday 24 November 2003 16:46, Mike Tancsa wrote: Are you sure you actually connect to an ERX on the other end, and its actually negotiating LQR ? e.g. if you add LQM to the logging section, do you see tun0: LQM: deflink: Will send LQR every 10.00 secs or do you see tun0: LQM: deflink: LQR/ECHO LQR not negotiated Yes. LQM: deflink: Will send LQR every 30.00 secs I even found this way back in my ppp.log: Phase: deflink: ** Too many LQR packets lost ** So it's actually doing what it should. :) But is it doing that because its never hearing the LQR reply ? Yes. ppp nicely detects when they're up and fuzzing with the AC again. And for sure its an ERX on the other end ? Actually it's an NRP - it seems Cisco does a better job with their PPPoE implementation. -- ,_, | 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: ppp(8) v. 3.1 : PPPoE lqr problem.
At 11:25 AM 24/11/2003, Michael Nottebrock wrote: And for sure its an ERX on the other end ? Actually it's an NRP - it seems Cisco does a better job with their PPPoE implementation. OK, thanks. The problem I see is only against an ERX. So either misconfigured ERX or something about Juniper's implementation. As the original poster was connecting against Frace Telecom and I to Bell Canada and given that VJ Header compression also does not play well with FreeBSD's I am leaning to the ERX. Back to the original question of how best to work around this. I will be deploying close to 100 boxes, most of which will talk to an ERX. It would be nice if I could avoid having to manually patch the boxes each time I do an update. If I work with my programmers here to come up with a patch, is there even a chance that someone would commit it to HEAD and then MFC it back to RELENG_4? Who is looking after PPP these days anyways ? ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
NFS related error?
I note on a 4.9-prerelease running NFS server (kernel built October 3rd) a series of infrequent messages such as: Nov 18 14:19:56 nas /kernel: ufs_rename: fvp == tvp (can't happen) Nov 18 23:06:41 nas /kernel: ufs_rename: fvp == tvp (can't happen) Nov 19 22:25:29 nas /kernel: ufs_rename: fvp == tvp (can't happen) Nov 21 09:42:35 nas /kernel: ufs_rename: fvp == tvp (can't happen) Followed by a total system freeze a few days later :-( Seems to me like a race condition someplace. Has this been found/addressed in the 4-stable tree since then or is there a pending MFC? -- Michael Butler CISSP Security Consultant Cable and Wireless www.cw.com PGP Key ID: 0x5E873CC5 Fingerprint: 2CFF 581F D192 F885 7ED9 3C44 889C A479 5E87 3CC5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
On Monday 24 November 2003 17:35, Mike Tancsa wrote: given that VJ Header compression also does not play well with FreeBSD's I am leaning to the ERX. Right, vjcomp, I don't need to disable that here as well... Back to the original question of how best to work around this. I will be deploying close to 100 boxes, most of which will talk to an ERX. It would be nice if I could avoid having to manually patch the boxes each time I do an update. If I work with my programmers here to come up with a patch, is there even a chance that someone would commit it to HEAD and then MFC it back to RELENG_4? Who is looking after PPP these days anyways ? I guess there is a definite chance, it's not like ppp's pppoe functionality is some rarely-used feature... I myself am only a lowly ports-committer, but if you submit a PR and send me a note, I'll make sure it gets assigned to brian (or maybe there are already PRs pending?). -- ,_, | 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
