2.6.1-love1 - "May not destroy your computer"

MrNugget · Posted: Fri Jan 09, 2004 7:52 pm Post subject:

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

Pink · Veteran Joined: 24 Jul 2003 Posts: 1062

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.

Wedge_ · Posted: Fri Jan 09, 2004 7:58 pm Post subject:

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

Wedge_ · Posted: Fri Jan 09, 2004 8:02 pm Post subject:

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

Wedge_ · Posted: Fri Jan 09, 2004 8:09 pm Post subject:

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

The second debug function has it's entire body inside an #ifdef DEBUG. The first debug function looks like this:

Redeeman · l33t Joined: 25 Sep 2003 Posts: 958 Location: Portugal

Wedge_ · Posted: Fri Jan 09, 2004 8:18 pm Post subject:

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

Pink · Veteran Joined: 24 Jul 2003 Posts: 1062

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:

Wedge_ · Posted: Fri Jan 09, 2004 8:37 pm Post subject:

PrakashP · Posted: Fri Jan 09, 2004 9:08 pm Post subject:

@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.

Wedge_ · Posted: Fri Jan 09, 2004 9:12 pm Post subject:

mile_slo · Posted: Fri Jan 09, 2004 10:04 pm Post subject:

I was using 2.6.0-test11 until now and this baby works even better

I love it

MrNugget · Posted: Fri Jan 09, 2004 10:22 pm Post subject:

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!

Wedge_ · Posted: Fri Jan 09, 2004 10:27 pm Post subject:

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

Dinini · Apprentice Joined: 11 Jun 2003 Posts: 236

Redeeman · l33t Joined: 25 Sep 2003 Posts: 958 Location: Portugal

nepenthe · Guru Joined: 14 Jul 2002 Posts: 317 Location: Sanford, ME

Dinini · Apprentice Joined: 11 Jun 2003 Posts: 236

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.).

Ricky · Guru Joined: 30 May 2003 Posts: 341

Master_Of_Disaster · Posted: Sat Jan 10, 2004 4:30 am Post subject:

Compilation fails on amd64:

Dinini · Apprentice Joined: 11 Jun 2003 Posts: 236

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/

Master_Of_Disaster · Posted: Sat Jan 10, 2004 5:04 am Post subject:

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!

Dinini · Apprentice Joined: 11 Jun 2003 Posts: 236

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.

glaskows · Posted: Sat Jan 10, 2004 7:02 am Post subject: Question.

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?

MrNugget · Posted: Sat Jan 10, 2004 10:22 am Post subject: