Hi gorgeous
My name is Gavin. I want to get to know you better, if I may be so bold. I consider myself an honest man, and I am currently looking for a relationship in which I feel loved. Please tell me more about yourself, if you don't mind. Gavin.
Re: 2.4.6-pre9: Failed HPT370 detection
On Tuesday 03 July 2001 17:22, Gav wrote: > This kernel refuses to detect my HPT370 chipset. (where my root filesystem > is, on raid0). It just hangs where the detection usually takes place, so no > oops and no meaningfull bugreport :/ > > I have the same options set in my config as I always have, I've never had > any problem with this before. > > CONFIG_BLK_DEV_HPT366=y > CONFIG_MD_RAID0=y > > Anyone else seen this? Maybe its more VIA weirdness. > Actually its the drives ON the HPT chipset that arent being detected, not the chipset itself. usually: HPT370: IDE controller on PCI bus 00 dev 98 PCI: Found IRQ 11 for device 00:13.0 HPT370: chipset revision 3 HPT370: not 100%% native mode: will probe irqs later ide2: BM-DMA at 0xe000-0xe007, BIOS settings: hde:DMA, hdf:pio ide3: BM-DMA at 0xe008-0xe00f, BIOS settings: hdg:DMA, hdh:pio hda: SAMSUNG SV0322A, ATA DISK drive hdb: Hewlett-Packard CD-Writer Plus 9100b, ATAPI CD/DVD-ROM drive hde: IBM-DTLA-305040, ATA DISK drive hdg: IBM-DTLA-305040, ATA DISK drive in 2.4.6-pre9: HPT370: IDE controller on PCI bus 00 dev 98 PCI: Found IRQ 11 for device 00:13.0 HPT370: chipset revision 3 HPT370: not 100%% native mode: will probe irqs later ide2: BM-DMA at 0xe000-0xe007, BIOS settings: hde:DMA, hdf:pio ide3: BM-DMA at 0xe008-0xe00f, BIOS settings: hdg:DMA, hdh:pio hda: SAMSUNG SV0322A, ATA DISK drive hdb: Hewlett-Packard CD-Writer Plus 9100b, ATAPI CD/DVD-ROM drive Sorry about that. -- Gavin Baker - 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.6-pre9: Failed HPT370 detection
This kernel refuses to detect my HPT370 chipset. (where my root filesystem is, on raid0). It just hangs where the detection usually takes place, so no oops and no meaningfull bugreport :/ I have the same options set in my config as I always have, I've never had any problem with this before. CONFIG_BLK_DEV_HPT366=y CONFIG_MD_RAID0=y Anyone else seen this? Maybe its more VIA weirdness. -- Regards, Gavin Baker - 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.6-pre9: Failed HPT370 detection
This kernel refuses to detect my HPT370 chipset. (where my root filesystem is, on raid0). It just hangs where the detection usually takes place, so no oops and no meaningfull bugreport :/ I have the same options set in my config as I always have, I've never had any problem with this before. CONFIG_BLK_DEV_HPT366=y CONFIG_MD_RAID0=y Anyone else seen this? Maybe its more VIA weirdness. -- Regards, Gavin Baker - 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.6-pre9: Failed HPT370 detection
On Tuesday 03 July 2001 17:22, Gav wrote: This kernel refuses to detect my HPT370 chipset. (where my root filesystem is, on raid0). It just hangs where the detection usually takes place, so no oops and no meaningfull bugreport :/ I have the same options set in my config as I always have, I've never had any problem with this before. CONFIG_BLK_DEV_HPT366=y CONFIG_MD_RAID0=y Anyone else seen this? Maybe its more VIA weirdness. Actually its the drives ON the HPT chipset that arent being detected, not the chipset itself. usually: HPT370: IDE controller on PCI bus 00 dev 98 PCI: Found IRQ 11 for device 00:13.0 HPT370: chipset revision 3 HPT370: not 100%% native mode: will probe irqs later ide2: BM-DMA at 0xe000-0xe007, BIOS settings: hde:DMA, hdf:pio ide3: BM-DMA at 0xe008-0xe00f, BIOS settings: hdg:DMA, hdh:pio hda: SAMSUNG SV0322A, ATA DISK drive hdb: Hewlett-Packard CD-Writer Plus 9100b, ATAPI CD/DVD-ROM drive hde: IBM-DTLA-305040, ATA DISK drive hdg: IBM-DTLA-305040, ATA DISK drive etc in 2.4.6-pre9: HPT370: IDE controller on PCI bus 00 dev 98 PCI: Found IRQ 11 for device 00:13.0 HPT370: chipset revision 3 HPT370: not 100%% native mode: will probe irqs later ide2: BM-DMA at 0xe000-0xe007, BIOS settings: hde:DMA, hdf:pio ide3: BM-DMA at 0xe008-0xe00f, BIOS settings: hdg:DMA, hdh:pio hda: SAMSUNG SV0322A, ATA DISK drive hdb: Hewlett-Packard CD-Writer Plus 9100b, ATAPI CD/DVD-ROM drive Hang Sorry about that. -- Gavin Baker - 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/
ac17 "kernel BUG at slab.c:1244!"
The first occurrence of this I didn't even notice until i checked my logs. kernel BUG at slab.c:1244! invalid operand: CPU:0 EIP:0010:[] EFLAGS: 00010082 eax: 001b ebx: c187f788 ecx: 0001 edx: 2765 esi: d9a5f000 edi: d9a5f9aa ebp: 00012800 esp: d9fcbda4 ds: 0018 es: 0018 ss: 0018 Process kdeinit (pid: 993, stackpage=d9fcb000) Stack: c023d5c5 04dc d9a5f000 1000 d9a5f9aa 0246 ca0fe000 0282 d9fcbf5c 04c8 dfa43128 0007 d9fca000 0002 c01f47d7 087c 0007 d9dbef40 c01f3ed5 0840 0007 0810 Call Trace: [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 5d 8b 6b 10 58 81 e5 00 04 00 00 74 4b b8 a5 c2 0f 17 >>EIP; c0126850<= Trace; c01f47d7 Trace; c01f3ed5 Trace; c0223ab7 Trace; c01f1beb Trace; c01f1f23 Trace; c01f1faa Trace; c012e4e1 Trace; c0126d9c Trace; c013c988 <__pollwait+838/1040> Trace; c012e651 Trace; c0106ca7 <__up_wakeup+10fb/23f4> Code; c0126850 <_EIP>: Code; c0126850<= 0: 0f 0b ud2a <= Code; c0126852 2: 5dpop%ebp Code; c0126853 3: 8b 6b 10 mov0x10(%ebx),%ebp Code; c0126856 6: 58pop%eax Code; c0126857 7: 81 e5 00 04 00 00 and$0x400,%ebp Code; c012685d d: 74 4b je 5a <_EIP+0x5a> c01268aa Code; c012685f f: b8 a5 c2 0f 17mov$0x170fc2a5,%eax 1 warning and 1 error issued. Results may not be reliable. This second one was immediately after rebooting, and hard locked at getty. kernel BUG at slab.c:1244! invalid operand: CPU:0 EIP:0010:[] EFLAGS: 00010082 eax: 001b ebx: c187f788 ecx: 0001 edx: 2704 esi: dfa5c000 edi: dfa5c9aa ebp: 00012800 esp: da801e2c ds: 0018 es: 0018 ss: 0018 Process mingetty (pid: 811, stackpage=da801000) Stack: c023d5c5 04dc dfa5c000 1000 dfa5c9aa 0246 0007 0001 dfa5c000 c0230b4a c030a2e0 0006 0406 c01931dd 0c3c 0007 0406 c0193e48 c198df88 0005 dfa5d000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 5d 8b 6b 10 58 81 e5 00 04 00 00 74 4b b8 a5 c2 0f 17 >>EIP; c0126850<= Trace; c0230b4a <_mmx_memcpy+fa/260> Trace; c01931dd Trace; c0193e48 Trace; c0126d9c Trace; c019485e Trace; c012e932 Trace; c010fd26 Trace; c012eac6 Trace; c012db40 Trace; c012da69 Trace; c0137c5a Trace; c012dd43 Trace; c0106ca7 <__up_wakeup+10fb/23f4> Code; c0126850 <_EIP>: Code; c0126850<= 0: 0f 0b ud2a <= Code; c0126852 2: 5dpop%ebp Code; c0126853 3: 8b 6b 10 mov0x10(%ebx),%ebp Code; c0126856 6: 58pop%eax Code; c0126857 7: 81 e5 00 04 00 00 and$0x400,%ebp Code; c012685d d: 74 4b je 5a <_EIP+0x5a> c01268aa Code; c012685f f: b8 a5 c2 0f 17mov$0x170fc2a5,%eax 1 warning and 1 error issued. Results may not be reliable. This kernel was built with gcc 2.96 on an Athlon 1.33Ghz. Hope this is usefull, -- Regards, Gavin Baker - 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/
ac17 kernel BUG at slab.c:1244!
The first occurrence of this I didn't even notice until i checked my logs. kernel BUG at slab.c:1244! invalid operand: CPU:0 EIP:0010:[c0126850] EFLAGS: 00010082 eax: 001b ebx: c187f788 ecx: 0001 edx: 2765 esi: d9a5f000 edi: d9a5f9aa ebp: 00012800 esp: d9fcbda4 ds: 0018 es: 0018 ss: 0018 Process kdeinit (pid: 993, stackpage=d9fcb000) Stack: c023d5c5 04dc d9a5f000 1000 d9a5f9aa 0246 ca0fe000 0282 d9fcbf5c 04c8 dfa43128 0007 d9fca000 0002 c01f47d7 087c 0007 d9dbef40 c01f3ed5 0840 0007 0810 Call Trace: [c01f47d7] [c01f3ed5] [c0223ab7] [c01f1beb] [c01f1f23] [c01f1faa] [c012e4e1] [c0126d9c] [c013c988] [c012e651] [c0106ca7] Code: 0f 0b 5d 8b 6b 10 58 81 e5 00 04 00 00 74 4b b8 a5 c2 0f 17 EIP; c0126850 kmalloc+140/1e0 = Trace; c01f47d7 alloc_skb+d7/310 Trace; c01f3ed5 sock_alloc_send_skb+85/f0 Trace; c0223ab7 ip_rt_ioctl+3a67/5110 Trace; c01f1beb sock_sendmsg+6b/90 Trace; c01f1f23 sock_recvmsg+313/5b0 Trace; c01f1faa sock_recvmsg+39a/5b0 Trace; c012e4e1 default_llseek+501/9c0 Trace; c0126d9c kfree+1ec/290 Trace; c013c988 __pollwait+838/1040 Trace; c012e651 default_llseek+671/9c0 Trace; c0106ca7 __up_wakeup+10fb/23f4 Code; c0126850 kmalloc+140/1e0 _EIP: Code; c0126850 kmalloc+140/1e0 = 0: 0f 0b ud2a = Code; c0126852 kmalloc+142/1e0 2: 5dpop%ebp Code; c0126853 kmalloc+143/1e0 3: 8b 6b 10 mov0x10(%ebx),%ebp Code; c0126856 kmalloc+146/1e0 6: 58pop%eax Code; c0126857 kmalloc+147/1e0 7: 81 e5 00 04 00 00 and$0x400,%ebp Code; c012685d kmalloc+14d/1e0 d: 74 4b je 5a _EIP+0x5a c01268aa kmalloc+19a/1e0 Code; c012685f kmalloc+14f/1e0 f: b8 a5 c2 0f 17mov$0x170fc2a5,%eax 1 warning and 1 error issued. Results may not be reliable. This second one was immediately after rebooting, and hard locked at getty. kernel BUG at slab.c:1244! invalid operand: CPU:0 EIP:0010:[c0126850] EFLAGS: 00010082 eax: 001b ebx: c187f788 ecx: 0001 edx: 2704 esi: dfa5c000 edi: dfa5c9aa ebp: 00012800 esp: da801e2c ds: 0018 es: 0018 ss: 0018 Process mingetty (pid: 811, stackpage=da801000) Stack: c023d5c5 04dc dfa5c000 1000 dfa5c9aa 0246 0007 0001 dfa5c000 c0230b4a c030a2e0 0006 0406 c01931dd 0c3c 0007 0406 c0193e48 c198df88 0005 dfa5d000 Call Trace: [c0230b4a] [c01931dd] [c0193e48] [c0126d9c] [c019485e] [c012e932] [c010fd26] [c012eac6] [c012db40] [c012da69] [c0137c5a] [c012dd43] [c0106ca7] Code: 0f 0b 5d 8b 6b 10 58 81 e5 00 04 00 00 74 4b b8 a5 c2 0f 17 EIP; c0126850 kmalloc+140/1e0 = Trace; c0230b4a _mmx_memcpy+fa/260 Trace; c01931dd parport_pc_unregister_port+a5d/b90 Trace; c0193e48 tty_hung_up_p+588/1d30 Trace; c0126d9c kfree+1ec/290 Trace; c019485e tty_hung_up_p+f9e/1d30 Trace; c012e932 default_llseek+952/9c0 Trace; c010fd26 do_BUG+246/740 Trace; c012eac6 unregister_chrdev+96/a0 Trace; c012db40 dentry_open+c0/140 Trace; c012da69 filp_open+49/60 Trace; c0137c5a getname+5a/a0 Trace; c012dd43 get_unused_fd+183/220 Trace; c0106ca7 __up_wakeup+10fb/23f4 Code; c0126850 kmalloc+140/1e0 _EIP: Code; c0126850 kmalloc+140/1e0 = 0: 0f 0b ud2a = Code; c0126852 kmalloc+142/1e0 2: 5dpop%ebp Code; c0126853 kmalloc+143/1e0 3: 8b 6b 10 mov0x10(%ebx),%ebp Code; c0126856 kmalloc+146/1e0 6: 58pop%eax Code; c0126857 kmalloc+147/1e0 7: 81 e5 00 04 00 00 and$0x400,%ebp Code; c012685d kmalloc+14d/1e0 d: 74 4b je 5a _EIP+0x5a c01268aa kmalloc+19a/1e0 Code; c012685f kmalloc+14f/1e0 f: b8 a5 c2 0f 17mov$0x170fc2a5,%eax 1 warning and 1 error issued. Results may not be reliable. This kernel was built with gcc 2.96 on an Athlon 1.33Ghz. Hope this is usefull, -- Regards, Gavin Baker - 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 2.4.5-ac16 kernel panic
On Wednesday 20 June 2001 21:33, Gary White (Network Administrator) wrote: > 2.4.5-ac16 patch applied to clean 2.4.5 tree. 2.4.5-ac15 boots > with no problem. > > model name : AMD Athlon(tm) Processor > > Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 3). > > > PnP: PNP BIOS installation structure at 0xc00fc2b0 > PnP: PNP BIOS version 1.0, entry at f:c2e0, dseg at f > Linux NET4.0 for Linux 2.4 > Based upon Swansea University Computer Society NET3.039 > Initializing RT netlink socket > invalid operand: > CPU:0 > EIP:0010:[] > EFLAGS: 00010286 > eax: 007ec000 ebx: e080 ecx: 3f7ec000 edx: c0101000 > esi: 1ffec000 edi: 1ffec000 ebp: esp: dffe3f54 > ds: 0018 es: 0018 ss: 0018 > Process swapper (pid: 1, stackpage=dffe3000) > Stack: e080 1ffec000 1ffec000 0246 1ffec000 1ffec000 > 1ffec000 c0126384 0010 007ec000 c0101e08 1ffec000 3f7ec000 c0111521 > e080 1ffec000 1ffec000 1ffec000 c00f6ed8 0014 000f6ed0 > 3ffd7fff Call Trace: [] [] [] [] > [] [] [] > > Code: 0f 0b e9 40 01 00 00 8b 44 24 28 8b 54 24 2c 8b 4c 24 34 8b > <0>Kernel panic: Attempted to kill init > -- > Gary White Network Administrator > [EMAIL PROTECTED] Internet Pathway > Voice 601-776-3355Fax 601-776-2314 > Same here Gary. While starting kswapd "Kernel BUG at ioremap.c:73! Invalid operand:" etc AMD Athlon 00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- -- Regards, Gavin Baker - 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 2.4.5-ac16 kernel panic
On Wednesday 20 June 2001 21:33, Gary White (Network Administrator) wrote: 2.4.5-ac16 patch applied to clean 2.4.5 tree. 2.4.5-ac15 boots with no problem. model name : AMD Athlon(tm) Processor Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 3). PnP: PNP BIOS installation structure at 0xc00fc2b0 PnP: PNP BIOS version 1.0, entry at f:c2e0, dseg at f Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket invalid operand: CPU:0 EIP:0010:[c01112cf] EFLAGS: 00010286 eax: 007ec000 ebx: e080 ecx: 3f7ec000 edx: c0101000 esi: 1ffec000 edi: 1ffec000 ebp: esp: dffe3f54 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 1, stackpage=dffe3000) Stack: e080 1ffec000 1ffec000 0246 1ffec000 1ffec000 1ffec000 c0126384 0010 007ec000 c0101e08 1ffec000 3f7ec000 c0111521 e080 1ffec000 1ffec000 1ffec000 c00f6ed8 0014 000f6ed0 3ffd7fff Call Trace: [e080] [c0126384] [c0101e08] [c0111521] [e080] [c0105267] [c01056e8] Code: 0f 0b e9 40 01 00 00 8b 44 24 28 8b 54 24 2c 8b 4c 24 34 8b 0Kernel panic: Attempted to kill init -- Gary White Network Administrator [EMAIL PROTECTED] Internet Pathway Voice 601-776-3355Fax 601-776-2314 Same here Gary. While starting kswapd Kernel BUG at ioremap.c:73! Invalid operand: etc AMD Athlon 00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin ? routed to IRQ 11 Capabilities: [68] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 03) Subsystem: ABIT Computer Corp.: Unknown device a401 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 8 Region 0: Memory at d800 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 2.0 Status: RQ=31 SBA+ 64bit- FW+ Rate=x1,x2 Command: RQ=0 SBA- AGP- 64bit- FW- Rate=none Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- -- Regards, Gavin Baker - 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/
