Re: 5.2-RELEASE TODO
On Wed, 3 Dec 2003, Eric Anderson wrote: ... Well, there are so many kinds of PERC cards. Some are just Mylex cards. Others are MegaRAID. I think they use some Adaptec now. My troubles were with the MegaRAID variant, I'm not sure about the others.. Either way, I tried booting the install CD with all cards disconnected, just to see if I could get the installer up to the main menu. No go. The display switches off as soon as sysinstall starts probing devices. It appears to panic, but the display is dead. Once I was able to use scrolllock at the critical moment just before the kernel starts sysinstall, and prevent the display from switch off, but when I release the scroll lock, I was at the DDB prompt. Not good. First - I hope you mean the cards are physically OUT of the machine - it seemed to me that if they had a logical disk configuration on the card, it would hang. Although, it sounds like your problem is different. Actually, it kind of sounds like it thinks you are doing the -p boot thing to check for keyboard and roll over to the serial port. Other than that, I'm out of ideas (doesn't take long for that to happen though!).. :( Yes, the cards are physically out of the machine. -p seems unlikely, since the display is literally shutoff. The monitor goes into a power-save mode, so it appears that as soon as sysinstall touches whatever devices it touches, the onboard video stops generating output. I've also tried a serial console, which seems to fail the same way. There is simply no output to the serial console after sysinstall starts, and the machine appears to be hung. So, this was with 5.0 and 5.1. I will have to try 5.2 and see if it has the same problem. No one has contacted me about my PR, or even given me any suggestions about more debugging info that I can gather, so unless this gets fixed by chance, I suspect that 5.x is just going to orphan a significant number of machines. Which is a shame, since 5.x would be clearly superior on a quad Xeon machine than 4.9-RELEASE. Eric Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Tue, 2 Dec 2003, Eric Anderson wrote: Tom wrote: Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Are you using a PERC in those boxes? I've seen issues with PERC controllers on 5.1, but 4.8 worked fine. I received a patch, which fixed it, but it's a bit hard to install the os, and then rebuild world without rebooting the machine. :) Well, there are so many kinds of PERC cards. Some are just Mylex cards. Others are MegaRAID. I think they use some Adaptec now. Either way, I tried booting the install CD with all cards disconnected, just to see if I could get the installer up to the main menu. No go. The display switches off as soon as sysinstall starts probing devices. It appears to panic, but the display is dead. Once I was able to use scrolllock at the critical moment just before the kernel starts sysinstall, and prevent the display from switch off, but when I release the scroll lock, I was at the DDB prompt. Not good. Eric -- -- Eric AndersonSystems Administrator Centaur Technology All generalizations are false, including this one. -- Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
Tom wrote: On Tue, 2 Dec 2003, Eric Anderson wrote: Tom wrote: Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Are you using a PERC in those boxes? I've seen issues with PERC controllers on 5.1, but 4.8 worked fine. I received a patch, which fixed it, but it's a bit hard to install the os, and then rebuild world without rebooting the machine. :) Well, there are so many kinds of PERC cards. Some are just Mylex cards. Others are MegaRAID. I think they use some Adaptec now. My troubles were with the MegaRAID variant, I'm not sure about the others.. Either way, I tried booting the install CD with all cards disconnected, just to see if I could get the installer up to the main menu. No go. The display switches off as soon as sysinstall starts probing devices. It appears to panic, but the display is dead. Once I was able to use scrolllock at the critical moment just before the kernel starts sysinstall, and prevent the display from switch off, but when I release the scroll lock, I was at the DDB prompt. Not good. First - I hope you mean the cards are physically OUT of the machine - it seemed to me that if they had a logical disk configuration on the card, it would hang. Although, it sounds like your problem is different. Actually, it kind of sounds like it thinks you are doing the -p boot thing to check for keyboard and roll over to the serial port. Other than that, I'm out of ideas (doesn't take long for that to happen though!).. :( Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Wed, 3 Dec 2003, Tom wrote: On Tue, 2 Dec 2003, Eric Anderson wrote: Tom wrote: Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Are you using a PERC in those boxes? I've seen issues with PERC controllers on 5.1, but 4.8 worked fine. I received a patch, which fixed it, but it's a bit hard to install the os, and then rebuild world without rebooting the machine. :) Well, there are so many kinds of PERC cards. Some are just Mylex cards. Others are MegaRAID. I think they use some Adaptec now. 1550 = lsi megaraid 1650 = adaptec 1750 = lsi megaraid 2550 = adaptec ( don't know the 2650 card just know ). perc stands for poweredge raid controller, so perc just means dell raid card nothing more nothing less. And with the dell habit of switching vendors every model that ain't very informative. -- Sten Spans There is a crack in everything that's how the light gets in. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On 02-Dec-2003 Scott Long wrote: On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote: On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote: This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. Show stopper defects for 5.2-RELEASE ++ | Issue | Status |Responsible |Description| |---+---++---| | | ||The new i386 interrupt code| |ACPI kernel| ||requires that ACPI be compiled into| |module |In progress|John Baldwin|the kernel if it to be used. Work | | | ||is underway to restore the ability | | | ||to load it as a module.| |---+---++---| I'm currently investigating ACPI problems on a dual processor Intel motherboard (re@ knows about this). It looks as if the new code is much fussier than the old code about the quality of the motherboard BIOS: this machine runs fine on 5.1, but won't finish booting on 5.2-BETA. Yes, this is probably an ACPI bug, but users aren't going to see it that way: if we release a 5.2 which won't boot on a lot of machines, people are going to blame 5.2, not the machine. I think we should ensure that there's at least a fallback for machines with broken ACPI. This argument is exactly why I added the 'disable acpi' option in the boot loader menu. Of course, we STILL need to get good debugging information from you as to why you get a Trap 9 when ACPI is disabled. This is the more important issue. This is actually a known issue on Intel motherboards. Somehow we broke something in our bios32 code. 4.x works fine using the BIOS to enumerate PNP BIOS devices, but 5.x (including 5.0 and 5.1) get a GPF (Trap 9) with the code segment set to 0x58 trying to enumerate the last PNPBIOS device. Somehow the BIOS routine jumps off into lala land where it eventually traps. I dumped the BIOS and dissassembled and tried to walk it to figure out how it was breaking but couldn't see anything obvious. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Mon, 1 Dec 2003, Scott Long wrote: On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote: On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote: ... I'm currently investigating ACPI problems on a dual processor Intel motherboard (re@ knows about this). It looks as if the new code is much fussier than the old code about the quality of the motherboard BIOS: this machine runs fine on 5.1, but won't finish booting on 5.2-BETA. Yes, this is probably an ACPI bug, but users aren't going to see it that way: if we release a 5.2 which won't boot on a lot of machines, people are going to blame 5.2, not the machine. I think we should ensure that there's at least a fallback for machines with broken ACPI. This argument is exactly why I added the 'disable acpi' option in the boot loader menu. Of course, we STILL need to get good debugging information from you as to why you get a Trap 9 when ACPI is disabled. This is the more important issue. Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
Tom wrote: Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Are you using a PERC in those boxes? I've seen issues with PERC controllers on 5.1, but 4.8 worked fine. I received a patch, which fixed it, but it's a bit hard to install the os, and then rebuild world without rebooting the machine. :) Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
: This argument is exactly why I added the 'disable acpi' option in the boot : loader menu. Of course, we STILL need to get good debugging information : from you as to why you get a Trap 9 when ACPI is disabled. This is the : more important issue. : :This is actually a known issue on Intel motherboards. Somehow we broke :something in our bios32 code. 4.x works fine using the BIOS to enumerate :PNP BIOS devices, but 5.x (including 5.0 and 5.1) get a GPF (Trap 9) :with the code segment set to 0x58 trying to enumerate the last PNPBIOS :device. Somehow the BIOS routine jumps off into lala land where it :eventually traps. I dumped the BIOS and dissassembled and tried to walk :it to figure out how it was breaking but couldn't see anything obvious. : :-- : :John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ I have a motherboard that even 4.x doesn't work on... same deal, GPF while enumerating PNP devices. It died on the 6th device or something like that. I went so far as to 'fix' DDB's disassembler (in DFly) to properly decode the code segment (instead of double faulting on a 'bad' EIP in DDB) and properly show 16 bit instructions, and I set break points and single-stepped through. It died in the same place every time, during an attempt to issue a write to a CS: prefixed memory address. But I suspect a bad branch or indirect-jump table lookup. I finally gave up but if I were to do it again I would attach a serial console and record the single-step session all the way through two device number iterations... the one prior to the one that failed, and the one that failed, then I'd compare the output for the successful device iteration verses the failure to figure out where they diverge. That's what I suggest... don't play around, just connect the serial console, fix DDB's disassembler (you can pop the changes that I made in DFly, they should be the same), single step through two iterations, and compare. If you figure out what is causing the problem I'd love an email. I suspect it is a mapping overlap somewhere due to the page 0 map. I just can't think of anything else it might be. -Matt Matthew Dillon [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Show stopper defects for 5.2-RELEASE ++ | Issue | Status |Responsible |Description| |---+---++---| |Panic when | || | |rebuilding |Not done |-- |The panic reported in PR kern/58228| |ata-raid | ||must be fixed. | |arrays | || | |---+---++---| | | ||panic: Assertion td-td_turnstile | | | ||!= NULL failed at | | | ||../../../kern/subr_turnstile.c:427 | | | ||has been affecting several users on| | | ||multiple platforms. Note: further | |Turnstile | ||research indicates that these | |assertion |In progress|John Baldwin|panics tend to be double panics | |failure| ||that are a side effect of the | | | ||turnstile code in the context of an| | | ||existing panic. Reporters of this | | | ||panic should make sure to include a| | | ||full stack trace so that it's clear| | | ||if a second panic is also present. | |---+---++---| | | ||The new i386 interrupt code| |ACPI kernel| ||requires that ACPI be compiled into| |module |In progress|John Baldwin|the kernel if it to be used. Work | | | ||is underway to restore the ability | | | ||to load it as a module.| |---+---++---| | | ||There have been a number of reports| |Reported | ||of NFS clients and server hangs. | |NFS|In progress||Unfortunately, these are difficult | |failures | ||to reproduce, and have not yet been| | | ||traced back to a particular change | | | ||or reliable reproduction scenario. | ++ Required features for 5.2-RELEASE ++ | Issue | Status| Responsible | Description| |-+-+-+--| | | | | Kernel and userland bits | | KSE support for | | Jake| are implemented but | | sparc64 | In progress | Burkholder | untested and known to be | | | | | incomplete. Required for | | | | | 5.2-RELEASE. | |-+-+-+--| | | | | Userland bits| | KSE support for | | Marcel | implemented, kernel bits | | alpha | In progress | Moolenaar | not implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+-+-+--| | | | | Significant parts of the | | | | | network stack| | | | | (especially IPv4 and | | | | | IPv6) now have | | | | | fine-grained locking of | | | | | their data structures. | | | | | However, it is not yet | | | | | possible for the netisr | |
Re: 5.2-RELEASE TODO
On Mon, 1 Dec 2003 10:01:23 -0500 (EST) Robert Watson [EMAIL PROTECTED] wrote: This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. Just wondering if, when one is announced, you could include in this messages the release date forecast. -- Cogeco ergo sum pgp0.pgp Description: PGP signature
Re: 5.2-RELEASE TODO
On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote: This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. Show stopper defects for 5.2-RELEASE ++ | Issue | Status |Responsible |Description| |---+---++---| | | ||The new i386 interrupt code| |ACPI kernel| ||requires that ACPI be compiled into| |module |In progress|John Baldwin|the kernel if it to be used. Work | | | ||is underway to restore the ability | | | ||to load it as a module.| |---+---++---| I'm currently investigating ACPI problems on a dual processor Intel motherboard (re@ knows about this). It looks as if the new code is much fussier than the old code about the quality of the motherboard BIOS: this machine runs fine on 5.1, but won't finish booting on 5.2-BETA. Yes, this is probably an ACPI bug, but users aren't going to see it that way: if we release a 5.2 which won't boot on a lot of machines, people are going to blame 5.2, not the machine. I think we should ensure that there's at least a fallback for machines with broken ACPI. Greg -- See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Re: 5.2-RELEASE TODO
On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote: On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote: This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. Show stopper defects for 5.2-RELEASE ++ | Issue | Status |Responsible |Description| |---+---++---| | | ||The new i386 interrupt code| |ACPI kernel| ||requires that ACPI be compiled into| |module |In progress|John Baldwin|the kernel if it to be used. Work | | | ||is underway to restore the ability | | | ||to load it as a module.| |---+---++---| I'm currently investigating ACPI problems on a dual processor Intel motherboard (re@ knows about this). It looks as if the new code is much fussier than the old code about the quality of the motherboard BIOS: this machine runs fine on 5.1, but won't finish booting on 5.2-BETA. Yes, this is probably an ACPI bug, but users aren't going to see it that way: if we release a 5.2 which won't boot on a lot of machines, people are going to blame 5.2, not the machine. I think we should ensure that there's at least a fallback for machines with broken ACPI. This argument is exactly why I added the 'disable acpi' option in the boot loader menu. Of course, we STILL need to get good debugging information from you as to why you get a Trap 9 when ACPI is disabled. This is the more important issue. Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Monday, 1 December 2003 at 17:12:23 -0700, Scott Long wrote: On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote: On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote: This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. Show stopper defects for 5.2-RELEASE I'm currently investigating ACPI problems on a dual processor Intel motherboard (re@ knows about this). It looks as if the new code is much fussier than the old code about the quality of the motherboard BIOS: this machine runs fine on 5.1, but won't finish booting on 5.2-BETA. Yes, this is probably an ACPI bug, but users aren't going to see it that way: if we release a 5.2 which won't boot on a lot of machines, people are going to blame 5.2, not the machine. I think we should ensure that there's at least a fallback for machines with broken ACPI. This argument is exactly why I added the 'disable acpi' option in the boot loader menu. Of course, we STILL need to get good debugging information from you as to why you get a Trap 9 when ACPI is disabled. This is the more important issue. I've sent information, and I'm waiting for feedback about what to do next. The fact that the stack is completely trashed doesn't help, admittedly. Greg -- See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Show stopper defects for 5.2-RELEASE ++ | Issue| Status | Responsible |Description | |++-+| | Panic when || | The panic reported in PR | | rebuilding | -- | -- | kern/58228 must be fixed. | | ata-raid arrays|| || |++-+| ||| | Kris Kennaway reports that | ||| | Alpha packages builds are | | pipe/VM corruption | -- | -- | being silently corrupted | | on Alpha || | and suspects pipe and vm | ||| | issues. This must be | ||| | investigated and resolved. | |++-+| ||| | The panic reported in PR | | Lingering PSE | -- | -- | kern/58787 is likely | | instability|| | related to PSE problems| ||| | and must be fixed. | ++ Required features for 5.2-RELEASE ++ | Issue |Status| Responsible | Description | |-+--+---+---| | | | | Kernel and userland | | | | | bits are implemented | | KSE support for | In progress | Jake | but untested and | | sparc64 | | Burkholder| known to be | | | | | incomplete. Required | | | | | for 5.2-RELEASE. | |-+--+---+---| | | | | Userland bits | | KSE support for | | Marcel| implemented, kernel | | alpha | In progress. | Moolenaar | bits not implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+--+---+---| | | | | Significant parts of | | | | | the network stack | | | | | (especially IPv4 and | | | | | IPv6) now have| | | | | fine-grained locking | | | | | of their data | | | | | structures. However, | | | | | it is not yet | | | | | possible for the | | | | | netisr threads to run | | Fine-grained| | | without Giant, due to | | network stack | | | dependencies on | | locking without | In progress | Sam Leffler | sockets, routing, | | Giant | | | etc. A 5.2-RELEASE| | | | | goal is to have the | | | | | network stack running | | | | | largely without | | | | | Giant, which should | | | | | substantially improve | | | | | performance of the| | | | | stack, as well as | | | | | other system | | | | | components by | |
5.2-RELEASE TODO
[NOTE: This is being resent due to a cvs update error that caused an un-updated version of the TODO list to be sent out earlier] This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
Sigh. Try three to follow. My script was checking out only the www tree, and the checkout of the doc tree it depended on was gradually getting stale. At some point, it picked up a new dependency in the doc tree and the build broke. Hopefully third time will be the charm. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Senior Research Scientist, McAfee Research On Sat, 29 Nov 2003, Robert Watson wrote: [NOTE: This is being resent due to a cvs update error that caused an un-updated version of the TODO list to be sent out earlier] This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. ___ [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]
5.2-RELEASE TODO
[NOTE: This is being resent due to a cvs update error that caused an un-updated version of the TODO list to be sent out earlier] This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Show stopper defects for 5.2-RELEASE ++ | Issue | Status |Responsible |Description| |---+---++---| |Panic when | || | |rebuilding |Not done |-- |The panic reported in PR kern/58228| |ata-raid | ||must be fixed. | |arrays | || | |---+---++---| | | ||Kris Kennaway reports that Alpha | |pipe/VM| ||packages builds are being silently | |corruption |Not done |-- |corrupted and suspects pipe and vm | |on Alpha | ||issues. This must be investigated | | | ||and resolved. | |---+---++---| | | ||panic: Assertion td-td_turnstile | | | ||!= NULL failed at | | | ||../../../kern/subr_turnstile.c:427 | | | ||has been affecting several users on| | | ||multiple platforms. Note: further | |Turnstile | ||research indicates that these | |assertion |In progress|John Baldwin|panics tend to be double panics | |failure| ||that are a side effect of the | | | ||turnstile code in the context of an| | | ||existing panic. Reporters of this | | | ||panic should make sure to include a| | | ||full stack trace so that it's clear| | | ||if a second panic is also present. | |---+---++---| | | ||The new i386 interrupt code| |ACPI kernel| ||requires that ACPI be compiled into| |module |In progress|John Baldwin|the kernel if it to be used. Work | | | ||is underway to restore the ability | | | ||to load it as a module.| |---+---++---| | | ||There have been a number of reports| |Reported | ||of NFS clients and server hangs. | |NFS|In progress||Unfortunately, these are difficult | |failures | ||to reproduce, and have not yet been| | | ||traced back to a particular change | | | ||or reliable reproduction scenario. | ++ Required features for 5.2-RELEASE ++ | Issue | Status| Responsible | Description| |-+-+-+--| | | | | Kernel and userland bits | | KSE support for | | Jake| are implemented but | | sparc64 | In progress | Burkholder | untested and known to be | | | | | incomplete. Required for | | | | | 5.2-RELEASE. | |-+-+-+--| | | | | Userland bits| | KSE support for | | Marcel | implemented, kernel bits | | alpha | In progress | Moolenaar | not implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+-+-+--| | | |
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Show stopper defects for 5.2-RELEASE ++ | Issue| Status | Responsible |Description | |++-+| | Panic when || | The panic reported in PR | | rebuilding | -- | -- | kern/58228 must be fixed. | | ata-raid arrays|| || |++-+| ||| | Kris Kennaway reports that | ||| | Alpha packages builds are | | pipe/VM corruption | -- | -- | being silently corrupted | | on Alpha || | and suspects pipe and vm | ||| | issues. This must be | ||| | investigated and resolved. | |++-+| ||| | The panic reported in PR | | Lingering PSE | -- | -- | kern/58787 is likely | | instability|| | related to PSE problems| ||| | and must be fixed. | ++ Required features for 5.2-RELEASE ++ | Issue |Status| Responsible | Description | |-+--+---+---| | | | | Kernel and userland | | | | | bits are implemented | | KSE support for | In progress | Jake | but untested and | | sparc64 | | Burkholder| known to be | | | | | incomplete. Required | | | | | for 5.2-RELEASE. | |-+--+---+---| | | | | Userland bits | | KSE support for | | Marcel| implemented, kernel | | alpha | In progress. | Moolenaar | bits not implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+--+---+---| | | | | Significant parts of | | | | | the network stack | | | | | (especially IPv4 and | | | | | IPv6) now have| | | | | fine-grained locking | | | | | of their data | | | | | structures. However, | | | | | it is not yet | | | | | possible for the | | | | | netisr threads to run | | Fine-grained| | | without Giant, due to | | network stack | | | dependencies on | | locking without | In progress | Sam Leffler | sockets, routing, | | Giant | | | etc. A 5.2-RELEASE| | | | | goal is to have the | | | | | network stack running | | | | | largely without | | | | | Giant, which should | | | | | substantially improve | | | | | performance of the| | | | | stack, as well as | | | | | other system | | | | | components by | |
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Show stopper defects for 5.2-RELEASE ++ | Issue | Status| Responsible | Description | |-+-++---| | Panic when | || The panic reported in | | rebuilding | -- | -- | PR kern/58228 must be | | ata-raid arrays | || fixed.| |-+-++---| | | || Performing a | | | || crashdump on an ATA | | ATAng crashdump | | So/ren Schmidt | device can result in | | causes disk | In Progress | Tor Egge | a corrupted MBR | | corruption | || record. Tor has a | | | || possible patch for| | | || this. | |-+-++---| | | || Kris Kennaway reports | | | || that Alpha packages | | pipe/VM | || builds are being | | corruption on | -- | -- | silently corrupted| | Alpha | || and suspects pipe and | | | || vm issues. This must | | | || be investigated and | | | || resolved. | |-+-++---| | | || The panic reported in | | Lingering PSE | || PR kern/58787 is | | instability | -- | -- | likely related to PSE | | | || problems and must be | | | || fixed.| ++ Required features for 5.2-RELEASE ++ | Issue |Status| Responsible | Description | |-+--+---+---| | | | | Kernel and userland | | | | | bits are implemented | | KSE support for | In progress | Jake | but untested and | | sparc64 | | Burkholder| known to be | | | | | incomplete. Required | | | | | for 5.2-RELEASE. | |-+--+---+---| | | | | Userland bits | | KSE support for | | Marcel| implemented, kernel | | alpha | In progress. | Moolenaar | bits not implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+--+---+---| | | | | Significant parts of | | | | | the network stack | | | | | (especially IPv4 and | | | | | IPv6) now have| | | | | fine-grained locking | | | | | of their data | | | | | structures. However, | | | | | it is not yet | | | | | possible for the | | | | | netisr threads to run | | Fine-grained| | | without Giant, due to | | network stack | | | dependencies on | | locking
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Show stopper defects for 5.2-RELEASE ++ | Issue | Status| Responsible | Description | |+-++| | Panic when | || The panic reported in | | rebuilding | -- | -- | PR kern/58228 must be | | ata-raid | || fixed. | | arrays | ||| |+-++| || || The LOR reported in PR | | filedesc LOR | -- | -- | kern/55175 must be | || || fixed. | |+-++| || || Performing a crashdump | | ATAng | || on an ATA device can | | crashdump | In Progress | So/ren Schmidt | result in a corrupted | | causes disk| | Tor Egge | MBR record. Tor has a | | corruption | || possible patch for | || || this. | |+-++| || || ATAng driver looses| || || device interrupts in | | ATAng lost | || certain scenarios, | | interrupts | In Progress | So/ren Schmidt | leading to hangs and | || || poor performance. | || || Possibly related to| || || timing problems. | |+-++| || || Kris Kennaway reports | || || that Alpha packages| | pipe/VM| || builds are being | | corruption on | -- | -- | silently corrupted and | | Alpha | || suspects pipe and vm | || || issues. This must be | || || investigated and | || || resolved. | |+-++| || || Kris Kennaway reports | || || high instability of| || || 5-CURRENT on ia64 | || | Marcel | machines, such as the | | ia64 stability | In Progress | Moolenaar | pluto* machines. These | || || problems need to be| || || fixed in order to get | || || a successful package | || || build. | |+-++| || || Brian Feldman has | || || submitted patches to | || || improve the| || || consistency of the | | MAC Framework | || pathnames passed into | | devfs path | In progress | Robert Watson | the MAC Framework | | fixes | || devfs labeling entry | || || points. These patches | || || need to be thoroughly | || || reviewed and tested, | || || then merged. | |+-++| || ||
Re: 5.2-RELEASE TODO
On Wed, Oct 29, 2003 at 10:00:22AM -0500, Robert Watson wrote: This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: Desired features for 5.2-RELEASE ++ | Issue| Status | Responsible | Description | |+---++--| || || The PCM autdio | || || framework and device | || || drivers have been| || || locked and free of | || || Giant for quite a| | PCM locking and| || while, but LOR | | performance issues | --| -- | problems persist | || || along with reports | || || of poor audio| || || performance under| || || load. The locking| || || needs to be reviewed | || || and corrected. | |+---++--| I just want to notify that Mathew Kanner mat [at] cnd.mcgill.ca sends some sound LOR patches into the -current maillist. -- Rgdz,/\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible |Description | |-+---+-+| | | | | KSE M:N threading | | | | | support is | | | | | reaching | | | | | experimental yet | | | | Julian | usable status on | | Production-quality | In| Elischer, David | i386 for | | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N | | | | Eischen | threading should | | | | | be productionable | | | | | and usable on all | | | | | platforms by | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kernel bits are| | | | | implemented but| | KSE support for | In| | untested. Userland | | sparc64 | progress | Jake Burkholder | bits are not | | | | | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Userland bits | | | | | implemented, | | KSE support for | In| Marcel | kernel bits not| | alpha | progress. | Moolenaar | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kris Kennaway | | | | | reports high | | | | | instability of | | | | | 5-CURRENT on ia64 | | | | | machines, such as | | ia64 stability | In| Marcel | the pluto* | | | Progress | Moolenaar | machines. These| | | | | problems need to | | | | | be fixed in order | | | | | to get a | | | | | successful package | | | | | build. | |-+---+-+| | | | | FAST_IPSEC | | | | | currently cannot | | | | | be used directly | | | | | with the KAME IPv6 | | | | | implementation,| | | | | requiring an | | | | | additional level | | | | | of IP tunnel | | | | | indirection to | | | | | protect IPv6 | | | | | packets when using | | | | | hardware crypto| | FAST_IPSEC and KAME | | | acceleration. This | | compatibility | --| -- | issue must be | | | |
Re: 5.2-RELEASE TODO
On Wed, 15 Oct 2003, Robert Watson wrote: Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] |-+---+-+| | | | | Kernel bits are| | | | | implemented but| | KSE support for | In| | untested. Userland | | sparc64 | progress | Jake Burkholder | bits are not | | | | | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| Userland bits are implemented but don't yet work. Jake said he would take a look at them. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Wed, Oct 01, 2003 at 10:00:18AM -0400, Robert Watson wrote: FreeBSD 5.2 Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE It would be nice if fixing the Raidframe driver could be added to the must resolve list, or a note added to the release notes explaining that's it's broken. It's been totally unusable since before 5.1-RELEASE (raidctl panics). See kern/50541. -- Pierre Beyssac [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible |Description | |-+---+-+| | | | | KSE M:N threading | | | | | support is | | | | | reaching | | | | | experimental yet | | | | Julian | usable status on | | Production-quality | In| Elischer, David | i386 for | | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N | | | | Eischen | threading should | | | | | be productionable | | | | | and usable on all | | | | | platforms by | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kernel bits are| | | | | implemented but| | KSE support for | In| | untested. Userland | | sparc64 | progress | Jake Burkholder | bits are not | | | | | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Userland bits | | | | | implemented, | | KSE support for | In| Marcel | kernel bits not| | alpha | progress. | Moolenaar | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kris Kennaway | | | | | reports high | | | | | instability of | | | | | 5-CURRENT on ia64 | | | | | machines, such as | | ia64 stability | In| Marcel | the pluto* | | | Progress | Moolenaar | machines. These| | | | | problems need to | | | | | be fixed in order | | | | | to get a | | | | | successful package | | | | | build. | |-+---+-+| | | | | FAST_IPSEC | | | | | currently cannot | | | | | be used directly | | | | | with the KAME IPv6 | | | | | implementation,| | | | | requiring an | | | | | additional level | | | | | of IP tunnel | | | | | indirection to | | | | | protect IPv6 | | | | | packets when using | | | | | hardware crypto| | FAST_IPSEC and KAME | | | acceleration. This | | compatibility | --| -- | issue must be | | | |
Way Down [The Line] (was: 5.2-RELEASE TODO)
Dan Nelson wrote: In the last episode (Sep 29), Wilko Bulte said: On Mon, Sep 29, 2003 at 12:19:30PM -0700, Marcel Moolenaar wrote: I also mentioned recently (in the last couple of days) that we should worry more about sparc64 than alpha. Simply because I think alpha is on it's way down and should already be a tier 2 platform and sparc64 is still on its way up ... sort of. In my book sparc64 is also with one foot in the grave. As is Sun itself. Fujitsu makes sparc-compatible CPUs, too, so it'll be harder to kill the entire architecture like HP did with the Alpha. Alpha was buried by DEC itself, with a little help from Compaq. Vague marketing policy and the way they supported OEMs led to the disaster. Samsung tried to change something, but it was too late. Besides, it was hard to promote 21264 without an adequate chipset: AMD-751 wasn't able to supply neccessary memory bandwidth, DEC Tsunami and Typhoon were, but Tsunami was offered to OEMs by Compaq for over a thousand USD per set... Unfortunately, AMD-761 appeared too late to help Alpha in its final struggle. HP has only confirmed the lethal issue, thus ceasing this agony. But Alpha will always live in our hearts :( --- Regards, Rhett Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible |Description | |-+---+-+| | | | | KSE M:N threading | | | | | support is | | | | | reaching | | | | | experimental yet | | | | Julian | usable status on | | Production-quality | In| Elischer, David | i386 for | | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N | | | | Eischen | threading should | | | | | be productionable | | | | | and usable on all | | | | | platforms by | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kernel bits are| | | | | implemented but| | KSE support for | In| | untested. Userland | | sparc64 | progress | Jake Burkholder | bits are not | | | | | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kernel and | | KSE support for | | Marcel | userland bits | | ia64| Complete. | Moolenaar | implemented but| | | | | unstable. Required | | | | | for 5.2-RELEASE. | |-+---+-+| | | | | Userland bits | | | | | implemented, | | KSE support for | In| Marcel | kernel bits not| | alpha | progress. | Moolenaar | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kris Kennaway | | | | | reports high | | | | | instability of | | | | | 5-CURRENT on ia64 | | | | | machines, such as | | ia64 stability | In| Marcel | the pluto* | | | Progress | Moolenaar | machines. These| | | | | problems need to | | | | | be fixed in order | | | | | to get a | | | | | successful package | | | | | build. | |-+---+-+| | | | | A reworking of the | | | | | sio driver is | | | | | needed to support | | | | | serial terminal| | | | Marcel | devices on sparc64 | | New serial UART | In| Moolenaar, | and ia64 | | framework | progress | Warner Losh | platforms, among | | | | | others. This is| | | |
Re: 5.2-RELEASE TODO
On Mon, 29 Sep 2003, Robert Watson wrote: |-+---+-+| | | | | Userland bits | | | | | implemented, | | KSE support for | In| Marcel | kernel bits not| | alpha | progress. | Moolenaar | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | You should probably remove Marcel from this item. This task needs another volunteer. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Mon, Sep 29, 2003 at 02:05:16PM -0400, Daniel Eischen wrote: On Mon, 29 Sep 2003, Robert Watson wrote: |-+---+-+| | | | | Userland bits | | | | | implemented, | | KSE support for | In| Marcel | kernel bits not| | alpha | progress. | Moolenaar | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | You should probably remove Marcel from this item. This task needs another volunteer. Recently Marcel noted to me he was planning to engage on this one. I have offered him help for testing. -- | / 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: 5.2-RELEASE TODO
On Mon, 29 Sep 2003, Wilko Bulte wrote: On Mon, Sep 29, 2003 at 02:05:16PM -0400, Daniel Eischen wrote: On Mon, 29 Sep 2003, Robert Watson wrote: |-+---+-+| | | | | Userland bits | | | | | implemented, | | KSE support for | In| Marcel | kernel bits not| | alpha | progress. | Moolenaar | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | You should probably remove Marcel from this item. This task needs another volunteer. Recently Marcel noted to me he was planning to engage on this one. I have offered him help for testing. OK. This differs from what I heard from him just a couple of days ago. I'll just shut up and let things lie (as in rest) ;-) -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Mon, Sep 29, 2003 at 08:07:32PM +0200, Wilko Bulte wrote: You should probably remove Marcel from this item. This task needs another volunteer. Recently Marcel noted to me he was planning to engage on this one. I have offered him help for testing. The deal is this (if you find your way between the parenthesis): I talked to Wilko prior to the DevSummit and told him that since it was on my plate (because I stupidly made some commits to get things rolling; which it did, but not much more than rolling on my plate :-) and support is almost finished (I looked at it this weekend and it appears that upcalls work, there's probably something wrong with the context save/restore code) and I needed to fix ia64 as which (already done) I likely would fix Alpha in one big swoop. At the DevSummit we failed to reach agreement that alpha should be dropped to a tier 2 platform, but we did acknowledge that alpha needs developers pronto. There it was also agreed that I would enter a holding pattern (which roughly boils down to me circling between home, work and Starbucks) until either someone fixes KSE or my weakness shows and I do it anyway (the fact that I looked at it this weekend means that I was pretty close to folding -- I made it to Starbucks just in time). I also mentioned recently (in the last couple of days) that we should worry more about sparc64 than alpha. Simply because I think alpha is on it's way down and should already be a tier 2 platform and sparc64 is still on its way up ... sort of. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Mon, Sep 29, 2003 at 12:19:30PM -0700, Marcel Moolenaar wrote: On Mon, Sep 29, 2003 at 08:07:32PM +0200, Wilko Bulte wrote: You should probably remove Marcel from this item. This task needs another volunteer. Recently Marcel noted to me he was planning to engage on this one. I have offered him help for testing. The deal is this (if you find your way between the parenthesis): ... At the DevSummit we failed to reach agreement that alpha should be dropped to a tier 2 platform, but we did acknowledge that alpha needs developers pronto. There it was also agreed that I would enter a holding pattern (which roughly boils down to me circling between home, work and Starbucks) until either someone fixes KSE or my weakness shows and I do it anyway (the fact that I looked at it this weekend means that I was pretty close to folding -- I made it to Starbucks just in time). You get red hair from too much coffee anyway :-) :-) I also mentioned recently (in the last couple of days) that we should worry more about sparc64 than alpha. Simply because I think alpha is on it's way down and should already be a tier 2 platform and sparc64 is still on its way up ... sort of. In my book sparc64 is also with one foot in the grave. As is Sun itself. If we want to be future proof ia64 and amd64 are the only viable architectures. The rest are just interesting passtimes.. -- | / 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: 5.2-RELEASE TODO
In the last episode (Sep 29), Wilko Bulte said: On Mon, Sep 29, 2003 at 12:19:30PM -0700, Marcel Moolenaar wrote: I also mentioned recently (in the last couple of days) that we should worry more about sparc64 than alpha. Simply because I think alpha is on it's way down and should already be a tier 2 platform and sparc64 is still on its way up ... sort of. In my book sparc64 is also with one foot in the grave. As is Sun itself. Fujitsu makes sparc-compatible CPUs, too, so it'll be harder to kill the entire architecture like HP did with the Alpha. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
In message [EMAIL PROTECTED], Dan Nelson writes: In my book sparc64 is also with one foot in the grave. As is Sun itself. Fujitsu makes sparc-compatible CPUs, too, so it'll be harder to kill the entire architecture like HP did with the Alpha. Having at least on architecture with the other byte order helps keep our code honest. I also think that VM afflicted people tend to think that it is a good idea to have another model in order to keep MI separated properly from MD. Alpha has sort of outlived its role as our token architecture, pc98 doesn't qualify due to inbreeding, amd64 doesn't qualify due to nepotism, ia64 is not yet there. That leaves us only sparc64 as candidate for that job. Therefore I would like to keep the sparc64 port alive, even at a pretty high cost in effort. -- 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]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible |Description | |-+---+-+| | | | | KSE M:N threading | | | | | support is | | | | | reaching | | | | | experimental yet | | | | Julian | usable status on | | Production-quality | In| Elischer, David | i386 for | | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N | | | | Eischen | threading should | | | | | be productionable | | | | | and usable on all | | | | | platforms by | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kernel bits are| | | | | implemented but| | KSE support for | In| | untested. Userland | | sparc64 | progress | Jake Burkholder | bits are not | | | | | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kernel and | | KSE support for | | Marcel | userland bits | | ia64| Complete. | Moolenaar | implemented but| | | | | unstable. Required | | | | | for 5.2-RELEASE. | |-+---+-+| | | | | Userland bits | | | | | implemented, | | KSE support for | In| Marcel | kernel bits not| | alpha | progress. | Moolenaar | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kris Kennaway | | | | | reports high | | | | | instability of | | | | | 5-CURRENT on ia64 | | | | | machines, such as | | ia64 stability | In| Marcel | the pluto* | | | Progress | Moolenaar | machines. These| | | | | problems need to | | | | | be fixed in order | | | | | to get a | | | | | successful package | | | | | build. | |-+---+-+| | | | | A reworking of the | | | | | sio driver is | | | | | needed to support | | | | | serial terminal| | | | Marcel | devices on sparc64 | | New serial UART | In| Moolenaar, | and ia64 | | framework | progress | Warner Losh | platforms, among | | | | | others. This is| | | |
Re: 5.2-RELEASE TODO
On Wed, Sep 03, 2003 at 08:27:17PM -0700, Peter Wemm wrote: Sorry, I missed this when I did my scrub yesterday. I'll fix it now. Btw, does X work on it? Can I compile/install it without hassle? Yes. It installs Just Fine. You wont even notice the difference relative to an i386 machine. X builds/runs. I dont think the Xserver port packages yet though, but it does build. I think David is working on that. It packages now. :-) I've got a package to put on ftp-master if I can find a good place for it. -- -- David ([EMAIL PROTECTED]) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
Scott Long wrote: Btw, does X work on it? Can I compile/install it without hassle? I've tried. portinstall XFree86-Server succeeded with no error. But XFree86 -configure dumps core and exits abnormally. In /var/log/messages: kernel: pid 23797 (XFree86), uid 0: exited on signal 6 (core dumped) and XFree86.0.log reports: (stuff deleted) (II) Primary Device is: PCI 03:06:0 Symbol VBEGetModePool from module /usr/X11R6/lib/modules/drivers/vesa_drv.o is u nresolved! Symbol xf86InterpretEDID from module /usr/X11R6/lib/modules/drivers/sis_drv.o is unresolved! *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 10. Server aborting When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] Examining core file with gdb 3.3 (oops, gdb isn't in FreeBSD/amd64) shows as follows. kuroyebisu# gdb /usr/X11R6/bin/XFree86 GNU gdb 20030829 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-unknown-freebsd5.1... (gdb) core-file XFree86.core Core was generated by `XFree86'. Program terminated with signal 6, Aborted. Reading symbols from /lib/libz.so.2...done. Loaded symbols for /lib/libz.so.2 Reading symbols from /lib/libm.so.2...done. Loaded symbols for /lib/libm.so.2 Reading symbols from /lib/libc.so.5...done. Loaded symbols for /lib/libc.so.5 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x20a07884 in kill () from /lib/libc.so.5 BTW, is SMP support for amd64 in progress? -- FUJIMOTO Kou, Tokyo Denki University http://www.j.dendai.ac.jp/~fujimoto/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
Scott Long wrote: David O'Brien wrote: On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote: |-+---+-+| | | | | Productionable | | | | | support for the| | | | | AMD64 platform.| | | | | Currently, AMD64 | | | | | runs fully in | | | | | 32-bit emulation | | Tier-1 Support for | In| Peter Wemm, | mode, and boots to | | AMD64 Hammer| progress | David O'Brien | single-user in | | | | | 64-bit mode. We| | | | | expect full| | | | | production support | | | | | for the AMD64 | | | | | architecture in| | | | | 5.2-RELEASE. | |-+---+-+| PLEASE, PLEASE update this. Not implying that FreeBSD/amd64 doesn't make it multiuser and can build its own world would be sufficient. Sorry, I missed this when I did my scrub yesterday. I'll fix it now. Btw, does X work on it? Can I compile/install it without hassle? Yes. It installs Just Fine. You wont even notice the difference relative to an i386 machine. X builds/runs. I dont think the Xserver port packages yet though, but it does build. I think David is working on that. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO -2
On Mon, 1 Sep 2003, Nicole wrote: It just drives me crazy when important things get broken and people act like.. What the big deal. I don't need it why should you? You're certainly free to draw that conclusion, however you'd be mistaken. There are times when adding new features means that things change. That's life in a volunteer project. If this isn't to your liking, feel free to move on, or get to work restoring functionality that you think is important. Either way, you need to dial down the rhetoric quite a bit if you expect people to help you. I still have not solved the going to comsonsole mode if there is no keyboard detected crap, new feature. Yea great for those who could benifit from it.. But I have YET to have one person be able to show me how to STOP it from doing that. Remove the 0x01 flag from the atkbd0 line in your kernel config. -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO -2
On 02-Sep-03 Unnamed Administration sources reported Doug Barton said : On Mon, 1 Sep 2003, Nicole wrote: It just drives me crazy when important things get broken and people act like.. What the big deal. I don't need it why should you? You're certainly free to draw that conclusion, however you'd be mistaken. There are times when adding new features means that things change. That's life in a volunteer project. If this isn't to your liking, feel free to move on, or get to work restoring functionality that you think is important. Either way, you need to dial down the rhetoric quite a bit if you expect people to help you. Sorry I didn't mean to be so testy I guess would discribe it. It's an old issue for me. Every so often I try asking for help with it, and its usually the response I get :( So you are correct. I am infolving old feelings etc when I shoudl not be. Sorry. I still have not solved the going to comsonsole mode if there is no keyboard detected crap, new feature. Yea great for those who could benifit from it.. But I have YET to have one person be able to show me how to STOP it from doing that. Remove the 0x01 flag from the atkbd0 line in your kernel config. I will give that a shot. Thats certainly different than abyone else has suggested. In my 5.1 system I see this in my .hints file. So I assume I edit it there or do I treat it like a defaults file and import and change in in my config file? Thanks for the assist ! Nicole -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] |\ __ /| (`\ | o_o |__ ) ) // \\ - [EMAIL PROTECTED] - Powered by FreeBSD - -- Daemons will now be known as spiritual guides -Politically Correct UNIX Page ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO -2
On Mon, 1 Sep 2003, Nicole wrote: Sorry I didn't mean to be so testy I guess would discribe it. It's an old issue for me. Not to put too fine a point on it, but I've seen numerous posts from you, on several topics, all of them berating people for not giving you what you want, when you wanted it. I tend to ignore posts from you for just this reason. Remove the 0x01 flag from the atkbd0 line in your kernel config. I will give that a shot. Thats certainly different than abyone else has suggested. That's because they didn't understand the problem you were trying to solve. In my 5.1 system I see this in my .hints file. So I assume I edit it there or do I treat it like a defaults file and import and change in in my config file? I didn't say anything about your hints file. You need to edit your kernel config file, build a new kernel, then reboot. If any of that is confusing to you, please follow up on freebsd-questions, since people running -current are assumed to have that base of knowledge. Hope this helps, Doug -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO -2
Doug Barton wrote: On Mon, 1 Sep 2003, Nicole wrote: In my 5.1 system I see this in my .hints file. So I assume I edit it there or do I treat it like a defaults file and import and change in in my config file? I didn't say anything about your hints file. You need to edit your kernel config file, build a new kernel, then reboot. If any of that is confusing to you, please follow up on freebsd-questions, since people running -current are assumed to have that base of knowledge. Hope this helps, Doug Device flags are not specified in the kernel config anymore unless you try really, really hard. /etc/device.hints is the correct place to adjust this flag. Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO -2
Scott Long wrote: Doug Barton wrote: On Mon, 1 Sep 2003, Nicole wrote: In my 5.1 system I see this in my .hints file. So I assume I edit it there or do I treat it like a defaults file and import and change in in my config file? I didn't say anything about your hints file. You need to edit your kernel config file, build a new kernel, then reboot. If any of that is confusing to you, please follow up on freebsd-questions, since people running -current are assumed to have that base of knowledge. Hope this helps, Doug Device flags are not specified in the kernel config anymore unless you try really, really hard. /etc/device.hints is the correct place to adjust this flag. Scott Of course I mean '/boot/device.hints' =-) Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO -2
On Mon, 1 Sep 2003, Scott Long wrote: Device flags are not specified in the kernel config anymore unless you try really, really hard. /etc/device.hints is the correct place to adjust this flag. Yeah, I was looking at the kernel config on the wrong box. This flag did used to be in GENERIC, so it's worth double-checking the kernel config anyway just to be sure, but it should definitely be updated in /boot/device.hints if it's there. Sorry for the confusion, Doug -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible |Description | |-+---+-+| | | | | KSE M:N threading | | | | | support is | | | | | reaching | | | | | experimental yet | | | | Julian | usable status on | | Production-quality | In| Elischer, David | i386 for | | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N | | | | Eischen | threading should | | | | | be productionable | | | | | and usable on all | | | | | platforms by | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kernel bits are| | | | | implemented but| | KSE support for | In| | untested. Userland | | sparc64 | progress | Jake Burkholder | bits are not | | | | | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kernel and | | KSE support for | | Marcel | userland bits | | ia64| Complete. | Moolenaar | implemented but| | | | | unstable. Required | | | | | for 5.2-RELEASE. | |-+---+-+| | | | | Userland bits | | | | | implemented, | | KSE support for | In| Marcel | kernel bits not| | alpha | progress. | Moolenaar | implemented. | | | | | Required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Kris Kennaway | | | | | reports high | | | | | instability of | | | | | 5-CURRENT on ia64 | | | | | machines, such as | | ia64 stability | In| Marcel | the pluto* | | | Progress | Moolenaar | machines. These| | | | | problems need to | | | | | be fixed in order | | | | | to get a | | | | | successful package | | | | | build. | |-+---+-+| | | | | A reworking of the | | | | | sio driver is | | | | | needed to support | | | | | serial terminal| | | | Marcel | devices on sparc64 | | New serial UART | In| Moolenaar, | and ia64 | | framework | progress | Warner Losh | platforms, among | | | | | others. This is| | | |
Re: 5.2-RELEASE TODO
On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote: |-+---+-+| | | | | Productionable | | | | | support for the| | | | | AMD64 platform.| | | | | Currently, AMD64 | | | | | runs fully in | | | | | 32-bit emulation | | Tier-1 Support for | In| Peter Wemm, | mode, and boots to | | AMD64 Hammer| progress | David O'Brien | single-user in | | | | | 64-bit mode. We| | | | | expect full| | | | | production support | | | | | for the AMD64 | | | | | architecture in| | | | | 5.2-RELEASE. | |-+---+-+| PLEASE, PLEASE update this. Not implying that FreeBSD/amd64 doesn't make it multiuser and can build its own world would be sufficient. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
David O'Brien wrote: On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote: |-+---+-+| | | | | Productionable | | | | | support for the| | | | | AMD64 platform.| | | | | Currently, AMD64 | | | | | runs fully in | | | | | 32-bit emulation | | Tier-1 Support for | In| Peter Wemm, | mode, and boots to | | AMD64 Hammer| progress | David O'Brien | single-user in | | | | | 64-bit mode. We| | | | | expect full| | | | | production support | | | | | for the AMD64 | | | | | architecture in| | | | | 5.2-RELEASE. | |-+---+-+| PLEASE, PLEASE update this. Not implying that FreeBSD/amd64 doesn't make it multiuser and can build its own world would be sufficient. Sorry, I missed this when I did my scrub yesterday. I'll fix it now. Btw, does X work on it? Can I compile/install it without hassle? Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
David O'Brien wrote: On Mon, Sep 01, 2003 at 10:00:17AM -0400, Robert Watson wrote: |-+---+-+| | | | | Productionable | | | | | support for the| | | | | AMD64 platform.| | | | | Currently, AMD64 | | | | | runs fully in | | | | | 32-bit emulation | | Tier-1 Support for | In| Peter Wemm, | mode, and boots to | | AMD64 Hammer| progress | David O'Brien | single-user in | | | | | 64-bit mode. We| | | | | expect full| | | | | production support | | | | | for the AMD64 | | | | | architecture in| | | | | 5.2-RELEASE. | |-+---+-+| PLEASE, PLEASE update this. Not implying that FreeBSD/amd64 doesn't make it multiuser and can build its own world would be sufficient. Raising you through the normal channels does not seem to be working at the moment. Please go ahead and update this entry as you see fit. It's in www/en/releases/5.2R. Thanks! Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
Is anyone going to be fixing the sysinstall problem of not being able to re-slice a drive? For those who are not technical whizes this IS a big problem. We do still care about them right? Nicole |\ __ /| (`\ | o_o |__ ) ) // \\ - [EMAIL PROTECTED] - Powered by FreeBSD - -- Daemons will now be known as spiritual guides -Politically Correct UNIX Page ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
In message [EMAIL PROTECTED], Nicole writes: Is anyone going to be fixing the sysinstall problem of not being able to re-slice a drive? For those who are not technical whizes this IS a big problem. We do still care about them right? If you are talking about using sysinstall to modify drives in use, then the answer is probably no. For that job you want to use the correct tools: fdisk(8) and bsdlabel(8) (tacitly assuming i386 here). If you are talking about a problem during initial install of FreeBSD you need to provide more details about it. -- 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: 5.2-RELEASE TODO
So are you saying it Will work in single user mode perhaps? (drives in use) or are you saying gee we have this nice new version that if you need to modify any disk slice you did after an install your screwed into going back to caveman tools (which I admit I have NO IDEA how to use and I bet many others don't as well.) I have been using FreeBSD since 1997 and have never HAD to use anything else. Way to win over those Linux users. Nicole On 01-Sep-03 Unnamed Administration sources reported Poul-Henning Kamp said : In message [EMAIL PROTECTED], Nicole writes: Is anyone going to be fixing the sysinstall problem of not being able to re-slice a drive? For those who are not technical whizes this IS a big problem. We do still care about them right? If you are talking about using sysinstall to modify drives in use, then the answer is probably no. For that job you want to use the correct tools: fdisk(8) and bsdlabel(8) (tacitly assuming i386 here). If you are talking about a problem during initial install of FreeBSD you need to provide more details about it. -- 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. |\ __ /| (`\ | o_o |__ ) ) // \\ - [EMAIL PROTECTED] - Powered by FreeBSD - -- Daemons will now be known as spiritual guides -Politically Correct UNIX Page Witchcraft is in essence the worship of the powers of this world, beautiful and terrible, but all in a circle under the turning sky that is the One. -C.A. Burland, Echoes of Magic Connecting with energy is something humans have to be open to and talking about and expecting, otherwise the whole human race can go back to pretending that life is about power over others and exploiting the planet. If we go back to doing this, then we won't survive. -James Redfield, The Celestine Prophecy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On 01-Sep-03 Unnamed Administration sources reported Marc G. Fournier said : On Mon, 1 Sep 2003, Nicole wrote: So are you saying it Will work in single user mode perhaps? (drives in use) or are you saying gee we have this nice new version that if you need to modify any disk slice you did after an install your screwed into going back to caveman tools (which I admit I have NO IDEA how to use and I bet many others don't as well.) Ummm ... if you are talking about something that I just went through, why can't you just boot up off the floppies and do the reconfig from there? Well Server not even in same city as I am would be a start. I thought detrimeatures were more a MS thing. You didn't really NEED that feature did you.. there is a way around it, but you need our $$ training course then. You want to compete with Linux and Solaris who has all the nice friendly features and now its ok to eliminate them and make someones job require on-site visits and downbooting to floppies? Hellooo?? Nicole |\ __ /| (`\ | o_o |__ ) ) // \\ - [EMAIL PROTECTED] - Powered by FreeBSD - -- Daemons will now be known as spiritual guides -Politically Correct UNIX Page Witchcraft is in essence the worship of the powers of this world, beautiful and terrible, but all in a circle under the turning sky that is the One. -C.A. Burland, Echoes of Magic Connecting with energy is something humans have to be open to and talking about and expecting, otherwise the whole human race can go back to pretending that life is about power over others and exploiting the planet. If we go back to doing this, then we won't survive. -James Redfield, The Celestine Prophecy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO -2
BTW - I do thank you Marc for your advice. I know you were trying to assist. It just drives me crazy when important things get broken and people act like.. What the big deal. I don't need it why should you? I still have not solved the going to comsonsole mode if there is no keyboard detected crap, new feature. Yea great for those who could benifit from it.. But I have YET to have one person be able to show me how to STOP it from doing that. Why??? gosh why?? Becouse I don't want serial console and I don't have a keyboard on every server. So if I walk into the datacenter and try to access a server that has been rebooted.. I'm screwed! I have to ssh from some other server that has not been rebooted and if I NEED console.. then I have to reb oot the server. That detrimeature still has me pissed and the people I do work for scratching their head wanting to know why I install such a broken OS. They don't know and can't directly see the good things... managers and clients can only see it when you have to strugle to do something that should not be so obtuse. Nicole On 01-Sep-03 Unnamed Administration sources reported Marc G. Fournier said : On Mon, 1 Sep 2003, Nicole wrote: So are you saying it Will work in single user mode perhaps? (drives in use) or are you saying gee we have this nice new version that if you need to modify any disk slice you did after an install your screwed into going back to caveman tools (which I admit I have NO IDEA how to use and I bet many others don't as well.) Ummm ... if you are talking about something that I just went through, why can't you just boot up off the floppies and do the reconfig from there? |\ __ /| (`\ | o_o |__ ) ) // \\ - [EMAIL PROTECTED] - Powered by FreeBSD - -- Daemons will now be known as spiritual guides -Politically Correct UNIX Page Witchcraft is in essence the worship of the powers of this world, beautiful and terrible, but all in a circle under the turning sky that is the One. -C.A. Burland, Echoes of Magic Connecting with energy is something humans have to be open to and talking about and expecting, otherwise the whole human race can go back to pretending that life is about power over others and exploiting the planet. If we go back to doing this, then we won't survive. -James Redfield, The Celestine Prophecy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible |Description | |-+---+-+| | | | | KSE M:N threading | | | | | support is | | | | | reaching | | | | | experimental yet | | | | Julian | usable status on | | Production-quality | In| Elischer, David | i386 for | | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N | | | | Eischen | threading should | | | | | be productionable | | | | | and usable on all | | | | | platforms by | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Unsupported in | | KSE support for | In| Jake Burkholder | 5.1-RELEASE; | | sparc64 | progress | | required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Unsupported in | | KSE support for | Complete. | Marcel | 5.1-RELEASE; | | ia64| | Moolenaar | required for | | | | | 5.2-RELEASE. | |-+---+-+| | | | | Unsupported in | | | | | 5.1-RELEASE; | | KSE support for | In| | desired for| | amd64 | progress. | Peter Wemm | 5.2-RELEASE if | | | | | amd64 is to| | | | | achieve Tier 1 | | | | | support. | |-+---+-+| | | | | Unsupported in | | | | | 5.1-RELEASE; | | KSE support for | In| Marcel | desired for| | alpha | progress. | Moolenaar | 5.2-RELEASE if | | | | | alpha is to retain | | | | | Tier 1 support.| |-+---+-+| | | | | Kris Kennaway | | | | | reports high | | | | | instability of | | | | | 5-CURRENT on ia64 | | | | | machines, such as | | ia64 stability | In| Marcel | the pluto* | | | Progress | Moolenaar | machines. These| | | | | problems need to | | | | | be fixed in order | | | | | to get a | | | | | successful package | | | | | build. | |-+---+-+| | | | | ia64 serial| | | | | console support is | | | | | reported to not be | | | | | functional on HP | | | | Marcel
Re: 5.2-RELEASE TODO
On Fri, 29 Aug 2003, Robert Watson wrote: |-+---+-+| | | | | Unsupported in | | | | | 5.1-RELEASE; | | KSE support for | In| | desired for| | amd64 | progress. | Peter Wemm | 5.2-RELEASE if | | | | | amd64 is to| | | | | achieve Tier 1 | | | | | support. | |-+---+-+| I think this is complete; David and myself have done it with some guidance from Peter. Unless there's some issues we don't know about... -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.2-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | Kris Kennaway | | | | | reports high| | | | | instability of | | | | | 5-CURRENT on ia64 | | | In | Marcel | machines, such as | | ia64 stability | Progress | Moolenaar | the pluto* | | | | | machines. These | | | | | problems need to be | | | | | fixed in order to | | | | | get a successful| | | | | package build. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | | | | Warner Losh | sio driver to | | | | | improve platform| | | | | independence and| | | | | bus handling is | | | |
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.2-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | Kris Kennaway | | | | | reports high| | | | | instability of | | | | | 5-CURRENT on ia64 | | | In | Marcel | machines, such as | | ia64 stability | Progress | Moolenaar | the pluto* | | | | | machines. These | | | | | problems need to be | | | | | fixed in order to | | | | | get a successful| | | | | package build. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | | | | Warner Losh | sio driver to | | | | | improve platform| | | | | independence and| | | | | bus handling is | | | |
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.2-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | Kris Kennaway | | | | | reports high| | | | | instability of | | | | | 5-CURRENT on ia64 | | | In | Marcel | machines, such as | | ia64 stability | Progress | Moolenaar | the pluto* | | | | | machines. These | | | | | problems need to be | | | | | fixed in order to | | | | | get a successful| | | | | package build. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | | | | Warner Losh | sio driver to | | | | | improve platform| | | | | independence and| | | | | bus handling is | | | |
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.2-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | Kris Kennaway | | | | | reports high| | | | | instability of | | | | | 5-CURRENT on ia64 | | | In | Marcel | machines, such as | | ia64 stability | Progress | Moolenaar | the pluto* | | | | | machines. These | | | | | problems need to be | | | | | fixed in order to | | | | | get a successful| | | | | package build. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | | | | Warner Losh | sio driver to | | | | | improve platform| | | | | independence and| | | | | bus handling is | | | |
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.2-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | Kris Kennaway | | | | | reports high| | | | | instability of | | | | | 5-CURRENT on ia64 | | | In | Marcel | machines, such as | | ia64 stability | Progress | Moolenaar | the pluto* | | | | | machines. These | | | | | problems need to be | | | | | fixed in order to | | | | | get a successful| | | | | package build. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | | | | Warner Losh | sio driver to | | | | | improve platform| | | | | independence and| | | | | bus handling is | | | |
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.2-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | Kris Kennaway | | | | | reports high| | | | | instability of | | | | | 5-CURRENT on ia64 | | | In | Marcel | machines, such as | | ia64 stability | Progress | Moolenaar | the pluto* | | | | | machines. These | | | | | problems need to be | | | | | fixed in order to | | | | | get a successful| | | | | package build. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | | | | Warner Losh | sio driver to | | | | | improve platform| | | | | independence and| |
Re: 5.2-RELEASE TODO
On Sun, Jun 29, 2003 at 10:00:15AM -0400, Robert Watson wrote: |+---++---| | || || Kris Kennaway | | || || reports | | || || deadlocks | | || || involving the | | || || use of nullfs | | || || in the bento | | || || environment: | | || || buildworld| | || || -j4 with src | | || || and obj | | || || mounted via | | || || nullfs; the | | | nullfs | --| -- | gcc processes | | | deadlocks | || eventually| | || || deadlocked in | | || || the ufs | | || || state. DDB| | || || traceback | | || || showed two| | || || different | | || || codepaths.| | || || I've just | | || || repeated | | || || this, so the | | || || bug still | | || || exists. | | |+---++---| | This has already been fixed. Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Sun, 29 Jun 2003, Robert Watson wrote: ++ |Issue| Status | Responsible | Description | |-+--+-+-| ^^^ I don't suppose it would be possible to delete a couple of those leading spaces on each line? Although it fits into an 80-column display in vim/cat/whatever, mutt ends up wrapping it, and making it very ugly, but removing a couple of the spaces would make it fit fine. -- David Taylor [EMAIL PROTECTED] The future just ain't what it used to be ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Sun, 29 Jun 2003, David Taylor wrote: On Sun, 29 Jun 2003, Robert Watson wrote: ++ |Issue| Status | Responsible | Description | |-+--+-+-| ^^^ I don't suppose it would be possible to delete a couple of those leading spaces on each line? Although it fits into an 80-column display in vim/cat/whatever, mutt ends up wrapping it, and making it very ugly, but removing a couple of the spaces would make it fit fine. The way these are currently produced is to check out the web tree, build the HTML for the todo lists/etc, render them with links, dump to text, trim the unnecessary headers and footers, and spit them into a form e-mail. I can trim the leading spaces easily enough using sed; most other properties of the rendering are up to links and therefore hard to adjust. 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: 5.2-RELEASE TODO
On Sun, 29 Jun 2003, David Taylor wrote: I don't suppose it would be possible to delete a couple of those leading spaces on each line? Bah, ignore me, after deciding it was mutt's fault for wrapping it when it shouldn't be, I found the 'wrapmargin' setting in my muttrc file... Reducing that a little fixed the problem. Sorry about that, -- David Taylor [EMAIL PROTECTED] The future just ain't what it used to be ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
David Taylor wrote this message on Sun, Jun 29, 2003 at 17:04 +0100: Although it fits into an 80-column display in vim/cat/whatever, mutt ends up wrapping it, and making it very ugly, but removing a couple of the spaces would make it fit fine. Reconfigure your mutt. It works fine over here on Mutt 1.4.1i (2003-03-19). Did you happen to set the wrapmargin variable? -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Mon, 30 Jun 2003, Tim Robbins wrote: This has already been fixed. Great, I'll update the list, thanks! 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]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.2-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | Kris Kennaway | | | | | reports high| | | | | instability of | | | | | 5-CURRENT on ia64 | | | In | Marcel | machines, such as | | ia64 stability | Progress | Moolenaar | the pluto* | | | | | machines. These | | | | | problems need to be | | | | | fixed in order to | | | | | get a successful| | | | | package build. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | | | | Warner Losh | sio driver to | | | | | improve platform| | | | | independence and| |
Re: 5.2-RELEASE TODO
Actually, I would think it a desirable feature mac support that won't panic within 24 hours. :-) I've given up on mac again. Can't have it if it panics on every daily. :-( What's the plans for dealing with that? Robert Watson wrote: This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.2-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | Kris Kennaway | | | | | reports high| | | | | instability of | | | | | 5-CURRENT on ia64 | | | In | Marcel | machines, such as | | ia64 stability | Progress | Moolenaar | the pluto* | | | | | machines. These | | | | | problems need to be | | | | | fixed in order to | | | | | get a successful| | | | | package build. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | |
Re: 5.2-RELEASE TODO
On Mon, 2 Jun 2003, Daniel C. Sobral wrote: Actually, I would think it a desirable feature mac support that won't panic within 24 hours. :-) I've given up on mac again. Can't have it if it panics on every daily. :-( What's the plans for dealing with that? Right now I'm aware of one panic that shows up only if labeled MAC policies are linked to the kernel, rather than loaded as modules during the boot process. Currently, it manifests when multiple applications open sockets listening on the same UDP port, and may relate to multiple delivery of mbufs; this panic does not occur when using the modules, however. I'm still tracking down the details. We corrected the compat/linux/dev/null panic (or at least, eliminated it) -- this turned out to be a bug in UFS2 that can be triggered without the use of MAC. Are there are additional panics you're experiencing? 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: 5.2-RELEASE TODO
On Sun, 1 Jun 2003 10:00:14 -0400 (EDT) [EMAIL PROTECTED](Robert Watson) said: | | | | The FreeBSD KAME| | | | | IPv6 code is now| | | | | substantially dated | | | | | with respect to the | | KAME| | | KAME vendor source. | | Synchronization | -- | -- | The FreeBSD Project | | | | | needs to take | | | | | initiative in | | | | | driving the merge | | | | | of new bug fixes, | | | | | features, et al.| I discussed this issued within KAME. Here's our rough plan about this synchronization. If you have some opinion, please let me know. When I've finished each merge, I'll ask you how to proceed. - sync per feature; don't do a complete sync with the KAME-snap: Since some of the KAME-specific features are still under standardization or immature, it's dangerous to sync without much consideration. - items to be merged Here's the candidate items to be merged. 5.2-RELEASE - IPv6 Advanced API (RFC3542 = written as 'RFC2292bis' in source code) Binary compatibility to RFC2292 is provided. - Source Address Selection (RFC3484) It involves too many unessential changes. (e.g. NDP data structure change, use struct sockaddr_in6 instead of struct in6_addr). So if time does not permit, I'll shift it to the future release. 5.x-RELEASE - IGMPv3 (RFC3478 and draft-ietf-magma-msf-api-04.txt) seems almost okay in terms of standardization, but has less priority. So if time permits, I'll shift it to 5.2-RELEASE. - Mobile IPv6 Corresponding Node (draft-ietf-mobileip-ipv6-22.txt) waiting for becoming an RFC - items not to be merged The following items are not merged for the time being, because of their immaturity, wating for standardization, etc. MLDv2 mDNS Scoped routing VRRPv6 Mobile-IPv6 Home-Agent and Mobile-Node Router Selection ISATAP DNS server discovery DHCPv6 SCTP ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-RELEASE TODO
On Tue, Jun 03, 2003 at 05:32:35PM +0900, SUZUKI Shinsuke wrote: I discussed this issued within KAME. Here's our rough plan about this synchronization. If you have some opinion, please let me know. When I've finished each merge, I'll ask you how to proceed. - sync per feature; don't do a complete sync with the KAME-snap: Since some of the KAME-specific features are still under standardization or immature, it's dangerous to sync without much consideration. For what its worth, I have some of this stuff already merged in my local cvs tree. Drop me note if I can be of any help. I have the IGMPv3 code in my repo merged. Cheers. -- Hiten [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.2-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | Kris Kennaway | | | | | reports high| | | | | instability of | | | | | 5-CURRENT on ia64 | | | In | Marcel | machines, such as | | ia64 stability | Progress | Moolenaar | the pluto* | | | | | machines. These | | | | | problems need to be | | | | | fixed in order to | | | | | get a successful| | | | | package build. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | | | | Warner Losh | sio driver to | | | | | improve platform| | | | | independence and| |
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.1-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | | | | Warner Losh | sio driver to | | | | | improve platform| | | | | independence and| | | | | bus handling is | | | | | likely needed. | |-+--+-+-| | | | | FAST_IPSEC | | | | | currently cannot be | | | | | used directly with | | | | | the KAME IPv6 | | | | | implementation, | | | | | requiring an| | | | | additional level of | | | | | IP tunnel | | | | | indirection to | |
Re: 5.2-RELEASE TODO
On Thu, May 29, 2003 at 10:00:13AM -0400, Robert Watson wrote: |-+--+-+-| | | | | Almost all process | | | | | debugging tools | | | | | have been updated | | | | | to use non-procfs | | | | | kernel primitives, | | | | | with the exception | | | | | of truss(1). As | | | | | procfs is | | | | | considered | | | | | deprecated due to | | truss support for | In | | its inherent| | ptrace | progress | Robert Drehmel | security risks, it | | | | | is highly desirable | | | | | to update truss to | | | | | operate in a| | | | | post-procfs world. | | | | | Dag-Erling Smorgrav | | | | | had prototype | | | | | patches;| | | | | Robert Drehmel is | | | | | developing and | | | | | testing patches | | | | | now.| |-+--+-+-| gcore also uses procfs. Converting it to use something else (libkvm or perhaps ptrace) won't be straightforward. Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
