Re: Update Linux 2.4 Status/TODO list
[EMAIL PROTECTED] wrote: The bug about loopback devices is still not fixed, but this document says it is. This hangs linux-2.4.0.test9 (only tested with Pentium II. Noname SMP and a Dell.) dd if=/dev/zero of=/tmp/dos.img bs=64k count=1 # a lot more the viritual memory avail mkdosfs /tmp/dos.img mount -o loop /tmp/dos.img /mnt/dos dd if=/dev/zero of=/mnt/dos/bigfile.empty OK, here's the updated Linux 2.4 bug list. I let myself get a bit behind, so it took me a while to process through all of my backlogged l-k mail archives to assemble this list. As always, it's complete as I can make it, but it's not perfect. In particualar, some bugs listed on this page may have been fixed already. If so, or if you know some bug that didn't make on to this list, please let me know. For people who are wondering what changed, the differences from the last major release of this page can be found at http://linux24.sourceforge.net/status-changes.html As always, if you're curious what state this document is in, you can always get the latest copy by going to: http://linux24.sourceforge.net - Ted Linux 2.4 Status/TODO Page Last modified: [tytso:2913.0151EDT] Hopefully up to date as of: test8 1. Should Be Fixed (Confirmation Wanted) * Fbcon races (cursor problems when running continual streaming output mixed with printk + races when switching from X while doing continuous rapid printing --- Alan) 2. Capable Of Corrupting Your FS/data * Use PCI DMA by default in IDE is unsafe (must not do so on via VPx, x < 3) (requires chipset tuning to be enabled according to Andre Hedrick --- we need to turn this on by default -- TYT) * Fix the OOPS in usb-storage from the error-recovery handler. (reported by Matthew Dharm) * Non-atomic page-map operations can cause loss of dirty bit on pages (sct, alan) 3. Security * Fix module remove race bug (still to be done: TTY, ldisc, I2C, video_device - Al Viro) (Rogier Wolff will handle ATM) 4. Boot Time Failures * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC Versa LX with PIIX tuning) * HT6560/UMC8672 ide sets up stuff too early (before region stuff can be done) * Crashes on boot on some Compaqs ? (may be fixed) * Boot hangs on a range of Dell docking stations (Latitude) + Almost certainly related: PCI code doesn't see devices behind DECchip 21150 PCI bridges (used in Dell Latitude). Reported by Simon Trimmer . (Patch from Martin Mares exists but it disables cardbus devices, according to Tigran.) + Derek Fawcus at Cisco reports similar problems with Toshiba Tecra 8000 attached to the DeskStation V+ docking station. (once again, caused by bridge returning 0 when reading the I/O base/limit and Memory base/limit registers which confuses the new PCI resource code). * IBM Thinkpad 390 won't boot since 2.3.11 (See Decklin Foster for more info) 5. Compile errors * arcnet/com20020-isa.c doesn't compile, as of 2.4.0-test8. Dan Aloni has a fix * drivers/sound/cs46xx.c has compile errors test7 and test8 (C Sanjayan Rosenmund) 6. In Progress * Finish I2O merge (Intel/Alan) * Restore O_SYNC functionality (Stephen) - core code and ext2 done * Fix all remaining PCI code to use pci_enable_device (mostly done) * Fix, um, interesting races around dup2() and friends. (Al Viro) * Finish the audit/code review of the code dealing with descriptor tables. (Al Viro) * DMFE is not SMP safe (Frank Davis patch exists, but hasn't gotten much commens yet) * Audit all char and block drivers to ensure they are safe with the 2.3 locking - a lot of them are not especially on the read()/write() path. (Frank Davis --- moving slowly; if someone wants to help, contact Frank) 7. Obvious Projects For People (well if you have the hardware..) * Make syncppp use new ppp code * Fix SPX socket code 8. Fix Exists But Isnt Merged * Update SGI VisWS to new-style IRQ handling (Ingo) * Support MP table above 1Gig (Ingo) * Dont panic on boot when meeting HP boxes with wacked APIC table numbering (AC) * Scheduler bugs in RT (Dimitris) * AIC7xxx doesnt work non PCI ? (Doug says OK, new version due anyway) * Fix boards with different TSC per CPU and kill TSC use on them * Floppy last block cache flush error * PPC-specific: won't boot on 601 CPU's (powermac) (Andreas Tobler; Paul Mackerras has fix in PPC tree) * IRDA fixes (patches from Russell King
Re: Update Linux 2.4 Status/TODO list
[EMAIL PROTECTED] wrote: The bug about loopback devices is still not fixed, but this document says it is. This hangs linux-2.4.0.test9 (only tested with Pentium II. Noname SMP and a Dell.) dd if=/dev/zero of=/tmp/dos.img bs=64k count=1 # a lot more the viritual memory avail mkdosfs /tmp/dos.img mount -o loop /tmp/dos.img /mnt/dos dd if=/dev/zero of=/mnt/dos/bigfile.empty OK, here's the updated Linux 2.4 bug list. I let myself get a bit behind, so it took me a while to process through all of my backlogged l-k mail archives to assemble this list. As always, it's complete as I can make it, but it's not perfect. In particualar, some bugs listed on this page may have been fixed already. If so, or if you know some bug that didn't make on to this list, please let me know. For people who are wondering what changed, the differences from the last major release of this page can be found at http://linux24.sourceforge.net/status-changes.html As always, if you're curious what state this document is in, you can always get the latest copy by going to: http://linux24.sourceforge.net - Ted Linux 2.4 Status/TODO Page Last modified: [tytso:2913.0151EDT] Hopefully up to date as of: test8 1. Should Be Fixed (Confirmation Wanted) * Fbcon races (cursor problems when running continual streaming output mixed with printk + races when switching from X while doing continuous rapid printing --- Alan) 2. Capable Of Corrupting Your FS/data * Use PCI DMA by default in IDE is unsafe (must not do so on via VPx, x 3) (requires chipset tuning to be enabled according to Andre Hedrick --- we need to turn this on by default -- TYT) * Fix the OOPS in usb-storage from the error-recovery handler. (reported by Matthew Dharm) * Non-atomic page-map operations can cause loss of dirty bit on pages (sct, alan) 3. Security * Fix module remove race bug (still to be done: TTY, ldisc, I2C, video_device - Al Viro) (Rogier Wolff will handle ATM) 4. Boot Time Failures * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC Versa LX with PIIX tuning) * HT6560/UMC8672 ide sets up stuff too early (before region stuff can be done) * Crashes on boot on some Compaqs ? (may be fixed) * Boot hangs on a range of Dell docking stations (Latitude) + Almost certainly related: PCI code doesn't see devices behind DECchip 21150 PCI bridges (used in Dell Latitude). Reported by Simon Trimmer . (Patch from Martin Mares exists but it disables cardbus devices, according to Tigran.) + Derek Fawcus at Cisco reports similar problems with Toshiba Tecra 8000 attached to the DeskStation V+ docking station. (once again, caused by bridge returning 0 when reading the I/O base/limit and Memory base/limit registers which confuses the new PCI resource code). * IBM Thinkpad 390 won't boot since 2.3.11 (See Decklin Foster for more info) 5. Compile errors * arcnet/com20020-isa.c doesn't compile, as of 2.4.0-test8. Dan Aloni has a fix * drivers/sound/cs46xx.c has compile errors test7 and test8 (C Sanjayan Rosenmund) 6. In Progress * Finish I2O merge (Intel/Alan) * Restore O_SYNC functionality (Stephen) - core code and ext2 done * Fix all remaining PCI code to use pci_enable_device (mostly done) * Fix, um, interesting races around dup2() and friends. (Al Viro) * Finish the audit/code review of the code dealing with descriptor tables. (Al Viro) * DMFE is not SMP safe (Frank Davis patch exists, but hasn't gotten much commens yet) * Audit all char and block drivers to ensure they are safe with the 2.3 locking - a lot of them are not especially on the read()/write() path. (Frank Davis --- moving slowly; if someone wants to help, contact Frank) 7. Obvious Projects For People (well if you have the hardware..) * Make syncppp use new ppp code * Fix SPX socket code 8. Fix Exists But Isnt Merged * Update SGI VisWS to new-style IRQ handling (Ingo) * Support MP table above 1Gig (Ingo) * Dont panic on boot when meeting HP boxes with wacked APIC table numbering (AC) * Scheduler bugs in RT (Dimitris) * AIC7xxx doesnt work non PCI ? (Doug says OK, new version due anyway) * Fix boards with different TSC per CPU and kill TSC use on them * Floppy last block cache flush error * PPC-specific: won't boot on 601 CPU's (powermac) (Andreas Tobler; Paul Mackerras has fix in PPC tree) * IRDA fixes (patches from Russell King
Re: Update Linux 2.4 Status/TODO list
--- Andre Hedrick <[EMAIL PROTECTED]> a écrit : > > Ted and LT, > > I think this are the two things you wanted that were located in: > > /src/tar-files/testing/direct_add/ht6560b.c > /src/tar-files/testing/direct_add/qd65xx.c > /src/tar-files/testing/direct_add/qd65xx.h > > First Petr and Samuel, are these good to go into 2.4.0 ?? > qd65xx.x : I think so : This will replace qd6580.c, and hence add support for qd6500 (Petr will be pleased) Cheers, Samuel __ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/ - 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/
Re: Update Linux 2.4 Status/TODO list
--- Andre Hedrick [EMAIL PROTECTED] a écrit : Ted and LT, I think this are the two things you wanted that were located in: /src/tar-files/testing/direct_add/ht6560b.c /src/tar-files/testing/direct_add/qd65xx.c /src/tar-files/testing/direct_add/qd65xx.h First Petr and Samuel, are these good to go into 2.4.0 ?? qd65xx.x : I think so : This will replace qd6580.c, and hence add support for qd6500 (Petr will be pleased) Cheers, Samuel __ Do You Yahoo!? Send instant messages get email alerts with Yahoo! Messenger. http://im.yahoo.com/ - 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/
Re: Update Linux 2.4 Status/TODO list
Alan Cox <[EMAIL PROTECTED]> writes: > I've seen no reproduction of it. The only oddity I've seen is that > you can now do overlapping shm attaches which is different to 2.2, > but quite legal according to the standards Yes, I introduced this by purpose. It now much more behaves the standard UN*X way where you can create a file with the same name an unlinked file has had. We had some bug report some time before on lkml about the nonstandard Linux behaviour. Christoph - 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/
Re: Update Linux 2.4 Status/TODO list
On 13 Sep 2000, at 22:37, Andre Hedrick wrote: > > Ted and LT, > > I think this are the two things you wanted that were located in: > > /src/tar-files/testing/direct_add/ht6560b.c > /src/tar-files/testing/direct_add/qd65xx.c > /src/tar-files/testing/direct_add/qd65xx.h > > First Petr and Samuel, are these good to go into 2.4.0 ?? > I'm sorry, I don't know, I have no time to test these drivers now and I have received no help from you regarding test methodology so far, so I have even no idea how to test these drivers. Everything what I know about IDE VLB chips is at http://www.ryston.cz/petr/vlb/ and there is also a list of VLB IDE controllers I own. I also own several ide drives - old Alps DR-312C, ST3120A, WDC: AC340, AC22100, AC33100, AC24300 and other and some ATAPI CD-ROMS. As a test box I can use OPTi895 motherboard with 32 MB RAM and AM486DX5-133 processor, I have also A80486DX-50 processor for testing 50 MHz VLB bus. So if anybody give me exact test directions, I'm able to do these tests if they will be not too much time consuming. But please no "compile the kernel" or "make some copy" advices. In fact, I think at first shall be all IDE/ATA/ATAPI drivers tested whether they give correct timing on IDE bus according ATA/ATAPI specifications and with various load. Then problem drives can be tested. But it needs good laboratory equipment. Back to a.m. drivers. What about the problem with region stuff? Was it rectified already? Best Regards, Petr Soucek Ryston Electronics s.r.o. Modranska 621/72 CZ-143 00 Praha 4, Czech Republic tel +420-2-6130fax +420-2-61302211 Email: [EMAIL PROTECTED] http://www.ryston.cz - 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/
Re: Update Linux 2.4 Status/TODO list
[EMAIL PROTECTED] writes: > * SHM segments not always being detached and destroyed right ? >(problem reported by Lincoln Dale) This problem is not reproducible AFAIK. I did not get any error report for the latest kernels and Lincoln also said he could not reproduce it on the latest kernels. Greetings Christoph - 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/
Re: Update Linux 2.4 Status/TODO list
[EMAIL PROTECTED] writes: * SHM segments not always being detached and destroyed right ? (problem reported by Lincoln Dale) This problem is not reproducible AFAIK. I did not get any error report for the latest kernels and Lincoln also said he could not reproduce it on the latest kernels. Greetings Christoph - 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/
Re: Update Linux 2.4 Status/TODO list
On 13 Sep 2000, at 22:37, Andre Hedrick wrote: Ted and LT, I think this are the two things you wanted that were located in: /src/tar-files/testing/direct_add/ht6560b.c /src/tar-files/testing/direct_add/qd65xx.c /src/tar-files/testing/direct_add/qd65xx.h First Petr and Samuel, are these good to go into 2.4.0 ?? I'm sorry, I don't know, I have no time to test these drivers now and I have received no help from you regarding test methodology so far, so I have even no idea how to test these drivers. Everything what I know about IDE VLB chips is at http://www.ryston.cz/petr/vlb/ and there is also a list of VLB IDE controllers I own. I also own several ide drives - old Alps DR-312C, ST3120A, WDC: AC340, AC22100, AC33100, AC24300 and other and some ATAPI CD-ROMS. As a test box I can use OPTi895 motherboard with 32 MB RAM and AM486DX5-133 processor, I have also A80486DX-50 processor for testing 50 MHz VLB bus. So if anybody give me exact test directions, I'm able to do these tests if they will be not too much time consuming. But please no "compile the kernel" or "make some copy" advices. In fact, I think at first shall be all IDE/ATA/ATAPI drivers tested whether they give correct timing on IDE bus according ATA/ATAPI specifications and with various load. Then problem drives can be tested. But it needs good laboratory equipment. Back to a.m. drivers. What about the problem with region stuff? Was it rectified already? Best Regards, Petr Soucek Ryston Electronics s.r.o. Modranska 621/72 CZ-143 00 Praha 4, Czech Republic tel +420-2-6130fax +420-2-61302211 Email: [EMAIL PROTECTED] http://www.ryston.cz - 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/
Re: Update Linux 2.4 Status/TODO list
On Sep 15, Alexander Viro <[EMAIL PROTECTED]> wrote: >> I tried doing that for Andrea but I think it's not useful, active is >> mmapped and strace shows nothing interesting. >mmapped... Does mmap() go past the end of file? I asked INN developers and they think it should not. The file size is fixed and its fields are updated in place. >> >BTW, how does test8+patch to block_truncate_page() behave? There is no change, yesterday at shutdown the active file has not been updated. -- ciao, Marco - 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/
Re: Update Linux 2.4 Status/TODO list
On Sep 15, Alexander Viro [EMAIL PROTECTED] wrote: I tried doing that for Andrea but I think it's not useful, active is mmapped and strace shows nothing interesting. mmapped... Does mmap() go past the end of file? I asked INN developers and they think it should not. The file size is fixed and its fields are updated in place. BTW, how does test8+patch to block_truncate_page() behave? There is no change, yesterday at shutdown the active file has not been updated. -- ciao, Marco - 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/
Re: Update Linux 2.4 Status/TODO list
On Fri, 15 Sep 2000, Marco d'Itri wrote:
> On Sep 14, Alexander Viro <[EMAIL PROTECTED]> wrote:
>
> >> - the whole active file is now 100% identical to the saved copy
> >Ugh... How about relevant subset of strace?
> I tried doing that for Andrea but I think it's not useful, active is
> mmapped and strace shows nothing interesting.
mmapped... Does mmap() go past the end of file?
> >> Right now it happened after the daily expire run: I stopped INN and the
> >> file on disk changed to the copy I saved before expire started.
> >Wait a minute. I don't believe in on-disk file being restored by magic,
> >but I could believe in page(s) being never written to disk and giving the
> >impression of "update that doesn't stick". You have a file shorter than
> Sure, this is what I meant.
> But what about the mtime which does not get updated?
Well, _that_ makes perfect sense - after all, you update mtime when you
write the data and that is the part that didn't happen.
> >BTW, how does test8+patch to block_truncate_page() behave?
> I missed it, do you still have the patch?
Sure. Apply to fs/buffer.c:
@@ -1758,13 +1758,14 @@
pos += blocksize;
}
+ err = 0;
+ if (!buffer_mapped(bh)) {
+ get_block(inode, iblock, bh, 0);
+ if (!buffer_mapped(bh))
+ goto unlock;
+ }
+
if (!buffer_uptodate(bh)) {
- err = 0;
- if (!buffer_mapped(bh)) {
- get_block(inode, iblock, bh, 0);
- if (!buffer_mapped(bh))
- goto unlock;
- }
err = -EIO;
bh->b_end_io = end_buffer_io_sync;
ll_rw_block(READ, 1, );
-
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/
Re: Update Linux 2.4 Status/TODO list
On Sep 14, Alexander Viro <[EMAIL PROTECTED]> wrote: >> - the whole active file is now 100% identical to the saved copy >Ugh... How about relevant subset of strace? I tried doing that for Andrea but I think it's not useful, active is mmapped and strace shows nothing interesting. >> Right now it happened after the daily expire run: I stopped INN and the >> file on disk changed to the copy I saved before expire started. >Wait a minute. I don't believe in on-disk file being restored by magic, >but I could believe in page(s) being never written to disk and giving the >impression of "update that doesn't stick". You have a file shorter than Sure, this is what I meant. But what about the mtime which does not get updated? >BTW, how does test8+patch to block_truncate_page() behave? I missed it, do you still have the patch? >And what is the block size on your fs? Filesystem revision #:1 (dynamic) Filesystem features: filetype sparse_super Block size: 4096 -- ciao, Marco - 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/
Re: Update Linux 2.4 Status/TODO list
I have an alpha noritake that won't run any 2.4.0-test kernel (last 2 tried were -test6 and 7) 7 seems to think that all pci devices are on irq 0 -- Lab tests show that use of micro$oft causes cancer in lab animals - 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/
Re: Update Linux 2.4 Status/TODO list
Arnaldo Carvalho de Melo writes: > - prumpf suggested, rmk agreed > > - get rid of save_flags_cli, use local_irq_save instead or use spin_lock_irqsave() when it makes more sense (ie, when something may be shared, or when its not truely local to the CPU). There are now some ARM boards out there which have the ability to have more than one processor on them. (*note in big red flashing letters* I'm NOT saying SMP here). _ |_| - ---+---+- | | Russell King[EMAIL PROTECTED] --- --- | | | | http://www.arm.linux.org.uk/personal/aboutme.html / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ - /\\\ | - 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/
Re: Update Linux 2.4 Status/TODO list
Arnaldo Carvalho de Melo writes: - prumpf suggested, rmk agreed - get rid of save_flags_cli, use local_irq_save instead or use spin_lock_irqsave() when it makes more sense (ie, when something may be shared, or when its not truely local to the CPU). There are now some ARM boards out there which have the ability to have more than one processor on them. (*note in big red flashing letters* I'm NOT saying SMP here). _ |_| - ---+---+- | | Russell King[EMAIL PROTECTED] --- --- | | | | http://www.arm.linux.org.uk/personal/aboutme.html / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ - /\\\ | - 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/
Re: Update Linux 2.4 Status/TODO list
On Fri, 15 Sep 2000, Marco d'Itri wrote:
On Sep 14, Alexander Viro [EMAIL PROTECTED] wrote:
- the whole active file is now 100% identical to the saved copy
Ugh... How about relevant subset of strace?
I tried doing that for Andrea but I think it's not useful, active is
mmapped and strace shows nothing interesting.
mmapped... Does mmap() go past the end of file?
Right now it happened after the daily expire run: I stopped INN and the
file on disk changed to the copy I saved before expire started.
Wait a minute. I don't believe in on-disk file being restored by magic,
but I could believe in page(s) being never written to disk and giving the
impression of "update that doesn't stick". You have a file shorter than
Sure, this is what I meant.
But what about the mtime which does not get updated?
Well, _that_ makes perfect sense - after all, you update mtime when you
write the data and that is the part that didn't happen.
BTW, how does test8+patch to block_truncate_page() behave?
I missed it, do you still have the patch?
Sure. Apply to fs/buffer.c:
@@ -1758,13 +1758,14 @@
pos += blocksize;
}
+ err = 0;
+ if (!buffer_mapped(bh)) {
+ get_block(inode, iblock, bh, 0);
+ if (!buffer_mapped(bh))
+ goto unlock;
+ }
+
if (!buffer_uptodate(bh)) {
- err = 0;
- if (!buffer_mapped(bh)) {
- get_block(inode, iblock, bh, 0);
- if (!buffer_mapped(bh))
- goto unlock;
- }
err = -EIO;
bh-b_end_io = end_buffer_io_sync;
ll_rw_block(READ, 1, bh);
-
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/
Re: Update Linux 2.4 Status/TODO list
Ted and LT, I think this are the two things you wanted that were located in: /src/tar-files/testing/direct_add/ht6560b.c /src/tar-files/testing/direct_add/qd65xx.c /src/tar-files/testing/direct_add/qd65xx.h First Petr and Samuel, are these good to go into 2.4.0 ?? Cheers, Andre Hedrick The Linux ATA/IDE guy /* * TEMPORARY VERSION FOR HT6560A MODEL TESTING! * * MODIFIED FOR BOTH A AND B VERSIONS * 2000-07-16 Petr Soucek <[EMAIL PROTECTED]> */ /* * linux/drivers/block/ht6560b.c Version 0.07Feb 1, 2000 * * Copyright (C) 1995-2000 Linus Torvalds & author (see below) */ /* * * Version 0.01Initial version hacked out of ide.c * * Version 0.02Added support for PIO modes, auto-tune * * Version 0.03Some cleanups * * Version 0.05PIO mode cycle timings auto-tune using bus-speed * * Version 0.06Prefetch mode now defaults no OFF. To set * prefetch mode OFF/ON use "hdparm -p8/-p9". * Unmask irq is disabled when prefetch mode * is enabled. * * Version 0.07Trying to fix CD-ROM detection problem. * "Prefetch" mode bit OFF for ide disks and * ON for anything else. * * * HT-6560B EIDE-controller support * To activate controller support use kernel parameter "ide0=ht6560b". * Use hdparm utility to enable PIO mode support. * * Author:Mikko Ala-Fossi<[EMAIL PROTECTED]> * Jan Evert van Grootheest <[EMAIL PROTECTED]> * * Try: http://www.maf.iki.fi/~maf/ht6560b/ */ #define HT6560B_VERSION "v0.07" #undef REALLY_SLOW_IO /* most systems can safely undef this */ #include #include #include #include #include #include #include #include #include #include #include #include #include "ide_modes.h" #define DEBUG /* remove comments for DEBUG messages */ /* * The special i/o-port that HT-6560B uses to configuration: *bit0 (0x01): "1" selects secondary interface *bit2 (0x04): "1" enables FIFO function *bit5 (0x20): "1" enables prefetched data read function (???) * * The special i/o-port that HT-6560A uses to configuration: *bit0 (0x01): "0" selects secondary interface *bit1 (0x02): "0" enables prefetched data read function *bit2 (0x04): "0" enables multi-master system(?) *bit3 (0x08): "1" 3 cycle time, "0" 2 cycle time (?) */ #define HT_CONFIG_PORT0x3e6 #define HT_CONFIG(drivea) (byte)(((drivea)->drive_data & 0xff00) >> 8) /* * FIFO + PREFETCH (both a/b-model) */ #define HT_CONFIG_DEFAULT 0x1c /* no prefetch */ /* #define HT_CONFIG_DEFAULT 0x3c */ /* with prefetch */ #define HT_CONFIG_DEFAULT_A 0x0f /* no prefetch */ /* #define HT_CONFIG_DEFAULT_A 0x0d */ /* with prefetch */ #define HT_SECONDARY_IF 0x01 #define HT_PREFETCH_MODE 0x20 #define HT_PREFETCH_MODE_A 0x02 /* * ht6560b Timing values: * * I reviewed some assembler source listings of htide drivers and found * out how they setup those cycle time interfacing values, as they at Holtek * call them. IDESETUP.COM that is supplied with the drivers figures out * optimal values and fetches those values to drivers. I found out that * they use IDE_SELECT_REG to fetch timings to the ide board right after * interface switching. After that it was quite easy to add code to * ht6560b.c. * * IDESETUP.COM gave me values 0x24, 0x45, 0xaa, 0xff that worked fine * for hda and hdc. But hdb needed higher values to work, so I guess * that sometimes it is necessary to give higher value than IDESETUP * gives. [see cmd640.c for an extreme example of this. -ml] * * Perhaps I should explain something about these timing values: * The higher nibble of value is the Recovery Time (rt) and the lower nibble * of the value is the Active Time (at). Minimum value 2 is the fastest and * the maximum value 15 is the slowest. Default values should be 15 for both. * So 0x24 means 2 for rt and 4 for at. Each of the drives should have * both values, and IDESETUP gives automatically rt=15 st=15 for CDROMs or * similar. If value is too small there will be all sorts of failures. * * Timing byte consists of * High nibble: Recovery Cycle Time (rt) * The valid values range from 2 to 15. The default is 15. * * Low nibble: Active Cycle Time(at) * The valid values range from 2 to 15. The default is 15. * * You can obtain optimized timing values by running Holtek IDESETUP.COM * for DOS. DOS drivers get their timing values from command line, where * the first value is the Recovery Time and the second value is the * Active Time for each drive. Smaller value gives higher speed. * In case of failures you should probably fall back to a higher value. */ #define
Re: Update Linux 2.4 Status/TODO list
On Wed, 13 Sep 2000, Marco d'Itri wrote: > On Sep 13, [EMAIL PROTECTED] wrote: > > > * Innd data corruption, probably caused by bug truncation bug (Rik > > van Riel) > This bug has not been fixed, I can still reproduce it (but not every > time). This is how it happens: > > - INN (1.7.2+insync+other patches, the debian package I maintain) is > running > - active is correct > - I post an article, which is filed with the correct number > - for *this group only* the high value is wrong and equal to the one > in the active file I precedently saved (in some cases this does not > happen and I can't notice anything wrong in the active file) > - I stop INN > - the whole active file is now 100% identical to the saved copy Ugh... How about relevant subset of strace? > Right now it happened after the daily expire run: I stopped INN and the > file on disk changed to the copy I saved before expire started. Wait a minute. I don't believe in on-disk file being restored by magic, but I could believe in page(s) being never written to disk and giving the impression of "update that doesn't stick". You have a file shorter than one page, so in principle it seems to point to the handling of partially truncated pages. Hmm... BTW, how does test8+patch to block_truncate_page() behave? And what is the block size on your fs? - 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/
Re: Update Linux 2.4 Status/TODO list
"Theodore Y. Ts'o" wrote: >Date: Tue, 12 Sep 2000 23:55:55 -0700 >From: David Ford <[EMAIL PROTECTED]> > >Please add 'APM resume returns the machine to the first tty, crashes >X' This appeared w/ test8. If this is intended, I'd be very happy to >know if so and I can write in to xfree86 about it. If not >intended..fix needed. > > Can you send more information? Hardware, etc. Do we know whether this > is a hardware specific problem, or a more general problem? (To several people) Yes, I will. Until later this evening I need my laptop for work. This evening I'll grab the serial cable and start making kernels and modules. AFAIK, this is a kernel issue, going backwards to a kernel that doesn't switch back to the first tty on resume, X remains in control of the screen and is quite happy. The first kernel that resumes and jumps back to the first tty, X crashes. Doing a gdb on it yields a writev() that results in a segfault. I'll do these two problems individually. >> 10. To Do But Non Showstopper >> * PCMCIA/Cardbus hangs (Basically unusable - Hinds pcmcia code is >>reliable) >> + PCMCIA crashes on unloading pci_socket > >With test8, pcmcia either with kernel code, mixed, or dhinds code; >nothing is usable. > > Can you send more details? I don't have a scratch laptop to try 2.4.0, > and I'm too chicken to put it there. (My laptop has to work; it's a > production machine; failure is not an option. Among other things, the > master 2.4.0 bug list lives there. :-) > >> * cdrecord doesn't work (produces CD-ROM coasters) w/o any errors >>reported, works under 2.2 (Damon LoCascio) > >Hmm, upgrade cdrecord perhaps? I'm using the second to last release and I'm >not burning coasters. cdrecord is undergoing a scsi subsystem rewrite. > > According to Damon LoCascio, he's using the latest cdrecord. > > Kernel : 2.4.0-test5 > SCSI: Advansys APB940U Quad scsi controller > CDRW: Yamaha 8824CDRW > CPU : AMD K6-III @450 MHz > Mem : 256Mb > MB : FIC 503+ > CDrecord: 1.6, 1.81, 1.9, 1.10 > > He says that it works just fine under 2.2.16, and he's seeing subtle > data corruption problems under 2.4 (sometimes only 100 bytes between > binary files). It could be a hardware problem where the 2.4 kernel is > stressing things more than the 2.2 kernel; or it could be a SCSI > controller specific problem. It's not clear. > >> Fixed >> * Keyboard/mouse problems (should be fixed?) > >Related to pcmcia, no, not fixed. Certain mixes of drivers and hardware can >stick the interrupt until they're removed and a different card inserted. > > Can you give more information on this one? What specifically is going > on? There's no name associated with it, which means it was entered > while Alan was maintaining the list, so I have no history associated > with it. (For that matter, it may be referring to different problem > from the one you're seeing now.) > > Thanks for the update, and your comments. (The rest of your comments > will be on the linux24.sourceforge.net web page shortly.) > > - Ted Certainly. I amonst others reported the key/mouse issue many kernels back and it was a guess game for a while then Linus said the yenta was a red herring. I don't have that email anymore but there's a lot of detail to the key/mouse/pcmcia story and I'll dig it all up and write it out again. Basically I believe the kernel pcmcia code is off by one in the socket numbering as dhinds socket numbering works and w/ the kernel, one socket hangs the machine and the other socket appears to be numbered as #0 where w/ dhinds it was #1. It seems to wedge something physically because my laptop will forever hang at maestro init after trying to use the top socket w/ the kernel pcmcia. I have to remove all power then it will boot up past the maestro init. Note, the machine isn't hard hung at maestro, the magic key works. It just won't proceed through the boot. More to come this evening. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:http://www.kalifornia.com/images/paradise.jpg"> adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
Re: Update Linux 2.4 Status/TODO list
"Theodore Y. Ts'o" wrote: >Date: Tue, 12 Sep 2000 23:37:57 -0700 >From: David Ford <[EMAIL PROTECTED]> > >> > 4. Boot Time Failures >> > >> > * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC >> >Versa LX with PIIX tuning) >> >> If this is a rare version of the BX/LX that has a no fix errata, then it >> will be messy to issue resets to get out of the loop. >> >> > * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) >> >> Need more details of how APM/ACPI is dorking with DMA settins by the OEM. > >These two are both reported by me, are the same issue. The exact >same kernel, one with PIIXn tuning enabled, will hang the hardware on >boot requiring a physical power loss to restart. > > Ah, OK, thanks. I've collapsed the two bug reports. (The first one was > added by Alan, and his lists didn't give any indication as to two > reported the problem, so I didn't realize they were the same problem.) > > - Ted Just to clarify, I meant the two PIIX entries. The ACPI/APM line got in there by mistake. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:http://www.kalifornia.com/images/paradise.jpg"> adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
Re: Update Linux 2.4 Status/TODO list
"Theodore Y. Ts'o" wrote: > >Date:Wed, 13 Sep 2000 08:46:00 +0200 >From: Harald Dunkel <[EMAIL PROTECTED]> > >How can I submit a bug report to be added to this list? > > I *try* to follow bug reports sent to Linux-kernel, but if you want to > be sure, send it directly to me ([EMAIL PROTECTED]). > > (And now for the standard spiel of developers everywhere.) > > [ This has been explicitly cc'ed to Richard Gooch so he can add it to > the linux-kernel FAQ (http://www.tux.org/lkml/). There is a section > about bug reporting, but it's a bit thin. The old-kernel-faq maintained > by Frohwalt Egerer has a lot more to say on this topic; what follows > below has taken some ideas and lists from the old faq. ] > > Please follow general good bug reporting guidelines: Remember, the > developers don't have access to your system, and they're not mind > readers. Tell us which kernel version, and what your hardware is (if > you're not sure, more details is better than less). At the very least, [...] Don't forget we have linux/REPORTING-BUGS. If that is missing some good suggestions, update that too... Jeff -- Jeff Garzik | Windows NT Performance, Building 1024| on the next "In Search Of" MandrakeSoft, Inc. | - 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/
Re: Update Linux 2.4 Status/TODO list
On Sep 13, [EMAIL PROTECTED] wrote: > * Innd data corruption, probably caused by bug truncation bug (Rik > van Riel) This bug has not been fixed, I can still reproduce it (but not every time). This is how it happens: - INN (1.7.2+insync+other patches, the debian package I maintain) is running - active is correct - I post an article, which is filed with the correct number - for *this group only* the high value is wrong and equal to the one in the active file I precedently saved (in some cases this does not happen and I can't notice anything wrong in the active file) - I stop INN - the whole active file is now 100% identical to the saved copy And the file mtime has not been updated (this time since the precedent day): -rw-r--r--1 news news 3075 Sep 10 00:02 active This happens on my personal workstation with plenty of free RAM and a tiny UUCP feed. Right now it happened after the daily expire run: I stopped INN and the file on disk changed to the copy I saved before expire started. Linux wonderland.linux.it 2.4.0-test8 #4 Sat Sep 9 23:45:09 CEST 2000 i586 unknown /dev/ide/host0/bus0/target0/lun0/part5 on /var type ext2 (rw,noatime) -- ciao, Marco - 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/
Re: Update Linux 2.4 Status/TODO list
On Wed, 13 Sep 2000, Alan Cox wrote: > > > * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) > > > > Need more details of how APM/ACPI is dorking with DMA settins by the OEM. > > Case 1 I've seen is assuming windows put the drive back into PIO no multimode > before letting the bios suspend (for suspend to disk) > Case 2 I've seen is coming back from the BIOS with the controller in PIO > non multimode and forgetting the previous settings This is why I was wanting to buffer setting in the driver and offer APM/ACPI the callout to prevent this. Again you would have the option of invoking spin-up by APM attempts or using taskfile commands to brut force it into life. 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 PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Update Linux 2.4 Status/TODO list
David Ford wrote: > > Andre Hedrick wrote: > > > > 4. Boot Time Failures > > > > > > * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC > > >Versa LX with PIIX tuning) > > > > If this is a rare version of the BX/LX that has a no fix errata, then it > > will be messy to issue resets to get out of the loop. > > > > > * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) > > > > Need more details of how APM/ACPI is dorking with DMA settins by the OEM. > > These two are both reported by me, are the same issue. The exact same kernel, > one with PIIXn tuning enabled, will hang the hardware on boot requiring a > physical power loss to restart. > > No tuning options applied, only the capability enabled in the kernel, makes it > crash. > > If necessary I can again provide the boot log and a verbose lspci and whatever > else is desired. I'll even let you log in and look at it. > I have the very same problem with my system w/ PIIXn enabled on 2.4.0-test8, BP6 MB. If you need another system/person/datapoint to help narrow down the variables I can supply whatever info you may need or try various patches. Martin - 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/
Re: Update Linux 2.4 Status/TODO list
Date: Wed, 13 Sep 2000 10:03:39 +0200 From: Andries Brouwer <[EMAIL PROTECTED]> On Wed, Sep 13, 2000 at 01:56:39AM -0400, [EMAIL PROTECTED] wrote: > 8. Fix Exists But Isnt Merged ... > 9. To Do > * Mount of new fs over existing mointpoint should return an error >unless forced (Andrew McNabb, Alan Cox) Probably this belongs under 8. I posted a patch a few days ago. Thanks for the update. When the patch gets accepted into the mainline kernel, would you mind dropping me a note? I do try to scan Linus announcements, but I sometimes miss matching a bug report with his patch summaries, and it's a lot easier if I get an explicit notification from the patch author. Thanks!! - Ted - 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/
Re: Update Linux 2.4 Status/TODO list
Date: Tue, 12 Sep 2000 23:55:55 -0700 From: David Ford <[EMAIL PROTECTED]> Please add 'APM resume returns the machine to the first tty, crashes X' This appeared w/ test8. If this is intended, I'd be very happy to know if so and I can write in to xfree86 about it. If not intended..fix needed. Can you send more information? Hardware, etc. Do we know whether this is a hardware specific problem, or a more general problem? > 10. To Do But Non Showstopper > * PCMCIA/Cardbus hangs (Basically unusable - Hinds pcmcia code is >reliable) > + PCMCIA crashes on unloading pci_socket With test8, pcmcia either with kernel code, mixed, or dhinds code; nothing is usable. Can you send more details? I don't have a scratch laptop to try 2.4.0, and I'm too chicken to put it there. (My laptop has to work; it's a production machine; failure is not an option. Among other things, the master 2.4.0 bug list lives there. :-) > * cdrecord doesn't work (produces CD-ROM coasters) w/o any errors >reported, works under 2.2 (Damon LoCascio) Hmm, upgrade cdrecord perhaps? I'm using the second to last release and I'm not burning coasters. cdrecord is undergoing a scsi subsystem rewrite. According to Damon LoCascio, he's using the latest cdrecord. Kernel : 2.4.0-test5 SCSI: Advansys APB940U Quad scsi controller CDRW: Yamaha 8824CDRW CPU : AMD K6-III @450 MHz Mem : 256Mb MB : FIC 503+ CDrecord: 1.6, 1.81, 1.9, 1.10 He says that it works just fine under 2.2.16, and he's seeing subtle data corruption problems under 2.4 (sometimes only 100 bytes between binary files). It could be a hardware problem where the 2.4 kernel is stressing things more than the 2.2 kernel; or it could be a SCSI controller specific problem. It's not clear. > Fixed > * Keyboard/mouse problems (should be fixed?) Related to pcmcia, no, not fixed. Certain mixes of drivers and hardware can stick the interrupt until they're removed and a different card inserted. Can you give more information on this one? What specifically is going on? There's no name associated with it, which means it was entered while Alan was maintaining the list, so I have no history associated with it. (For that matter, it may be referring to different problem from the one you're seeing now.) Thanks for the update, and your comments. (The rest of your comments will be on the linux24.sourceforge.net web page shortly.) - Ted - 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/
Re: Update Linux 2.4 Status/TODO list
Em Wed, Sep 13, 2000 at 01:56:39AM -0400, [EMAIL PROTECTED] escreveu: > 9. To Do > > * Check all devices use resources properly (Everyone now has to use >request_region and check the return since we no longer single >thread driver inits in all module cases. Also memory regions are >now requestable and a lot of old drivers dont know this yet. -- >Alan Cox) I've been doing this for quite a while, there's lots of patches fixing this still pending integration > * Tulip hang on rmmod/crashes sometimes > * Devfs races (mostly done - Al Viro) > * Fix further NFS races (Al Viro) > * Test other file systems on write > * Fix mount failures due to copy_* user mishandling not necessarily for mount failures, but I've been fixing/cleaning up copy_*_usage > + Dawson Engler's list of potential kmalloc/kfree bugs been fixing this as well for quite some time, lots of patches pending integration And here is my current TODO list, maybe some itens should be merged to this larger list: - get rid of check_region, use just request_region checking its return (2.2 request_region returned void) and now the driver init sequence is not to be serialized anymore, so races are possible (look at cardbus/pcihotplug code) - check isapnp.c: doesn't release regions on failure - request_irq needs to be checked - check all init_etherdev return - drivers allocating net_device with init_etherdev doesn't need zeroing it (init_etherdev does this for us) - check all kmalloc, vmaloc, skb_alloc, etcalloc - check drivers/char/ip2main.c - register_netdev has to be checked as well - release previously successful allocations on failure - use forward gotos to release previously successfull allocations - convert drivers to new PCI API - remove uneeded historic code - checking for NULL on probe routines for net drivers - proc_register() is dead. Use create_proc_read_entry() instead. (from Al Viro on lkml) - check proc_*_create result, again, it can fail, and is common (bad) practice in most of the kernel sources - check freeing skbs with kfree instead of kfree_skb - get rid of panic function in drivers (watchdogs need to use machine_restart instead of panic 8) ) - several char drivers do this happily :( - get rid of isa_read/write[bwl], use ioremap instead - sed s/return EWHATEVER/return -EWHATEVER/ - check misc_register return (yes, it can fail, murphy's law applies here as well) - converting cli to spinlocks (look at net/netrom/*.c, net/ipx/*.c, etc) - get rid of verify_area with copy_*_user get/put_user, only needed if using __copy_*_user et al - to make sure that copy_to_user et all are checked - look at drivers/char/generic_serial.c - look at drivers/char/n_tty.c - use "return copy_to_user(...) ? -EFAULT : ok_value;" - check drivers/char/dz.c wrt return copy*user(...); has to be ... ? -EFAULT : 0; - prumpf suggested: - make sure drivers never read loops_per_sec - it might change under them - fix watchdog drivers to use link order rather than explicit initialization calls (i810 is particularly broken) - get rid of init_module / cleanup_module (softdog in particular) - make sure BUG() is used correctly (i.e. if(function()) BUG(); is evil) i.e. even when no opping BUG we still have an if - get rid of if (p) kfree(p); style constructs - kfree(NULL) is a nop and it shortens the code path - prumpf suggested, rmk agreed - get rid of save_flags_cli, use local_irq_save instead Maybe: - check drivers/scsi/ips.c for resource leaks (ips_release doesn't seems to release all the kmalloc memory it got in ips_detect. (quick look) = DONE = - get rid of copy_to_user_ret et all (Linus call) (davem) - 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/
Re: Update Linux 2.4 Status/TODO list
Date:Wed, 13 Sep 2000 08:46:00 +0200 From: Harald Dunkel <[EMAIL PROTECTED]> How can I submit a bug report to be added to this list? I *try* to follow bug reports sent to Linux-kernel, but if you want to be sure, send it directly to me ([EMAIL PROTECTED]). (And now for the standard spiel of developers everywhere.) [ This has been explicitly cc'ed to Richard Gooch so he can add it to the linux-kernel FAQ (http://www.tux.org/lkml/). There is a section about bug reporting, but it's a bit thin. The old-kernel-faq maintained by Frohwalt Egerer has a lot more to say on this topic; what follows below has taken some ideas and lists from the old faq. ] Please follow general good bug reporting guidelines: Remember, the developers don't have access to your system, and they're not mind readers. Tell us which kernel version, and what your hardware is (if you're not sure, more details is better than less). At the very least, tell us what processor and motherboard you have, how much memory, how many and what kind of disks (IDE, SCSI, etc.), what kind of disk controllers you have, what other expansion boards (specify whether they're PCI or ISA or some other bus). Also useful: what version of gcc and binutils were used to compile the kernel. Try to find a simple, reliable way to trigger the problem. Telling the developer that they have to set up some complicated application environment (especially if it involves some ghastly expensive proprietary software like SAP or Oracle :-) may cause the developer to hit the 'd' key and move on. In general, raw data is better than jumping to conclusions. If you want to give your guesses in your bug reports, they're of course welcome, but this is *not* a substitute for raw data. Many problems are not what they first seem. A hardware problem can masquerade as a VM problem. A device driver or VM problem can cause the filesystem code to notice a discrepancy, and flag a warning. Even if you're *sure* that the problem isn't a hardware problem, or by some other theory that the developer advances, the scientific method demands that you do a test to rule these sorts of things out. Sometimes, you will get surprised. If you get a kernel oops message, it's useless unless you give us the proper symbolic information. This used to mean sending relevant pieces out of System.map. Fortunately, with the latest syslogd/klogd, this is much simpler (check the man page of klogd to see if your version has this feature; if it doesn't, you should upgrade to the latest version, and probably to a modern distribution). Make sure that you have the System.map file installed the appropriate place so that klogd can find it (the standard search path is in the /boot, /, and /usr/src/linux directories). If the system oops and then dies without a chance for klogd to record the information into a syslog file, copy down the oops message exactly, and then use the ksymoops (see the man page) to get the symbolic information out. Remember, the raw numbers by themselves will generally not be useful. If you can, try to isolate the problem to a specific kernel version. Knowledge that it worked in version 2.2.17, as well as 2.3.0-test6, but it stopped working in 2.3.0-test7-pre1, is extremely helpful, and will save developers a lot of time. (If you're comfortable disecting patches, fell free, taking apart the individual file changes and try to isolate to a particular change.) - Ted - 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/
Re: Update Linux 2.4 Status/TODO list
Date: Tue, 12 Sep 2000 23:37:57 -0700 From: David Ford <[EMAIL PROTECTED]> > > 4. Boot Time Failures > > > > * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC > >Versa LX with PIIX tuning) > > If this is a rare version of the BX/LX that has a no fix errata, then it > will be messy to issue resets to get out of the loop. > > > * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) > > Need more details of how APM/ACPI is dorking with DMA settins by the OEM. These two are both reported by me, are the same issue. The exact same kernel, one with PIIXn tuning enabled, will hang the hardware on boot requiring a physical power loss to restart. Ah, OK, thanks. I've collapsed the two bug reports. (The first one was added by Alan, and his lists didn't give any indication as to two reported the problem, so I didn't realize they were the same problem.) - Ted - 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/
Re: Update Linux 2.4 Status/TODO list
> > * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) > > Need more details of how APM/ACPI is dorking with DMA settins by the OEM. Case 1 I've seen is assuming windows put the drive back into PIO no multimode before letting the bios suspend (for suspend to disk) Case 2 I've seen is coming back from the BIOS with the controller in PIO non multimode and forgetting the previous settings > - 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/
Re: Update Linux 2.4 Status/TODO list
On Wed, Sep 13 2000, [EMAIL PROTECTED] wrote: > * Loading the qlogicfc driver in 2.4.0-test8 causes the kernel to >loop forver reporting SCSI disks that aren't present (Paul >Hubbard) This is probaly due to the module_init/exit stuff that got into test8. I have already sent Linus a patch, but I still need to verify this with Paul Hubbard. -- Torben Mathiasen <[EMAIL PROTECTED]> Linux ThunderLAN maintainer http://tlan.kernel.dk - 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/
Re: Update Linux 2.4 Status/TODO list
David Ford wrote:
>
> > 10. To Do But Non Showstopper
> > * PCMCIA/Cardbus hangs (Basically unusable - Hinds pcmcia code is
> >reliable)
> > + PCMCIA crashes on unloading pci_socket
>
> With test8, pcmcia either with kernel code, mixed, or dhinds code; nothing is
> usable.
David,
I'll take a stab at this while my PCMCIA memories are fresh. Can you
please try the attached patch and, when it doesn't work, send me all the
usual details?
--- linux-2.4.0-test8/include/pcmcia/ss.h Sat Sep 9 16:19:30 2000
+++ linux-akpm/include/pcmcia/ss.h Wed Sep 13 00:13:06 2000
@@ -82,6 +82,7 @@
#define SS_DMA_MODE0x0080
#define SS_SPKR_ENA0x0100
#define SS_OUTPUT_ENA 0x0200
+#define SS_DEBOUNCED 0x0400 /* Tell driver that the debounce delay has ended */
/* Flags for I/O port and memory windows */
#define MAP_ACTIVE 0x01
--- linux-2.4.0-test8/drivers/pcmcia/cardbus.c Sat Sep 9 16:19:26 2000
+++ linux-akpm/drivers/pcmcia/cardbus.c Wed Sep 13 00:13:06 2000
@@ -58,11 +58,6 @@
#include
#include
-#ifndef PCMCIA_DEBUG
-#define PCMCIA_DEBUG 1
-#endif
-static int pc_debug = PCMCIA_DEBUG;
-
#define IN_CARD_SERVICES
#include
#include
@@ -72,6 +67,11 @@
#include
#include "cs_internal.h"
#include "rsrc_mgr.h"
+
+#ifndef PCMCIA_DEBUG
+#define PCMCIA_DEBUG 1
+#endif
+static int pc_debug = PCMCIA_DEBUG;
/**/
--- linux-2.4.0-test8/drivers/pcmcia/cs.c Sat Sep 9 16:19:26 2000
+++ linux-akpm/drivers/pcmcia/cs.c Wed Sep 13 00:13:06 2000
@@ -103,13 +103,13 @@
#define INT_MODULE_PARM(n, v) static int n = v; MODULE_PARM(n, "i")
-INT_MODULE_PARM(setup_delay, HZ/20); /* ticks */
-INT_MODULE_PARM(resume_delay, HZ/5); /* ticks */
-INT_MODULE_PARM(shutdown_delay,HZ/40); /* ticks */
-INT_MODULE_PARM(vcc_settle,400); /* msecs */
+INT_MODULE_PARM(setup_delay, 10);/* centiseconds */
+INT_MODULE_PARM(resume_delay, 20);/* centiseconds */
+INT_MODULE_PARM(shutdown_delay,3); /* centiseconds */
+INT_MODULE_PARM(vcc_settle,40);/* centiseconds */
INT_MODULE_PARM(reset_time,10);/* usecs */
-INT_MODULE_PARM(unreset_delay, 100); /* msecs */
-INT_MODULE_PARM(unreset_check, 100); /* msecs */
+INT_MODULE_PARM(unreset_delay, 10);/* centiseconds */
+INT_MODULE_PARM(unreset_check, 10);/* centiseconds */
INT_MODULE_PARM(unreset_limit, 30);/* unreset_check's */
/* Access speed for attribute memory windows */
@@ -446,10 +446,13 @@
static int send_event(socket_info_t *s, event_t event, int priority);
-static void msleep(unsigned int msec)
+/*
+ * Sleep for n_cs centiseconds (1 cs = 1/100th of a second)
+ */
+static void cs_sleep(unsigned int n_cs)
{
current->state = TASK_INTERRUPTIBLE;
- schedule_timeout( (msec * HZ + 999) / 1000);
+ schedule_timeout( (n_cs * HZ + 99) / 100);
}
static void shutdown_socket(socket_info_t *s)
@@ -504,7 +507,7 @@
if (!(val & SS_PENDING))
break;
if (--setup_timeout) {
- msleep(100);
+ cs_sleep(10);
continue;
}
printk(KERN_NOTICE "cs: socket %p voltage interrogation"
@@ -516,7 +519,7 @@
if (val & SS_DETECT) {
DEBUG(1, "cs: setup_socket(%p): applying power\n", s);
s->state |= SOCKET_PRESENT;
- s->socket.flags = 0;
+ s->socket.flags &= SS_DEBOUNCED;
if (val & SS_3VCARD)
s->socket.Vcc = s->socket.Vpp = 33;
else if (!(val & SS_XVCARD))
@@ -533,7 +536,7 @@
#endif
}
set_socket(s, >socket);
- msleep(vcc_settle);
+ cs_sleep(vcc_settle);
reset_socket(s);
ret = 1;
} else {
@@ -561,7 +564,7 @@
udelay((long)reset_time);
s->socket.flags &= ~SS_RESET;
set_socket(s, >socket);
-msleep(unreset_delay);
+cs_sleep(unreset_delay);
unreset_socket(s);
} /* reset_socket */
@@ -580,11 +583,11 @@
break;
DEBUG(2, "cs: socket %d not ready yet\n", s->sock);
if (--setup_timeout) {
- msleep(unreset_check);
+ cs_sleep(unreset_check);
continue;
}
printk(KERN_NOTICE "cs: socket %p timed out during"
- " reset\n", s);
+ " reset. Try increasing setup_delay.\n", s);
s->state &= ~EVENT_MASK;
return;
}
@@ -656,7 +659,7 @@
DEBUG(0, "cs: flushing pending setup\n");
s->state &= ~EVENT_MASK;
}
-msleep(shutdown_delay);
+
Re: Update Linux 2.4 Status/TODO list
On Tue, 12 Sep 2000, David Ford wrote:
> Please add 'Quota support causes OOPS' Someone posted a patch but I don't
> have the reference offhand. That patch appears to have fixed one person's
> problems.
[..]
>
> > * Oops in dquot_transfer (David Ford, Martin Diehl) (Jan Kara has a
> >potential patch)
>
> I believe this would be the referenced patch.
after getting some positive feedback on this patch I've just sent it to
Linus. Haven't CC'd to l-k as it was already there. I'm reposting it below
in case somebody is missing it. Alan did already include it in 2.2.18pre5
which had the same Oops introduced in 2.2.18pre4.
Martin
--- linux-2.4.0-test8/fs/dquot.c.orig Mon Sep 11 01:42:56 2000
+++ linux-2.4.0-test8/fs/dquot.cMon Sep 11 02:12:04 2000
@@ -1285,12 +1285,15 @@
blocks = isize_to_blocks(inode->i_size, BLOCK_SIZE_BITS);
else
blocks = (inode->i_blocks >> 1);
- for (cnt = 0; cnt < MAXQUOTAS; cnt++)
+ for (cnt = 0; cnt < MAXQUOTAS; cnt++) {
+ if (transfer_to[cnt] == NODQUOT)
+ continue;
if (check_idq(transfer_to[cnt], 1) == NO_QUOTA ||
check_bdq(transfer_to[cnt], blocks, 0) == NO_QUOTA) {
cnt = MAXQUOTAS;
goto put_all;
}
+ }
if ((error = notify_change(dentry, iattr)))
goto put_all;
-
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/
Re: Update Linux 2.4 Status/TODO list
On Wed, Sep 13 2000, [EMAIL PROTECTED] wrote: > * TLAN nic appears to be adding a timer twice (2.4.0test8pre6, Arjan >ve de Ven) This has been fixed, just not sent off to Linus yet. -- Torben Mathiasen <[EMAIL PROTECTED]> Linux ThunderLAN maintainer http://tlan.kernel.dk - 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/
Re: Update Linux 2.4 Status/TODO list
On Wed, Sep 13, 2000 at 01:56:39AM -0400, [EMAIL PROTECTED] wrote: > 8. Fix Exists But Isnt Merged ... > 9. To Do > * Mount of new fs over existing mointpoint should return an error >unless forced (Andrew McNabb, Alan Cox) Probably this belongs under 8. I posted a patch a few days ago. Andries - 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/
Re: Update Linux 2.4 Status/TODO list
On Tue, Sep 12, 2000 at 11:55:55PM -0700, David Ford wrote: > > * Possible ppp problem (fail to connect; may be user error; reported > >by Matt Spong; claims worked on 2.3.40) > > I use ppp frequently w/ current kernels, works fine. Most likely an user error, yes, for 2.4.0 the latest pppd is needed, older pppd's causing the above described error. -- Vojtech Pavlik SuSE Labs - 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/
Re: Update Linux 2.4 Status/TODO list
[EMAIL PROTECTED] wrote: > 8. Fix Exists But Isnt Merged Please add 'Quota support causes OOPS' Someone posted a patch but I don't have the reference offhand. That patch appears to have fixed one person's problems. > 9. To Do > * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) Actually this bug applies to all kernels as far back as early 2.3 afair. > * Oops in dquot_transfer (David Ford, Martin Diehl) (Jan Kara has a >potential patch) I believe this would be the referenced patch. Please add 'APM resume returns the machine to the first tty, crashes X' This appeared w/ test8. If this is intended, I'd be very happy to know if so and I can write in to xfree86 about it. If not intended..fix needed. > 10. To Do But Non Showstopper > * PCMCIA/Cardbus hangs (Basically unusable - Hinds pcmcia code is >reliable) > + PCMCIA crashes on unloading pci_socket With test8, pcmcia either with kernel code, mixed, or dhinds code; nothing is usable. > * RTL 8139 cards sometimes stop responding. Both drivers don't >handle this quite good enough yet. (reported by Rogier Wolff) This one can tentatively be moved into 'fixed' I was one of the people submitting this a long time ago and since that point in time numerous updates have occured and I'm now able to transfer multi-gigs of data day after day and no problems. > * USB pegasus driver doesn't work since 2.4.0test5 (David Ford) Fixed. Only thing now is cosmetic. It spews between a few and a few hundred lines to klog on disconnect. > * Possible ppp problem (fail to connect; may be user error; reported >by Matt Spong; claims worked on 2.3.40) I use ppp frequently w/ current kernels, works fine. > * cdrecord doesn't work (produces CD-ROM coasters) w/o any errors >reported, works under 2.2 (Damon LoCascio) Hmm, upgrade cdrecord perhaps? I'm using the second to last release and I'm not burning coasters. cdrecord is undergoing a scsi subsystem rewrite. > Fixed > * Keyboard/mouse problems (should be fixed?) Related to pcmcia, no, not fixed. Certain mixes of drivers and hardware can stick the interrupt until they're removed and a different card inserted. > * USB Pegasus driver explodes on disconnect (lots of printk and/or >OOPS spewage to the console. David Ford) (reported fixed by Petko >Manolov) OOPS fixed, spewage not fixed. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:http://www.kalifornia.com/images/paradise.jpg"> adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
Re: Update Linux 2.4 Status/TODO list
On Tue, Sep 12, 2000 at 11:37:57PM -0700, David Ford wrote: > > > 4. Boot Time Failures > > > > > > * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC > > >Versa LX with PIIX tuning) > > > > If this is a rare version of the BX/LX that has a no fix errata, then it > > will be messy to issue resets to get out of the loop. > > > > > * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) > > > > Need more details of how APM/ACPI is dorking with DMA settins by the OEM. > > These two are both reported by me, are the same issue. The exact same kernel, > one with PIIXn tuning enabled, will hang the hardware on boot requiring a > physical power loss to restart. > > No tuning options applied, only the capability enabled in the kernel, makes it > crash. > > If necessary I can again provide the boot log and a verbose lspci and whatever > else is desired. I'll even let you log in and look at it. I can look into this. I don't guarantee I'll find the problem, but I've got all the PIIX datasheets handy now and some time on my hands ... -- Vojtech Pavlik SuSE Labs - 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/
Re: Update Linux 2.4 Status/TODO list
Hi folks, How can I submit a bug report to be added to this list? Regards Harri - 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/
Re: Update Linux 2.4 Status/TODO list
Andre Hedrick wrote: > > 4. Boot Time Failures > > > > * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC > >Versa LX with PIIX tuning) > > If this is a rare version of the BX/LX that has a no fix errata, then it > will be messy to issue resets to get out of the loop. > > > * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) > > Need more details of how APM/ACPI is dorking with DMA settins by the OEM. These two are both reported by me, are the same issue. The exact same kernel, one with PIIXn tuning enabled, will hang the hardware on boot requiring a physical power loss to restart. No tuning options applied, only the capability enabled in the kernel, makes it crash. If necessary I can again provide the boot log and a verbose lspci and whatever else is desired. I'll even let you log in and look at it. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:http://www.kalifornia.com/images/paradise.jpg"> adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
Re: Update Linux 2.4 Status/TODO list
On Wed, 13 Sep 2000 [EMAIL PROTECTED] wrote: > 2. Capable Of Corrupting Your FS/data > > * Use PCI DMA by default in IDE is unsafe (must not do so on via >VPx, x < 3) (requires chipset tuning to be enabled according to >Andre Hedrick --- we need to turn this on by default -- TYT) VIA Chipset code now handled by Vojtech Pavlik <[EMAIL PROTECTED]> > 4. Boot Time Failures > > * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC >Versa LX with PIIX tuning) If this is a rare version of the BX/LX that has a no fix errata, then it will be messy to issue resets to get out of the loop. > * HT6560/UMC8672 ide sets up stuff too early (before region stuff >can be done) I have HT6560 fix some where ... > * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) Need more details of how APM/ACPI is dorking with DMA settins by the OEM. > * Multiwrite IDE breaks on a disk error [minor issue at best] >(hopefully fixed) Have not seen this issue lately but that may be because of TF fixes that I use. > * ACPI/APM suspend issue - IDE related stuff ? (requires full >taskfile support that was vetoed by Linus) Only the IOCTL method, but the re-write will not happen in time to make 2.4 release. > Probably Hardware Bugs > > * Data corruption on IDE disks (Generic PCI DMA and SiS support >Steven Walter) (sounds like PCChips #M599LMR motherboard doesn't >disable UDMA when a non-UDMA cable is used. If you disable UDMA in >the BIOS, then there is no problem. hardware bug?) Try newest SIS code because it supports auto-dma-downgrade if iCRC's are hit. 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 PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Update Linux 2.4 Status/TODO list
On Wed, 13 Sep 2000 [EMAIL PROTECTED] wrote: > * Fix, um, interesting races around dup2() and friends. (Al Viro) Done. > + complete the ext2 races fixes (truncate) (Al Viro) Done > + fix the UFS, minixfs and sysvfs SMP races(the latter couple > is broken as ext2 was, UFS is _completely_ broken; eats > filesystems) (Al Viro) SMP? They are reproducable on UP. Easily. And it's mostly "patch exists but is not merged". _Very_ larger one for UFS ;-/ - 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/
Re: Update Linux 2.4 Status/TODO list
On Wed, 13 Sep 2000 [EMAIL PROTECTED] wrote: 2. Capable Of Corrupting Your FS/data * Use PCI DMA by default in IDE is unsafe (must not do so on via VPx, x 3) (requires chipset tuning to be enabled according to Andre Hedrick --- we need to turn this on by default -- TYT) VIA Chipset code now handled by Vojtech Pavlik [EMAIL PROTECTED] 4. Boot Time Failures * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC Versa LX with PIIX tuning) If this is a rare version of the BX/LX that has a no fix errata, then it will be messy to issue resets to get out of the loop. * HT6560/UMC8672 ide sets up stuff too early (before region stuff can be done) I have HT6560 fix some where ... * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) Need more details of how APM/ACPI is dorking with DMA settins by the OEM. * Multiwrite IDE breaks on a disk error [minor issue at best] (hopefully fixed) Have not seen this issue lately but that may be because of TF fixes that I use. * ACPI/APM suspend issue - IDE related stuff ? (requires full taskfile support that was vetoed by Linus) Only the IOCTL method, but the re-write will not happen in time to make 2.4 release. Probably Hardware Bugs * Data corruption on IDE disks (Generic PCI DMA and SiS support Steven Walter) (sounds like PCChips #M599LMR motherboard doesn't disable UDMA when a non-UDMA cable is used. If you disable UDMA in the BIOS, then there is no problem. hardware bug?) Try newest SIS code because it supports auto-dma-downgrade if iCRC's are hit. 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 PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Update Linux 2.4 Status/TODO list
Andre Hedrick wrote: 4. Boot Time Failures * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC Versa LX with PIIX tuning) If this is a rare version of the BX/LX that has a no fix errata, then it will be messy to issue resets to get out of the loop. * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) Need more details of how APM/ACPI is dorking with DMA settins by the OEM. These two are both reported by me, are the same issue. The exact same kernel, one with PIIXn tuning enabled, will hang the hardware on boot requiring a physical power loss to restart. No tuning options applied, only the capability enabled in the kernel, makes it crash. If necessary I can again provide the boot log and a verbose lspci and whatever else is desired. I'll even let you log in and look at it. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:img src="http://www.kalifornia.com/images/paradise.jpg" adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
Re: Update Linux 2.4 Status/TODO list
Hi folks, How can I submit a bug report to be added to this list? Regards Harri - 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/
Re: Update Linux 2.4 Status/TODO list
On Tue, Sep 12, 2000 at 11:37:57PM -0700, David Ford wrote: 4. Boot Time Failures * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC Versa LX with PIIX tuning) If this is a rare version of the BX/LX that has a no fix errata, then it will be messy to issue resets to get out of the loop. * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) Need more details of how APM/ACPI is dorking with DMA settins by the OEM. These two are both reported by me, are the same issue. The exact same kernel, one with PIIXn tuning enabled, will hang the hardware on boot requiring a physical power loss to restart. No tuning options applied, only the capability enabled in the kernel, makes it crash. If necessary I can again provide the boot log and a verbose lspci and whatever else is desired. I'll even let you log in and look at it. I can look into this. I don't guarantee I'll find the problem, but I've got all the PIIX datasheets handy now and some time on my hands ... -- Vojtech Pavlik SuSE Labs - 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/
Re: Update Linux 2.4 Status/TODO list
[EMAIL PROTECTED] wrote: 8. Fix Exists But Isnt Merged Please add 'Quota support causes OOPS' Someone posted a patch but I don't have the reference offhand. That patch appears to have fixed one person's problems. 9. To Do * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) Actually this bug applies to all kernels as far back as early 2.3 afair. * Oops in dquot_transfer (David Ford, Martin Diehl) (Jan Kara has a potential patch) I believe this would be the referenced patch. Please add 'APM resume returns the machine to the first tty, crashes X' This appeared w/ test8. If this is intended, I'd be very happy to know if so and I can write in to xfree86 about it. If not intended..fix needed. 10. To Do But Non Showstopper * PCMCIA/Cardbus hangs (Basically unusable - Hinds pcmcia code is reliable) + PCMCIA crashes on unloading pci_socket With test8, pcmcia either with kernel code, mixed, or dhinds code; nothing is usable. * RTL 8139 cards sometimes stop responding. Both drivers don't handle this quite good enough yet. (reported by Rogier Wolff) This one can tentatively be moved into 'fixed' I was one of the people submitting this a long time ago and since that point in time numerous updates have occured and I'm now able to transfer multi-gigs of data day after day and no problems. * USB pegasus driver doesn't work since 2.4.0test5 (David Ford) Fixed. Only thing now is cosmetic. It spews between a few and a few hundred lines to klog on disconnect. * Possible ppp problem (fail to connect; may be user error; reported by Matt Spong; claims worked on 2.3.40) I use ppp frequently w/ current kernels, works fine. * cdrecord doesn't work (produces CD-ROM coasters) w/o any errors reported, works under 2.2 (Damon LoCascio) Hmm, upgrade cdrecord perhaps? I'm using the second to last release and I'm not burning coasters. cdrecord is undergoing a scsi subsystem rewrite. Fixed * Keyboard/mouse problems (should be fixed?) Related to pcmcia, no, not fixed. Certain mixes of drivers and hardware can stick the interrupt until they're removed and a different card inserted. * USB Pegasus driver explodes on disconnect (lots of printk and/or OOPS spewage to the console. David Ford) (reported fixed by Petko Manolov) OOPS fixed, spewage not fixed. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:img src="http://www.kalifornia.com/images/paradise.jpg" adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
Re: Update Linux 2.4 Status/TODO list
On Tue, Sep 12, 2000 at 11:55:55PM -0700, David Ford wrote: * Possible ppp problem (fail to connect; may be user error; reported by Matt Spong; claims worked on 2.3.40) I use ppp frequently w/ current kernels, works fine. Most likely an user error, yes, for 2.4.0 the latest pppd is needed, older pppd's causing the above described error. -- Vojtech Pavlik SuSE Labs - 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/
Re: Update Linux 2.4 Status/TODO list
On Wed, Sep 13, 2000 at 01:56:39AM -0400, [EMAIL PROTECTED] wrote: 8. Fix Exists But Isnt Merged ... 9. To Do * Mount of new fs over existing mointpoint should return an error unless forced (Andrew McNabb, Alan Cox) Probably this belongs under 8. I posted a patch a few days ago. Andries - 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/
Re: Update Linux 2.4 Status/TODO list
On Wed, Sep 13 2000, [EMAIL PROTECTED] wrote: * TLAN nic appears to be adding a timer twice (2.4.0test8pre6, Arjan ve de Ven) This has been fixed, just not sent off to Linus yet. -- Torben Mathiasen [EMAIL PROTECTED] Linux ThunderLAN maintainer http://tlan.kernel.dk - 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/
Re: Update Linux 2.4 Status/TODO list
On Tue, 12 Sep 2000, David Ford wrote:
Please add 'Quota support causes OOPS' Someone posted a patch but I don't
have the reference offhand. That patch appears to have fixed one person's
problems.
[..]
* Oops in dquot_transfer (David Ford, Martin Diehl) (Jan Kara has a
potential patch)
I believe this would be the referenced patch.
after getting some positive feedback on this patch I've just sent it to
Linus. Haven't CC'd to l-k as it was already there. I'm reposting it below
in case somebody is missing it. Alan did already include it in 2.2.18pre5
which had the same Oops introduced in 2.2.18pre4.
Martin
--- linux-2.4.0-test8/fs/dquot.c.orig Mon Sep 11 01:42:56 2000
+++ linux-2.4.0-test8/fs/dquot.cMon Sep 11 02:12:04 2000
@@ -1285,12 +1285,15 @@
blocks = isize_to_blocks(inode-i_size, BLOCK_SIZE_BITS);
else
blocks = (inode-i_blocks 1);
- for (cnt = 0; cnt MAXQUOTAS; cnt++)
+ for (cnt = 0; cnt MAXQUOTAS; cnt++) {
+ if (transfer_to[cnt] == NODQUOT)
+ continue;
if (check_idq(transfer_to[cnt], 1) == NO_QUOTA ||
check_bdq(transfer_to[cnt], blocks, 0) == NO_QUOTA) {
cnt = MAXQUOTAS;
goto put_all;
}
+ }
if ((error = notify_change(dentry, iattr)))
goto put_all;
-
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/
Re: Update Linux 2.4 Status/TODO list
On Wed, Sep 13 2000, [EMAIL PROTECTED] wrote: * Loading the qlogicfc driver in 2.4.0-test8 causes the kernel to loop forver reporting SCSI disks that aren't present (Paul Hubbard) This is probaly due to the module_init/exit stuff that got into test8. I have already sent Linus a patch, but I still need to verify this with Paul Hubbard. -- Torben Mathiasen [EMAIL PROTECTED] Linux ThunderLAN maintainer http://tlan.kernel.dk - 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/
Re: Update Linux 2.4 Status/TODO list
* PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) Need more details of how APM/ACPI is dorking with DMA settins by the OEM. Case 1 I've seen is assuming windows put the drive back into PIO no multimode before letting the bios suspend (for suspend to disk) Case 2 I've seen is coming back from the BIOS with the controller in PIO non multimode and forgetting the previous settings - 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/
Re: Update Linux 2.4 Status/TODO list
Em Wed, Sep 13, 2000 at 01:56:39AM -0400, [EMAIL PROTECTED] escreveu: 9. To Do * Check all devices use resources properly (Everyone now has to use request_region and check the return since we no longer single thread driver inits in all module cases. Also memory regions are now requestable and a lot of old drivers dont know this yet. -- Alan Cox) I've been doing this for quite a while, there's lots of patches fixing this still pending integration * Tulip hang on rmmod/crashes sometimes * Devfs races (mostly done - Al Viro) * Fix further NFS races (Al Viro) * Test other file systems on write * Fix mount failures due to copy_* user mishandling not necessarily for mount failures, but I've been fixing/cleaning up copy_*_usage + Dawson Engler's list of potential kmalloc/kfree bugs been fixing this as well for quite some time, lots of patches pending integration And here is my current TODO list, maybe some itens should be merged to this larger list: - get rid of check_region, use just request_region checking its return (2.2 request_region returned void) and now the driver init sequence is not to be serialized anymore, so races are possible (look at cardbus/pcihotplug code) - check isapnp.c: doesn't release regions on failure - request_irq needs to be checked - check all init_etherdev return - drivers allocating net_device with init_etherdev doesn't need zeroing it (init_etherdev does this for us) - check all kmalloc, vmaloc, skb_alloc, etcalloc - check drivers/char/ip2main.c - register_netdev has to be checked as well - release previously successful allocations on failure - use forward gotos to release previously successfull allocations - convert drivers to new PCI API - remove uneeded historic code - checking for NULL on probe routines for net drivers - proc_register() is dead. Use create_proc_read_entry() instead. (from Al Viro on lkml) - check proc_*_create result, again, it can fail, and is common (bad) practice in most of the kernel sources - check freeing skbs with kfree instead of kfree_skb - get rid of panic function in drivers (watchdogs need to use machine_restart instead of panic 8) ) - several char drivers do this happily :( - get rid of isa_read/write[bwl], use ioremap instead - sed s/return EWHATEVER/return -EWHATEVER/ - check misc_register return (yes, it can fail, murphy's law applies here as well) - converting cli to spinlocks (look at net/netrom/*.c, net/ipx/*.c, etc) - get rid of verify_area with copy_*_user get/put_user, only needed if using __copy_*_user et al - to make sure that copy_to_user et all are checked - look at drivers/char/generic_serial.c - look at drivers/char/n_tty.c - use "return copy_to_user(...) ? -EFAULT : ok_value;" - check drivers/char/dz.c wrt return copy*user(...); has to be ... ? -EFAULT : 0; - prumpf suggested: - make sure drivers never read loops_per_sec - it might change under them - fix watchdog drivers to use link order rather than explicit initialization calls (i810 is particularly broken) - get rid of init_module / cleanup_module (softdog in particular) - make sure BUG() is used correctly (i.e. if(function()) BUG(); is evil) i.e. even when no opping BUG we still have an if - get rid of if (p) kfree(p); style constructs - kfree(NULL) is a nop and it shortens the code path - prumpf suggested, rmk agreed - get rid of save_flags_cli, use local_irq_save instead Maybe: - check drivers/scsi/ips.c for resource leaks (ips_release doesn't seems to release all the kmalloc memory it got in ips_detect. (quick look) = DONE = - get rid of copy_to_user_ret et all (Linus call) (davem) - 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/
Re: Update Linux 2.4 Status/TODO list
On Wed, 13 Sep 2000, Alan Cox wrote: * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) Need more details of how APM/ACPI is dorking with DMA settins by the OEM. Case 1 I've seen is assuming windows put the drive back into PIO no multimode before letting the bios suspend (for suspend to disk) Case 2 I've seen is coming back from the BIOS with the controller in PIO non multimode and forgetting the previous settings This is why I was wanting to buffer setting in the driver and offer APM/ACPI the callout to prevent this. Again you would have the option of invoking spin-up by APM attempts or using taskfile commands to brut force it into life. 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 PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Update Linux 2.4 Status/TODO list
On Sep 13, [EMAIL PROTECTED] wrote: * Innd data corruption, probably caused by bug truncation bug (Rik van Riel) This bug has not been fixed, I can still reproduce it (but not every time). This is how it happens: - INN (1.7.2+insync+other patches, the debian package I maintain) is running - active is correct - I post an article, which is filed with the correct number - for *this group only* the high value is wrong and equal to the one in the active file I precedently saved (in some cases this does not happen and I can't notice anything wrong in the active file) - I stop INN - the whole active file is now 100% identical to the saved copy And the file mtime has not been updated (this time since the precedent day): -rw-r--r--1 news news 3075 Sep 10 00:02 active This happens on my personal workstation with plenty of free RAM and a tiny UUCP feed. Right now it happened after the daily expire run: I stopped INN and the file on disk changed to the copy I saved before expire started. Linux wonderland.linux.it 2.4.0-test8 #4 Sat Sep 9 23:45:09 CEST 2000 i586 unknown /dev/ide/host0/bus0/target0/lun0/part5 on /var type ext2 (rw,noatime) -- ciao, Marco - 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/
Re: Update Linux 2.4 Status/TODO list
"Theodore Y. Ts'o" wrote: Date:Wed, 13 Sep 2000 08:46:00 +0200 From: Harald Dunkel [EMAIL PROTECTED] How can I submit a bug report to be added to this list? I *try* to follow bug reports sent to Linux-kernel, but if you want to be sure, send it directly to me ([EMAIL PROTECTED]). (And now for the standard spiel of developers everywhere.) [ This has been explicitly cc'ed to Richard Gooch so he can add it to the linux-kernel FAQ (http://www.tux.org/lkml/). There is a section about bug reporting, but it's a bit thin. The old-kernel-faq maintained by Frohwalt Egerer has a lot more to say on this topic; what follows below has taken some ideas and lists from the old faq. ] Please follow general good bug reporting guidelines: Remember, the developers don't have access to your system, and they're not mind readers. Tell us which kernel version, and what your hardware is (if you're not sure, more details is better than less). At the very least, [...] Don't forget we have linux/REPORTING-BUGS. If that is missing some good suggestions, update that too... Jeff -- Jeff Garzik | Windows NT Performance, Building 1024| on the next "In Search Of" MandrakeSoft, Inc. | - 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/
Re: Update Linux 2.4 Status/TODO list
"Theodore Y. Ts'o" wrote: Date: Tue, 12 Sep 2000 23:37:57 -0700 From: David Ford [EMAIL PROTECTED] 4. Boot Time Failures * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC Versa LX with PIIX tuning) If this is a rare version of the BX/LX that has a no fix errata, then it will be messy to issue resets to get out of the loop. * PIIXn tuning can hang laptop (2.4.0-test8-pre6, David Ford) Need more details of how APM/ACPI is dorking with DMA settins by the OEM. These two are both reported by me, are the same issue. The exact same kernel, one with PIIXn tuning enabled, will hang the hardware on boot requiring a physical power loss to restart. Ah, OK, thanks. I've collapsed the two bug reports. (The first one was added by Alan, and his lists didn't give any indication as to two reported the problem, so I didn't realize they were the same problem.) - Ted Just to clarify, I meant the two PIIX entries. The ACPI/APM line got in there by mistake. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:img src="http://www.kalifornia.com/images/paradise.jpg" adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
Re: Update Linux 2.4 Status/TODO list
"Theodore Y. Ts'o" wrote: Date: Tue, 12 Sep 2000 23:55:55 -0700 From: David Ford [EMAIL PROTECTED] Please add 'APM resume returns the machine to the first tty, crashes X' This appeared w/ test8. If this is intended, I'd be very happy to know if so and I can write in to xfree86 about it. If not intended..fix needed. Can you send more information? Hardware, etc. Do we know whether this is a hardware specific problem, or a more general problem? (To several people) Yes, I will. Until later this evening I need my laptop for work. This evening I'll grab the serial cable and start making kernels and modules. AFAIK, this is a kernel issue, going backwards to a kernel that doesn't switch back to the first tty on resume, X remains in control of the screen and is quite happy. The first kernel that resumes and jumps back to the first tty, X crashes. Doing a gdb on it yields a writev() that results in a segfault. I'll do these two problems individually. 10. To Do But Non Showstopper * PCMCIA/Cardbus hangs (Basically unusable - Hinds pcmcia code is reliable) + PCMCIA crashes on unloading pci_socket With test8, pcmcia either with kernel code, mixed, or dhinds code; nothing is usable. Can you send more details? I don't have a scratch laptop to try 2.4.0, and I'm too chicken to put it there. (My laptop has to work; it's a production machine; failure is not an option. Among other things, the master 2.4.0 bug list lives there. :-) * cdrecord doesn't work (produces CD-ROM coasters) w/o any errors reported, works under 2.2 (Damon LoCascio) Hmm, upgrade cdrecord perhaps? I'm using the second to last release and I'm not burning coasters. cdrecord is undergoing a scsi subsystem rewrite. According to Damon LoCascio, he's using the latest cdrecord. Kernel : 2.4.0-test5 SCSI: Advansys APB940U Quad scsi controller CDRW: Yamaha 8824CDRW CPU : AMD K6-III @450 MHz Mem : 256Mb MB : FIC 503+ CDrecord: 1.6, 1.81, 1.9, 1.10 He says that it works just fine under 2.2.16, and he's seeing subtle data corruption problems under 2.4 (sometimes only 100 bytes between binary files). It could be a hardware problem where the 2.4 kernel is stressing things more than the 2.2 kernel; or it could be a SCSI controller specific problem. It's not clear. Fixed * Keyboard/mouse problems (should be fixed?) Related to pcmcia, no, not fixed. Certain mixes of drivers and hardware can stick the interrupt until they're removed and a different card inserted. Can you give more information on this one? What specifically is going on? There's no name associated with it, which means it was entered while Alan was maintaining the list, so I have no history associated with it. (For that matter, it may be referring to different problem from the one you're seeing now.) Thanks for the update, and your comments. (The rest of your comments will be on the linux24.sourceforge.net web page shortly.) - Ted Certainly. I amonst others reported the key/mouse issue many kernels back and it was a guess game for a while then Linus said the yenta was a red herring. I don't have that email anymore but there's a lot of detail to the key/mouse/pcmcia story and I'll dig it all up and write it out again. Basically I believe the kernel pcmcia code is off by one in the socket numbering as dhinds socket numbering works and w/ the kernel, one socket hangs the machine and the other socket appears to be numbered as #0 where w/ dhinds it was #1. It seems to wedge something physically because my laptop will forever hang at maestro init after trying to use the top socket w/ the kernel pcmcia. I have to remove all power then it will boot up past the maestro init. Note, the machine isn't hard hung at maestro, the magic key works. It just won't proceed through the boot. More to come this evening. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." begin:vcard n:Ford;David x-mozilla-html:TRUE org:img src="http://www.kalifornia.com/images/paradise.jpg" adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;28256 fn:David Ford end:vcard
Re: Update Linux 2.4 Status/TODO list
Ted and LT, I think this are the two things you wanted that were located in: /src/tar-files/testing/direct_add/ht6560b.c /src/tar-files/testing/direct_add/qd65xx.c /src/tar-files/testing/direct_add/qd65xx.h First Petr and Samuel, are these good to go into 2.4.0 ?? Cheers, Andre Hedrick The Linux ATA/IDE guy /* * TEMPORARY VERSION FOR HT6560A MODEL TESTING! * * MODIFIED FOR BOTH A AND B VERSIONS * 2000-07-16 Petr Soucek [EMAIL PROTECTED] */ /* * linux/drivers/block/ht6560b.c Version 0.07Feb 1, 2000 * * Copyright (C) 1995-2000 Linus Torvalds author (see below) */ /* * * Version 0.01Initial version hacked out of ide.c * * Version 0.02Added support for PIO modes, auto-tune * * Version 0.03Some cleanups * * Version 0.05PIO mode cycle timings auto-tune using bus-speed * * Version 0.06Prefetch mode now defaults no OFF. To set * prefetch mode OFF/ON use "hdparm -p8/-p9". * Unmask irq is disabled when prefetch mode * is enabled. * * Version 0.07Trying to fix CD-ROM detection problem. * "Prefetch" mode bit OFF for ide disks and * ON for anything else. * * * HT-6560B EIDE-controller support * To activate controller support use kernel parameter "ide0=ht6560b". * Use hdparm utility to enable PIO mode support. * * Author:Mikko Ala-Fossi[EMAIL PROTECTED] * Jan Evert van Grootheest [EMAIL PROTECTED] * * Try: http://www.maf.iki.fi/~maf/ht6560b/ */ #define HT6560B_VERSION "v0.07" #undef REALLY_SLOW_IO /* most systems can safely undef this */ #include linux/types.h #include linux/kernel.h #include linux/delay.h #include linux/timer.h #include linux/mm.h #include linux/ioport.h #include linux/blkdev.h #include linux/hdreg.h #include linux/ide.h #include linux/init.h #include linux/version.h #include asm/io.h #include "ide_modes.h" #define DEBUG /* remove comments for DEBUG messages */ /* * The special i/o-port that HT-6560B uses to configuration: *bit0 (0x01): "1" selects secondary interface *bit2 (0x04): "1" enables FIFO function *bit5 (0x20): "1" enables prefetched data read function (???) * * The special i/o-port that HT-6560A uses to configuration: *bit0 (0x01): "0" selects secondary interface *bit1 (0x02): "0" enables prefetched data read function *bit2 (0x04): "0" enables multi-master system(?) *bit3 (0x08): "1" 3 cycle time, "0" 2 cycle time (?) */ #define HT_CONFIG_PORT0x3e6 #define HT_CONFIG(drivea) (byte)(((drivea)-drive_data 0xff00) 8) /* * FIFO + PREFETCH (both a/b-model) */ #define HT_CONFIG_DEFAULT 0x1c /* no prefetch */ /* #define HT_CONFIG_DEFAULT 0x3c */ /* with prefetch */ #define HT_CONFIG_DEFAULT_A 0x0f /* no prefetch */ /* #define HT_CONFIG_DEFAULT_A 0x0d */ /* with prefetch */ #define HT_SECONDARY_IF 0x01 #define HT_PREFETCH_MODE 0x20 #define HT_PREFETCH_MODE_A 0x02 /* * ht6560b Timing values: * * I reviewed some assembler source listings of htide drivers and found * out how they setup those cycle time interfacing values, as they at Holtek * call them. IDESETUP.COM that is supplied with the drivers figures out * optimal values and fetches those values to drivers. I found out that * they use IDE_SELECT_REG to fetch timings to the ide board right after * interface switching. After that it was quite easy to add code to * ht6560b.c. * * IDESETUP.COM gave me values 0x24, 0x45, 0xaa, 0xff that worked fine * for hda and hdc. But hdb needed higher values to work, so I guess * that sometimes it is necessary to give higher value than IDESETUP * gives. [see cmd640.c for an extreme example of this. -ml] * * Perhaps I should explain something about these timing values: * The higher nibble of value is the Recovery Time (rt) and the lower nibble * of the value is the Active Time (at). Minimum value 2 is the fastest and * the maximum value 15 is the slowest. Default values should be 15 for both. * So 0x24 means 2 for rt and 4 for at. Each of the drives should have * both values, and IDESETUP gives automatically rt=15 st=15 for CDROMs or * similar. If value is too small there will be all sorts of failures. * * Timing byte consists of * High nibble: Recovery Cycle Time (rt) * The valid values range from 2 to 15. The default is 15. * * Low nibble: Active Cycle Time(at) * The valid values range from 2 to 15. The default is 15. * * You can obtain optimized timing values by running Holtek IDESETUP.COM * for DOS. DOS drivers get their timing values from command line, where * the first value is the Recovery Time and the second value is the * Active Time for
Update Linux 2.4 Status/TODO list
OK, here's the updated Linux 2.4 bug list. I let myself get a bit behind, so it took me a while to process through all of my backlogged l-k mail archives to assemble this list. As always, it's complete as I can make it, but it's not perfect. In particualar, some bugs listed on this page may have been fixed already. If so, or if you know some bug that didn't make on to this list, please let me know. For people who are wondering what changed, the differences from the last major release of this page can be found at http://linux24.sourceforge.net/status-changes.html As always, if you're curious what state this document is in, you can always get the latest copy by going to: http://linux24.sourceforge.net - Ted Linux 2.4 Status/TODO Page Last modified: [tytso:2913.0151EDT] Hopefully up to date as of: test8 1. Should Be Fixed (Confirmation Wanted) * Fbcon races (cursor problems when running continual streaming output mixed with printk + races when switching from X while doing continuous rapid printing --- Alan) 2. Capable Of Corrupting Your FS/data * Use PCI DMA by default in IDE is unsafe (must not do so on via VPx, x < 3) (requires chipset tuning to be enabled according to Andre Hedrick --- we need to turn this on by default -- TYT) * Fix the OOPS in usb-storage from the error-recovery handler. (reported by Matthew Dharm) * Non-atomic page-map operations can cause loss of dirty bit on pages (sct, alan) 3. Security * Fix module remove race bug (still to be done: TTY, ldisc, I2C, video_device - Al Viro) (Rogier Wolff will handle ATM) 4. Boot Time Failures * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC Versa LX with PIIX tuning) * HT6560/UMC8672 ide sets up stuff too early (before region stuff can be done) * Crashes on boot on some Compaqs ? (may be fixed) * Boot hangs on a range of Dell docking stations (Latitude) + Almost certainly related: PCI code doesn't see devices behind DECchip 21150 PCI bridges (used in Dell Latitude). Reported by Simon Trimmer . (Patch from Martin Mares exists but it disables cardbus devices, according to Tigran.) + Derek Fawcus at Cisco reports similar problems with Toshiba Tecra 8000 attached to the DeskStation V+ docking station. (once again, caused by bridge returning 0 when reading the I/O base/limit and Memory base/limit registers which confuses the new PCI resource code). * IBM Thinkpad 390 won't boot since 2.3.11 (See Decklin Foster for more info) 5. Compile errors * arcnet/com20020-isa.c doesn't compile, as of 2.4.0-test8. Dan Aloni has a fix * drivers/sound/cs46xx.c has compile errors test7 and test8 (C Sanjayan Rosenmund) 6. In Progress * Finish I2O merge (Intel/Alan) * Restore O_SYNC functionality (Stephen) - core code and ext2 done * Fix all remaining PCI code to use pci_enable_device (mostly done) * Fix, um, interesting races around dup2() and friends. (Al Viro) * Finish the audit/code review of the code dealing with descriptor tables. (Al Viro) * DMFE is not SMP safe (Frank Davis patch exists, but hasn't gotten much commens yet) * Audit all char and block drivers to ensure they are safe with the 2.3 locking - a lot of them are not especially on the read()/write() path. (Frank Davis --- moving slowly; if someone wants to help, contact Frank) 7. Obvious Projects For People (well if you have the hardware..) * Make syncppp use new ppp code * Fix SPX socket code 8. Fix Exists But Isnt Merged * Update SGI VisWS to new-style IRQ handling (Ingo) * Support MP table above 1Gig (Ingo) * Dont panic on boot when meeting HP boxes with wacked APIC table numbering (AC) * Scheduler bugs in RT (Dimitris) * AIC7xxx doesnt work non PCI ? (Doug says OK, new version due anyway) * Fix boards with different TSC per CPU and kill TSC use on them * Floppy last block cache flush error * PPC-specific: won't boot on 601 CPU's (powermac) (Andreas Tobler; Paul Mackerras has fix in PPC tree) * IRDA fixes (patches from Russell King sent to Linus and DAG) + IRDA calls get_random_bytes before random is set up + Infinite loop in IrDA parameter code + Device name in /proc/net/irda/irias is not updated when /proc/sys/net/irda/devname is written + IrDA Discovery slot allocation is not random * Splitting a posix lock causes an infinite loop (Stephen Rothwell) * Many network device drivers don't call MOD_INC_USE_COUNT in dev->open. (Paul Gortmaker has patches) * 2.4.0-test8 has a BUG at ll_rw_blk:711.
Update Linux 2.4 Status/TODO list
OK, here's the updated Linux 2.4 bug list. I let myself get a bit behind, so it took me a while to process through all of my backlogged l-k mail archives to assemble this list. As always, it's complete as I can make it, but it's not perfect. In particualar, some bugs listed on this page may have been fixed already. If so, or if you know some bug that didn't make on to this list, please let me know. For people who are wondering what changed, the differences from the last major release of this page can be found at http://linux24.sourceforge.net/status-changes.html As always, if you're curious what state this document is in, you can always get the latest copy by going to: http://linux24.sourceforge.net - Ted Linux 2.4 Status/TODO Page Last modified: [tytso:2913.0151EDT] Hopefully up to date as of: test8 1. Should Be Fixed (Confirmation Wanted) * Fbcon races (cursor problems when running continual streaming output mixed with printk + races when switching from X while doing continuous rapid printing --- Alan) 2. Capable Of Corrupting Your FS/data * Use PCI DMA by default in IDE is unsafe (must not do so on via VPx, x 3) (requires chipset tuning to be enabled according to Andre Hedrick --- we need to turn this on by default -- TYT) * Fix the OOPS in usb-storage from the error-recovery handler. (reported by Matthew Dharm) * Non-atomic page-map operations can cause loss of dirty bit on pages (sct, alan) 3. Security * Fix module remove race bug (still to be done: TTY, ldisc, I2C, video_device - Al Viro) (Rogier Wolff will handle ATM) 4. Boot Time Failures * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC Versa LX with PIIX tuning) * HT6560/UMC8672 ide sets up stuff too early (before region stuff can be done) * Crashes on boot on some Compaqs ? (may be fixed) * Boot hangs on a range of Dell docking stations (Latitude) + Almost certainly related: PCI code doesn't see devices behind DECchip 21150 PCI bridges (used in Dell Latitude). Reported by Simon Trimmer . (Patch from Martin Mares exists but it disables cardbus devices, according to Tigran.) + Derek Fawcus at Cisco reports similar problems with Toshiba Tecra 8000 attached to the DeskStation V+ docking station. (once again, caused by bridge returning 0 when reading the I/O base/limit and Memory base/limit registers which confuses the new PCI resource code). * IBM Thinkpad 390 won't boot since 2.3.11 (See Decklin Foster for more info) 5. Compile errors * arcnet/com20020-isa.c doesn't compile, as of 2.4.0-test8. Dan Aloni has a fix * drivers/sound/cs46xx.c has compile errors test7 and test8 (C Sanjayan Rosenmund) 6. In Progress * Finish I2O merge (Intel/Alan) * Restore O_SYNC functionality (Stephen) - core code and ext2 done * Fix all remaining PCI code to use pci_enable_device (mostly done) * Fix, um, interesting races around dup2() and friends. (Al Viro) * Finish the audit/code review of the code dealing with descriptor tables. (Al Viro) * DMFE is not SMP safe (Frank Davis patch exists, but hasn't gotten much commens yet) * Audit all char and block drivers to ensure they are safe with the 2.3 locking - a lot of them are not especially on the read()/write() path. (Frank Davis --- moving slowly; if someone wants to help, contact Frank) 7. Obvious Projects For People (well if you have the hardware..) * Make syncppp use new ppp code * Fix SPX socket code 8. Fix Exists But Isnt Merged * Update SGI VisWS to new-style IRQ handling (Ingo) * Support MP table above 1Gig (Ingo) * Dont panic on boot when meeting HP boxes with wacked APIC table numbering (AC) * Scheduler bugs in RT (Dimitris) * AIC7xxx doesnt work non PCI ? (Doug says OK, new version due anyway) * Fix boards with different TSC per CPU and kill TSC use on them * Floppy last block cache flush error * PPC-specific: won't boot on 601 CPU's (powermac) (Andreas Tobler; Paul Mackerras has fix in PPC tree) * IRDA fixes (patches from Russell King sent to Linus and DAG) + IRDA calls get_random_bytes before random is set up + Infinite loop in IrDA parameter code + Device name in /proc/net/irda/irias is not updated when /proc/sys/net/irda/devname is written + IrDA Discovery slot allocation is not random * Splitting a posix lock causes an infinite loop (Stephen Rothwell) * Many network device drivers don't call MOD_INC_USE_COUNT in dev-open. (Paul Gortmaker has patches) * 2.4.0-test8 has a BUG at ll_rw_blk:711.
