Re: Dual Athlon on 2.2.19 ?
Without the patch below the boot up would hang right after it detected the ide devices.
After applying the patch it booted all the way but the keyboard would hang.
BTW I'm trying to port this patch back to the 2.2.18 TL-Kernel. Are there anymore
changes I have to
look at ?
--- arch/i386/kernel/io_apic.c.old Wed May 16 12:48:03 2001
+++ arch/i386/kernel/io_apic.c Wed May 16 12:55:30 2001
@@ -204,6 +204,8 @@
/*
* We disable IO-APIC IRQs by setting their 'destination CPU mask' to
* zero. Trick by Ramesh Nalluri.
+ * Not anymore. This causes problems on some IO-APIC's, notably AMD 760MP's
+ * So we do it a more 2.4 kind of way now which should be safer -jerdfelt
*/
DO_ACTION( mask,0, |= 0x0001, io_apic_sync(entry->apic))/* mask = 1 */
DO_ACTION( unmask, 0, &= 0xfffe, )/* mask = 0 */
@@ -646,8 +648,8 @@
entry.delivery_mode = dest_LowestPrio;
entry.dest_mode = 1;/* logical delivery */
- entry.mask = 0; /* enable IRQ */
- entry.dest.logical.logical_dest = 0xff; /* but no route */
+ entry.mask = 1; /* disable IRQ */
+ entry.dest.logical.logical_dest = 0xff;
idx = find_irq_entry(apic,pin,mp_INT);
if (idx == -1) {
On Thu, May 24, 2001 at 03:36:54PM -0400, Johannes Erdfelt wrote:
> On Thu, May 24, 2001, Prasanna P Subash <[EMAIL PROTECTED]> wrote:
> > I have a dual athlon on the 760MP chipset.
> > 2.2.20pre1 and 2 dont work. I got it to work partly after applying Johannes
> > Erdfel's 760MP patch in io_apic.c. Even after applying the patch, there
> > are messages like
>
> 2.2.20pre1 and pre2 both have the patch I created already applied. If
> you had to apply them yourself then something is wrong.
>
> > hdc: IRQ probe failed(0)
> > hdd: IRQ probe failed(0)
> > hde: IRQ probe failed(0)
> >
> > hdc: lost interrupt
> > hdc: lost interrupt
> >
> > and then the machine hangs randomly. I an guessing the io_apic does not
> > route the interrupts correctly.
>
> That would be the problem.
>
> Which patch of mine did you apply? Which motherboard are you doing your
> testing with?
>
> JE
--
Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC
Linux, the choice | The only real advantage to punk music is
of a GNU generation -o) | that nobody can whistle it.
Kernel 2.4.1 /\\ |
on a i686_\\_v |
|
-
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: Dual Athlon on 2.2.19 ?
Alan, I have a dual athlon on the 760MP chipset. 2.2.20pre1 and 2 dont work. I got it to work partly after applying Johannes Erdfel's 760MP patch in io_apic.c. Even after applying the patch, there are messages like hdc: IRQ probe failed(0) hdd: IRQ probe failed(0) hde: IRQ probe failed(0) hdc: lost interrupt hdc: lost interrupt and then the machine hangs randomly. I an guessing the io_apic does not route the interrupts correctly. On Thu, May 24, 2001 at 01:02:11PM +0100, Alan Cox wrote: > > Is there a patch to make dual athlons work on 2.2.19 ? I know it work on > > 2.4.3-pre1 with AA's patch. > > 2.2.20pre1 and 2.4.current should both work -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | Reporter, n.: A writer who guesses his way of a GNU generation -o) | to the truth and dispels it with a tempest Kernel 2.4.1 /\\ | of words. -- Ambrose Bierce, "The Devil's on a i686_\\_v | Dictionary" | - 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/
Dual Athlon on 2.2.19
Is there a patch to make 2.2.19 kernel work on a dual athlon ? I tried both 2.2.20-pre2aa( with k7 smp ) and 2.2.20-pre2 and at boot after it detects the ide devices it hangs. I tried compiling in kdb to get a stack trace but the machine went into a hang. -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | Stockmayer's Theorem: If it looks easy, of a GNU generation -o) | it's tough. If it looks tough, it's damn Kernel 2.4.1 /\\ | well impossible. on a i686_\\_v | | - 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/
Dual Athlon on 2.2.19 ?
Hi all, Is there a patch to make dual athlons work on 2.2.19 ? I know it work on 2.4.3-pre1 with AA's patch. -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | Doing business with the government is like of a GNU generation -o) | fucking sheep. It's easy, but it's not Kernel 2.4.1 /\\ | very satisfying. on a i686_\\_v | | - 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: [Problem] 3c90x on 2.4.3-ac3
On Thu, Apr 05, 2001 at 11:40:36AM -0700, Grover, Andrew wrote:
> I'm confused. 3c59x.c has a little acpi WOL stuff, but that's it.
I tried "#ifdef 0"-ing the set_WOL function body( empty function ) in
3c59x.c and enabled acpi and built another kernel
and I still have the problem.
So its NOT a problem with the ACPI code in 3c59x.c per se.
I noticed that the following message was from net/core/netfilter.c( i
got this message on running dhclient )
ip_local_deliver: bad loopback skb: PRE_ROUTING LOCAL_IN
so i diabled netfilter also, and I still had the issue.
I assigned a static IP. ifconfig showed me the right info.
"route" however froze most of the times. I have 2 routes
172.16.12.0 * 255.255.252.0 U 0 00 eth0
default 172.16.12.1 0.0.0.0 UG0 00 eth0
It would freeze after the first one most often. If it did'nt, do a ping www.google.com,
which will drop all the packets, and try route again, and it would freeze after the
first route.
I strace'd route and noticed that I was waiting on "poll". I have attached the strace
info on route.
>
> What specifically is ACPI doing to break things? Are ACPI and the NIC
> sharing any resources?
I dont know about sharing resources. I have attached my dmesg.
The whole thing works like a charm under APM however.
I'm gonna try increasing vortex_debug level to see what happens.
would be glad to furnish more info...
-Prasanna Subash
[EMAIL PROTECTED]
>
> Regards -- Andy
>
> > -Original Message-
> > From: Prasanna P Subash [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, April 05, 2001 11:12 AM
> > To: Marcus Meissner
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: [Problem] 3c90x on 2.4.3-ac3
> > Importance: High
> >
> >
> > Thats right. ACPI was what made 3c90x not work :( With APM it
> > works perfectly.
> >
> > Thanks Marcus.
> >
> > On Thu, Apr 05, 2001 at 10:14:56AM +0200, Marcus Meissner wrote:
> > > In article <[EMAIL PROTECTED]> you wrote:
> > >
> > > > hi lkml,
> > > > I just built 2.4.3-ac3 with my old 2.4.2 .config and
> > somehow networking does not work.
> > > > dhclient eventually froze the machine.
> > >
> > > > here is what dhclient complains.
> > >
> > > > [root@psubash linux]# cat /tmp/error.txt
> > > > skb: pf=2 (unowned) dev=lo len=328
> > > > PROTO=17 0.0.0.0:68 255.255.255.255:67 L=328 S=0x10 I=0
> > F=0x T=16
> > > > DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 14
> > > > ip_local_deliver: bad loopback skb: PRE_ROUTING LOCAL_IN
> > > > skb: pf=2 (unowned) dev=lo len=328
> > > > PROTO=17 0.0.0.0:68 255.255.255.255:67 L=328 S=0x10 I=0
> > F=0x T=16
> > > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
> > > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
> > > > DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 12
> > > > ip_local_deliver: bad loopback skb: PRE_ROUTING LOCAL_IN
> > > > skb: pf=2 (unowned) dev=lo len=328
> > >
> > > > Here is my ver_linux info
> > >
> > > ...
> > > > CONFIG_ACPI=y
> > >
> > > The ACPI powermanagement for the 3c59x devices appears to
> > be a bit broken.
> > >
> > > Disable ACPI support. Recompile. Reboot. Watch problem
> > disappear hopefully.
> > >
> > > Ciao, Marcus
> > -
> > 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/
> >
execve("/sbin/route", ["route"], [/* 26 vars */]) = 0
brk(0) = 0x80527a8
open("/etc/ld.so.preload", O_RDONLY)= -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=33735, ...}) = 0
old_mmap(NULL, 33735, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40014000
close(3)= 0
open("/lib/libc.so.6", O_RDONLY)= 3
fstat(3, {st_mode=S_IFREG|0755, st_size=5173447, ...}) = 0
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\215\1"..., 4096) = 4096
old_mmap(NULL, 947548, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4001d000
mprotect(0x400fd000, 30044, PROT_NONE) = 0
old_mmap(0x400fd000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0xdf000) =
0x400fd0
Re: [Problem] 3c90x on 2.4.3-ac3
Thats right. ACPI was what made 3c90x not work :( With APM it works perfectly. Thanks Marcus. On Thu, Apr 05, 2001 at 10:14:56AM +0200, Marcus Meissner wrote: > In article <[EMAIL PROTECTED]> you wrote: > > > hi lkml, > > I just built 2.4.3-ac3 with my old 2.4.2 .config and somehow networking does >not work. > > dhclient eventually froze the machine. > > > here is what dhclient complains. > > > [root@psubash linux]# cat /tmp/error.txt > > skb: pf=2 (unowned) dev=lo len=328 > > PROTO=17 0.0.0.0:68 255.255.255.255:67 L=328 S=0x10 I=0 F=0x T=16 > > DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 14 > > ip_local_deliver: bad loopback skb: PRE_ROUTING LOCAL_IN > > skb: pf=2 (unowned) dev=lo len=328 > > PROTO=17 0.0.0.0:68 255.255.255.255:67 L=328 S=0x10 I=0 F=0x T=16 > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 > > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 > > DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 12 > > ip_local_deliver: bad loopback skb: PRE_ROUTING LOCAL_IN > > skb: pf=2 (unowned) dev=lo len=328 > > > Here is my ver_linux info > > ... > > CONFIG_ACPI=y > > The ACPI powermanagement for the 3c59x devices appears to be a bit broken. > > Disable ACPI support. Recompile. Reboot. Watch problem disappear hopefully. > > Ciao, Marcus - 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/
[Problem] 3c90x on 2.4.3-ac3
hi lkml, I just built 2.4.3-ac3 with my old 2.4.2 .config and somehow networking does not work. dhclient eventually froze the machine. here is what dhclient complains. [root@psubash linux]# cat /tmp/error.txt skb: pf=2 (unowned) dev=lo len=328 PROTO=17 0.0.0.0:68 255.255.255.255:67 L=328 S=0x10 I=0 F=0x T=16 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 14 ip_local_deliver: bad loopback skb: PRE_ROUTING LOCAL_IN skb: pf=2 (unowned) dev=lo len=328 PROTO=17 0.0.0.0:68 255.255.255.255:67 L=328 S=0x10 I=0 F=0x T=16 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 12 ip_local_deliver: bad loopback skb: PRE_ROUTING LOCAL_IN skb: pf=2 (unowned) dev=lo len=328 Here is my ver_linux info [root@psubash linux]# cat /tmp/ver_linux If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux psubash 2.4.3-ac3 #3 Wed Apr 4 16:49:40 PDT 2001 i686 unknown Gnu C 2.95.2.1 Gnu make 3.79.1 binutils 2.10.1 util-linux 2.11a mount 2.11a modutils 2.3.24 e2fsprogs 1.20-WIP pcmcia-cs 3.1.24 PPP2.3.11 Linux C Library2.1.3 Dynamic linker (ldd) 2.1.3 Linux C++ Library .. Procps 2.0.6 Net-tools 1.55 Console-tools 0.3.3 Sh-utils 2.0 Modules Loaded 3c59x Here is the output of lspci. [root@psubash linux]# lspci -v 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03) Flags: bus master, medium devsel, latency 64 Memory at f800 (32-bit, prefetchable) Capabilities: [a0] AGP version 1.0 00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 128 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 Memory behind bridge: f410-f4ff Prefetchable memory behind bridge: fc00-fdff 00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) Flags: bus master, medium devsel, latency 0 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) (prog-if 80 [Master]) Flags: bus master, medium devsel, latency 64 I/O ports at 10c0 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at 1080 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02) Flags: medium devsel 00:0e.0 Multimedia audio controller: Creative Labs SB Live! EMU1 (rev 07) Subsystem: Creative Labs CT4832 SBLive! Value Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at 10a0 Capabilities: [dc] Power Management version 1 00:0e.1 Input device controller: Creative Labs SB Live! (rev 07) Subsystem: Creative Labs Gameport Joystick Flags: bus master, medium devsel, latency 64 I/O ports at 10d0 Capabilities: [dc] Power Management version 1 00:0f.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30) Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100 Flags: bus master, medium devsel, latency 80, IRQ 5 I/O ports at 1000 Memory at f400 (32-bit, non-prefetchable) Capabilities: [dc] Power Management version 1 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) (prog-if 00 [VGA]) Subsystem: Matrox Graphics, Inc. Millennium G400 16Mb SDRAM Flags: bus master, medium devsel, latency 128, IRQ 11 Memory at fc00 (32-bit, prefetchable) Memory at f410 (32-bit, non-prefetchable) Memory at f480 (32-bit, non-prefetchable) Capabilities: [dc] Power Management version 2 Capabilities: [f0] AGP version 2.0 I have also attached my .config. thanks, Prasanna Subash [EMAIL PROTECTED] # # Automatically generated by make menuconfig: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCH
Verbose debug messages when accessing /dev/fd0
Hi lkml. when i do a fd = open( "/dev/fd0", O_WRONLY ); in 2.4.2 series kernels, i get these messages on the console: psubash kernel: floppy0: reschedule timeout lock fdc psubash kernel: floppy0: reschedule timeout redo fd request psubash kernel: floppy0: reschedule timeout redo fd request psubash kernel: floppy0: checking disk change line for drive 0 psubash kernel: floppy0: jiffies=34789296 psubash kernel: floppy0: disk change line=80 psubash kernel: floppy0: flags=2 psubash kernel: queue fd request dtime=2 psubash kernel: floppy0: reschedule timeout floppy start psubash kernel: floppy0: setting NEWCHANGE in floppy_start psubash kernel: floppy0: calling disk change from floppy_ready psubash kernel: floppy0: checking disk change line for drive 0 psubash kernel: floppy0: jiffies=34789296 psubash kernel: floppy0: disk change line=80 psubash kernel: floppy0: flags=6 psubash kernel: floppy0: calling disk change from seek psubash kernel: recalibrate floppy: dtime=2 psubash kernel: recal interrupt: dtime=2 psubash kernel: floppy0: calling disk change from floppy_ready psubash kernel: floppy0: checking disk change line for drive 0 psubash kernel: floppy0: jiffies=34789296 psubash kernel: floppy0: disk change line=80 psubash kernel: floppy0: flags=6 psubash kernel: floppy0: calling disk change from seek psubash kernel: seek command: dtime=2 psubash kernel: seek interrupt: dtime=3 psubash kernel: floppy0: clearing NEWCHANGE flag because of effective seek= psubash kernel: floppy0: jiffies=34789297 psubash kernel: floppy0: calling disk change from floppy_ready psubash kernel: floppy0: checking disk change line for drive 0 psubash kernel: floppy0: jiffies=34789299 psubash kernel: floppy0: disk change line=80 psubash kernel: floppy0: flags=2 psubash kernel: floppy0: calling disk change from seek psubash kernel: floppy0: checking disk change line for drive 0 psubash kernel: floppy0: jiffies=34789299 psubash kernel: floppy0: disk change line=80 psubash kernel: floppy0: flags=2 psubash kernel: floppy0: reschedule timeout request done 0 psubash kernel: end_request: I/O error, dev 02:00 (floppy), sector 0 psubash kernel: floppy0: calling disk change from set_dor psubash kernel: floppy0: checking disk change line for drive 0 psubash kernel: floppy0: jiffies=34789590 psubash kernel: floppy0: disk change line=80 psubash kernel: floppy0: flags=12 the last 4 lines showup after 2-3 seconds as I guess they are from the bottom halves. To prevent this from writing all over my text based app I have to flank the open() with syslog()'s. On a 2.2 kernel I get 2 debug lines instead (from end_request). Are the log levels correct for these debug messages ? Thanks, -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | Your heart is pure, and your mind clear, of a GNU generation -o) | and your soul devout. Kernel 2.4.2-ac3 /\\ | on a i686_\\_v | | - 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: Linux device driver writing
a treasure trove of info on linux would be /usr/src/linux/Documentation/kernel-docs.txt -Prasanna On Fri, Feb 23, 2001 at 10:01:40AM +, Rahul wrote: > Hi friends, > > I am new to this field of writing device drivers. I > have done my course in Unix/C and presently working > for a company in india in embedded systems. I am > looking forward to write some device drivers in > Linux/Unix/QNX can any one suggest me any good book > which i can refer for my guidance. > > thx for your constant support. > bye > rahul > > > Do You Yahoo!? > Get your free @yahoo.co.in address at http://mail.yahoo.co.in > - > 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/ -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | The idea of male and female are universal of a GNU generation -o) | constants. -- Kirk, "Metamorphosis", Kernel 2.4.0-test /\\ | stardate 3219.8 on a i686_\\_v | | PGP signature
Re: Documentation about programming sk_buffers
maybe this will be useful. http://www.linux-sna.org/events/papers/Bang%21inux-netstack-2001/skb%20definition.html On Wed, Feb 21, 2001 at 02:23:53PM -, Dragos, Radu wrote: > Does anyone know some good documentation about handling sk_buffers ? > > I'll need to work with them for some kind of filter. > > Thanks. > > - > 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/ -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | There are three things men can do with of a GNU generation -o) | women: love them, suffer for them, or turn Kernel 2.4.0-ac4 /\\ | them into literature. -- Stephen Stills on a i686_\\_v | | PGP signature
Re: PROBLEM: ext2 superblock issue on 2.4.1-ac20
On Thu, Feb 22, 2001 at 12:50:52AM +, Alan Cox wrote:
> > I just oldconfiged linux kernel with my 2.4.1 .config. When I boot the new
> > 2.4.1-ac20 kernel, I get a message saying that my ext2 superblock is corrup=
> > ted.
> > I get a message asking me to run e2fsck -b 8193 <...hdd dev..>
> > My 2.4.0-ac4 that I've been running for more than 2-3 weeks now has no prob=
> > lems
> > booting though.
> >
> > What am I doing wrong ? I would be glad to give more info.
>
> Sounds like a driver change broke the handling for your disks or re-ordered
> them.
>
> What hardware
e2fsprogs version : e2fsprogs-1.18-1
cat /proc/partitions
[psubash@psubash[ttypts/0]/tmp]$ cat /proc/partitions
[05:11pm/02-21-01]
major minor #blocks name
3 0 20044080 hda
3 12048256 hda1
3 23076447 hda2
3 3 128520 hda3
3 4 14787832 hda4
[psubash@psubash[ttypts/0]/proc]$ cat interrupts
[05:14pm/02-21-01]
CPU0
0: 448484 XT-PIC timer
1: 12572 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 9908 XT-PIC eth0
9: 0 XT-PIC usb-uhci
10: 222641 XT-PIC EMU10K1
12: 31073 XT-PIC PS/2 Mouse
14: 264281 XT-PIC ide0
15: 4 XT-PIC ide1
NMI: 0
ERR: 0
[psubash@psubash[ttypts/0]/proc]$ cat filesystems
[05:15pm/02-21-01]
nodev sockfs
nodev shm
nodev pipefs
nodev proc
ext2
iso9660
nodev autofs
nodev nfs
nodev devpts
[psubash@psubash[ttypts/0]/proc]$ cat mounts
[05:14pm/02-21-01]
/dev/root / ext2 rw 0 0
/proc /proc proc rw 0 0
/dev/hda4 /home ext2 rw 0 0
/dev/hda2 /usr ext2 rw 0 0
none /dev/pts devpts rw 0 0
[psubash@psubash[ttypts/0]/proc]$ cat devices
[05:15pm/02-21-01]
Character devices:
1 mem
2 pty
3 ttyp
4 ttyS
5 cua
7 vcs
10 misc
14 sound
128 ptm
136 pts
162 raw
180 usb
202 cpu/msr
203 cpu/cpuid
Block devices:
2 fd
3 ide0
22 ide1
cat /proc/cpuinfo
[psubash@psubash[ttypts/0]/tmp]$ cat /proc/cpuinfo
[05:11pm/02-21-01]
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping: 3
cpu MHz : 548.743
cache size : 512 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception : yes
cpuid level : 3
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36
mmx fxsr sse
bogomips: 1094.45
disk info
[psubash@psubash[ttypts/0]~]$ sudo hdparm -gi /dev/hda
[05:03pm/02-21-01]
/dev/hda:
geometry = 2495/255/63, sectors = 40088160, start = 0
Model=IBM-DPTA-372050, FwRev=P76OA30A, SerialNo=JMYJMHL1856
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=34
BuffType=3(DualPortCache), BuffSize=1961kB, MaxMultSect=16, MultSect=off
DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=2(fast)
CurCHS=16383/16/63, CurSects=16514064, LBA=yes
LBA CHS=1023/256/63 Remapping, LBA=yes, LBAsects=40088160
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 *mode2
lspci -vvxx output
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-
00: 86 80 90 71 06 01 10 22 03 00 00 06 00 40 00 00
10: 08 00 00 f8 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03)
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping-
SERR+ FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B+
00: 86 80 91 71 1f 01 20 02 03 00 04 06 00 80 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 40 f0 00 a0 22
20: 10 f4 f0 f4 00 fc f0 fd 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8c 00
00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
Re: PROBLEM: ext2 superblock issue on 2.4.1-ac20
oops. sorry for the panic. my fault. I was trying to boot a non-devfs'ed with devfs. thanks anyway. -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | Who is John Galt? of a GNU generation -o) | Kernel 2.4.1-ac20 /\\ | on a i686_\\_v | | On Thu, Feb 22, 2001 at 12:50:52AM +, Alan Cox wrote: > > I just oldconfiged linux kernel with my 2.4.1 .config. When I boot the new > > 2.4.1-ac20 kernel, I get a message saying that my ext2 superblock is corrup= > > ted. > > I get a message asking me to run e2fsck -b 8193 <...hdd dev..> > > My 2.4.0-ac4 that I've been running for more than 2-3 weeks now has no prob= > > lems > > booting though. > > > > What am I doing wrong ? I would be glad to give more info. > > Sounds like a driver change broke the handling for your disks or re-ordered > them. > > What hardware PGP signature
PROBLEM: ext2 superblock issue on 2.4.1-ac20
Hello lkml, I just oldconfiged linux kernel with my 2.4.1 .config. When I boot the new 2.4.1-ac20 kernel, I get a message saying that my ext2 superblock is corrupted. I get a message asking me to run e2fsck -b 8193 <...hdd dev..> My 2.4.0-ac4 that I've been running for more than 2-3 weeks now has no problems booting though. What am I doing wrong ? I would be glad to give more info. Here is the ver_linux output of 2.4.0-ac24 kernel. Every thing but the kernel must be same. -- Versions installed: (if some fields are empty or look -- unusual then possibly you have very old versions) Linux psubash.dev.us.tlan 2.4.0-ac4 #1 Tue Jan 9 12:01:27 PST 2001 i686 unknown Kernel modules 2.3.7 Gnu C 2.95.2 Gnu Make 3.78.1 Binutils 2.9.1.0.25 Linux C Library2.1.2 Dynamic linker ldd (GNU libc) 2.1.2 Linux C++ Library .. Procps 2.0.6 Mount 2.10f Net-tools 1.53 Kbd0.99 Sh-utils 2.0 Modules Loaded Here is the .config of the 2.4.1-ac20 kernel. # # Automatically generated by make menuconfig: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_PGE=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_TOSHIBA is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_SMP is not set # CONFIG_X86_UP_APIC is not set # CONFIG_X86_UP_IOAPIC is not set # # General setup # CONFIG_NET=y # CONFIG_VISWS is not set CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y # CONFIG_EISA is not set # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # CONFIG_PCMCIA=y CONFIG_CARDBUS=y # CONFIG_I82365 is not set # CONFIG_TCIC is not set CONFIG_SYSVIPC=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PM=y CONFIG_ACPI=y # CONFIG_APM is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play configuration # # CONFIG_PNP is not set # CONFIG_ISAPNP is not set # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_BLK_DEV_INITRD is not set # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID5 is not set # CONFIG_BLK_DEV_LVM is not set # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y CONFIG_NETFILTER=y CONFIG_NETFILTER_DEBUG=y CONFIG_FILTER=y CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set # CONFIG_INET_ECN is not set # CONFIG_SYN_COOKIES is not set # # IP: Netfilter Configuration # CONFIG_IP_NF_CONNTRACK=y CONFIG_IP_NF_FTP=y CONFIG_IP_NF_QUEUE=y CONFIG_IP_NF_IPTABLES=y CONFIG_IP_NF_MATCH_LIMIT=y CONFIG_IP_NF_MATCH_MAC=y CONFIG_IP_NF_MATCH_MARK=y CONFIG_IP_NF_MATCH_MULTIPORT=y CONFIG_IP_NF_MATCH_TOS=y # CONFIG_IP_NF_MATCH_TCPMSS is not set CONFIG_IP_NF_MATCH_STATE=y CONFIG_IP_NF_MATCH_UNCLEAN=y CONFIG_IP_NF_MATCH_OWNER=y CONFIG_IP_NF_FILTER=y CONFIG_IP_NF_TARGET_REJECT=y CONFIG_IP_NF_TARGET_MIRROR=y CONFIG_IP_NF_NAT=y CONFIG_IP_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=y CONFIG_IP_NF_TARGET_REDIRECT=y CONFIG_IP_NF_NAT_FTP=y CONFIG_IP_NF_MANGLE=y CONFIG_IP_NF_TARGET_TOS=y CONFIG_IP_NF_TARGET_MARK=y CONFIG_IP_NF_TARGET_LOG=y # CONFIG_IP_NF_TARGET_TCPMSS is not set # CONFIG_IPV6 is not set # CONFIG_
Re: problem in BOGOmips
the bogomips algorithm changed between kernels. Now it uses the tsc register. Your bogomips should typically be about 2*processor mhz. On Sat, Feb 10, 2001 at 02:35:05AM +0530, Ashish Gupta wrote: > Hi, > I want to use bogomips as the indicator of CPU capability for > different architectures. I have found following values from /proc/cpuinfo > for different CPUs. > > MHz bogomips version > 233 intel 233 2.2.9, 2.0.36 > 166 intel 331 2.2.9 > 450 AMD-K6 900 2.2.14 > 800 intel 1600 2.2.16 > > Why there is a exceptional behaviour of bogomips for 233 intel ? > If there is some patch or changes then please indicate so that i can use > it. > > Thanks in advance > Ashish Gupta > > > > > - > 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/ -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | I've got a COUSIN who works in the GARMENT of a GNU generation -o) | DISTRICT ... Kernel 2.4.0-ac4 /\\ | on a i686_\\_v | | PGP signature
[Patch]Re: Serious reproducible 2.4.x kernel hang
> #include
> #include
> #include
> #include
>
> int
> main(int argc, const char* argv[])
> {
> int retval;
> int sockets[2];
> char buf[1];
>
> retval = socketpair(PF_UNIX, SOCK_DGRAM, 0, sockets);
> if (retval != 0)
> {
> perror("socketpair");
> exit(1);
> }
> shutdown(sockets[0], SHUT_RDWR);
> read(sockets[0], buf, 1);
> }
I tried to debug this issue with the kdb on 2.4.1-pre7.
Here is the stack trace
mcount+0x1f9
wait_for_packet+0x13
skb_recv_datagram+0xbb
unix_dgram_recvmsg+0x53
sock_recvmsg+0x41
sock_read+0x8f
sys_read+0xa4
system_call+0x3c
I looked at the skb_recv_datagram code and noticed that wait_for_packet is not
returning an error, even while trying to read a closed socket.
Anyways here is a patch against 2.4.1 that will fix the issue.
Please feel free to flame me about the patch :)
thanks
--
Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC
Linux, the choice | Q: How do you keep a moron in suspense?
of a GNU generation -o) |
Kernel 2.2.16 /\\ |
on a i686_\\_v |
|
--- 2.4.1/net/core/datagram.c Fri Feb 2 01:00:10 2001
+++ linux/net/core/datagram.c Fri Feb 2 01:06:59 2001
@@ -74,15 +74,15 @@
if (error)
goto out;
- if (!skb_queue_empty(&sk->receive_queue))
- goto ready;
-
+ error = -ENOTCONN;
/* Socket shut down? */
if (sk->shutdown & RCV_SHUTDOWN)
goto out;
+ if (!skb_queue_empty(&sk->receive_queue))
+ goto ready;
+
/* Sequenced packets can come disconnected. If so we report the problem */
- error = -ENOTCONN;
if(connection_based(sk) && !(sk->state==TCP_ESTABLISHED || sk->state==TCP_LISTEN))
goto out;
PGP signature
Re: kernel ver 2.4.1 VFS problem
On Thu, Feb 01, 2001 at 04:22:03PM -0800, [EMAIL PROTECTED] wrote: > > > But the driver for my Hard disk is not there in the list, mine is FUJISTU disk > .I think Generic scsi driver will work > > Thanks > Jagan > > Your scsi driver could be compiled into as a module. "mkinitrd" to boot off a scsi root disk and update lilo info. Another quick solution would be to compile the scsi driver into the kernel. > - > 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/ -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | Can't open /usr/fortunes. Lid stuck on of a GNU generation -o) | cookie jar. Kernel 2.2.16 /\\ | on a i686_\\_v | | PGP signature
Re: bttv problems in 2.4.0/2.4.1
My bttv is at IRQ 3 and it still hangs the machine :( I dont even have acpi built in. btw I am testing with 2.4.1-pre9 -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | When the sun shineth, make hay. -- John of a GNU generation -o) | Heywood Kernel 2.4.0-ac4 /\\ | on a i686_\\_v | | On Wed, Jan 31, 2001 at 08:41:45AM +0100, Gerd Knorr wrote: > > > > I have sent all this info to Gerd Knorr but, as far as I know, he hasn't > > > > been able to track down the bug yet. I thought that by posting here, > > > > more eyes might at least make more reports of similar situations that > > > > might help track down the problem. > > > > > > Try flipping the card into a different slot. A lot of the cards > > > exceptionally do not like IRQ/DMA sharing, and a lot of the motherboards > > > share them between different slots. > > > > I will try this, but my card has (and does) worked with irq sharing for > > a long time. Its entry in /proc/interrupts: > > 9: 164935 165896 IO-APIC-level acpi, bttv > > What happens with acpi disabled? The power-down at boot could be caused by > the acpi power management maybe ... > > Gerd > > -- > Get back there in front of the computer NOW. Christmas can wait. > -- Linus "the Grinch" Torvalds, 24 Dec 2000 on linux-kernel > - > 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/ PGP signature
Re: bttv problems in 2.4.0/2.4.1
I have experienced similar issues with 2.4.0 and its test. I have a bttv848 chipset. I even tried compiling in kdb as a part of the kernel to see if it oopses, but no luck. I will try trying 0.7.47 today. this works on 2.2.16, last time i tried. -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | "You've got to think about tomorrow!" of a GNU generation -o) | "TOMORROW! I haven't even prepared for Kernel 2.4.0-ac4 /\\ | yesterday* yet!" on a i686_\\_v | | On Tue, Jan 30, 2001 at 07:53:11PM -0500, John Jasen wrote: > On Tue, 30 Jan 2001, Matthew Gabeler-Lee wrote: > > > These errors all occur in the same way (as near as I can tell) in > > kernels 2.4.0 and 2.4.1, using bttv drivers 0.7.50 (incl. w/ kernel), > > 0.7.53, and 0.7.55. > > > > I am currently using 2.4.0-test10 with bttv 0.7.47, which works fine. > > > > I have sent all this info to Gerd Knorr but, as far as I know, he hasn't > > been able to track down the bug yet. I thought that by posting here, > > more eyes might at least make more reports of similar situations that > > might help track down the problem. > > Try flipping the card into a different slot. A lot of the cards > exceptionally do not like IRQ/DMA sharing, and a lot of the motherboards > share them between different slots. > > -- > -- John E. Jasen ([EMAIL PROTECTED]) > -- In theory, theory and practise are the same. In practise, they aren't. > > - > 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/ PGP signature
Re: 2.2.18 and EMU10K1 problems...
remember seeing something about this on the list. Build it as a module, and not into the kernel and it should work. -- Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC Linux, the choice | Actually, what I'd like is a little toy of a GNU generation -o) | spaceship!! Kernel 2.4.0-test11 /\\ | on a i686_\\_v | | On Mon, Jan 08, 2001 at 01:56:29PM -0800, Taner Halicioglu wrote: > (please cc me if you reply - thanks :) > > I probably missed a message or note or something about this, but when I went > from 2.2.17 to 2.2.18, my sound card (SB Live!) stopped working. It seems > that in 2.2.18, it gets detected TWICE: > > > kernel: Linux version 2.2.18 > [...] > kernel: Creative EMU10K1 PCI Audio Driver, version 0.7, 20:05:23 Jan 7 2001 > kernel: emu10k1: EMU10K1 rev 5 model 0x21 found, IO at 0xb400-0xb41f, IRQ 10 > [... IDE, floppy, SCSI, eth0, partition check ...] > kernel: Creative EMU10K1 PCI Audio Driver, version 0.7, 20:05:23 Jan 7 2001 > > > This is what it normally does: > > > kernel: Linux version 2.2.17 > [...] > kernel: Creative EMU10K1 PCI Audio Driver, version 0.6, 20:25:53 Jan 7 2001 > kernel: emu10k1: EMU10K1 rev 5 model 0x21 found, IO at 0xb400-0xb41f, IRQ 10 > [...] > > > In the 2.2.18 case, /proc/interrupts doesn't show anything on int 10. > > I guess I should (and will) take this up with the EMU10k people, but I was > just wondering if anyone here has seen this problem before? I'm curious how > a broken driver would have made it into .18 like that ;-) ...unless I'm the > one that is broken :) > > Thanks, > > -Taner > - > 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/ PGP signature
Re: Pentium IV-summary
On Wed, Nov 08, 2000 at 03:14:22PM -0500, Frank Davis wrote: > 3. 2.4.x may support processor speeds up to 100GHz, as well as Pentium IV. Linus >will have a Pentium IV available soon, but can someone test the kernel with a Pentium >IV sooner? I've gotta Pentium IV 800MHz working on 2.4.0-test10. Just started testing it. It actually seems pretty stable. -- Prasanna P Subash [EMAIL PROTECTED] PGP signature
