Dan Kegel <[EMAIL PROTECTED]> writes:
> It's harder to write correct programs that use edge-triggered events.
Huh? The race between when an event is reported, and when you take action
on it effectively means all events are edge triggered.
So making the interface clearly edge triggered seems t
I'm using 2.4.0-test10-pre5 on a PIII (compiled with gcc 2.7.2.3) and
having problems with usb. I'm able to load the usb-driver (usb-uhci) and
then the driver for my usb-webcam (cpia_usb). The webcam works fine for
something like 20 minutes. After that I start to get this kind of messages
to the
Anil kumar wrote:
>
> Hi,
> After I create a RAID setup on the drives,The
> superblock will be generated at the end of the drives.
> If I move these drives to other linux system, will
> this
> system recognise the RAID setup without reconfiguring
> the Linux ?
>
Yes - if that other linux syste
Hi Jeff!
> First, some definitions:
> downstream - away from the host processor
> primary - number of the PCI bus closer to the host processor
> secondary - number of the PCI bus on the downstream side of the PCI
> bridge
> subordinate - number of the highest-numbered bus on the downstream side
>
Jonathan Lemon wrote:
>
> Also, consider the following scenario for the proposed get_event():
>
>1. packet arrives, queues an event.
>2. user retrieves event.
>3. second packet arrives, queues event again.
>4. user reads() all data.
>
> Now, next time around the loop, we get a n
On 23 Oct 2000, Patrick J. LoPresti wrote:
> If you send SIGSTOP to syslogd on a Red Hat 6.2 system (glibc 2.1.3,
> kernel 2.2.x), within a few minutes you will find your entire machine
> grinds to a halt. For example, nobody can log in.
>
> This happens because once the /dev/log buffer fills,
On Wed, Oct 25, 2000 at 05:59:39PM -0400, Jeff Garzik wrote:
> It may work, but the bridge secondary/subordinate numbers look wrong.
>
No, these numbers look correct for me. Read comment in drivers/pci/pci.c:
if (!is_cardbus) {
/* Now we can scan all subordinate buses... *
> You obviously don't understand the communication channel being used.
> "/dev/log" is a UNIX DOMAIN SOCKET -- AF_UNIX. Datagrams are unreliable
> for _IP_ (AF_INET). Traffic on an AF_UNIX socket is always reliable.
>
> Ok, smarty, go change the syslogd source to open /dev/log as SOCK_STREAM
>
"Pasi Kärkkäinen" wrote:
>
> I'm using 2.4.0-test10-pre5 on a PIII (compiled with gcc 2.7.2.3) and
> ...
gcc-2.7.2.3 miscompiles kernel/module.c and it has been decided that
this will not be worked around. The new baseline gcc release for x86
is gcc-2.91.66 (otherwise known as egcs-1.1.2).
-
To
> Ulrich Drepper <[EMAIL PROTECTED]> writes:
>
> > If anything has to be changed it's (as suggested) the configuration
> > or even the implementation of syslogd. Make it robust.
>
> OK, but my current syslogd only listens to /dev/log as a SOCK_DGRAM.
> If I wanted reliable syslogging, it would
On 23 Oct 2000, Patrick J. LoPresti wrote:
> Jesse Pollard <[EMAIL PROTECTED]> writes:
>
> > Don't configure syslogd to do reverse lookups.
>
> Our syslogd has no option to disable the reverse lookups.
Requires a recompile.
> > You can NEVER guarantee that the reverse lookup will succeed, and
Hi,
I was having some little trouble with the QLOGIC Fibre Channel SCSI
cards.
The issue is, that I have a box with an internal SCSI controller/disk
and
a QLOGIC card which is connected to an external RAID. The probelm is,
that the internal disk is my root disk but is the second in the chain
(s
Hi,
This bug was triggered by trying ctrl-alt-del for reboot in
test10-pre5. It appears to show schedule() getting stuck in
a loop with the stack growing unbounded.
Unfortunately, the module list and symbols are not exposed.
I don't know what had been unloaded before the bug
triggered. The initi
On Thu, 26 Oct 2000, Klaus Naumann wrote:
> I was having some little trouble with the QLOGIC Fibre Channel SCSI
> cards.
> The issue is, that I have a box with an internal SCSI controller/disk
> and a QLOGIC card which is connected to an external RAID. The probelm
> is, that the internal disk is
> No, I didn't say they "should" be dropped but merely that dropping them
> would fix your problem. Personally, I'd look closely at your setup to
> determine exactly why this has become a problem. named is being blocked
> on writing to /dev/log. This should only happen if there is sufficient
>
> Perhaps syslogd is not giving higher priority to local messages; if it
> did, maybe it could recover from the deadlock. But this would not be
> a reliable solution; the only reliable solution is for syslogd to be
> independent of any processes which need to talk to it.
In that case, don't do
On Thu, 26 Oct 2000, Andrew Morton wrote:
> "Pasi Kärkkäinen" wrote:
> >
> > I'm using 2.4.0-test10-pre5 on a PIII (compiled with gcc 2.7.2.3) and
> > ...
>
> gcc-2.7.2.3 miscompiles kernel/module.c and it has been decided that
> this will not be worked around. The new baseline gcc release fo
Byeong-ryeol Kim wrote:
>
> On Thu, 26 Oct 2000, Klaus Naumann wrote:
>
> > I was having some little trouble with the QLOGIC Fibre Channel SCSI
> > cards.
> > The issue is, that I have a box with an internal SCSI controller/disk
> > and a QLOGIC card which is connected to an external RAID. The p
On Wed, 25 Oct 2000, Anil kumar wrote:
> Hi,
> After I create a RAID setup on the drives,The
> superblock will be generated at the end of the drives.
> If I move these drives to other linux system, will
> this
> system recognise the RAID setup without reconfiguring
> the Linux ?
If the CHS / L
>
>Yes, it will break on any machine with multiple primary PCI busses, because
>the registers assigning bus number ranges to primary busses are chipset
>specific.
>
>In 2.5, I'd like to rewrite the resource + bus number assignment code to be
>able to re-layout the busses and resources even on i386
On Thu, 26 Oct 2000 14:22:54 +0200,
Klaus Naumann <[EMAIL PROTECTED]> wrote:
>The problem with that is that on boot up (for lilo) the internal disk
>is disk number one. But when I'm in the system and want to install lilo
>it's disk number two - that's what lilo is complaining about on boot up.
>(
I recently installed 2.4test9pre5 and noticed that when I cat
/proc/meminfo the value for shared memory is 0. Am I the only one that
is seeing this.
Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ a
You can use an initial ramdisk (initrd), and specify the load order of your
drivers (driver for internal disk first, qlogic driver second). That
removes the dependency on the static link order in hosts.c.
Thanks,
Matt
-Original Message-
From: Klaus Naumann [mailto:[EMAIL PROTECTED]]
Sen
"Pasi Kärkkäinen" wrote:
>
> Ok. I recompiled the kernel and modules with 2.95.2 and it still seems not
> to work. This is from syslog:
>
> __alloc_pages: 2-order allocation failed.
> __alloc_pages: 2-order allocation failed.
> __alloc_pages: 5-order allocation failed.
> __alloc_pages: 4-order a
Hi,
I got the following OOPS while doing some heavy compilations (make -j4) on dual SMP
P-III,
2.4.0-test10-pre5 and reiserfs 3.6.18 for 2.4.0-test9.
It looks like page without page->mapping has been passed to
block_read_full_page().
Unable to handle kernel NULL pointer dereference at virtua
On Thu, 26 Oct 2000, Albert D. Cahalan wrote:
> Richard B. Johnson writes:
> > On Sun, 22 Oct 2000, Dwayne C . Litzenberger wrote:
>
> > o Once installed, a kernel module is every bit as "efficient"
> > as some driver linked into the kernel at build-time. Of course
>
> I doubt this is true on
Stephen Clark wrote:
>
>I recently installed 2.4test9pre5 and noticed that when I cat
>/proc/meminfo the value for shared memory is 0. Am I the only one that
>is seeing this.
I'm seeing this also for 2.4.0-test10-pre5. Here is /proc/meminfo followed
by the same for a 2.2 machine running the same
Hi!
I've found a bug in my VIA SuperSouth (vt82c686a) chip (ISA bridge
revision 0x12, silicon rev CD) on my FIC VA-503A rev 1.2:
When there is heavy disk activity (several tars running concurrently on
UDMA66 drive, or tar'ing from one UDMA66 drive to another over two
channels), the system time,
Hi,
i hope i am right here, and this problem wasn't mailed a thousand times
before - but it is not older than 3 days (2.4.0-test10-pre5 is'nt
older...)
I am playing around with usb and usb-storage, and then i wanted to reload
the usb-ohci-module, during the insmod i got this error:
Oct 26 15:11:
On Thu, Oct 26, 2000 at 07:25:34AM -0600, Steven Cole wrote:
> Stephen Clark wrote:
> >
> >I recently installed 2.4test9pre5 and noticed that when I cat
> >/proc/meminfo the value for shared memory is 0. Am I the only one that
> >is seeing this.
>
> I'm seeing this also for 2.4.0-test10-pre5. He
Hi Linus,
in the current kernel versions we have a lot of new list-style makefiles
(find -name Makefile | xargs grep -l obj- | wc -l gives 48 in -pre5) and
the number increases all the time.
This patch adds a new makefile ($(TOPDIR])/Makefile.inc) that can be
included by the list-style makefiles,
Vojtech Pavlik <[EMAIL PROTECTED]> writes:
> Hi!
>
> I've found a bug in my VIA SuperSouth (vt82c686a) chip (ISA bridge
> revision 0x12, silicon rev CD) on my FIC VA-503A rev 1.2:
>
> When there is heavy disk activity (several tars running concurrently on
> UDMA66 drive, or tar'ing from one UDM
On Thu, 26 Oct 2000 23:52:02 +1100,
Andrew Morton <[EMAIL PROTECTED]> wrote:
>[ You could put a show_stack(0) in here, but I believe ksymoops
> doesn't understand show_stack() output ].
It does, and extracts the "Call Trace:" data. The stack is not printed
by ksymoops because it does not have
On Thu, 26 Oct 2000 09:17:49 -0400 (EDT),
"Richard B. Johnson" <[EMAIL PROTECTED]> wrote:
>On Thu, 26 Oct 2000, Albert D. Cahalan wrote:
>> I doubt this is true on most modern processors. On the Pentium
>> and above, large pages are used for the kernel. The PowerPC port
> ^^^
Hello,
I'm unable to boot kernel 2.4.0-test10-pre5 on a:
root@cyrix:/usr/src/linux/arch/i386/mm# cat /proc/cpuinfo
processor : 0
vendor_id : CyrixInstead
cpu family : 6
model : 2
model name : 6x86MX 2.5x Core/Bus Clock
stepping: 7
cpu MHz : 166.
On Thu, 26 Oct 2000 15:39:59 +0200 (CEST),
Christian Reiser <[EMAIL PROTECTED]> wrote:
> kernel BUG at slab.c:804!
>Code: 0f 0b 83 c4 0c 8d b4 26 00 00 00 00 8b 1b 81 fb bc 23 26 c0
>... hope it could help ...
Almost completely useless until you follow the procedures in
linux/REPORTING-BUGS.
On Thu, Oct 26, 2000 at 03:58:21PM +0200, Yoann Vandoorselaere wrote:
> > I've found a bug in my VIA SuperSouth (vt82c686a) chip (ISA bridge
> > revision 0x12, silicon rev CD) on my FIC VA-503A rev 1.2:
> >
> > When there is heavy disk activity (several tars running concurrently on
> > UDMA66 dr
Vojtech Pavlik <[EMAIL PROTECTED]> writes:
> On Thu, Oct 26, 2000 at 03:58:21PM +0200, Yoann Vandoorselaere wrote:
>
> > > I've found a bug in my VIA SuperSouth (vt82c686a) chip (ISA bridge
> > > revision 0x12, silicon rev CD) on my FIC VA-503A rev 1.2:
> > >
> > > When there is heavy disk acti
On Thu, Oct 26, 2000 at 04:13:51PM +0200, Yoann Vandoorselaere wrote:
> > > > I've found a bug in my VIA SuperSouth (vt82c686a) chip (ISA bridge
> > > > revision 0x12, silicon rev CD) on my FIC VA-503A rev 1.2:
> > > >
> > > > When there is heavy disk activity (several tars running concurrently
On Thu, 26 Oct 2000, Mircea Damian wrote:
>
>
> Hello,
>
> I'm unable to boot kernel 2.4.0-test10-pre5 on a:
>
>
> And here is the broken routine:
>
> 03f4 :
> 3f4: 8b 44 24 04 movl 0x4(%esp,1),%eax
> 3f8: b9 01 00 00 00 movl $0x1,%ecx
> 3fd: 8a 10
++ 26/10/00 16:11 +0200 - Vojtech Pavlik:
> On Thu, Oct 26, 2000 at 04:13:51PM +0200, Yoann Vandoorselaere wrote:
>
> > > > > I've found a bug in my VIA SuperSouth (vt82c686a) chip (ISA bridge
> > > > > revision 0x12, silicon rev CD) on my FIC VA-503A rev 1.2:
> > > > >
> > > > > When there is h
Mircea Damian wrote:
>
> Hello,
>
> I'm unable to boot kernel 2.4.0-test10-pre5 on a:
Upgrade GCC to 2.91.66 (aka egcs-1.1.2)
--
Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Thu, Oct 26, 2000 at 02:57:30PM +0300, Pasi Kärkkäinen wrote:
>
> On Thu, 26 Oct 2000, Andrew Morton wrote:
>
> > "Pasi Kärkkäinen" wrote:
> >
> > gcc-2.7.2.3 miscompiles kernel/module.c and it has been decided that
> > this will not be worked around. The new baseline gcc release for x86
> >
"Richard B. Johnson" wrote:
> Stand-alone, it can't do anything useful. However, if it generates
> a page-fault due to the read or write, the page-fault handler could
> do "something". Currently, the fault it fatal, probably because
> the passed pointer is invalid.
The write-protect test code is
Richard B. Johnson wrote:
> > And here is the broken routine:
> >
> > 03f4 :
[...]
> This is not good code. It does the following:
>
> o Gets a parameter off the stack and puts into eax (a pointer).
> o Put the value 1 into ecx.
> o Take a byte from the pointed-to location and pu
Then shouldn't it be removed?
Craig Schlenter wrote:
> On Thu, Oct 26, 2000 at 07:25:34AM -0600, Steven Cole wrote:
> > Stephen Clark wrote:
> > >
> > >I recently installed 2.4test9pre5 and noticed that when I cat
> > >/proc/meminfo the value for shared memory is 0. Am I the only one that
> > >i
On Thu, 26 Oct 2000, Brian Gerst wrote:
> "Richard B. Johnson" wrote:
> > Stand-alone, it can't do anything useful. However, if it generates
> > a page-fault due to the read or write, the page-fault handler could
> > do "something". Currently, the fault it fatal, probably because
> > the passed p
On Thu, Oct 26, 2000 at 10:40:33AM -0400, Stephen Clark wrote:
[/proc/meminfo shared is 0]
> Then shouldn't it be removed?
Probably not. There may be tools that rely on it existing that may break
if it goes away altogether.
Maybe 'free' does for example.
--C
-
To unsubscribe from this list: sen
Marc Schneider wrote:
>
> msgsnd seems to be corrupting memory around the msgbuf pointer.
>
> for example I have the following code:
>
> pMsgBuf = malloc(iPacketLen + 4 + 8);
> bzero(pMsgBuf, iPacketLen + 4 + 8);
> pMsgBuf += 4; /* Build a guard band */
>
> printf("PMQ:pMsgBuf: %p\n",pMsgBuf);
That makes sense.
Steve
Craig Schlenter wrote:
> On Thu, Oct 26, 2000 at 10:40:33AM -0400, Stephen Clark wrote:
> [/proc/meminfo shared is 0]
> > Then shouldn't it be removed?
>
> Probably not. There may be tools that rely on it existing that may break
> if it goes away altogether.
>
> Maybe 'f
[EMAIL PROTECTED] wrote:
>
> Marc Schneider wrote:
> >
> > msgsnd seems to be corrupting memory around the msgbuf pointer.
> >
> > for example I have the following code:
> >
> > pMsgBuf = malloc(iPacketLen + 4 + 8);
> > bzero(pMsgBuf, iPacketLen + 4 + 8);
> > pMsgBuf += 4; /* Build a guard band *
Hi All,
I built the kernel on RedHat Linux 7 after configuring
the build (make menuconfig) for SMP kernel.
After installing the kernel (copy bzImage to /boot directory
and run lilo) I rebooted the system to run the new kernel.
Then I looked at the /proc/ksyms file to see if the
symbol names are p
On Wed, 25 Oct 2000, Roger Larsson wrote:
> I noted that even try_to_free_buffers locks lru_list_lock.
lru_list_lock != pagemap_lru_lock
cheers,
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.s
>
>ftp://ftp.kernel.org/pub/people/andrea/patches/v2.2/2.2.18pre17/VM-global-2.2.18pre17-7.bz2
> > eth0: card reports no resources
> > VFS: file-max limit 4096 reached
> > Kernel panic: VFS: LRU block list corrupted.
> > Kernel panic: VFS: LRU block list corrupted.
> > Kernel panic: VFS: LRU bloc
I realize all of this is 2.5 material.
We had been talking about this earlier, until Viro and Cox told us to
quit until 2.5.
Alexander Viro wrote:
>
> It goes off-list.
But, in light of Andreas Gruenbacher's proposal
(http://lwn.net/2000/1026/a/extended-attributes.php3) and Stephen
Tweedie'
Igmar Palsenberg <[EMAIL PROTECTED]> writes:
> On 23 Oct 2000, Patrick J. LoPresti wrote:
>
> > Not true. The named on our loghost is authoritative for the reverse
> > mappings for all of the machines which can log there.
>
> Put the names of your machines in /etc/hosts on your logmachine.
Thi
On Thu, 26 Oct 2000, Rik van Riel wrote:
> On Wed, 25 Oct 2000, Roger Larsson wrote:
>
> > I noted that even try_to_free_buffers locks lru_list_lock.
>
> lru_list_lock != pagemap_lru_lock
>
btw, while we are at it, I am not able to reproduce this with test10-pre5
but am still running tests wi
ksymoops 2.3.4 on i686 2.4.0-test10. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test10/ (specified)
-m /usr/src/linux/System.map (default)
Error (regular_file): read_system_map stat /usr/src/linux/System.map failed
On Thu, Oct 26, 2000 at 04:04:16PM +0100, Mark Cooke wrote:
> On 26 Oct 2000, Yoann Vandoorselaere wrote:
>
> > This is an athlon 750 machine, with scsi and ide a disk...
> > I've tryed to see where the problem was comming from for age
> > ( the problem is what you describe and it happen after s
On Thu, 26 Oct 2000, Stephen Rothwell wrote:
>
> OK, I include below a more or less translation for 2.4. I have not even
> compiled this, and have not got the hardware to test it anyway.
I disagree violently with doing this in the low-level drivers.
If it cannot be done in user space (which
On Thu, Oct 26, 2000 at 04:42:31PM +0200, Yoann Vandoorselaere wrote:
> > On Thu, Oct 26, 2000 at 04:20:43PM +0200, Yoann Vandoorselaere wrote:
> >
> > > ...
> > >
> > > Have you any idea what is the relation between time and this chip ?
> > >
> > > Also, I'm experiencing the problem for sever
Hi,
I have the same problem.
On Thu, 26 Oct 2000, Vojtech Pavlik wrote:
[...snip...]
> Could you send me your 'lspci -vvxxx' to confirm it's the very same
> chip?
00:07.0 ISA bridge: VIA Technologies, Inc.: Unknown device 0686 (rev 21)
Subsystem: Unknown device 1106:
Contr
Vojtech Pavlik <[EMAIL PROTECTED]> writes:
> On Thu, Oct 26, 2000 at 04:42:31PM +0200, Yoann Vandoorselaere wrote:
>
> > > On Thu, Oct 26, 2000 at 04:20:43PM +0200, Yoann Vandoorselaere wrote:
> > >
> > > > ...
> > > >
> > > > Have you any idea what is the relation between time and this chip ?
On Thu, 26 Oct 2000, Andrea Arcangeli wrote:
> On Wed, Oct 25, 2000 at 02:46:19PM -0400, Doug Ledford wrote:
> > I've made a few correctness changes to this code. Items that needed to be
> > corrected for include the facts that the XMM feature bit is an Intel specific
> > bit that other vendor
On Thu, 26 Oct 2000, Igmar Palsenberg wrote:
>> Per chance are you running the name service caching daemon (nscd)? I'd
>> also guess you aren't disabling fsync() for your sysylog files (it's part
>> of the syslog.conf format) -- this is a conciderable drain on syslogd.
>
>Agree. It is there for a
Keith Owens <[EMAIL PROTECTED]>:
>
> On Thu, 26 Oct 2000 09:17:49 -0400 (EDT),
> "Richard B. Johnson" <[EMAIL PROTECTED]> wrote:
[snip]
> >This shows that out of 34,678 bytes we needed, we wasted 6282, ~1.5
> >pages. Since there are 5 modules, we waste about 1/3 page per module.
> >
> >So I don'
On 26 Oct 2000, Yoann Vandoorselaere wrote:
> Vojtech Pavlik <[EMAIL PROTECTED]> writes:
[Snipped...]
../drivers/block/ide.c, line 162, on version 2.2.17 does bad things
to the timer. It writes 0 to the control-word for timer 0. This
does the following:
o Selects timer 0.
o Latches t
> "christian" == Christian Reiser <[EMAIL PROTECTED]> writes:
christian> Hi,
christian> i hope i am right here, and this problem wasn't mailed a thousand times
christian> before - but it is not older than 3 days (2.4.0-test10-pre5 is'nt
christian> older...)
christian> I am playing around with
> > Hi,
> > After I create a RAID setup on the drives,The
> > superblock will be generated at the end of the drives.
> > If I move these drives to other linux system, will
> > this
> > system recognise the RAID setup without reconfiguring
> > the Linux ?
>
> If the CHS / LBA settings are the sa
"Eric W. Biederman" wrote:
>
> Dan Kegel <[EMAIL PROTECTED]> writes:
> > It's harder to write correct programs that use edge-triggered events.
>
> Huh? The race between when an event is reported, and when you take action
> on it effectively means all events are edge triggered.
Nope. With any o
On Thu, Oct 26, 2000 at 10:20:45AM -0400, Brian Gerst wrote:
> Mircea Damian wrote:
> >
> > Hello,
> >
> > I'm unable to boot kernel 2.4.0-test10-pre5 on a:
>
> Upgrade GCC to 2.91.66 (aka egcs-1.1.2)
Ok. I can do that, but there is nowhere written that I should do
that. If I remember right gc
octave klaba wrote:
>
> >
>ftp://ftp.kernel.org/pub/people/andrea/patches/v2.2/2.2.18pre17/VM-global-2.2.18pre17-7.bz2
> > > eth0: card reports no resources
> > > VFS: file-max limit 4096 reached
> > > Kernel panic: VFS: LRU block list corrupted.
> > > Kernel panic: VFS: LRU block list corrupted
> > Oct 26 16:38:01 ns29 kernel: eth0: card reports no resources.
> let me guess: intel eepro100 or similar??
yeap
00:02.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08)
Subsystem: Asustek Computer, Inc.: Unknown device 1043
Control: I/O+ Mem+ BusMaster
Hello,
I didn't see this posted yet, so I have attached it below. If it has, sorry in
advance. I have gcc 2.8.1 , and the kernel version is : test10-5
Regards,
Frank
During make modules
...
af_irda.o : In function 'cleanup_module' :
af_irda.o(.text+0x3e90): multiple definition of 'cleanup
Markus Pfeiffer <[EMAIL PROTECTED]> wrote:
>
> > Oct 26 11:24:13 ns29 kernel: eth0: card reports no resources.
> > Oct 26 11:24:15 ns29 kernel: eth0: card reports no resources.
> > Oct 26 12:22:21 ns29 kernel: eth0: card reports no resources.
> > Oct 26 16:16:59 ns29 kernel: eth0: card reports no
On Thu, 26 Oct 2000, Dan Kegel wrote:
>
> With level-triggered interfaces like poll(), your chances
> of writing a correctly functioning program are higher because you
> can throw events away (on purpose or accidentally) with no consequences;
> the next time around the loop, poll() will happil
On Thu, Oct 26, 2000 at 02:16:28AM -0700, Gideon Glass wrote:
> Jonathan Lemon wrote:
> >
> > Also, consider the following scenario for the proposed get_event():
> >
> >1. packet arrives, queues an event.
> >2. user retrieves event.
> >3. second packet arrives, queues event again.
>
On Thu, Oct 26, 2000 at 12:04:21PM -0400, Richard B. Johnson wrote:
> ../drivers/block/ide.c, line 162, on version 2.2.17 does bad things
> to the timer. It writes 0 to the control-word for timer 0. This
> does the following:
>
> o Selects timer 0.
> o Latches the timer.
> o Selects
LT,
I can do it from user-space completely, but not today.
The tools are missing.
Also I have/will get my traces on my code in a day or so.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Mircea Damian wrote:
>
> On Thu, Oct 26, 2000 at 10:20:45AM -0400, Brian Gerst wrote:
> > Mircea Damian wrote:
> > >
> > > Hello,
> > >
> > > I'm unable to boot kernel 2.4.0-test10-pre5 on a:
> >
> > Upgrade GCC to 2.91.66 (aka egcs-1.1.2)
>
> Ok. I can do that, but there is nowhere written that
On Thu, 26 Oct 2000, Forever shall I be. wrote:
> On Thu, Oct 26, 2000 at 02:57:30PM +0300, Pasi Kärkkäinen wrote:
> > __alloc_pages: 2-order allocation failed.
> > __alloc_pages: 2-order allocation failed.
> > __alloc_pages: 5-order allocation failed.
> > __alloc_pages: 4-order allocation failed
On Thu, 26 Oct 2000, Rik van Riel wrote:
> On Thu, 26 Oct 2000, Forever shall I be. wrote:
> > On Thu, Oct 26, 2000 at 02:57:30PM +0300, Pasi Kärkkäinen wrote:
>
> > > __alloc_pages: 2-order allocation failed.
> > > __alloc_pages: 2-order allocation failed.
> > > __alloc_pages: 5-order allocati
Andrea Arcangeli writes ("Re: linux 2.2.18-pre17: "Kernel panic: LRU list corrupted""):
> I also included the fix in a new VM-global patch against vanilla 2.2.18pre17
> (the VM-global patch is available as a single patch inside 2.2.18pre17aa1/
> directory too but I have to maintain a separate vers
On Thu, 26 Oct 2000, Vojtech Pavlik wrote:
> On Thu, Oct 26, 2000 at 12:04:21PM -0400, Richard B. Johnson wrote:
>
> > ../drivers/block/ide.c, line 162, on version 2.2.17 does bad things
> > to the timer. It writes 0 to the control-word for timer 0. This
> > does the following:
[Snipped...]
>
On Thu, 26 Oct 2000, Robert Lynch wrote:
> Oct 19 13:00:23 ives kernel: EIP:0010:[try_to_swap_out+252/796]
Those Oopsen look like they're from test10-pre4 (fixed in pre5). Also,
please include the lines beginning with "kernel BUG at...".
-ben
-
To unsubscribe from this lis
On Thu, Oct 26, 2000 at 01:42:29PM -0400, Richard B. Johnson wrote:
> > > ../drivers/block/ide.c, line 162, on version 2.2.17 does bad things
> > > to the timer. It writes 0 to the control-word for timer 0. This
> > > does the following:
> [Snipped...]
> >
> > Well, at least on 2.4.0-test9, the
This is a long posting, with a humble beginning, but it has
a point. I'm being complete so that no one is left in the
dark, or in any doubt as to what that point is. That means
rehashing some history.
This posting is not really about select or Linux: it's about
interfaces. Like cached state, i
Andi Kleen <[EMAIL PROTECTED]>:
> On Thu, Oct 26, 2000 at 11:00:03AM -0500, Jesse Pollard wrote:
> > Keith Owens <[EMAIL PROTECTED]>:
> > >
> > > On Thu, 26 Oct 2000 09:17:49 -0400 (EDT),
> > > "Richard B. Johnson" <[EMAIL PROTECTED]> wrote:
> > [snip]
> > > >This shows that out of 34,678 bytes
Hi Heinz,
it looks like the LVM snapshotting in 2.4 doesn't allow you
to create snapshots from anything else than the _first_ LV
in the VG...
I have run both the following command lines (after lvremoving
snap1, of course) and both of them give as a result that the
LV /dev/test_vg/swap ends up be
[EMAIL PROTECTED] wrote:
>
> On Thu, 26 Oct 2000, Robert Lynch wrote:
>
> > Oct 19 13:00:23 ives kernel: EIP:0010:[try_to_swap_out+252/796]
>
> Those Oopsen look like they're from test10-pre4 (fixed in pre5). Also,
> please include the lines beginning with "kernel BUG at...".
>
>
Linus, Alan,
I am proposing this patch for inclusion in the 2.2.x tree. (Whether it goes
into 2.2.18 or 2.2.19 is your call.) We have run this successfully with
2.2.14 through 2.2.17.
Our kernel patches help stacking file systems work properly in two
areas:
* dentry reference count fixes when
On Thu, Oct 26, 2000 at 06:21:29PM +0200, octave klaba wrote:
>
>
> > > Oct 26 16:38:01 ns29 kernel: eth0: card reports no resources.
> > let me guess: intel eepro100 or similar??
> yeap
>
> 00:02.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08)
> Subsystem: As
Note that there is another aspect to the efficiency / performance of the
select/poll style of interfaces not immediately obvious, but which occurs
as a result of how some (streaming/batching) protocols work.
An X server does not call select all that often (probably one of the two items most
f
Vojtech Pavlik <[EMAIL PROTECTED]> writes:
> On Thu, Oct 26, 2000 at 01:42:29PM -0400, Richard B. Johnson wrote:
>
> > > > ../drivers/block/ide.c, line 162, on version 2.2.17 does bad things
> > > > to the timer. It writes 0 to the control-word for timer 0. This
> > > > does the following:
> > [
On Thu, Oct 26, 2000 at 10:11:54PM +0200, Yoann Vandoorselaere wrote:
> > > > > ../drivers/block/ide.c, line 162, on version 2.2.17 does bad things
> > > > > to the timer. It writes 0 to the control-word for timer 0. This
> > > > > does the following:
> > > [Snipped...]
> > > >
> > > > Well, at
On Thu, 26 Oct 2000, Rik van Riel wrote:
> it looks like the LVM snapshotting in 2.4 doesn't allow you
> to create snapshots from anything else than the _first_ LV
> in the VG...
OK, I reproduced it in 2.2 as well ... ;(
> I have run both the following command lines (after lvremoving
> snap1, o
On Wed, 25 Oct 2000, Alexander Viro wrote:
>
> Linus, what do you think about that? I can do the remaining filesystems
> and give it initial testing today.
Ok, looks reasonable, if not really pretty. I'd probably prefer
last_page = size >> PAGE_CACHE_SIZE;
last_page_size = siz
> cpu family : 5
> model : 8
> model name : AMD-K6(tm) 3D processor
> ^^
>
> Shouldn't it be K6-2?
We report what AMD report
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please re
Vojtech Pavlik <[EMAIL PROTECTED]> writes:
> On Thu, Oct 26, 2000 at 10:11:54PM +0200, Yoann Vandoorselaere wrote:
>
> > > > > > ../drivers/block/ide.c, line 162, on version 2.2.17 does bad things
> > > > > > to the timer. It writes 0 to the control-word for timer 0. This
> > > > > > does the fo
kernel.org is back up.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
1 - 100 of 155 matches
Mail list logo
