[EMAIL PROTECTED] said:
i prefer clear oopses and bug reports instead of ignoring them. A
failed MSR write is not something to be taken easily. MSR writes if
fail mean that there is a serious kernel bug - we want to stop the
kernel and complain ASAP. And correct code will be much more
[EMAIL PROTECTED] said:
And what a pile of crud those patches are!! Instead of using the
clean replacement interface for get_module_symbol, nvidia/
patch-2.4.0-PR hard codes the old get_module_symbol algorithm as
inline code.
Taking away get_module_symbol() and providing a replacement
[EMAIL PROTECTED] said:
Q. With your suggested static method, what happens when Y initialises
before X, calls inter_module_get, retrieves X's static data and
starts to use it before X has initialised?
A. Oops!
No. You'd explicitly only use the static registration when object X
[EMAIL PROTECTED] said:
So you want two services, one static for code that does not do any
initialisation and one dynamic for code that does do initialisation.
Can you imagine the fun when somebody adds startup code to a routine
that was using static registration?
Oh come on. If you
On Fri, 12 Jan 2001, Keith Owens wrote:
People need to realise that the problem is initialisation order,
nothing more, nothing less. You have to determine and document the
startup requirements for your code.
This is true. But I'd also agree with the implication which you probably
didn't
[EMAIL PROTECTED] said:
You just proved my point. It is extremely difficult to deduce the
required initialisation order by reading an undocumented Makefile
where the init order is implemented as a side effect of selection
order. The existing method implies link order when none is
[EMAIL PROTECTED] said:
No, I'm judging based on the fact that I found reports from people
using NE2K-PCI with several cards as well as tulip-based cards
(different driver) on abit BP6 as well as Gigabyte motherboards,
mostly on 2.3.x/2.4.x kernels. I found some postings with these
[EMAIL PROTECTED] said:
IRR for interrupt 19 is set, that means the IO APIC has sent the
interrupt to a cpu but not yet received the corresponding EOI.
OK, but couldn't we reset it by sending an extra EOI when the drivers
decide that they've missed interrupts?
--
dwmw2
-
To unsubscribe
On Fri, 12 Jan 2001, Ingo Molnar wrote:
okay - i just wanted to hear a definitive word from you that this fixes
your problem, because this is what we'll have to do as a final solution.
(barring any other solution.)
Patching 8390.c won't fix this for me. The only thing on IRQ19 when I saw
On Sat, 13 Jan 2001, Keith Owens wrote:
Over emphasis for humorous effect. Must remember to add smiley.
Heh. But it does deserve to get into the fortune file.
What this patch and David Woodhouse's comments show is that I need to
look at a generic and safe mechanism for kernel/module symbol
On Sat, 13 Jan 2001, Keith Owens wrote:
BTW, modutils cannot automatically fill in upward references when a
module is loaded. A reference is a use count, an automatic reference
would be an automatic use count with no way of removing it. Code that
calls upwards to a symbol must perform an
On 12 Jan 2001, Linus Torvalds wrote:
In short, let's leave it out of a stable kernel for now, and add
blacklisting of auto-DMA. Alan has a list. We can play around with
trying to _fix_ DMA on the VIA chipsets in 2.5.x (and possibly backport
the thing once it has been sufficiently
On Sun, 14 Jan 2001, Keith Owens wrote:
This is becoming more important as the kernel moves towards hot
plugging devices, especially for binary only drivers. It is far better
for the kernel community if modutils can say "cannot load module foo
because its interfaces do not match the kernel,
On Sat, 13 Jan 2001, Linus Torvalds wrote:
Somebody who can test it needs to send me a patch - I'm NOT going to apply
patches that haven't been tested and that I cannot test myself.
This patch has worked for me and is obvious enough that I haven't bothered
to rewire my box to put the IBM
On 13 Jan 2001, Linus Torvalds wrote:
You miss _entirely_ the reason why "get_module_symbol()" was removed,
and why I will not _ever_ accept it coming back.
Hint #1: get_MODULE_symbol().
Hint #2: compiled in functionality.
Er,... forgive me if I'm being overly dense here, but I can't see
On Sun, 14 Jan 2001, Linus Torvalds wrote:
Note that previously there _were_ order dependencies. In fact, I consider
it very tasteless to have modules that act differently on whether another
module is loaded. I saw some arguments saying that this is th "right
thing", and I disagree
On Sun, 14 Jan 2001, Linus Torvalds wrote:
This is what "request_module()" and "kmod" is all about. Once we probe the
hardware, the drievr itself can ask for more drivers.
I completely fail to see the arguments that have been brought up for drm
doing ugly things. The code should simply do
On Sun, 14 Jan 2001, Linus Torvalds wrote:
On Sun, 14 Jan 2001, David Woodhouse wrote:
That's the one flaw in the inter_module_get() stuff - we could do with a
way to put entries in the table at _compile_ time, rather than _only_
at run time.
Ok, I can buy that. Not having
[EMAIL PROTECTED] said:
That is a lot of work for a very few special cases. OTOH, you could
just add a few lines of __initcall code in two source files (which I
did when I wrote inter_module_xxx) and swap the order of 3 lines in
drivers/mtd/Makefile. Guess which alternative I am going for?
[EMAIL PROTECTED] said:
[Venkatesh Ramamurthy]
Your name is already in the headers of the mail you sent. There's no need to
repeat it.
The LILO boot loader and the LILO command line utility should be changed
for this.
Is anybody doing this? -
There are patches available for the
[EMAIL PROTECTED] said:
One reason why this may NOT ever make it into the kernel is that I
know "kernel poking at devices" is really frowned upon.
A possible alternative is to specify drives by serial number.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe
[EMAIL PROTECTED] said:
The one thing I don't know is... can the kernel mount the root fs if
only given the uuid?
There are 2.2 patches to do it, which I think are now being dusted off and
resurrected. but scanning for UUID involves poking at every partition on
every available hard drive.
[EMAIL PROTECTED] said:
Access is ok with kernel 2.2 even in a case when machine with 2.4
kernel is masquerading host. It doesn't work with any port. Ping
works.
Read the FAQ again. More carefully this time. Pay close attention to
section 14.2
http://www.tux.org/lkml/
--
dwmw2
-
To
[EMAIL PROTECTED] said:
we need some kind of signature being written in the drive, which the
kernel will use for determining the boot drive and later re-order
drives, if required.
Is someone handling this already?
It should be possible to read the BIOS setting for this option and
behave
[EMAIL PROTECTED] said:
For Linux I think the right way to handle this is to have each
(SA_SHIRQ) sharing capable interrupt handler return a TRUE or FALSE
value indicating whether the interrupt belongs to the driver. In
kernel/irq.c:handle_IRQ_event() check the return value. If after one
On Fri, 19 Jan 2001 [EMAIL PROTECTED] wrote:
Many oopses appeared, among others gcc closed with signal 11.
One output:
Read http://www.tux.org/lkml/#s4-3
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Fri, 19 Jan 2001, John O'Donnell wrote:
snpe wrote:
Is there ibcs2 or abi for kernel 2.4.x ?
Been discussed - Check this out:
http://marc.theaimsgroup.com/?l=linux-kernelm=97149702506290w=2
Yeah - dusting it off and making it work in 2.5 is somewhere on my
ever-growing TODO list.
On Sat, 20 Jan 2001, Linus Torvalds wrote:
There's no no-no here: you can even create the "struct page"s on demand,
and create a dummy local zone that contains them that they all point back
to. It should be trivial - nobody else cares about those pages or that
zone anyway.
This is very
On Mon, 22 Jan 2001, Rainer Mager wrote:
I brought up this issue last month and had some response but as
of yet my particular problem still exists. In brief, X windows dies
with signal 11. I have done quite a bit of testing and this does not
seem to be a hardware issue. Also, I have
[EMAIL PROTECTED] said:
It says: IP-Config: No network devices available.
a few lines below that the nic (3com 575) is detected. Of course it
fails to do the nfs mount.
The kernel delays the initialisation of CardBus sockets to prevent it from
dying in an IRQ storm as soon as it registers
On Wed, 24 Jan 2001, Albert D. Cahalan wrote:
Paul Mackerras writes:
I'll bet you're using an old pppd. You need version 2.4.0 of pppd,
available from ftp://linuxcare.com.au/pub/ppp/, as documented in the
Documentation/Changes file.
Even Red Hat 7 only has the 2.3.11 version.
That's
What does IS_DEADDIR give us that (!(inode)-i_nlink) doesn't?
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
[EMAIL PROTECTED] said:
I seem to be getting more and more patches that have tabs/spaces
broken and line wrap damage. I've dumped a pile in my queue including
some pcmcia support for sh3 and the like
Note that pine 4.30 (shipped with Red Hat 7) has taken to stripping
trailing whitespace
[EMAIL PROTECTED] said:
This corruption still occurs in pine 4.32.
I should qualify that, just in case I'm actually lying.
s/^/As far as I can tell from a quick glance at the source, /
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Fri, 26 Jan 2001, Ookhoi wrote:
And unfortunately, the guy who mailed me didn't respond at my cry
for help, so now I try the list again. :-)
Sorry, try this patch.
Index: drivers/pcmcia/yenta.c
===
RCS file:
Er... no, don't try that patch. It'll oops. Try this instead.
--- drivers/pcmcia/yenta.c 2000/12/05 13:30:42 1.1.2.23
+++ drivers/pcmcia/yenta.c 2001/01/25 23:10:35
@@ -859,7 +859,8 @@
socket-tq_task.data = socket;
MOD_INC_USE_COUNT;
-
[EMAIL PROTECTED] said:
Please send additions and corrections to me and I'll try to keep it
updated.
Anything which uses sleep_on() has a 90% chance of being broken. Fix
them all, because we want to remove sleep_on() and friends in 2.5.
--
dwmw2
-
To unsubscribe from this list: send the
On Sun, 28 Jan 2001, Manfred Spraul wrote:
It isn't wrong to call schedule() with disabled interrupts - it's a
feature ;-)
Those 10% sleep_on() users that aren't broken use it:
for(;;) {
cli();
if(condition)
break;
sleep_on(my_wait_queue);
sti();
[EMAIL PROTECTED] said:
Is is intentional that tummy_task is not initialized?
It _is_ initialised. To zero :)
Ok, it won't crash because the current __run_task_queue()
implementation doesn't call tq-routine if it's NULL, but IMHO it's
ugly.
-static struct tq_struct dummy_task;
+static
[EMAIL PROTECTED] said:
Remember, most of you guys have been coding for years, or working on
the kernel for years. Some of us don't have that level of expertise,
are trying to get it, and feel like we're being told that information
is a private domain we aren't allowed in to.
Note that
[EMAIL PROTECTED] said:
A recent example I came across is in the MTD code which invokes the
erase algorithm for CFI memory. This algorithm spews a command
sequence to the flash chips followed by a list of sectors to erase.
Following each sector adress, the chip will wait for 50usec for
On Tue, 30 Jan 2001, Marcel J.E. Mol wrote:
Installed a Matrox G450 on my linux system. Now it has problems
booting.
Previously I had a matrox G400 card and that worked without any problems.
Below follows .config for the 2.4.0 kernel.
# CONFIG_FB_MATROX_G450 is not set
--
dwmw2
-
[EMAIL PROTECTED] said:
ftp cd gnu
ftp ls
ftp ls mak*
ftp bin
ftp get make-3.79.1.tar.gz
ftp get make-3.79.1.tar.gz
ftp exit
Try typing 'pwd' instead of 'exit' at the end of this script.
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
[EMAIL PROTECTED] said:
+ * This macro should be used for accessing values larger in size than single
+ * bytes at locations that may be improperly aligned, e.g. retrieving a u16
+ * value from a location not u16-aligned.
I'd suggest s/that may be/that are expected to be/
If it's _expected_,
[EMAIL PROTECTED] said:
We've identified several unchecked pointers using the Stanford checker
and have produced patches for them:
FTL (a memory card driver)
Patch applied to the master CVS, along with a cleanup on the immediately
subsequent malloc check too. It'll be in my next merge to
[EMAIL PROTECTED] said:
There wasn't even DHCP support before so yes you did. As you can't
get the nfs mount point from bootp.
Wasn't there a default? The Indy behind me seems to try to mount
/tftpboot/172.16.18.195, so I put a filesystem there just to make it happy.
It's a 2.4.3 kernel.
[EMAIL PROTECTED] said:
Andrea Arcangeli writes:
Related side note: for the x86-64 kernel we won't support the emulation
of the lvm ioctl from the 32bit executables to avoid the pointer
conversion an mainteinance pain enterely, at least in the early stage
the x86-64 lvmtools will
[EMAIL PROTECTED] said:
There is no reason why bdflush should call page_launder().
Its pretty obvious that bdflush's job is to only write out _buffers_.
Under my tests this patch makes things faster.
Oh good. ISTR last time I looked at implementing CONFIG_BLK_DEV I got as far
as trying
[EMAIL PROTECTED] said:
JFFS - dunno.
Bah. JFFS doesn't use any of those horrible block device thingies.
--
dwmw2
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
[EMAIL PROTECTED] said:
I'll take that as a vote for (b), to handle even perverse
configurations even if it means adding a lot of complexity to the
ruleset.
As long as the ruleset is sufficient to represent the desired parts of the
original behaviour of CML1, that should be fine.
Which
[EMAIL PROTECTED] said:
Why?
-- Forwarded message --
Some explanations/translations for these reports
can be found at:
http://www.zmailer.org/reports.html
- 550-Open relay - see http://www.orbs.org/verify.php3?address=212.153.111.69
- 550 mail from
[EMAIL PROTECTED] said:
I don't understand this request. I have no concept of `advisory'
dependencies. What are you talking about? Is my documentation
horribly unclear?
By 'dependency' I refer to the case where the value of one symbol is derived
entirely from, or the range of possible
[EMAIL PROTECTED] said:
There are no `advisory' dependencies in CML2. They're all absolute.
What you call an `advisory' dependency would be simulated by having a
policy symbol for Aunt Tillie mode and writing constraints like this:
require AUNT_TILLIE implies FOO = BAR
This is exactly
Thankyou for the clarification.
[EMAIL PROTECTED] said:
I used case 3 to explore a touchy question about design philosophy,
which is really what caused all hell to break loose. The question is
this: holding down configuration complexity is a good thing, but
supporting all hardware
[EMAIL PROTECTED] said:
Since you have to set the command line anyway ip=dhcp is no extra
burden and it lets you use the same kernel to boot of the harddrive
etc.
You don't have to set the command line anyway. At least you _didn't_.
[EMAIL PROTECTED] said:
I boot diskless all of time
[EMAIL PROTECTED] said:
I'm nervous that if we go down this path we will end up with a
thicket of modes and a combinatorial explosion in ruleset complexity,
leading immediately to a user configuration experience that is more
complex than necessary, and eventually to an unmaintainable mess
I can't see anything immediately wrong with your code - make sure you're
compiling against the source for the kernel you're running, with the same
options enabled.
In general, though, you shouldn't be using any of the sleep_on() functions
if you care about the fact that you'll miss wakeup
[EMAIL PROTECTED] said:
Maybe it would be possible to separate hard dependencies like the
current system has with the soft ones one needs for entry-level
configtools.
Actually, the current system has both types. As well as the hard
dependencies, we also have stuff like
[EMAIL PROTECTED] said:
What discussion is that? Unless Linus has changed his mind and I
don't know about it, CML2 is going in between 2.5.1 and 2.5.2.
Because it is evidently confusing the issue. Perhaps because it sounds like
you were intending to feed Linus large patches for 2.5.[12]
[EMAIL PROTECTED] said:
I can tell you haven't had to write any 32-bit ioctl emulation code
for a 64-bit kernel recently.
If that had been done right the first time, you wouldn't have had to either.
For that matter, it's often the case that if the ioctl had been done right
the first time,
[EMAIL PROTECTED] said:
I don't think there is a less contentious part. The same people who
bitched about the engine are now bitching about the changes I'm
contemplating in the rulesfiles. It seems clear to me that their
attitude, in general, has little to do with technical specifics of
[EMAIL PROTECTED] said:
Having now briefly looked at the language constructs first-hand, I
can see two ways to go about this:
1) Have a HACKER symbol which unsuppresses the unusual options, and
suppresses the generalised ones
2) Have a HACKERS submenu system which contains all the
[EMAIL PROTECTED] said:
David for the sake of the sanity of all concerned, do things one at a
David time. Provide for merging into 2.5 a set of rules which
David reproduce the existing CML1 behaviour in this respect.
Can you define what you mean here? It's not really clear to me, and I
[EMAIL PROTECTED] said:
I don't agree with this, since the current CML1 scheme has wierd,
unwanted and wrong dependencies already, which can't (or haven't) been
found. Since it would be put in during the 2.5.x branching, it's
expected that things will/can/should break, so I don't think
[EMAIL PROTECTED] said:
I want to know , is there any method to register ntfs file system
without recompiling the whole kernel
No, it is not possible to not recompile the kernel if NTFS was {not}
configured.
Is it not possible to build NTFS as a module?
--
dwmw2
-
To unsubscribe
[EMAIL PROTECTED] said:
1 | drivers/mtd/mtdchar.c
1 | fs/jffs/jffs_fm.c
2 | fs/jffs/intrep.c
1 | drivers/mtd/slram.c
1 | drivers/mtd/ftl.c
1 | drivers/mtd/mtdram.c
These are all now either fixed or obsoleted in my tree, and I
[EMAIL PROTECTED] said:
I'm trying to run jffs on my ATA-flash disk (running ext2 could kill
some flash cells too soon, right?) but it refuses:
CompactFlash does wear levelling internally.
if (MAJOR(dev) != MTD_BLOCK_MAJOR) {
printk(KERN_WARNING JFFS: Trying to
[EMAIL PROTECTED] said:
BTW the printk probably should be KERN_ERR, because this warning is
fatal.
Surely it's only fatal if it's the root filesystem, and the panic() message
on being unable to mount the root filesystem already has a higher loglevel?
--
dwmw2
-
To unsubscribe from this
[EMAIL PROTECTED] said:
There is this growing (think growing as in fungus) set of thinking
that just because something can be misused, this is an argument
against it even existing.
I think this is wrong. I'm seeing it a lot, especially on this list,
and it's becomming a real concern at
[EMAIL PROTECTED] said:
So you are constructing a improved NTFS file driver. So
when you have to check your written codes of file driver, will u
recompile the whole kernel ? . That is what I am asking. I am in a way
to build a new file system.
In general, it is not necessary
[EMAIL PROTECTED] said:
Now, a good way to force the issue may be to just remove the ioctl
function pointer from the file operations structure altogether. We
don't have to force peopel to use read/write - we can just make it
clear that ioctl's _have_ to be wrapped, and that the only ioctl's
[EMAIL PROTECTED] said:
I hate config options that change how the core of the kernel boot
makes decisions. Things like where is root, what is my network
address or where do I get that information have no reasonable
default. This is why the command line args are there.
If you're told (by
[EMAIL PROTECTED] said:
After using the 'map_user_kiobuf', I observed the followiing:
1. 'kiobuf-maplist[0]-virtual' contains a different virtual address than
the user space buffer address
2. But these two addresses are mapped as when i write something using the
address
[EMAIL PROTECTED] said:
I have a couple of user DMA drivers up and running, but in light of
your comment, I am not so sure.
I'm sorry, it seems I lied. Although map_user_kiobuf in 2.2 used to lock
the pages, apparently that's no longer necessary. You just need to make
sure they're marked
[EMAIL PROTECTED] said:
drivers/mtd/docprobe.c:195:DoC_Probe: ERROR:INIT: non-init fn
'DoC_Probe' calling init fn 'doccheck'
Strictly speaking, not actually a bug. DoC_Probe() itself is only ever
called from __init code. But it's probably not worth trying to make the
checker notice that
[EMAIL PROTECTED] said:
It's a space/performance bug, though, right? From the original mail:
1. The best case: the caller should actually be an __init function
as well. This is a performance bug since it won't be freed.
Yes, sorry. I hadn't properly read the beginning or
The flash mapping driver arch/cris/drivers/axisflashmap.c uses a cached
mapping of the flash chips for bulk reads, but obviously an uncached mapping
for sending commands and reading status when we're actually writing to or
erasing parts of the chip.
However, it fails to flush the dcache for the
[EMAIL PROTECTED] said:
I was pointed at Documentation/DMA-mapping.txt but that doesn't seem
very helpful - it's very PCI-specific, and a quick perusal of
pci_dma_sync() on i386 shows that it doesn't do what's required anyway.
What should it do on i386? mb()?
For it to have any use in
Who wants this?
invalid operand:
CPU:1
EIP:0010:[c0159975]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: 0039 ebx: cdfae6c0 ecx: c0288c4c edx: 0001
esi: c14b0c40 edi: ccd55c80 ebp: cf1a4560 esp: cb235e5c
ds: 0018 es: 0018 ss: 0018
My home directory lives on a SunOS 4.1.4 server, which helpfully expands
16-bit UIDs to 32 bits as signed quantities, not unsigned. So any uid above
32768 gets 0x added to it.
This patch adds a mount option to the Linux NFS client to work round this
brokenness. I haven't updated the
[EMAIL PROTECTED] said:
I'm sure that once the FSF is willing to step up, there will be lots
of supporters and sponsors to finance this.
Far smaller companies have _already_ got away with not only violating the
Linux kernel's GPL, but blatantly encouraging their customers to do so.
Why
[EMAIL PROTECTED] said:
nfs_file_cred() - nfs_create_request() - nfs_update_request() -
nfs_updatepage() - nfs_commit_write() - generic_file_write() -
nfs_file_write() - write(2).
Fscked credentials during write(2) on NFS...
Is this known and fixed, or just known?
--
dwmw2
-
To
[EMAIL PROTECTED] said:
- convert drivers to new PCI API
Don't bother with drivers/char/applicom.c - I've already done it, just
waiting to borrow the hardware again to test it.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Fri, 8 Sep 2000, Andrew Burgess wrote:
Oops from 2.2.17 (some more before this, but it went offscreen):
...
You need to capture and decode the first oops. Compile a kernel with a
serial console and capture the oops log on a second machine.
Or set your console for more than 80x25
[EMAIL PROTECTED] said:
I have to admit, the thought hadn't occurred to me to do that. It
almost sounds like a good idea... after all the stub can't be used if
no modules can be loaded. Are you thinking, then, that the stub can't
be used by compiled in (ie non-module) code? Or am I
[EMAIL PROTECTED] said:
Ah... I did misunderstand you. I thought you meant CONFIG_MODULES in
general, which'd be okay - obviously, if module support is disabled,
you can't load a module anyway.
Well actually, that's not strictly true. But it is fair to say that if
you're hacking new code
[EMAIL PROTECTED] said:
But where do I get the other argument (struct pt_regs *) from? A
normal Linux syscall does not appear to have access to such a beast...
With difficulty. A normal syscall wouldn't generally go through the lcall7
handler. Some of the ABI/iBCS code gets access to the
[EMAIL PROTECTED] said:
I didn't know how to get hold of a "struct pt_regs*" till someone sent
me a message this morning
Ah. I didn't realise you wanted the struct pt_regs for any purpose other
than to pass to the lcall7 handler - and I was no longer using the lcall7
handler in the
[EMAIL PROTECTED] said:
Note that with most versions of gcc this is all a complete non-issue,
as most versions of gcc will _always_ inline a function that the user
has asked to be inlined. So the issue seldom actually comes up.
I thought that 'extern inline' was in fact the intended usage.
[EMAIL PROTECTED] said:
Linus,
Where do architecture maintainers stand when they don't submit their
problems to linux-kernel or the great Ted Bug List(tm)?
Up against the wall so we can shoot them?
:)
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
[EMAIL PROTECTED] said:
I tried it with two compilers, one older than yours and one newer:
In both cases, the memory read occurs before "zzz".
[EMAIL PROTECTED] said:
I guess Alexey point is that the current compiler doesn't notice
that.
I don't understand why we're bringing empirical
[EMAIL PROTECTED] said:
I think its fixable to make it do the RR/RNR after bouncing it up the
stack. -
ARCnet does ACK in hardware. Packets don't hit the wire until the
destination has indicated that it's got a buffer available.
You really want to be able to reserve space on the queue
[EMAIL PROTECTED] said:
Okay, twice this evening I've seen my 2.2.16-kernel based i586 (K6-2)
machine become ignorant of the utility of eth0. Both times I'd been
playing mp3 audio on another linux box from an NFS volume served by
the machine that went nuts.
Let me guess - eth0 is a tulip
On Fri, 6 Oct 2000, Andre Hedrick wrote:
void go_take_a_dump (float load)
{
if (pull_down_pants() purge_bowles() wipe_anus() pull_up_pants())
flush(load);
else
wear(load);
}
But here you make another classic mistake. Consider the case where
purge_bowels() fails
* USB: system hang with USB audio driver {CRITICAL} (David
Woodhouse, Randy Dunlap, Narayan Desai)
This is necessary but not sufficient:
Index: drivers/usb/audio.c
===
RCS file: /net/passion/inst/cvs/linux/drivers
On Thu, 12 Oct 2000, David Woodhouse wrote:
* USB: system hang with USB audio driver {CRITICAL} (David
Woodhouse, Randy Dunlap, Narayan Desai)
That fixes failure mode #1, in which the NMI watchdog gets triggered and
all subsequent attempts to open /dev/audio just block
[EMAIL PROTECTED] said:
Do we have any [non-kernel] software that will read/analyze MPS
tables?
I believe there's a port of http://people.freebsd.org/~fsmp/SMP/mptable/
somewhere. It's probably quicker to port it again yourself than search for
it.
--
dwmw2
-
To unsubscribe from this
[EMAIL PROTECTED] said:
The 'C' language can order structure members anyway it wants. It also
can add any 'fill' or alignment bytes it wants. The compiler is not
broken in this respect.
Anyone who's been following this list for a while will know not to take any
notice of Dick, especially
[EMAIL PROTECTED] said:
I've found a few inconsistencies with the wording of some license
statements refering to "GNU public license" and similar, and have
reworded them properly to "GNU General Public License".
If we're referring to it by name, we probably ought to call it the
'GNU General
ftp.uk.linux.org:/pub/people/dwmw2/pcsp/patch-pcsp-soundcore-2.4.0-test10-pre3
Thanks to Erik Inge Bolsø for porting it to 2.3.45, this saving me most of
the work.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
1 - 100 of 4023 matches
Mail list logo