Re: 2.6.24 module problem
Am Sonntag, 3. Februar 2008 schrieb Jack Byer: > PAX: modprobe:752, uid/euid: 0/0, invalid execution attempt at This looks like an issue with PAX - [EMAIL PROTECTED] might be a better list to ask. Christian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24 module problem
Am Sonntag, 3. Februar 2008 schrieb Jack Byer: PAX: modprobe:752, uid/euid: 0/0, invalid execution attempt at This looks like an issue with PAX - [EMAIL PROTECTED] might be a better list to ask. Christian -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Disable cache disk
On Wednesday 30 March 2005 15:00, Yves Crespin wrote: > 1/ is-it possible to *really* be synchronize. I prefer to have a blocked > write() than use cache and get swap! Try to mount with the sync option. > 2/ is-it possible to disable cache disk ? your copy tool has to support/use O_DIRECT - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ANNOUNCE] hotplug-ng 001 release
On Friday 11 February 2005 07:46, Greg KH wrote: > And finally, even if you do use udevstart to manager /sbin/hotplug > events, you still need a module autoloader program. This package > provides executables for that problem, if you don't want to (or you > can't) use the existing linux-hotplug scripts. udev will never do the > module loading logic, so there's no duplication in this case. Greg, the pci module autoloader is a real agent, which means it depends on having a hotplug event. Are you planning to support a scan for already present devices, like the pci.rc file in current hotplug solutions? cheers Christian - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
onboard promise + dvd/cdrom no ultra dma
I attached a Toshiba DVD-ROM at the ASUS A7V133 Promise controller.
The highest transfer mode I can use is Multiword DMA 2, though I activated
the DMA-Option in the IDE-kernel configuration.
>hdparm -i /dev/hde
/dev/hde:
Model=TOSHIBA DVD-ROM SD-M1502, FwRev=1008, SerialNo=2100807146
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=128kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2 udma0 udma1 udma2
AdvancedPM=no
Drive Supports : ATA/ATAPI-5 T13 1321D revision 3 : ATA-2 ATA-3 ATA-4 ATA-5
If I try
>hdparm -d 1 /dev/hde
/dev/hde:
setting using_dma to 1 (on)
using_dma = 1 (on)
to active the UDMA-Modes the drive is not accessible. Mount and file access
fail, but
> hdparm -i /dev/hde
/dev/hde:
Model=TOSHIBA DVD-ROM SD-M1502, FwRev=1008, SerialNo=2100807146
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=128kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2 udma0 udma1 udma2
AdvancedPM=no
Drive Supports : ATA/ATAPI-5 T13 1321D revision 3 : ATA-2 ATA-3 ATA-4 ATA-5
shows no difference.
after I tried to access to drive dmesg shows:
ISO 9660 Extensions: Microsoft Joliet Level 3
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: tray open
end_request: I/O error, dev 21:00 (hde), sector 112
ISOFS: unable to read i-node block
ISOFS: changing to secondary root
hde: tray open
end_request: I/O error, dev 21:00 (hde), sector 336
ISOFS: unable to read i-node block
VFS: Disk change detected on device ide2(33,0)
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: tray open
end_request: I/O error, dev 21:00 (hde), sector 120
But I did not opened the tray.
After setting back with hdparm -d 0 the drive is functional again.
If I use the VIA-Controller with the same drive I am able to activate udma2
successfully.
Any ideas?
Thanks
my configuration:
hda=Maxtor 5T020H2 (VIA)
hdc=Maxtor 52049H3 (VIA)
hde=TOSHIBA DVD-ROM SD-M1502 (Promise PDC20265)
hdg=SONY CD-RW CRX140E with SCSI-Emulation
Kernel 2.4.5-ac21. But similar with older Kernels.
Mandrake 8.0
>lsmod
Module Size Used by
NVdriver 658480 15
parport_pc 24144 1 (autoclean)
lp 6256 0 (autoclean)
parport 27008 1 (autoclean) [parport_pc lp]
es1370 26432 1
soundcore 4176 4 [es1370]
3c59x 25440 1 (autoclean)
usbmouse 2016 0 (unused)
mousedev 4096 1
input 3584 0 [usbmouse mousedev]
usb-uhci 21360 0 (unused)
usbcore 49152 1 [usbmouse usb-uhci]
ide-scsi 7952 0
scsi_mod 54720 1 [ide-scsi]
ntfs 49072 1 (autoclean)
nls_iso8859-1 2880 3 (autoclean)
nls_cp850 3616 2 (autoclean)
>lspci
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8305
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 40)
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 06)
00:04.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 16)
00:04.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 16)
00:04.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:0a.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 01)
00:0d.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev
30)
00:11.0 Unknown mass storage controller: Promise Technology, Inc.: Unknown
device 0d30 (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV11 (rev a1)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
onboard promise + dvd/cdrom no ultra dma
I attached a Toshiba DVD-ROM at the ASUS A7V133 Promise controller.
The highest transfer mode I can use is Multiword DMA 2, though I activated
the DMA-Option in the IDE-kernel configuration.
hdparm -i /dev/hde
/dev/hde:
Model=TOSHIBA DVD-ROM SD-M1502, FwRev=1008, SerialNo=2100807146
Config={ Fixed Removeable DTR=5Mbs DTR10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=128kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2 udma0 udma1 udma2
AdvancedPM=no
Drive Supports : ATA/ATAPI-5 T13 1321D revision 3 : ATA-2 ATA-3 ATA-4 ATA-5
If I try
hdparm -d 1 /dev/hde
/dev/hde:
setting using_dma to 1 (on)
using_dma = 1 (on)
to active the UDMA-Modes the drive is not accessible. Mount and file access
fail, but
hdparm -i /dev/hde
/dev/hde:
Model=TOSHIBA DVD-ROM SD-M1502, FwRev=1008, SerialNo=2100807146
Config={ Fixed Removeable DTR=5Mbs DTR10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=128kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2 udma0 udma1 udma2
AdvancedPM=no
Drive Supports : ATA/ATAPI-5 T13 1321D revision 3 : ATA-2 ATA-3 ATA-4 ATA-5
shows no difference.
after I tried to access to drive dmesg shows:
ISO 9660 Extensions: Microsoft Joliet Level 3
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: tray open
end_request: I/O error, dev 21:00 (hde), sector 112
ISOFS: unable to read i-node block
ISOFS: changing to secondary root
hde: tray open
end_request: I/O error, dev 21:00 (hde), sector 336
ISOFS: unable to read i-node block
VFS: Disk change detected on device ide2(33,0)
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: tray open
end_request: I/O error, dev 21:00 (hde), sector 120
But I did not opened the tray.
After setting back with hdparm -d 0 the drive is functional again.
If I use the VIA-Controller with the same drive I am able to activate udma2
successfully.
Any ideas?
Thanks
my configuration:
hda=Maxtor 5T020H2 (VIA)
hdc=Maxtor 52049H3 (VIA)
hde=TOSHIBA DVD-ROM SD-M1502 (Promise PDC20265)
hdg=SONY CD-RW CRX140E with SCSI-Emulation
Kernel 2.4.5-ac21. But similar with older Kernels.
Mandrake 8.0
lsmod
Module Size Used by
NVdriver 658480 15
parport_pc 24144 1 (autoclean)
lp 6256 0 (autoclean)
parport 27008 1 (autoclean) [parport_pc lp]
es1370 26432 1
soundcore 4176 4 [es1370]
3c59x 25440 1 (autoclean)
usbmouse 2016 0 (unused)
mousedev 4096 1
input 3584 0 [usbmouse mousedev]
usb-uhci 21360 0 (unused)
usbcore 49152 1 [usbmouse usb-uhci]
ide-scsi 7952 0
scsi_mod 54720 1 [ide-scsi]
ntfs 49072 1 (autoclean)
nls_iso8859-1 2880 3 (autoclean)
nls_cp850 3616 2 (autoclean)
lspci
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8305
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 40)
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 06)
00:04.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 16)
00:04.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 16)
00:04.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:0a.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 01)
00:0d.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev
30)
00:11.0 Unknown mass storage controller: Promise Technology, Inc.: Unknown
device 0d30 (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV11 (rev a1)
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: VIA KT133A crash *post* 2.4.3-ac6
> I'm certainly willing to provide any data it's decided is necessary to > collect to make the correlations. I'll even volunteer to be the . > bit different - I have the hard drive on the promise interface (ide2) and If possible, can you remove the hard disc from the promise and attach it on the VIA-Controller and test if the problem still occurs? (prepare a bootdisc if you cannot boot. Propably, you have to pass a new root-partition to the kernel) I hardly believe that the promise controller has some problems with the new VIA setup introduced in 2.4.3-ac7. Using the promise ports of the A7V133 is the only correlation I see again and again... -- PS: Sorry for using outlook, but sometimes you use an computer you doesn´t own. :-) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: VIA KT133A crash *post* 2.4.3-ac6
I'm certainly willing to provide any data it's decided is necessary to collect to make the correlations. I'll even volunteer to be the . bit different - I have the hard drive on the promise interface (ide2) and If possible, can you remove the hard disc from the promise and attach it on the VIA-Controller and test if the problem still occurs? (prepare a bootdisc if you cannot boot. Propably, you have to pass a new root-partition to the kernel) I hardly believe that the promise controller has some problems with the new VIA setup introduced in 2.4.3-ac7. Using the promise ports of the A7V133 is the only correlation I see again and again... -- PS: Sorry for using outlook, but sometimes you use an computer you doesn´t own. :-) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: VIA KT133A crash *post* 2.4.3-ac6
> With DMA (UDMA Mode 5) enabled, my machine crashes on kernel versions > from 2.4.3-ac7 onwards up to 2.4.5 right up to 2.4.5-ac13. 2.4.3 vanilla > and 2.4.3-ac6 are completely stable. -ac7 of course is when a load of > VIA fixes were done. :-} I encountered the same problem after 2.4.3-ac6. > CPU: Athlon 1.33 GHz with 266MHz FSB > Mobo: Asus A7V133 with 266MHz FSB, UltraDMA100 (PDC20265 according to So you put your IBM drive on the promise, right? Removing the hard disc from the promise controller and attaching it on the VIA-Controller solved my problems. The system is now rock solid. If you do so, take care that your root partition moves from hde to hda. Prepare a boot disk and pass a parameter like root=/dev/hda to the kernel. After a successful boot, modify fstab and lilo.conf and run lilo. > With DMA disabled, *all* kernels are completely stable. same for me. > With DMA (any setting, but UDMA mode 5 preferred of course) enabled, on > kernels 2.4.3-ac7 and onwards, random lockup on disk access within first > few minutes of use - sometimes very quickly after boot, sometimes as > much as ten minutes later given use. Running bonnie -s 1024 once or > twice after boot generally excites it too. :-}. Lockup is pretty severe: > machine goes completely unresponsive, Magic SysRq doesn't work. About > the only thing that does still work is the flashing VGA cursor. :-) > Please read the FAQ at http://www.tux.org/lkml/ sounds absoluty identical to my problem with ASUS A7V133 I reported some weeks ago. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: VIA KT133A crash *post* 2.4.3-ac6
With DMA (UDMA Mode 5) enabled, my machine crashes on kernel versions from 2.4.3-ac7 onwards up to 2.4.5 right up to 2.4.5-ac13. 2.4.3 vanilla and 2.4.3-ac6 are completely stable. -ac7 of course is when a load of VIA fixes were done. :-} I encountered the same problem after 2.4.3-ac6. CPU: Athlon 1.33 GHz with 266MHz FSB Mobo: Asus A7V133 with 266MHz FSB, UltraDMA100 (PDC20265 according to So you put your IBM drive on the promise, right? Removing the hard disc from the promise controller and attaching it on the VIA-Controller solved my problems. The system is now rock solid. If you do so, take care that your root partition moves from hde to hda. Prepare a boot disk and pass a parameter like root=/dev/hda to the kernel. After a successful boot, modify fstab and lilo.conf and run lilo. With DMA disabled, *all* kernels are completely stable. same for me. With DMA (any setting, but UDMA mode 5 preferred of course) enabled, on kernels 2.4.3-ac7 and onwards, random lockup on disk access within first few minutes of use - sometimes very quickly after boot, sometimes as much as ten minutes later given use. Running bonnie -s 1024 once or twice after boot generally excites it too. :-}. Lockup is pretty severe: machine goes completely unresponsive, Magic SysRq doesn't work. About the only thing that does still work is the flashing VGA cursor. :-) Please read the FAQ at http://www.tux.org/lkml/ sounds absoluty identical to my problem with ASUS A7V133 I reported some weeks ago. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Break 2.4 VM in five easy steps
OK, Linus said if I use swap it should be at least twice as much as RAM. there will be much more discussion about it, for me this contraint is a very very bad idea. Have you ever thought about diskless workstations? Swapping over a network sounds ugly. Nevertheless, my question is: what happens if I plan to use no swap. I have enough memory installed for my purposes and every swapping operation can do only one thing: slowing down the system. Is there a different behaviour if I completely disable swap? greetings Christian Bornträger - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5 VM
> On a side question: does Linux support swap-files in addition to > sawp-partitions? Even if that has a performance penalty, when the system > is swapping performance is dead anyway. Yes. A possible solution could be: > dd if=/dev/zero of=/swap bs=1M count= > mkswap /swap > swapon /swap Works fine for me. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5 VM
On a side question: does Linux support swap-files in addition to sawp-partitions? Even if that has a performance penalty, when the system is swapping performance is dead anyway. Yes. A possible solution could be: dd if=/dev/zero of=/swap bs=1M count=whatever you like in MB mkswap /swap swapon /swap Works fine for me. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Break 2.4 VM in five easy steps
OK, Linus said if I use swap it should be at least twice as much as RAM. there will be much more discussion about it, for me this contraint is a very very bad idea. Have you ever thought about diskless workstations? Swapping over a network sounds ugly. Nevertheless, my question is: what happens if I plan to use no swap. I have enough memory installed for my purposes and every swapping operation can do only one thing: slowing down the system. Is there a different behaviour if I completely disable swap? greetings Christian Bornträger - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PROMISE+ATHLON crashes with 2.4.3ac7 or higher. workaround?
Hi all, I faced several system hangs with an ASUS A7V133 using a kernel 2.4.3ac7 or higher. (I reported this some time ago) Now I removed the 2 hard drives from the promise controller and attached them an to the via controller. After that step I could not reproduced the system freeze at least with 2.4.5. So I __guess__ that the promise controller in combination with the VIA PCI Interface leads to some trouble. I will do some further investigations, to find out, if the promise controller was my problem. Just ask if you need more information. greetings Christian Bornträger - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PROMISE+ATHLON crashes with 2.4.3ac7 or higher. workaround?
Hi all, I faced several system hangs with an ASUS A7V133 using a kernel 2.4.3ac7 or higher. (I reported this some time ago) Now I removed the 2 hard drives from the promise controller and attached them an to the via controller. After that step I could not reproduced the system freeze at least with 2.4.5. So I __guess__ that the promise controller in combination with the VIA PCI Interface leads to some trouble. I will do some further investigations, to find out, if the promise controller was my problem. Just ask if you need more information. greetings Christian Bornträger - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG ? and questions
> I have a Cx 486/66 with 12 Megs of ram AST computer > gcc 2.95.3, glibc 2.1.3, make 3.79.1 binutils 2.11 ?? > Problems: > 1. When I try to run multiple (2) compilations on a > 2.4.4 kernel usually one > of them dies -- if it's gcc - signal 11 , if it's sh looks like an out-of-memory (OOM) kill. Check your log files. (var/log/messages but can vary on some distributions) 12 MB of RAM is not enough for Kernel 2.4.4 and several gcc runs, as some gcc optimizations have complexity of O(n^2) or higher. greetings Christian Bornträger - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG ? and questions
I have a Cx 486/66 with 12 Megs of ram AST computer gcc 2.95.3, glibc 2.1.3, make 3.79.1 binutils 2.11 ?? Problems: 1. When I try to run multiple (2) compilations on a 2.4.4 kernel usually one of them dies -- if it's gcc - signal 11 , if it's sh looks like an out-of-memory (OOM) kill. Check your log files. (var/log/messages but can vary on some distributions) 12 MB of RAM is not enough for Kernel 2.4.4 and several gcc runs, as some gcc optimizations have complexity of O(n^2) or higher. greetings Christian Bornträger - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Latest on Athlon Via KT133A chipset solution?
> Give the current -ac a spin and tell me if it works/doesnt and if not how > it fails I will test it on Sunday evening, when I get back access to my Athlon. Again I am not sure if I had the same problem related to the compiler-optimizations. My problems (system freeze) started with 2.4.3-ac7. So the problem might related to the VIA-bug-workaround. Is there a possibility to get debugging messages or register dumps without a second PC? Or is there a possibility to an unbuffered log write? e.g. write kernel logs to a floppy disc unbuffered. Otherwise I am not sure, if I am able to help you finding the problem. Unfortunately I have only a VIA-based Athlon system and not a S/390 greetings Christian Bornträger - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Latest on Athlon Via KT133A chipset solution?
Give the current -ac a spin and tell me if it works/doesnt and if not how it fails I will test it on Sunday evening, when I get back access to my Athlon. Again I am not sure if I had the same problem related to the compiler-optimizations. My problems (system freeze) started with 2.4.3-ac7. So the problem might related to the VIA-bug-workaround. Is there a possibility to get debugging messages or register dumps without a second PC? Or is there a possibility to an unbuffered log write? e.g. write kernel logs to a floppy disc unbuffered. Otherwise I am not sure, if I am able to help you finding the problem. Unfortunately I have only a VIA-based Athlon system and not a S/390 greetings Christian Bornträger - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Athlon possible fixes
> Hmm, I'm wondering if this could be same bug that I'm seeing with ASUS > A7V133 & Duron/800 when using IDE autotuning (PDC20265). > Still haven't got any replies suggesting any reason for lockups I'm seeing > (no oopses). Or is the Promise driver just buggy, because system is solid > with noautotune. RAID5 (md) on that server is just little bit sluggish with OK. I tried it on my A7V133 system and leaving out autotune (just for Promise, where I connected the hard discs) makes the system stable. I thought my problem is related to the Athlon compile problem I read in this group, but now I am not sure. Can you try and mail me if the Kernel 2.4.3 (without any ac patch) is stable with your system even if you use autotune? "Downgrade" to this kernel works fine for me. greetings Christian Bornträger - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DISCOVERED! Cause of Athlon/VIA KX133 Instability
> Mandrake 8's kernel comes with i586 CPU support, it is alredy known it > works. Remember that the instability occurs only when Athlon optimizations > are used. You are right. But I like to point out that on my Athlon kernel 2.4.3 is working fine. The first kernel I face problems is 2.4.3-ac7. I also know that the problem occurs of kernel 2.4.4. That might help to find the problem. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DISCOVERED! Cause of Athlon/VIA KX133 Instability
>Maybe, but the IWILL board is the only one we've heard about problems with. I have also stability problems with an ASUS A7V133. I already have the 1004-d2 bios which should fix the VIA IDE problems. But my hard drives are connected to the promise controller of the board. Only 2 CD-drives are on teh VIA-Chip. I am quite sure that my problem was introduced with 2.4.3-ac7, because, the board is rock solid up to kernel 2.4.3-ac6 or with the Madrake 8 kernel. But If I try to put some load on 2.4.3-ac7 or above I get lock ups. Even the magic sysrq does not work. No matter if compiled for athlon Pentium II or 586. No matter if I use the mandrake 8 gcc 2.96 or a self compiled gcc 2.95.3. The problem also occurs on kernel 2.4.4. Bytheway there is a thread called "ABit KT7A-RAIN random lock ups " It might be related to one of the Athlon/VIA problems. greetings Christian - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DISCOVERED! Cause of Athlon/VIA KX133 Instability
Maybe, but the IWILL board is the only one we've heard about problems with. I have also stability problems with an ASUS A7V133. I already have the 1004-d2 bios which should fix the VIA IDE problems. But my hard drives are connected to the promise controller of the board. Only 2 CD-drives are on teh VIA-Chip. I am quite sure that my problem was introduced with 2.4.3-ac7, because, the board is rock solid up to kernel 2.4.3-ac6 or with the Madrake 8 kernel. But If I try to put some load on 2.4.3-ac7 or above I get lock ups. Even the magic sysrq does not work. No matter if compiled for athlon Pentium II or 586. No matter if I use the mandrake 8 gcc 2.96 or a self compiled gcc 2.95.3. The problem also occurs on kernel 2.4.4. Bytheway there is a thread called ABit KT7A-RAIN random lock ups It might be related to one of the Athlon/VIA problems. greetings Christian - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DISCOVERED! Cause of Athlon/VIA KX133 Instability
Mandrake 8's kernel comes with i586 CPU support, it is alredy known it works. Remember that the instability occurs only when Athlon optimizations are used. You are right. But I like to point out that on my Athlon kernel 2.4.3 is working fine. The first kernel I face problems is 2.4.3-ac7. I also know that the problem occurs of kernel 2.4.4. That might help to find the problem. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Athlon possible fixes
Hmm, I'm wondering if this could be same bug that I'm seeing with ASUS A7V133 Duron/800 when using IDE autotuning (PDC20265). Still haven't got any replies suggesting any reason for lockups I'm seeing (no oopses). Or is the Promise driver just buggy, because system is solid with noautotune. RAID5 (md) on that server is just little bit sluggish with OK. I tried it on my A7V133 system and leaving out autotune (just for Promise, where I connected the hard discs) makes the system stable. I thought my problem is related to the Athlon compile problem I read in this group, but now I am not sure. Can you try and mail me if the Kernel 2.4.3 (without any ac patch) is stable with your system even if you use autotune? Downgrade to this kernel works fine for me. greetings Christian Bornträger - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
