Strange thing that the version x86 of centos works very well and not freeze. Anyway, after talking on centos irc channel , i filed this bug to redhat. The i kernel does not freeze, it run very well. Don't forget that CentOS uses only kernels released upstream See the bugzilla entry on upstream's website and you'll see that they didn't even react on this not a rh problem anyway My idea is that you can contact people from the pptpclient.
Hello, What is Centosplus? What is difference between Centos and Centosplus? And where coudl I find packages of centosplus? What am I supposed to do to trigger the freeze reported here? Hi guys! Could you be so kind to try to read bug description? I'm afraid, that we should remove centos from our security servers and migrate to debian.
Kernel freeze is caused by the module, not by userspace programs using it pppd, actually. Plesase, read the first post carefully. Create an encrypted ppp connection if you want to reproduce kernel panic. Please, read the first post carefully. Just a user like yourself. So I am free to say good luck with debian.
I also had a very nasty kernel crash problem which was introduced in the cifs module of kernel 2. The system was totally useless FC5 and FC6. Luckily, I was able to get a fix with a lot of help from cifs programmers. Then when CentOS 5 came out which uses 2. RedHat does not even offer this kind of help.
In principle, CentOS does not repair the kernel. It reproduces everything from upstream including bugs. In the above example, I also worked with RedHat to get the bug fix applied to their kernel because this is the only way to have that fix in CentOS kernels.
As a result, the cifs bug is now supposed to be included in RHEL 5. I think you should do the same. Push upstream and do it very hard. That's the lesson I learned. I suggest all "bug friend" to post on redhat bugzilla, as i realize, centos cannot fix the kernel, the solution is in upstream.
Ok, thank you. Another question: does anybody compile mppe module with dkms in CentOS5? Again, my answer is as a user If the channel needs some headroom in the skbuffs presented to it for transmission i.
The generic PPP code does not require this but will be more efficient if this is done. The generic PPP layer has been designed to minimize the amount of data that it buffers in the transmit direction.
It maintains a queue of transmit packets for the PPP unit network interface device plus a queue of transmit packets for each attached channel.
After this point the packets can no longer be reordered, as the decompression algorithms rely on receiving compressed packets in the same order that they were generated. If the channel refuses to take the packet, the generic layer saves it for later transmission. The generic layer contains no timeout and retransmission logic; it relies on the core networking code for that.
If multilink is in use, the generic layer divides the packet into one or more fragments and puts a multilink header on each fragment. It decides how many fragments to use based on the length of the packet and the number of channels which are potentially able to accept a fragment at the moment. The channel may still refuse a fragment; in this case the fragment is queued up for the channel to transmit later.
This scheme has the effect that more fragments are given to higher- bandwidth channels. It also means that under light load, the generic layer will tend to fragment large packets across all the channels, thus reducing latency, while under heavy load, packets will tend to be transmitted as single fragments, thus reducing the overhead of fragmentation.
Locks are used around accesses to the internal data structures where necessary to ensure their integrity. As part of this, the generic layer requires that the channels adhere to certain requirements and in turn provides certain guarantees to the channels. The generic layer will not call the ioctl function for a channel while any thread is already executing in that function for that channel. This is used by pppd to control PPP interface units and channels.
Using an ioctl call, it can then be attached to an existing unit, attached to a newly-created unit, or attached to an existing channel.
An instance attached to a unit can be used to send and receive PPP control frames, using the read and write system calls, along with poll if necessary. Similarly, an instance attached to a channel can be used to send and receive PPP frames on that channel. In multilink terms, the unit represents the bundle, while the channels represent the individual physical links.
Thus, a PPP frame sent by a write to the unit i. In contrast, a PPP frame sent by a write to the channel will be sent as-is on that channel, without any multilink header.
A channel is not initially attached to any unit. In this state it can be used for PPP negotiation but not for the transfer of data packets. It can then be connected to a PPP unit with an ioctl call, which makes it available to send and receive data packets for that unit. The ioctl calls which are available on an unattached instance are:. The argument should point to an int containing the unit number. This does not make this instance the owner of the PPP interface.
The argument should point to an int containing the channel number. The argument should point to an int containing the interface unit number. The argument should point to an int containing the channel number of the channel to bridge to.
The argument should point to an int containing the new MRU value. The argument should be a pointer to an int containing the new flags value. The bits in the flags value that can be set are:.
0コメント