[PATCH] hgafb.c as module (unresolved symbol) 2.4.6+
Hi,
As far as i noticed - since 2.4.6
there should be defined
#define INCLUDE_LINUX_LOGO_DATA
instead of
#define INCLUDE_LINUX_LOGOBW
otherwise linux logos do not get included and unresolved symbol occures
patch against 2.4.7-pre{1,2,3} attached, which afaik also applies for 2.4.6
PS.
in any case - please CC - not subscribed
--- linux/drivers/video/hgafb.c.origThu Feb 22 22:09:04 2001
+++ linux/drivers/video/hgafb.c Fri Jul 6 12:08:54 2001
@@ -49,7 +49,7 @@
#ifdef MODULE
-#define INCLUDE_LINUX_LOGOBW
+#define INCLUDE_LINUX_LOGO_DATA
#include
#endif /* MODULE */
[PATCH] hgafb.c as module (unresolved symbol) 2.4.6+
Hi,
As far as i noticed - since 2.4.6
there should be defined
#define INCLUDE_LINUX_LOGO_DATA
instead of
#define INCLUDE_LINUX_LOGOBW
otherwise linux logos do not get included and unresolved symbol occures
patch against 2.4.7-pre{1,2,3} attached, which afaik also applies for 2.4.6
PS.
in any case - please CC - not subscribed
--- linux/drivers/video/hgafb.c.origThu Feb 22 22:09:04 2001
+++ linux/drivers/video/hgafb.c Fri Jul 6 12:08:54 2001
@@ -49,7 +49,7 @@
#ifdef MODULE
-#define INCLUDE_LINUX_LOGOBW
+#define INCLUDE_LINUX_LOGO_DATA
#include linux/linux_logo.h
#endif /* MODULE */
2.4.5 2.4.6pre crashes
Hi, For few months I am running XFS CVS kernels (http://oss.sgi.com/projects/xfs/). Up till now i haven't faced any generic 2.4 issues. Problems began while XFS moved to 2.4.5 , same thing (i believe) i observed with both 2.4.6pre kernels. Linux-xfs people suggested to mail linux-kernel, so.. take a look please. My machine is Celeron 366 (Mendocino) 128MB RAM, PIIX4E, PDC20262, HPT366, with 6 ide disks (4 at PDC, 1 at PIIX4E and 1 at HPT366) and DM9102 Ethernet. RedHat 6.2 with some vital updates for 2.4 kernels... Sorry for not-complete backtrace (no serial console at the moment - rewritten manually). Stuff you can find below was observed on 2.4.6-pre2-xfs dated at 06/09. Machine crashed just before init run gettys (first output, no bt), the second time it crashed after being up for 3 minutes ca.. -- Scheduling in interrupt kernel BUG at sched.c:709! invalid operand: CPU:0 EIP:0010:[] EFLAGS: 00010092 eax: 001b ebx: ecx: c76a4000 edx: 0001 esi: edi: c01104f4 ebp: c12f9e04 esp: c12f9db4 ds: 0018 es: 0018 ss: 0018 Process init (pid: 1, stackpage=c12f9000) Stack c024aab4 c024ab56 02c5 c12f8000 c01104f4 c12f9e74 c12f8000 c014ffd6 c7fa9460 c6c38bc0 c12f9e24 c0150200 c12f9e74 c12f9e80 c12f8000 c014ff17 c12f8000 c0106c48 c881818c c0106c05 c76b41a0 c76b4228 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 8d 65 bc 5b 5e 5f 89 ec 5d c3 8d 76 00 55 89 e5 83 ec Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing -- -- Scheduling in interrupt kernel BUG at sched.c:709! Entering kdb (current=0xc1b3, pid 1822) Oops: invalid operand due to oops @ 0xc01118d1 eax = 0x001b ebx = 0x ecx = 0xc75e2000 edx = 0x0001 esi = 0x edi = 0x0246 esp = 0xc1b31ea0 eip = 0xc01118d1 ebp = 0xc1b31ef0 xss = 0x0018 xcs = 0x0010 eflags = 0x00010086 xds = 0x0018 xes = 0x0018 origeax = 0x = 0xc1b31e6c kdb> bt EBP EIP Function(args) 0xc1b31ef0 0xc01118d1 schedule+0x421 (0xc12e1d40, 0xa490, 0x0, 0xc12e1c00, 0x246 ) kernel .text 0xc010 0xc01114b0 0xc01118e0 0xc1b31f44 0xc0106cd9 reschedule+0x5 (0xc12e1c00) kernel .text 0xc010 0xc0106cd4 0xc0106ce0 0xc011aa52 timer_bh+0x226 kernel .text 0xc010 0xc011a82c 0xc011aa90 0xc1b31f74 0xc0117828 bh_action+0x1c (0x0) kernel .text 0xc010 0xc011780c 0xc0117844 0xc1b31f8c 0xc0117745 tasklet_hi_action+0x81 (0xc034fd60) kernel .text 0xc010 0xc01176c4 0xc0117774 0xc1b31fa4 0xc01174fc do_softirq+0x4c kernel .text 0xc010 0xc01174b0 0xc011752c 0xc1b31fbc 0xc01084d3 do_IRQ+0x9f kernel .text 0xc010 0xc0108434 0xc01084e4 kdb> lsmod Module Size modstruct Used by cls_u32 5705 0xc881b000 1 (autoclean) sch_tbf 3257 0xc8819000 3 sch_cbq13053 0xc8814000 1 nls_iso8859-1 3536 0xc8812000 1 kdb> -- Hope that it helps... Cheers, Krzysztof PS. please CC, ain't subscriber. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.5 2.4.6pre crashes
Hi, For few months I am running XFS CVS kernels (http://oss.sgi.com/projects/xfs/). Up till now i haven't faced any generic 2.4 issues. Problems began while XFS moved to 2.4.5 , same thing (i believe) i observed with both 2.4.6pre kernels. Linux-xfs people suggested to mail linux-kernel, so.. take a look please. My machine is Celeron 366 (Mendocino) 128MB RAM, PIIX4E, PDC20262, HPT366, with 6 ide disks (4 at PDC, 1 at PIIX4E and 1 at HPT366) and DM9102 Ethernet. RedHat 6.2 with some vital updates for 2.4 kernels... Sorry for not-complete backtrace (no serial console at the moment - rewritten manually). Stuff you can find below was observed on 2.4.6-pre2-xfs dated at 06/09. Machine crashed just before init run gettys (first output, no bt), the second time it crashed after being up for 3 minutes ca.. -- Scheduling in interrupt kernel BUG at sched.c:709! invalid operand: CPU:0 EIP:0010:[c0111341] EFLAGS: 00010092 eax: 001b ebx: ecx: c76a4000 edx: 0001 esi: edi: c01104f4 ebp: c12f9e04 esp: c12f9db4 ds: 0018 es: 0018 ss: 0018 Process init (pid: 1, stackpage=c12f9000) Stack c024aab4 c024ab56 02c5 c12f8000 c01104f4 c12f9e74 c12f8000 c014ffd6 c7fa9460 c6c38bc0 c12f9e24 c0150200 c12f9e74 c12f9e80 c12f8000 c014ff17 c12f8000 c0106c48 c881818c c0106c05 c76b41a0 c76b4228 Call Trace: [c01104f4] [c014ffd6] [c0150200] [c014ff17] [c0106c48] [c 881818c] [c0106c05] [c881818c] [c881818c] [c011a46c] [c0119d66] [c01171e2] [c01171 04] [c0116edc] [c0107fe8] [c0106bd8] [c0120018] [c011e983] [c011232f] [c0112c4e] [c01057 d4] [c0106af3] Code: 0f 0b 8d 65 bc 5b 5e 5f 89 ec 5d c3 8d 76 00 55 89 e5 83 ec Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing -- -- Scheduling in interrupt kernel BUG at sched.c:709! Entering kdb (current=0xc1b3, pid 1822) Oops: invalid operand due to oops @ 0xc01118d1 eax = 0x001b ebx = 0x ecx = 0xc75e2000 edx = 0x0001 esi = 0x edi = 0x0246 esp = 0xc1b31ea0 eip = 0xc01118d1 ebp = 0xc1b31ef0 xss = 0x0018 xcs = 0x0010 eflags = 0x00010086 xds = 0x0018 xes = 0x0018 origeax = 0x regs = 0xc1b31e6c kdb bt EBP EIP Function(args) 0xc1b31ef0 0xc01118d1 schedule+0x421 (0xc12e1d40, 0xa490, 0x0, 0xc12e1c00, 0x246 ) kernel .text 0xc010 0xc01114b0 0xc01118e0 0xc1b31f44 0xc0106cd9 reschedule+0x5 (0xc12e1c00) kernel .text 0xc010 0xc0106cd4 0xc0106ce0 0xc011aa52 timer_bh+0x226 kernel .text 0xc010 0xc011a82c 0xc011aa90 0xc1b31f74 0xc0117828 bh_action+0x1c (0x0) kernel .text 0xc010 0xc011780c 0xc0117844 0xc1b31f8c 0xc0117745 tasklet_hi_action+0x81 (0xc034fd60) kernel .text 0xc010 0xc01176c4 0xc0117774 0xc1b31fa4 0xc01174fc do_softirq+0x4c kernel .text 0xc010 0xc01174b0 0xc011752c 0xc1b31fbc 0xc01084d3 do_IRQ+0x9f kernel .text 0xc010 0xc0108434 0xc01084e4 kdb lsmod Module Size modstruct Used by cls_u32 5705 0xc881b000 1 (autoclean) sch_tbf 3257 0xc8819000 3 sch_cbq13053 0xc8814000 1 nls_iso8859-1 3536 0xc8812000 1 kdb -- Hope that it helps... Cheers, Krzysztof PS. please CC, ain't subscriber. - 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/
[?] __alloc_pages: 1-order allocation failed.
Hi, Here's what i've found today in logs: Feb 13 02:10:41 main kernel: __alloc_pages: 1-order allocation failed. Feb 13 02:10:42 main last message repeated 143 times Feb 13 02:10:47 main kernel: ed. Feb 13 02:10:47 main kernel: __alloc_pages: 1-order allocation failed. Feb 13 02:50:30 main syslogd 1.3-3: restart (remote reception). After that there was possibly lock-up or reboot (i don't know, when i connected to the machine it was already running). What can be possible cause of such things ? I am running 2.4.1-XFS (2001/02/10) on a Mendocino 366/128MB/VT82C596A/PDC20262. Regards, - Krzysztof PS. lkml subscribers: please reply to my email if it's possible :) - 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/
[?] __alloc_pages: 1-order allocation failed.
Hi, Here's what i've found today in logs: Feb 13 02:10:41 main kernel: __alloc_pages: 1-order allocation failed. Feb 13 02:10:42 main last message repeated 143 times Feb 13 02:10:47 main kernel: ed. Feb 13 02:10:47 main kernel: __alloc_pages: 1-order allocation failed. Feb 13 02:50:30 main syslogd 1.3-3: restart (remote reception). After that there was possibly lock-up or reboot (i don't know, when i connected to the machine it was already running). What can be possible cause of such things ? I am running 2.4.1-XFS (2001/02/10) on a Mendocino 366/128MB/VT82C596A/PDC20262. Regards, - Krzysztof PS. lkml subscribers: please reply to my email if it's possible :) - 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/
[BUG?] Unix Domain sockets in 2.4 series ?
I ain't kernel developer .. just poor little user,
but i think you might want to look at this stuff below...
I only tried that little code remotely so i do NOT know
what's system reaction on console ...
Anyway socket interface goes bye bye after this...
I tried it on 2.4.1-XFS and 2.4.0-XFS (both remotely)
and effects were exactly the same...
#include
#include
#include
#include
int main(int argc, const char* argv[])
{
int retval;
int sockets[2];
char buf[1];
retval = socketpair(PF_UNIX, SOCK_DGRAM, 0, sockets);
if (retval != 0)
{
perror("socketpair");
exit(1);
}
shutdown(sockets[0], SHUT_RDWR);
read(sockets[0], buf, 1);
}
- Krzysztof
PS.
CC reply for me, i am not subscriber of lkml
thanks :)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
[BUG?] Unix Domain sockets in 2.4 series ?
I ain't kernel developer .. just poor little user,
but i think you might want to look at this stuff below...
I only tried that little code remotely so i do NOT know
what's system reaction on console ...
Anyway socket interface goes bye bye after this...
I tried it on 2.4.1-XFS and 2.4.0-XFS (both remotely)
and effects were exactly the same...
#include stdio.h
#include unistd.h
#include sys/types.h
#include sys/socket.h
int main(int argc, const char* argv[])
{
int retval;
int sockets[2];
char buf[1];
retval = socketpair(PF_UNIX, SOCK_DGRAM, 0, sockets);
if (retval != 0)
{
perror("socketpair");
exit(1);
}
shutdown(sockets[0], SHUT_RDWR);
read(sockets[0], buf, 1);
}
- Krzysztof
PS.
CC reply for me, i am not subscriber of lkml
thanks :)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
2.4.0 (w/XFS) & reset_xmit_timer
Hi, Since 2.4.0 (from XFS CVS source tree) i get such things from kernel: Jan 13 20:55:48 main kernel: reset_xmit_timer sk=c299b9a0 1 when=0x6061, caller=c0218f88 Jan 13 20:58:09 main kernel: reset_xmit_timer sk=c49aa040 1 when=0x594b, caller=c0218f88 Jan 13 21:01:30 main kernel: reset_xmit_timer sk=c0a25040 1 when=0x2f24, caller=c0218f88 Jan 13 21:22:33 main kernel: reset_xmit_timer sk=c6ce99a0 1 when=0x337a, caller=c0218f88 Jan 13 21:32:15 main kernel: reset_xmit_timer sk=c2fb5680 1 when=0x58ef, caller=c0218f88 Jan 13 21:34:49 main kernel: reset_xmit_timer sk=c46bccc0 1 when=0x2fcf, caller=c0218f88 Jan 13 21:34:52 main kernel: reset_xmit_timer sk=c2a949a0 1 when=0x3724, caller=c0218f88 Jan 13 21:36:42 main kernel: reset_xmit_timer sk=c49aa040 1 when=0x8fbf, caller=c0218f88 Jan 13 21:41:42 main kernel: reset_xmit_timer sk=c49aa040 1 when=0x4c4e, caller=c0218f88 Jan 13 21:45:51 main kernel: reset_xmit_timer sk=c398f360 1 when=0x552b, caller=c0218f88 Jan 13 21:50:38 main kernel: reset_xmit_timer sk=c7c979a0 1 when=0x3caf, caller=c0218f88 Jan 13 21:50:38 main kernel: reset_xmit_timer sk=c7c979a0 1 when=0x38d3, caller=c0218f88 Jan 13 21:50:38 main kernel: reset_xmit_timer sk=c7c979a0 1 when=0x3432, caller=c0218f88 On 2.4.0-test13-pre3 (patched with XFS patch from SGI) there was _NO_ such things... I ain't kernel developer, so i have no idea of possible cause... My 2.4.0-t13-pre3 and 2.4.0 kernel configs does _NOT_ practically differ. I use DM9102 ethernet driver together with QoS (CBQ & TBF queues and U32 classifier). I didn't find this problem related stuff in LKML archives, so i decided to write this down here... - Krzysztof PS sorry for my english - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
2.4.0 (w/XFS) reset_xmit_timer
Hi, Since 2.4.0 (from XFS CVS source tree) i get such things from kernel: Jan 13 20:55:48 main kernel: reset_xmit_timer sk=c299b9a0 1 when=0x6061, caller=c0218f88 Jan 13 20:58:09 main kernel: reset_xmit_timer sk=c49aa040 1 when=0x594b, caller=c0218f88 Jan 13 21:01:30 main kernel: reset_xmit_timer sk=c0a25040 1 when=0x2f24, caller=c0218f88 Jan 13 21:22:33 main kernel: reset_xmit_timer sk=c6ce99a0 1 when=0x337a, caller=c0218f88 Jan 13 21:32:15 main kernel: reset_xmit_timer sk=c2fb5680 1 when=0x58ef, caller=c0218f88 Jan 13 21:34:49 main kernel: reset_xmit_timer sk=c46bccc0 1 when=0x2fcf, caller=c0218f88 Jan 13 21:34:52 main kernel: reset_xmit_timer sk=c2a949a0 1 when=0x3724, caller=c0218f88 Jan 13 21:36:42 main kernel: reset_xmit_timer sk=c49aa040 1 when=0x8fbf, caller=c0218f88 Jan 13 21:41:42 main kernel: reset_xmit_timer sk=c49aa040 1 when=0x4c4e, caller=c0218f88 Jan 13 21:45:51 main kernel: reset_xmit_timer sk=c398f360 1 when=0x552b, caller=c0218f88 Jan 13 21:50:38 main kernel: reset_xmit_timer sk=c7c979a0 1 when=0x3caf, caller=c0218f88 Jan 13 21:50:38 main kernel: reset_xmit_timer sk=c7c979a0 1 when=0x38d3, caller=c0218f88 Jan 13 21:50:38 main kernel: reset_xmit_timer sk=c7c979a0 1 when=0x3432, caller=c0218f88 On 2.4.0-test13-pre3 (patched with XFS patch from SGI) there was _NO_ such things... I ain't kernel developer, so i have no idea of possible cause... My 2.4.0-t13-pre3 and 2.4.0 kernel configs does _NOT_ practically differ. I use DM9102 ethernet driver together with QoS (CBQ TBF queues and U32 classifier). I didn't find this problem related stuff in LKML archives, so i decided to write this down here... - Krzysztof PS sorry for my english - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
