Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
2.6.1-love1 - "May not destroy your computer"
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5  Next  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
MrNugget
Tux's lil' helper
Tux's lil' helper


Joined: 15 Nov 2003
Posts: 144
Location: Germany

PostPosted: Fri Jan 09, 2004 7:52 pm    Post subject: Reply with quote

Why is this version so damn buggy? I mean.. everything worked for me with 2.6.1-rc1, and this should be the _stable_ ... But i don't want to change back, too.. But thanks to wedge for the big support :) I hope my insmod problem and the other thinks will be fixed in another version of the kernel ;)
Back to top
View user's profile Send private message
Pink
Veteran
Veteran


Joined: 24 Jul 2003
Posts: 1062

PostPosted: Fri Jan 09, 2004 7:54 pm    Post subject: Reply with quote

Wedge: I think they are basically harmless, but a lot of people seem to get them and may be confusing them for other problems..

EG: Look at this post

I know it's not your responsiblity but if you do find something then we can spread the word that they are harmless or what to do to fix it...

I am still looking myself.
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Jan 09, 2004 7:58 pm    Post subject: Reply with quote

Searching through the LKML archives, there are lots of posts that mention this type of message. They seem to occur in lots of different situations for various different reasons. I remember getting them occasionally a couple of months ago, and they seemed to be related to the ATI fglrx driver. They just stopped appearing at some point, either a driver or kernel upgrade must've fixed something.

Anyway, I'm hoping to find a magical post that basically says "They're harmless. Ignore" :lol:
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Jan 09, 2004 8:02 pm    Post subject: Reply with quote

If anyone wants to get rid of all the bootsplash warnings, apply this patch. It doesn't seem to cause any problems for me.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Jan 09, 2004 8:09 pm    Post subject: Reply with quote

Sorry for the constant stream of posts here :)

I was looking at the messages PickledOnion posted, and went to try and find out where they were coming from. kmem_cache_alloc() is in mm/slab.c, and is just a wrapper around a function called __cache_alloc(). This function calls a pair of debugging functions before and after doing whatever the hell it does :D The second debug function has it's entire body inside an #ifdef DEBUG. The first debug function looks like this:
Code:
static inline void
cache_alloc_debugcheck_before(kmem_cache_t *cachep, int flags)
{     
   might_sleep_if(flags & __GFP_WAIT);
#if DEBUG
   kmem_flagcheck(cachep, flags);
#endif
}

That appears to be where the messages are being generated, and it just looks like the might_sleep should be inside the #ifdef. Can one of the people affected try making that change (mm/slab.c, line 1868) and see if it fixes things?
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
Redeeman
l33t
l33t


Joined: 25 Sep 2003
Posts: 957
Location: Denmark

PostPosted: Fri Jan 09, 2004 8:14 pm    Post subject: Reply with quote

PrakashKC wrote:
Ok, then you have not compiled it into the kernel or the kernel doesn't know about it, as your interrupt table just shows PIC usage.


now i compiled into my brand new 2.6.1-love1. and i still get the acpi errors, but acpi works, i compiled in apic too, dmesg:

Code:
Linux version 2.6.1-love1 (root@redeeman) (gcc version 3.3.1 20030916 (Gentoo Linux 3.3.1-r4, propolice)) #1 Fri Jan 9 20:22:40 CET 2004
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000025fec000 (usable)
 BIOS-e820: 0000000025fec000 - 0000000025fef000 (ACPI data)
 BIOS-e820: 0000000025fef000 - 0000000025fff000 (reserved)
 BIOS-e820: 0000000025fff000 - 0000000026000000 (ACPI NVS)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
607MB LOWMEM available.
On node 0 totalpages: 155628
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 151532 pages, LIFO batch:16
  HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 ASUS                                      ) @ 0x000f93d0
ACPI: RSDT (v001 ASUS   A7N266   0x42302e31 MSFT 0x31313031) @ 0x25fec000
ACPI: FADT (v001 ASUS   A7N266   0x42302e31 MSFT 0x31313031) @ 0x25fec100
ACPI: BOOT (v001 ASUS   A7N266   0x42302e31 MSFT 0x31313031) @ 0x25fec040
ACPI: MADT (v001 ASUS   A7N266   0x42302e31 MSFT 0x31313031) @ 0x25fec080
ACPI: DSDT (v001   ASUS A7N266   0x00001000 MSFT 0x0100000b) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:6 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Building zonelist for node : 0
Found and enabled local APIC!
current: c031ea60
current->thread_info: c038c000
Initializing CPU#0
Kernel command line: root=/dev/hda3 vga=794
PID hash table entries: 4096 (order 12: 32768 bytes)
Detected 1536.991 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Memory: 612548k/622512k available (1899k kernel code, 9176k reserved, 706k data, 152k init, 0k highmem)
zapping low mappings.
Calibrating delay loop... 3039.23 BogoMIPS
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000
CPU:     After vendor identify, caps: 0383fbff c1cbfbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU:     After all inits, caps: 0383fbff c1cbfbff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(TM) XP 1800+ stepping 02
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1536.0636 MHz.
..... host bus clock speed is 267.0241 MHz.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf1660, last bus=2
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20031203
ACPI: IRQ9 SCI: Edge set to Level Trigger.
spurious 8259A interrupt: IRQ7.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKU] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKI] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKJ] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKK] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKM] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT]
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
    ACPI-1120: *** Error: Method execution failed [\_SB_.SRS_] (Node e5fdac80), AE_AML_BUFFER_LIMIT
    ACPI-1120: *** Error: Method execution failed [\_SB_.LNKF._SRS] (Node c1623680), AE_AML_BUFFER_LIMIT
ACPI: Retrying with extended IRQ descriptor
ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 5
    ACPI-1120: *** Error: Method execution failed [\_SB_.SRS_] (Node e5fdac80), AE_AML_BUFFER_LIMIT
    ACPI-1120: *** Error: Method execution failed [\_SB_.LNKU._SRS] (Node c1623580), AE_AML_BUFFER_LIMIT
ACPI: Retrying with extended IRQ descriptor
ACPI: PCI Interrupt Link [LNKU] enabled at IRQ 10
    ACPI-1120: *** Error: Method execution failed [\_SB_.SRS_] (Node e5fdac80), AE_AML_BUFFER_LIMIT
    ACPI-1120: *** Error: Method execution failed [\_SB_.LNKB._SRS] (Node e5fdaa80), AE_AML_BUFFER_LIMIT
ACPI: Retrying with extended IRQ descriptor
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
    ACPI-1120: *** Error: Method execution failed [\_SB_.SRS_] (Node e5fdac80), AE_AML_BUFFER_LIMIT
    ACPI-1120: *** Error: Method execution failed [\_SB_.LNKD._SRS] (Node c1623880), AE_AML_BUFFER_LIMIT
ACPI: Retrying with extended IRQ descriptor
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
    ACPI-1120: *** Error: Method execution failed [\_SB_.SRS_] (Node e5fdac80), AE_AML_BUFFER_LIMIT
    ACPI-1120: *** Error: Method execution failed [\_SB_.LNKE._SRS] (Node c1623780), AE_AML_BUFFER_LIMIT
ACPI: Retrying with extended IRQ descriptor
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 11
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
vesafb: framebuffer at 0xe8000000, mapped to 0xe6809000, size 16384k
vesafb: mode is 1280x1024x16, linelength=2560, pages=1
vesafb: protected mode interface info at c000:bb20
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
Machine check exception polling timer started.
IA-32 Microcode Update Driver: v1.13 <tigran@veritas.com>
devfs: v1.22 (20021013) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
Initializing Cryptographic API
ACPI: Power Button (FF) [PWRF]
ACPI: Processor [CPU] (supports C1)
Console: switching to colour frame buffer device 160x64
pty: 512 Unix98 ptys configured
Real Time Clock Driver v1.12
Non-volatile memory driver v1.2
8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0xe780a000, 00:50:bf:77:9a:7a, IRQ 5
eth0:  Identified 8139 chip type 'RTL-8139C'
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE: IDE controller at PCI slot 0000:00:09.0
NFORCE: chipset revision 195
NFORCE: not 100% native mode: will probe irqs later
NFORCE: BIOS didn't set cable bits correctly. Enabling workaround.
NFORCE: BIOS didn't set cable bits correctly. Enabling workaround.
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE: 0000:00:09.0 (rev c3) UDMA100 controller
    ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 4D060H3, ATA DISK drive
hdb: LITE-ON LTR-32125W, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: Maxtor 6Y120L0, ATA DISK drive
hdd: Maxtor 6Y160P0, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 120069936 sectors (61475 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
 /dev/ide/host0/bus0/target0/lun0: p1 < p5 p6 p7 p8 > p2 p3
hdc: max request size: 128KiB
hdc: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
 /dev/ide/host0/bus1/target0/lun0: p1 p2 < p5 p6 p7 p8 >
hdd: max request size: 1024KiB
hdd: 320173056 sectors (163928 MB) w/7936KiB Cache, CHS=19929/255/63, UDMA(100)
 /dev/ide/host0/bus1/target1/lun0: p1 < p5 >
cdrom: : unknown mrw mode page
hdb: ATAPI 40X CD-ROM CD-R/RW drive, 1984kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Console: switching to colour frame buffer device 160x64
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
input: ImPS/2 Logitech Wheel Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
Advanced Linux Sound Architecture Driver Version 1.0.1 (Tue Dec 30 10:04:14 2003 UTC).
request_module: failed /sbin/modprobe -- snd-card-0. error = -16
ALSA device list:
  #0: C-Media PCI CMI8738-MC6 (model 55) at 0xc800, irq 5
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 152k freed
Adding 514040k swap on /dev/hda8.  Priority:-1 extents:1
EXT3 FS on hda3, internal journal
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
ohci_hcd: 2003 Oct 13 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: irq 10, pci mem e7850000
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
ohci_hcd 0000:00:03.0: OHCI Host Controller
PCI: Setting latency timer of device 0000:00:03.0 to 64
ohci_hcd 0000:00:03.0: irq 10, pci mem e7852000
ohci_hcd 0000:00:03.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected NVIDIA nForce chipset
agpgart: Maximum main memory to use for agp memory: 533M
agpgart: AGP aperture is 64M @ 0xf8000000
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
eth0: no IPv6 routers present


look, it finds apic, but that i dont care about right now, look at acpi errors, why??! :(

now /proc/interrupts
Code:
redeeman@redeeman: ~$ cat /proc/interrupts
           CPU0
  0:    2304988          XT-PIC  timer
  1:       9926          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  5:      34265          XT-PIC  CMI8738-MC6, eth0
  8:          2          XT-PIC  rtc
  9:          0          XT-PIC  acpi
 10:          0          XT-PIC  ohci_hcd, ohci_hcd
 11:     155271          XT-PIC  nvidia
 12:      66118          XT-PIC  i8042
 14:      18972          XT-PIC  ide0
 15:         18          XT-PIC  ide1
NMI:          0
LOC:    2304907
ERR:       2496

_________________
Sandberg Enterprises
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Jan 09, 2004 8:18 pm    Post subject: Reply with quote

Does adding "pci=noacpi" to your kernel command line help?
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
Pink
Veteran
Veteran


Joined: 24 Jul 2003
Posts: 1062

PostPosted: Fri Jan 09, 2004 8:26 pm    Post subject: Reply with quote

Wedge - just changed line 1868 in mm/slab.c and recompiling now.. don't know if it needs a recompile but it won't take too long, report back in a minute.

Edit: It's all gone horribly wrong...I will start again and see how things go - perhaps it is an nvidia thing but don't know if it was the patch to halt errors or the editing slab.c. I get a black screen at login now... I'll keep you informed.

Edit2: Thank goodness someone has said ignore them! I am trying to fix the mess I made and am now using generic nv drivers....
Lesson #1: Don't change more than one thing at a time when trying to find out where errors are :oops:
Lesson #2: Write down the changes you make or make some attempt to remember them :lol:


Last edited by Pink on Fri Jan 09, 2004 9:18 pm; edited 1 time in total
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Jan 09, 2004 8:37 pm    Post subject: Reply with quote

PickledOnion wrote:
Edit: It's all gone horribly wrong...I will start again and see how things go - perhaps it is an nvidia thing but don't know if it was the patch to halt errors or the editing slab.c. I get a black screen at login now... I'll keep you informed.

:( I'll try doing the change in slab.c myself, see if does the same thing.

Edit: No change, but that doesn't prove much since I wasn't getting the messages beforehand.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
PrakashP
Veteran
Veteran


Joined: 27 Oct 2003
Posts: 1246
Location: C.C.A.A., Germania

PostPosted: Fri Jan 09, 2004 9:08 pm    Post subject: Reply with quote

@Reedeman

I said *APIC* not ACPI. Two different things...

@Wedge_

Those warning with nvidia is fault of nvidia. The don't appear if you turn this spinlock checking off in kernel config. (Dunno exact option, it is right beside frame pointers.) I once asked on lkml and they basically said ignore/tell nvidia to fix it.

I think it is due to their drivers not being compiled for 2.6 kernel.
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Jan 09, 2004 9:12 pm    Post subject: Reply with quote

PrakaskKC wrote:
@Wedge_

Those warning with nvidia is fault of nvidia. The don't appear if you turn this spinlock checking off in kernel config. (Dunno exact option, it is right beside frame pointers.) I once asked on lkml and they basically said ignore/tell nvidia to fix it.

I think it is due to their drivers not being compiled for 2.6 kernel.

Right, so it's OK to ignore them?

Edit: I really have to start reading right to the end of sentences :P Thanks for the information.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
mile_slo
Tux's lil' helper
Tux's lil' helper


Joined: 29 Apr 2003
Posts: 91
Location: Ljubljana, Slovenia

PostPosted: Fri Jan 09, 2004 10:04 pm    Post subject: Reply with quote

I was using 2.6.0-test11 until now and this baby works even better :D
I love it
Back to top
View user's profile Send private message
MrNugget
Tux's lil' helper
Tux's lil' helper


Joined: 15 Nov 2003
Posts: 144
Location: Germany

PostPosted: Fri Jan 09, 2004 10:22 pm    Post subject: Reply with quote

Good to hear that someone loves the love-sources too ;)

What i wanted to ask.. are you guys using irc? I mean... i just don't want to post every second if i got a problem with the sources ;) I mean... i still got the problems and no solution in sight... but hey: life goes on! :D
Back to top
View user's profile Send private message
Wedge_
Advocate
Advocate


Joined: 08 Aug 2002
Posts: 3614
Location: Scotland

PostPosted: Fri Jan 09, 2004 10:27 pm    Post subject: Reply with quote

What problems are you still having? According to PrakashKC, you can ignore the messages starting with might_sleep, and the vt.c messages can be removed by applying the patch I posted.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ
Back to top
View user's profile Send private message
Dinini
Apprentice
Apprentice


Joined: 11 Jun 2003
Posts: 236

PostPosted: Fri Jan 09, 2004 11:11 pm    Post subject: Reply with quote

OneOfOne wrote:
for all people getting weird oops/sigfaults it is module-init-tool's fault, if you're using the 3.0_pre* downgrade to 0.9.15_pre14.
i found out this after recompiling the kernel 5 times....

peace

Well since I never was using 3.0 pre, I don't think that's it :) but rather this instead (least here)
Andrew Morton wrote:
My original thought is about Rusty.

The `check for truncated module' patch is clearly triggering when it should
not be. It then incorrectly returns "success" from load_module() even
though load_module() failed.

A `patch -R' of

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm1/broken-out/check-for-truncated-modules.patch

should fix it up.
Back to top
View user's profile Send private message
Redeeman
l33t
l33t


Joined: 25 Sep 2003
Posts: 957
Location: Denmark

PostPosted: Fri Jan 09, 2004 11:36 pm    Post subject: Reply with quote

MrNugget wrote:
Good to hear that someone loves the love-sources too ;)

What i wanted to ask.. are you guys using irc? I mean... i just don't want to post every second if i got a problem with the sources ;) I mean... i still got the problems and no solution in sight... but hey: life goes on! :D


i do :)
_________________
Sandberg Enterprises
Back to top
View user's profile Send private message
nepenthe
Guru
Guru


Joined: 14 Jul 2002
Posts: 317
Location: Sanford, ME

PostPosted: Sat Jan 10, 2004 12:19 am    Post subject: Reply with quote

Redeeman wrote:
MrNugget wrote:
Good to hear that someone loves the love-sources too ;)

What i wanted to ask.. are you guys using irc? I mean... i just don't want to post every second if i got a problem with the sources ;) I mean... i still got the problems and no solution in sight... but hey: life goes on! :D


i do :)


as do i =)
Back to top
View user's profile Send private message
Dinini
Apprentice
Apprentice


Joined: 11 Jun 2003
Posts: 236

PostPosted: Sat Jan 10, 2004 1:18 am    Post subject: Reply with quote

For what it's worth reversing ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm1/broken-out/check-for-truncated-modules.patch has allowed me to run 2.6.1-mm1 without any more problems.

Unfortunately I can't say if Love1 is stable. (Stupid me, it didn't compile cleanly after reversing Reiser4 so I went ahead and tried it with the Reiser4 sources installed but Reiser4 unselected, currently restoring two reiser 3.6 partition that fsck won't recover.).
Back to top
View user's profile Send private message
Ricky
Guru
Guru


Joined: 30 May 2003
Posts: 339

PostPosted: Sat Jan 10, 2004 1:24 am    Post subject: Reply with quote

MrNugget wrote:
Good to hear that someone loves the love-sources too ;)

What i wanted to ask.. are you guys using irc? I mean... i just don't want to post every second if i got a problem with the sources ;) I mean... i still got the problems and no solution in sight... but hey: life goes on! :D


but if you post, I get to read about it later. :wink:
Back to top
View user's profile Send private message
Master_Of_Disaster
l33t
l33t


Joined: 28 Feb 2003
Posts: 610
Location: 15.05072° East, 48.13747° North (aka Mauer), Austria

PostPosted: Sat Jan 10, 2004 4:30 am    Post subject: Reply with quote

Compilation fails on amd64:

Quote:
[...]
CC arch/x86_64/kernel/irq.o
arch/x86_64/kernel/irq.c: In function `do_IRQ':
arch/x86_64/kernel/irq.c:409: warning: implicit declaration of function `kgdb_process_breakpoint'
CC arch/x86_64/kernel/ptrace.o
CC arch/x86_64/kernel/i8259.o
CC arch/x86_64/kernel/ioport.o
CC arch/x86_64/kernel/ldt.o
CC arch/x86_64/kernel/setup.o
CC arch/x86_64/kernel/time.o
CC arch/x86_64/kernel/sys_x86_64.o
arch/x86_64/kernel/sys_x86_64.c: In function `sys_mmap':
arch/x86_64/kernel/sys_x86_64.c:59: warning: passing arg 1 of `do_mmap_pgoff' from incompatible pointer type
arch/x86_64/kernel/sys_x86_64.c:59: warning: passing arg 2 of `do_mmap_pgoff' makes pointer from integer without a cast
arch/x86_64/kernel/sys_x86_64.c:59: error: too few arguments to function `do_mmap_pgoff'
make[1]: *** [arch/x86_64/kernel/sys_x86_64.o] Error 1
make: *** [arch/x86_64/kernel] Error 2

_________________
post tenebras lux, post fenestras tux
Registered Linux User Nr. 312509
Adopt an unanswered post today!
Back to top
View user's profile Send private message
Dinini
Apprentice
Apprentice


Joined: 11 Jun 2003
Posts: 236

PostPosted: Sat Jan 10, 2004 4:57 am    Post subject: Reply with quote

amd64 takes a specialized patchset. :( Andi Keen mantains the patchset and I believe you can find it (or at least a link to it) over at http://www.x86-64.org/
Back to top
View user's profile Send private message
Master_Of_Disaster
l33t
l33t


Joined: 28 Feb 2003
Posts: 610
Location: 15.05072° East, 48.13747° North (aka Mauer), Austria

PostPosted: Sat Jan 10, 2004 5:04 am    Post subject: Reply with quote

2.6.1-rc2-mm1 worked without adding any patches, 2.6.1-mm1 fails when linking. AFAIK x86_64 patches are included in Andrew's patchset
_________________
post tenebras lux, post fenestras tux
Registered Linux User Nr. 312509
Adopt an unanswered post today!
Back to top
View user's profile Send private message
Dinini
Apprentice
Apprentice


Joined: 11 Jun 2003
Posts: 236

PostPosted: Sat Jan 10, 2004 5:22 am    Post subject: Reply with quote

Andrew syncs to Andi's patchset periodically (I'd thought I'd seen a note that it was broken last patch but don't have time to track it). Last bug report I saw asked folks to test against Andi's patches (since that it the "official" x86_64 tree). I haven't seen any bug reports on linux-kernel for 2.6.1-mm1 referencing x86_64. Have you tried against the base mm1 patch or just the combined love1 sources?

This seems to be the only x86_64 change I've seen for 2.6.1-mm1 vs 2.6.1-rc2-mm1:

+kgdb-x86_64-support.patch
kgdb for x86_64

Think I'm going to bed rather than look at anything else in the forums :) This is the second time I've not written all that I meant to say and as a result am giving misleading information. Good luck and sorry for the confusion.
Back to top
View user's profile Send private message
glaskows
Tux's lil' helper
Tux's lil' helper


Joined: 05 Jan 2004
Posts: 77
Location: Chile

PostPosted: Sat Jan 10, 2004 7:02 am    Post subject: Question. Reply with quote

Is the 2.6.1-love1-r1.patch.bz2 already incorporated into love-sources-2.6.1-r1 or is a patch for it?
If the second... how do i use the patch?
Back to top
View user's profile Send private message
MrNugget
Tux's lil' helper
Tux's lil' helper


Joined: 15 Nov 2003
Posts: 144
Location: Germany

PostPosted: Sat Jan 10, 2004 10:22 am    Post subject: Reply with quote

Wedge_ wrote:
What problems are you still having? According to PrakashKC, you can ignore the messages starting with might_sleep, and the vt.c messages can be removed by applying the patch I posted.


I cannot "insmod" my webcam modul: computer freezes. With 2.6.1-rc2 i could.

I'm getting some "Calculating Dependencies failed!" Errors while booting, it's about depscan.sh and net.eth0 ... It says i need to run that script, i ran and the same again.

That makes me somehow... mad... I mean, the error.. i could ignore it. But what about the insmod? I need that modul. Really. And i don't want to have reboot my computer manually if i do an insmod.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3, 4, 5  Next
Page 4 of 5

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum