Re: NUC freeazing due to kernel bug

Tim Janssen wrote: > I use debian server on my NUC to run a low powered home server. It freezes > every 2-3 days what looks to be a kernel bug. From a lot of testing it only > occurs when the ethernet cable is inserted and it seems it has to do > something with low power mode (c-st

NUC freeazing due to kernel bug

Dear Sir/Madam, I use debian server on my NUC to run a low powered home server. It freezes every 2-3 days what looks to be a kernel bug. From a lot of testing it only occurs when the ethernet cable is inserted and it seems it has to do something with low power mode (c-states). These issues have

Re: Package for Kernel Bug?

Le 12/23/17 à 20:53, Mason Dean Kukosky a écrit : > I'm trying to send a bug report with reportbug, and It's asking for > the package name. What do I put under package name if it's a bug with > the Linux kernel? > > > Sent with ProtonMail Secure Email. > That's linux-image

Package for Kernel Bug?

I'm trying to send a bug report with reportbug, and It's asking for the package name. What do I put under package name if it's a bug with the Linux kernel? Sent with [ProtonMail](https://protonmail.com) Secure Email.

Re: overcoming known kernel bug

Hi, before doing make, do make menuconfig or make xconfig and inspect the relevant options. I usually collect the chipset specs regarding the mainboard CPU and expansion cards and go through documentation and configuration (if needed). Mostly I just check that the drivers is enabled and if it shou

Re: overcoming known kernel bug

Thank you for the advice. I have gotten that far and went that far again. Below is what I am doing: kversion="4.14.2" cd ~/kernel/linux-$kversion # uname -r # 4.9.0-4-amd64 cp /boot/config-`uname -r` .config yes '' | make oldconfig # There are TONS of new options make -j 4 deb-pkg I get everythin

Re: overcoming known kernel bug

would report this as a low priority kernel bug but it's (far) upstream. > It's also a known problem, which isn't necessarily debian's problem. > > I would appreciate any advice. I bought this laptop because it's tough and > has a good battery. Any laptop that

Re: overcoming known kernel bug

On 12/13/17 05:49, Jeroen Mathon wrote: Please do not top post: https://wiki.debian.org/FAQsFromDebianUser#What_is_top-posting_.28and_why_shouldn.27t_I_do_it.29.3F Hey David, Please address your posts to the list. Have you tried compiling your kernel from source, or researching if a cert

Re: overcoming known kernel bug

On 12/13/17 05:22, Brian J. Oney wrote: Please do not top post: https://wiki.debian.org/FAQsFromDebianUser#What_is_top-posting_.28and_why_shouldn.27t_I_do_it.29.3F Dear David, Please address your posts to the list. this is different issue. My CPUs are just fine and I can use the laptop wi

Re: overcoming known kernel bug

gt; > > > > > > >https://bugzilla.kernel.org/show_bug.cgi?id=196129 > > > > The bug is present up until it's fix in kernel 4.13.4 or something > > > > around > > > > that time. The solution is to install a much newer kernel (or

Re: overcoming known kernel bug

out of disk >>> space lately (15Gb is huge!) My idea was to use the old kernel >>> configuration (with 'make olddefconfig'), but there are so many new >>> options and I honestly have no clue how to get an overview and make >>> an informed decision. I woul

Re: overcoming known kernel bug

> > but I have failed (after consulting the debian kernel handbook). One thing > > or the other doesn't work afterwards. Also, I run out of disk space lately > > (15Gb is huge!) My idea was to use the old kernel configuration (with > > 'make olddefconfig&#

Re: overcoming known kernel bug

n overview and make an informed decision. I would report this as a low priority kernel bug but it's (far) upstream. It's also a known problem, which isn't necessarily debian's problem. I would appreciate any advice. I bought this laptop because it's tough and has a good

overcoming known kernel bug

n informed decision. I would report this as a low priority kernel bug but it's (far) upstream. It's also a known problem, which isn't necessarily debian's problem. I would appreciate any advice. I bought this laptop because it's tough and has a good battery. Any laptop

overcoming known kernel bug

ian kernel handbook). One thing or the other doesn't work afterwards. My idea was to use the old kernel configuration (with 'make olddefconfig'), but there are so many new options and I honestly have no clue how to get an overview and make an informed decision. I would report this as

Re: who to report a kernel bug to in Jessie

wrote: > >>> > >>>>My computer crashes and the text on the screen says it's a kernel bug. > >>>>The first pid is comm, upowerd. > >>>If we knew *exactly* what the screen told you and in what circumstances > >>>the crash occur

Re: who to report a kernel bug to in Jessie

On 03/29/2015 06:54 AM, Brian wrote: On Sat 28 Mar 2015 at 16:43:31 -0400, James wrote: On 03/28/2015 03:36 PM, Brian wrote: On Sat 28 Mar 2015 at 14:41:42 -0400, James wrote: My computer crashes and the text on the screen says it's a kernel bug. The first pid is comm, upowerd.

Re: who to report a kernel bug to in Jessie

On Sat 28 Mar 2015 at 16:43:31 -0400, James wrote: > On 03/28/2015 03:36 PM, Brian wrote: > >On Sat 28 Mar 2015 at 14:41:42 -0400, James wrote: > > > >>My computer crashes and the text on the screen says it's a kernel bug. > >>The first pid is comm, upo

Re: who to report a kernel bug to in Jessie

On 03/28/2015 03:36 PM, Brian wrote: On Sat 28 Mar 2015 at 14:41:42 -0400, James wrote: My computer crashes and the text on the screen says it's a kernel bug. The first pid is comm, upowerd. If we knew *exactly* what the screen told you and in what circumstances the crash occurs an

Re: who to report a kernel bug to in Jessie

On Sat 28 Mar 2015 at 14:41:42 -0400, James wrote: > My computer crashes and the text on the screen says it's a kernel bug. > The first pid is comm, upowerd. If we knew *exactly* what the screen told you and in what circumstances the crash occurs and how repeatable it is we might be a

who to report a kernel bug to in Jessie

My computer crashes and the text on the screen says it's a kernel bug. The first pid is comm, upowerd. -- 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.or

Re: Bug#684293: Info received (Bug#684293: root cause of mount hang in installer [kernel bug])

On Sat, 11 Aug 2012 21:18:34 +0200, Sven Joachim wrote: > On 2012-08-11 21:06 +0200, Mika Suomalainen wrote: > >> On 11.08.2012 21:18, Debian Bug Tracking System wrote: >>> Thank you for the additional information you have supplied regarding >>> this Bug report. (...) >> What is this email? Isn

Re: Bug#684293: root cause of mount hang in installer [kernel bug]

e of the recent mount > > > problems with extended partitions (maybe also mounting disks like sda) > > > are related to the infinite loop kernel bug in __getblk_slow. > > > > > > (see the explanation: https://patchwork.kernel.org/patch/1189121/) > > > The

Re: Bug#684293: Info received (Bug#684293: root cause of mount hang in installer [kernel bug])

On 2012-08-11 21:06 +0200, Mika Suomalainen wrote: > On 11.08.2012 21:18, Debian Bug Tracking System wrote: >> Thank you for the additional information you have supplied >> regarding this Bug report. >> >> This is an automatically generated reply to let you know your >> message has been received.

Re: Bug#684293: Info received (Bug#684293: root cause of mount hang in installer [kernel bug])

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11.08.2012 21:18, Debian Bug Tracking System wrote: > Thank you for the additional information you have supplied > regarding this Bug report. > > This is an automatically generated reply to let you know your > message has been received. > > Your

Bug#684293: Info received (Bug#684293: root cause of mount hang in installer [kernel bug])

Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will rep

Re: kernel bug and reportbug bug

On Sun, 26 Feb 2012 12:05:12 -0500, Jude DaShiell wrote: (please, post at the bottom :-) ) > On Sun, 26 Feb 2012, Camale?n wrote: (...) >> > I was told I ought to file a bug against the debian kernel since the >> > drivers my disk needs are in the kernel but for some reason don't >> > work. Th

Re: kernel bug and reportbug bug

I have one instance of debian working on an ide drive and slackware installed on the serial ATA drive instance. I don't know how connections were done on this machine since I didn't install the serial ATA drive but can find out. On Sun, 26 Feb 2012, Camale?n wrote: > On Fri, 24 Feb 2012 18:39:

Re: kernel bug and reportbug bug

On Fri, 24 Feb 2012 18:39:36 -0500, Jude DaShiell wrote: > I had a successful install of slackware 13.0 on my nVidia CK804 Serial > ATA drive. Before doing so, I had a failed install of debian on that > drive with debian causing much banging of the drive before throwing > drive detection failed m

kernel bug and reportbug bug

I had a successful install of slackware 13.0 on my nVidia CK804 Serial ATA drive. Before doing so, I had a failed install of debian on that drive with debian causing much banging of the drive before throwing drive detection failed message and dropping me into media change dialog. Of course, t

Re: Debian 6 Squeeze bug report: application or kernel bug?

On Fri, 2011-10-07 at 21:15 +0200, Ralf Mardorf wrote: > On Fri, 2011-10-07 at 21:10 +0200, Ralf Mardorf wrote: > > On Fri, 2011-10-07 at 17:21 +, Camaleón wrote: > > > :-) > > > > > > I have put Xfce in my "radar" as a possible candidate to replace the > > > upcoming GNOME3 > > > > :) > >

Re: Debian 6 Squeeze bug report: application or kernel bug?

Hi! My other 2 cents is to use LXDE *with* RatPoison! ;-) It's what I'm doing! ;-) On the Lemote Yeeloong it's perfect! On Fri, 07 Oct 2011 21:10:48 +0200 Ralf Mardorf > [...] > One of two candidates for me to, the other one is LXDE (not fluxbox). > > A snapshot from my terminal emulation: spinym

Re: Debian 6 Squeeze bug report: application or kernel bug?

On Fri, 2011-10-07 at 21:10 +0200, Ralf Mardorf wrote: > On Fri, 2011-10-07 at 17:21 +, Camaleón wrote: > > :-) > > > > I have put Xfce in my "radar" as a possible candidate to replace the > > upcoming GNOME3 > > :) > > One of two candidates for me to, the other one is LXDE (not fluxbox). >

Re: Debian 6 Squeeze bug report: application or kernel bug?

On Fri, 2011-10-07 at 17:21 +, Camaleón wrote: > :-) > > I have put Xfce in my "radar" as a possible candidate to replace the > upcoming GNOME3 :) One of two candidates for me to, the other one is LXDE (not fluxbox). A snapshot from my terminal emulation: spinymouse@debian:~$ I have tende

Re: Debian 6 Squeeze bug report: application or kernel bug?

On Fri, 07 Oct 2011 17:44:38 +0100, Ad L. wrote: (re-arranging the message) > 2011/10/7 Camaleón (...) >> > Should I report this as a kernel bug, or as a bug in the mount >> > package? (considering "Pid: 3218, comm: umount ...") I am not sure >> > where

Re: Debian 6 Squeeze bug report: application or kernel bug?

> > at #1 more often while using the MEPIS Live CD, but it simply resulted > > in read error messages, but nothing serious. This time, at least one of > > the exceptions occurred when 'umount' was running. > > > > Should I report this as a kernel bug, or as a

Re: Debian 6 Squeeze bug report: application or kernel bug?

MEPIS Live CD, but it simply resulted > in read error messages, but nothing serious. This time, at least one of > the exceptions occurred when 'umount' was running. > > Should I report this as a kernel bug, or as a bug in the mount package? > (considering "Pid: 32

Debian 6 Squeeze bug report: application or kernel bug?

onto the register contents, stacktrace etc. again It concerns me that things got this far now. I encountered the problem at #1 more often while using the MEPIS Live CD, but it simply resulted in read error messages, but nothing serious. This time, at least one of the exceptions occurred when 'um

Re: Wheezy kernel bug

Dne 12.8.2011 15:57, piše Tony Gallagher: Hi, This is my first time reporting a bug, so bear with me. I installed Debian Squeeze and performed a dist-upgrade once. From there, I changed my sources.list to point at Wheezy and have regularly performed a dist-upgrade. Everything is reasonably

Wheezy kernel bug

Hi, This is my first time reporting a bug, so bear with me. I installed Debian Squeeze and performed a dist-upgrade once. From there, I changed my sources.list to point at Wheezy and have regularly performed a dist-upgrade. Everything is reasonably stable, with the exception of the kernel.

Re: Kernel bug in Squeeze

On Thursday 13 Jan 2011 09:35:04 Russell Gadd wrote: > Also how/where could I report this bug? For the how, I suggest you look at the reportbug man page. Neil Youngman -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...

Re: Kernel bug in Squeeze

On Thu, 13 Jan 2011 09:35:04 +, Russell Gadd wrote: > I have had 2 freezes recently with a kernel bug reported on the screen. > One was at the end of shutdown (on a reboot) and the other just now on > bootup (not the same reboot). I had a look in syslog for some info but I > susp

Kernel bug in Squeeze

I have had 2 freezes recently with a kernel bug reported on the screen. One was at the end of shutdown (on a reboot) and the other just now on bootup (not the same reboot). I had a look in syslog for some info but I suspect that the output wasn't able to be added due to the system halting. I

nfs kernel bug ?

] [ cut here ] Oct 20 13:17:47 localhost kernel: [602284.351294] kernel BUG at net/sunrpc/svc.c:491! Oct 20 13:17:47 localhost kernel: [602284.351294] invalid opcode: [1] SMP Oct 20 13:17:47 localhost kernel: [602284.351294] CPU 1 Oct 20 13:17:47 localhost kernel: [602284.351294

Does anybody understand this !!!! kernel bug with ndiswrapper

I have a wireless pcmcia card, on a lappy. If i use ftp or smbmount or nfs my network connection dies and i get the following ( below ) while transfering files. http seems fine ! and does'nt cause the kernel bug !! I have to reboot the laptop i'm using, anybody know how to sol

message at logs: kernel BUG at mm/rmap.c

04:01 devel kernel: [ cut here ] Jul 15 08:04:01 devel kernel: kernel BUG at mm/rmap.c:522! Jul 15 08:04:01 devel kernel: invalid opcode: [#291] Jul 15 08:04:01 devel kernel: SMP Jul 15 08:04:01 devel kernel: Modules linked in: xt_multiport ipt_REJECT xt_tcpudp ipt_LOG xt_

Kernel bug? when using lucent modem

13:16:36 alfa pppd[3526]: sent [LCP ConfReq id=0x1] Mar 18 13:16:37 alfa kernel: skb_under_panic: text:ccac3d97 len:11 put:1 head:c2b28800 data:c2b287ff tail:c2b2880a end:c2b28e00 dev: Mar 18 13:16:37 alfa kernel: [ cut here ] Mar 18 13:16:37 alfa kernel: kernel BUG at ne

Re: Wating for root file system. Kernel bug?

On Tue, Dec 11, 2007 at 07:13:49PM +0200, wanderlust wrote: > Hello. > > I'm trying to install Debian/etch on Acer Aspire 5520G, but the problem > is, that kernel 2.6.18 doesn't support Marvell netcard 436b. I found it > is supportable in 2.6.23.9, so I decided to compile it. I used default > conf

Wating for root file system. Kernel bug?

Hello. I'm trying to install Debian/etch on Acer Aspire 5520G, but the problem is, that kernel 2.6.18 doesn't support Marvell netcard 436b. I found it is supportable in 2.6.23.9, so I decided to compile it. I used default configuration, taken from /proc/config.gz and after compiling and installing

Kernel bug?

I installed Etch a couple of weeks on a Toshiba Tecra A4-S211 for a friend of mine. Today I had to install some software and get his new printer working. While I was at it I ran apt-get update && apt-get upgrade. The kernel was patched during this upgrade and now the laptop will no longer s

jpilot/pilot link kernel bug

] kernel BUG at kernel/workqueue.c:109! invalid operand: [#1] Modules linked in: visor parport_pc lp parport ipv6 nfs lockd nfs_acl sunrpc ext2 usbserial usb_storage usblp snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq joydev evdev psmouse serio_raw snd_via82xx gameport

Re: USB Mass Storage - Kernel Bug?

ses a 200GB IDE drive. When I try to > > perform large transfers (eg 500MB files) to the box it aborts after a > > variable proportion of the file/s have been transferred. > > > > The dmesg output calls it a kernel bug... Google is unhelpful, does [...] > > Yo

Re: USB Mass Storage - Kernel Bug?

files) to the box it aborts after a > variable proportion of the file/s have been transferred. > > The dmesg output calls it a kernel bug... Google is unhelpful, does > anybody know what this is or where I could go for further assistance. > All the recent kernels versions that I've

USB Mass Storage - Kernel Bug?

calls it a kernel bug... Google is unhelpful, does anybody know what this is or where I could go for further assistance. All the recent kernels versions that I've tried seem affected, from 2.6.4 through to 2.6.9-rc2. Note that the drive works under Windows 2k/XP. Dmesg output is attached, wit

Re: USB Mass Storage - Kernel Bug?

gt; variable proportion of the file/s have been transferred. > > The dmesg output calls it a kernel bug... Google is unhelpful, does > anybody know what this is or where I could go for further assistance. > Kernel versions that seem affected are 2.6.7 to 2.6.9-rc2. > > Note that the d

Re: USB Mass Storage - Kernel Bug?

ng an external USB 2.0 to IDE converter box with > recent 2.6 kernels. The box houses a 200GB IDE drive. When I try to > perform large transfers (eg 500MB files) to the box it aborts after a > variable proportion of the file/s have been transferred. > > The dmesg output calls it a kerne

USB Mass Storage - Kernel Bug?

calls it a kernel bug... Google is unhelpful, does anybody know what this is or where I could go for further assistance. Kernel versions that seem affected are 2.6.7 to 2.6.9-rc2. Note that the drive works under Windows 2k/XP and previously worked under 2.6 kernels (about 2.6.5 IIRC). Dmesg output

Re: So is this a kernel bug?

I think it has to do with the NFS implementation in Linux. I remember running similar problem when I tried to copy a couple of 100+ Mb MPEG file from one Linux system to another over NFS. Try increasing the wsize and rsize in the mount options. That might help. Otherwise, I would suggest to try u

Re: So is this a kernel bug?

George Cristian Birzan wrote: On Tue, Apr 20, 2004 at 10:20:03AM -0500, Kent West wrote: Now I'm trying to move those files to a similar server named PEZ10 using my Debian box as the middle man. This is terribly bandwidth inefficient. You should copy directly, it'll be twice as fast. :-)

Re: So is this a kernel bug?

Take 2, actually mailing the list. On Tue, Apr 20, 2004 at 10:20:03AM -0500, Kent West wrote: > Now I'm trying to move those files to a similar server named PEZ10 using > my Debian box as the middle man. This is terribly bandwidth inefficient. You should copy directly, it'll be twice as fast. :-

Re: So is this a kernel bug?

On (20/04/04 10:20), Kent West wrote: > The other day I backed up a lot of Macintosh files to a Linux-based > backup "appliance" server (SNAP server?); it's named PEZ13. > > Now I'm trying to move those files to a similar server named PEZ10 using > my Debian box as the middle man. From the Debia

So is this a kernel bug?

The other day I backed up a lot of Macintosh files to a Linux-based backup "appliance" server (SNAP server?); it's named PEZ13. Now I'm trying to move those files to a similar server named PEZ10 using my Debian box as the middle man. From the Debian box, I've tried the command: cp -av /[mountp

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

On 12/23/02 19:46, Nathan E Norman wrote: 'man mount' tells you what the options _are_ ... finding out what the options _do_ is a bit more work :) I haven't actually found a great reference for ext3 yet. Thank you. So, 'data=ordered' (default) means that the data is written to the file system

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

On Mon, Dec 23, 2002 at 18:46:07 -0600, Nathan E Norman wrote: > On Mon, Dec 23, 2002 at 07:28:21PM -0500, Andrew Hurt wrote: [data=journal, etc] > > Where might I find more info on the types/benefits of these options? > > 'man mount' tells you what the options _are_ ... finding out what the > opt

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

On Mon, Dec 23, 2002 at 07:28:21PM -0500, Andrew Hurt wrote: > On 12/23/02 18:57, Nathan E Norman wrote: > >On Mon, Dec 23, 2002 at 06:31:30PM -0500, Andrew Hurt wrote: > > > >>How do I tell what type of mode I currently have > > > >Look in your fstab (or vgrep the output of 'mount') and look at th

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

On 12/23/02 18:57, Nathan E Norman wrote: On Mon, Dec 23, 2002 at 06:31:30PM -0500, Andrew Hurt wrote: How do I tell what type of mode I currently have Look in your fstab (or vgrep the output of 'mount') and look at the options in parens after the "type ext3" bit: if you don't see "data=journa

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

On Mon, Dec 23, 2002 at 06:31:30PM -0500, Andrew Hurt wrote: > On 12/21/02 20:52, Craig Dickson wrote: > >Frank Copeland wrote: > > > >>AIUI, the problem with ext3 filesystems applies only if they are in > >>journal mode, which isn't the default. I've also seen suggestions that > >>the bug exists i

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

On 12/21/02 20:52, Craig Dickson wrote: Frank Copeland wrote: AIUI, the problem with ext3 filesystems applies only if they are in journal mode, which isn't the default. I've also seen suggestions that the bug exists in several versions of the 2.4.x kernels prior to 2.4.20. You mean "data journ

Re: ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

Frank Copeland wrote: > AIUI, the problem with ext3 filesystems applies only if they are in > journal mode, which isn't the default. I've also seen suggestions that > the bug exists in several versions of the 2.4.x kernels prior to > 2.4.20. You mean "data journaling" mode -- ext3 is always journ

ext3 kernel bug, was: Compiling a kernel on an UltraSparc?

On 21 Dec 02 19:15:50 GMT, Nathan E Norman <[EMAIL PROTECTED]> wrote: > BTW, 2.4.20 is not the kernel you want if you run ext3 filesystems. AIUI, the problem with ext3 filesystems applies only if they are in journal mode, which isn't the default. I've also seen suggestions that the bug exists in

kernel bug!

Every day my server "dies", presumably doing cron job stuff. So I went through the cron.daily items, and ran into: baboon:/etc/cron.daily# ./modutils Assertion failure in journal_forget() at transaction.c:1217: "!jh->b_committed_data" kernel BUG at transaction.c:1217! in

OT: where to post kernel bug

Hi, I think i found a bug in the recent kernel series but i am not sure where the best place is to post it. Do i need to subscribe to the kernel ml and post it there or is it better to contact the author of the code directly (the bug is in the ide-scsi code), or is there some sort of a bug trac

Re: Linux kernel bug report?

* On 24-09-01 at 07:08 Dave Thayer ([EMAIL PROTECTED]) wrote: +Here quoted text begins+ > I was able to get apm to work (aside from some incompatabilities with > my hardware) under 2.4.10. I compiled it as modules, ISTR compiling it > directly into the kernel under 2.4.9 didn't work well.

Re: Linux kernel bug report?

* On 24-09-01 at 07:08 Dave Thayer ([EMAIL PROTECTED]) wrote: +Here quoted text begins+ > On Mon, Sep 24, 2001 at 12:44:23AM +0200, [EMAIL PROTECTED] wrote: > > > > I have just discovered that APM in kernel 2.4.10 does not work (/proc/apm > > file > > does not get created and consequentia

Re: Linux kernel bug report?

On Mon, Sep 24, 2001 at 12:44:23AM +0200, [EMAIL PROTECTED] wrote: > > I have just discovered that APM in kernel 2.4.10 does not work (/proc/apm file > does not get created and consequentially apm progs do not work). > Can someone else confirm this? > I was able to get apm to work (aside from som

Linux kernel bug report?

Hi! I have just discovered that APM in kernel 2.4.10 does not work (/proc/apm file does not get created and consequentially apm progs do not work). Can someone else confirm this? And where can a bug report about this kind of bug be sent? (this is not a Debian kernel but a vanilla one from ftp.kern

Re: Kernel Bug

Felipe Alvarez Harnecker wrote: > > Hi, > > i'm getting this kernel errors: > > Jan 24 08:36:00 Lakgo kernel: VM: do_try_to_free_pages failed for rpc.nfsd... > Jan 24 08:36:00 Lakgo last message repeated 5 times > Jan 24 08:36:00 Lakgo kernel: VM: do_try_to_free_pages failed for > rpc.mountd...

Re: Kernel Bug

On Wed, 24 Jan 2001, Felipe Alvarez Harnecker wrote: > I thought that was a 2.2.17 bug so i compiled 2.2.18 ( release ) and > the prob. remains the same. > > Any hint to solve this. reading the kernel changelogs helps a lot. 19pre2 minimum. -- [-] So, you're a Ph.D. Just don't touch anythi

Kernel Bug

Hi, i'm getting this kernel errors: Jan 24 08:36:00 Lakgo kernel: VM: do_try_to_free_pages failed for rpc.nfsd... Jan 24 08:36:00 Lakgo last message repeated 5 times Jan 24 08:36:00 Lakgo kernel: VM: do_try_to_free_pages failed for rpc.mountd... Jan 24 08:36:00 Lakgo kernel: VM: do_try_to_free_

Re: files appear corrupt, but aren't; kernel bug?

Scott Henry <[EMAIL PROTECTED]> writes: > > "D" == Dan Christensen <[EMAIL PROTECTED]> writes: > > D> Over the past few hours, my potato machine has been behaving very > D> strangely. Many of the files on my hard drive or which I read from > D> cdrom have minor errors. Specifically, at a ran

Re: files appear corrupt, but aren't; kernel bug?

> "D" == Dan Christensen <[EMAIL PROTECTED]> writes: D> Over the past few hours, my potato machine has been behaving very D> strangely. Many of the files on my hard drive or which I read from D> cdrom have minor errors. Specifically, at a random point in the file, D> two consecutive bytes ar

files appear corrupt, but aren't; kernel bug?

Over the past few hours, my potato machine has been behaving very strangely. Many of the files on my hard drive or which I read from cdrom have minor errors. Specifically, at a random point in the file, two consecutive bytes are changed to 160 and 192 (240 300 octal). Moreover, this often repeats