It seems as if recent kernles don't cache floppy reads. Is this
intentional? I haven't tried it for a long time, so I have no idea
when this behavior changed.
Miklos
bcica:~> time dd if=/dev/fd0 of=/dev/null bs=2048 count=100
100+0 records in
100+0 records out
0.000u 0.000s 0:07.59 0.0% 0+
Peter Samuelson wrote:
> > +int loopback = 0;
> > +int fs_debug = 0;
> > +struct fs_dev *fs_boards = NULL;
> Aside from the 'static' issue already mentioned, these should be left
> uninitialized. ('gcc -fassume-bss-zero' would be nice, but then again
> in userspace it rarely matters.)
Hi Pete
Alan,
Here is a patch that should fix the problem. I could trim down
verify_local_APIC() now, but given the code freeze I guess it's for
post-2.4.
Maciej
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--+
+
[1.] One line summary of the problem: 2.4.0-test11 freezes when writing to FAT
SCSI-MO-Drive
[2.] Full description of the problem/report:
When writing to a msdos fat formated 640 MB magneto-optical disc the
system freezes and neither ctrl-alt-del nor the reset button can wake
the machine aga
[Rogier Wolff <[EMAIL PROTECTED]>]
> However, if my code assumes that the compiler needs to initialize the
kernel
> variable one way or another, I want to put in the initialization,
> even if that means an "= 0;" which is already the default.
Well,
[Adam J. Richter]
> +static struct pci_device_id isicom_pci_tbl[] __initdata = {
> + { VENDOR_ID, 0x2028, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2051, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2052, PCI_ANY_ID, PCI_ANY_ID },
> + { VENDOR_ID, 0x2053, PCI_ANY_ID, PCI_ANY_ID
On Wed, Nov 22, 2000 at 05:58:14PM +, Alan Cox wrote:
> > > if(vendor!=INTEL && !has_apic)
> > > /* No SMP */
> >
> > And suddenly certain i486 systems do not work anymore? Well, I haven't
>
> i486 is an intel processor
... but is there a reason why for example AMD 486's coul
[Christian Haul]
> 2.4.0-test11 freezes when writing to FAT SCSI-MO-Drive
I think this is a known problem with FAT vs. large block sizes.
I imagine it will be addressed soon.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PRO
On Thu, 23 Nov 2000, Neil Brown wrote:
> Oh, good. It's not just me and Tigran then. I was at first blaming
> my raid5 code for this, but if you get it and Tigran gets it (reported
> http://boudicca.tux.org/hypermail/linux-kernel/2000week48/0257.html
> ) then it's probably not me.
>
> And
[ChenLi Tien, from http://members.home.net/puresoft/cmedia.html]
> - * Copyright (C) 1999 ChenLi Tien ([EMAIL PROTECTED])
> - *
> - * Based on the PCI drivers by Thomas Sailer ([EMAIL PROTECTED])
> + * Copyright (C) 1999 ChenLi Tien ([EMAIL PROTECTED])
> + * C-
--- clean/arch/i386/kernel/time.c Thu Nov 2 21:00:59 2000
+++ linux/arch/i386/kernel/time.c Wed Nov 22 11:12:05 2000
@@ -63,7 +63,7 @@
*/
#include
-
+extern int x86_udelay_tsc;
unsigned long cpu_khz; /* Detected as we calibrate the TSC */
/* Number of usecs that the last int
Hi!
> You will find that most Overlockers run their favorite game in a loop for 10
> or 20 minutes as the best test they have found. This often does
> Video+Ram+CPU+Sound board (PCI) at full tilt. What is needed is a
> _standardized test_ that really goes after everything (including network).
Y
Hi!
> - A file is saved to disk
> - If the file isn't touched (read or written to) within days
> (default 14), the file is compressed.
> - If the file isn't compressed more than percent (default 20), the
> file is flagged "can't compress".
> - All file compression is done on low traffic times (
[1.] One line summary of the problem:
kernel 2.4.0-test11-ac1 hang with usb-uhci and emu10k1
[2.] Full description of the problem/report:
If I load the emu10k1.o module prior to loading the usb-uhci.o module, the
system will completely hang with no oops. 3-finger-salute has no effect,
had
Alan Cox wrote:
> > under 1 gig in size. You can exhibit the problem by mounting the dvd movie
> > "The World is Not Enough" as it contains a video_ts.vob which is larger than
> > 1 gigabyte. You will see that most of the file lengths are incorrect due to
> > the "cruft mounting option" hacking
[EMAIL PROTECTED] said:
> > |> Can't we change that to :
> > |> #error "Udelay..."
> >
> > No.
>
> ?? I think I'm missing something here.
> preprocessor stuff is done too early for this
We were talking about
#if 0
/* Don't turn this on, fix your code instead */
void __bad_udelay(int c)
{
#e
>Keith Owens wrote:
>>
>> [Adam J. Richter]
>> > +static struct pci_device_id atp870u_pci_tbl[] __initdata = {
>> > +{vendor: 0x1191, device: 0x8002, subvendor: PCI_ANY_ID, subdevice: PCI_ANY_ID},
>> > +{vendor: 0x1191, device: 0x8010, subvendor: PCI_ANY_ID, subdevice: PCI_ANY_ID},
>>
>> It woul
On Thu, Nov 23, 2000 at 09:22:09AM +0100, Rogier Wolff wrote:
> Peter Samuelson wrote:
>
> > > +int loopback = 0;
> > > +int fs_debug = 0;
> > > +struct fs_dev *fs_boards = NULL;
>
> > Aside from the 'static' issue already mentioned, these should be left
> > uninitialized. ('gcc -fassume-bss-z
On Thursday November 23, [EMAIL PROTECTED] wrote:
>
> Guys, could you try to reproduce it with the following:
Well, I tried but it didn't go real well.
I build a 2 drive raid5 array (the script goes on to 3,4,5,6,7 drive
arrays), ran mkfs, mounted, ran "hdparm -t" on /dev/md0, ran bonnie.
S
Pavel Machek wrote:
> > - A file is saved to disk
> > - If the file isn't touched (read or written to) within days
> > (default 14), the file is compressed.
> > - If the file isn't compressed more than percent (default 20), the
> > file is flagged "can't compress".
> > - All file compression is
Mitchell Blank Jr wrote:
> > +MODULE_PARM(fs_debug, "i");
>
> There's no reason to wrap these "MODULE_PARM"s inside an "#ifdef MODULE".
anymore in 2.4
OK.
> > +#define MIN(a,b) (((a)<(b))?(a):(b))
>
> You don't seem to ever use this definition.
H. Used to though..
Mitchell Blank Jr wrote:
> * I don't like header files that define the registers of the chip - since
> the header file is only included in the driver's .c
For a non-hypothetical case why it makes sense to have such things in
their own header file: if you dig out some older versions of the A
> mtrr: your CPUs had inconsistent variable MTRR settings
> mtrr: probably your BIOS does not setup all CPUs
>
> Am not sure if this is going to lead to bad juju. Anybody else seeing
> this on a similar mobo
This is a BIOS bug the kernel detects and fixes providing you have mtrr
enabled so you s
Small cleanup in mad16.c MPU probing code. Against any 2.4 kernel.
Replacing mad loops with readable switches. Removing unnecessary array
declarations. Removing variable 'with secret power'. Removing double
declaration (tmp).
Is there a maintainer for this stuff?
Whom to feed with this kind of
The following patch against 2.4.0-test11 changes INIT_FILES, INIT_MM and
INIT_SIGNALS to use named initializers.
Please apply,
Thanks,
Helge
--- linux/include/linux/sched.h.org Tue Nov 21 00:50:43 2000
+++ linux/include/linux/sched.h Thu Nov 23 10:20:37 2000
@@ -174,18 +174,19 @@
[Rogier Wolff]
> > > +MODULE_PARM(fs_debug, "i");
> >
> > There's no reason to wrap these "MODULE_PARM"s inside an "#ifdef MODULE".
> anymore in 2.4
^^^2.2
Verified in 2.2.0 (the oldest tree I have).
Peter
-
To unsubscribe from this lis
Peter Samuelson wrote:
>
> [Rogier Wolff]
> > > > +MODULE_PARM(fs_debug, "i");
> > >
> > > There's no reason to wrap these "MODULE_PARM"s inside an "#ifdef MODULE".
> > anymore in 2.4
>^^^2.2
>
> Verified in 2.2.0 (the oldest tree I hav
On Thursday November 23, [EMAIL PROTECTED] wrote:
> On Thursday November 23, [EMAIL PROTECTED] wrote:
> >
> > Guys, could you try to reproduce it with the following:
>
> Well, I tried but it didn't go real well.
>
.
> It looks like extending a file is not allowed any more.
>
> This is
The sundance driver in 2.4.0-test11 doesn't seem to like a DFE-550
that I have
On module installation te driver identifies the card but cant find any
PHYs, also if I remove the module afterwards I can't reinsert it.
Any suggestions?
The messages are
On installation:
eth0: OEM Sundance Technol
Keith Owens writes:
> "Albert D. Cahalan" <[EMAIL PROTECTED]> wrote:
>> The hard part of klogd/ksymoops is decoding the code bytes AFAIK.
>> The rest is a just a cross between grep and ps -- you search and
>> you do symbol lookups. I could throw it together in a few hours,
>> minus the disassembl
> Also, cross-arch debugging is done by people who don't need tools
> like ksymoops anyway. Most likely they have half the opcodes
Nope
> memorized already, and they have the CPU manual open on their desk.
Nope
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
> > - A file is saved to disk
> > - If the file isn't touched (read or written to) within days
> > (default 14), the file is compressed.
> > - If the file isn't compressed more than percent (default 20), the
> > file is flagged "can't compress".
> > - All file compression is done on low traffic
On Thu, Nov 23, 2000 at 05:03:00PM +1100, Neil Brown wrote:
> Oh, good. It's not just me and Tigran then.
You have it all backwards. It would be good if it were
just you and Tigran. Unfortunately it also hits me.
(I am reorganizing my disks, copying large trees from
one place to the other. Alw
Michael Elizabeth Chastain wrote:
> I have a compiler from gcc.gnu.org's CVS tree that's only a few days old,
> so I can verify Jakub's claim.
BTW, do you have any estimate of how much dead string space it actually
removed ? (I.e. did the .data segment size change significantly, or was
is lost in
Peter Samuelson wrote:
> [ChenLi Tien, from http://members.home.net/puresoft/cmedia.html]
> > - * Copyright (C) 1999 ChenLi Tien ([EMAIL PROTECTED])
> > - *
> > - * Based on the PCI drivers by Thomas Sailer ([EMAIL PROTECTED])
> > + * Copyright (C) 1999 ChenLi Tien ([EMAIL PROTECT
I've just recompiled my kernel from 2.4.0-test10, upgrading to test-11, this
is the output from a make bzlilo:
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686-c -o ixj.o
ixj.c
ixj.c: In function xj_ioctl
> ixj.c: In function xj_ioctl':
> ixj.c:4703: D_PHONE_RING_START' undeclared (first use in this function)
You have some kind of corruption here
You might want to unpack and build the new kernel with a known good kernel
rather than test9
-
To unsubscribe from this list: send the line "unsub
I had a problem while compiling test11 on test9 kernel with debian
gcc-2.95.2. I had suspended the compilation with Ctrl-Z and it
continuted by compiling some garbage. Next time it compiled fine, so I'd
guess the files were ok in cache.
I do not know who is to blaim. Just thought to share this in
Hi!
I think I found a bug in the IDE subsystem. When I do 'cat
/proc/ide/hde/identify', the system locks up completely, not
even Alt+RysRq+B helps. Everything else under /proc/ide works.
hdparm can cause the same symptoms, but I have not checked
when exactly it does so.
I have an Asus A7V mainbo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ARND BERGMANN wrote:
> Hi!
>
> I think I found a bug in the IDE subsystem. When I do 'cat
> /proc/ide/hde/identify', the system locks up completely, not
> even Alt+RysRq+B helps. Everything else under /proc/ide works.
> hdparm can cause the same symp
[ChenLi Tien]
> > I don't think the (2,3,0) ifdef is necessary. Just use the labeled
> > initializers for all kernels. See also cm_audio_fops, cm_dsp_fops,
> > cm_midi_fops, cm_dmfm_fops.
>
> Yes, as 2.3.x series is not for end-user, I can remove them. I keep it for
> easy to tell what's diffe
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Thats because too many things get put on a line then.
> > And because we do [] [] not [][] ?
>
> In the good old times we had foo bar for a total of 8*(8+1) = 72
> positions. Now we have [] [] which takes 8*(8+1+4) = 104
> positions. If you tu
I was testing out 2.2.18pre23 for USB purposes and found that its
outputing binary garbage at boot:
BIOS Vendor: Intel Corporation
BIOS Version: 1.00.10.DD04
BIOS Release: 03/19/97
System Vendor: Sony Corporation.
Product Name: PCV-70(U2).
Version Sony GI.
Serial Number 1003494.
Board Vendor: In
> BIOS Vendor: Intel Corporation
> BIOS Version: 1.00.10.DD04
> BIOS Release: 03/19/97
> System Vendor: Sony Corporation.
> Product Name: PCV-70(U2).
> Version Sony GI.
> Serial Number 1003494.
> Board Vendor: Intel Corporation.
> Board Name: Agate.
> Board Version: AA662195-305.
So far so good
On Thu, 23 Nov 2000, Michael Elkins wrote:
Usb controller is sharing a interrupt with the emu10k1.
For what I know the emu10k1 driver doesn't have any problem
sharing irq's, so I would blame the usb driver...
Rui Sousa
> 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog
On Thu, 23 Nov 2000 [EMAIL PROTECTED] wrote:
>
> I never read assembler, but looking at the code produced
> by gcc (2.95.2) it seemed peculiar, maybe an attempt to
> optimize something combining the
> if (filp->f_pos >= inode->i_size)
> with the
> while (filp->f_pos < inode->i_size)
Changes in 2.4.0test11ac3
o Features is back to flags for compatibility (me)
o Cleanup ramdisk namespace (Jeff Garzik)
o ACPI updates(Andrew Grover)
o Make SET_MODULE_OWNER macro safer (Jeff Garzik
On Thu, Nov 23, 2000 at 07:37:27AM -0800, Linus Torvalds wrote:
> > I have seen that there were discussions on the right compiler to use.
> > Is 2.95.2 wrong? Have other things to do tomorrow, so it will be
> > 24 hours before I can look at this again.
>
> 2.95.2 should have been reasonably ok, b
Not on list just throwing an idea out.
One thing that "bugs" me is if a given drive has more than one partion
each partion has to be mounted seperatly.
With CDs this also means you can not mount "split" cds in full if you
want to. Soo Given that Super-Mount is already taken, How about (in
2.5??)
On Thu, Nov 23, 2000 at 03:31:51PM +, Alan Cox wrote:
> > Board Name: Agate.
> > Board Version: AA662195-305.
>
> So far so good
>
> > BIOS Vendor: f.=A3^]<94>fA=E8^D.=A3ESC<94>^N^_
>
> This looks like the table end markers are missing or the length was wrong.
> If you change
>
> static in
(2.4.0-test11, but probably every version)
The name member of the net_device struct is fixed to IFNAMSIZ (16) bytes,
and is accessed using strcpy, strcmp and friends all over the place, which
suggests that the last byte of the name must be a null character. This
must be verified when the name is
[Alan Cox]
> > Thats because too many things get put on a line then.
> > And because we do [] [] not [][] ?
[Andries Brouwer]
> In the good old times we had foo bar for a total of 8*(8+1) = 72
> positions. Now we have [] [] which takes 8*(8+1+4) = 104
I've got it! Put multiple addresses w
On Thu, 23 Nov 2000, Neil Brown wrote:
> which enabled ext2_notify_change, however ext2_notify_change has a
> bug.
> It sets attributes from iattr->ia_attr_flags even
> if ATTR_ATTR_FLAG is NOT SET in iattr->ia_valid.
Arrrgh. Could you try that:
diff -urN rc11/fs/buffer.c rc11-ext2/fs/buffer.
On Thu, Nov 23, 2000 at 04:35:33PM +, Rui Sousa wrote:
> On Thu, 23 Nov 2000, Michael Elkins wrote:
>
> Usb controller is sharing a interrupt with the emu10k1.
> For what I know the emu10k1 driver doesn't have any problem
> sharing irq's, so I would blame the usb driver...
usb-uhci doesn't a
Howdy,
Calling read() on some directories in /proc returns EINVAL, rather
than EISDIR. The other filesystems return EISDIR and the manpage says
this is what should be returned in this situation. The appended patch
applies against 2.4.0-test11.
Matt
diff -urN linux-vanilla/fs/proc/generic.c li
On Thu, Nov 23, 2000 at 04:50:22AM +0100, [EMAIL PROTECTED] wrote:
> Below a working patch for which the isofs images I got
> all are OK. (There is still a lot of silliness here -
> superfluous parentheses, a rename of isofs_cmp to isofs_comp
> in one file to avoid confusion with the isofs_cmp in
On Tue, 21 Nov 2000, Tobias Ringstrom wrote:
> >
> > Tobias, can you confirm that calling pci_enable_device before reading
> > dev->irq fixes the 3c59x.c problem for you?
>
> Nope. The interrupts do not seem to get through. Packets are transmitted,
> but that's it. I've copied the interesting
Followup to: <[EMAIL PROTECTED]>
By author:Robert L Martin <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Not on list just throwing an idea out.
> One thing that "bugs" me is if a given drive has more than one partion
> each partion has to be mounted seperatly.
> With CDs this also me
On Thu, 23 Nov 2000, Alexander Viro wrote:
> On Thu, 23 Nov 2000, Neil Brown wrote:
>
> > which enabled ext2_notify_change, however ext2_notify_change has a
> > bug.
> > It sets attributes from iattr->ia_attr_flags even
> > if ATTR_ATTR_FLAG is NOT SET in iattr->ia_valid.
>
> Arrrgh. Could yo
On Thu, 23 Nov 2000, Ragnar Hojland Espinosa wrote:
>
> Yup, indeed it solves the dir/namei problem.
Can you check whether the single patch of _just_ removing the extra "f_pos
>= i_size" test in do_isofs_readdir() fixes it? The other changes of
Andries patch look like they should not affect
On Thu, 23 Nov 2000, Linus Torvalds wrote:
> To tie two threads together again: the thread about FS corruption is one
> of my main worries right now. Do people who see this happen to use a gcc
> other than egcs-2.91.66? I know Andries apparently has 2.95.2, and he's
> one of the people who have re
[ Tobias: thanks for an excellent report, btw ]
On Wed, 22 Nov 2000, Tobias Ringstrom wrote:
> On Wed, 22 Nov 2000, Tobias Ringstrom wrote:
>
> > Not that I like it, but I need to boot Win98, and then warm boot into
> > Linux, or the Cardbus is not working. This is using Linux-2.4.0-test11 on
On Thu, Nov 23, 2000 at 09:20:15AM -0800, Linus Torvalds wrote:
> Can you check whether the single patch of _just_ removing the extra "f_pos
> >= i_size" test in do_isofs_readdir() fixes it? The other changes of
> Andries patch look like they should not affect code generation at all, but
> I'd sti
Rogier Wolff wrote:
>
> Alan Cox wrote:
> > > under 1 gig in size. You can exhibit the problem by mounting the dvd movie
> > > "The World is Not Enough" as it contains a video_ts.vob which is larger than
> > > 1 gigabyte. You will see that most of the file lengths are incorrect due to
> > > the
On Thu, 23 Nov 2000, Linus Torvalds wrote:
> > > Tobias, can you confirm that calling pci_enable_device before reading
> > > dev->irq fixes the 3c59x.c problem for you?
> >
> > Nope. The interrupts do not seem to get through. Packets are transmitted,
> > but that's it. I've copied the interesting
Albert D. Cahalan writes:
> > they are not only references to
> > kernel functions, but also kernel data and read only data within
> > the kernel text segment.
>
> 1. this is harmless
> 2. this is useful (you might get a variable's name)
Wrong. Op-codes on this machine are organised such that b
Ragnar Hojland Espinosa writes:
> On Thu, Nov 23, 2000 at 12:26:30AM +, Russell King wrote:
> > Oh, missed this one. Here you're wrong again. The numbers in [< >]
> > should be looked up, and no others. The code can look exactly like
> > a kernel address. In this case you definitely do NOT
[Martin Dalecki]
> Just a small trivial obviously correct update...
OK, merged into my pending pci_ids.h patch. (This is bigger than
necessary because I converted almost all spaces to tabs.)
Peter
--- 2.4.0test11/include/linux/pci_ids.h.bak Mon Nov 13 01:43:49 2000
+++ 2.4.0test11/include
On Thu, 23 Nov 2000, Linus Torvalds wrote:
> Tobias? Does changing that if-statement that make your bus happier?
I'll try this tomorrow. The sick laptop is at work, and I'm home. The time
difference really slows things down. :-(
/Tobias
-
To unsubscribe from this list: send the line "unsubscri
On Thu, 23 Nov 2000, Tobias Ringstrom wrote:
> >
> > - enable DEBUG in arch/i386/kernel/pci-i386.h. This should make the code
> >print out what the pirq table entries are etc.
>
> Done. When adding the call to eisa_set_level_irq, the line
>
> IRQ for 00:0a.0(0) via 00:0a.0 -> PIRQ 03, ma
hot-pluggable devices are turned off in the config (see below).
-test9 had some problems with depmod arguments, make completed
if i used '-' in the Makefile to ignore the status and went back
to run depmod by hand.
make[1]: Leaving directory `/usr/src/linux-2.4.0-test11/arch/i386/lib'
cd /lib/mo
Hi,
The sizeof(struct tty_struct) = 3084. Why don't we have a private slab
cache for it instead of getting a page and wasting some precious bytes at
the end? Potentially, we can have thousands of tty_struct allocated
(assuming we have thousands of concurrent users)...
regards,
Tigran
-
To unsub
On Thu, Nov 23, 2000 at 06:54:48PM +, Tigran Aivazian wrote:
> Hi,
>
> The sizeof(struct tty_struct) = 3084. Why don't we have a private slab
> cache for it instead of getting a page and wasting some precious bytes at
> the end? Potentially, we can have thousands of tty_struct allocated
> (as
Hi,
Since I use kernel 2.4.0(test11) the power-off on halt doesn't work
anymore (I have the same problem with previous 2.4.0 releases).
I use apm to power-off the system (my system doesn't support acpi) and
with kernel 2.2.17 everything works great. But since I've compiled
2.4.0test11 with ex
Dans son message du Thu 23 November, Maciej W. Rozycki ecrit :
> Hmm, your BIOS reports the timer IRQ is directly connected...
> > Int: type 0, pol 3, trig 3, bus 2, IRQ 09, APIC ID 2, APIC INT 09
> This is weird for an ISA IRQ.
Remember that I have TWO PCI buses and one ISA Bus.
>
> > ENABLI
"Heinz J. Mauelshagen" wrote:
>
> On Wed, Nov 22, 2000 at 04:27:51PM -0500, Brian Kress wrote:
> > "Heinz J. Mauelshagen" wrote:
> > >
> > > On Wed, Nov 22, 2000 at 04:05:39PM -0500, Brian Kress wrote:
> > > > Question about /proc/partitions and LVM. LVM devices in
> > > > /proc/partitions
On Thu, Nov 23, 2000 at 06:54:48PM +, Tigran Aivazian wrote:
> Hi,
>
> The sizeof(struct tty_struct) = 3084. Why don't we have a private slab
> cache for it instead of getting a page and wasting some precious bytes at
> the end? Potentially, we can have thousands of tty_struct allocated
> (as
On Thu, Nov 23, 2000 at 08:59:46AM -0800, Linus Torvalds wrote:
> [ Btw, I noticed that one of my machines _does_ have gcc-2.95.2, so I can
> look at the isofs code generation myself. I don't see anything obvious,
> and the code is hairy. The differences between 2.91.66 and 2.95.2 are
> big
Tiny patch for vmware-config.pl
Phil Stracchino wrote:
>
> I just compiled and installed kernel 2.4.0-test11. Upon rebooting,
> vmware-2.0.3-786 refused to run. Running vmware-config.pl resulted in a
> the following message:
>
> "Your processor does not have a Time Stamp Counter. VMwa
On Thu, 23 Nov 2000, Charles Cazabon wrote:
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > Thats because too many things get put on a line then.
> > > And because we do [] [] not [][] ?
> >
> > In the good old times we had foo bar for a total of 8*(8+1) = 72
> > positions. Now we hav
On Thu, Nov 23, 2000 at 12:07:01PM -0800, Phil Stracchino wrote:
> I just compiled and installed kernel 2.4.0-test11. Upon rebooting,
> vmware-2.0.3-786 refused to run. Running vmware-config.pl resulted in a
> the following message:
>
> "Your processor does not have a Time Stamp Counter.
> vmware-2.0.3-786 refused to run. Running vmware-config.pl resulted in a
> the following message:
Run 2.4.0-test11-ac3
-
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/
Albert D. Cahalan writes:
> Also, cross-arch debugging is done by people who don't need tools
> like ksymoops anyway. Most likely they have half the opcodes
> memorized already, and they have the CPU manual open on their desk.
I certainly don't have each of the 4 billion opcode combinations on
th
On Tue, 21 Nov 2000, Jorge Nerin wrote:
>> How about a working URL?
>>
>> traceroute to skaro.nightcrawler.com (216.186.140.118), 30 hops max, 38 byte packets
>> [...]
>> 11 pos3-0-0-155M.sjc-bb3.cerf.net (134.24.29.26) 66.400 ms 74.860 ms 68.486 ms
>> 12 dslnetworks1.dslnetworks.com (206.19
On Thu, 23 Nov 2000, Andi Kleen wrote:
>
> I am actually not sure if the normal kernel contains even a variable
> width long long shift.
Sure it does. The isofs code contains exctly that:
block = filp->f_pos >> bufbits;
In fact, almost all filesystems do this at some point. ext2 does
On Wed, Nov 22, 2000 at 09:39:51PM +, Keir Fraser wrote:
> > The reason that everyone else uses copy_{to,from}_user is that there
> > is no way to guarantee that the userspace pointer is valid. That
> > memory may have been swapped out. The copy macros are prepared to
> > fault the memory in.
On Thu, Nov 23, 2000 at 12:38:55PM -0800, Linus Torvalds wrote:
...
> In fact, almost all filesystems do this at some point. ext2 does it for
> directories too, for some very similar reasons that isofs does. See
> fs/ext2/dir.c:
>
> blk = (filp->f_pos) >> EXT2_BLOCK_SIZE_BITS(sb);
>
> (an
I'm still trying to reproduce the darn thing w/o the patch. No luck so
far.
Maybe I'll put some mission critical stuff on my machine. Then it'll pop
up like clock works. Thats the way everythign is supposed to work right?
=)
Tigran Aivazian wrote:
> However, I can't say that _without_ your patch
Hello all,
Using RHL 2.2.16-3 kernel on i686.
Raising MAX_UNITS define from 8 to 16 or 32 in net drivers (tested
tulip.c) causes reproducible oops. The latest Don Becker driver also does
this. Using DFE-570TX quad ethernet cards.
So, why change MAX_UNITS? Interfaces 9-> can't be passed optio
Hi.
Some time ago there was a thread about subject and a patch was posted
(by davej?). It was rejected because of the vmlist_modify_{un}lock
mess (AFAIR) and nothing has been done since. The first patch below
moves mm->rss inside the page_table_lock in mm/.
I noticed that mm->rss is also modif
Hi Alexander,
I am "hammering" an ext2 filesystem with all sorts (bonnies, make -j8
bzImage, cp -a dir1 dir2 + all these over localhost NFSv3) for a while and
so far it survives. The system is 2way SMP with 1G RAM.
However, I can't say that _without_ your patch the above did _not_
survive. The c
With recent ide patches, the ide driver seems to try to use DMA mode even for a drive
which dosen't support it. CONFIG_IDEDMA_PCI_AUTO is enabled but even so with the stock
kernel this dosen't happen. older patches didn't have this behavior either. Is this
change intentional ?
hdc: 333630 sect
On 23 Nov 00 at 20:22, Alan Cox wrote:
> > vmware-2.0.3-786 refused to run. Running vmware-config.pl resulted in a
> > the following message:
>
> Run 2.4.0-test11-ac3
Hi Alan,
is change to field name temporary, and name will be reverted back
to flags, even although contents may differ between
On Thu, 23 Nov 2000, Matti Aarnio wrote:
> On Thu, Nov 23, 2000 at 12:38:55PM -0800, Linus Torvalds wrote:
> ...
> > In fact, almost all filesystems do this at some point. ext2 does it for
> > directories too, for some very similar reasons that isofs does. See
> > fs/ext2/dir.c:
> >
> > b
Hi,
I use an USB mouse, it works perfectly both with 'gpm' and with X-window but
time to time, I've this kind of message stream :
[root@debian-f5ibh] ~ # usb-uhci.c: interrupt, status 3, frame# 20
usb-uhci.c: interrupt, status 3, frame# 44
usb-uhci.c: interrupt, status 3, frame# 68
usb-uhci.c: i
On Thu, Nov 23, 2000 at 10:32:01PM +0100, f5ibh wrote:
> Hi,
>
> I use an USB mouse, it works perfectly both with 'gpm' and with X-window but
> time to time, I've this kind of message stream :
>
> [root@debian-f5ibh] ~ # usb-uhci.c: interrupt, status 3, frame# 20
> usb-uhci.c: interrupt, status
> is change to field name temporary, and name will be reverted back
> to flags, even although contents may differ between 2.2.x and 2.4.x,
> or is there features to stay? Currently VMware does
>
> "^\(features\|flags\).* tsc"
>
> but question is - should we leave it here, or revert it back?
I
Hi!
Just a few hints on __init/__exit stuff...
On Wed, 22 Nov 2000, Patrick van de Lageweg wrote:
> +struct reginit_item PHY_NTC_INIT[] = {
Can be marked __initdata
> +void undocumented_pci_fix (struct pci_dev *pdev)
Can be marked __init
> +void write_phy (struct fs_dev *dev, int regnum, i
Hi
patch-3c503:
@@ -307,11 +307,12 @@
{
ei_status.tx_start_page = EL2_MB1_START_PG;
ei_status.rx_start_page = EL2_MB1_START_PG + TX_PAGES;
- printk("\n%s: %s, %dkB RAM, using programmed I/O (REJUMPER for SHARED
MEMORY).\n",
- dev->name, ei_status.name, (w
On Thu, 23 Nov 2000, Andreas Bombe wrote:
> > I may be wrong on this, but I thought that copy_{to,from}_user are
> > only necessary if the address range you are accessing might cause a
> > fault which Linux cannot handle (ie. one which would cause the
> > application to segfault if it accessed tha
1 - 100 of 158 matches
Mail list logo
