Re: Linux 2.6.12-rc3: various swsusp problems
On 4/22/05, Stefan Seyfried <[EMAIL PROTECTED]> wrote:
> --- linux/kernel/power/swsusp.c~2005-04-22 17:07:56.0 +0200
> +++ linux/kernel/power/swsusp.c 2005-04-22 17:09:22.0 +0200
> @@ -1239,7 +1239,7 @@ static int check_sig(void)
> */
>error = bio_write_page(0, _header);
>} else {
> - printk(KERN_ERR "swsusp: Suspend partition has wrong
> signature?\n");
> + printk(KERN_ERR "swsusp: Suspend partition is no suspend
> image.\n");
Hrm, I don't think it is a good message... What about "Suspend
partition has no suspend image" or, better yet, "Suspend partition
does not contain valid suspend image"?
--
Dmitry
-
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.6.12-rc3:microtek.c:338: error: for each function it appears in.
Thank you. On Fri, 2005-04-22 at 08:20 +0200, Oliver Neukum wrote: > Am Freitag, > 22. April 2005 03:20 schrieb Bob Gill: > > OK. I downloaded, patched and started the build. Basically everything > > stops when I get a "microtek.c:338: error: `FAILURE' undeclared" error > > Known problem. Fix in the pipeline. > > Regards > Oliver -- Bob Gill <[EMAIL PROTECTED]> - 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.6.12-rc3: various swsusp problems
Pavel Machek wrote:
>> 1. Is it necessary to print the following message during regular boot?
>>swsusp: Suspend partition has wrong signature?
> Hmm, feel free to provide a patch. (I need something to try git on :-).
Attached (sorry, Thunderbird...). One may argue over KERN_ERR, but i
don't mind.
--
Stefan Seyfried, QA / R Team Mobile Devices, SUSE LINUX Nürnberg.
"Any ideas, John?"
"Well, surrounding them's out."
--- linux/kernel/power/swsusp.c~2005-04-22 17:07:56.0 +0200
+++ linux/kernel/power/swsusp.c 2005-04-22 17:09:22.0 +0200
@@ -1239,7 +1239,7 @@ static int check_sig(void)
*/
error = bio_write_page(0, _header);
} else {
- printk(KERN_ERR "swsusp: Suspend partition has wrong
signature?\n");
+ printk(KERN_ERR "swsusp: Suspend partition is no suspend
image.\n");
return -EINVAL;
}
if (!error)
Re: Linux 2.6.12-rc3
Hi! > > Nice, so I now have my own -git tree, with two changes in it... > > > > Is there way to say "git diff -r origin:" but dump it patch-by-patch > > with some usable headers? > > > > [Looking at git export] > > Either Linus' demo git-export (NOT the same as git export!), or git > patch. In the latest tree, it was extended to accept a range of two > commits to process too. > > Note that the range semantics is rather peculiar at the least. ;-) Nice, it seems to work. Unfortunately first merge will make it practically unusable :-(. git diff -r origin: will only list differences between my tree and Linus'. git patch origin: will list my patches, plus any merges I done... Is there any reasonable way to get only "my" changes? When I do not have to resolve anything during merge, it should be usable... but that is starting to look ugly. Pavel -- Boycott Kodak -- for their patent abuse against Java. - 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.6.12-rc3:microtek.c:338: error: for each function it appears in.
Thank you. On Fri, 2005-04-22 at 08:20 +0200, Oliver Neukum wrote: Am Freitag, 22. April 2005 03:20 schrieb Bob Gill: OK. I downloaded, patched and started the build. Basically everything stops when I get a microtek.c:338: error: `FAILURE' undeclared error Known problem. Fix in the pipeline. Regards Oliver -- Bob Gill [EMAIL PROTECTED] - 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.6.12-rc3: various swsusp problems
On 4/22/05, Stefan Seyfried [EMAIL PROTECTED] wrote:
--- linux/kernel/power/swsusp.c~2005-04-22 17:07:56.0 +0200
+++ linux/kernel/power/swsusp.c 2005-04-22 17:09:22.0 +0200
@@ -1239,7 +1239,7 @@ static int check_sig(void)
*/
error = bio_write_page(0, swsusp_header);
} else {
- printk(KERN_ERR swsusp: Suspend partition has wrong
signature?\n);
+ printk(KERN_ERR swsusp: Suspend partition is no suspend
image.\n);
Hrm, I don't think it is a good message... What about Suspend
partition has no suspend image or, better yet, Suspend partition
does not contain valid suspend image?
--
Dmitry
-
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.6.12-rc3
Hi! Nice, so I now have my own -git tree, with two changes in it... Is there way to say git diff -r origin: but dump it patch-by-patch with some usable headers? [Looking at git export] Either Linus' demo git-export (NOT the same as git export!), or git patch. In the latest tree, it was extended to accept a range of two commits to process too. Note that the range semantics is rather peculiar at the least. ;-) Nice, it seems to work. Unfortunately first merge will make it practically unusable :-(. git diff -r origin: will only list differences between my tree and Linus'. git patch origin: will list my patches, plus any merges I done... Is there any reasonable way to get only my changes? When I do not have to resolve anything during merge, it should be usable... but that is starting to look ugly. Pavel -- Boycott Kodak -- for their patent abuse against Java. - 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.6.12-rc3: various swsusp problems
Pavel Machek wrote:
1. Is it necessary to print the following message during regular boot?
swsusp: Suspend partition has wrong signature?
Hmm, feel free to provide a patch. (I need something to try git on :-).
Attached (sorry, Thunderbird...). One may argue over KERN_ERR, but i
don't mind.
--
Stefan Seyfried, QA / RD Team Mobile Devices, SUSE LINUX Nürnberg.
Any ideas, John?
Well, surrounding them's out.
--- linux/kernel/power/swsusp.c~2005-04-22 17:07:56.0 +0200
+++ linux/kernel/power/swsusp.c 2005-04-22 17:09:22.0 +0200
@@ -1239,7 +1239,7 @@ static int check_sig(void)
*/
error = bio_write_page(0, swsusp_header);
} else {
- printk(KERN_ERR swsusp: Suspend partition has wrong
signature?\n);
+ printk(KERN_ERR swsusp: Suspend partition is no suspend
image.\n);
return -EINVAL;
}
if (!error)
Re: Linux 2.6.12-rc3
Al Viro wrote: > thread_info, part 1: Patches look fine. Some of the helper stuff could be moved to asm-generic, but that can still be done later. The headers really need some serious cleanup in this area, the dependencies are damned fragile. I8 still have a completely untested patch to convert the thread flags to bitmasks, but I hadn't much time for m68k hacking lately... bye, Roman - 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.6.12-rc3
On Sat, 23 Apr 2005, Pavel Machek wrote: > > Unfortunately first merge will make it practically unusable :-(. No, quite the reverse. If I merge from you, and you use my commit ID as the "base" point, it will work again. But yes, if you actually send the result as _patches_ to me, then the commit objects I create will be totally separate from the commit objects you had in your tree, and "git-export" will continue to export your old stale entries since they won't show up as already being in my tree. The point being, that there is a big difference between a proper merge (with history etc merged) and just sending me the patches in your tree. Linus - 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.6.12-rc3
On Thursday 21 April 2005 02:59, you wrote: Hello, [build.log] ... drivers/usb/storage/debug.c: In function `usb_stor_show_sense': drivers/usb/storage/debug.c:166: warning: implicit declaration of function `scsi_sense_key_string' drivers/usb/storage/debug.c:166: warning: assignment makes pointer from integer without a cast drivers/usb/storage/debug.c:167: warning: implicit declaration of function `scsi_extd_sense_format' drivers/usb/storage/debug.c:167: warning: assignment makes pointer from integer without a cast ... Hmm, actually I've already sent the trivial patch below for this to Andrew a few weeks ago and he included it in mm but somehow it is not there.. --- drivers/usb/storage/debug.c.orig2005-04-05 14:24:21.0 +0200 +++ drivers/usb/storage/debug.c 2005-04-05 14:24:35.0 +0200 @@ -47,7 +47,7 @@ #include #include #include - +#include #include "debug.h" #include "scsi.h" Regards, Boris. - 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.6.12-rc3
Followup to: <[EMAIL PROTECTED]> By author:Pavel Machek <[EMAIL PROTECTED]> In newsgroup: linux.dev.kernel > > You should put this into .git/remotes > > linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > Make that rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git Right now they're the same thing, but it's not guaranteed to stay that way. -hpa - 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.6.12-rc3:microtek.c:338: error: for each function it appears in.
Am Freitag, 22. April 2005 03:20 schrieb Bob Gill: > OK. I downloaded, patched and started the build. Basically everything > stops when I get a "microtek.c:338: error: `FAILURE' undeclared" error Known problem. Fix in the pipeline. Regards Oliver - 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.6.12-rc3:microtek.c:338: error: for each function it appears in.
Am Freitag, 22. April 2005 03:20 schrieb Bob Gill: OK. I downloaded, patched and started the build. Basically everything stops when I get a microtek.c:338: error: `FAILURE' undeclared error Known problem. Fix in the pipeline. Regards Oliver - 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.6.12-rc3
Followup to: [EMAIL PROTECTED] By author:Pavel Machek [EMAIL PROTECTED] In newsgroup: linux.dev.kernel You should put this into .git/remotes linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git Make that rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git Right now they're the same thing, but it's not guaranteed to stay that way. -hpa - 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.6.12-rc3
On Thursday 21 April 2005 02:59, you wrote: snip Hello, [build.log] ... drivers/usb/storage/debug.c: In function `usb_stor_show_sense': drivers/usb/storage/debug.c:166: warning: implicit declaration of function `scsi_sense_key_string' drivers/usb/storage/debug.c:166: warning: assignment makes pointer from integer without a cast drivers/usb/storage/debug.c:167: warning: implicit declaration of function `scsi_extd_sense_format' drivers/usb/storage/debug.c:167: warning: assignment makes pointer from integer without a cast ... Hmm, actually I've already sent the trivial patch below for this to Andrew a few weeks ago and he included it in mm but somehow it is not there.. --- drivers/usb/storage/debug.c.orig2005-04-05 14:24:21.0 +0200 +++ drivers/usb/storage/debug.c 2005-04-05 14:24:35.0 +0200 @@ -47,7 +47,7 @@ #include linux/cdrom.h #include scsi/scsi.h #include scsi/scsi_cmnd.h - +#include scsi/scsi_dbg.h #include debug.h #include scsi.h Regards, Boris. - 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.6.12-rc3
On Sat, 23 Apr 2005, Pavel Machek wrote: Unfortunately first merge will make it practically unusable :-(. No, quite the reverse. If I merge from you, and you use my commit ID as the base point, it will work again. But yes, if you actually send the result as _patches_ to me, then the commit objects I create will be totally separate from the commit objects you had in your tree, and git-export will continue to export your old stale entries since they won't show up as already being in my tree. The point being, that there is a big difference between a proper merge (with history etc merged) and just sending me the patches in your tree. Linus - 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.6.12-rc3
Al Viro wrote: thread_info, part 1: Patches look fine. Some of the helper stuff could be moved to asm-generic, but that can still be done later. The headers really need some serious cleanup in this area, the dependencies are damned fragile. I8 still have a completely untested patch to convert the thread flags to bitmasks, but I hadn't much time for m68k hacking lately... bye, Roman - 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.6.12-rc3:microtek.c:338: error: for each function it appears in.
OK. I downloaded, patched and started the build. Basically everything stops when I get a "microtek.c:338: error: `FAILURE' undeclared" error (the build keeps trying, but no modules get created). I suspect others may have the same problem, but feel free to e-mail me for more information (and you will have to as I am not on the list). ...ok, also I have tried adding #define MTS_SCSI_ERR_MASK ~0x3fu >#define FAILURE ~0x3fu on line 55 of microtek.h ...basically a copycat of the previous error line...(but I suspect the kernel maintainer would be a better person to define FAILURE somewhere...) And...it does boot and I can taint.the.kernel.with.nvidia.video TIA, Bob -- Bob Gill <[EMAIL PROTECTED]> - 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.6.12-rc3
On Thu, Apr 21, 2005 at 03:33:42PM +0200, Andreas Steinmetz wrote: > Compile error on x86_64: > > CC [M] drivers/usb/image/microtek.o > drivers/usb/image/microtek.c: In function `mts_scsi_abort': > drivers/usb/image/microtek.c:338: error: `FAILURE' undeclared (first use > in this function) Patch to fix this was posted on lkml and is in my queue to send to Linus in a bit. thanks, greg k-h - 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.6.12-rc3
Dear diary, on Fri, Apr 22, 2005 at 01:22:01AM CEST, I got a letter where Pavel Machek <[EMAIL PROTECTED]> told me that... > Hi! Hi, > > > > You should put this into .git/remotes > > > > > > > > linus > > > > rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > > > > (git addremote is preferred for that :-) > > Nice, so I now have my own -git tree, with two changes in it... > > Is there way to say "git diff -r origin:" but dump it patch-by-patch > with some usable headers? > > [Looking at git export] Either Linus' demo git-export (NOT the same as git export!), or git patch. In the latest tree, it was extended to accept a range of two commits to process too. Note that the range semantics is rather peculiar at the least. ;-) -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor - 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.6.12-rc3
On Fri, 22 Apr 2005, Pavel Machek wrote: > > Is there way to say "git diff -r origin:" but dump it patch-by-patch > with some usable headers? In my git version there is a command called "git-export" for exactly this. I don't know if Pasky included that in his trees, but if not, you can just get my git tree (which should be compatible with Pasky's scripts, but mine just has the "core" stuff). Using "git-export" you can export your whole git tree if you want to, but more commonly you'd say git-export $(cat .git/HEAD) $(cat .git/BASE) where you'd have saved the previous head that you exported in the BASE thing (or, if you pull my tree, and want to export your changes back to me, you'd initialize BASE to the original HEAD in my tree). The output format of "git-export" is not the prettiest in the world, but I've never actually _used_ that command, I just wrote it as a demonstration thing. Linus - 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.6.12-rc3
Hi! > > > You should put this into .git/remotes > > > > > > linus > > > rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > > (git addremote is preferred for that :-) Nice, so I now have my own -git tree, with two changes in it... Is there way to say "git diff -r origin:" but dump it patch-by-patch with some usable headers? [Looking at git export] Pavel Index: Documentation/git.txt === --- /dev/null (tree:9120479b4c721855b378db8907e1259f2e583f2b) +++ 007d34e2ed3d5fc54cbb4c16880145ade93affef/Documentation/git.txt (mode:100644 sha1:939d378ddaac5390c879520c139e66d9649ec4c4) @@ -0,0 +1,19 @@ + Kernel hacker's guide to git + + 2005 Pavel Machek <[EMAIL PROTECTED]> + +You can get git at http://pasky.or.cz/~pasky/dev/git/ . Compile it, +and place it somewhere in $PATH. Then you can get kernel by running + +git init rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git + +... Run git log to get idea of what happened in tree you are +tracking. Do git pull linus to pickup latest changes from Linus. You +can do git diff to see what changes you done in your local tree. git +cancel will kill any such changes. + +You can commit changes by doing git commit... If you want to get diff +of your changes against mainline, do + +git diff -r origin: + -- Boycott Kodak -- for their patent abuse against Java. - 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.6.12-rc3
Dear diary, on Thu, Apr 21, 2005 at 11:38:11PM CEST, I got a letter where Pavel Machek <[EMAIL PROTECTED]> told me that... > Hi! > > It seems that someone should write "Kernel hacker's guide to > git"... Documentation/git.txt seems like good place. I guess I'll do > it. I've also started writing some tutorial-like guide to Cogito on my notebook, but I have time for that only during lectures. :^) > > I'm not yet sure if we should have some Cogito interface for doing this > > and what its semantics should be. > > What is Cogito, BTW? New name for git-pasky. Everyone will surely rejoice as the usage will change significantly. But better let's clean it up now. (For more details, check git@ archives for git-pasky-0.6 announcement.) > > > I see quite a lot of problems with fsck-tree. Is that normal? > > > (I ran out of disk space few times during different operations...) > > > > Actually, in case your tree is older than about two days, I hope you did > > the convert-cache magic or fetched a fresh tree? > > No, I did not anything like that. I guess it is rm -rf time, then... That's the root of all your problems then. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor - 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.6.12-rc3
Hi! It seems that someone should write "Kernel hacker's guide to git"... Documentation/git.txt seems like good place. I guess I'll do it. > > just plain vanilla" without rm -rf? > > git cancel will give you "plain last commit". If you need plain vanilla, > the "hard way" now is to just do > > commit-id >.git/HEAD > > but your current HEAD will be lost forever. Or do > > git fork vanilla ~/vanilla linus > > and you will have the vanilla tree tracking linus in ~/vanilla. Ok, thanks. > I'm not yet sure if we should have some Cogito interface for doing this > and what its semantics should be. What is Cogito, BTW? > > I see quite a lot of problems with fsck-tree. Is that normal? > > (I ran out of disk space few times during different operations...) > > Actually, in case your tree is older than about two days, I hope you did > the convert-cache magic or fetched a fresh tree? No, I did not anything like that. I guess it is rm -rf time, then... Pavel -- Boycott Kodak -- for their patent abuse against Java. - 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.6.12-rc3: various swsusp problems
Pavel Machek wrote: > Hi! > Are they new or were they in -rc2, too? Some further backtracking: The nic problem is already present in 2.6.12-rc1. The pcmcia hang problem is not present in 2.6.12-rc1. -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] - 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.6.12-rc3: various swsusp problems
Pavel Machek wrote: > Hi! > > >>there's some problems with swsusp in 2.6.12-rc3 (x86_64): > > > Are they new or were they in -rc2, too? > Fixed the rc2/rc3 IDE Oops myself today that prevented me to test rc2 earlier. It seems the IDE maintainer is currently not very responsive and I didn't have sufficient spare time to look into this before today :-( Yes, all problems are already in rc2. > >>1. Is it necessary to print the following message during regular boot? >> swsusp: Suspend partition has wrong signature? >> It is a bit annoying and I believe it will confuse some swsusp >> users. > > > Hmm, feel free to provide a patch. (I need something to try git on :-). I'll have a look over the weekend. > > >>2. PCMCIA related hangs during swsusp. >> swsusp hangs after freeing memory when either cardmgr is running >> or pcmcia cards are *physically* inserted. It is insufficient >> to do a 'cardctl eject' the cards must be removed, too, for >> swsusp not to hang. I do suspect some problem with the >> 'pccardd' kernel threads. > > > Did it work with any older kernel? Which driver is it? yenta? 2.6.11.2 works ok and, yes, its yenta. Some excerpt from lspci: 00:0b.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller 00:0b.1 CardBus bridge: Texas Instruments PCI7420 CardBus Controller > > >>3. Sometimes during the search for the suspend hang reason the system >> went during suspend into a lightshow of: >> eth0: Too much work at interrupt! >> and some line that ends in: >> release_console_sem+0x13d/0x1c0) >> The start of the line is not readable as it just flickers by in >> the eth0 message limbo. NIC is a built in RTL-8169 Gigabit Ethernet >> (rev 10). Oh, no chance for a serial console capture as there's no >> built in serial device in this laptop. > > > How repeatable is that? Will NIC work okay if you rmmod/insmod its driver? > Pavel Happens with a probability of about 10% to 20%. I did comment out the 'Too much work...' printk in r8169.c which results in the following effect: no more message from the network driver (expected), no other printk related to release_console_sem or anything else unusal, but write to disk in the case the problem seems to happen is suddenly quite slow and suspend eventually succeeds. As the nic driver is built into the kernel insmod/rmmod currently won't do:-) Nevertheless there doesn't seem to be any strange behaviour after resume though I didn't really try to use the nic then. There is, however, definitely no such problem with the nic in 2.6.11.2. -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] - 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.6.12-rc3
Dear diary, on Thu, Apr 21, 2005 at 09:00:09PM CEST, I got a letter where Pavel Machek <[EMAIL PROTECTED]> told me that... > Hi! Hi, > > > Well, not sure. > > > > > > I did > > > > > > git track linus > > > git cancel > > > > > > but Makefile still contains -rc2. (Is "git cancel" right way to check > > > out the tree?) > > > > No. git cancel does what it says - cancels your local changes to the > > working tree. git track will only set that next time you pull from > > linus, the changes will be automatically merged. (Note that this will > > change with the big UI change.) > > Is there way to say "forget those changes in my repository, I want > just plain vanilla" without rm -rf? git cancel will give you "plain last commit". If you need plain vanilla, the "hard way" now is to just do commit-id >.git/HEAD but your current HEAD will be lost forever. Or do git fork vanilla ~/vanilla linus and you will have the vanilla tree tracking linus in ~/vanilla. I'm not yet sure if we should have some Cogito interface for doing this and what its semantics should be. > I see quite a lot of problems with fsck-tree. Is that normal? > (I ran out of disk space few times during different operations...) Actually, in case your tree is older than about two days, I hope you did the convert-cache magic or fetched a fresh tree? -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor - 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.6.12-rc3
On 4/21/05, Linus Torvalds <[EMAIL PROTECTED]> wrote: > > > Changes since 2.6.12-rc2: > > Benjamin Herrenschmidt: ... > [PATCH] ppc32: Fix cpufreq problems this depends on two patches in -mm: add-suspend-method-to-cpufreq-core.patch Add suspend method to cpufreq core add-suspend-method-to-cpufreq-core-warning-fix.patch add-suspend-method-to-cpufreq-core-warning-fix without those patches defconfig is broken on ppc32 regards, Benoit - 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.6.12-rc3
Hi! > > > You should put this into .git/remotes > > > > > > linus > > > rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > > (git addremote is preferred for that :-) Oops :-). > > Well, not sure. > > > > I did > > > > git track linus > > git cancel > > > > but Makefile still contains -rc2. (Is "git cancel" right way to check > > out the tree?) > > No. git cancel does what it says - cancels your local changes to the > working tree. git track will only set that next time you pull from > linus, the changes will be automatically merged. (Note that this will > change with the big UI change.) Is there way to say "forget those changes in my repository, I want just plain vanilla" without rm -rf? I see quite a lot of problems with fsck-tree. Is that normal? (I ran out of disk space few times during different operations...) -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms - 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.6.12-rc3
On Thu, Apr 21, 2005 at 06:57:23PM +0100, Al Viro wrote: > thread_info part 3: heads. headers, even... - 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.6.12-rc3
m68k thread_info - part 4
The rest:
a) added embedded thread_info [m68k processor.h]
b) added missing symbols in asm-offsets.c
c) task_thread_info() and freinds in asm-m68k/thread_info.h
d) made m68k thread_info.h included by m68k processor.h, not the
other way round.
At that point thread_info mess is resolved - m68k builds and the rest of
the stuff to merge consists of normal driver patches.
IMO that's the least intrusive way to merge that sucker...
Comments?
diff -urN RC12-rc3-includes/arch/m68k/kernel/asm-offsets.c
RC12-rc3-m68k/arch/m68k/kernel/asm-offsets.c
--- RC12-rc3-includes/arch/m68k/kernel/asm-offsets.cThu Feb 26 02:23:09 2004
+++ RC12-rc3-m68k/arch/m68k/kernel/asm-offsets.cWed Apr 20 22:51:18 2005
@@ -31,6 +31,7 @@
DEFINE(TASK_SIGPENDING, offsetof(struct task_struct,
thread.work.sigpending));
DEFINE(TASK_NOTIFY_RESUME, offsetof(struct task_struct,
thread.work.notify_resume));
DEFINE(TASK_THREAD, offsetof(struct task_struct, thread));
+ DEFINE(TASK_INFO, offsetof(struct task_struct, thread.info));
DEFINE(TASK_MM, offsetof(struct task_struct, mm));
DEFINE(TASK_ACTIVE_MM, offsetof(struct task_struct, active_mm));
@@ -44,6 +45,10 @@
DEFINE(THREAD_FPREG, offsetof(struct thread_struct, fp));
DEFINE(THREAD_FPCNTL, offsetof(struct thread_struct, fpcntl));
DEFINE(THREAD_FPSTATE, offsetof(struct thread_struct, fpstate));
+
+ /* offsets into the thread_info struct */
+ DEFINE(TINFO_PREEMPT, offsetof(struct thread_info, preempt_count));
+ DEFINE(HARDIRQ_SHIFT, HARDIRQ_SHIFT);
/* offsets into the pt_regs */
DEFINE(PT_D0, offsetof(struct pt_regs, d0));
diff -urN RC12-rc3-includes/include/asm-m68k/processor.h
RC12-rc3-m68k/include/asm-m68k/processor.h
--- RC12-rc3-includes/include/asm-m68k/processor.h Wed Apr 20 21:25:51 2005
+++ RC12-rc3-m68k/include/asm-m68k/processor.h Wed Apr 20 22:51:19 2005
@@ -14,6 +14,7 @@
#define current_text_addr() ({ __label__ _l; _l: &&_l;})
#include
+#include
#include
#include
#include
@@ -79,6 +80,7 @@
unsigned long fpcntl[3]; /* fp control regs */
unsigned char fpstate[FPSTATESIZE]; /* floating point state */
struct task_work work;
+ struct thread_info info;
};
#define INIT_THREAD { \
diff -urN RC12-rc3-includes/include/asm-m68k/thread_info.h
RC12-rc3-m68k/include/asm-m68k/thread_info.h
--- RC12-rc3-includes/include/asm-m68k/thread_info.hWed Apr 20 21:25:51 2005
+++ RC12-rc3-m68k/include/asm-m68k/thread_info.hWed Apr 20 22:51:19 2005
@@ -2,7 +2,6 @@
#define _ASM_M68K_THREAD_INFO_H
#include
-#include
#include
struct thread_info {
@@ -36,10 +35,11 @@
#endif /* PAGE_SHIFT == 13 */
//#define init_thread_info (init_task.thread.info)
-#define init_stack (init_thread_union.stack)
-
-#define current_thread_info() (current->thread_info)
+#define init_thread_info (init_thread_union.thread_info)
+#define init_stack (init_thread_union.stack)
+#define task_thread_info(tsk) (&(tsk)->thread.info)
+#define current_thread_info() task_thread_info(current)
#define __HAVE_THREAD_FUNCTIONS
@@ -51,6 +51,10 @@
#define TIF_MEMDIE 5
extern int thread_flag_fixme(void);
+
+#define setup_thread_info(p, ti) do (ti)->task = p; while(0)
+
+#define end_of_stack(p) ((unsigned long *)(p)->thread_info + 1)
/*
* flag set/clear/test wrappers
-
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.6.12-rc3
thread_info part 2:
encapsulates the rest of arch-dependent operations with thread_info access.
Two new helpers - setup_thread_info() and end_of_stack(). For normal
case the former consists of copying thread_info of parent to new thread_info
and the latter returns pointer immediately past the end of thread_info.
Again, normal platforms are obviously safe. Note that end_of_stack() is
need since unlike the default case, m68k has only a single pointer in
stack - not the entire thread_info. So DEBUG_STACK_USAGE needs to be
a bit different there.
diff -urN RC12-rc3-task_thread_info/include/linux/sched.h
RC12-rc3-other_helpers/include/linux/sched.h
--- RC12-rc3-task_thread_info/include/linux/sched.h Wed Apr 20 22:51:13 2005
+++ RC12-rc3-other_helpers/include/linux/sched.hWed Apr 20 22:51:15 2005
@@ -1104,6 +1104,16 @@
#define task_thread_info(task) (task)->thread_info
+static inline void setup_thread_info(struct task_struct *p, struct thread_info
*ti)
+{
+ *ti = *p->thread_info;
+}
+
+static inline unsigned long *end_of_stack(struct task_struct *p)
+{
+ return (unsigned long *)(p->thread_info + 1);
+}
+
/* set thread flags in other task's structures
* - see asm/thread_info.h for TIF_ flags available
*/
diff -urN RC12-rc3-task_thread_info/kernel/fork.c
RC12-rc3-other_helpers/kernel/fork.c
--- RC12-rc3-task_thread_info/kernel/fork.c Wed Apr 20 22:51:13 2005
+++ RC12-rc3-other_helpers/kernel/fork.cWed Apr 20 22:51:15 2005
@@ -169,8 +169,8 @@
return NULL;
}
- *ti = *orig->thread_info;
*tsk = *orig;
+ setup_thread_info(tsk, ti);
tsk->thread_info = ti;
ti->task = tsk;
diff -urN RC12-rc3-task_thread_info/kernel/sched.c
RC12-rc3-other_helpers/kernel/sched.c
--- RC12-rc3-task_thread_info/kernel/sched.cWed Apr 20 22:51:13 2005
+++ RC12-rc3-other_helpers/kernel/sched.c Wed Apr 20 22:51:15 2005
@@ -3945,10 +3945,10 @@
#endif
#ifdef CONFIG_DEBUG_STACK_USAGE
{
- unsigned long * n = (unsigned long *) (p->thread_info+1);
+ unsigned long * n = end_of_stack(p);
while (!*n)
n++;
- free = (unsigned long) n - (unsigned long)(p->thread_info+1);
+ free = (unsigned long) n - (unsigned long) end_of_stack(p);
}
#endif
printk("%5lu %5d %6d ", free, p->pid, p->parent->pid);
-
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.6.12-rc3
thread_info, part 1:
new helper - task_thread_info(task). On platforms that have thread_info
allocated separately (i.e. in default case) it simply returns task->thread_info.
m68k wants (and for good reasons) to embed its thread_info into task_struct.
So it will (in later patch) have task_thread_info() of its own.
For now we just add a macro for generic case and convert existing users in
core kernel to its user. Obviously safe - all normal architectures get
the same preprocessor output they used to get.
diff -urN RC12-rc3-delta23/include/linux/sched.h
RC12-rc3-task_thread_info/include/linux/sched.h
--- RC12-rc3-delta23/include/linux/sched.h Wed Apr 20 21:25:54 2005
+++ RC12-rc3-task_thread_info/include/linux/sched.h Wed Apr 20 22:51:13 2005
@@ -1102,32 +1102,34 @@
spin_unlock(>alloc_lock);
}
+#define task_thread_info(task) (task)->thread_info
+
/* set thread flags in other task's structures
* - see asm/thread_info.h for TIF_ flags available
*/
static inline void set_tsk_thread_flag(struct task_struct *tsk, int flag)
{
- set_ti_thread_flag(tsk->thread_info,flag);
+ set_ti_thread_flag(task_thread_info(tsk), flag);
}
static inline void clear_tsk_thread_flag(struct task_struct *tsk, int flag)
{
- clear_ti_thread_flag(tsk->thread_info,flag);
+ clear_ti_thread_flag(task_thread_info(tsk), flag);
}
static inline int test_and_set_tsk_thread_flag(struct task_struct *tsk, int
flag)
{
- return test_and_set_ti_thread_flag(tsk->thread_info,flag);
+ return test_and_set_ti_thread_flag(task_thread_info(tsk), flag);
}
static inline int test_and_clear_tsk_thread_flag(struct task_struct *tsk, int
flag)
{
- return test_and_clear_ti_thread_flag(tsk->thread_info,flag);
+ return test_and_clear_ti_thread_flag(task_thread_info(tsk), flag);
}
static inline int test_tsk_thread_flag(struct task_struct *tsk, int flag)
{
- return test_ti_thread_flag(tsk->thread_info,flag);
+ return test_ti_thread_flag(task_thread_info(tsk), flag);
}
static inline void set_tsk_need_resched(struct task_struct *tsk)
@@ -1198,12 +1200,12 @@
static inline unsigned int task_cpu(const struct task_struct *p)
{
- return p->thread_info->cpu;
+ return task_thread_info(p)->cpu;
}
static inline void set_task_cpu(struct task_struct *p, unsigned int cpu)
{
- p->thread_info->cpu = cpu;
+ task_thread_info(p)->cpu = cpu;
}
#else
diff -urN RC12-rc3-delta23/kernel/exit.c RC12-rc3-task_thread_info/kernel/exit.c
--- RC12-rc3-delta23/kernel/exit.c Wed Apr 20 21:25:54 2005
+++ RC12-rc3-task_thread_info/kernel/exit.c Wed Apr 20 22:51:13 2005
@@ -827,7 +827,7 @@
if (group_dead && tsk->signal->leader)
disassociate_ctty(1);
- module_put(tsk->thread_info->exec_domain->module);
+ module_put(task_thread_info(tsk)->exec_domain->module);
if (tsk->binfmt)
module_put(tsk->binfmt->module);
diff -urN RC12-rc3-delta23/kernel/fork.c RC12-rc3-task_thread_info/kernel/fork.c
--- RC12-rc3-delta23/kernel/fork.c Wed Apr 20 21:25:54 2005
+++ RC12-rc3-task_thread_info/kernel/fork.c Wed Apr 20 22:51:13 2005
@@ -893,7 +893,7 @@
if (nr_threads >= max_threads)
goto bad_fork_cleanup_count;
- if (!try_module_get(p->thread_info->exec_domain->module))
+ if (!try_module_get(task_thread_info(p)->exec_domain->module))
goto bad_fork_cleanup_count;
if (p->binfmt && !try_module_get(p->binfmt->module))
@@ -1138,7 +1138,7 @@
if (p->binfmt)
module_put(p->binfmt->module);
bad_fork_cleanup_put_domain:
- module_put(p->thread_info->exec_domain->module);
+ module_put(task_thread_info(p)->exec_domain->module);
bad_fork_cleanup_count:
put_group_info(p->group_info);
atomic_dec(>user->processes);
diff -urN RC12-rc3-delta23/kernel/sched.c
RC12-rc3-task_thread_info/kernel/sched.c
--- RC12-rc3-delta23/kernel/sched.c Wed Apr 20 21:25:55 2005
+++ RC12-rc3-task_thread_info/kernel/sched.cWed Apr 20 22:51:13 2005
@@ -1151,7 +1151,7 @@
* but it also can be p->switch_lock.) So we compensate with a count
* of 1. Also, we want to start with kernel preemption disabled.
*/
- p->thread_info->preempt_count = 1;
+ task_thread_info(p)->preempt_count = 1;
#endif
/*
* Share the timeslice between parent and child, thus the
@@ -4018,9 +4018,9 @@
/* Set the preempt count _outside_ the spinlocks! */
#if defined(CONFIG_PREEMPT) && !defined(CONFIG_PREEMPT_BKL)
- idle->thread_info->preempt_count = (idle->lock_depth >= 0);
+ task_thread_info(idle)->preempt_count = (idle->lock_depth >= 0);
#else
- idle->thread_info->preempt_count = 0;
+ task_thread_info(idle)->preempt_count = 0;
#endif
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Re: Linux 2.6.12-rc3: various swsusp problems
Hi Pavel, there's some problems with swsusp in 2.6.12-rc3 (x86_64): 1. Is it necessary to print the following message during regular boot? swsusp: Suspend partition has wrong signature? It is a bit annoying and I believe it will confuse some swsusp users. 2. PCMCIA related hangs during swsusp. swsusp hangs after freeing memory when either cardmgr is running or pcmcia cards are *physically* inserted. It is insufficient to do a 'cardctl eject' the cards must be removed, too, for swsusp not to hang. I do suspect some problem with the 'pccardd' kernel threads. 3. Sometimes during the search for the suspend hang reason the system went during suspend into a lightshow of: eth0: Too much work at interrupt! and some line that ends in: release_console_sem+0x13d/0x1c0) The start of the line is not readable as it just flickers by in the eth0 message limbo. NIC is a built in RTL-8169 Gigabit Ethernet (rev 10). Oh, no chance for a serial console capture as there's no built in serial device in this laptop. -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] - 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.6.12-rc3
Dear diary, on Thu, Apr 21, 2005 at 02:03:27PM CEST, I got a letter where Pavel Machek <[EMAIL PROTECTED]> told me that... > > You should put this into .git/remotes > > > > linus > > rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (git addremote is preferred for that :-) > > Then > > > > RSYNC_FLAGS=-zavP git pull linus -v is passed to rsync by default. I'll gladly add other reasonable rsync flags (I don't call printing each considered file reasonable; fsck or wget-like progressbar would be ideal). > Well, not sure. > > I did > > git track linus > git cancel > > but Makefile still contains -rc2. (Is "git cancel" right way to check > out the tree?) No. git cancel does what it says - cancels your local changes to the working tree. git track will only set that next time you pull from linus, the changes will be automatically merged. (Note that this will change with the big UI change.) Either do git track linus git pull or git merge linus to get Linus' changes if you didn't pull yet. > and git diff -r linus: still contains some changes. [I did some > experimental pull of scsi changes long time ago, is it that problem?] If you don't have your HEAD on Linus' branch, it will do a tree merge instead of fast-forward; that is, it will not just move your HEAD on to match Linus' HEAD, but it will make a regular merge and then ask you to do a merge commit. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor - 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.6.12-rc3
On Thu, Apr 21, 2005 at 11:10:15AM +0200, Geert Uytterhoeven wrote: > On Thu, 21 Apr 2005, Jan Dittmer wrote: > > Linus Torvalds wrote: > > > Geert Uytterhoeven: > > > [PATCH] M68k: Update defconfigs for 2.6.11 > > > [PATCH] M68k: Update defconfigs for 2.6.12-rc2 > > > > Why do I still get this error when trying to cross-compile for m68k? > > Because to build m68k kernels, you (still :-( have to use the Linux/m68k CVS > repository, cfr. http://linux-m68k-cvs.ubb.ca/. > > BTW, my patch queue is at > http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-2.6.x-merging/. > The main offender is POSTPONED/156-thread_info.diff. I think I have a sane splitup of that stuff. If you have time to review - yell - 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.6.12-rc3
On Thu, 21 Apr 2005 14:19:10 +0200 Ralf Hildebrandt wrote: | > It's available both as a patch (against 2.6.11) and as a tar-ball, and | Where IS the tarball? Not on www.kernel.org, that's for sure. in http://www.kernel.org/pub/linux/kernel/v2.6/testing/ --- ~Randy - 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.6.12-rc3: Oops on IDE flash disk eject
The following patch fixes the Oops though I don't know if this is the
correct solution.
--- linux-2.6.12-rc3/drivers/ide/ide.c.ast
+++ linux-2.6.12-rc3/drivers/ide/ide.c
@@ -2082,7 +2082,8 @@
static int ide_drive_remove(struct device * dev)
{
ide_drive_t * drive = container_of(dev,ide_drive_t,gendev);
- DRIVER(drive)->cleanup(drive);
+ if(DRIVER(drive))
+ DRIVER(drive)->cleanup(drive);
return 0;
}
--
Andreas Steinmetz SPAMmers use [EMAIL PROTECTED]
-
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.6.12-rc3: Oops on IDE flash disk eject
As already reported to lkml and IDE maintainer for 2.6.12-rc2: Oops on 'cardctl eject' of an IDE flash disk (Pretec ATA Flash 16MB). 2.6.11.2 works fine. System: Linux (none) 2.6.12-rc3-gringo #1 Thu Apr 21 15:45:08 CEST 2005 x86_64 unknown unknown GNU/Linux Kernel messages from startup to and including Oops as well as config are attached. -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] Bootdata ok (command line is BOOT_IMAGE=2.6.12rc2 ro root=301 hdb=none hdc=cdrom hdd=none elevator=cfq psmouse.rate=20 report_lost_ticks iommu=off init=/bin/bash) Linux version 2.6.12-rc3-gringo ([EMAIL PROTECTED]) (gcc version 3.4.3) #1 Thu Apr 21 15:45:08 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009f800 (usable) BIOS-e820: 0009f800 - 000a (reserved) BIOS-e820: 000d8000 - 0010 (reserved) BIOS-e820: 0010 - 3ff7 (usable) BIOS-e820: 3ff7 - 3ff7a000 (ACPI data) BIOS-e820: 3ff7a000 - 3ff8 (ACPI NVS) BIOS-e820: 3ff8 - 4000 (reserved) BIOS-e820: fffe - 0001 (reserved) ACPI: RSDP (v000 PTLTD ) @ 0x000f6a60 ACPI: RSDT (v001 PTLTDRSDT 0x0604 LTP 0x) @ 0x3ff73fde ACPI: FADT (v002 AMDK8 PTLTW0x0604 PTL_ 0x000f4240) @ 0x3ff79e56 ACPI: SSDT (v001 PTLTD POWERNOW 0x0604 LTP 0x0001) @ 0x3ff79eda ACPI: MADT (v001 PTLTD APIC 0x0604 LTP 0x) @ 0x3ff79fb0 ACPI: DSDT (v001 VIA PTL_ACPI 0x0604 MSFT 0x010e) @ 0x On node 0 totalpages: 262000 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 257904 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:4 APIC version 16 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 3, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 4000 (gap: 4000:bffe) Built 1 zonelists Kernel command line: BOOT_IMAGE=2.6.12rc2 ro root=301 hdb=none hdc=cdrom hdd=none elevator=cfq psmouse.rate=20 report_lost_ticks iommu=off init=/bin/bash console=tty0 ide_setup: hdb=none ide_setup: hdc=cdrom ide_setup: hdd=none Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 1801.076 MHz processor. time.c: Using PIT/TSC based timekeeping. Console: colour VGA+ 80x50 time.c: Lost 3 timer tick(s)! rip vfs_caches_init_early+0x0/0xa0) Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Memory: 1024468k/1048000k available (2958k kernel code, 22832k reserved, 1639k data, 164k init) Calibrating delay loop... 3547.13 BogoMIPS (lpj=1773568) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 0a time.c: Lost 86 timer tick(s)! rip acpi_os_write_port+0x1a/0x36) Using local APIC NMI watchdog using perfctr0 Using local APIC timer interrupts. Detected 12.507 MHz APIC timer. time.c: Lost 55 timer tick(s)! rip setup_boot_APIC_clock+0x112/0x120) NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20050309 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) PCI: Via IRQ fixup Boot video device is :01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [ALKA] (IRQs 16 17 18 19 20 21 22 23) *10, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs 16 17 18 19 20 21 22 23) *10, disabled. ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *11, disabled. ACPI: PCI Interrupt Link [ALKD] (IRQs 21) *11, disabled. ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 12 14 15) *10 ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *10 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12 14 15) ACPI: Embedded Controller [EC] (gpe 11) time.c: Lost 8 timer tick(s)! rip acpi_os_write_port+0x1a/0x36) time.c: Lost 8 timer tick(s)! rip acpi_os_write_port+0x1a/0x36) Linux Plug and Play Support v0.97 (c) Adam Belay
Re: Linux 2.6.12-rc3
Compile error on x86_64: CC [M] drivers/usb/image/microtek.o drivers/usb/image/microtek.c: In function `mts_scsi_abort': drivers/usb/image/microtek.c:338: error: `FAILURE' undeclared (first use in this function) drivers/usb/image/microtek.c:338: error: (Each undeclared identifier is reported only once drivers/usb/image/microtek.c:338: error: for each function it appears in.) make[3]: *** [drivers/usb/image/microtek.o] Error 1 make[2]: *** [drivers/usb/image] Error 2 make[1]: *** [drivers/usb] Error 2 make: *** [drivers] Error 2 -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] - 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.6.12-rc3
> It's available both as a patch (against 2.6.11) and as a tar-ball, and Where IS the tarball? Not on www.kernel.org, that's for sure. -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - 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.6.12-rc3
On Thu, 2005-04-21 at 13:20 +0200, Pavel Machek wrote: > Hi! > > > And for the crazy people, the git archive on kernel.org is up and running > > under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the > > adventurous of you, the name of the 2.6.12-rc3 release is a very nice and > > readable: > > > > a2755a80f40e5794ddc20e00f781af9d6320fafb > > > > and eventually I'll try to make sure that I actually accompany all > > releases with the SHA1 git name of the release signed with a digital > > signature. > > As far as I can see... (working with pasky's version of git) > > You should put this into .git/remotes > > linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > > Then > > RSYNC_FLAGS=-zavP git pull linus > > should do the right thing. > From 0.5 or 0.6 you just have to do: git init rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > [pasky, would it be possible to make some kind of progress indication > default for long pulls?] > Latest seems to do the rsync verbose. -- Martin Schlemmer signature.asc Description: This is a digitally signed message part
Re: Linux 2.6.12-rc3
Hi! > > And for the crazy people, the git archive on kernel.org is up and running > > under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the > > adventurous of you, the name of the 2.6.12-rc3 release is a very nice and > > readable: > > > > a2755a80f40e5794ddc20e00f781af9d6320fafb > > > > and eventually I'll try to make sure that I actually accompany all > > releases with the SHA1 git name of the release signed with a digital > > signature. > > As far as I can see... (working with pasky's version of git) > > You should put this into .git/remotes > > linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > > Then > > RSYNC_FLAGS=-zavP git pull linus > > should do the right thing. Well, not sure. I did git track linus git cancel but Makefile still contains -rc2. (Is "git cancel" right way to check out the tree?) and git diff -r linus: still contains some changes. [I did some experimental pull of scsi changes long time ago, is it that problem?] Pavel -- Boycott Kodak -- for their patent abuse against Java. - 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.6.12-rc3
Hi! > And for the crazy people, the git archive on kernel.org is up and running > under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the > adventurous of you, the name of the 2.6.12-rc3 release is a very nice and > readable: > > a2755a80f40e5794ddc20e00f781af9d6320fafb > > and eventually I'll try to make sure that I actually accompany all > releases with the SHA1 git name of the release signed with a digital > signature. As far as I can see... (working with pasky's version of git) You should put this into .git/remotes linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git Then RSYNC_FLAGS=-zavP git pull linus should do the right thing. [pasky, would it be possible to make some kind of progress indication default for long pulls?] > One of the tools I don't have set up yet is the old "shortlog" script, so > I did this really hacky conversion. You don't want to know, but let's say > that I'm re-aquainting myself with 'sed' after a long time ;). But if some > lines look like they got hacked up in the middle, rest assured that that's > exactly what happened, and the long log should have the rest ... -- Boycott Kodak -- for their patent abuse against Java. - 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.6.12-rc3
On Thu, 21 Apr 2005, Jan Dittmer wrote:
> Linus Torvalds wrote:
> > Geert Uytterhoeven:
> > [PATCH] M68k: Update defconfigs for 2.6.11
> > [PATCH] M68k: Update defconfigs for 2.6.12-rc2
>
> Why do I still get this error when trying to cross-compile for m68k?
Because to build m68k kernels, you (still :-( have to use the Linux/m68k CVS
repository, cfr. http://linux-m68k-cvs.ubb.ca/.
BTW, my patch queue is at
http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-2.6.x-merging/.
The main offender is POSTPONED/156-thread_info.diff.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-
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.6.12-rc3
Linus Torvalds wrote:
> Geert Uytterhoeven:
> [PATCH] M68k: Update defconfigs for 2.6.11
> [PATCH] M68k: Update defconfigs for 2.6.12-rc2
Why do I still get this error when trying to cross-compile for m68k?
toolchain:
Reading specs from
/usr/local/m68k-uclinux-tools/lib/gcc/m68k-uclinux/3.4.0/specs
Configured with: /usr/local/src/uclinux-tools/gcc-3.4.0/configure
--target=m68k-uclinux --prefix=/usr/local/m68k-uclinux-tools
--enable-languages=c,c++ --enable-multilib --enable-target-optspace
--with-gnu-ld --disable-nls --disable-__cxa_atexit --disable-c99
--disable-clocale
--disable-c-mbchar --disable-long-long --enable-threads=posix
--enable-cxx-flags=-D_ISOC99_SOURCE -D_BSD_SOURCE
Thread model: posix
gcc version 3.4.0
GNU ld version 2.14.90.0.8 20040114
(I tried an alternative toolchain with gcc 3.3.3 as well)
$ make mrproper
$ make ARCH=m68k CROSS_COMPILE=m68k-elf- mrproper
$ make ARCH=m68k CROSS_COMPILE=m68k-elf- defconfig
$ make ARCH=m68k CROSS_COMPILE=m68k-elf-
CHK include/linux/version.h
UPD include/linux/version.h
SYMLINK include/asm -> include/asm-m68k
SPLIT include/linux/autoconf.h -> include/config/*
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
CC arch/m68k/kernel/asm-offsets.s
In file included from include/linux/spinlock.h:12,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/thread_info.h:30: error: parse error before '{' token
include/linux/thread_info.h:35: error: parse error before '{' token
include/linux/thread_info.h: In function `test_and_set_thread_flag':
include/linux/thread_info.h:42: error: `current' undeclared (first use in this
function)
include/linux/thread_info.h:42: error: (Each undeclared identifier is reported
only once
include/linux/thread_info.h:42: error: for each function it appears in.)
include/linux/thread_info.h: In function `test_and_clear_thread_flag':
include/linux/thread_info.h:47: error: `current' undeclared (first use in this
function)
include/linux/thread_info.h: At top level:
include/linux/thread_info.h:50: error: parse error before '{' token
include/linux/thread_info.h:50: warning: type defaults to `int' in declaration
of `___res'
include/linux/thread_info.h:50: warning: data definition has no type or storage
class
include/linux/thread_info.h:50: error: parse error before '}' token
include/linux/thread_info.h: In function `set_ti_thread_flag':
include/linux/thread_info.h:57: error: structure has no member named `flags'
include/linux/thread_info.h:57: error: structure has no member named `flags'
include/linux/thread_info.h: In function `clear_ti_thread_flag':
include/linux/thread_info.h:62: error: structure has no member named `flags'
include/linux/thread_info.h:62: error: structure has no member named `flags'
include/linux/thread_info.h: In function `test_and_set_ti_thread_flag':
include/linux/thread_info.h:67: error: structure has no member named `flags'
include/linux/thread_info.h:67: error: structure has no member named `flags'
include/linux/thread_info.h: In function `test_and_clear_ti_thread_flag':
include/linux/thread_info.h:72: error: structure has no member named `flags'
include/linux/thread_info.h:72: error: structure has no member named `flags'
include/linux/thread_info.h: In function `test_ti_thread_flag':
include/linux/thread_info.h:77: error: structure has no member named `flags'
In file included from include/linux/spinlock.h:12,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/thread_info.h:80:41: macro "set_need_resched" passed 1 arguments,
but takes just 0
include/linux/thread_info.h: At top level:
include/linux/thread_info.h:81: error: syntax error before '{' token
include/linux/thread_info.h:85:43: macro "clear_need_resched" passed 1
arguments, but takes just 0
include/linux/thread_info.h:86: error: syntax error before '{' token
In file included from arch/m68k/kernel/asm-offsets.c:12:
include/linux/sched.h:1108: error: parse error before '{' token
include/linux/sched.h:1113: error: parse error before '{' token
include/linux/sched.h:1118: error: parse error before '{' token
include/linux/sched.h:1118: warning: type defaults to `int' in declaration of
`___res'
include/linux/sched.h:1118: warning: data definition has no type or storage
class
include/linux/sched.h:1118: error: parse error before '}' token
include/linux/sched.h:1118: warning: type defaults to `int' in declaration of
`__res'
include/linux/sched.h:1118: warning: data definition has no type or storage
class
include/linux/sched.h:1118: error: parse error before '}' token
include/linux/sched.h:1128: error: parse error before '{' token
include/linux/sched.h:1128: warning: type defaults to `int' in declaration of
`___res'
include/linux/sched.h:1128: warning: data definition has no type
Re: Linux 2.6.12-rc3
> [EMAIL PROTECTED]: > [PATCH] zfcp: convert to compat_ioctl This does not seem to compile anymore with defconfig: CC drivers/s390/scsi/zfcp_aux.o /usr/src/ctest/rc/kernel/drivers/s390/scsi/zfcp_aux.c:63: warning: initialization from incompatible pointer type /usr/src/ctest/rc/kernel/drivers/s390/scsi/zfcp_aux.c:366: error: conflicting types for `zfcp_cfdc_dev_ioctl' /usr/src/ctest/rc/kernel/drivers/s390/scsi/zfcp_aux.c:55: error: previous declaration of `zfcp_cfdc_dev_ioctl' make[3]: *** [drivers/s390/scsi/zfcp_aux.o] Error 1 make[2]: *** [drivers/s390/scsi] Error 2 make[1]: *** [drivers/s390] Error 2 make: *** [_all] Error 2 Jan - 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.6.12-rc3
On Wed, 2005-04-20 at 17:59 -0700, Linus Torvalds wrote: > And for the crazy people, the git archive on kernel.org is up and running > under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the > adventurous of you, the name of the 2.6.12-rc3 release is a very nice and > readable: > > a2755a80f40e5794ddc20e00f781af9d6320fafb > > and eventually I'll try to make sure that I actually accompany all > releases with the SHA1 git name of the release signed with a digital > signature. > Small nit - how about using 'git tag' to tag the releases? Then it will not be a problem to find a release later on ... Thanks, -- Martin Schlemmer signature.asc Description: This is a digitally signed message part
Re: Linux 2.6.12-rc3
On Wed, 2005-04-20 at 17:59 -0700, Linus Torvalds wrote: And for the crazy people, the git archive on kernel.org is up and running under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the adventurous of you, the name of the 2.6.12-rc3 release is a very nice and readable: a2755a80f40e5794ddc20e00f781af9d6320fafb and eventually I'll try to make sure that I actually accompany all releases with the SHA1 git name of the release signed with a digital signature. Small nit - how about using 'git tag' to tag the releases? Then it will not be a problem to find a release later on ... Thanks, -- Martin Schlemmer signature.asc Description: This is a digitally signed message part
Re: Linux 2.6.12-rc3
[EMAIL PROTECTED]: [PATCH] zfcp: convert to compat_ioctl This does not seem to compile anymore with defconfig: CC drivers/s390/scsi/zfcp_aux.o /usr/src/ctest/rc/kernel/drivers/s390/scsi/zfcp_aux.c:63: warning: initialization from incompatible pointer type /usr/src/ctest/rc/kernel/drivers/s390/scsi/zfcp_aux.c:366: error: conflicting types for `zfcp_cfdc_dev_ioctl' /usr/src/ctest/rc/kernel/drivers/s390/scsi/zfcp_aux.c:55: error: previous declaration of `zfcp_cfdc_dev_ioctl' make[3]: *** [drivers/s390/scsi/zfcp_aux.o] Error 1 make[2]: *** [drivers/s390/scsi] Error 2 make[1]: *** [drivers/s390] Error 2 make: *** [_all] Error 2 Jan - 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.6.12-rc3
Linus Torvalds wrote:
Geert Uytterhoeven:
[PATCH] M68k: Update defconfigs for 2.6.11
[PATCH] M68k: Update defconfigs for 2.6.12-rc2
Why do I still get this error when trying to cross-compile for m68k?
toolchain:
Reading specs from
/usr/local/m68k-uclinux-tools/lib/gcc/m68k-uclinux/3.4.0/specs
Configured with: /usr/local/src/uclinux-tools/gcc-3.4.0/configure
--target=m68k-uclinux --prefix=/usr/local/m68k-uclinux-tools
--enable-languages=c,c++ --enable-multilib --enable-target-optspace
--with-gnu-ld --disable-nls --disable-__cxa_atexit --disable-c99
--disable-clocale
--disable-c-mbchar --disable-long-long --enable-threads=posix
--enable-cxx-flags=-D_ISOC99_SOURCE -D_BSD_SOURCE
Thread model: posix
gcc version 3.4.0
GNU ld version 2.14.90.0.8 20040114
(I tried an alternative toolchain with gcc 3.3.3 as well)
$ make mrproper
$ make ARCH=m68k CROSS_COMPILE=m68k-elf- mrproper
$ make ARCH=m68k CROSS_COMPILE=m68k-elf- defconfig
$ make ARCH=m68k CROSS_COMPILE=m68k-elf-
CHK include/linux/version.h
UPD include/linux/version.h
SYMLINK include/asm - include/asm-m68k
SPLIT include/linux/autoconf.h - include/config/*
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
CC arch/m68k/kernel/asm-offsets.s
In file included from include/linux/spinlock.h:12,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/thread_info.h:30: error: parse error before '{' token
include/linux/thread_info.h:35: error: parse error before '{' token
include/linux/thread_info.h: In function `test_and_set_thread_flag':
include/linux/thread_info.h:42: error: `current' undeclared (first use in this
function)
include/linux/thread_info.h:42: error: (Each undeclared identifier is reported
only once
include/linux/thread_info.h:42: error: for each function it appears in.)
include/linux/thread_info.h: In function `test_and_clear_thread_flag':
include/linux/thread_info.h:47: error: `current' undeclared (first use in this
function)
include/linux/thread_info.h: At top level:
include/linux/thread_info.h:50: error: parse error before '{' token
include/linux/thread_info.h:50: warning: type defaults to `int' in declaration
of `___res'
include/linux/thread_info.h:50: warning: data definition has no type or storage
class
include/linux/thread_info.h:50: error: parse error before '}' token
include/linux/thread_info.h: In function `set_ti_thread_flag':
include/linux/thread_info.h:57: error: structure has no member named `flags'
include/linux/thread_info.h:57: error: structure has no member named `flags'
include/linux/thread_info.h: In function `clear_ti_thread_flag':
include/linux/thread_info.h:62: error: structure has no member named `flags'
include/linux/thread_info.h:62: error: structure has no member named `flags'
include/linux/thread_info.h: In function `test_and_set_ti_thread_flag':
include/linux/thread_info.h:67: error: structure has no member named `flags'
include/linux/thread_info.h:67: error: structure has no member named `flags'
include/linux/thread_info.h: In function `test_and_clear_ti_thread_flag':
include/linux/thread_info.h:72: error: structure has no member named `flags'
include/linux/thread_info.h:72: error: structure has no member named `flags'
include/linux/thread_info.h: In function `test_ti_thread_flag':
include/linux/thread_info.h:77: error: structure has no member named `flags'
In file included from include/linux/spinlock.h:12,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/thread_info.h:80:41: macro set_need_resched passed 1 arguments,
but takes just 0
include/linux/thread_info.h: At top level:
include/linux/thread_info.h:81: error: syntax error before '{' token
include/linux/thread_info.h:85:43: macro clear_need_resched passed 1
arguments, but takes just 0
include/linux/thread_info.h:86: error: syntax error before '{' token
In file included from arch/m68k/kernel/asm-offsets.c:12:
include/linux/sched.h:1108: error: parse error before '{' token
include/linux/sched.h:1113: error: parse error before '{' token
include/linux/sched.h:1118: error: parse error before '{' token
include/linux/sched.h:1118: warning: type defaults to `int' in declaration of
`___res'
include/linux/sched.h:1118: warning: data definition has no type or storage
class
include/linux/sched.h:1118: error: parse error before '}' token
include/linux/sched.h:1118: warning: type defaults to `int' in declaration of
`__res'
include/linux/sched.h:1118: warning: data definition has no type or storage
class
include/linux/sched.h:1118: error: parse error before '}' token
include/linux/sched.h:1128: error: parse error before '{' token
include/linux/sched.h:1128: warning: type defaults to `int' in declaration of
`___res'
include/linux/sched.h:1128: warning: data definition has no type or
Re: Linux 2.6.12-rc3
On Thu, 21 Apr 2005, Jan Dittmer wrote:
Linus Torvalds wrote:
Geert Uytterhoeven:
[PATCH] M68k: Update defconfigs for 2.6.11
[PATCH] M68k: Update defconfigs for 2.6.12-rc2
Why do I still get this error when trying to cross-compile for m68k?
Because to build m68k kernels, you (still :-( have to use the Linux/m68k CVS
repository, cfr. http://linux-m68k-cvs.ubb.ca/.
BTW, my patch queue is at
http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-2.6.x-merging/.
The main offender is POSTPONED/156-thread_info.diff.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
-
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.6.12-rc3
Hi! And for the crazy people, the git archive on kernel.org is up and running under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the adventurous of you, the name of the 2.6.12-rc3 release is a very nice and readable: a2755a80f40e5794ddc20e00f781af9d6320fafb and eventually I'll try to make sure that I actually accompany all releases with the SHA1 git name of the release signed with a digital signature. As far as I can see... (working with pasky's version of git) You should put this into .git/remotes linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git Then RSYNC_FLAGS=-zavP git pull linus should do the right thing. [pasky, would it be possible to make some kind of progress indication default for long pulls?] One of the tools I don't have set up yet is the old shortlog script, so I did this really hacky conversion. You don't want to know, but let's say that I'm re-aquainting myself with 'sed' after a long time ;). But if some lines look like they got hacked up in the middle, rest assured that that's exactly what happened, and the long log should have the rest ... -- Boycott Kodak -- for their patent abuse against Java. - 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.6.12-rc3
Hi! And for the crazy people, the git archive on kernel.org is up and running under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the adventurous of you, the name of the 2.6.12-rc3 release is a very nice and readable: a2755a80f40e5794ddc20e00f781af9d6320fafb and eventually I'll try to make sure that I actually accompany all releases with the SHA1 git name of the release signed with a digital signature. As far as I can see... (working with pasky's version of git) You should put this into .git/remotes linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git Then RSYNC_FLAGS=-zavP git pull linus should do the right thing. Well, not sure. I did git track linus git cancel but Makefile still contains -rc2. (Is git cancel right way to check out the tree?) and git diff -r linus: still contains some changes. [I did some experimental pull of scsi changes long time ago, is it that problem?] Pavel -- Boycott Kodak -- for their patent abuse against Java. - 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.6.12-rc3
On Thu, 2005-04-21 at 13:20 +0200, Pavel Machek wrote: Hi! And for the crazy people, the git archive on kernel.org is up and running under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the adventurous of you, the name of the 2.6.12-rc3 release is a very nice and readable: a2755a80f40e5794ddc20e00f781af9d6320fafb and eventually I'll try to make sure that I actually accompany all releases with the SHA1 git name of the release signed with a digital signature. As far as I can see... (working with pasky's version of git) You should put this into .git/remotes linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git Then RSYNC_FLAGS=-zavP git pull linus should do the right thing. From 0.5 or 0.6 you just have to do: git init rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git [pasky, would it be possible to make some kind of progress indication default for long pulls?] Latest seems to do the rsync verbose. -- Martin Schlemmer signature.asc Description: This is a digitally signed message part
Re: Linux 2.6.12-rc3
It's available both as a patch (against 2.6.11) and as a tar-ball, and Where IS the tarball? Not on www.kernel.org, that's for sure. -- Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] - 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.6.12-rc3
Compile error on x86_64: CC [M] drivers/usb/image/microtek.o drivers/usb/image/microtek.c: In function `mts_scsi_abort': drivers/usb/image/microtek.c:338: error: `FAILURE' undeclared (first use in this function) drivers/usb/image/microtek.c:338: error: (Each undeclared identifier is reported only once drivers/usb/image/microtek.c:338: error: for each function it appears in.) make[3]: *** [drivers/usb/image/microtek.o] Error 1 make[2]: *** [drivers/usb/image] Error 2 make[1]: *** [drivers/usb] Error 2 make: *** [drivers] Error 2 -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] - 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.6.12-rc3: Oops on IDE flash disk eject
As already reported to lkml and IDE maintainer for 2.6.12-rc2: Oops on 'cardctl eject' of an IDE flash disk (Pretec ATA Flash 16MB). 2.6.11.2 works fine. System: Linux (none) 2.6.12-rc3-gringo #1 Thu Apr 21 15:45:08 CEST 2005 x86_64 unknown unknown GNU/Linux Kernel messages from startup to and including Oops as well as config are attached. -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] Bootdata ok (command line is BOOT_IMAGE=2.6.12rc2 ro root=301 hdb=none hdc=cdrom hdd=none elevator=cfq psmouse.rate=20 report_lost_ticks iommu=off init=/bin/bash) Linux version 2.6.12-rc3-gringo ([EMAIL PROTECTED]) (gcc version 3.4.3) #1 Thu Apr 21 15:45:08 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009f800 (usable) BIOS-e820: 0009f800 - 000a (reserved) BIOS-e820: 000d8000 - 0010 (reserved) BIOS-e820: 0010 - 3ff7 (usable) BIOS-e820: 3ff7 - 3ff7a000 (ACPI data) BIOS-e820: 3ff7a000 - 3ff8 (ACPI NVS) BIOS-e820: 3ff8 - 4000 (reserved) BIOS-e820: fffe - 0001 (reserved) ACPI: RSDP (v000 PTLTD ) @ 0x000f6a60 ACPI: RSDT (v001 PTLTDRSDT 0x0604 LTP 0x) @ 0x3ff73fde ACPI: FADT (v002 AMDK8 PTLTW0x0604 PTL_ 0x000f4240) @ 0x3ff79e56 ACPI: SSDT (v001 PTLTD POWERNOW 0x0604 LTP 0x0001) @ 0x3ff79eda ACPI: MADT (v001 PTLTD APIC 0x0604 LTP 0x) @ 0x3ff79fb0 ACPI: DSDT (v001 VIA PTL_ACPI 0x0604 MSFT 0x010e) @ 0x On node 0 totalpages: 262000 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 257904 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:4 APIC version 16 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 3, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 4000 (gap: 4000:bffe) Built 1 zonelists Kernel command line: BOOT_IMAGE=2.6.12rc2 ro root=301 hdb=none hdc=cdrom hdd=none elevator=cfq psmouse.rate=20 report_lost_ticks iommu=off init=/bin/bash console=tty0 ide_setup: hdb=none ide_setup: hdc=cdrom ide_setup: hdd=none Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 1801.076 MHz processor. time.c: Using PIT/TSC based timekeeping. Console: colour VGA+ 80x50 time.c: Lost 3 timer tick(s)! rip vfs_caches_init_early+0x0/0xa0) Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Memory: 1024468k/1048000k available (2958k kernel code, 22832k reserved, 1639k data, 164k init) Calibrating delay loop... 3547.13 BogoMIPS (lpj=1773568) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 0a time.c: Lost 86 timer tick(s)! rip acpi_os_write_port+0x1a/0x36) Using local APIC NMI watchdog using perfctr0 Using local APIC timer interrupts. Detected 12.507 MHz APIC timer. time.c: Lost 55 timer tick(s)! rip setup_boot_APIC_clock+0x112/0x120) NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20050309 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) PCI: Via IRQ fixup Boot video device is :01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [ALKA] (IRQs 16 17 18 19 20 21 22 23) *10, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs 16 17 18 19 20 21 22 23) *10, disabled. ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *11, disabled. ACPI: PCI Interrupt Link [ALKD] (IRQs 21) *11, disabled. ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 12 14 15) *10 ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *10 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12 14 15) ACPI: Embedded Controller [EC] (gpe 11) time.c: Lost 8 timer tick(s)! rip acpi_os_write_port+0x1a/0x36) time.c: Lost 8 timer tick(s)! rip acpi_os_write_port+0x1a/0x36) Linux Plug and Play Support v0.97 (c) Adam Belay
Re: Linux 2.6.12-rc3: Oops on IDE flash disk eject
The following patch fixes the Oops though I don't know if this is the
correct solution.
--- linux-2.6.12-rc3/drivers/ide/ide.c.ast
+++ linux-2.6.12-rc3/drivers/ide/ide.c
@@ -2082,7 +2082,8 @@
static int ide_drive_remove(struct device * dev)
{
ide_drive_t * drive = container_of(dev,ide_drive_t,gendev);
- DRIVER(drive)-cleanup(drive);
+ if(DRIVER(drive))
+ DRIVER(drive)-cleanup(drive);
return 0;
}
--
Andreas Steinmetz SPAMmers use [EMAIL PROTECTED]
-
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.6.12-rc3
On Thu, 21 Apr 2005 14:19:10 +0200 Ralf Hildebrandt wrote: | It's available both as a patch (against 2.6.11) and as a tar-ball, and | Where IS the tarball? Not on www.kernel.org, that's for sure. in http://www.kernel.org/pub/linux/kernel/v2.6/testing/ --- ~Randy - 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.6.12-rc3
Dear diary, on Thu, Apr 21, 2005 at 02:03:27PM CEST, I got a letter where Pavel Machek [EMAIL PROTECTED] told me that... You should put this into .git/remotes linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (git addremote is preferred for that :-) Then RSYNC_FLAGS=-zavP git pull linus -v is passed to rsync by default. I'll gladly add other reasonable rsync flags (I don't call printing each considered file reasonable; fsck or wget-like progressbar would be ideal). Well, not sure. I did git track linus git cancel but Makefile still contains -rc2. (Is git cancel right way to check out the tree?) No. git cancel does what it says - cancels your local changes to the working tree. git track will only set that next time you pull from linus, the changes will be automatically merged. (Note that this will change with the big UI change.) Either do git track linus git pull or git merge linus to get Linus' changes if you didn't pull yet. and git diff -r linus: still contains some changes. [I did some experimental pull of scsi changes long time ago, is it that problem?] If you don't have your HEAD on Linus' branch, it will do a tree merge instead of fast-forward; that is, it will not just move your HEAD on to match Linus' HEAD, but it will make a regular merge and then ask you to do a merge commit. -- Petr Pasky Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor - 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.6.12-rc3
On Thu, Apr 21, 2005 at 11:10:15AM +0200, Geert Uytterhoeven wrote: On Thu, 21 Apr 2005, Jan Dittmer wrote: Linus Torvalds wrote: Geert Uytterhoeven: [PATCH] M68k: Update defconfigs for 2.6.11 [PATCH] M68k: Update defconfigs for 2.6.12-rc2 Why do I still get this error when trying to cross-compile for m68k? Because to build m68k kernels, you (still :-( have to use the Linux/m68k CVS repository, cfr. http://linux-m68k-cvs.ubb.ca/. BTW, my patch queue is at http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-2.6.x-merging/. The main offender is POSTPONED/156-thread_info.diff. I think I have a sane splitup of that stuff. If you have time to review - yell - 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.6.12-rc3: various swsusp problems
Hi Pavel, there's some problems with swsusp in 2.6.12-rc3 (x86_64): 1. Is it necessary to print the following message during regular boot? swsusp: Suspend partition has wrong signature? It is a bit annoying and I believe it will confuse some swsusp users. 2. PCMCIA related hangs during swsusp. swsusp hangs after freeing memory when either cardmgr is running or pcmcia cards are *physically* inserted. It is insufficient to do a 'cardctl eject' the cards must be removed, too, for swsusp not to hang. I do suspect some problem with the 'pccardd' kernel threads. 3. Sometimes during the search for the suspend hang reason the system went during suspend into a lightshow of: eth0: Too much work at interrupt! and some line that ends in: release_console_sem+0x13d/0x1c0) The start of the line is not readable as it just flickers by in the eth0 message limbo. NIC is a built in RTL-8169 Gigabit Ethernet (rev 10). Oh, no chance for a serial console capture as there's no built in serial device in this laptop. -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] - 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.6.12-rc3
thread_info, part 1:
new helper - task_thread_info(task). On platforms that have thread_info
allocated separately (i.e. in default case) it simply returns task-thread_info.
m68k wants (and for good reasons) to embed its thread_info into task_struct.
So it will (in later patch) have task_thread_info() of its own.
For now we just add a macro for generic case and convert existing users in
core kernel to its user. Obviously safe - all normal architectures get
the same preprocessor output they used to get.
diff -urN RC12-rc3-delta23/include/linux/sched.h
RC12-rc3-task_thread_info/include/linux/sched.h
--- RC12-rc3-delta23/include/linux/sched.h Wed Apr 20 21:25:54 2005
+++ RC12-rc3-task_thread_info/include/linux/sched.h Wed Apr 20 22:51:13 2005
@@ -1102,32 +1102,34 @@
spin_unlock(p-alloc_lock);
}
+#define task_thread_info(task) (task)-thread_info
+
/* set thread flags in other task's structures
* - see asm/thread_info.h for TIF_ flags available
*/
static inline void set_tsk_thread_flag(struct task_struct *tsk, int flag)
{
- set_ti_thread_flag(tsk-thread_info,flag);
+ set_ti_thread_flag(task_thread_info(tsk), flag);
}
static inline void clear_tsk_thread_flag(struct task_struct *tsk, int flag)
{
- clear_ti_thread_flag(tsk-thread_info,flag);
+ clear_ti_thread_flag(task_thread_info(tsk), flag);
}
static inline int test_and_set_tsk_thread_flag(struct task_struct *tsk, int
flag)
{
- return test_and_set_ti_thread_flag(tsk-thread_info,flag);
+ return test_and_set_ti_thread_flag(task_thread_info(tsk), flag);
}
static inline int test_and_clear_tsk_thread_flag(struct task_struct *tsk, int
flag)
{
- return test_and_clear_ti_thread_flag(tsk-thread_info,flag);
+ return test_and_clear_ti_thread_flag(task_thread_info(tsk), flag);
}
static inline int test_tsk_thread_flag(struct task_struct *tsk, int flag)
{
- return test_ti_thread_flag(tsk-thread_info,flag);
+ return test_ti_thread_flag(task_thread_info(tsk), flag);
}
static inline void set_tsk_need_resched(struct task_struct *tsk)
@@ -1198,12 +1200,12 @@
static inline unsigned int task_cpu(const struct task_struct *p)
{
- return p-thread_info-cpu;
+ return task_thread_info(p)-cpu;
}
static inline void set_task_cpu(struct task_struct *p, unsigned int cpu)
{
- p-thread_info-cpu = cpu;
+ task_thread_info(p)-cpu = cpu;
}
#else
diff -urN RC12-rc3-delta23/kernel/exit.c RC12-rc3-task_thread_info/kernel/exit.c
--- RC12-rc3-delta23/kernel/exit.c Wed Apr 20 21:25:54 2005
+++ RC12-rc3-task_thread_info/kernel/exit.c Wed Apr 20 22:51:13 2005
@@ -827,7 +827,7 @@
if (group_dead tsk-signal-leader)
disassociate_ctty(1);
- module_put(tsk-thread_info-exec_domain-module);
+ module_put(task_thread_info(tsk)-exec_domain-module);
if (tsk-binfmt)
module_put(tsk-binfmt-module);
diff -urN RC12-rc3-delta23/kernel/fork.c RC12-rc3-task_thread_info/kernel/fork.c
--- RC12-rc3-delta23/kernel/fork.c Wed Apr 20 21:25:54 2005
+++ RC12-rc3-task_thread_info/kernel/fork.c Wed Apr 20 22:51:13 2005
@@ -893,7 +893,7 @@
if (nr_threads = max_threads)
goto bad_fork_cleanup_count;
- if (!try_module_get(p-thread_info-exec_domain-module))
+ if (!try_module_get(task_thread_info(p)-exec_domain-module))
goto bad_fork_cleanup_count;
if (p-binfmt !try_module_get(p-binfmt-module))
@@ -1138,7 +1138,7 @@
if (p-binfmt)
module_put(p-binfmt-module);
bad_fork_cleanup_put_domain:
- module_put(p-thread_info-exec_domain-module);
+ module_put(task_thread_info(p)-exec_domain-module);
bad_fork_cleanup_count:
put_group_info(p-group_info);
atomic_dec(p-user-processes);
diff -urN RC12-rc3-delta23/kernel/sched.c
RC12-rc3-task_thread_info/kernel/sched.c
--- RC12-rc3-delta23/kernel/sched.c Wed Apr 20 21:25:55 2005
+++ RC12-rc3-task_thread_info/kernel/sched.cWed Apr 20 22:51:13 2005
@@ -1151,7 +1151,7 @@
* but it also can be p-switch_lock.) So we compensate with a count
* of 1. Also, we want to start with kernel preemption disabled.
*/
- p-thread_info-preempt_count = 1;
+ task_thread_info(p)-preempt_count = 1;
#endif
/*
* Share the timeslice between parent and child, thus the
@@ -4018,9 +4018,9 @@
/* Set the preempt count _outside_ the spinlocks! */
#if defined(CONFIG_PREEMPT) !defined(CONFIG_PREEMPT_BKL)
- idle-thread_info-preempt_count = (idle-lock_depth = 0);
+ task_thread_info(idle)-preempt_count = (idle-lock_depth = 0);
#else
- idle-thread_info-preempt_count = 0;
+ task_thread_info(idle)-preempt_count = 0;
#endif
}
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Re: Linux 2.6.12-rc3
thread_info part 2:
encapsulates the rest of arch-dependent operations with thread_info access.
Two new helpers - setup_thread_info() and end_of_stack(). For normal
case the former consists of copying thread_info of parent to new thread_info
and the latter returns pointer immediately past the end of thread_info.
Again, normal platforms are obviously safe. Note that end_of_stack() is
need since unlike the default case, m68k has only a single pointer in
stack - not the entire thread_info. So DEBUG_STACK_USAGE needs to be
a bit different there.
diff -urN RC12-rc3-task_thread_info/include/linux/sched.h
RC12-rc3-other_helpers/include/linux/sched.h
--- RC12-rc3-task_thread_info/include/linux/sched.h Wed Apr 20 22:51:13 2005
+++ RC12-rc3-other_helpers/include/linux/sched.hWed Apr 20 22:51:15 2005
@@ -1104,6 +1104,16 @@
#define task_thread_info(task) (task)-thread_info
+static inline void setup_thread_info(struct task_struct *p, struct thread_info
*ti)
+{
+ *ti = *p-thread_info;
+}
+
+static inline unsigned long *end_of_stack(struct task_struct *p)
+{
+ return (unsigned long *)(p-thread_info + 1);
+}
+
/* set thread flags in other task's structures
* - see asm/thread_info.h for TIF_ flags available
*/
diff -urN RC12-rc3-task_thread_info/kernel/fork.c
RC12-rc3-other_helpers/kernel/fork.c
--- RC12-rc3-task_thread_info/kernel/fork.c Wed Apr 20 22:51:13 2005
+++ RC12-rc3-other_helpers/kernel/fork.cWed Apr 20 22:51:15 2005
@@ -169,8 +169,8 @@
return NULL;
}
- *ti = *orig-thread_info;
*tsk = *orig;
+ setup_thread_info(tsk, ti);
tsk-thread_info = ti;
ti-task = tsk;
diff -urN RC12-rc3-task_thread_info/kernel/sched.c
RC12-rc3-other_helpers/kernel/sched.c
--- RC12-rc3-task_thread_info/kernel/sched.cWed Apr 20 22:51:13 2005
+++ RC12-rc3-other_helpers/kernel/sched.c Wed Apr 20 22:51:15 2005
@@ -3945,10 +3945,10 @@
#endif
#ifdef CONFIG_DEBUG_STACK_USAGE
{
- unsigned long * n = (unsigned long *) (p-thread_info+1);
+ unsigned long * n = end_of_stack(p);
while (!*n)
n++;
- free = (unsigned long) n - (unsigned long)(p-thread_info+1);
+ free = (unsigned long) n - (unsigned long) end_of_stack(p);
}
#endif
printk(%5lu %5d %6d , free, p-pid, p-parent-pid);
-
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.6.12-rc3
m68k thread_info - part 4
The rest:
a) added embedded thread_info [m68k processor.h]
b) added missing symbols in asm-offsets.c
c) task_thread_info() and freinds in asm-m68k/thread_info.h
d) made m68k thread_info.h included by m68k processor.h, not the
other way round.
At that point thread_info mess is resolved - m68k builds and the rest of
the stuff to merge consists of normal driver patches.
IMO that's the least intrusive way to merge that sucker...
Comments?
diff -urN RC12-rc3-includes/arch/m68k/kernel/asm-offsets.c
RC12-rc3-m68k/arch/m68k/kernel/asm-offsets.c
--- RC12-rc3-includes/arch/m68k/kernel/asm-offsets.cThu Feb 26 02:23:09 2004
+++ RC12-rc3-m68k/arch/m68k/kernel/asm-offsets.cWed Apr 20 22:51:18 2005
@@ -31,6 +31,7 @@
DEFINE(TASK_SIGPENDING, offsetof(struct task_struct,
thread.work.sigpending));
DEFINE(TASK_NOTIFY_RESUME, offsetof(struct task_struct,
thread.work.notify_resume));
DEFINE(TASK_THREAD, offsetof(struct task_struct, thread));
+ DEFINE(TASK_INFO, offsetof(struct task_struct, thread.info));
DEFINE(TASK_MM, offsetof(struct task_struct, mm));
DEFINE(TASK_ACTIVE_MM, offsetof(struct task_struct, active_mm));
@@ -44,6 +45,10 @@
DEFINE(THREAD_FPREG, offsetof(struct thread_struct, fp));
DEFINE(THREAD_FPCNTL, offsetof(struct thread_struct, fpcntl));
DEFINE(THREAD_FPSTATE, offsetof(struct thread_struct, fpstate));
+
+ /* offsets into the thread_info struct */
+ DEFINE(TINFO_PREEMPT, offsetof(struct thread_info, preempt_count));
+ DEFINE(HARDIRQ_SHIFT, HARDIRQ_SHIFT);
/* offsets into the pt_regs */
DEFINE(PT_D0, offsetof(struct pt_regs, d0));
diff -urN RC12-rc3-includes/include/asm-m68k/processor.h
RC12-rc3-m68k/include/asm-m68k/processor.h
--- RC12-rc3-includes/include/asm-m68k/processor.h Wed Apr 20 21:25:51 2005
+++ RC12-rc3-m68k/include/asm-m68k/processor.h Wed Apr 20 22:51:19 2005
@@ -14,6 +14,7 @@
#define current_text_addr() ({ __label__ _l; _l: _l;})
#include linux/config.h
+#include linux/thread_info.h
#include asm/segment.h
#include asm/fpu.h
#include asm/ptrace.h
@@ -79,6 +80,7 @@
unsigned long fpcntl[3]; /* fp control regs */
unsigned char fpstate[FPSTATESIZE]; /* floating point state */
struct task_work work;
+ struct thread_info info;
};
#define INIT_THREAD { \
diff -urN RC12-rc3-includes/include/asm-m68k/thread_info.h
RC12-rc3-m68k/include/asm-m68k/thread_info.h
--- RC12-rc3-includes/include/asm-m68k/thread_info.hWed Apr 20 21:25:51 2005
+++ RC12-rc3-m68k/include/asm-m68k/thread_info.hWed Apr 20 22:51:19 2005
@@ -2,7 +2,6 @@
#define _ASM_M68K_THREAD_INFO_H
#include asm/types.h
-#include asm/processor.h
#include asm/page.h
struct thread_info {
@@ -36,10 +35,11 @@
#endif /* PAGE_SHIFT == 13 */
//#define init_thread_info (init_task.thread.info)
-#define init_stack (init_thread_union.stack)
-
-#define current_thread_info() (current-thread_info)
+#define init_thread_info (init_thread_union.thread_info)
+#define init_stack (init_thread_union.stack)
+#define task_thread_info(tsk) ((tsk)-thread.info)
+#define current_thread_info() task_thread_info(current)
#define __HAVE_THREAD_FUNCTIONS
@@ -51,6 +51,10 @@
#define TIF_MEMDIE 5
extern int thread_flag_fixme(void);
+
+#define setup_thread_info(p, ti) do (ti)-task = p; while(0)
+
+#define end_of_stack(p) ((unsigned long *)(p)-thread_info + 1)
/*
* flag set/clear/test wrappers
-
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.6.12-rc3
On Thu, Apr 21, 2005 at 06:57:23PM +0100, Al Viro wrote: thread_info part 3: heads. headers, even... - 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.6.12-rc3
Hi! You should put this into .git/remotes linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (git addremote is preferred for that :-) Oops :-). Well, not sure. I did git track linus git cancel but Makefile still contains -rc2. (Is git cancel right way to check out the tree?) No. git cancel does what it says - cancels your local changes to the working tree. git track will only set that next time you pull from linus, the changes will be automatically merged. (Note that this will change with the big UI change.) Is there way to say forget those changes in my repository, I want just plain vanilla without rm -rf? I see quite a lot of problems with fsck-tree. Is that normal? (I ran out of disk space few times during different operations...) -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms - 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.6.12-rc3
On 4/21/05, Linus Torvalds [EMAIL PROTECTED] wrote: Changes since 2.6.12-rc2: Benjamin Herrenschmidt: ... [PATCH] ppc32: Fix cpufreq problems this depends on two patches in -mm: add-suspend-method-to-cpufreq-core.patch Add suspend method to cpufreq core add-suspend-method-to-cpufreq-core-warning-fix.patch add-suspend-method-to-cpufreq-core-warning-fix without those patches defconfig is broken on ppc32 regards, Benoit - 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.6.12-rc3
Dear diary, on Thu, Apr 21, 2005 at 09:00:09PM CEST, I got a letter where Pavel Machek [EMAIL PROTECTED] told me that... Hi! Hi, Well, not sure. I did git track linus git cancel but Makefile still contains -rc2. (Is git cancel right way to check out the tree?) No. git cancel does what it says - cancels your local changes to the working tree. git track will only set that next time you pull from linus, the changes will be automatically merged. (Note that this will change with the big UI change.) Is there way to say forget those changes in my repository, I want just plain vanilla without rm -rf? git cancel will give you plain last commit. If you need plain vanilla, the hard way now is to just do commit-id .git/HEAD but your current HEAD will be lost forever. Or do git fork vanilla ~/vanilla linus and you will have the vanilla tree tracking linus in ~/vanilla. I'm not yet sure if we should have some Cogito interface for doing this and what its semantics should be. I see quite a lot of problems with fsck-tree. Is that normal? (I ran out of disk space few times during different operations...) Actually, in case your tree is older than about two days, I hope you did the convert-cache magic or fetched a fresh tree? -- Petr Pasky Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor - 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.6.12-rc3: various swsusp problems
Pavel Machek wrote: Hi! there's some problems with swsusp in 2.6.12-rc3 (x86_64): Are they new or were they in -rc2, too? Fixed the rc2/rc3 IDE Oops myself today that prevented me to test rc2 earlier. It seems the IDE maintainer is currently not very responsive and I didn't have sufficient spare time to look into this before today :-( Yes, all problems are already in rc2. 1. Is it necessary to print the following message during regular boot? swsusp: Suspend partition has wrong signature? It is a bit annoying and I believe it will confuse some swsusp users. Hmm, feel free to provide a patch. (I need something to try git on :-). I'll have a look over the weekend. 2. PCMCIA related hangs during swsusp. swsusp hangs after freeing memory when either cardmgr is running or pcmcia cards are *physically* inserted. It is insufficient to do a 'cardctl eject' the cards must be removed, too, for swsusp not to hang. I do suspect some problem with the 'pccardd' kernel threads. Did it work with any older kernel? Which driver is it? yenta? 2.6.11.2 works ok and, yes, its yenta. Some excerpt from lspci: 00:0b.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller 00:0b.1 CardBus bridge: Texas Instruments PCI7420 CardBus Controller 3. Sometimes during the search for the suspend hang reason the system went during suspend into a lightshow of: eth0: Too much work at interrupt! and some line that ends in: release_console_sem+0x13d/0x1c0) The start of the line is not readable as it just flickers by in the eth0 message limbo. NIC is a built in RTL-8169 Gigabit Ethernet (rev 10). Oh, no chance for a serial console capture as there's no built in serial device in this laptop. How repeatable is that? Will NIC work okay if you rmmod/insmod its driver? Pavel Happens with a probability of about 10% to 20%. I did comment out the 'Too much work...' printk in r8169.c which results in the following effect: no more message from the network driver (expected), no other printk related to release_console_sem or anything else unusal, but write to disk in the case the problem seems to happen is suddenly quite slow and suspend eventually succeeds. As the nic driver is built into the kernel insmod/rmmod currently won't do:-) Nevertheless there doesn't seem to be any strange behaviour after resume though I didn't really try to use the nic then. There is, however, definitely no such problem with the nic in 2.6.11.2. -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] - 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.6.12-rc3: various swsusp problems
Pavel Machek wrote: Hi! Are they new or were they in -rc2, too? Some further backtracking: The nic problem is already present in 2.6.12-rc1. The pcmcia hang problem is not present in 2.6.12-rc1. -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] - 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.6.12-rc3
Hi! It seems that someone should write Kernel hacker's guide to git... Documentation/git.txt seems like good place. I guess I'll do it. just plain vanilla without rm -rf? git cancel will give you plain last commit. If you need plain vanilla, the hard way now is to just do commit-id .git/HEAD but your current HEAD will be lost forever. Or do git fork vanilla ~/vanilla linus and you will have the vanilla tree tracking linus in ~/vanilla. Ok, thanks. I'm not yet sure if we should have some Cogito interface for doing this and what its semantics should be. What is Cogito, BTW? I see quite a lot of problems with fsck-tree. Is that normal? (I ran out of disk space few times during different operations...) Actually, in case your tree is older than about two days, I hope you did the convert-cache magic or fetched a fresh tree? No, I did not anything like that. I guess it is rm -rf time, then... Pavel -- Boycott Kodak -- for their patent abuse against Java. - 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.6.12-rc3
Dear diary, on Thu, Apr 21, 2005 at 11:38:11PM CEST, I got a letter where Pavel Machek [EMAIL PROTECTED] told me that... Hi! It seems that someone should write Kernel hacker's guide to git... Documentation/git.txt seems like good place. I guess I'll do it. I've also started writing some tutorial-like guide to Cogito on my notebook, but I have time for that only during lectures. :^) I'm not yet sure if we should have some Cogito interface for doing this and what its semantics should be. What is Cogito, BTW? New name for git-pasky. Everyone will surely rejoice as the usage will change significantly. But better let's clean it up now. (For more details, check git@ archives for git-pasky-0.6 announcement.) I see quite a lot of problems with fsck-tree. Is that normal? (I ran out of disk space few times during different operations...) Actually, in case your tree is older than about two days, I hope you did the convert-cache magic or fetched a fresh tree? No, I did not anything like that. I guess it is rm -rf time, then... That's the root of all your problems then. -- Petr Pasky Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor - 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.6.12-rc3
Hi! You should put this into .git/remotes linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (git addremote is preferred for that :-) Nice, so I now have my own -git tree, with two changes in it... Is there way to say git diff -r origin: but dump it patch-by-patch with some usable headers? [Looking at git export] Pavel Index: Documentation/git.txt === --- /dev/null (tree:9120479b4c721855b378db8907e1259f2e583f2b) +++ 007d34e2ed3d5fc54cbb4c16880145ade93affef/Documentation/git.txt (mode:100644 sha1:939d378ddaac5390c879520c139e66d9649ec4c4) @@ -0,0 +1,19 @@ + Kernel hacker's guide to git + + 2005 Pavel Machek [EMAIL PROTECTED] + +You can get git at http://pasky.or.cz/~pasky/dev/git/ . Compile it, +and place it somewhere in $PATH. Then you can get kernel by running + +git init rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git + +... Run git log to get idea of what happened in tree you are +tracking. Do git pull linus to pickup latest changes from Linus. You +can do git diff to see what changes you done in your local tree. git +cancel will kill any such changes. + +You can commit changes by doing git commit... If you want to get diff +of your changes against mainline, do + +git diff -r origin: + -- Boycott Kodak -- for their patent abuse against Java. - 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.6.12-rc3
On Fri, 22 Apr 2005, Pavel Machek wrote: Is there way to say git diff -r origin: but dump it patch-by-patch with some usable headers? In my git version there is a command called git-export for exactly this. I don't know if Pasky included that in his trees, but if not, you can just get my git tree (which should be compatible with Pasky's scripts, but mine just has the core stuff). Using git-export you can export your whole git tree if you want to, but more commonly you'd say git-export $(cat .git/HEAD) $(cat .git/BASE) where you'd have saved the previous head that you exported in the BASE thing (or, if you pull my tree, and want to export your changes back to me, you'd initialize BASE to the original HEAD in my tree). The output format of git-export is not the prettiest in the world, but I've never actually _used_ that command, I just wrote it as a demonstration thing. Linus - 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.6.12-rc3
Dear diary, on Fri, Apr 22, 2005 at 01:22:01AM CEST, I got a letter where Pavel Machek [EMAIL PROTECTED] told me that... Hi! Hi, You should put this into .git/remotes linus rsync://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (git addremote is preferred for that :-) Nice, so I now have my own -git tree, with two changes in it... Is there way to say git diff -r origin: but dump it patch-by-patch with some usable headers? [Looking at git export] Either Linus' demo git-export (NOT the same as git export!), or git patch. In the latest tree, it was extended to accept a range of two commits to process too. Note that the range semantics is rather peculiar at the least. ;-) -- Petr Pasky Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor - 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.6.12-rc3
On Thu, Apr 21, 2005 at 03:33:42PM +0200, Andreas Steinmetz wrote: Compile error on x86_64: CC [M] drivers/usb/image/microtek.o drivers/usb/image/microtek.c: In function `mts_scsi_abort': drivers/usb/image/microtek.c:338: error: `FAILURE' undeclared (first use in this function) Patch to fix this was posted on lkml and is in my queue to send to Linus in a bit. thanks, greg k-h - 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.6.12-rc3:microtek.c:338: error: for each function it appears in.
OK. I downloaded, patched and started the build. Basically everything stops when I get a microtek.c:338: error: `FAILURE' undeclared error (the build keeps trying, but no modules get created). I suspect others may have the same problem, but feel free to e-mail me for more information (and you will have to as I am not on the list). ...ok, also I have tried adding #define MTS_SCSI_ERR_MASK ~0x3fu #define FAILURE ~0x3fu on line 55 of microtek.h ...basically a copycat of the previous error line...(but I suspect the kernel maintainer would be a better person to define FAILURE somewhere...) And...it does boot and I can coughtaint.the.kernel.with.nvidia.videocough TIA, Bob -- Bob Gill [EMAIL PROTECTED] - 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.6.12-rc3
Linux 2.6.12-rc3 is still missing the following compile fixes: [PATCH] fix ultrastor.c compile error http://marc.theaimsgroup.com/?l=linux-scsi=111391774018717=2 [PATCH] fix aic7xxx_osm.c compile failure (gcc 2.95.x only) http://marc.theaimsgroup.com/?l=linux-scsi=111391769011616=2 [linux-usb-devel] Re: [PATCH] fix microtek.c compile failure http://marc.theaimsgroup.com/?l=linux-usb-devel=111391865311903=2 Another LKML poster (who I added to CC on this message) already hit the aic7xxx compile failure with 2.6.12-rc3... -Barry K. Nathan <[EMAIL PROTECTED]> - 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.6.12-rc3
Patrick McFarland wrote: On Wednesday 20 April 2005 09:09 pm, Alejandro Bonilla wrote: Why is kb not used anymore? What happened? Linus decided that keyboards are out, and voice activation is in. Remember to use a high quality microphone! Ohh _G_ Is that Why!? I thought it was cause there were some problems with 2 guys and a non-free Software? James gave me what I needed to know. ;-) Thanks. And I really hope that Linus can find a way to do things better for him and everyone else. Hopefully someone can create an SCM as nice and good as I read BK was... Sorry for invoking this old topic. - Alejandro - 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.6.12-rc3
On Wednesday 20 April 2005 09:09 pm, Alejandro Bonilla wrote: > Why is kb not used anymore? What happened? Linus decided that keyboards are out, and voice activation is in. Remember to use a high quality microphone! -- Patrick "Diablo-D3" McFarland || [EMAIL PROTECTED] "Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989 pgpA1nFX5rQ0f.pgp Description: PGP signature
Re: Linux 2.6.12-rc3
Have a look through the mail archives and try "Bitkeeper and Linux" in google, lets just say its been interesting. -- James Purser http://ksit.dynalias.com - 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.6.12-rc3
Linus Torvalds wrote: Ok, you know what the subject line means by now, but this release is a bit different from the usual ones, for obvious reasons. It's the first in a _long_ time that I've done without using BK, and it's the first one ever that has been built up completely with "git". It's available both as a patch (against 2.6.11) and as a tar-ball, and for non-BK users the biggest difference is probably that the ChangeLog format has changed a bit. And it will probably continue to evolve, since I don't have my "release-script" tools set up for the new setup, so this release was done largely manually with some ad-hoc scripting to get the ChangeLog information etc out of git. For BK users, I hope we can get a BK tree that tracks this set up soon, and it should hopefully not be too disruptive either. Excuse me for being so uninformed, poor reader and so on... Why is kb not used anymore? What happened? Thanks for the time, - Alejandro - 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/
Linux 2.6.12-rc3
Ok, you know what the subject line means by now, but this release is a bit different from the usual ones, for obvious reasons. It's the first in a _long_ time that I've done without using BK, and it's the first one ever that has been built up completely with "git". It's available both as a patch (against 2.6.11) and as a tar-ball, and for non-BK users the biggest difference is probably that the ChangeLog format has changed a bit. And it will probably continue to evolve, since I don't have my "release-script" tools set up for the new setup, so this release was done largely manually with some ad-hoc scripting to get the ChangeLog information etc out of git. For BK users, I hope we can get a BK tree that tracks this set up soon, and it should hopefully not be too disruptive either. And for the crazy people, the git archive on kernel.org is up and running under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the adventurous of you, the name of the 2.6.12-rc3 release is a very nice and readable: a2755a80f40e5794ddc20e00f781af9d6320fafb and eventually I'll try to make sure that I actually accompany all releases with the SHA1 git name of the release signed with a digital signature. One of the tools I don't have set up yet is the old "shortlog" script, so I did this really hacky conversion. You don't want to know, but let's say that I'm re-aquainting myself with 'sed' after a long time ;). But if some lines look like they got hacked up in the middle, rest assured that that's exactly what happened, and the long log should have the rest ... Linus Changes since 2.6.12-rc2: Adrian Bunk: [PATCH] MAINTAINERS: remove obsolete ACP/MWAVE MODEM entry [PATCH] let SOUND_AD1889 depend on PCI Alan Stern: [PATCH] USB: USB API documentation modification Alexander Nyberg: [PATCH] swsusp: SMP fix Andi Kleen: [PATCH] x86-64/i386: Revert cpuinfo siblings behaviour back to 2.6.10 [PATCH] x86-64: Fix BUG() [PATCH] x86_64: Add acpi_skip_timer_override option [PATCH] x86_64: Always use CPUID 8008 to figure out MTRR address space size [PATCH] x86_64: Call do_notify_resume unconditionally in entry.S [PATCH] x86_64: Correct wrong comment in local.h [PATCH] x86_64: Don't assume future AMD CPUs have K8 compatible performance counters [PATCH] x86_64: Dump stack and prevent recursion on early fault [PATCH] x86_64: Final support for AMD dual core [PATCH] x86_64: Fix a small missing schedule race [PATCH] x86_64: Fix interaction of single stepping with debuggers [PATCH] x86_64: Handle programs that set TF in user space using popf while single stepping [PATCH] x86_64: Keep only a single debug notifier chain [PATCH] x86_64: Make IRDA devices are not really ISA devices not depend on CONFIG_ISA [PATCH] x86_64: Make kernel math errors a die() now [PATCH] x86_64: Minor microoptimization in syscall entry slow path [PATCH] x86_64: Port over e820 gap detection from i386 [PATCH] x86_64: Regularize exception stack handling [PATCH] x86_64: Remove duplicated syscall entry. [PATCH] x86_64: Remove excessive stack allocation in MCE code with large NR_CPUS [PATCH] x86_64: Remove unused macro in preempt support [PATCH] x86_64: Rename the extended cpuid level field [PATCH] x86_64: Rewrite exception stack backtracing [PATCH] x86_64: Some fixes for single step handling [PATCH] x86_64: Support constantly ticking TSCs [PATCH] x86_64: Switch SMP bootup over to new CPU hotplug state machine [PATCH] x86_64: Use a VMA for the 32bit vsyscall [PATCH] x86_64: Use a common function to find code segment bases [PATCH] x86_64: Use the e820 hole to map the IOMMU/AGP aperture [PATCH] x86_64: Use the extended RIP MSR for machine check reporting if available. [PATCH] x86_64: add support for Intel dual-core detection and displaying [PATCH] x86_64: clean up ptrace single-stepping [PATCH] x86_64: disable interrupts during SMP bogomips checking Andrea Arcangeli: [PATCH] oom-killer disable for iscsi/lvm2/multipath userland critical sections Andrew Morton: [PATCH] Fix acl Oops [PATCH] USB: usb_cdc build fix [PATCH] USB: usbnet printk warning fix [PATCH] arm: add comment about dma_supported() [PATCH] arm: add comment about max_low_pfn/max_pfn [PATCH] arm: fix SIGBUS handling [PATCH] arm: fix help text for ixdp465 [PATCH] end_buffer_write_sync() avoid pointless assignments [PATCH] fix Bug 4395: modprobe bttv freezes the computer [PATCH] jbd dirty buffer leak fix [PATCH] vmscan: pageout(): remove unneeded test [PATCH] x86_64 show_stack(): call touch_nmi_watchdog Anton Blanchard: [PATCH] ppc64: remove -fno-omit-frame-pointer Arnaldo Carvalho de Melo: [PATCH] net: don't call kmem_cache_create with a spinlock held [SOCK]: on failure free the sock from the right place Artem B. Bityuckiy:
Linux 2.6.12-rc3
Ok, you know what the subject line means by now, but this release is a bit different from the usual ones, for obvious reasons. It's the first in a _long_ time that I've done without using BK, and it's the first one ever that has been built up completely with git. It's available both as a patch (against 2.6.11) and as a tar-ball, and for non-BK users the biggest difference is probably that the ChangeLog format has changed a bit. And it will probably continue to evolve, since I don't have my release-script tools set up for the new setup, so this release was done largely manually with some ad-hoc scripting to get the ChangeLog information etc out of git. For BK users, I hope we can get a BK tree that tracks this set up soon, and it should hopefully not be too disruptive either. And for the crazy people, the git archive on kernel.org is up and running under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the adventurous of you, the name of the 2.6.12-rc3 release is a very nice and readable: a2755a80f40e5794ddc20e00f781af9d6320fafb and eventually I'll try to make sure that I actually accompany all releases with the SHA1 git name of the release signed with a digital signature. One of the tools I don't have set up yet is the old shortlog script, so I did this really hacky conversion. You don't want to know, but let's say that I'm re-aquainting myself with 'sed' after a long time ;). But if some lines look like they got hacked up in the middle, rest assured that that's exactly what happened, and the long log should have the rest ... Linus Changes since 2.6.12-rc2: Adrian Bunk: [PATCH] MAINTAINERS: remove obsolete ACP/MWAVE MODEM entry [PATCH] let SOUND_AD1889 depend on PCI Alan Stern: [PATCH] USB: USB API documentation modification Alexander Nyberg: [PATCH] swsusp: SMP fix Andi Kleen: [PATCH] x86-64/i386: Revert cpuinfo siblings behaviour back to 2.6.10 [PATCH] x86-64: Fix BUG() [PATCH] x86_64: Add acpi_skip_timer_override option [PATCH] x86_64: Always use CPUID 8008 to figure out MTRR address space size [PATCH] x86_64: Call do_notify_resume unconditionally in entry.S [PATCH] x86_64: Correct wrong comment in local.h [PATCH] x86_64: Don't assume future AMD CPUs have K8 compatible performance counters [PATCH] x86_64: Dump stack and prevent recursion on early fault [PATCH] x86_64: Final support for AMD dual core [PATCH] x86_64: Fix a small missing schedule race [PATCH] x86_64: Fix interaction of single stepping with debuggers [PATCH] x86_64: Handle programs that set TF in user space using popf while single stepping [PATCH] x86_64: Keep only a single debug notifier chain [PATCH] x86_64: Make IRDA devices are not really ISA devices not depend on CONFIG_ISA [PATCH] x86_64: Make kernel math errors a die() now [PATCH] x86_64: Minor microoptimization in syscall entry slow path [PATCH] x86_64: Port over e820 gap detection from i386 [PATCH] x86_64: Regularize exception stack handling [PATCH] x86_64: Remove duplicated syscall entry. [PATCH] x86_64: Remove excessive stack allocation in MCE code with large NR_CPUS [PATCH] x86_64: Remove unused macro in preempt support [PATCH] x86_64: Rename the extended cpuid level field [PATCH] x86_64: Rewrite exception stack backtracing [PATCH] x86_64: Some fixes for single step handling [PATCH] x86_64: Support constantly ticking TSCs [PATCH] x86_64: Switch SMP bootup over to new CPU hotplug state machine [PATCH] x86_64: Use a VMA for the 32bit vsyscall [PATCH] x86_64: Use a common function to find code segment bases [PATCH] x86_64: Use the e820 hole to map the IOMMU/AGP aperture [PATCH] x86_64: Use the extended RIP MSR for machine check reporting if available. [PATCH] x86_64: add support for Intel dual-core detection and displaying [PATCH] x86_64: clean up ptrace single-stepping [PATCH] x86_64: disable interrupts during SMP bogomips checking Andrea Arcangeli: [PATCH] oom-killer disable for iscsi/lvm2/multipath userland critical sections Andrew Morton: [PATCH] Fix acl Oops [PATCH] USB: usb_cdc build fix [PATCH] USB: usbnet printk warning fix [PATCH] arm: add comment about dma_supported() [PATCH] arm: add comment about max_low_pfn/max_pfn [PATCH] arm: fix SIGBUS handling [PATCH] arm: fix help text for ixdp465 [PATCH] end_buffer_write_sync() avoid pointless assignments [PATCH] fix Bug 4395: modprobe bttv freezes the computer [PATCH] jbd dirty buffer leak fix [PATCH] vmscan: pageout(): remove unneeded test [PATCH] x86_64 show_stack(): call touch_nmi_watchdog Anton Blanchard: [PATCH] ppc64: remove -fno-omit-frame-pointer Arnaldo Carvalho de Melo: [PATCH] net: don't call kmem_cache_create with a spinlock held [SOCK]: on failure free the sock from the right place Artem B. Bityuckiy: [PATCH]
Re: Linux 2.6.12-rc3
Linus Torvalds wrote: Ok, you know what the subject line means by now, but this release is a bit different from the usual ones, for obvious reasons. It's the first in a _long_ time that I've done without using BK, and it's the first one ever that has been built up completely with git. It's available both as a patch (against 2.6.11) and as a tar-ball, and for non-BK users the biggest difference is probably that the ChangeLog format has changed a bit. And it will probably continue to evolve, since I don't have my release-script tools set up for the new setup, so this release was done largely manually with some ad-hoc scripting to get the ChangeLog information etc out of git. For BK users, I hope we can get a BK tree that tracks this set up soon, and it should hopefully not be too disruptive either. Excuse me for being so uninformed, poor reader and so on... Why is kb not used anymore? What happened? Thanks for the time, - Alejandro - 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.6.12-rc3
Have a look through the mail archives and try Bitkeeper and Linux in google, lets just say its been interesting. -- James Purser http://ksit.dynalias.com - 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.6.12-rc3
On Wednesday 20 April 2005 09:09 pm, Alejandro Bonilla wrote: Why is kb not used anymore? What happened? Linus decided that keyboards are out, and voice activation is in. Remember to use a high quality microphone! -- Patrick Diablo-D3 McFarland || [EMAIL PROTECTED] Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music. -- Kristian Wilson, Nintendo, Inc, 1989 pgpA1nFX5rQ0f.pgp Description: PGP signature
Re: Linux 2.6.12-rc3
Patrick McFarland wrote: On Wednesday 20 April 2005 09:09 pm, Alejandro Bonilla wrote: Why is kb not used anymore? What happened? Linus decided that keyboards are out, and voice activation is in. Remember to use a high quality microphone! Ohh _G_ Is that Why!? I thought it was cause there were some problems with 2 guys and a non-free Software? James gave me what I needed to know. ;-) Thanks. And I really hope that Linus can find a way to do things better for him and everyone else. Hopefully someone can create an SCM as nice and good as I read BK was... Sorry for invoking this old topic. - Alejandro - 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.6.12-rc3
Linux 2.6.12-rc3 is still missing the following compile fixes: [PATCH] fix ultrastor.c compile error http://marc.theaimsgroup.com/?l=linux-scsim=111391774018717w=2 [PATCH] fix aic7xxx_osm.c compile failure (gcc 2.95.x only) http://marc.theaimsgroup.com/?l=linux-scsim=111391769011616w=2 [linux-usb-devel] Re: [PATCH] fix microtek.c compile failure http://marc.theaimsgroup.com/?l=linux-usb-develm=111391865311903w=2 Another LKML poster (who I added to CC on this message) already hit the aic7xxx compile failure with 2.6.12-rc3... -Barry K. Nathan [EMAIL PROTECTED] - 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/
