Re: BUG: soft lockup with 3.7.0 but not 3.6.10
On Tue, Dec 11, 2012 at 20:16:47, Borislav Petkov wrote: > What family is that? Can you give /proc/cpuinfo? processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping: 1 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv bogomips: 2004.56 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc 100mhzsteps processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping: 1 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv bogomips: 2004.56 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc 100mhzsteps >> Dec 11 16:02:15 pervalidus kernel: [11260.096015] BUG: soft lockup - >> CPU#1 stuck for 22s! [cc1:20906] > > Hmm, this says that gcc gets stuck at some point. Is this always > reproducible on 3.7? It always happens when I compile MPlayer. It was always cc1, but yasm once. >> What about using another version of gcc, can you repro it then too? >> >> It would be interesting to know where all those cc1 processes get >> stuck. >> Can you break into them with gdb and dump the code around RIP >> everytime those tasks gets stuck? Try doing a couple of them to see >> whether it is repeatable. I'll see what I can do. I'm compiling with -j3, so it's hard to see before the kernel reports it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: soft lockup with 3.7.0 but not 3.6.10
On Tue, Dec 11, 2012 at 20:16:47, Borislav Petkov wrote: What family is that? Can you give /proc/cpuinfo? processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping: 1 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv bogomips: 2004.56 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc 100mhzsteps processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ stepping: 1 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv bogomips: 2004.56 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc 100mhzsteps Dec 11 16:02:15 pervalidus kernel: [11260.096015] BUG: soft lockup - CPU#1 stuck for 22s! [cc1:20906] Hmm, this says that gcc gets stuck at some point. Is this always reproducible on 3.7? It always happens when I compile MPlayer. It was always cc1, but yasm once. What about using another version of gcc, can you repro it then too? It would be interesting to know where all those cc1 processes get stuck. Can you break into them with gdb and dump the code around RIP everytime those tasks gets stuck? Try doing a couple of them to see whether it is repeatable. I'll see what I can do. I'm compiling with -j3, so it's hard to see before the kernel reports it. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: radeonfb blanks my monitor
On Thu, 3 Mar 2005, Frédéric L. W. Meunier wrote: On Fri, 4 Mar 2005, Benjamin Herrenschmidt wrote: Well, I would need the full log, and with radeonfb verbose debug enabled in the config. I'll later try as module with debug. Here's: /var/log/messages: Mar 4 14:00:29 pervalidus kernel: radeonfb: Found Intel x86 BIOS ROM Image Mar 4 14:00:29 pervalidus kernel: radeonfb: Retreived PLL infos from BIOS Mar 4 14:00:30 pervalidus kernel: radeonfb: Monitor 1 type CRT found Mar 4 14:00:30 pervalidus kernel: radeonfb: EDID probed Mar 4 14:00:30 pervalidus kernel: radeonfb: Monitor 2 type no found /var/log/syslog: Mar 4 14:00:28 pervalidus kernel: radeonfb_pci_register BEGIN Mar 4 14:00:28 pervalidus kernel: radeonfb (:01:00.0): Found 262144k of DDR 128 bits wide videoram Mar 4 14:00:29 pervalidus kernel: radeonfb (:01:00.0): mapped 16384k videoram Mar 4 14:00:29 pervalidus kernel: radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=325.00 Mhz, System=200.00 MHz Mar 4 14:00:29 pervalidus kernel: radeonfb: PLL min 2 max 4 Mar 4 14:00:29 pervalidus kernel: 1 chips in connector info Mar 4 14:00:29 pervalidus kernel: - chip 1 has 2 connectors Mar 4 14:00:29 pervalidus kernel: * connector 0 of type 2 (CRT) : 2300 Mar 4 14:00:29 pervalidus kernel: * connector 1 of type 3 (DVI-I) : 3221 Mar 4 14:00:29 pervalidus kernel: Starting monitor auto detection... Mar 4 14:00:29 pervalidus kernel: radeonfb: I2C (port 1) ... not found Mar 4 14:00:29 pervalidus kernel: radeonfb: I2C (port 2) ... not found Mar 4 14:00:29 pervalidus kernel: radeonfb: I2C (port 3) ... found CRT display Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 4) ... not found Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 2) ... not found Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 4) ... not found Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 3) ... found CRT display Mar 4 14:00:30 pervalidus kernel: hStart = 694, hEnd = 757, hTotal = 795 Mar 4 14:00:30 pervalidus kernel: vStart = 402, vEnd = 408, vTotal = 418 Mar 4 14:00:30 pervalidus kernel: h_total_disp = 0x590062^I hsync_strt_wid =0x8702c0 Mar 4 14:00:30 pervalidus kernel: v_total_disp = 0x18f01a1^I vsync_strt_wid = 0x860191 Mar 4 14:00:30 pervalidus kernel: pixclock = 85925 Mar 4 14:00:30 pervalidus kernel: freq = 1163 Mar 4 14:00:30 pervalidus kernel: freq = 1666, PLL min = 2, PLL max = 4 Mar 4 14:00:30 pervalidus kernel: ref_div = 12, ref_clk = 2700, output_freq = 26656 Mar 4 14:00:30 pervalidus kernel: ref_div = 12, ref_clk = 2700, output_freq = 26656 Mar 4 14:00:30 pervalidus kernel: post div = 0x5 Mar 4 14:00:30 pervalidus kernel: fb_div = 0x76 Mar 4 14:00:30 pervalidus kernel: ppll_div_3 = 0x50076 Mar 4 14:00:30 pervalidus kernel: Console: switching to colour frame buffer device 90x25 Mar 4 14:00:30 pervalidus kernel: radeonfb (:01:00.0): ATI Radeon AP Mar 4 14:00:30 pervalidus kernel: radeonfb_pci_register END BTW, I noticed that it locking the system. I was able to issue a shutdown. The commands still work, but beep is disabled. -- How to contact me - http://www.pervalidus.net/contact.html
Re: radeonfb blanks my monitor
On Fri, 4 Mar 2005, Jean Delvare wrote: Frédéric, can you check in /etc/modprobe.conf if you have a line like: options i2c-algo-bit bit_test=1 If you do, please comment it out and see if it changes anything. Yes, I had, but commenting it out didn't change anything. -- How to contact me - http://www.pervalidus.net/contact.html
Re: radeonfb blanks my monitor
On Fri, 4 Mar 2005, Jean Delvare wrote: Frédéric, can you check in /etc/modprobe.conf if you have a line like: options i2c-algo-bit bit_test=1 If you do, please comment it out and see if it changes anything. Yes, I had, but commenting it out didn't change anything. -- How to contact me - http://www.pervalidus.net/contact.html
Re: radeonfb blanks my monitor
On Thu, 3 Mar 2005, Frédéric L. W. Meunier wrote: On Fri, 4 Mar 2005, Benjamin Herrenschmidt wrote: Well, I would need the full log, and with radeonfb verbose debug enabled in the config. I'll later try as module with debug. Here's: /var/log/messages: Mar 4 14:00:29 pervalidus kernel: radeonfb: Found Intel x86 BIOS ROM Image Mar 4 14:00:29 pervalidus kernel: radeonfb: Retreived PLL infos from BIOS Mar 4 14:00:30 pervalidus kernel: radeonfb: Monitor 1 type CRT found Mar 4 14:00:30 pervalidus kernel: radeonfb: EDID probed Mar 4 14:00:30 pervalidus kernel: radeonfb: Monitor 2 type no found /var/log/syslog: Mar 4 14:00:28 pervalidus kernel: radeonfb_pci_register BEGIN Mar 4 14:00:28 pervalidus kernel: radeonfb (:01:00.0): Found 262144k of DDR 128 bits wide videoram Mar 4 14:00:29 pervalidus kernel: radeonfb (:01:00.0): mapped 16384k videoram Mar 4 14:00:29 pervalidus kernel: radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=325.00 Mhz, System=200.00 MHz Mar 4 14:00:29 pervalidus kernel: radeonfb: PLL min 2 max 4 Mar 4 14:00:29 pervalidus kernel: 1 chips in connector info Mar 4 14:00:29 pervalidus kernel: - chip 1 has 2 connectors Mar 4 14:00:29 pervalidus kernel: * connector 0 of type 2 (CRT) : 2300 Mar 4 14:00:29 pervalidus kernel: * connector 1 of type 3 (DVI-I) : 3221 Mar 4 14:00:29 pervalidus kernel: Starting monitor auto detection... Mar 4 14:00:29 pervalidus kernel: radeonfb: I2C (port 1) ... not found Mar 4 14:00:29 pervalidus kernel: radeonfb: I2C (port 2) ... not found Mar 4 14:00:29 pervalidus kernel: radeonfb: I2C (port 3) ... found CRT display Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 4) ... not found Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 2) ... not found Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 4) ... not found Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 3) ... found CRT display Mar 4 14:00:30 pervalidus kernel: hStart = 694, hEnd = 757, hTotal = 795 Mar 4 14:00:30 pervalidus kernel: vStart = 402, vEnd = 408, vTotal = 418 Mar 4 14:00:30 pervalidus kernel: h_total_disp = 0x590062^I hsync_strt_wid =0x8702c0 Mar 4 14:00:30 pervalidus kernel: v_total_disp = 0x18f01a1^I vsync_strt_wid = 0x860191 Mar 4 14:00:30 pervalidus kernel: pixclock = 85925 Mar 4 14:00:30 pervalidus kernel: freq = 1163 Mar 4 14:00:30 pervalidus kernel: freq = 1666, PLL min = 2, PLL max = 4 Mar 4 14:00:30 pervalidus kernel: ref_div = 12, ref_clk = 2700, output_freq = 26656 Mar 4 14:00:30 pervalidus kernel: ref_div = 12, ref_clk = 2700, output_freq = 26656 Mar 4 14:00:30 pervalidus kernel: post div = 0x5 Mar 4 14:00:30 pervalidus kernel: fb_div = 0x76 Mar 4 14:00:30 pervalidus kernel: ppll_div_3 = 0x50076 Mar 4 14:00:30 pervalidus kernel: Console: switching to colour frame buffer device 90x25 Mar 4 14:00:30 pervalidus kernel: radeonfb (:01:00.0): ATI Radeon AP Mar 4 14:00:30 pervalidus kernel: radeonfb_pci_register END BTW, I noticed that it locking the system. I was able to issue a shutdown. The commands still work, but beep is disabled. -- How to contact me - http://www.pervalidus.net/contact.html
Re: radeonfb blanks my monitor
On Fri, 4 Mar 2005, Benjamin Herrenschmidt wrote: On Thu, 2005-03-03 at 12:38 -0300, Frédéric L. W. Meunier wrote: Maybe we are having conflicting bus names between radeonfb and matroxfb, or 2 instances of radeonfb ? Can you send the entire log please ? I don't have matroxfb and there aren't 2 instances of radeonfb. There's nothing about radeonfb in dmesg because I manually loaded the modules. And ? You should have it in dmesg after the module load... Not in /var/log/dmesg, and I can't type dmesg. Well, I would need the full log, and with radeonfb verbose debug enabled in the config. I'll later try as module with debug. -- How to contact me - http://www.pervalidus.net/contact.html
Re: radeonfb blanks my monitor
On Thu, 3 Mar 2005, Benjamin Herrenschmidt wrote: There should be more than these... Does it continue booting afte the screen goes blank or not at all ? Can you send the full dmesg log too ? Also, enable radeonfb verbose debug in the config. Yes, there were more in /var/log/syslog: Mar 2 15:16:45 darkstar kernel: radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=325.00 Mhz, System=200.00 MHz Mar 2 15:16:45 darkstar kernel: radeonfb: PLL min 2 max 4 Mar 2 15:16:45 darkstar kernel: i2c-algo-bit.o: monid seems to be busy. Mar 2 15:16:45 darkstar kernel: radeonfb :01:00.0: Failed to register I2C bus monid. Mar 2 15:16:45 darkstar kernel: i2c-algo-bit.o: crt2 seems to be busy. Mar 2 15:16:46 darkstar kernel: radeonfb :01:00.0: Failed to register I2C bus crt2. Mar 2 15:16:46 darkstar kernel: Console: switching to colour frame buffer device 90x25 Mar 2 15:16:46 darkstar kernel: radeonfb (:01:00.0): ATI Radeon AP Do the "seems to be busy." and/or "Failed to register I2C bus" indicate a problem ? There's nothing about radeonfb in dmesg because I manually loaded the modules. I now compiled built-in with debug enabled and got the same problem. Nothing got logged. Everything seems to stop when it blanks, but SysRq works. -- How to contact me - http://www.pervalidus.net/contact.html - 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: radeonfb blanks my monitor
On Thu, 3 Mar 2005, Benjamin Herrenschmidt wrote: There should be more than these... Does it continue booting afte the screen goes blank or not at all ? Can you send the full dmesg log too ? Also, enable radeonfb verbose debug in the config. Yes, there were more in /var/log/syslog: Mar 2 15:16:45 darkstar kernel: radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=325.00 Mhz, System=200.00 MHz Mar 2 15:16:45 darkstar kernel: radeonfb: PLL min 2 max 4 Mar 2 15:16:45 darkstar kernel: i2c-algo-bit.o: monid seems to be busy. Mar 2 15:16:45 darkstar kernel: radeonfb :01:00.0: Failed to register I2C bus monid. Mar 2 15:16:45 darkstar kernel: i2c-algo-bit.o: crt2 seems to be busy. Mar 2 15:16:46 darkstar kernel: radeonfb :01:00.0: Failed to register I2C bus crt2. Mar 2 15:16:46 darkstar kernel: Console: switching to colour frame buffer device 90x25 Mar 2 15:16:46 darkstar kernel: radeonfb (:01:00.0): ATI Radeon AP Do the seems to be busy. and/or Failed to register I2C bus indicate a problem ? There's nothing about radeonfb in dmesg because I manually loaded the modules. I now compiled built-in with debug enabled and got the same problem. Nothing got logged. Everything seems to stop when it blanks, but SysRq works. -- How to contact me - http://www.pervalidus.net/contact.html - 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: radeonfb blanks my monitor
On Fri, 4 Mar 2005, Benjamin Herrenschmidt wrote: On Thu, 2005-03-03 at 12:38 -0300, Frédéric L. W. Meunier wrote: Maybe we are having conflicting bus names between radeonfb and matroxfb, or 2 instances of radeonfb ? Can you send the entire log please ? I don't have matroxfb and there aren't 2 instances of radeonfb. There's nothing about radeonfb in dmesg because I manually loaded the modules. And ? You should have it in dmesg after the module load... Not in /var/log/dmesg, and I can't type dmesg. Well, I would need the full log, and with radeonfb verbose debug enabled in the config. I'll later try as module with debug. -- How to contact me - http://www.pervalidus.net/contact.html
Re: radeonfb blanks my monitor
On Thu, 3 Mar 2005, Benjamin Herrenschmidt wrote: On Wed, 2005-03-02 at 23:51 -0300, Frédéric L. W. Meunier wrote: I just replaced my Matrox G400 with a Jetway Radeon 9600LE (256Mb). If I run 'modprobe radeonfb', the monitor blanks out and the power on light keeps flashing. What may be wrong ? Using 2.6.11. Do you have a way to capture the dmesg log produced ? These are the lines before I have to use SysRq. Mar 2 15:16:45 darkstar kernel: radeonfb: Found Intel x86 BIOS ROM Image Mar 2 15:16:45 darkstar kernel: radeonfb: Retreived PLL infos from BIOS Mar 2 15:16:45 darkstar kernel: i2c-algo-bit.o: dvi passed test. Mar 2 15:16:45 darkstar kernel: i2c-algo-bit.o: vga passed test. Mar 2 15:16:46 darkstar kernel: radeonfb: Monitor 1 type CRT found Mar 2 15:16:46 darkstar kernel: radeonfb: EDID probed Mar 2 15:16:46 darkstar kernel: radeonfb: Monitor 2 type no found BTW, I don't know if it could be related, but my motherboard only supports AGP 4x. Also, does it work if radeonfb is built-in ? I'll try later. Time to sleep. -- How to contact me - http://www.pervalidus.net/contact.html
radeonfb blanks my monitor
I just replaced my Matrox G400 with a Jetway Radeon 9600LE (256Mb). If I run 'modprobe radeonfb', the monitor blanks out and the power on light keeps flashing. What may be wrong ? Using 2.6.11. -- How to contact me - http://www.pervalidus.net/contact.html - 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/
radeonfb blanks my monitor
I just replaced my Matrox G400 with a Jetway Radeon 9600LE (256Mb). If I run 'modprobe radeonfb', the monitor blanks out and the power on light keeps flashing. What may be wrong ? Using 2.6.11. -- How to contact me - http://www.pervalidus.net/contact.html - 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: radeonfb blanks my monitor
On Thu, 3 Mar 2005, Benjamin Herrenschmidt wrote: On Wed, 2005-03-02 at 23:51 -0300, Frédéric L. W. Meunier wrote: I just replaced my Matrox G400 with a Jetway Radeon 9600LE (256Mb). If I run 'modprobe radeonfb', the monitor blanks out and the power on light keeps flashing. What may be wrong ? Using 2.6.11. Do you have a way to capture the dmesg log produced ? These are the lines before I have to use SysRq. Mar 2 15:16:45 darkstar kernel: radeonfb: Found Intel x86 BIOS ROM Image Mar 2 15:16:45 darkstar kernel: radeonfb: Retreived PLL infos from BIOS Mar 2 15:16:45 darkstar kernel: i2c-algo-bit.o: dvi passed test. Mar 2 15:16:45 darkstar kernel: i2c-algo-bit.o: vga passed test. Mar 2 15:16:46 darkstar kernel: radeonfb: Monitor 1 type CRT found Mar 2 15:16:46 darkstar kernel: radeonfb: EDID probed Mar 2 15:16:46 darkstar kernel: radeonfb: Monitor 2 type no found BTW, I don't know if it could be related, but my motherboard only supports AGP 4x. Also, does it work if radeonfb is built-in ? I'll try later. Time to sleep. -- How to contact me - http://www.pervalidus.net/contact.html
Re: EXT2-fs error with 2.4.4 (using CVS)
On Mon, May 07, 2001 at 10:45:59PM -0600, Andreas Dilger wrote:
> > May 8 01:11:29 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir:
>bad entry in
> > directory #162813: directory entry across blocks - offset=92, inode=45,
>rec_len=16404,
> > name_len=9
> Since it is always the same inode, I would say it is corrupt. You need to
> run e2fsck to fix it. It looks like it is a single-bit error on the disk.
> The rec_len=16404=0x4014. One (of many possible) valid rec_len would be
> 0x14=20. To be valid we need name_len <= rec_len <= block size.
OK, I ran.
# fsck -v /dev/ide/host0/bus0/target0/lun0/part3
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
/dev/ide/host0/bus0/target0/lun0/part3 contains a file system with errors, check
forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
159689 inodes used (31%)
1363 non-contiguous inodes (0.9%)
# of inodes with ind/dind/tind blocks: 3884/1/0
408910 blocks used (79%)
0 bad blocks
145848 regular files
13624 directories
0 character device files
0 block device files
0 fifos
2 links
208 symbolic links (208 fast symbolic links)
0 sockets
159682 file
> Chances are, when you run e2fsck, it will fix this dirent, but the rest of
> the directory entries in that block will be moved to lost+found.
Nothing in /usr/local/src/lost+found
> I would suspect a hardware problem, to create a single-bit error (if it
> is such).
I hope not. I know at least my RAM is OK. I installed 256Mb
before booting with 2.4.4 and tested all with memtest86.
CVS couldn't remove mozilla/xpinstall/wizard/windows/nszip
after the process terminated, but
mozilla/xpinstall/wizard/windows/nszip/Entries and
mozilla/xpinstall/wizard/windows/nszip/Tag were updated after
the first EXT2-fs error messages.
Well, everything seems OK for now. Thanks.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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/
EXT2-fs error with 2.4.4 (using CVS)
Hi. I received the following error while updating my Mozilla
sources from MOZILLA_0_8_1_20010326_RELEASE to
MOZILLA_0_9_RELEASE via CVS:
==> /var/log/syslog <==
May 8 00:25:52 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad
entry in
directory #162813: directory entry across blocks - offset=92, inode=45,
rec_len=16404,
name_len=9
May 8 00:25:52 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad
entry in
directory #162813: directory entry across blocks - offset=92, inode=45,
rec_len=16404,
name_len=9
When CVS finished, I received the following error:
May 8 01:11:29 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad
entry in
directory #162813: directory entry across blocks - offset=92, inode=45,
rec_len=16404,
name_len=9
May 8 01:11:29 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad
entry in
directory #162813: directory entry across blocks - offset=92, inode=45,
rec_len=16404,
name_len=9
And the following CVS message:
cvs checkout: cannot remove
mozilla/xpinstall/wizard/windows/nszip: No such file or
directory
When I tried to access
/usr/local/src/CVS/X/mozilla/xpinstall/wizard/windows/ I got
the same EXT2-fs error messages.
The partition is /usr/local/src
(/dev/ide/host0/bus0/target0/lun0/part3)
Is this some sort of ext2 fs corruption or what ? I booted with
2.4.4 9 days ago, and there were no problems with fsck.
checkout start: Tue May 8 00:22:40 BRT 2001
checkout finish: Tue May 8 01:11:31 BRT 2001
My .config is at http://www.pervalidus.net/.config-2.4.4.txt
dmesg at http://www.pervalidus.net/dmesg-2.4.4.txt
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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/
EXT2-fs error with 2.4.4 (using CVS)
Hi. I received the following error while updating my Mozilla
sources from MOZILLA_0_8_1_20010326_RELEASE to
MOZILLA_0_9_RELEASE via CVS:
== /var/log/syslog ==
May 8 00:25:52 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad
entry in
directory #162813: directory entry across blocks - offset=92, inode=45,
rec_len=16404,
name_len=9
May 8 00:25:52 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad
entry in
directory #162813: directory entry across blocks - offset=92, inode=45,
rec_len=16404,
name_len=9
When CVS finished, I received the following error:
May 8 01:11:29 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad
entry in
directory #162813: directory entry across blocks - offset=92, inode=45,
rec_len=16404,
name_len=9
May 8 01:11:29 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad
entry in
directory #162813: directory entry across blocks - offset=92, inode=45,
rec_len=16404,
name_len=9
And the following CVS message:
cvs checkout: cannot remove
mozilla/xpinstall/wizard/windows/nszip: No such file or
directory
When I tried to access
/usr/local/src/CVS/X/mozilla/xpinstall/wizard/windows/ I got
the same EXT2-fs error messages.
The partition is /usr/local/src
(/dev/ide/host0/bus0/target0/lun0/part3)
Is this some sort of ext2 fs corruption or what ? I booted with
2.4.4 9 days ago, and there were no problems with fsck.
checkout start: Tue May 8 00:22:40 BRT 2001
checkout finish: Tue May 8 01:11:31 BRT 2001
My .config is at http://www.pervalidus.net/.config-2.4.4.txt
dmesg at http://www.pervalidus.net/dmesg-2.4.4.txt
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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: EXT2-fs error with 2.4.4 (using CVS)
On Mon, May 07, 2001 at 10:45:59PM -0600, Andreas Dilger wrote:
skip
May 8 01:11:29 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir:
bad entry in
directory #162813: directory entry across blocks - offset=92, inode=45,
rec_len=16404,
name_len=9
Since it is always the same inode, I would say it is corrupt. You need to
run e2fsck to fix it. It looks like it is a single-bit error on the disk.
The rec_len=16404=0x4014. One (of many possible) valid rec_len would be
0x14=20. To be valid we need name_len = rec_len = block size.
OK, I ran.
# fsck -v /dev/ide/host0/bus0/target0/lun0/part3
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
/dev/ide/host0/bus0/target0/lun0/part3 contains a file system with errors, check
forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
159689 inodes used (31%)
1363 non-contiguous inodes (0.9%)
# of inodes with ind/dind/tind blocks: 3884/1/0
408910 blocks used (79%)
0 bad blocks
145848 regular files
13624 directories
0 character device files
0 block device files
0 fifos
2 links
208 symbolic links (208 fast symbolic links)
0 sockets
159682 file
Chances are, when you run e2fsck, it will fix this dirent, but the rest of
the directory entries in that block will be moved to lost+found.
Nothing in /usr/local/src/lost+found
I would suspect a hardware problem, to create a single-bit error (if it
is such).
I hope not. I know at least my RAM is OK. I installed 256Mb
before booting with 2.4.4 and tested all with memtest86.
CVS couldn't remove mozilla/xpinstall/wizard/windows/nszip
after the process terminated, but
mozilla/xpinstall/wizard/windows/nszip/Entries and
mozilla/xpinstall/wizard/windows/nszip/Tag were updated after
the first EXT2-fs error messages.
Well, everything seems OK for now. Thanks.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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 IDE driver status ?
I'm not overclocking. It's an ASUS A7Pro with Athlon 1000. I
had the same problem with an ASUS K7V with Athlon 700. But
the processor died after my cooler failed for 20 minutes!
BTW, how do I know if my cable is ATA100/ATA66, not only ATA66
? The manual from the A7Pro says it supports both, but at the
site it says the cable shipped with this motherboard is ATA66.
On Sat, Mar 31, 2001 at 12:00:41PM -0600, Glenn C. Hofmann wrote:
> I am not sure if this applies in your case, but I was getting problems
> such as this on my Abit KT7-RAID and had the correct cables, also. One
> day, on a hunch after reading a post from Alan about overclocking, I
> took my Athlon 750 down to 850 from 1.05 GHz and all is working great
> now. If your overclocking, I would suggest not doing so (at least not
> so much), based on my experience. I am also using the v4.0 driver.
>
> Chris
>
> On 31 Mar 2001 00:41:32 -0300, Frédéric L. W. Meunier wrote:
> > Hi. I really can't get UDMA66 with the VIA driver. I tried
> > everything, also a new motherboard (ASUS A7Pro) with a
> > ATA100/ATA66 cable (using both ends...)!
> >
> > All I get are the usual CRC error messages.
> >
> > So, there's no UDMA66 for any vt82c686a ? I'm using 2.4.3.
> >
> > If there's no UDMA66, what are the advantages using this
> > driver ?
> >
> > TIA.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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 IDE driver status ?
I'm not overclocking. It's an ASUS A7Pro with Athlon 1000. I
had the same problem with an ASUS K7V with Athlon 700. But
the processor died after my cooler failed for 20 minutes!
BTW, how do I know if my cable is ATA100/ATA66, not only ATA66
? The manual from the A7Pro says it supports both, but at the
site it says the cable shipped with this motherboard is ATA66.
On Sat, Mar 31, 2001 at 12:00:41PM -0600, Glenn C. Hofmann wrote:
I am not sure if this applies in your case, but I was getting problems
such as this on my Abit KT7-RAID and had the correct cables, also. One
day, on a hunch after reading a post from Alan about overclocking, I
took my Athlon 750 down to 850 from 1.05 GHz and all is working great
now. If your overclocking, I would suggest not doing so (at least not
so much), based on my experience. I am also using the v4.0 driver.
Chris
On 31 Mar 2001 00:41:32 -0300, Frdric L. W. Meunier wrote:
Hi. I really can't get UDMA66 with the VIA driver. I tried
everything, also a new motherboard (ASUS A7Pro) with a
ATA100/ATA66 cable (using both ends...)!
All I get are the usual CRC error messages.
So, there's no UDMA66 for any vt82c686a ? I'm using 2.4.3.
If there's no UDMA66, what are the advantages using this
driver ?
TIA.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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/
VIA IDE driver status ?
Hi. I really can't get UDMA66 with the VIA driver. I tried
everything, also a new motherboard (ASUS A7Pro) with a
ATA100/ATA66 cable (using both ends...)!
All I get are the usual CRC error messages.
So, there's no UDMA66 for any vt82c686a ? I'm using 2.4.3.
If there's no UDMA66, what are the advantages using this
driver ?
TIA.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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/
2.4.3: INIT: PANIC: segmentation violation...
I get the message segmentation violation at XXX! sleeping for
30 seconds. with 2.4.3.
No problems with 2.4.2 and the same configuration.
Any hints ?
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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/
2.4.3: INIT: PANIC: segmentation violation...
I get the message segmentation violation at XXX! sleeping for
30 seconds. with 2.4.3.
No problems with 2.4.2 and the same configuration.
Any hints ?
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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/
VIA IDE driver status ?
Hi. I really can't get UDMA66 with the VIA driver. I tried
everything, also a new motherboard (ASUS A7Pro) with a
ATA100/ATA66 cable (using both ends...)!
All I get are the usual CRC error messages.
So, there's no UDMA66 for any vt82c686a ? I'm using 2.4.3.
If there's no UDMA66, what are the advantages using this
driver ?
TIA.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No such file or directory))
Maybe I should give details about my hardware. The system was
installed 5 months ago, and this is the first problem.
I used 2.2.16 stock Kernel from Slackware 7.1
2.2.17
2.2.18
2.4.0
2.4.1
And the only problem was with 2.4.2.
FYI, I'm not using hdparm or changing the BIOS to use UDMA 66.
It'd fail with 2.4.1 and 2.4.2 (CRC errors), so the setting
is AUTO and it's using UDMA 33.
And please note that this machine is fine, but I actually only
open 2 consoles and run GNU screen. No XFree86, and only a few
applications running.
If needed, my /var/log/dmesg is at
http://members.nbci.com/pervalidus/dmesg-2.4.2.txt
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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/
2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No such file or directory))
Hi. After a reboot I had to manually run fsck (sulogin from
sysinit script) since there were failures.
In my second (and problematic) boot with 2.4.2 I used the
option mount --bind in my sysinit script to mount the old /dev
in /dev-old before devfs was mounted, so I could get rid of all
entries that were still there (I removed most before building a
Kernel with devfs support).
For some reason I couldn't remove /dev-old/hdd2. It reported
can't state file. Note that I never used /dev/hdd*, since I
only use hda and hdc, but am sure it was OK with 2.4.0 (mc
reported an error when I accessed /dev-old, what never happened
before), the last time I used a Kernel without devfs support.
If you read my old thread, you should notice various
applications couldn't access (or rename ?) files. It happened
after ~8h of idle time. It was OK at 5:58, when I last ran cvs
and killed pppd, but failed at ~14:30, when multilog (from
daemontools) had to do something to a full dnscache log file (I
was online).
I'm not sure 2.4.2 is the culprit. I just hope it's the last
time. There were no errors when I first booted with this Kernel
(I was using 2.4.1), and my first uptime was ~6 days (~23 with
2.4.1). Also there were no errors when I booted 2.4.2 for the
second time.
BTW, /lost+found contains hdd2:
brw-r-1 root disk 22, 66 May 8 1995 #518878
The other partitions (/home/ftp/pub and /usr/local/src) have no
problems.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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/
2.4.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No such file or directory))
Hi. After a reboot I had to manually run fsck (sulogin from
sysinit script) since there were failures.
In my second (and problematic) boot with 2.4.2 I used the
option mount --bind in my sysinit script to mount the old /dev
in /dev-old before devfs was mounted, so I could get rid of all
entries that were still there (I removed most before building a
Kernel with devfs support).
For some reason I couldn't remove /dev-old/hdd2. It reported
can't state file. Note that I never used /dev/hdd*, since I
only use hda and hdc, but am sure it was OK with 2.4.0 (mc
reported an error when I accessed /dev-old, what never happened
before), the last time I used a Kernel without devfs support.
If you read my old thread, you should notice various
applications couldn't access (or rename ?) files. It happened
after ~8h of idle time. It was OK at 5:58, when I last ran cvs
and killed pppd, but failed at ~14:30, when multilog (from
daemontools) had to do something to a full dnscache log file (I
was online).
I'm not sure 2.4.2 is the culprit. I just hope it's the last
time. There were no errors when I first booted with this Kernel
(I was using 2.4.1), and my first uptime was ~6 days (~23 with
2.4.1). Also there were no errors when I booted 2.4.2 for the
second time.
BTW, /lost+found contains hdd2:
brw-r-1 root disk 22, 66 May 8 1995 #518878
The other partitions (/home/ftp/pub and /usr/local/src) have no
problems.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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.2 ext2 filesystem corruption ? (was 2.4.2: What happened ? (No such file or directory))
Maybe I should give details about my hardware. The system was
installed 5 months ago, and this is the first problem.
I used 2.2.16 stock Kernel from Slackware 7.1
2.2.17
2.2.18
2.4.0
2.4.1
And the only problem was with 2.4.2.
FYI, I'm not using hdparm or changing the BIOS to use UDMA 66.
It'd fail with 2.4.1 and 2.4.2 (CRC errors), so the setting
is AUTO and it's using UDMA 33.
And please note that this machine is fine, but I actually only
open 2 consoles and run GNU screen. No XFree86, and only a few
applications running.
If needed, my /var/log/dmesg is at
http://members.nbci.com/pervalidus/dmesg-2.4.2.txt
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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: ide / usb problem
Alan Cox wrote:
>> I was not sure if the VIA82CXXX option should be set with the
>> via kt133 chipset , but setting it results in hundreds of
>> hda: dma_intr:status=0x51 { DriveReady SeekComplete Error }
>> hda: dma_intr:error=0x84 { DriveStatusError BadCRC }
>> mesages along with the uhci: errors mentioned above. Again ,
>> the directory was copied correctly.
> That indicates cable problems. The CRC will avoid bad transfers
> as it will do retries
Oh my god. Are you sure it's a cable problem? I'm using the
cable shipped by ASUS with my K7V and have the same problem:
devfs: v0.102 (2622) Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x2
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
Again, if it's really a cable problem, then ASUS is selling
cables that don't work with UDMA66 (but they sell it as
UDMA66).
I urge ASUS to explain this problem. If you do a search for
BadCRC at any lkml archive, you should notice most complaints
are from... VIA (and most seem to have an ASUS motherboard).
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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: ide / usb problem
Alan Cox wrote:
I was not sure if the VIA82CXXX option should be set with the
via kt133 chipset , but setting it results in hundreds of
hda: dma_intr:status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr:error=0x84 { DriveStatusError BadCRC }
mesages along with the uhci: errors mentioned above. Again ,
the directory was copied correctly.
That indicates cable problems. The CRC will avoid bad transfers
as it will do retries
Oh my god. Are you sure it's a cable problem? I'm using the
cable shipped by ASUS with my K7V and have the same problem:
devfs: v0.102 (2622) Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x2
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
Again, if it's really a cable problem, then ASUS is selling
cables that don't work with UDMA66 (but they sell it as
UDMA66).
I urge ASUS to explain this problem. If you do a search for
BadCRC at any lkml archive, you should notice most complaints
are from... VIA (and most seem to have an ASUS motherboard).
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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/
Why CONFIG_MPENTIUMIII by default?
Is there any reason to use CONFIG_MPENTIUMIII by default? I
think this should be changed to CONFIG_M386, which should work
for most, and would avoid people reporting problems because
they forgot to set the right processor type.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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/
Why CONFIG_MPENTIUMIII by default?
Is there any reason to use CONFIG_MPENTIUMIII by default? I
think this should be changed to CONFIG_M386, which should work
for most, and would avoid people reporting problems because
they forgot to set the right processor type.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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: [PATCH] modify ver_linux to check e2fsprogs and more.
Jochen Striepe wrote:
> tolot:/root # hostname --version
> hostname (GNU sh-utils) 2.0.11
> Written by Jim Meyering.
AFAIK, all distributions use hostname from net-tools, not from
sh-utils.
% hostname -V
net-tools 1.57
hostname 1.99 (2000-02-13)
Why duplicate it (on Linux) ?
--
Frédéric L. W. Meunier - http://www.pervalidus.net/
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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: [PATCH] modify ver_linux to check e2fsprogs and more.
Jochen Striepe wrote:
tolot:/root # hostname --version
hostname (GNU sh-utils) 2.0.11
Written by Jim Meyering.
AFAIK, all distributions use hostname from net-tools, not from
sh-utils.
% hostname -V
net-tools 1.57
hostname 1.99 (2000-02-13)
Why duplicate it (on Linux) ?
--
Frdric L. W. Meunier - http://www.pervalidus.net/
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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: Fix for include/linux/fs.h in 2.4.0 kernels
Keith Owens wrote:
> Rule 2. Any glibc that has a symlink from
> /usr/include/{linux,asm} to /usr/src/linux/include/{linux,asm}
> is wrong.
Such symlinks are created by the user.
> Relying on /usr/include/{linux,asm} always pointing at the
> current kernel source is broken as designed.
From glibc 2.2.1 FAQ:
2.17. I have /usr/include/net and /usr/include/scsi as symlinks
into my Linux source tree. Is that wrong?
{PB} This was necessary for libc5, but is not correct when
using glibc. Including the kernel header files directly in user
programs usually does not work (see question 3.5). glibc
provides its own and header files to replace
them, and you may have to remove any symlink that you have in
place before you install glibc. However, /usr/include/asm and
/usr/include/linux should remain as they were.
Keith, are you saying that glibc is wrong?
3.5.On Linux I've got problems with the declarations in Linux
kernel headers.
{UD,AJ} On Linux, the use of kernel headers is reduced to the
minimum. This gives Linus the ability to change the headers
more freely. Also, user programs are now insulated from changes
in the size of kernel data structures.
For example, the sigset_t type is 32 or 64 bits wide in the
kernel. In glibc it is 1024 bits wide. This guarantees that
when the kernel gets a bigger sigset_t (for POSIX.1e realtime
support, say) user programs will not have to be recompiled.
Consult the header files for more information about the
changes.
Therefore you shouldn't include Linux kernel header files
directly if glibc has defined a replacement. Otherwise you
might get undefined results because of type conflicts.
> /usr/include/{linux,asm} must be real directories that are
> shipped as part of glibc, not symlinks to some random version
> of the kernel. Fix /usr/include.
But make install didn't create them. I built 2.2 and 2.2.1.
--
Frédéric L. W. Meunier - http://www.pervalidus.net/
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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: svgalib problem
> svgalib: mmap error in paged screen memory.
A fix is to build SVGAlib without background execution support.
Take a look at http://www.arava.co.il/matan/svgalib/hypermail/
--
Frédéric L. W. Meunier - http://www.pervalidus.net/
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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: svgalib problem
svgalib: mmap error in paged screen memory.
A fix is to build SVGAlib without background execution support.
Take a look at http://www.arava.co.il/matan/svgalib/hypermail/
--
Frdric L. W. Meunier - http://www.pervalidus.net/
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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: Fix for include/linux/fs.h in 2.4.0 kernels
Keith Owens wrote:
Rule 2. Any glibc that has a symlink from
/usr/include/{linux,asm} to /usr/src/linux/include/{linux,asm}
is wrong.
Such symlinks are created by the user.
Relying on /usr/include/{linux,asm} always pointing at the
current kernel source is broken as designed.
From glibc 2.2.1 FAQ:
2.17. I have /usr/include/net and /usr/include/scsi as symlinks
into my Linux source tree. Is that wrong?
{PB} This was necessary for libc5, but is not correct when
using glibc. Including the kernel header files directly in user
programs usually does not work (see question 3.5). glibc
provides its own net/* and scsi/* header files to replace
them, and you may have to remove any symlink that you have in
place before you install glibc. However, /usr/include/asm and
/usr/include/linux should remain as they were.
Keith, are you saying that glibc is wrong?
3.5.On Linux I've got problems with the declarations in Linux
kernel headers.
{UD,AJ} On Linux, the use of kernel headers is reduced to the
minimum. This gives Linus the ability to change the headers
more freely. Also, user programs are now insulated from changes
in the size of kernel data structures.
For example, the sigset_t type is 32 or 64 bits wide in the
kernel. In glibc it is 1024 bits wide. This guarantees that
when the kernel gets a bigger sigset_t (for POSIX.1e realtime
support, say) user programs will not have to be recompiled.
Consult the header files for more information about the
changes.
Therefore you shouldn't include Linux kernel header files
directly if glibc has defined a replacement. Otherwise you
might get undefined results because of type conflicts.
/usr/include/{linux,asm} must be real directories that are
shipped as part of glibc, not symlinks to some random version
of the kernel. Fix /usr/include.
But make install didn't create them. I built 2.2 and 2.2.1.
--
Frdric L. W. Meunier - http://www.pervalidus.net/
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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: problem with devfsd compilation
Georg Nikodym wrote:
> Also, RH7's /etc/rc.sysinit can already start devfsd
> automatically with the following line:
> [ -e /dev/.devfsd -a -x /sbin/devfsd ] && /sbin/devfsd /dev
If devfs is mounted and devfsd exists, start devfsd.
> So, all you have to do is create an empty file /dev/.devfsd
Not true. I'm pretty sure /dev/.devfsd is only created when you
mount devfs at boot time or via mount -t devfs devfs /dev in
your system initialization script. Creating /dev/.devfsd with
touch defeats the purpose of /etc/rc.sysinit example.
crw--- 1 root root 144, 0 Dec 31 1969 .devfsd
--
Frédéric L. W. Meunier - http://www.pervalidus.net/
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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: problem with devfsd compilation
Georg Nikodym wrote:
Also, RH7's /etc/rc.sysinit can already start devfsd
automatically with the following line:
[ -e /dev/.devfsd -a -x /sbin/devfsd ] /sbin/devfsd /dev
If devfs is mounted and devfsd exists, start devfsd.
So, all you have to do is create an empty file /dev/.devfsd
Not true. I'm pretty sure /dev/.devfsd is only created when you
mount devfs at boot time or via mount -t devfs devfs /dev in
your system initialization script. Creating /dev/.devfsd with
touch defeats the purpose of /etc/rc.sysinit example.
crw--- 1 root root 144, 0 Dec 31 1969 .devfsd
--
Frdric L. W. Meunier - http://www.pervalidus.net/
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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/
2.4.1 with pppd 2.4.0: log problem
Hi. It worked without any problems with 2.4.0. Now with 2.4.1 I
don't get anymore the usual messages in /var/log/messages (like
pppd start and local and remote IP). The only change was the
addition of devfs, but I don't think it's causing this problem.
Any hints? I didn't change anything on my machine.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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: VIA VT82C686X
Me too. But I couldn't get UDMA 66 after changing my BIOS
settings and booting. With 33 it's very stable (what I used
with 2.4.0). A diff:
-hda: 30015216 sectors (15368 MB) w/2048KiB Cache, CHS=1868/255/63, UDMA(33)
+hda: 30015216 sectors (15368 MB) w/2048KiB Cache, CHS=1868/255/63, UDMA(66)
...
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
+hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
VFS: Mounted root (ext2 filesystem) readonly.
-Freeing unused kernel memory: 200k freed
+Freeing unused kernel memory: 204k freed
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
+hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
+hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
+hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
+hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+ide0: reset: success
I know this is a known issue, but I thought testing would be
OK. ASUS K7V with the shipped cable.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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: VIA VT82C686X
Me too. But I couldn't get UDMA 66 after changing my BIOS
settings and booting. With 33 it's very stable (what I used
with 2.4.0). A diff:
-hda: 30015216 sectors (15368 MB) w/2048KiB Cache, CHS=1868/255/63, UDMA(33)
+hda: 30015216 sectors (15368 MB) w/2048KiB Cache, CHS=1868/255/63, UDMA(66)
...
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
+hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
VFS: Mounted root (ext2 filesystem) readonly.
-Freeing unused kernel memory: 200k freed
+Freeing unused kernel memory: 204k freed
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
+hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
+hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
+hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
+hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
+ide0: reset: success
I know this is a known issue, but I thought testing would be
OK. ASUS K7V with the shipped cable.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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/
2.4.1 with pppd 2.4.0: log problem
Hi. It worked without any problems with 2.4.0. Now with 2.4.1 I
don't get anymore the usual messages in /var/log/messages (like
pppd start and local and remote IP). The only change was the
addition of devfs, but I don't think it's causing this problem.
Any hints? I didn't change anything on my machine.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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: 2.4.0 umount problem
Just FYI, when 2.2.0 was released (yes, 2.2), I moved from
2.0.36 to it on a RedHat 5.1 with all the updates and the rest
built from scratch. And shutting down the system gave me the
same results: / -> device or resource busy. No need to say
that fsck was used. The other partitions were cleanly
unmounted.
2.2.1 was released after some days. Rebooting with this Kernel
would do the same. Then (I was too lazy to try fuser or lsof) I
started doing init 1 and umount / for half a year, then it
worked again (I don't know what changed, but I never edited the
RedHat scripts).
BTW, what's the problem with devfs? I plan to use it, but now
am afraid.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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: 2.4.0 umount problem
Just FYI, when 2.2.0 was released (yes, 2.2), I moved from
2.0.36 to it on a RedHat 5.1 with all the updates and the rest
built from scratch. And shutting down the system gave me the
same results: / - device or resource busy. No need to say
that fsck was used. The other partitions were cleanly
unmounted.
2.2.1 was released after some days. Rebooting with this Kernel
would do the same. Then (I was too lazy to try fuser or lsof) I
started doing init 1 and umount / for half a year, then it
worked again (I don't know what changed, but I never edited the
RedHat scripts).
BTW, what's the problem with devfs? I plan to use it, but now
am afraid.
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niteri-RJ BR)
-
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/
make menuconfig: where's USB Mass Storage?
Is this just me? Configuring 2.4.0 with make menuconfig with
CONFIG_EXPERIMENTAL=y I get no prompt for USB Mass Storage,
but the .config is saved with # CONFIG_USB_STORAGE is not set
I have the following:
#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
CONFIG_USB_UHCI_ALT=m
# CONFIG_USB_OHCI is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH is not set
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
CONFIG_USB_SCANNER=m
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_PLUSB is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_NET1080 is not set
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_RIO500 is not set
I checked a lot of times, and there's no such option here.
< > OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support
--- USB Device Class drivers
< > USB Audio support
< > USB Bluetooth support (EXPERIMENTAL)
< > USB Modem (CDC ACM) support
--
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
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: USB mass storage backport status?
On Tue, Dec 12, 2000 at 08:08:40PM -0800, Matthew Dharm wrote:
> Depending on the type of device you have and how you use it, it can either:
> (1) Work properly
> (2) Corrupt your data
> (3) Crash the driver
> (4) Crash your system
The reboot was about Iomega's Zip Drive under 2.2.18pre21:
http://slashdot.org/comments.pl?sid=00/12/11/2355217=0=1=thread=110
> It's allready labeled EXPERIMENTAL. Perhaps it should be labeled
> DANGEROUS, also, but how many labels can you put on things to warn people
> off?
Hmm, where? I don't see an (EXPERIMENTAL) in
Documentation/Configure.help:
USB Mass Storage support
CONFIG_USB_STORAGE
Say Y here if you want to connect USB mass storage devices to your
computer's USB port.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called usb-storage.o. If you want to compile it
as a module, say M here and read Documentation/modules.txt.
USB Mass Storage verbose debug
CONFIG_USB_STORAGE_DEBUG
Say Y here in order to have the USB Mass Storage code generate
verbose debugging messages.
Maybe it's only enabled when you set CONFIG_EXPERIMENTAL? I don't know, because I
enabled
it to just set CONFIG_FB.
> On Wed, Dec 13, 2000 at 01:41:54AM -0200, Frédéric L . W . Meunier wrote:
> > What's the real status of the mass storage backport to 2.2.18?
> > Some people report it can corrupt your data, another that it
> > rebooted his computer while doing a large trasnfer, and so on.
> >
> > If it's not good, shouldn't it be removed or labeled
> > DANGEROUS? BTW, where can I see a list of what's backported
> > and working without major problems?
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
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/
USB mass storage backport status?
What's the real status of the mass storage backport to 2.2.18?
Some people report it can corrupt your data, another that it
rebooted his computer while doing a large trasnfer, and so on.
If it's not good, shouldn't it be removed or labeled
DANGEROUS? BTW, where can I see a list of what's backported
and working without major problems?
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
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/
USB mass storage backport status?
What's the real status of the mass storage backport to 2.2.18?
Some people report it can corrupt your data, another that it
rebooted his computer while doing a large trasnfer, and so on.
If it's not good, shouldn't it be removed or labeled
DANGEROUS? BTW, where can I see a list of what's backported
and working without major problems?
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
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: USB mass storage backport status?
On Tue, Dec 12, 2000 at 08:08:40PM -0800, Matthew Dharm wrote:
Depending on the type of device you have and how you use it, it can either:
(1) Work properly
(2) Corrupt your data
(3) Crash the driver
(4) Crash your system
The reboot was about Iomega's Zip Drive under 2.2.18pre21:
http://slashdot.org/comments.pl?sid=00/12/11/2355217threshold=0commentsort=1mode=threadcid=110
It's allready labeled EXPERIMENTAL. Perhaps it should be labeled
DANGEROUS, also, but how many labels can you put on things to warn people
off?
Hmm, where? I don't see an (EXPERIMENTAL) in
Documentation/Configure.help:
USB Mass Storage support
CONFIG_USB_STORAGE
Say Y here if you want to connect USB mass storage devices to your
computer's USB port.
This code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called usb-storage.o. If you want to compile it
as a module, say M here and read Documentation/modules.txt.
USB Mass Storage verbose debug
CONFIG_USB_STORAGE_DEBUG
Say Y here in order to have the USB Mass Storage code generate
verbose debugging messages.
Maybe it's only enabled when you set CONFIG_EXPERIMENTAL? I don't know, because I
enabled
it to just set CONFIG_FB.
On Wed, Dec 13, 2000 at 01:41:54AM -0200, Frédéric L . W . Meunier wrote:
What's the real status of the mass storage backport to 2.2.18?
Some people report it can corrupt your data, another that it
rebooted his computer while doing a large trasnfer, and so on.
If it's not good, shouldn't it be removed or labeled
DANGEROUS? BTW, where can I see a list of what's backported
and working without major problems?
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
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: [PATCH] ide-pci.c: typo
Alan Cox wrote:
> I disagree with the patch. The bug is in printk
No problem. So, it's a bug report instead. I have no clues,
and just thought it'd be a fix :)
Not sure if 2.2.17 reported the double %% from syslog. I
usually look at my dmesg.
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
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: warning during make modules
Is this a 2.4.0 issue? Because I see the warnings on 2.2.18
too, and also building alsa-driver. I use modutils 2.3.22.
binutils 2.10.1.0.2. glibc 2.2.
2.2.17 reported the same, 2.4.0-test11 too (but I never ran
this one).
The compiler is egcs 1.1.2. gcc is a symlink to egcs-2.1.96.
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
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/
[PATCH] ide-pci.c: typo
dmesg: VP_IDE: not 100% native mode: will probe irqs later
syslog: Dec 11 14:28:48 pervalidus kernel: VP_IDE: not 100%% native mode: will probe
irqs later
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
--- linux/drivers/block/ide-pci.c.old Sun Dec 10 23:10:22 2000
+++ linux/drivers/block/ide-pci.c Mon Dec 11 20:16:36 2000
@@ -344,7 +344,7 @@
*/
pciirq = dev->irq;
if ((dev->class & ~(0xfa)) != ((PCI_CLASS_STORAGE_IDE << 8) | 5)) {
- printk("%s: not 100%% native mode: will probe irqs later\n", d->name);
+ printk("%s: not 100% native mode: will probe irqs later\n", d->name);
pciirq = ide_special_settings(dev, d->name);
} else if (tried_config) {
printk("%s: will probe irqs later\n", d->name);
[PATCH] ide-pci.c: typo
dmesg: VP_IDE: not 100% native mode: will probe irqs later
syslog: Dec 11 14:28:48 pervalidus kernel: VP_IDE: not 100%% native mode: will probe
irqs later
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
--- linux/drivers/block/ide-pci.c.old Sun Dec 10 23:10:22 2000
+++ linux/drivers/block/ide-pci.c Mon Dec 11 20:16:36 2000
@@ -344,7 +344,7 @@
*/
pciirq = dev-irq;
if ((dev-class ~(0xfa)) != ((PCI_CLASS_STORAGE_IDE 8) | 5)) {
- printk("%s: not 100%% native mode: will probe irqs later\n", d-name);
+ printk("%s: not 100% native mode: will probe irqs later\n", d-name);
pciirq = ide_special_settings(dev, d-name);
} else if (tried_config) {
printk("%s: will probe irqs later\n", d-name);
Re: warning during make modules
Is this a 2.4.0 issue? Because I see the warnings on 2.2.18
too, and also building alsa-driver. I use modutils 2.3.22.
binutils 2.10.1.0.2. glibc 2.2.
2.2.17 reported the same, 2.4.0-test11 too (but I never ran
this one).
The compiler is egcs 1.1.2. gcc is a symlink to egcs-2.1.96.
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
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: [PATCH] ide-pci.c: typo
Alan Cox wrote:
I disagree with the patch. The bug is in printk
No problem. So, it's a bug report instead. I have no clues,
and just thought it'd be a fix :)
Not sure if 2.2.17 reported the double %% from syslog. I
usually look at my dmesg.
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
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/
SysRq behavior
I don't remember having the same problem months (6?) ago when
I built my first Kernel with this enabled (well, maybe I never
touched the key).
When built into the Kernel, by only pressing the
PrintScreen/SysRq the current application is terminated (tested
on a console and GNU screen). Is this just me or I should
expect it?
% calc
C-style arbitrary precision calculator (version 2.11.2t1.0)
Calc is open software. For license details type: help
copyright
[Type "exit" to exit, or "help" for help.]
> zsh: quit
While running the application I press the key and you see the
result. It's very annoying because I accidentaly keep touching
it.
Kernel 2.2.17 on x86 (br-abnt2 keyboard, kbd 1.03). glibc 2.2,
but Kernel compiled with egcs 1.1.2.
The SysRq stuff works:
Dec 9 04:09:05 pervalidus kernel: SysRq: unRaw saK Boot Sync
Unmount showPc showTasks showMem loglevel0-8 tErm kIll killalL
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
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/
SysRq behavior
I don't remember having the same problem months (6?) ago when
I built my first Kernel with this enabled (well, maybe I never
touched the key).
When built into the Kernel, by only pressing the
PrintScreen/SysRq the current application is terminated (tested
on a console and GNU screen). Is this just me or I should
expect it?
% calc
C-style arbitrary precision calculator (version 2.11.2t1.0)
Calc is open software. For license details type: help
copyright
[Type "exit" to exit, or "help" for help.]
zsh: quit
While running the application I press the key and you see the
result. It's very annoying because I accidentaly keep touching
it.
Kernel 2.2.17 on x86 (br-abnt2 keyboard, kbd 1.03). glibc 2.2,
but Kernel compiled with egcs 1.1.2.
The SysRq stuff works:
Dec 9 04:09:05 pervalidus kernel: SysRq: unRaw saK Boot Sync
Unmount showPc showTasks showMem loglevel0-8 tErm kIll killalL
--
0@pervalidus.{net,{dyndns.}org} TelFax: 55-21-717-2399 (Niterói-RJ BR)
-
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/
make oldconfig with menuconfig
What's the best way to use make oldconfig with menuconfig?
oldconfig with config isn't what will make my life easier.
TIA.
--
0@pervalidus.{net, com, dyndns.org}
-
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/
make oldconfig with menuconfig
What's the best way to use make oldconfig with menuconfig?
oldconfig with config isn't what will make my life easier.
TIA.
--
0@pervalidus.{net, com, dyndns.org}
-
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: gcc-2.95.2-51 is buggy
[EMAIL PROTECTED] wrote:
> % /usr/gcc/aeb/bin/gcc -v
> Reading specs from
> /usr/gcc/aeb/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/specs
> gcc version 2.95.2 19991024 (release)gcc version 2.95.2 19991024 (release)
> % /usr/gcc/aeb/bin/gcc -Wall -O2 -o nobug bug.c; ./nobug
> 0x0
Interesting. On a Slackware 7.1 recently upgraded to glibc 2.2
(and where gcc 2.95.2 from ftp.gnu.org was built because 2.2
requires this version) I get:
% gcc -Wall -O2 -o bug bug.c
% ./bug
0x8480
% egcs-2.91.66 -Wall -O2 -o bug bug.c
% ./bug
0x0
% gcc -Wall -O -o bug bug.c
% ./bug
0x0
% gcc -v
Reading specs from
/usr/lib/gcc-lib/i386-slackware-linux/2.95.2/specs
gcc version 2.95.2 19991024 (release)
% egcs-2.91.66 -v
Reading specs from
/usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
Slackware's -current tree was upgraded to glibc 2.2 and gcc
2.95.2, but I built them myself.
--
0@pervalidus.{net, com, dyndns.org}
-
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/
