Re: FreeBSD has serious problems with focus, longevity, and lifecycle
Robert Watson wrote: On Mon, 16 Jan 2012, Julian Elischer wrote: On 1/16/12 3:32 PM, William Bentley wrote: I also echo John's sentiments here. Very excellent points made here. Thank you for voicing your opinion. I was beginning to think I was the only one who felt this way. [...] We seem to have lost our way around the release of FreeBSD 7. I am all in favor of new features but not at the risk of stability and proper life cycle management. Are me and John the only people that feel this way or are we among the minority? It pretty much boils down to one thing.. man power.. I disagree. Resourcing is an issue, but it is not *the* issue. The real issue here is a failure by the release engineering team (which includes me) to concurrently perform major and minor releases. Given that minor releases run like clockwork in most cases, this is disappointing. In the past, there have been a lot of good technical and structural obstacles to trying to do clockwork releases for both major and minor releases: - Tight synchronisation of the ports and base release schedule means that the base release schedule limits ports productivity. - Long freezes forced on us by poor revision control support for branching. None of these really apply any longer -- and in as much as they do, they should be addressed. In particular, I think there's a growing feeling that ports should be conducting its own releases out of lockstep with the base tree, producing package sets as a primary product at regular intervals regardless of the base release schedule. Likewise, long freezes enforced by expensive branching operation in CVS no longer apply due to use of Subversion -- it's not perfect, but it's workable. There's no way to satisfy everyone with any particular maintenance schedule and release cycle. However, it seems clear that the current model with minor releases spaced at a year is satisfying no one. It's easy to point at a developer-user divide, but I think that misses the point: most developers are users. A big gap between development branch and shipped features hurts the commercial users of FreeBSD that pay for so much of its development, since it forces them to support diverging local development and shipping products -- ISPs, etc. There is no incentive for year-long gaps in minor releases. My view is therefore that we have a social -- which is to say structural -- problem. Regardless of .0 releases, we should be forcing out minor releases, which are morally similar to service packs in the vocabulary of other vendors: device driver improvements, new CPU support, steady of conservative feature development, etc, required to keep older major releases viable on contemporary hardware and with contemporary applications. One known problem is using a single head release engineer in steering all releases. I think this is a mistake, as it makes the whole project's release schedule subject to individual unavailability, burnout, etc, as well as increasing the risks associated with low bus factor. I'd like to see us move to a model where new release engineers are mentored in from the developer community for point releases, ensuring that we increase our expertise, share knowledge about release engineering in the broader community, and get new eyes on the process which can lead more readily to process improvements. The role of the head release engineer shouldn't be hands-on prodution of every release, but rather, steering of the overall team. I'd like to see this begin with 8.3, drawing a per-release lead from the developer community, and continue with a fixed schedule release of 8.4. Yes, more staffing is needed, but first, what is needed is an improvement in model. It looks like Intel's development model. They have two teams. One works on new processor, while the second do upgrade of the previous one. On next turn the last one start the new processor and the first one does. I think it is great model. [...] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Hardware supported by ng_frame_relay?
Jan Mikkelsen wrote: On 15/01/2012, at 6:00 PM, Roman Kurakin wrote: Hi, Jan Mikkelsen wrote: Hi, I'm looking to upgrade a system running frame relay over a Sangoma A101 card and WANPIPE. Sangoma do not support FreeBSD anymore, so I'm looking for alternatives. What hardware does ng_frame_relay support now that ar(4) and sr(4) are not in FreeBSD 9? Specifically, will ng_frame_relay work with a Digium TE121 and ports/dahdi-kmod? Any suggestions welcome, G.703, X.21 or V.35 interfaces OK. Check also www. cronyx. ru for ce(4) and cp(4). As far as I know, an old digium adapters were using software framer for HDLC, but I don'k know the current state. If they didn't provide hardware framer now, I suggest to check for any other adapter. Thanks. Just had a look at their site; they support up to 6.x, there is a red note saying 7.x is not supported. I suspect that would also apply to 8.x and 9.x ... I know, I quit the company and support was stopped at that point. But code in the base tree, and should work. For now going with a standalone router. Might have a look at the Digium card more closely if I have a different application for it ... Then take a look at www. nsg. ru they have nice linux based boxes. Though, I didn't play with them by my self. Best regards, rik rik Regards, Jan. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: * Re: FreeBSD has serious problems with focus, longevity, and lifecycle
Devin Teske wrote: [...] We could adopt a cycle similar to the Linux Kernel... Odd numbered releases are experimental while even numbered releases are stable I do not know the current state things in Linux kernel, but as far as I know 2.6 branch was not stable. It was branch with a lot of experimental code and with a lot of API change. rik (ducks for flying fruit) _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Hardware supported by ng_frame_relay?
Hi, Jan Mikkelsen wrote: Hi, I'm looking to upgrade a system running frame relay over a Sangoma A101 card and WANPIPE. Sangoma do not support FreeBSD anymore, so I'm looking for alternatives. What hardware does ng_frame_relay support now that ar(4) and sr(4) are not in FreeBSD 9? Specifically, will ng_frame_relay work with a Digium TE121 and ports/dahdi-kmod? Any suggestions welcome, G.703, X.21 or V.35 interfaces OK. Check also www. cronyx. ru for ce(4) and cp(4). As far as I know, an old digium adapters were using software framer for HDLC, but I don'k know the current state. If they didn't provide hardware framer now, I suggest to check for any other adapter. Best regards, rik Thanks, Jan Mikkelsen___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages
Have you also posted this to [EMAIL PROTECTED] rik Eygene Ryabinkin wrote: Good day. A while ago I had created the new utility that serves as VuXML filter for the installed packages: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/126853 My primary intention was to speed up the process of auditing the vulnerable ports: I needed to run portaudit checks with Nagios and to avoid large timeouts. The new utility is called pkg_audit and it serves as a simple text filter: on input it takes the full VuXML feed and on output it puts VuXML entries that matches ports that are installed in the system with port version specification substituted with the actual port versions. No harm is done to the actual poartudit -- if pkg_audit is missing, old code path is activated. If someone is interested and will be able to test -- I am all ears. Thanks! ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Patch RFC: Promise SATA300 TX4 hardware bug workaround.
By the way, is there any chance to get RAID5 working with this controller? rik Alexander Sabourenkov wrote: Arno J. Klaassen wrote: Rather than the marginal HW part, it seems, for me, closely related to MB/BIOS (as well (Alexander apperently has about the same setup as I have for this test)): [...] I vaguely remember from another PR that the Promise card does something with PCI-bursting which fbsd does not detect and/or handle correctly (and beyond my simple skills as dumb tester, but maybe the linux-sources contain a clue about that as well). Analysis of chip initialization in vendor-supplied, Linux and FreeBSD drivers shows that FreeBSD's one: - does not enable something called 'BMR_BURST', - performs hotplug init in one write (instead of two read-modify-writes ), - does an extra write (offset 0x54) which is not done in other drivers. Analysis text: http://lxnt.info/tx4/chipinit.text Patch with ported chipinit (dangerous to use with anything from Promise other than sata300 tx4 !!): http://lxnt.info/tx4/freebsd/chipinit.patch (cumulative) http://lxnt.info/tx4/freebsd/ata-chipset.c+chipinit (patched source) Note two things: 1. I have not compiled or tested this patch. Please do. 2. I may have missed this bug because I'm frequently rebooting between Linux and FreeBSD, and what Linux driver initialized may have lasted the reboots. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A handy utility (at least for me)
Rick C. Petty: On Sat, Aug 26, 2006 at 07:19:06PM -0300, Mario Lobo wrote: My /usr/ports directory was occuping 24 gigs, of which 20 was just from the 'work' directories ! Removing them one by one was a pain so I wrote this little utility to wipe them off. I find that the following command works just fine for me: find /usr/ports -type d -name work -prune -print -delete A bit rude, but also works cd /usr/ports make clean rik =) -- Rick C. Petty ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A handy utility (at least for me)
albi: On Sun, 27 Aug 2006 03:12:52 +0400 Roman Kurakin [EMAIL PROTECTED] wrote: Rick C. Petty: On Sat, Aug 26, 2006 at 07:19:06PM -0300, Mario Lobo wrote: My /usr/ports directory was occuping 24 gigs, of which 20 was just from the 'work' directories ! Removing them one by one was a pain so I wrote this little utility to wipe them off. I find that the following command works just fine for me: find /usr/ports -type d -name work -prune -print -delete A bit rude, but also works cd /usr/ports make clean guys... please use the official portsclean ! :) In most of cases, you not need it. Portupgrade will clean after itself ;-) rik included in the sysutils/portupgrade portsclean -h portsclean 2.0.1 (2006/06/13) usage: portsclean [-hCDDiLnPPQQq] -h, --help Show this message -C, --workcleanClean up working directories --- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to change kernel version tag?
Yuan, Jue wrote: Hi all. Could I change the kernel version tag manually? say, I have a kernel which is 7.0-CUREENT, but for some reasons I wanna it be something like 6.1-RELEASE, while the kernel itself does't change from 7.0-CURRENT to 6.1-RELEASE. All I want is the change of tag. For example, if this works, then when I type uname -a in console, I would get 6.1-RELEASE ... instead of 7.0-CURRENT You jast want to change the uname output, or some software checks kernel version? rik I guess some config files in src/sys/ could take care of this. But I cannot find it out. Anybody knows how to get this job done? Any ideas are really appreciated. :-) BTW: I am not in this list. So if you reply, please CC a copy to me. Thanks. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: global data via module howto
Hi,
I've done it. Thanks for the road map.
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Roman Kurakin [EMAIL PROTECTED] writes:
: M. Warner Losh wrote:
: In message: [EMAIL PROTECTED]
: Roman Kurakin [EMAIL PROTECTED] writes:
: : I have the following problem:
: : module A
: : int x;
: :
: : module B
: : extern int x;
: :
: : Module A is loaded, module B can't be loaded cause of unknow 'x'.
: : What should I do to make x global?
:
: Better to make module B depend on module A. Making it global is
: generally a bad idea.
:
: in module A:
: MODULE_VERSION(A, 1);
:
: In module B:
: MODULE_DEPEND(B, A, 1, 1, 1);
:
: Module dependence is not the goal.
Right. That's how symbols are visible to other modules.
Yes, it works. And it is still needed for class/subclass scheme.
:
: : PS. I am working on porting irda support for USB devices from NetBSD.
: : The current model consists of two layers hw and sw. hw is the usb device
: : driver. sw is some software layer the same for all device and it is a
: : child on top of hw 'bus'. To make this working I need to add
: : DRIVER_MODULE for each 'bus'. To make sw independent from the
: : bus I need to export _driver and _class structures and put DRIVER_MODULE
: : in 'bus' code instead of 'child'.
:
: Are you sure that you need to do this? I'm pretty sure that you can
: create a base class irdabus and then derive all the hw modules that
: implement irdabus from than and all the children will automatically
: probe. No need to export the driver/class structures.
This was a bit wrong. You still need to export kobj_class (eq driver_t
structure,
DECLARE_CLASS).
:
: I have a bit reversed case. In common case we have a driver for bus
: with many
: consumers. And we have children that declares itself via DRIVER_MODULE.
: If child could work on several buses it declares itself several times
: one for each
: bus. In my case I have several drivers that could be treated as bus
: driver for the
: same child:
:
: ---USB
: || |
: ustir uirda smth_else
: \| /
: -irframe
:
: Imagine, if the network interface was implemented as a child of every
: network
: adapter. This is the same. In common case I'll put DRIVER_MODULE in a child
: for each bus and recompile after adding a new one. In this case I do no
: want to
: recompile the child for every new bus since child do not depend on
: such bus
: - it is the same for all. So we may call this a pseudo-device with
: unknown list
: of buses. I know, I could implement this other way, but I just want to
: play with
: newbus a bit and the original NetBSD driver was implemented this way.
I think I must have not been clear before. I thought gave a solution
to this that doesn't require a new DRIVER_MODULE for each new device.
Let me try again.
I'd hoped to say make ustir, uirda and smth_else all subclasses of a
irbridge class, just like we do for pci and cardbus today. Then
irframe would attach to irbridge and you'd only need to list
DRIVER_MODULE lines once. This isn't a reversed case at all. It is
actually quite common, but has been 'papered over' until now via
multiple DRIVER_MODULE lines, except in the case of pci/cardbus[*].
I can provide more details on actually doing this. Right now I'm
doing something similar for all the iic bridges that we have in the
kernel. The number of devices with iicbus children is way too large
and we can eliminate that issue via the technique. I'd be happy to
flesh it out a bit, or provide you with sample code if you need that.
For curious:
==irda_bus==
static device_probe_t irda_bus_probe;
static device_attach_t irda_bus_attach;
static device_detach_t irda_bus_detach;
static device_method_t irda_bus_methods[] = {
/* stub functions */
DEVMETHOD(device_probe, irda_bus_probe), /* aka match */
DEVMETHOD(device_attach, irda_bus_attach),
DEVMETHOD(device_detach, irda_bus_detach),
{0,0}
};
struct irda_bus_softc {
};
MODULE_VERSION(irda_bus, 1);
DEFINE_CLASS_0(irda_bus, irda_bus_driver, irda_bus_methods,
sizeof(struct irda_bus_softc));
===
ustir
Static device_probe_t ustir_match;
Static device_attach_t ustir_attach;
Static device_detach_t ustir_detach;
Static devclass_t ustir_devclass;
Static device_method_t ustir_methods[] = {
DEVMETHOD(device_probe, ustir_match),
DEVMETHOD(device_attach, ustir_attach),
DEVMETHOD(device_detach, ustir_detach),
{0,0}
};
MODULE_DEPEND(ustir, usb, 1, 1, 1);
MODULE_DEPEND(ustir, irda_bus, 1, 1, 1);
DECLARE_CLASS(irda_bus_driver);
DEFINE_CLASS_1(irda_bus, ustir_driver, ustir_methods,
sizeof(struct ustir_softc), irda_bus_driver);
DRIVER_MODULE(ustir, uhub, ustir_driver, ustir_devclass
Re: Latest patch for PPP
Frederic Praca:
Hello,
in the latest security advisory for PPP, the patch deals with conditions
in a for loop. The correct line is :
for (rlen=0; len = 2 p[1] = 2 len = p[1]; len-=p[1], p+=p[1]) {
Couldn't the condition be simpler like :
for (rlen=0; p[1] = 2 len = p[1]; len-=p[1], p+=p[1]){
If len2 you just can't access (theoretically) p[1] cause in best case
you have only p[0] (len=1)
or do not have even p[0] (len=0). So from general point of view this is
correct code.
rik
Or is there a hack I didn't understand ?
In this case, if p[1] is greater or equal than 2, if we ensure that len
= p[1], we don't have to test that it's greater or equal than 2, isn't
it ?
Fred
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: global data via module howto
M. Warner Losh wrote: In message: [EMAIL PROTECTED] Roman Kurakin [EMAIL PROTECTED] writes: : I have the following problem: : module A : int x; : : module B : extern int x; : : Module A is loaded, module B can't be loaded cause of unknow 'x'. : What should I do to make x global? Better to make module B depend on module A. Making it global is generally a bad idea. in module A: MODULE_VERSION(A, 1); In module B: MODULE_DEPEND(B, A, 1, 1, 1); Module dependence is not the goal. Warner : PS. I am working on porting irda support for USB devices from NetBSD. : The current model consists of two layers hw and sw. hw is the usb device : driver. sw is some software layer the same for all device and it is a : child on top of hw 'bus'. To make this working I need to add : DRIVER_MODULE for each 'bus'. To make sw independent from the : bus I need to export _driver and _class structures and put DRIVER_MODULE : in 'bus' code instead of 'child'. Are you sure that you need to do this? I'm pretty sure that you can create a base class irdabus and then derive all the hw modules that implement irdabus from than and all the children will automatically probe. No need to export the driver/class structures. I have a bit reversed case. In common case we have a driver for bus with many consumers. And we have children that declares itself via DRIVER_MODULE. If child could work on several buses it declares itself several times one for each bus. In my case I have several drivers that could be treated as bus driver for the same child: ---USB || | ustir uirda smth_else \| / -irframe Imagine, if the network interface was implemented as a child of every network adapter. This is the same. In common case I'll put DRIVER_MODULE in a child for each bus and recompile after adding a new one. In this case I do no want to recompile the child for every new bus since child do not depend on such bus - it is the same for all. So we may call this a pseudo-device with unknown list of buses. I know, I could implement this other way, but I just want to play with newbus a bit and the original NetBSD driver was implemented this way. rik Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: global data via module howto
M. Warner Losh: In message: [EMAIL PROTECTED] Roman Kurakin [EMAIL PROTECTED] writes: : M. Warner Losh wrote: : In message: 44E87CChttp://comp.krovatka.ru/[EMAIL PROTECTED] : Roman Kurakin [EMAIL PROTECTED] writes: : : I have the following problem: : : module A : : int x; : : : : module B : : extern int x; : : : : Module A is loaded, module B can't be loaded cause of unknow 'x'. : : What should I do to make x global? : : Better to make module B depend on module A. Making it global is : generally a bad idea. : : in module A: : MODULE_VERSION(A, 1); : : In module B: : MODULE_DEPEND(B, A, 1, 1, 1); : : Module dependence is not the goal. Right. That's how symbols are visible to other modules. : : : PS. I am working on porting irda support for USB devices from NetBSD. : : The current model consists of two layers hw and sw. hw is the usb device : : driver. sw is some software layer the same for all device and it is a : : child on top of hw 'bus'. To make this working I need to add : : DRIVER_MODULE for each 'bus'. To make sw independent from the : : bus I need to export _driver and _class structures and put DRIVER_MODULE : : in 'bus' code instead of 'child'. : : Are you sure that you need to do this? I'm pretty sure that you can : create a base class irdabus and then derive all the hw modules that : implement irdabus from than and all the children will automatically : probe. No need to export the driver/class structures. : : I have a bit reversed case. In common case we have a driver for bus : with many : consumers. And we have children that declares itself via DRIVER_MODULE. : If child could work on several buses it declares itself several times : one for each : bus. In my case I have several drivers that could be treated as bus : driver for the : same child: : : ---USB : || | : ustir uirda smth_else : \| / : -irframe : : Imagine, if the network interface was implemented as a child of every : network : adapter. This is the same. In common case I'll put DRIVER_MODULE in a child : for each bus and recompile after adding a new one. In this case I do no : want to : recompile the child for every new bus since child do not depend on : such bus : - it is the same for all. So we may call this a pseudo-device with : unknown list : of buses. I know, I could implement this other way, but I just want to : play with : newbus a bit and the original NetBSD driver was implemented this way. I think I must have not been clear before. I thought gave a solution to this that doesn't require a new DRIVER_MODULE for each new device. Let me try again. I'd hoped to say make ustir, uirda and smth_else all subclasses of a irbridge class, just like we do for pci and cardbus today. Then irframe would attach to irbridge and you'd only need to list DRIVER_MODULE lines once. This isn't a reversed case at all. It is actually quite common, but has been 'papered over' until now via multiple DRIVER_MODULE lines, except in the case of pci/cardbus[*]. I can provide more details on actually doing this. Right now I'm doing something similar for all the iic bridges that we have in the kernel. The number of devices with iicbus children is way too large and we can eliminate that issue via the technique. I'd be happy to flesh it out a bit, or provide you with sample code if you need that. If you have a sample, it should help me a lot. Thanks. Warner [*] There's still pci and cardbus DRIVER_MODULE lines in many drivers, but they are almost not needed. There's a newbus bug that I've not had the time to track down that prevents kldload from working competely correctly in some cases (like when loading the cardbus module). Once I get that fixed... If I hit this problem for my case, I'll be glad to help to fix it. rik ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
global date via module howto
Hi, I have the following problem: module A int x; module B extern int x; Module A is loaded, module B can't be loaded cause of unknow 'x'. What should I do to make x global? PS. I am working on porting irda support for USB devices from NetBSD. The current model consists of two layers hw and sw. hw is the usb device driver. sw is some software layer the same for all device and it is a child on top of hw 'bus'. To make this working I need to add DRIVER_MODULE for each 'bus'. To make sw independent from the bus I need to export _driver and _class structures and put DRIVER_MODULE in 'bus' code instead of 'child'. rik ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nanosecond delay in kernel module
Hi, Julian Elischer: [EMAIL PROTECTED] wrote: Hi, what is the official way to delay in a kernel module for about 10 nanoseconds (1/1,000,000,000th second). I found DELAY(9), but it uses microseconds (1/1,000,000th second). at this time there is none. maybe you can write one? You probably need to find some machine instructions with a known delay Probably PCI read/write ... rik Any help would be appeciated Maik ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: provide ttys from device driver
Niki Denev: Hi, The cardbus hsdpa/umts adapter which driver i'm trying to port from linux to\ freebsd should look as four port serial device. The part of the driver that speaks with the hardware is more or less ready and working, i have setup a interrupt handler and can talk to the card and catch and service interrupts. Now the tricky part is to connect this to the tty layer... So, what is the best place to look for examples to provide ttys from a device driver? (apart from reading the code of existing serial drivers, which i'm doing right now :) ) Check smth like ng_tty. Thanks! --niki ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Adding remove file option to BSD tar?
Steven Hartland: - Original Message - From: Eric Anderson [EMAIL PROTECTED] Some people on this list might argue that you could do this another way, something like piping a tar extract to another tar create that excludes that file. Sure that can be done but its a PITA and majorly slow so a none option IMO. In case one concerned by the space problem there is now other way to do it failsafe. In case it is gziped it need to be extracted first in any case. rik Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: absolute vs. relative offsets in disklabel
John Baldwin: On Sunday 06 August 2006 10:59, Dmitry Marakasov wrote: * Dag-Erling Sm?rgrav ([EMAIL PROTECTED]) wrote: Recent `disklabel differences FreeBSD, DragonFly' thread gave me a thought - why do we have absolute offsets in disklabel? We don't, AFAIK. Since the transition to GEOM, the offsets are relative to the start of the containing provider. It has nothing to do with GEOM, it's ondisk format of disklabel. I've confirmed, there are global offsets. Actually, the GEOM provider goes though some gymnastics to portray the offsets as relative to userland, but ondisk they are still stored as absolute to preserve compatiblity. You mean that read mbroffset to geom could return a relative value? rik ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: bsdlabel: potential bug and/or question about it]
Forwarded to hackers since no reply on geom@ Hi, I am trying to understand filesystem structure to extract data from half-broken hard drive and I've started to read sources of bsdlabel (if someone know any articles about bsdlabel and/or ufs2 structure please let me know). My question is what for mbroffset and what is it? I have only some surmises about it, but it looks that this code could lead to filesystem corruption. But I hope I am wrong :-) http://cvsup.pt.freebsd.org/cgi-bin/cvsweb/cvsweb.cgi/src/sbin/bsdlabel/bsdlabel.c.diff?r1=1.89r2=1.90 My train of thought was that in case we have the mbroffset not equal to offset of c (raw) partition we wouldn't substruct mbroffset from all offsets. Lets also assume that this case we meet while we started to edit such slice. We've finished editing and started to write results. In case of write we would add mbroffset unconditionally and thus we get wrong offsets and corrupted partition table. Best regards, rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LOR #55 fix proposal (kern_descrip.c patch)
Commited. Roman Kurakin: Hi, It seems that the LOR #55 (http://sources.zabbadoz.net/freebsd/lor.html#055) could be fixed by following patch. I need testers and reviewers of it since I want to commit it. I do not see a reason why not to extend action of FILEDESC_LOCK. (http://www.cronyx.ru/~rik/freebsd/lor055/lor55.pch) Index: kern_descrip.c === RCS file: /home/ncvs/src/sys/kern/kern_descrip.c,v retrieving revision 1.280 diff -u -r1.280 kern_descrip.c --- kern_descrip.c 26 Aug 2005 11:16:39 - 1.280 +++ kern_descrip.c 27 Sep 2005 17:31:57 - @@ -2275,7 +2275,6 @@ fdused(fdp, indx); if (fp != NULL) FILE_LOCK(fp); - FILEDESC_UNLOCK(fdp); /* * We now own the reference to fp that the ofiles[] array @@ -2283,6 +2282,9 @@ */ if (fp != NULL) fdrop_locked(fp, td); + + FILEDESC_UNLOCK(fdp); + return (0); default: Best regards, rik ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
LOR #55 fix proposal (kern_descrip.c patch)
Hi, It seems that the LOR #55 (http://sources.zabbadoz.net/freebsd/lor.html#055) could be fixed by following patch. I need testers and reviewers of it since I want to commit it. I do not see a reason why not to extend action of FILEDESC_LOCK. (http://www.cronyx.ru/~rik/freebsd/lor055/lor55.pch) Index: kern_descrip.c === RCS file: /home/ncvs/src/sys/kern/kern_descrip.c,v retrieving revision 1.280 diff -u -r1.280 kern_descrip.c --- kern_descrip.c 26 Aug 2005 11:16:39 - 1.280 +++ kern_descrip.c 27 Sep 2005 17:31:57 - @@ -2275,7 +2275,6 @@ fdused(fdp, indx); if (fp != NULL) FILE_LOCK(fp); - FILEDESC_UNLOCK(fdp); /* * We now own the reference to fp that the ofiles[] array @@ -2283,6 +2282,9 @@ */ if (fp != NULL) fdrop_locked(fp, td); + + FILEDESC_UNLOCK(fdp); + return (0); default: Best regards, rik ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Remove Heimdal Kerberos from my FreeBSD
Hi, Vladimir Terziev wrote: Yes, i deleted it along with all libs related to it. This caused telnet/ssh/etc to stop working. So i rebuilt the world with NO_KERBEROS=yes and now all is like a charm -- no Heimdal Kerberos and no software depending on it. I think making the Heimdal Kerberos part of the base FreeBSD OS is bad idea, but linking base software (like telnet, ssh), which is part of the base FreeBSD OS, against it, is very very bad idea. Why? Yes, all current OSs have a lot of useless things from some one point of view. For example, at work I do not need X while driver development, but at home I need it. At home I may not need almost all development tools. This is normal. If I want to setup a system fast and without additional efforts I'll setup a typical options. And I'll start use it as fast as it would be up. Most peoples do the same. It is better to have all thing in generic system that suits the majority. If you want to setup a custom system, you need to do it manually. rik Vladimir On Sun, 17 Jul 2005 22:02:04 +0930 Daniel O'Connor [EMAIL PROTECTED] wrote: On Sunday 17 July 2005 02:26, Dominic Marks wrote: In /etc/make.conf put NO_KERBEROS=yes Then build a new world. That should do the trick. This won't remove it, it will just not update it. You would have to delete it by hand. Telnet/ssh/etc don't have to depend on Kerberos and if you use the above option they will be built without Kerb support. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Remove Heimdal Kerberos from my FreeBSD
Vladimir Terziev wrote: Hi, your right about useless things, but making basic software to depend on these useless things is a very bad idea. I'm sure, telnet ssh are the most used applications on any UNIX system, so they must not depend on any third party software by default. If you need kerberized ssh or telnet, then ok -- relink them to use kerberos, but why possible bugs in kerberos should affect ssh telnet when kerberos is not mandantory for their functioning? It depends on what we chose as a basic functionality. One wouldn't use it, for other person it is necessary. Again, for generic system it is normal to have extra functionality. If we remove it, many persons would suffer from that. If you do not need it, just do not use it. And all one would be happy. It is not a problem to depend on kerberos till it isn't removed. The worse thing is indirect depend. Why I have to setup lib by dependence, that is needed by the unused functions from the lib I use? The same would be to ask to remove those functions from that lib since they add extra dependance. If smth is commonly used, even not by majority but by quite nomerous community it should be in generic system. No one is restricted to customize system for any particular case. If you have such ability there is no any problem. rik Vladimir On Mon, 18 Jul 2005 11:27:53 +0400 Roman Kurakin [EMAIL PROTECTED] wrote: Hi, Vladimir Terziev wrote: Yes, i deleted it along with all libs related to it. This caused telnet/ssh/etc to stop working. So i rebuilt the world with NO_KERBEROS=yes and now all is like a charm -- no Heimdal Kerberos and no software depending on it. I think making the Heimdal Kerberos part of the base FreeBSD OS is bad idea, but linking base software (like telnet, ssh), which is part of the base FreeBSD OS, against it, is very very bad idea. Why? Yes, all current OSs have a lot of useless things from some one point of view. For example, at work I do not need X while driver development, but at home I need it. At home I may not need almost all development tools. This is normal. If I want to setup a system fast and without additional efforts I'll setup a typical options. And I'll start use it as fast as it would be up. Most peoples do the same. It is better to have all thing in generic system that suits the majority. If you want to setup a custom system, you need to do it manually. rik Vladimir On Sun, 17 Jul 2005 22:02:04 +0930 Daniel O'Connor [EMAIL PROTECTED] wrote: On Sunday 17 July 2005 02:26, Dominic Marks wrote: In /etc/make.conf put NO_KERBEROS=yes Then build a new world. That should do the trick. This won't remove it, it will just not update it. You would have to delete it by hand. Telnet/ssh/etc don't have to depend on Kerberos and if you use the above option they will be built without Kerb support. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Malloc while freeing some object
Hi, One simple question on programming style. Is it ok to call malloc while we releasing some object? rik ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Malloc while freeing some object
Dmitry Mityugov wrote: On 6/30/05, Roman Kurakin [EMAIL PROTECTED] wrote: Hi, One simple question on programming style. Is it ok to call malloc while we releasing some object? Are you releasing it in another thread? Is it a C++ object? How are you releasing it? This was general question. In fact I've found that ttyfree() function from kernel code allocates tempory variables to free tty. I didn't expect such behaviour. I always thought that deallocation of smth should need other alloc. rik ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Call for FreeBSD status reports
IIRC most of reports should valid from the last call since they wasn't published. Am I right, or we should send them again? rik Max Laier: All, as I wrote last week: Submissions are due on April 15. Thanks a lot, and we are hoping for a big turn-out. As always this is not final, but please get your reports ready by monday and maybe let us know that you are planing to submit. Unfortunately we have a dramatically lower turn-out so far, I hope to see more reports floating in over the weekend. Thanks a lot! http://www.FreeBSD.org/news/status/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: organization
mohamed aslan wrote: hi guys it's my first post here, BTW i was a linux hacker and linux kernel mailing list member for 3 years. I am driver developer, and I work with both Linux and FreeBSD. It is usual for me to changed OS I am working with a several times a day. What can I say, both source trees have some organization problems. Personally I prefer BSD one and more dislike Linux one. IMHO this is matter of taste. By the way is this your first feeling or you have some experience with BSD hacking? (e.q. try to start programming using other language or other environment, the first feeling would be the same) rik and i've a comment here , i think the freebsd kernel source files aren't well organized as linux ones. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel documentation and specification
Read section 9 of man. Read other drivers. Check if there is an example of driver you want to write. (/usr/share/examples) PS. Use edonkey, you may find there some books. I time to time ask my friend who use edonkey often to find me smth, but if book realy deserve and I need it for direct benefit (or it is not very expensive) I prefer to get a real book. I very dislike printed books. rik klowd9 - wrote: Reading the CVS logs for the relevant files should give you ideas about who might be able to answer your questions. However, you shouldn't expect that people have time to answer lots of questions. Of course, it helps if your interest is in the context of contributing something back to the project. Kirk's book, ``The Design and Implementation of the FreeBSD Operating System'' probably contains the answers to basic questions about scheduling and IPC. I considered purchasing that book, which is very very good imo, but a bit overpriced at $60.. Any other resources about kernel development, and to whom may i speak with to help me get started.. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: style(9) example :-)
Miguel Mendez:
On Fri, 18 Mar 2005 12:06:12 +1030
Greg 'groggy' Lehey [EMAIL PROTECTED] wrote:
On Thursday, 17 March 2005 at 19:33:50 +0300, Roman Kurakin wrote:
Hi,
I was unable to refrain from posting this :-)
int i;main(){for(;i[]i;++i){--i;}];read('-'-'-',i+++hell\
o, world!\n,'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
There used to be a whole culture of this sort of thing. My favourite
one is an anagram generator:
The IOCCC (http://www.ioccc.org/) is still alive. Some of the 2004
winners are quite impressive. I tend to prefer obfuscated C over perl,
although you can easily make perl look like line noise :)
I always tell to my pupils that they can win there with the code they
produce
on lessons. :-)
rik
Cheers,
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD on IBM BladeCenter?
Have you tried FreeBSD 6.Current? Also try to boot in safe mode. Best regards, Roman Kurakin nahthan subramanian: Hi there, Any success stories out there of getting FreeBSD running on IBM BladeCenter hardware? It's not officially supported. It's designed to run Linux/*doze. Here's a document of my attempts: --- Hardware Information general: http://www-1.ibm.com/servers/eserver/bladecenter/ chassis: http://tinyurl.com/4gcbw blade: http://tinyurl.com/6js9m HS20 blade machine type: 8843 HS20 blade model number: 11U Chassis model number: 8677-3XU Chassis machine type: 8843 Chassis model number: 11U basic blade config: Dual Intel Xeon 3.0Ghz hyper threading and EM64T support 4096MB memory FreeBSD Installation media tried: tried with freebsd 5.3 i386 from floppy CD tried with freebsd 4.ii i386 from floppy CD -- tried with BIOS 1.2 on blade. tried with BIOS 1.0 on blade. -- tried with an extrenal USB keyboard connected, and without. -- tried with hyperthreading disabled in BIOS. tried with CPU cache enabled/disabled in BIOS. tried with CPU write back cache enabled/disabled in BIOS. tried with CPU prefetch queue enabled/disabled in BIOS. tried with CPU Execute Disable bit enabled/disabled in BIOS. -- tried with ACPI enabled/disabled from the installation prompt. nothing. Here are the crashes and error messages: --- FreeBSD 5.3 boot from CD/floppy crash/panic: atapci0: Intel 6300ESB UDMA 100 controller port 0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at drvice 31.1 on pci0 fatal trap 12: page fault while in kernel mode fault virtual address = 0x5 fault code = supervisor read, page not present instruction pointer = 0x8:0xc06200d0 stack pointer = 0x10:0xc1021914 frame pointer = 0x10:0xc1021914 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IPOL=0 current process = 0 (swapper) trap number = 12 panic: page fault uptime: 1s shutting down ACPI stray IRQ 11 Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Keyboard reset did not work, attempting CPU shutdown -- FreeBSD 5.2.1 booting from CD, hangs on boot: acpi0: IBM SERBLADE on motherboard pcibios: BIOS version 2.10 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 (...hangs here forever... machine completely locks up...) -- FreeBSD 4.11, booting from CD: Uncompressing ... done BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive C: is disk0 BIOS 629/3275513kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 ([EMAIL PROTECTED], Fri Jan 21 15:42:07 GMT 2005) Can't work out which disk we're booting from. Guessed BIOS device 0x0 not found by probes, defaulting to disk0: Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... can't load 'kernel' can't load 'kernel.old' Type '?' for a list of commands, 'help' for more detailed help. ok - FreeBSD 4.11, booting from floppy: Uncompressing ... done BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive C: is disk0 BIOS 629/3275513kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 ([EMAIL PROTECTED], Fri Jan 21 15:42:07 GMT 2005) /kernel text=0x289d91 data=0x30170+0x32d04 zf_read: fill error elf_loadexec: archsw.readin failed can't load module '/kernel': input/output error - Hit [Enter] to boot immediately, or any other key for command prompt. booting [kernel]... /kernel text=0x289d91 data=0x30170+0x32d04 zf_read: fill error elf_loadexec: archsw.readin failed can't load 'kernel' can't load 'kernel.old' Type '?' for a list of commands, 'help' for more detailed help. ok I can't think of much else to try for now. Any clues? Thanks. -Nate - Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
style(9) example :-)
Hi,
I was unable to refrain from posting this :-)
int i;main(){for(;i[]i;++i){--i;}];read('-'-'-',i+++hell\
o, world!\n,'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
Best regards,
rik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: style(9) example :-)
Giorgos Keramidas:
On 2005-03-17 19:33, Roman Kurakin [EMAIL PROTECTED] wrote:
Hi,
I was unable to refrain from posting this :-)
int i;main(){for(;i[]i;++i){--i;}];read('-'-'-',i+++hell\
o, world!\n,'/'/'/'));}read(j,i,p){write(j/p+p,i---j,i/i);}
I've written stuff that's probably a bit harder to read, but in Perl :P
% cat filter.pl
#/usr/bin/perl
while(STDIN){chomp;print(join('',(map{my($b,$j,$t,$o)=(65,128,90,ord($_));((
$o-$b)=0($o-$b)=($t-$b))?eval{$o=(($o-$b)+13)%26+$b;$j=11;}:eval{$b=97;$t=
122;(($b$o)||($t$o))?eval{$j=10;}:eval{$o=(($o-$b)+13)%26+$b;$j=1431;};};$_=
chr(int(int(($j%2)==(chr($o)==$_))?$o:ord($_)));}(split//,$_))).\n);}
%
I saw smth like that, which run rm -rf /. I hope this one word greeting ;-)
Probably one such code could be added to fortunes.
rik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install Free BSD without floppy, without bootableCD-ROM-drive, without boot from LAN etc.
: Hello hackers, I wrote to @questions, but as result, I have advised to address the help to you. Sorry, if I spend your time I have notebook IP-120MHz without FDD He is NOT BOOT from CD. How can i install FreeBSD on it? Hardvare configuration: Compaq 5280 Intel Pentium 120MHz 80Mb RAM 4,3 Gb HDD Hitachi CD-ROM -8x Panasonic (I CAN NOT boot from it) NO able boot from LAN, NO FDD, 2,5 HDD - I can't connect this HDD to desktop and install FreeBSD on it. Why? Or you just don't have a connector? By the way, do you have USB? You may also try another copy of CD, or better original one. Best regards, Roman Kurakin I try to load a kernen from DOS-partition usin bsdboot.com kernel, but it have called a panic because of impossibility to mount root partition BUT I read in file /tools/00_index.txt (line 1): setup.exe Prepare for installation from a DOS partition. I hope it help me, but I can not FOUND IT - I can't found setup.exe in the installatoin CD-ROM, in the ftp-server on freebsd.org Where I can found this utilite??? Whether there is any other way of installation? How can i install FreeBSD? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: parameters for tsleep(9)
Hi,
1) man tsleep
2) tsleep is just msleep with NULL mutex.
if you check sys/kern/kern_synch.c you will
see KASSERT (ident != NULL ...
ident is exactly the first parameter.
rik
Norbert Koch:
Hello.
I am just writing a device driver for the i82527 (can-bus) chip.
For testing I need the driver to poll the chip instead of running
in interrupt mode.
My dev_t read function basically looks like this:
for (;;)
{
while (chip_has_data(...))
{
read_chip_data(...);
error = do_uiomove(...);
if (error || enough_read(...))
{
return error;
}
};
if (do_not_block_on_read(...))
{
return EWOULDBLOCK;
}
error = tsleep (XXX, PCATCH|PWAIT, canrd, hz / 10);
if (error != EWOULDBLOCK)
{
return error;
}
}
XXX should be 'something' which could be used
as parameter to wakeup(9), I read in tsleep(9).
In the kernel source tree I found one
place where tsleep _only_ sleeps: in sys/isa/ppc.c
(which already seems to be in the attic [?] but
still is in my computer's source tree).
Here, the first parameter was set to NULL.
Doing this I found, that tsleep immediately
returns 0 (which means: wakueup was called)
_without_ waiting. I even crashed or
froze the kernel by calling tsleep (NULL, ...)
for a random number of times. After changing
this to the address of the read-function itself,
all worked fine. No more crashes.
Just for my understanding: Is this a bug?
Does the first parameter have to point to
something useful?
Is it allowed to point it to a code position?
Or should I use some kind of dummy data in
the softc structure instead?
What about the second parameter: Is PWAIT
ok here or should I use PZERO or whatever?
(And btw, why has ppc.c been removed?)
Thank you.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: duplicate CVS modules in merged CVSROOT
Dag-Erling Smørgrav: Dmitry Morozovsky [EMAIL PROTECTED] writes: It seems some checks should be added to module merging code... ...or somebody should stop using the merged CVSROOT. I suggest to add prefixes like src_cut, port_cut while merging. rik DES ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network monitoring
Simon Roberts: [...] Unfortunately, it turns out the hub isn't a hub, it's a switching hub (what's not a switch about this? I don't get it). Consequently, all I see are arp packets, bootp packets, and the odd broadcast. I went to a local store to buy a hub, and guess what, they sold me another switching hub, so that has to be returned :( I have a switching hub and it means that it is a 10M hub + 100M hub with a switch between 10M and 100M networks. So I guess if you both links work in the same mode you should be able to use it for monitoring. rik [...] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
MPSAFE sppp(+fr support) cp cx ctau
Hi,
I am glad to announce stable version of patches for sppp, cp, ctau and cx
drivers with support of mpsafe.
SPPP:
Sppp will work in mpsafe mode only for adapters that do not have
IFF_NEEDSGIANT flag.
Also this patch contains if_spppfr.c with fr support for sppp (4).
CP/CX/CTAU:
Adapters will work in mpsafe mode only if both debug.mpsafenet
and debug.{cp|cx|ctau}.mpsafenet set to 1.
Patches (relative current) can be downloaded from:
http://people.freebsd.org/~rik/rik_netperf_20041128-1.pch
Please test them and let me know if you have any problems.
Patches were tested on Tau-PCI - Cisco 2500 at speed 4M
on Dual CPU system with ping-f and uptime ~one week.
rik
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing from kernel
Søren Schmidt wrote: Roman Kurakin wrote: Hi, I have some problems with printing from kernel. At first I think that my problems was cause I use printf, but changed all of them to log cause it safe to use from interrupt handlers. The situation become better but I still observe system lockup in case I output some debug information from my driver. Yes its a known problem, if you output enough from the kernel the console will eventually lockup, its been so for ages, and I dont think anyone really have been looking into it. I didn't saw it before, only now after moving from Giant, but probably some system changes affect this. Hm. may be I need to try some old versions to check for this. I'll try to dig this. This was the only eye in kernel I use for ages. rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing from kernel
Don Lewis wrote: On 7 Oct, Roman Kurakin wrote: Hi, I have some problems with printing from kernel. At first I think that my problems was cause I use printf, but changed all of them to log cause it safe to use from interrupt handlers. The situation become better but I still observe system lockup in case I output some debug information from my driver. Also I have some problems with system console via com port. Instead of messages from kernel I see the first letter of the month name. This is a bug in syslogd related to non-blocking I/O that bde and I discussed quite a while back, though we never figured out a proper fix. I recently made the interesting discovery that the same problem isn't present on sparc64. I think it'll start working again if you restart syslogd. From my observation I didn't came to conclusion that this could be due to syslog, but I'll check this. Could anybody comment my observation? Does anybody saw anything like this? Oh, I forget to say I observe that with both Current and Releng5, SMP. Also I can't trigger NMI so I can't see the point of lockup. I generally use printf for this sort of thing, and I was going to suggest that you take a look at the KTR stuff, but that won't help if the machine totally locks up so that you can't get to the KTR buffer. I think you'll have trouble getting close to the bug if you use log because of the log latency from the generation of the message, passing it through syslogd, and back to the kernel to be printed. I'll try to think up how to see where I have my problems. If you plan to work on this problems we could join our efforts, rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing from kernel
Greg 'groggy' Lehey wrote: On Thursday, 7 October 2004 at 0:31:33 +0400, Roman Kurakin wrote: Hi, I have some problems with printing from kernel. At first I think that my problems was cause I use printf, but changed all of them to log cause it safe to use from interrupt handlers. The situation become better but I still observe system lockup in case I output some debug information from my driver. About the only thing I can think is that you're doing this in some area where it's unsafe to print, probably holding a lock that's needed in the print routines. I have the same idea but I cant't get which one. Also I have some problems with system console via com port. Instead of messages from kernel I see the first letter of the month name. Could anybody comment my observation? Without more detail, it's impossible to help. Does anybody saw anything like this? No. printf() is widely used in the kernel. I know. But it seems that log is more safer ... Oh, I forget to say I observe that with both Current and Releng5, SMP. Also I can't trigger NMI so I can't see the point of lockup. Take a look at your code and check what locks you're holding. Also, if this is only for debugging, you should be using the kernel debugger. It is used not only for debugging by myself, part of this output is my eye on users side. But for now, most of output is locking debugging. rik Greg -- See complete headers for address and phone numbers. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Printing from kernel
Hi, I have some problems with printing from kernel. At first I think that my problems was cause I use printf, but changed all of them to log cause it safe to use from interrupt handlers. The situation become better but I still observe system lockup in case I output some debug information from my driver. Also I have some problems with system console via com port. Instead of messages from kernel I see the first letter of the month name. Could anybody comment my observation? Does anybody saw anything like this? Oh, I forget to say I observe that with both Current and Releng5, SMP. Also I can't trigger NMI so I can't see the point of lockup. rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
LOR
Hi, Question to gurus. Does witness keep in mind lock recursion when it checks for LORs. rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LOR
John Baldwin: On Monday 16 August 2004 08:19 am, Roman Kurakin wrote: Hi, Question to gurus. Does witness keep in mind lock recursion when it checks for LORs. Well, I'm not sure if I understand exactly what you are asking, but witness My question was silly cause it is based on very silly ideas. only does lock order checks when you first acquire the lock. Any recursive locks will skip the order checking altogether since recursive acquires can never block. Similarly, trylock operations also stick order checks You've answered just that I want to know. Thanks! altogether since they can never block either. rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Sppp Cronyx (cp(4), ct(4) and cx(4)) testers required
Hi, I am near finish line in mpsafe locking work for sppp and Cronyx adapters drivers, so I need testers for work I've done. Please contact me if you whish to test this code. Best regards, Roman Kurakin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc strangeness
Dmitry Morozovsky wrote:
Dear colleagues,
one of my friends has raisen very strange issue regarding gcc rounding:
[EMAIL PROTECTED]:/tmp/tsostik uname -r
4.10-STABLE
[EMAIL PROTECTED]:/tmp/tsostik gcc -v
Using builtin specs.
gcc version 2.95.4 20020320 [FreeBSD]
[EMAIL PROTECTED]:/tmp/tsostik cat x.c
#include stdio.h
int main ()
{
float a;
for(a=0.01;a=0.1; a+=0.01)
printf(%f %.3f %d\n, a*100, a*100, (int)(a*100));
I believe this should more correct:
printf (%f %.3f %d\n, a*100, a*100, (int)(a*100+.5));
rik
return 0;
}
[EMAIL PROTECTED]:/tmp/tsostik cc x.c
[EMAIL PROTECTED]:/tmp/tsostik ./a.out
1.00 1.000 0
2.00 2.000 1
3.00 3.000 2
4.00 4.000 3
5.00 5.000 5
6.00 6.000 6
7.00 7.000 7
8.00 8.000 7
9.00 9.000 8
9.99 10.000 9
Any comments?
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] ***
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
activation of interrupt
Hi, I have problem with activation/deactivation of interrupts. I have a device driver for one ISA card. Since it is legacy ISA it's interrupt line (or it's possible interrupt lines if we were loaded with autodetection) could be assigned for PNP devices. The simplest way to find out if we able to work with this interrupt line to try to generate it and check if we see it (for example via isa_irq_pending()). Now about my proble :-). At first load of my driver all is ok. I able to work with interrupt. But at second one this interrupt is detected as non-functional. If I ignore this test, it seems that all work Ok. So problem only while I am at attach code. More over system tells me about stray irq. So I guess that this interrupt was blocked after it was unregistered. Since I don't have any more ideas what to do with this situation I ask for help and open for any advices. rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 100mhz Wavelab on -current PCI and PCCARD.
Hi, We use SMC cards, and SMS hubs (they have a couple of normal ports). I didn't heard about problems with pccard variant and hubs works just fine. But pci cards works unstable.Since I do not work in that segment and I don't have any in my PCs I can't say why we have problems with them. rik Josef Karthauser wrote: Does anyone have wireless experience? I'm off to the US next week and I thought I'd buy some (cheaper) wireless kit whilst I'm out there. I would like to run 100mb wireless (802.11g?) on both my laptop and my home server which I guess means that I'd like a recommendation for both pccard as well as pci. I'm running -current on the laptop and -stable on the server, although this can be upgraded to 5.x if necessary. The server is currently an ethernet bridging firewall (IPFW) and ideally I'd like to be able to filter the wireless segment also. Is it possible to using a wireless card in the machine and be able to filter at a MAC address level? I want a bit of control of the network. Is there a recommended configuration? Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA/CHS problem (path + new information)
Bruce Evans wrote: On Sun, 11 Apr 2004, Roman Kurakin wrote: I remind you that now I have two problems. First one that FreeBSD uses wrong assumption about which device should be CHS and which LBA: if (!ad_version(atadev-param-version_major) || !(atadev-param-atavalid ATA_FLAG_54_58) || !lbasize) atadev-flags |= ATA_D_USE_CHS; True ATA device may not have ATA_FLAG_54_58 valid bit, and also due to last ATA standard this bit is obsoleted. I also want to know why ata driver doesn't check LBA support from word 49? May be this one check could solve my problems and didn't breake code for non-ATA devices. Possibly for similar reasons. It's hard to tell what's in the LBA bit for pre-ATA devices older than LBA. Similarly for the lbasize words, but it's easier to do a sanity check on a 32-bit values that a 1-bit flag. But since ATA_FLAG_54_58 bit from the fist spec means 1 - valid and 0 - may be valid this check is initialy incorrect. According to ATA-5 it is depricated. But in later revisions of ST380021A (according to their datasheet, I don't have one) Seagate changed this bit to 1 back, I may guess that this was done since probably others uses the same check. :-( Anyway, it seems that Soren already removed this check. So my ST380021A should back to the life. Second one, that only 20G part of my hard disk works with CHS. This is other side of the same problem. Device should work in CHS mode. And it works witch ICH5 controller. But with ICH2 it doesn't with out hack. I've checked standard again and I sew command 91h (Initialize drive parameters). Check out the commands for limiting the (apparent) disk size. IIRC, the CHS limit can be set independently of the LBA limit, and some settings are harder than others so that they can't be cleared by old commands like 0x91. The limits may be set to prevent old drivers which only understand old commands from becoming confused by trying to actually use the whole disk. This is good idea. I sew only LBA limits, but I didn't see anytihng about CHS limits. I'll try to check for some more commands. I can't get how ATA controller could affect on this. Brobably this is not controller problem but BIOS, but changing its settings didn't affect. Thanks for reply, I hope your suggestions will help me. Since Soren removed first bug I'll keep digging from obstinacy :-) rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
sysinstall
Hi, If sysinstall detects wrong geometry, it tries to correct it and suggests to use G option to chage geometry if I disagree with it. But it doesn't allow to set whatever geometry I want with G. Is this intentional behaviour or it should be fixed. (in case it should be fixed I may send my solution of this problem). PS. While searching for other things, I repeatedly faced with threads about such problem, and if my memory does not fail, I saw pr about it. But now I can't find any prs and messages about this behaviour of sysinstall. So please take my apologies if I am opening already closed subject. Best regards, Roman Kurakin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and Debugging?
Colin Percival wrote: At 06:11 10/04/2004, Brandon Erhart wrote: Are there any debuggers out there for BSD that will detect the heap/stack corruption!? Real Men use printf(3). :-) You are talking as Linus ;-) rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
ATA/CHS problem (path + new information)
Hi, You can find history of my previous postings below. I didn't moved far since that time, because lack of time. But any way I have some new information and one patch I want to share. This patch didn't solve any of my problems. Soren, please review it. This time it is comlete. I hope this patch would allow to track down similar problems I have. I remind you that now I have two problems. First one that FreeBSD uses wrong assumption about which device should be CHS and which LBA: if (!ad_version(atadev-param-version_major) || !(atadev-param-atavalid ATA_FLAG_54_58) || !lbasize) atadev-flags |= ATA_D_USE_CHS; True ATA device may not have ATA_FLAG_54_58 valid bit, and also due to last ATA standard this bit is obsoleted. I also want to know why ata driver doesn't check LBA support from word 49? May be this one check could solve my problems and didn't breake code for non-ATA devices. Second one, that only 20G part of my hard disk works with CHS. This is other side of the same problem. Device should work in CHS mode. And it works witch ICH5 controller. But with ICH2 it doesn't with out hack. I've checked standard again and I sew command 91h (Initialize drive parameters). YES, this command solved my problem witch CHS. But. But the life is no so easy :-) This command fails itself with abort code. But as I said I can access sectors that was previously NOT FOUND after it. (ata_controlcmd (atadev,0x91, 0, 0xfUL 24, 63); I've put it just after Identify driver command in ata_getparam function) Any comments and suggestions very very appreciated. And please do not suggest how to fix this problem only for me. I already know a few variant that can't be commited. I realy want to crush this bug. rik Roman Kurakin wrote: Hi, (Was HDD question on hackers@, posted also here cause this is also CURRENT problem) History: I have some problems with my HDD (ST380021A). The problem was checked on 5.2, 5.2.1, and some 5.Current (cvsuped about week or two). At first I got this problem while system installation. I get trap and message from ata after I start a commit: FAILURE READ_DMA status=51 READY, DSC, ERROR error=10 NID_NOT_FOUND LBA=245529601 I started to hack sysinstall and finally came to simple program that could lead to the same message from ata: fd = open (/dev/ata0, O_RDWR); read_block (fd, (daddr_t)41929650, 512); // this one could be changed // to pair calls lseek and read, // so this is not libdisk problem I checked the same code with /dev/ata1 which is twice as little, but I didn't get any messages. I don't have any ideas where my read call goes, which drivers to look to catch this bug. So I need a help from some gurus in this area. What I've found since that time: This is not an LBA request. ATA driver thinks that I have 80G CHS device, cause it's ATA_FLAG_54_58 is zero. (This decision is incorrect, we shouldn't relay on this flag). I've checked another seagate 80G drive in CHS mode(by driver hacking), and problematic one with LBA mode. I get the same behavior on both with CHS. And both work fine in LBA mode. It also should be mentioned that I get this problem on machine with ICH2 controller, and it seems that I don't have such problem on other machine with ICH5. PS. If you have any ideas, or if you have any materials (standards for example) about ATA/ATAPI and you can share them with me, please let me know. I am not ata developer, so this is a bit difficalt for me to dig this problem. rik diff -ubr ata-orig/ata-disk.c ata/ata-disk.c --- ata-orig/ata-disk.c Wed Mar 10 20:05:56 2004 +++ ata/ata-disk.c Sun Apr 11 12:26:02 2004 @@ -388,13 +388,14 @@ (adp-heads * adp-sectors)), adp-heads, adp-sectors, DEV_BSIZE); - ata_prtdev(adp-device, %d secs/int, %d depth queue, %s%s\n, + ata_prtdev(adp-device, %d secs/int, %d depth queue, %s%s%s\n, adp-max_iosize / DEV_BSIZE, adp-num_tags + 1, (adp-flags AD_F_TAG_ENABLED) ? tagged : , - ata_mode2str(adp-device-mode)); + ata_mode2str(adp-device-mode), + (adp-device-flags ATA_D_USE_CHS) ? (CHS mode): ); } else - ata_prtdev(adp-device,%lluMB %.40s [%lld/%d/%d] at ata%d-%s %s%s\n, + ata_prtdev(adp-device,%lluMB %.40s [%lld/%d/%d] at ata%d-%s %s%s%s\n, (unsigned long long)(adp-total_secs / ((1024L * 1024L) / DEV_BSIZE)), adp-device-param-model, @@ -404,7 +405,8 @@ device_get_unit(adp-device-channel-dev), (adp-device-unit == ATA_MASTER) ? master : slave, (adp-flags AD_F_TAG_ENABLED) ? tagged : , - ata_mode2str(adp-device-mode)); + ata_mode2str(adp-device-mode), + (adp-device-flags ATA_D_USE_CHS) ? (CHS mode): ); } static int diff -ubr ata-orig/ata-queue.c
Re: Kernel debugging with a multiport serial card
Craig Rodrigues wrote: Hi, I have a few FreeBSD machines with an RJ-45 serial connector on the motherboard. I would like to hook these machines up to a single FreeBSD PC with a multiport serial card and set it up to do kernel debugging. Can anyone recommend any multiport serial cards? There are many multiport cards. Just grep sio (4) or puc (4) sources. Cronyx: http://www.cronyx.ru/hardware/ompci.html DigiBoard Moxa atc Best regards, rik Are there any cards with known problems? Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: [Fwd: Re: ATA/CHS problem]]
S?ren Schmidt wrote: Roman Kurakin wrote: This is not an LBA request. ATA driver thinks that I have 80G CHS device, cause it's ATA_FLAG_54_58 is zero. (This decision is incorrect, we shouldn't relay on this flag). I've checked another seagate 80G drive in CHS mode(by driver hacking), and problematic one with LBA mode. I get the same behavior on both with CHS. And both work fine in LBA mode. It also should be mentioned that I get this problem on machine with ICH2 controller, and it seems that I don't have such problem on other machine with ICH5 Hmm, we could loosen up this check (Se patch below) but that will probably break support for real old ATA disks (note that those old Probably I'll do something like that, but since I've already lost some time on this problem I want to get why CHS mode doesn't works. I can't understand how using of ICH2 could lead to such problems ... (I'll try to get access to other ICH2 and non ICH2 machines to make extra checks). As I understand before using CHS we issue command 91h, to set proper CHS mode. I have one really CHS device and it seems to be working. systems most likely will have trouble with -current anyways). If I coul dhave my ways, we wouldn't even try to support disks that doesn't support LBA I think we could use another way to check old ata. Why no to use bit9 from word 49 and if device really ATA, why it's 60-61 words are non zero? PS. If you have any ideas, or if you have any materials (standards for example) about ATA/ATAPI and you can share them with me, please let me know. I am not ata developer, so this is a bit difficalt for me to dig this problem. Go to t13.org they are the standards body for ATA etc... I already have a couple of drafts, but probably I need to get some more information. Please take a look to my patch. It makes output more informative. If I have it before I started to dig, I didn't lost so much time. There is a couple of places where we may need to apply the alike patches. rik --- ata-queue.c.origTue Mar 23 20:39:22 2004 +++ ata-queue.c Thu Mar 25 00:45:51 2004 @@ -316,7 +316,9 @@ (request-dmastat ATA_BMSTAT_ERROR)) printf( dma=0x%02x, request-dmastat); if (!(request-flags (ATA_R_ATAPI | ATA_R_CONTROL))) - printf( LBA=%llu, (unsigned long long)request-u.ata.lba); + printf((request-device-flags ATA_D_USE_CHS) + ? CHS=%llx : LBA=%llu, + (unsigned long long)request-u.ata.lba); printf(\n); } ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
ATA/CHS problem
Hi, (Was HDD question on hackers@, posted also here cause this is also CURRENT problem) History: I have some problems with my HDD (ST380021A). The problem was checked on 5.2, 5.2.1, and some 5.Current (cvsuped about week or two). At first I got this problem while system installation. I get trap and message from ata after I start a commit: FAILURE READ_DMA status=51 READY, DSC, ERROR error=10 NID_NOT_FOUND LBA=245529601 I started to hack sysinstall and finally came to simple program that could lead to the same message from ata: fd = open (/dev/ata0, O_RDWR); read_block (fd, (daddr_t)41929650, 512); // this one could be changed to pair calls lseek and read, // so this is not libdisk problem I checked the same code with /dev/ata1 which is twice as little, but I didn't get any messages. I don't have any ideas where my read call goes, which drivers to look to catch this bug. So I need a help from some gurus in this area. What I've found since that time: This is not an LBA request. ATA driver thinks that I have 80G CHS device, cause it's ATA_FLAG_54_58 is zero. (This decision is incorrect, we shouldn't relay on this flag). I've checked another seagate 80G drive in CHS mode(by driver hacking), and problematic one with LBA mode. I get the same behavior on both with CHS. And both work fine in LBA mode. It also should be mentioned that I get this problem on machine with ICH2 controller, and it seems that I don't have such problem on other machine with ICH5. PS. If you have any ideas, or if you have any materials (standards for example) about ATA/ATAPI and you can share them with me, please let me know. I am not ata developer, so this is a bit difficalt for me to dig this problem. rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HDD questions
This is realy CHS request, not lba. I checked configuration it contains 6 in word 53 from indentify drive information. Ata driver decides because of that that hdd is in CHS mode not in LBA. By the way I checked this hdd with other main board. I read this (I hope that it is realy this one) sector without any problem. But hdd seems to be wroking in CHS mode any way. Any ideas? rik Søren Schmidt wrote: Roman Kurakin wrote: Hi, I have some problems with my HDD (ST380021A). The problem was checked on 5.2, 5.2.1, and some 5.Current (cvsuped about week or two). At first I got this problem while system installation. I get trap and message from ata after I start a commit: FAILURE READ_DMA status=51 READY, DSC, ERROR error=10 NID_NOT_FOUND LBA=245529601 If I read the above modelnumber correctly it is a 80G disk.. There is only ~16000 sectors on such a disk, so you cant expect to read sector 245529601 as its not there :) Now why sysinstall tries to do that is beyond me, but could be a problem with the geometry (it seems to always get it wrong these days). -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HDD questions
One more thing could we realy rely on presensents ATA_FLAG_54_58? As I find out 0 means could be valid (not not valid) and in ATA-6 we could se that this bit is obsolete? So if word 54-58 are not valid (or may be not valid) doesn't mean that we have non LBA drive. rik Roman Kurakin wrote: This is realy CHS request, not lba. I checked configuration it contains 6 in word 53 from indentify drive information. Ata driver decides because of that that hdd is in CHS mode not in LBA. By the way I checked this hdd with other main board. I read this (I hope that it is realy this one) sector without any problem. But hdd seems to be wroking in CHS mode any way. Any ideas? rik Søren Schmidt wrote: Roman Kurakin wrote: Hi, I have some problems with my HDD (ST380021A). The problem was checked on 5.2, 5.2.1, and some 5.Current (cvsuped about week or two). At first I got this problem while system installation. I get trap and message from ata after I start a commit: FAILURE READ_DMA status=51 READY, DSC, ERROR error=10 NID_NOT_FOUND LBA=245529601 If I read the above modelnumber correctly it is a 80G disk.. There is only ~16000 sectors on such a disk, so you cant expect to read sector 245529601 as its not there :) Now why sysinstall tries to do that is beyond me, but could be a problem with the geometry (it seems to always get it wrong these days). -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make install (kernel) without /modules dir
Ruslan Ermilov wrote:
Roman Kurakin wrote:
I forget to say that this problem is for 4. branch
Roman Kurakin wrote:
Hi,
It seems that I've found another problem. If /modules dir would be
removed,
make install (of kernel and kernel modules) will not create modules
dir and you'll
get /modules file with one of the modules inside.
One of the variants is to add flag -d to install or other to mkdir -p
explicitly:
misprint: -d flag should be -D flag
I forgot to check that this is only linux's install behavior.
--- Makefile.oldFri Mar 12 00:13:45 2004
+++ MakefileFri Mar 12 00:15:03 2004
@@ -626,6 +626,7 @@
cp -p ${DESTDIR}/modules/* ${DESTDIR}/modules.old; \
fi;
.endif
+ mkdir -p ${DESTDIR}/modules
cd $S/modules ; env ${MKMODULESENV} ${MAKE} install
modules-reinstall modules-reinstall.debug:
An old problem. 5.x is only partly affected by this, because
of a side effect of kern.post.mk creating the necessary directory,
but if you attempt to install from src/sys/modules/ when
/boot/kernel doesn't exist, it exhibits the same behavior.
In RELENG_4 the situation is worse, as even make installkernel
can exhibit such behavior. I once had a patch locally that adds
make hierarchy to the installkernel path, similar to how this
is done for installworld.
The problem is not unique to just kernel modules; if you attempt
to install src/bin/ when /bin doesn't exist you'll see the same
behavior, that's why I think the below change is not quite
incorrect.
I believe there's a PR open on this (probably even assigned to
myself), but I just don't have a clever idea of how to fix it
properly, sorry -- generally, standard directories are created
with mtree(8), and not with mkdir(1).
If our install was like linux one which have -D flag, we could solve our
problem
by setting it globaly to install in sys.mk:
-INSTALL ?= install -D
+INSTALL ?= install -D
This flag dictates to create all necessary dirs if needed.
It would be nice to have such option, not -D of course.
My FreeBSD 3.4 machine tolds me that -D is debug flag.
Roman
Cheers,
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make install (kernel) without /modules dir
Dag-Erling Smrgrav wrote: Roman Kurakin [EMAIL PROTECTED] writes: If our install was like linux one which have -D flag, we could solve our problem by setting it globaly to install in sys.mk: [...] My FreeBSD 3.4 machine tolds me that -D is debug flag. install(1) no longer has a -D option (since May 2001), so there's nothing to stop someone from reusing it for this purpose. Why are you still running 3.4? This is an old well configured server. New one will run 5.2.1 when I'll get enought time to configure it and test all applications. :-) This is an old good rule if it works do not touch it. rik DES ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make install (kernel) without /modules dir
Ruslan Ermilov wrote: On Fri, Mar 12, 2004 at 06:08:22PM +0300, Roman Kurakin wrote: [...] If our install was like linux one which have -D flag, we could solve our problem by setting it globaly to install in sys.mk: -INSTALL ?= install -D +INSTALL ?= install -D This flag dictates to create all necessary dirs if needed. It would be nice to have such option, not -D of course. $ install file foo/bar Should it install file as foo/bar or should it create the foo/bar directory and install it as foo/bar/file? ;) two variants 1. cp style (you can write foo/bar or foo/bar/ to get what you want) 2. linux's install -D style: foo - dirname, bar filename Cheers, ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HDD problem research (was HDD questions)
Thanks. This weekend I'll try last version from 4.x branch, and early versions of 5.x branch may be this would help me to find 10 diffs :-))) Best regards, Roman Kurakin [EMAIL PROTECTED] wrote: Does any body have Segate drive ST380021A working with FreeBSD? I do. For ~ 1.5 years now. Still running 4.6.2-RELEASE; booted 4.8-RELEASE live-CD (frenzy.org.ua) without any problem. ad0: 76319MB ST380021A [155061/16/63] at ata0-master UDMA100 IDE controller: Intel ICH4 Timestamp: 0x40500478 [SorAlx] http://cydem.org.ua/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
make install (kernel) without /modules dir
Hi,
It seems that I've found another problem. If /modules dir would be
removed,
make install (of kernel and kernel modules) will not create modules dir
and you'll
get /modules file with one of the modules inside.
One of the variants is to add flag -d to install or other to mkdir -p
explicitly:
--- Makefile.oldFri Mar 12 00:13:45 2004
+++ MakefileFri Mar 12 00:15:03 2004
@@ -626,6 +626,7 @@
cp -p ${DESTDIR}/modules/* ${DESTDIR}/modules.old; \
fi;
.endif
+ mkdir -p ${DESTDIR}/modules
cd $S/modules ; env ${MKMODULESENV} ${MAKE} install
modules-reinstall modules-reinstall.debug:
Best regards,
Roman Kurakin
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make install (kernel) without /modules dir
I forget to say that this problem is for 4. branch
Roman Kurakin wrote:
Hi,
It seems that I've found another problem. If /modules dir would be
removed,
make install (of kernel and kernel modules) will not create modules
dir and you'll
get /modules file with one of the modules inside.
One of the variants is to add flag -d to install or other to mkdir -p
explicitly:
--- Makefile.oldFri Mar 12 00:13:45 2004
+++ MakefileFri Mar 12 00:15:03 2004
@@ -626,6 +626,7 @@
cp -p ${DESTDIR}/modules/* ${DESTDIR}/modules.old; \
fi;
.endif
+ mkdir -p ${DESTDIR}/modules
cd $S/modules ; env ${MKMODULESENV} ${MAKE} install
modules-reinstall modules-reinstall.debug:
Best regards,
Roman Kurakin
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
HDD problem research (was HDD questions)
Does any body have Segate drive ST380021A working with FreeBSD? Does any body have problems with it running 5.2-5.current or other versions of FreeBSD? Best regards, Roman Kurakin Roman Kurakin wrote: Søren Schmidt wrote: Roman Kurakin wrote: Hi, I have some problems with my HDD (ST380021A). The problem was checked on 5.2, 5.2.1, and some 5.Current (cvsuped about week or two). At first I got this problem while system installation. I get trap and message from ata after I start a commit: FAILURE READ_DMA status=51 READY, DSC, ERROR error=10 NID_NOT_FOUND LBA=245529601 If I read the above modelnumber correctly it is a 80G disk.. There is only ~16000 sectors on such a disk, so you cant expect to read sector 245529601 as its not there :) I know that, and this is the problem. I am trying to read 41929650, but system thinks this is 245529601. This sector is near 20G mark, so I tried to read it from 40G disk, which I use to run fbsd. All is fine. Now why sysinstall tries to do that is beyond me, but could be a problem with the geometry (it seems to always get it wrong these days). This is not a problem of sysinstall at all. As I wrote, it is enougth to try to read one sector. So this problem somewhere between read call and ata driver. This area wasn't in focus of my interest before, so I don't know where to go. Also, I tryied to read some sectors back and forward, and found out that value of LBA changes nolinear. Lower byte is linear only on interval of 63 values, so I gues this is a sector value. And it seems that LBA value not LBA value at all :-( This is all I have now. Any ideas, comments? Best regards, Roman Kurakin -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HDD questions
Søren Schmidt wrote: Roman Kurakin wrote: Hi, I have some problems with my HDD (ST380021A). The problem was checked on 5.2, 5.2.1, and some 5.Current (cvsuped about week or two). At first I got this problem while system installation. I get trap and message from ata after I start a commit: FAILURE READ_DMA status=51 READY, DSC, ERROR error=10 NID_NOT_FOUND LBA=245529601 If I read the above modelnumber correctly it is a 80G disk.. There is only ~16000 sectors on such a disk, so you cant expect to read sector 245529601 as its not there :) I know that, and this is the problem. I am trying to read 41929650, but system thinks this is 245529601. This sector is near 20G mark, so I tried to read it from 40G disk, which I use to run fbsd. All is fine. Now why sysinstall tries to do that is beyond me, but could be a problem with the geometry (it seems to always get it wrong these days). This is not a problem of sysinstall at all. As I wrote, it is enougth to try to read one sector. So this problem somewhere between read call and ata driver. This area wasn't in focus of my interest before, so I don't know where to go. Also, I tryied to read some sectors back and forward, and found out that value of LBA changes nolinear. Lower byte is linear only on interval of 63 values, so I gues this is a sector value. And it seems that LBA value not LBA value at all :-( This is all I have now. Any ideas, comments? Best regards, Roman Kurakin -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
HDD questions
Hi, I have some problems with my HDD (ST380021A). The problem was checked on 5.2, 5.2.1, and some 5.Current (cvsuped about week or two). At first I got this problem while system installation. I get trap and message from ata after I start a commit: FAILURE READ_DMA status=51 READY, DSC, ERROR error=10 NID_NOT_FOUND LBA=245529601 I started to hack sysinstall and finally came to simple program that could lead to the same message from ata: fd = open (/dev/ata0, O_RDWR); read_block (fd, (daddr_t)41929650, 512); // this one could be changed to pair calls lseek and read, // so this is not libdisk problem I checked the same code with /dev/ata1 which is twice as little, but I didn't get any messages. I don't have any ideas where my read call goes, which drivers to look to catch this bug. So I need a help from some gurus in this area. Best regards, Roman Kurakin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MAJOR number #2
Hi, Daniel Eischen wrote: On Mon, 17 Nov 2003, Roman Kurakin wrote: Hi, I need a new MAJOR number for our new device. How can I get it? I've read that FreeBSD doesn't use them any more. But we may need it to not interfere with other device drivers in previous releases of FreeBSD. ??? ce Cronyx Tau-32 E1 adapter You don't need them in -current. You might want to send this to -stable or -arch if noone responds. Thank you for reply. Best regards, Roman Kurakin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
MAJOR number
Hi, I need a new MAJOR number for our new device. How can I get it? I've read that FreeBSD doesn't use them any more. But we may need it to not interfere with other device drivers in previous releases of FreeBSD. ??? ce Cronyx Tau-32 E1 adapter ___ Best regars, Roman Kurakin Cronyx Engineering http://www.cronyx.ru ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fgdg
Hi, Joerg Micheel wrote: On Mon, Mar 17, 2003 at 12:39:22PM +0300, sergej wrote: mozno li ustanovit% odnovremenno na odin disk: unix i windows, i kak jto sdelat%! I think it would be better if you will ask questions in English. Get yourself a copy of the Complete FreeBSD by Greg Lehey, which covers this subject very well. This question also belongs to freebsd-questions, not -hackers. In short, the configuration option is there with FreeBSD as delivered, but you need to take care on making the right steps at the right time. Starting off with BSD first is the better way to proceed, adding Windows later. If you setup at first FreeBSD and then add Windows you will lose FreeBSD's boot loader. And you will have to reinstall bootloader. You also could meet other problems. If your set incorrect (from FreeBSD's point of view) geometry for you hard disk and install freebsd 5.0 after Windows 2000, freebsd will fix windows partition entry and any reinstalletions or fix procedures of Windows will lead to nothing. Probably some last versions from 4.x branch have the same features, but the last 4.x version I worked with at home was 4.3. PS. I don't know if this bug was fixed in current versions. I am almost sure that it is not. Best regards, Roman Kurakin Joerg To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
