Re: Kernel message: BUG: Bad page state in process kworker
On Sat, Mar 13, 2021 at 03:01:45AM -0500, Michael Grant wrote: > > I'd say it is a Linode problem, unless you run custom kernel modules. > > It looks like a "memory" corruption to me and since it is virtualized > > system, > > you should check if host system is ok. > > Memory in quotes because this issue could be also related to a storage > > sub-system (local or network attached) of the host or VM. > > I'm definitely not running a custom kernel. You do run non-Debian kernel. It says so in your dmesg: kworker/0:3 Tainted: GB 5.10.13-x86_64-linode141 #1 Reco
Re: Kernel message: BUG: Bad page state in process kworker
> I'd say it is a Linode problem, unless you run custom kernel modules. > It looks like a "memory" corruption to me and since it is virtualized system, > you should check if host system is ok. > Memory in quotes because this issue could be also related to a storage > sub-system (local or network attached) of the host or VM. I'm definitely not running a custom kernel. They live migrated this linode to a new physical machine and still getting these errors so I don't think it's a h/w issue. It seems to be a qemu issue to me but I am not very familiar with qemu. The fact that they live migrated it does seem to imply it's all part of the same virtualization system, probably same qemu, which would make sense that it didn't fix the error. I'd like to know if anyone else is seeing this who is using linode and has recently been migrated to their new metal. signature.asc Description: PGP signature
Re: Kernel message: BUG: Bad page state in process kworker
On 13.03.2021 11:31, Michael Grant wrote: I'm seeing lots of errors like this in my kern.log on 2 of 3 of my deban Linodes running testing on Linode's provided kerne 5.10.13. Is this a problem in Debian or is this a Linode issue? Mar 12 19:32:18 strange kernel: [10849.820363] BUG: Bad page state in process kworker/0:3 pfn:10902f Mar 12 19:32:18 strange kernel: [10849.825374] page:edbc1187 refcount:-1 mapcount:0 mapping: index:0x0 pfn:0x10902f Mar 12 19:32:18 strange kernel: [10849.827665] flags: 0x200() Mar 12 19:32:18 strange kernel: [10849.828894] raw: 0200 dead0100 dead0122 Mar 12 19:32:18 strange kernel: [10849.830817] raw: 0011 Mar 12 19:32:18 strange kernel: [10849.832758] page dumped because: nonzero _refcount Mar 12 19:32:18 strange kernel: [10849.834141] Modules linked in: Mar 12 19:32:18 strange kernel: [10849.835229] CPU: 0 PID: 769 Comm: kworker/0:3 Tainted: GB 5.10.13-x86_64-linode141 #1 Mar 12 19:32:18 strange kernel: [10849.837423] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014 Mar 12 19:32:18 strange kernel: [10849.840005] Workqueue: mm_percpu_wq drain_local_pages_wq Mar 12 19:32:18 strange kernel: [10849.841538] Call Trace: Mar 12 19:32:18 strange kernel: [10849.842620] dump_stack+0x6d/0x88 Mar 12 19:32:18 strange kernel: [10849.843813] bad_page.cold.119+0x63/0x93 Mar 12 19:32:18 strange kernel: [10849.845096] free_pcppages_bulk+0x18e/0x6a0 Mar 12 19:32:18 strange kernel: [10849.846423] drain_pages_zone+0x41/0x50 Mar 12 19:32:18 strange kernel: [10849.847740] drain_pages+0x3c/0x50 Mar 12 19:32:18 strange kernel: [10849.848956] drain_local_pages_wq+0xe/0x10 Mar 12 19:32:18 strange kernel: [10849.850282] process_one_work+0x1fb/0x390 Mar 12 19:32:18 strange kernel: [10849.851579] ? process_one_work+0x390/0x390 Mar 12 19:32:18 strange kernel: [10849.852929] worker_thread+0x221/0x3e0 Mar 12 19:32:18 strange kernel: [10849.854159] ? process_one_work+0x390/0x390 Mar 12 19:32:18 strange kernel: [10849.855648] kthread+0x116/0x130 Mar 12 19:32:18 strange kernel: [10849.857066] ? kthread_park+0x80/0x80 Mar 12 19:32:18 strange kernel: [10849.858424] ret_from_fork+0x22/0x30 I'd say it is a Linode problem, unless you run custom kernel modules. It looks like a "memory" corruption to me and since it is virtualized system, you should check if host system is ok. Memory in quotes because this issue could be also related to a storage sub-system (local or network attached) of the host or VM. -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Kernel message: BUG: Bad page state in process kworker
I'm seeing lots of errors like this in my kern.log on 2 of 3 of my deban Linodes running testing on Linode's provided kerne 5.10.13. Is this a problem in Debian or is this a Linode issue? Mar 12 19:32:18 strange kernel: [10849.820363] BUG: Bad page state in process kworker/0:3 pfn:10902f Mar 12 19:32:18 strange kernel: [10849.825374] page:edbc1187 refcount:-1 mapcount:0 mapping: index:0x0 pfn:0x10902f Mar 12 19:32:18 strange kernel: [10849.827665] flags: 0x200() Mar 12 19:32:18 strange kernel: [10849.828894] raw: 0200 dead0100 dead0122 Mar 12 19:32:18 strange kernel: [10849.830817] raw: 0011 Mar 12 19:32:18 strange kernel: [10849.832758] page dumped because: nonzero _refcount Mar 12 19:32:18 strange kernel: [10849.834141] Modules linked in: Mar 12 19:32:18 strange kernel: [10849.835229] CPU: 0 PID: 769 Comm: kworker/0:3 Tainted: GB 5.10.13-x86_64-linode141 #1 Mar 12 19:32:18 strange kernel: [10849.837423] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014 Mar 12 19:32:18 strange kernel: [10849.840005] Workqueue: mm_percpu_wq drain_local_pages_wq Mar 12 19:32:18 strange kernel: [10849.841538] Call Trace: Mar 12 19:32:18 strange kernel: [10849.842620] dump_stack+0x6d/0x88 Mar 12 19:32:18 strange kernel: [10849.843813] bad_page.cold.119+0x63/0x93 Mar 12 19:32:18 strange kernel: [10849.845096] free_pcppages_bulk+0x18e/0x6a0 Mar 12 19:32:18 strange kernel: [10849.846423] drain_pages_zone+0x41/0x50 Mar 12 19:32:18 strange kernel: [10849.847740] drain_pages+0x3c/0x50 Mar 12 19:32:18 strange kernel: [10849.848956] drain_local_pages_wq+0xe/0x10 Mar 12 19:32:18 strange kernel: [10849.850282] process_one_work+0x1fb/0x390 Mar 12 19:32:18 strange kernel: [10849.851579] ? process_one_work+0x390/0x390 Mar 12 19:32:18 strange kernel: [10849.852929] worker_thread+0x221/0x3e0 Mar 12 19:32:18 strange kernel: [10849.854159] ? process_one_work+0x390/0x390 Mar 12 19:32:18 strange kernel: [10849.855648] kthread+0x116/0x130 Mar 12 19:32:18 strange kernel: [10849.857066] ? kthread_park+0x80/0x80 Mar 12 19:32:18 strange kernel: [10849.858424] ret_from_fork+0x22/0x30 signature.asc Description: PGP signature
Re: [solved] Re: Kernel message: `base address not set' at boot
On 2015-07-08, Rodolfo Medina rodolfo.med...@gmail.com wrote: It seems it is `0x6000': with it, the message didn't appear any more. What were the consequences of the message appearing (besides the message appearing)? Actually, none at all. But the start off has sometimes its own form of `aesthetics'. So you solved the Case of the Appearing Message, by Artie C. Doyle. Rodolfo -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmpq5pc.329.cu...@einstein.electron.org
Re: [solved] Re: Kernel message: `base address not set' at boot
Curt cu...@free.fr writes: On 2015-07-07, Rodolfo Medina rodolfo.med...@gmail.com wrote: Thanks, I will. The file should be modesetting.conf. But how do I know what the appropriate parameter for `0xaddr' will be? Rodolfo It seems it is `0x6000': with it, the message didn't appear any more. What were the consequences of the message appearing (besides the message appearing)? Actually, none at all. But the start off has sometimes its own form of `aesthetics'. Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87a8v72dom@gmail.com
Re: [solved] Re: Kernel message: `base address not set' at boot
Curt cu...@free.fr writes: On 2015-07-08, Rodolfo Medina rodolfo.med...@gmail.com wrote: It seems it is `0x6000': with it, the message didn't appear any more. What were the consequences of the message appearing (besides the message appearing)? Actually, none at all. But the start off has sometimes its own form of `aesthetics'. So you solved the Case of the Appearing Message, by Artie C. Doyle. It probably delayed the booting a few seconds, also. Rodolfo Medina -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87bnfm23s5@gmail.com
Re: [solved] Re: Kernel message: `base address not set' at boot
On 2015-07-07, Rodolfo Medina rodolfo.med...@gmail.com wrote: Thanks, I will. The file should be modesetting.conf. But how do I know what the appropriate parameter for `0xaddr' will be? Rodolfo It seems it is `0x6000': with it, the message didn't appear any more. What were the consequences of the message appearing (besides the message appearing)? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmppmcm.329.cu...@einstein.electron.org
[solved] Re: Kernel message: `base address not set' at boot
Rodolfo Medina rodolfo.med...@gmail.com writes: Darac Marjal mailingl...@darac.org.uk writes: On Tue, Jul 07, 2015 at 01:23:01PM +0100, Rodolfo Medina wrote: Hi all. On my old Pentiium III, at boot the following message appears: via686a :00:04.4: base address not set - upgrade BIOS or use force_addr=0xaddr How can I eliminate it? From the Kernel Documentation: https://www.kernel.org/doc/Documentation/hwmon/via686a Module Parameters - force_addr=0xaddr Set the I/O base address. Useful for boards that don't set the address in the BIOS. Look for a BIOS upgrade before resorting to this. Does not do a PCI force; the via686a must still be present in lspci. Don't use this unless the driver complains that the base address is not set. Example: 'modprobe via686a force_addr=0x6000' So, if you need to set this (that is, if a BIOS upgrade is unavailable or does not fix things), create a file /etc/modprobe.d/*.conf, with the contents options via686a force_addr=0xaddr (where 0xaddr is an appropriate value). Thanks, I will. The file should be modesetting.conf. But how do I know what the appropriate parameter for `0xaddr' will be? Rodolfo It seems it is `0x6000': with it, the message didn't appear any more. Thanks!, Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/871tgjlo44.fsf...@gmail.com
Kernel message: `base address not set' at boot
Hi all. On my old Pentiium III, at boot the following message appears: via686a :00:04.4: base address not set - upgrade BIOS or use force_addr=0xaddr How can I eliminate it? Thanks for any help, Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/871tgkp36i@gmail.com
Re: Kernel message: `base address not set' at boot
On Tue, Jul 07, 2015 at 01:23:01PM +0100, Rodolfo Medina wrote: Hi all. On my old Pentiium III, at boot the following message appears: via686a :00:04.4: base address not set - upgrade BIOS or use force_addr=0xaddr How can I eliminate it? From the Kernel Documentation: https://www.kernel.org/doc/Documentation/hwmon/via686a Module Parameters - force_addr=0xaddr Set the I/O base address. Useful for boards that don't set the address in the BIOS. Look for a BIOS upgrade before resorting to this. Does not do a PCI force; the via686a must still be present in lspci. Don't use this unless the driver complains that the base address is not set. Example: 'modprobe via686a force_addr=0x6000' So, if you need to set this (that is, if a BIOS upgrade is unavailable or does not fix things), create a file /etc/modprobe.d/*.conf, with the contents options via686a force_addr=0xaddr (where 0xaddr is an appropriate value). Thanks for any help, Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/871tgkp36i@gmail.com -- For more information, please reread. signature.asc Description: Digital signature
Re: Kernel message: `base address not set' at boot
Darac Marjal mailingl...@darac.org.uk writes: On Tue, Jul 07, 2015 at 01:23:01PM +0100, Rodolfo Medina wrote: Hi all. On my old Pentiium III, at boot the following message appears: via686a :00:04.4: base address not set - upgrade BIOS or use force_addr=0xaddr How can I eliminate it? From the Kernel Documentation: https://www.kernel.org/doc/Documentation/hwmon/via686a Module Parameters - force_addr=0xaddr Set the I/O base address. Useful for boards that don't set the address in the BIOS. Look for a BIOS upgrade before resorting to this. Does not do a PCI force; the via686a must still be present in lspci. Don't use this unless the driver complains that the base address is not set. Example: 'modprobe via686a force_addr=0x6000' So, if you need to set this (that is, if a BIOS upgrade is unavailable or does not fix things), create a file /etc/modprobe.d/*.conf, with the contents options via686a force_addr=0xaddr (where 0xaddr is an appropriate value). Thanks, I will. The file should be modesetting.conf. But how do I know what the appropriate parameter for `0xaddr' will be? Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87twtgnkxd@gmail.com
Re: Dropped Connections and Failed to create cgroup nnnn: -17 Kernel Message When vsftpd Spawning a New Process
Hi, just in case anyone comes across this thread: I have filed a bug report for this issue under #639453. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639453 Dirk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e58d769.40...@weinhardt.biz
Dropped Connections and Failed to create cgroup nnnn: -17 Kernel Message When vsftpd Spawning a New Process
Hello list,
I am experiencing the following issue with a Debian squeeze based server
and the most recent squeeze-backports kernel:
I realized that some vstfpd daemons randomly drop connections (sending a
FIN right after the initial TCP hand shake was completed). Furthermore,
a Failed to create cgroup : -17 message is logged by the kernel.
Furthermore, I am observing a steadily increasing number of directories
named like pids being created in the root of the cgroup virtual
filesystem (mounted at /cgroup). For each connection attempt to a vsftpd
daemon a new directory is created. Those directories seem to be never
deleted. After a few days of uptime there are about 7,500 directories
while there constantly are only about 150 processes running (more or
less idling, this server usually has low load).
When stracing vsftpd the call that fails seems to be this one (full
output below):
clone(child_stack=0, flags=0x2800|SIGCHLD) = -1 EEXIST (File exists)
Which makes me believe that those zombie directories in /cgroup might
conflict with the new pid . The longer the server is up the more likely
it becomes that connections are dropped.
Side note: The affected vsftpd daemons are running on a server that also
is hosting an LXC-based virtual server. I have experienced a steadily
increasing soft IRQ load on the server while a cgroup virtual filesystem
being mounted. I have upgraded to the recent squeeze-backports kernel
which seems not to suffer from this soft IRQ issue. vsftpd daemons
running inside LXC containers do not drop connections.
Anyone experiencing a similar issue or has any suggestions? When
reporting a bug for this issue would this need to be reported against
the kernel package?
Below is some information I thought might be useful. If required, I will
gladly provide any additional information.
Cheers,
Dirk
I am using vsftpd 2.3.2-3 which AFAIK is the most recent version
available from the squeeze and squeeze-backports repositories.
uname -a output:
Linux x 2.6.39-bpo.2-amd64 #1 SMP Tue Jul 26 10:35:23 UTC 2011
x86_64 GNU/Linux
strace vsftpd /etc/vsftp.conf output (successful connection attempt):
alarm(1)= 0
rt_sigreturn(0x1) = -1 EINTR (Interrupted system call)
alarm(0)= 1
wait4(-1, NULL, WNOHANG, NULL) = 6385
wait4(-1, NULL, WNOHANG, NULL) = -1 ECHILD (No child processes)
accept(3, {sa_family=AF_INET, sin_port=htons(46631),
sin_addr=inet_addr(xxx.xxx.xxx.xxx)}, [16]) = 4
clone(child_stack=0, flags=0x2800|SIGCHLD) = 6387
close(4)= 0
accept(3, 0x7fffc3ecdf70, [28]) = ? ERESTARTSYS (To be restarted)
strace vsftpd /etc/vsftp.conf output (failed connection attempt):
alarm(1)= 0
rt_sigreturn(0x1) = -1 EINTR (Interrupted system call)
alarm(0)= 1
wait4(-1, NULL, WNOHANG, NULL) = 6387
wait4(-1, NULL, WNOHANG, NULL) = -1 ECHILD (No child processes)
accept(3, {sa_family=AF_INET, sin_port=htons(47917),
sin_addr=inet_addr(xxx.xxx.xxx.xxx)}, [16]) = 4
clone(child_stack=0, flags=0x2800|SIGCHLD) = -1 EEXIST (File exists)
close(4)= 0
accept(33, 0x7fffc3ecdf70, [28]) = ? ERESTARTSYS (To be restarted)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e54188c.6060...@weinhardt.biz
Re: funky kernel message from syslogd
On Thu, Apr 22, 2010 at 07:24:38PM -0400, Nick Lidakis wrote: This popped up in one of my xterms after my Thinkpad came out of hibernation today. The machine has beeped a few times as this message was repeated. Does not sound good. Call Trace? That's, like, bad? Right? Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.069917] Oops: [#1] SMP Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.069923] last sysfs file: /sys/devices/virtual/misc/cpu_dma_latency/uevent Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070112] Process udev-acl.ck (pid: 17300, ti=df3a8000 task=f47e61c0 task.ti=df3a8000) Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070117] Stack: Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070164] Call Trace: Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070244] Code: c7 40 28 01 00 00 00 89 d0 5a 5b 5e 5f 5d c3 55 b9 00 10 00 00 57 56 53 83 ec 14 89 14 24 89 44 24 04 8b 42 0c 8b 68 58 8b 45 08 8b 78 14 89 d0 ba d4 c7 4a c1 83 c0 08 e8 1f d9 fc ff 85 c0 89 Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070322] EIP: [c10f285b] sysfs_open_file+0x1c/0x259 SS:ESP 0068:df3a9e7c Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070333] CR2: 0014 You'll probably find the complete message in /var/log/kern.log . -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best tzaf...@debian.org|| friend -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100425042715.gy16...@pear.tzafrir.org.il
Re: funky kernel message from syslogd
On Thu, 22 Apr 2010 19:24:38 -0400, Nick Lidakis wrote: This popped up in one of my xterms after my Thinkpad came out of hibernation today. The machine has beeped a few times as this message was repeated. Does not sound good. Call Trace? That's, like, bad? Right? Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.069917] Oops: [#1] SMP (...) That is a kernel Oops, not a good sign :-( I would report it (including full log information about the oops) into Debian bug tracking system. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.04.23.16.24...@gmail.com
funky kernel message from syslogd
This popped up in one of my xterms after my Thinkpad came out of hibernation today. The machine has beeped a few times as this message was repeated. Does not sound good. Call Trace? That's, like, bad? Right? Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.069917] Oops: [#1] SMP Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.069923] last sysfs file: /sys/devices/virtual/misc/cpu_dma_latency/uevent Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070112] Process udev-acl.ck (pid: 17300, ti=df3a8000 task=f47e61c0 task.ti=df3a8000) Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070117] Stack: Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070164] Call Trace: Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070244] Code: c7 40 28 01 00 00 00 89 d0 5a 5b 5e 5f 5d c3 55 b9 00 10 00 00 57 56 53 83 ec 14 89 14 24 89 44 24 04 8b 42 0c 8b 68 58 8b 45 08 8b 78 14 89 d0 ba d4 c7 4a c1 83 c0 08 e8 1f d9 fc ff 85 c0 89 Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070322] EIP: [c10f285b] sysfs_open_file+0x1c/0x259 SS:ESP 0068:df3a9e7c Message from sysl...@thinkpad at Apr 22 18:52:20 ... kernel:[42926.070333] CR2: 0014 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100422232438.ga25...@phobos
RE: Debian Lenny + Grub2 + kernel message log capturing
Sun, 11 Apr 2010 00:20:54 -0400 Hello, I was hoping to get some feedback or tips on how to setup a PCI serial card (not onboard) for kernel message log capturing. I am using Debian Lenny x64 with the grub2 bootloader. This might sound like an easy question, but does the Linux kernel module have to be compiled with the running kernel in order to log messages at boot time? I mean obviously the driver is required to be loaded in Debian GNU/Linux when the serial/com device is used in conjunction with /dev/ttyD[01]. Mainly I am asking if one needs to build the mcs9865-serial.ko (kernel module) against the kernel source for the running kernel in order to log kernel message during boot time or does grub implement a generic driver to capture the kernel message? The mcs9865 source code is here . It does not compile for me against the 2.6.32-4-xen-amd64 kernel from the Sid repositories. I have installed both the appropriate linux-kernel and linux-headers package for the 2.6.32-4-xen-amd64 kernel. Attached is also the output of the make command on the mcs9865 source code. I have found a website providing patches for the chip on the PCI serial card I am using at: http://izto.org/mcs9865/ Does Debian not include drivers for serial cards in any packages or would these drivers be considered non-free? Thanks. -M Videos that have everyone talking! Now also in HD! MSN.ca Video. _ Hotmail Messenger are available on your phone. Try now. http://go.microsoft.com/?linkid=9724461 make.output Description: Binary data
Debian Lenny + Grub2 + kernel message log capturing
Hello, I was hoping to get some feedback or tips on how to setup a PCI serial card (not onboard) for kernel message log capturing. I am using Debian Lenny x64 with the grub2 bootloader. This might sound like an easy question, but does the Linux kernel module have to be compiled with the running kernel in order to log messages at boot time? I mean obviously the driver is required to be loaded in Debian GNU/Linux when the serial/com device is used in conjunction with /dev/ttyD[01]. I have found a website providing patches for the chip on the PCI serial card I am using at: http://izto.org/mcs9865/ Does Debian not include drivers for serial cards in any packages or would these drivers be considered non-free? Thanks. -M _ Videos that have everyone talking! Now also in HD! http://go.microsoft.com/?linkid=9724465
Re: Kernel message
Yves Rutschle a écrit : C'est clair. La RAM est le premier élement que je testerais, mais ça peut être un tas d'autre trucs. Merci a tous pour votre participation, un memtest plus tard :-| soucis de Ram Bref sachant que sur le poste, j'ai un barette (512 Mo) sur laquelle je ne peux acceder, et une autre que je peux oter ... Reste a croiser les doigts pour que la defectueuse soit celle accessible... ++ -- Alexandre Mackow Jabber : [EMAIL PROTECTED] -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel message
Yves Rutschle a écrit : On Mon, Nov 12, 2007 at 09:27:13AM +0100, Alexandre Mackow wrote: Bref sachant que sur le poste, j'ai un barette (512 Mo) sur laquelle je ne peux acceder, et une autre que je peux oter ... Reste a croiser les doigts pour que la defectueuse soit celle accessible... Je n'ai jamais essayé, mais on doit pouvoir spécifier au noyau quelle partie de la RAM utiliser avec l'option memmap. C'est certainement moins satisfaisant que de pouvoir remplacer la RAM defectueuse, mais c'est mieux que de devoir jeter la machine... Y. Merci pour cette precision, je ferai le test sur la barette intégré, si c'est elle qui est defectueuse, je regarderai de ce coté Hors de question de jeter cette machine, elle ne m'a que trop rendu service ;-) et si les freeze sont genant, il n'en sont pas bloquant sur cette machine... Encore merci. ++ -- Alexandre Mackow Jabber : [EMAIL PROTECTED] -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel message
On Mon, Nov 12, 2007 at 09:27:13AM +0100, Alexandre Mackow wrote: Bref sachant que sur le poste, j'ai un barette (512 Mo) sur laquelle je ne peux acceder, et une autre que je peux oter ... Reste a croiser les doigts pour que la defectueuse soit celle accessible... Je n'ai jamais essayé, mais on doit pouvoir spécifier au noyau quelle partie de la RAM utiliser avec l'option memmap. C'est certainement moins satisfaisant que de pouvoir remplacer la RAM defectueuse, mais c'est mieux que de devoir jeter la machine... Y. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel message
Yves Rutschle a écrit : On Thu, Nov 08, 2007 at 10:23:05PM +0100, Leon Gray wrote: Arrêtez moi si je dis une bêtise mais à ma connaissance les opcode ne sont pas stockés en RAM (heureusement d'ailleurs), il est donc possible que le problème ne vienne pas de la RAM. L'opcode est la partie 'opération' d'une instruction. On charge le programme (suite d'instructions) en RAM. Puis on exécute en relisant les instructions en RAM. En conclusion, si la RAM s'avère bonne, essayer de voir si le disque dur ne fatigue pas (les opcode sont lus dans une ROM en général), sinon penser à la carte mère (qui sait interprèter les opcode lus)... C'est clair. La RAM est le premier élement que je testerais, mais ça peut être un tas d'autre trucs. J'ai dû mal m'exprimer car au final on dit la même chose ;). Si on charge le programme en RAM c'est donc que l'opcode n'est pas stocké en RAM au moment où j'appuie sur le bouton on de ma machine mais bien dans une mémoire morte. Ensuite cet opcode peut être lu via la RAM ou bien directement... Bref, tout ça pour dire que ça peut-être la RAM comme ça peut-être un autre composant. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel message
Salut à tous, j'ai un petit portable qui me rend bien service et qui, matériellement (amha) me convient parfaiatement pour l'usage que j'en ai (PIII 1Ghz et 1 Go de Ram). J'ai toujours été confronté a des soucis de stabilité sur cette machine (Dell d500 il me semble ), bloquage au demarrage, fermeture brutale de Firefox et il fige de temps à autre. Encore ce matin, je me mets a recupèrer le 1er Dvd de Lenny en ssh, et je m'apercois de message à l'ecran (cf en bas de mon message). Ne comprenant que mal l'hexadecimal :-| D'ou pensez vous que mon problème puisse venir? Sachant que j'ai installé dessus plusieurs distrib (Fedora, opensuse et Debian), plusieurs noyaux pour avoir toujours les memes soucis. Par avance merci a qui pourra m'aiguiller. ++ laptop kernel: [ cut here ] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:50 2007 ... laptop kernel: invalid opcode: [#1] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:50 2007 ... laptop kernel: SMP Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: CPU:0 Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: EIP:0060:[f89768f3]Not tainted VLI Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: EFLAGS: 00210292 (2.6.22-2-686 #1) Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: EIP is at do_get_write_access+0x21b/0x45d [jbd] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: eax: 0084 ebx: c2784198 ecx: 00200082 edx: 0020 Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: esi: f0030d80 edi: ebp: ea7fc788 esp: f2e7fa9c Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: Process wget (pid: 3656, ti=f2e7e000 task=f7951580 task.ti=f2e7e000) Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: Stack: f897c93d f897c619 f897c928 026c f897cb38 0001 f7c9d3ec Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel:dfc25200 eb07b000 f7c9d3ec eb075cf8 f8a1c229 f8a197fa 1000 dfd63e80 Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel:f7c9d3ec f7c9d3ec c2784198 f89776bb f2e7fb14 f7c9d3ec ea7fc788 Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: Call Trace: Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a197fa] __ext3_journal_dirty_metadata+0x16/0x3a [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f89776bb] journal_get_undo_access+0x26/0xfc [jbd] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a19920] __ext3_journal_get_undo_access+0x16/0x3a [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a0e8fc] ext3_mark_inode_dirty+0x20/0x27 [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a0bb29] ext3_try_to_allocate_with_rsv+0x3d/0x445 [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a0b1cc] read_block_bitmap+0x2f/0x61 [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [c018531f] __getblk+0x23/0x27a Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a0c105] ext3_new_blocks+0x1d4/0x5be [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [c0174df3] do_select+0x39f/0x3bc Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a0ead4] ext3_get_branch+0x79/0xcb [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a0efce] ext3_get_blocks_handle+0x3b6/0x817 [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a0f72f] ext3_get_block+0xba/0xd0 [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [c0185bc9] __block_prepare_write+0x199/0x447 Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8976f28] journal_start+0xaf/0xdd [jbd] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [c0185e99] block_prepare_write+0x22/0x30 Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a0f675] ext3_get_block+0x0/0xd0 [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a10a3f] ext3_prepare_write+0x96/0x151 [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [f8a0f675] ext3_get_block+0x0/0xd0 [ext3] Message from [EMAIL PROTECTED] at Thu Nov 8 12:43:51 2007 ... laptop kernel: [c0150320]
Re: Kernel message
On Thu, Nov 08, 2007 at 03:28:55PM +0100, Alexandre Mackow wrote: Salut à tous, Bonjour, J'ai toujours été confronté a des soucis de stabilité sur cette machine (Dell d500 il me semble ), bloquage au demarrage, fermeture brutale de Firefox et il fige de temps à autre. Il faut déjà vérifier qu'il n'y a pas de problèmes de RAM. memtest86 peut aider. http://packages.debian.org/etch/memtest86 -- Nicolas -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel message
On Thu, Nov 08, 2007 at 03:28:55PM +0100, Alexandre Mackow wrote: laptop kernel: invalid opcode: [#1] Je commencerais par tester la RAM (avec par exemple RescueSystemCD, qui contient memtest86). Y. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel message
Alexandre Mackow a écrit : Oki merci pour vis reponses, memetest installé je ferai le test ce soir... pfff la RAM ca coute la peau des fesses pour ces bidules Salut, Des fois le fait d'enlever puis de remettre les barrettes résout le problème. Les connecteurs de ram de portable sont moins fiables. Un Memtest te le dira. @+ Sil -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel message
Nicolas KOWALSKI a écrit : On Thu, Nov 08, 2007 at 03:28:55PM +0100, Alexandre Mackow wrote: Salut à tous, Bonjour, J'ai toujours été confronté a des soucis de stabilité sur cette machine (Dell d500 il me semble ), bloquage au demarrage, fermeture brutale de Firefox et il fige de temps à autre. Il faut déjà vérifier qu'il n'y a pas de problèmes de RAM. memtest86 peut aider. http://packages.debian.org/etch/memtest86 Oki merci pour vis reponses, memetest installé je ferai le test ce soir... pfff la RAM ca coute la peau des fesses pour ces bidules ++ -- Alexandre Mackow Jabber : [EMAIL PROTECTED] -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel message
On Thu, Nov 08, 2007 at 10:23:05PM +0100, Leon Gray wrote: Arrêtez moi si je dis une bêtise mais à ma connaissance les opcode ne sont pas stockés en RAM (heureusement d'ailleurs), il est donc possible que le problème ne vienne pas de la RAM. L'opcode est la partie 'opération' d'une instruction. On charge le programme (suite d'instructions) en RAM. Puis on exécute en relisant les instructions en RAM. En conclusion, si la RAM s'avère bonne, essayer de voir si le disque dur ne fatigue pas (les opcode sont lus dans une ROM en général), sinon penser à la carte mère (qui sait interprèter les opcode lus)... C'est clair. La RAM est le premier élement que je testerais, mais ça peut être un tas d'autre trucs. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel message
Yves Rutschle a écrit : On Thu, Nov 08, 2007 at 03:28:55PM +0100, Alexandre Mackow wrote: laptop kernel: invalid opcode: [#1] Je commencerais par tester la RAM (avec par exemple RescueSystemCD, qui contient memtest86). Y. Bonjour, Arrêtez moi si je dis une bêtise mais à ma connaissance les opcode ne sont pas stockés en RAM (heureusement d'ailleurs), il est donc possible que le problème ne vienne pas de la RAM. En conclusion, si la RAM s'avère bonne, essayer de voir si le disque dur ne fatigue pas (les opcode sont lus dans une ROM en général), sinon penser à la carte mère (qui sait interprèter les opcode lus)... -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel message
Le 13825ième jour après Epoch, Leon Gray écrivait: Bonjour, Arrêtez moi si je dis une bêtise STOP ... mais à ma connaissance les opcode ne sont pas stockés en RAM (heureusement d'ailleurs), STOPP ... il est donc possible que le problème ne vienne pas de la RAM. Oui. Au même titre que faux = vrai En conclusion, si la RAM s'avère bonne, essayer de voir si le disque dur ne fatigue pas Oui aussi. (les opcode sont lus dans une ROM en général), ou pas... sinon penser à la carte mère (qui sait interprèter les opcode lus)... STOOP... Dans le message kernel en question (arrêtez-moi si je dis une bêtise), l'opcode est une instruction processeur. Du coup, on peut dire que partout où le processeur peut lire, il va y avoir des opcodes ou des datas. En ROM (comme le bios) ou en RAM (comme les programmes ou notre OS préféré). En tout état de cause, ça peut venir de tout plein beaucoup de causes, genre erreurs RAM, (EP)ROM abîmée, erreurs de lecture disque, drivers de périphs buggués, toussa toussa... Même les rayons cosmiques ont leurs mots à dire à ce niveau. Mais c'est rare quand c'est systématique. Ou alors, il est sur MIR (ah, non) ou sur ISS, ou pire ya un rayon cosmique particulier qui lui en veut spécialement (rare). PS: Ben quoi, c'est presque vendredi, non?
Kernel message
Bonjour, sur un Toshiba tecra 8000 avec Debian etch, j'ai depuis hier un message qui s'affiche en mode console : parport0: FIFO is stuck parport0: BUSY timeout (1) in compat_write_block_pio DMA write timed out Je viens de chercher sur Google mais sans grands résultats. Quelqu'un a -t-il une quelconque info ou source d'info sur ce message? Merci Philippe -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel message logs - should I be worried?
I am using debian testing 2.6.5-1-686-smp kernel. In /var/log/kern.log, I see the following messages. May 22 12:03:05 kusumanchi kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) May 22 12:03:05 kusumanchi kernel: apm: disabled - APM is not SMP safe. May 22 12:03:05 kusumanchi kernel: 0: NVRM: AGPGART: unable to retrieve symbol table May 22 12:07:39 kusumanchi kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) May 22 12:07:39 kusumanchi kernel: apm: disabled - APM is not SMP safe. May 22 12:07:39 kusumanchi kernel: 0: NVRM: AGPGART: unable to retrieve symbol table May 22 14:47:44 kusumanchi kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) May 22 14:47:44 kusumanchi kernel: apm: disabled - APM is not SMP safe. May 22 14:47:45 kusumanchi kernel: 1: NVRM: AGPGART: unable to retrieve symbol table Should I be worried? If so how can I get rid of them? thanks raju -- Home page: http://www.people.cornell.edu/pages/kk288/index.html Fluid's group: http://groups.yahoo.com/group/flumech/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel message error
Bonjour, que signifie le message d'erreur suivant sur woody ? kernel: VFS: file-max limit 4096 reached merci -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel message error
On Wed, 10 Apr 2002, Schmitt georges wrote: Bonjour, que signifie le message d'erreur suivant sur woody ? kernel: VFS: file-max limit 4096 reached merci Que tu as 4096 fichiers ouverts simultanements (limite du kernel par defaut). Solution: faire executer le script suivant au boot de la machine. ---cut--- #!/bin/sh echo Setting /proc/sys/fs/file-max to 1 echo 1 /proc/sys/fs/file-max ---cut--- -- Vincent RENARDIAS Directeur Technique StrongHoldNET / http://www.strongholdnet.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel message error
Vincent Renardias wrote: On Wed, 10 Apr 2002, Schmitt georges wrote: Bonjour, que signifie le message d'erreur suivant sur woody ? kernel: VFS: file-max limit 4096 reached merci Que tu as 4096 fichiers ouverts simultanements (limite du kernel par defaut). Solution: faire executer le script suivant au boot de la machine. ---cut--- #!/bin/sh echo Setting /proc/sys/fs/file-max to 1 echo 1 /proc/sys/fs/file-max ---cut--- Le fichier pour faire des modifications dans l'arborescence /proc s'appelle : /etc/sysctl.conf -- == | FREDERIC MASSOT | | http://www.juliana-multimedia.com | | mailto:[EMAIL PROTECTED] | ===Debian=GNU/Linux=== -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
strange kernel message
Hi, I got some strange kernel message recently. I did not do anything to my init besides setting up the xfstt. Below are the strange messages I am getting: bmap of 39a,block 83 is 44f4 super 200 bmap 84 result 44f5 bmap of 39a,block 84 is 44f5 super 200 bmap 85 result 44f6 bmap of 39a,block 85 is 44f6 super 200 bmap 86 result 44f7 bmap of 39a,block 86 is 44f7 super 200 bmap 87 result 44f8 bmap of 39a,block 87 is 44f8 super 200 bmap 88 result 44f9 bmap of 39a,block 88 is 44f9 super 200 bmap 89 result 44fa bmap of 39a,block 89 is 44fa super 200 bmap 8a result 44fb bmap of 39a,block 8a is 44fb super 200 bmap 8b result 44fc bmap of 39a,block 8b is 44fc super 200 bmap 8c bmap of 39a,block 8c is super 200 bmap 8d bmap of 39a,block 8d is super 200 bmap 8e bmap of 39a,block 8e is super 200 bmap 8f bmap of 39a,block 8f is super 200 registered device ppp0 So far I haven't found any problems with it, but would be nice if I know what they mean and get rid of them... Thanks. Shao. Shao Zhang - Running Debian 2.1 ___ _ _ Department of Communications/ __| |_ __ _ ___ |_ / |_ __ _ _ _ __ _ University of New South Wales \__ \ ' \/ _` / _ \ / /| ' \/ _` | ' \/ _` | Sydney, Australia |___/_||_\__,_\___/ /___|_||_\__,_|_||_\__, | Email: [EMAIL PROTECTED]|___/ _
Re: CDROM trouble and Kernel message.
I saw a test patch on linux-kernel this morning, for what sounds like the same problem you're having. I'll take a look and see if I can find it again. On Mon, Feb 15, 1999 at 10:15:26PM +0100, Björn Elwhagen wrote: Hello! I'm having some strange problems. I can't eject my CDROM even tho it's unmounted according to mtab and all other places that i can think of. The message i get is simply: 1 21:59:52 marwin $ cdctrl eject cd_doEject[CDROMEJECT]: Device or resource busy Pressing the eject-button on the CD doesn't help either. If anyone has seen this behaviour b4 please let me know what's the problem. I'm using kernel 2.2.1 and the SCSI-emulation code with a ATAPI-drive. The problem were there with the native ATAPI-driver too so it's not driver-specific AFAIK. A message that i get in my syslog that puzzles me too is this: Feb 10 06:29:15 arwen kernel: khm Why does this message show up? If anyoen can help solve at least the first problem i would be really grateful. It's kinda annoying to have to reboot the freaking computer every time i want to change CD... Regards // Marwin
CDROM trouble and Kernel message.
Hello! I'm having some strange problems. I can't eject my CDROM even tho it's unmounted according to mtab and all other places that i can think of. The message i get is simply: 1 21:59:52 marwin $ cdctrl eject cd_doEject[CDROMEJECT]: Device or resource busy Pressing the eject-button on the CD doesn't help either. If anyone has seen this behaviour b4 please let me know what's the problem. I'm using kernel 2.2.1 and the SCSI-emulation code with a ATAPI-drive. The problem were there with the native ATAPI-driver too so it's not driver-specific AFAIK. A message that i get in my syslog that puzzles me too is this: Feb 10 06:29:15 arwen kernel: khm Why does this message show up? If anyoen can help solve at least the first problem i would be really grateful. It's kinda annoying to have to reboot the freaking computer every time i want to change CD... Regards // Marwin -- | Björn Elwhagen aka Marwin Finger [EMAIL PROTECTED] | | Student at Wexio University for PGP public key. (broken) | | SwedenICQ: 356095 |
Strange kernel-message.
Hello! The last few days i've been noticing strange messages in the kernel-log (kern.log). The message goes like this: Feb 10 06:28:14 arwen kernel: khm and repeats about 5 times every minute. I haven't got a single clue what it means and would appreciate an answer. I'm using kernel 2.2.1. Regards // Marwin -- | Björn Elwhagen aka Marwin Finger [EMAIL PROTECTED] | | Student at Wexio University for PGP public key. (broken) | | SwedenICQ: 356095 |
Kernel message .. HUH?
I received a kernel message this morning that was simply: Couldn't get a free page. what does this mean??? Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel message : Possible flooding ???
Hi, In the file /var/log/kern.log, I have the message like that : Nov 18 05:08:49 poynting last message repeated 2 times Nov 18 05:10:50 poynting kernel: Warning: possible SYN flooding. Sending cookies. Nov 18 05:10:59 poynting kernel: Warning: possible SYN flooding. Sending cookies. Nov 18 05:10:59 poynting kernel: validated probe(3103d184, 5a4ccb84, 33166, 20100, 1878646017) This message is repeated a lot of time. What is the meaning of this message? This week, a user (we actively search him) use our server to attack and crash a other server on the net. Today, our own server crash. We think that the crash was a strike back. So, the kernel message about a possible flooding could be related to our hacker war? Dany Dionne Physics Department Laval University Canada -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: kernel message : Possible flooding ???
From [EMAIL PROTECTED] Wed Nov 19 19:30:15 1997 Received: (qmail 23137 invoked by uid 38); 20 Nov 1997 03:25:23 - Resent-Date: 20 Nov 1997 03:25:23 - Resent-Cc: recipient list not shown: ; X-Envelope-Sender: [EMAIL PROTECTED] Received: (qmail 23099 invoked from network); 20 Nov 1997 03:25:20 - Received: from phy-einstein.ulaval.ca (HELO einstein.phy.ulaval.ca) ([EMAIL PROTECTED]) by 205.229.104.5 with SMTP; 20 Nov 1997 03:25:20 - Received: from astrosun by einstein.phy.ulaval.ca (SMI-8.6/SMI-SVR4) id WAA03432; Wed, 19 Nov 1997 22:29:26 -0500 Received: from cygnus.phy.ulaval.ca by astrosun (SMI-8.6/SMI-SVR4) id WAA22474; Wed, 19 Nov 1997 22:29:15 -0500 Received: from localhost by cygnus.phy.ulaval.ca (SMI-8.6) id WAA18923; Wed, 19 Nov 1997 22:29:24 -0500 Date: Wed, 19 Nov 1997 22:29:24 -0500 (EST) From: Dany Dionne [EMAIL PROTECTED] X-Sender: [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: kernel message : Possible flooding ??? Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: 6RrRJ.A.JpF.i26c0@debian Resent-From: debian-user@lists.debian.org X-Mailing-List: debian-user@lists.debian.org archive/latest/18862 X-Loop: debian-user@lists.debian.org Precedence: list Resent-Sender: [EMAIL PROTECTED] Hi, In the file /var/log/kern.log, I have the message like that : Nov 18 05:08:49 poynting last message repeated 2 times Nov 18 05:10:50 poynting kernel: Warning: possible SYN flooding. Sending cookies. Nov 18 05:10:59 poynting kernel: Warning: possible SYN flooding. Sending cookies. Nov 18 05:10:59 poynting kernel: validated probe(3103d184, 5a4ccb84, 33166, 20100, 1878646017) This message is repeated a lot of time. What is the meaning of this message? This week, a user (we actively search him) use our server to attack and crash a other server on the net. Today, our own server crash. We think that the crash was a strike back. So, the kernel message about a possible flooding could be related to our hacker war? Dany Dionne Physics Department Laval University Canada Dany, sure looks like a syn-flood attack, take a look in tcpdump and See if it gave a legit address. BTW: is this on the Irc???..Rik... TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . __ Get Your Private, Free Email at http://www.hotmail.com -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
kernel message
'Unable to load interpreter.' anyone ever seen this? m* -- The Shining One -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: ICMP redirect kernel message
mike horansky writes: Looking through /var/log/messages, I see Jan 18 18:23:34 bigbox kernel: ICMP redirect from IP addr withheld Jan 18 18:23:34 bigbox last message repeated 3 times every few days. Is that an indication of Ping Of Death? Some other problem? ICMP redirects are sent by your gateways to your host to provide it with a better route to some place (ie, telling you to use another local gateway for that particular connection). Gateways shouldn't obey ICMP redirs, BTW. If you received an ICMP redir from a host that's not your gateway, I think something is amiss. Maybe it's just a (remote) configuration problem? Shouldn't your routers block these packages? -- Adriano -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
ICMP redirect kernel message
Looking through /var/log/messages, I see Jan 18 18:23:34 bigbox kernel: ICMP redirect from IP addr withheld Jan 18 18:23:34 bigbox last message repeated 3 times every few days. Is that an indication of Ping Of Death? Some other problem? -- -Mike Horansky, Leland Consultant (http://consult.stanford.edu/) [EMAIL PROTECTED] OPINIONS EXPRESSED BY ME ARE NOT NECESSARILY SHARED BY MY EMPLOYERS. -- This message was delayed because the list mail delivery agent was down.
