ath10k driver generates kernel oops?

It has happened several times that my wifi didn't work after starting. When I look at the dmesg output I see an error which looks like a kernel oops, except for the fact that the word oops is not used: [   24.412326] CPU: 2 PID: 1391 Comm: Web Content Not tainted 4.19.0-6-amd64 #1 Debian 4.

tracking down a kernel oops

gh, because the logs show a kernel oops when this happens. It's hard to know what the ultimate cause of these events might be, but gdbus seems to be implicated often. I'll attach the relevant logs below from two of the most recent such events. The kernel is: 3.2.0-4-686-pae #1 SMP Debia

Re: Kernel Oops during/after rsync

Hello Camaleón, Camaleón wrote: > Is the Patrician III a stable pattern for the crash? I mean, is it always > crashing when running it and it keeps stable when at the time the routine > runs the computer is idle? I am not entirely sure. So far, the computer crashed thrice during a backup, and,

Re: Kernel Oops during/after rsync

On Wed, 08 Aug 2012 01:54:11 +0200, Claudius Hubig wrote: > recently, I _sometimes_ encounter a kernel oops during a backup run. > This did not occur until a few days ago, furthermore, all the crashes so > far (a backup takes place every half hour and I’ve only seen three > during t

Kernel Oops during/after rsync

Hello, recently, I _sometimes_ encounter a kernel oops during a backup run. This did not occur until a few days ago, furthermore, all the crashes so far (a backup takes place every half hour and I’ve only seen three during the last five days) occurred while I was playing Patrician III with Wine

Re: Kernel Oops when closing the lid on Alienware M11xR3 laptop

On Wed, 23 May 2012 21:42:45 +0100, elbbit wrote: > Update... > > With i915 blacklisted or not the problem continues: > > Full gnome -> close lid -> kernel oops Compiz -> close lid -> kernel > oops > Bare xorg (just an xterm) -> close lid -> kernel o

Re: Re: Kernel Oops when closing the lid on Alienware M11xR3 laptop

I tried with kernel 3.0.0 and it's working as well. I reported the bug in the BTS: 674243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674243 Thanks Sylvain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lis

Re: Kernel Oops when closing the lid on Alienware M11xR3 laptop

Update... With i915 blacklisted or not the problem continues: Full gnome -> close lid -> kernel oops Compiz -> close lid -> kernel oops Bare xorg (just an xterm) -> close lid -> kernel oops >> On Wed, 23 May 2012 06:36:24 +0100, elbbit wrote: >>> When logg

Re: Kernel Oops when closing the lid on Alienware M11xR3 laptop

at's what I thought. I put debugging on for the pm-utils scripts and >> checked a whole bunch of log files and, like you say, it seems to be a >> problem with the Intel software (callback trace suggests it). > > You can try to isolate the kernel oops by puting the intel VGA

Re: Kernel Oops when closing the lid on Alienware M11xR3 laptop

ep If I press power button while > in Gnome (configured) -> enter sleep If I do nothing and just close lid > -> Kernel oops Mmm... >> That's curious because closing the lid and suspending from menu should >> both trigger the same command unless > > That&#x

Re: Kernel Oops when closing the lid on Alienware M11xR3 laptop

un Debian/testing. This problem exists on both my laptops. If I run "sudo pm-suspend" -> enter sleep If I press power button while in Gnome (configured) -> enter sleep If I do nothing and just close lid -> Kernel oops > That's curious because closing the lid and suspendin

Re: Kernel Oops when closing the lid on Dell XPS 14z

intel_gtt_insert_sg_entries+0x45/0x8d (...) Looks like the Xorg server is crashing. > I looked online, but I couldn't find a workaround. Yes, you did: suspend from the menu instead closing the lid ;-) > Let me know if more information are needed. I would report a kernel oops in Debia

Kernel Oops when closing the lid on Dell XPS 14z

Hello, I'm running Sid on my Dell XPS 14z, everything is up to date. Suspend works fine when I select it from the menu. But when I close the lid, it crashes. If I suspend first with the menu, and then close the lid, it works correcty. I tried kernel 3.3 trunk and got the same problem. Intel

Re: kernel oops with Google Chrome after recent security update (2.6.32-35squeeze1)

On 2011-09-11, Curt wrote: > On 2011-09-10, Andrew Reid wrote: >>> >>> I'm talking about the recent kernel security update in stable to: >>> >>> 2.6.32-35squeeze1 >> >> Just FYI, I checked the repo, and 2.6.32-25squeeze2 is now available. >> I'm installing it now, I don't know yet if it fixes

Re: kernel oops with Google Chrome after recent security update (2.6.32-35squeeze1)

On 2011-09-10, Andrew Reid wrote: >> >> I'm talking about the recent kernel security update in stable to: >> >> 2.6.32-35squeeze1 > > Just FYI, I checked the repo, and 2.6.32-25squeeze2 is now available. > I'm installing it now, I don't know yet if it fixes the issue, but judging > from the bu

Re: kernel oops with Google Chrome after recent security update (2.6.32-35squeeze1)

> On 2011-09-10, Stephen Allen wrote: > > On Sat, Sep 10, 2011 at 09:19:52AM +, Curt wrote: > >> After installing a kernel security update yesterday, I'm getting random > >> kernel oops when using Google Chrome. Anybody else seeing this > >>

Re: kernel oops with Google Chrome after recent security update (2.6.32-35squeeze1)

> On 2011-09-10, Camaleón wrote: > > On Sat, 10 Sep 2011 09:19:52 +, Curt wrote: > >> After installing a kernel security update yesterday, I'm getting random > >> kernel oops when using Google Chrome. Anybody else seeing this > >> phenomenon? >

Re: kernel oops with Google Chrome after recent security update (2.6.32-35squeeze1)

On 2011-09-10, Stephen Allen wrote: > On Sat, Sep 10, 2011 at 09:19:52AM +, Curt wrote: >> After installing a kernel security update yesterday, I'm getting random >> kernel oops when using Google Chrome. Anybody else seeing this >> phenomenon? >> > ---en

Re: kernel oops with Google Chrome after recent security update (2.6.32-35squeeze1)

On Sat, Sep 10, 2011 at 09:19:52AM +, Curt wrote: > After installing a kernel security update yesterday, I'm getting random > kernel oops when using Google Chrome. Anybody else seeing this > phenomenon? > ---end quoted text--- No all is fine here on Wheezy 3.0.01 ker

Re: kernel oops with Google Chrome after recent security update (2.6.32-35squeeze1)

On 2011-09-10, Camaleón wrote: > On Sat, 10 Sep 2011 09:19:52 +, Curt wrote: > >> After installing a kernel security update yesterday, I'm getting random >> kernel oops when using Google Chrome. Anybody else seeing this >> phenomenon? > > Yes, a couple of us

Re: kernel oops with Google Chrome after recent security update (2.6.32-35squeeze1)

On Sat, 10 Sep 2011 09:19:52 +, Curt wrote: > After installing a kernel security update yesterday, I'm getting random > kernel oops when using Google Chrome. Anybody else seeing this > phenomenon? Yes, a couple of users in the Spanish mailing list are also reporting this. C

kernel oops with Google Chrome after recent security update (2.6.32-35squeeze1)

After installing a kernel security update yesterday, I'm getting random kernel oops when using Google Chrome. Anybody else seeing this phenomenon? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@l

Re: Third kernel oops in three days

On Mon, 04 Jul 2011 15:56:50 +0200, Jonathan Hanger wrote: > I've been having some troubles with the kernel these last three days. In > that time, three oops happened... which is really unusual (running > Debian for a few months with no kernel problems so far). (...) > WARNING: at > /build/buil

Third kernel oops in three days

Hello, I've been having some troubles with the kernel these last three days. In that time, three oops happened... which is really unusual (running Debian for a few months with no kernel problems so far). I can't know whether it is related or not, but the first oops came after I was "playing" a ga

Re: scsi/firewire kernel oops, any point in reporting a bug ?

On 2010-07-15 03:35 +0200, bri...@aracnet.com wrote: > Looks like the latest kernel is -5, is that correct ? Yes. Sven -- 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.o

Re: scsi/firewire kernel oops, any point in reporting a bug ?

On Wed, 14 Jul 2010 09:09:10 +0200 Sven Joachim wrote: > On 2010-07-14 04:31 +0200, bri...@aracnet.com wrote: > > > The question is , submit to Debian or to LKML ? > > Report a bug in Debian, they will likely instruct how to report > upstream. But first of all, boot a newer kernel because your

Re: scsi/firewire kernel oops, any point in reporting a bug ?

On 2010-07-14 04:31 +0200, bri...@aracnet.com wrote: > The question is , submit to Debian or to LKML ? Report a bug in Debian, they will likely instruct how to report upstream. But first of all, boot a newer kernel because your current one… > [24128.816259] Pid: 716, comm: scsi_eh_10 Tainted: P

scsi/firewire kernel oops, any point in reporting a bug ?

Hi All, I've attached the output of dmesg at the end of the e-mail. As usual everything was perfectly stable before I made the mistake of doing dist-upgrade. I've really got to quit doing that unless I _really_ need to. So I can't see that anyone is going to be able to use the information to d

Re: Kernel oops on Lenny, when opening tabs in Firefox

On 08/10/08 12:36, Carl Fink wrote: On Sun, Aug 10, 2008 at 12:00:51PM -0500, Ron Johnson wrote: Presumably this is repeatable? It repeats, but I don't know exactly what triggers it, except that so far it seems to happen when at least five FF tabs are open. Any 5 URLs, or specific URLs? IO

Re: Kernel oops on Lenny, when opening tabs in Firefox

On Sun, Aug 10, 2008 at 12:00:51PM -0500, Ron Johnson wrote: > Presumably this is repeatable? It repeats, but I don't know exactly what triggers it, except that so far it seems to happen when at least five FF tabs are open. -- Carl Fink [EMAIL PROTECTED] Read my blog

Re: Kernel oops on Lenny, when opening tabs in Firefox

On 08/10/08 11:29, Carl Fink wrote: The Firefox part might be a coincidence, of course. In an rxvt, I see: Oops: [1] SMP Then a few seconds later I get: CR2: 5a In syslog, I find this: Aug 10 11:22:47 NitpickingHP2 kernel: Unable to handle kernel NULL pointer dereference at

Kernel oops on Lenny, when opening tabs in Firefox

:47 NitpickingHP2 kernel: [] Aug 10 11:22:47 NitpickingHP2 kernel: PGD 68882067 PUD 6888a067 PMD 0 Aug 10 11:22:47 NitpickingHP2 kernel: Oops: [1] SMP Aug 10 11:22:47 NitpickingHP2 kernel: CPU 0 Aug 10 11:22:47 NitpickingHP2 kernel: Modules linked in: ndiswrapper ipt_MASQUERADE iptable_nat

Kernel oops in updated Woody 2.4.19 kernel

Hello, I'm running a Debian Woody system. I recently updated the kernel to the latest Debian-packaged kernel-source-2.4.19. This morning, the server crashed with a kernel oops. The function it crashed in is "may_ptrace_attach", one of the functions affected by the recent

Re: Problem with pc, kernel oops, applications crashed

handle kernel paging request at > virtual address 2404f9bd > Feb 24 09:07:31 debian kernel: printing eip: > Feb 24 09:07:31 debian kernel: c4809f5d > Feb 24 09:07:31 debian kernel: *pde = > Feb 24 09:07:31 debian kernel: Oops: [#2] > Feb 24 09:07:31 debian kernel: PR

Re: Problem with pc, kernel oops, applications crashed

:54:51 debian kernel: Unable to handle kernel paging request at >> virtual address fff598d7 >> Feb 23 09:54:51 debian kernel: printing eip: >> Feb 23 09:54:51 debian kernel: dc447f5d >> Feb 23 09:54:51 debian kernel: *pde = 2067 >> Feb 23 09:54:51 debian kernel: *pte

Re: Problem with pc, kernel oops, applications crashed

ress fff598d7 > Feb 23 09:54:51 debian kernel: printing eip: > Feb 23 09:54:51 debian kernel: dc447f5d > Feb 23 09:54:51 debian kernel: *pde = 2067 > Feb 23 09:54:51 debian kernel: *pte = > Feb 23 09:54:51 debian kernel: Oops: [#1] > Feb 23 09:54:51 debian kernel: PREEMP

Problem with pc, kernel oops, applications crashed

09:54:51 debian kernel: printing eip: Feb 23 09:54:51 debian kernel: dc447f5d Feb 23 09:54:51 debian kernel: *pde = 2067 Feb 23 09:54:51 debian kernel: *pte = Feb 23 09:54:51 debian kernel: Oops: [#1] Feb 23 09:54:51 debian kernel: PREEMPT Feb 23 09:54:51 debian kernel: Modules

anyone successful in using highpoint rocketraid 1520 with debian 2.6.8 kernel? kernel oops

to the system I am getting a kernel oops as soon as the kernel tries to load the hpt366 module. has anyone got this working? Can you tell me what you did? I would like to try the open source hpt302 module available as source from the highpoint people. I see from the instructions on the

Ring buffer size [Was: Re: What is "Kernel OOPs"?]

On Thu, Mar 04, 2004 at 05:44:46PM -0800, Vineet Kumar wrote: > * ([EMAIL PROTECTED])[20040304 09:19]: > > dmesg just displays what the kernel outputs during boot. Usually you > > want to type "dmesg | less" so that you can scroll through all the > > messages. > > More precisely, kernel messages a

Re: What is "Kernel OOPs"?

* ([EMAIL PROTECTED])[20040304 09:19]: > dmesg just displays what the kernel outputs during boot. Usually you > want to type "dmesg | less" so that you can scroll through all the > messages. More precisely, kernel messages are sent to a buffer known as the "kernel ring buffer". dmesg displays the

Re: What is "Kernel OOPs"?

Abdul Latip wrote: Apology, I am not a native English speaker. Maybe so, but your english and spelling are better than many posts I have seen :) It is still not so clear what exactly "Kernel OOPs" refers to. I tried to google with no luck. "oops" is like a short version

What is "Kernel OOPs"?

Apology, I am not a native English speaker. It is still not so clear what exactly "Kernel OOPs" refers to. I tried to google with no luck. How is kernel oops related to: - kernel crash? - dmesg? - someone/something is probing/tempering the kernel? - just an ordinary "whoops"

Re: Kernel Oops (was Re: Lots of scary segfaults)

On Tuesday 30 September 2003 00:37, Mark Ferlatte wrote: > It would mean taking your hardware offline, but I would try memtest. > Think of it this way: maybe the next bit flip is in the middle of > your data. Uhm, but I thought memtest from the sysutils package (as opposed to memtest86), was sui

Re: Kernel Oops (was Re: Lots of scary segfaults)

On Tue, 30 Sep 2003 04:40:09 +0200, csj wrote: > Try compiling the linux kernel X times. In my experience at some > point bad memory will cause a kernel compile to fail (of course a > bad CPU would casue it to fail much faster, but CPU's are > probably the hardiest part of your system) That, or i

Re: Kernel Oops (was Re: Lots of scary segfaults)

At Mon, 29 Sep 2003 23:03:27 +0200, Kjetil Kjernsmo wrote: > > On Monday 29 September 2003 22:06, Juri Haberland wrote: > > Though I don't know much about kernel opps messages I still > > recommend to check you RAM, e.g. with memtest86, as it might > > be just a bit flipped due to failed memory. >

Re: Kernel Oops (was Re: Lots of scary segfaults)

Mark Ferlatte schrieb: > Kjetil Kjernsmo said on Mon, Sep 29, 2003 at 11:03:27PM +0200: >> How about memtest...? This box is under some load, but usually not too >> bad, would it be a good idea to run it overnight? How would I go about >> to test a much as possible of my memory with it? > > It w

Re: Kernel Oops (was Re: Lots of scary segfaults)

Kjetil Kjernsmo said on Mon, Sep 29, 2003 at 11:03:27PM +0200: > How about memtest...? This box is under some load, but usually not too > bad, would it be a good idea to run it overnight? How would I go about > to test a much as possible of my memory with it? It would mean taking your hardware o

Re: Kernel Oops (was Re: Lots of scary segfaults)

On Monday 29 September 2003 22:06, Juri Haberland wrote: > Though I don't know much about kernel opps messages I still recommend > to check you RAM, e.g. with memtest86, as it might be just a bit > flipped due to failed memory. Oh, yes, that's right, I forgot. Thanks. However, it requires taking i

Re: Kernel Oops (was Re: Lots of scary segfaults)

Kjetil Kjernsmo schrieb: > These segfaults started to appear, and I found there were little I could > do to repair it. Eventually, it seems like more and more programs got > this problem, and finally I couldn't log on anymore on Sunday evening. > > In the server room, I booted the machine with

Kernel Oops (was Re: Lots of scary segfaults)

ern.log from Sunday evening: Sep 28 21:11:27 pooh kernel: <1>Unable to handle kernel NULL pointer dereference at virtual address 0004 Sep 28 21:11:27 pooh kernel: printing eip: Sep 28 21:11:27 pooh kernel: c013f765 Sep 28 21:11:27 pooh kernel: *pde = Sep 28 21:11:27 pooh k

Re: kernel oops playing sound -- sound now wedged

27;t helpful. As for compiling mplayer myself: 1. It shouldn't be relevant to a kernel oops, and 2. I've done so, and seen no performance difference between my package and Christian's "k7" series. -- Carl Fink [EMAIL PROTECTED] Jabootu's Ministe

Re: kernel oops playing sound -- sound now wedged

30 nitpicking kernel: printing eip: >Jul 19 07:41:30 nitpicking kernel: df935efb >Jul 19 07:41:30 nitpicking kernel: Oops: >Jul 19 07:41:30 nitpicking kernel: CPU:0 >Jul 19 07:41:30 nitpicking kernel: EIP:0010:[]Not >tainted >Jul 19 07:41:30 nitpic

kernel oops playing sound -- sound now wedged

35efb Jul 19 07:41:30 nitpicking kernel: Oops: Jul 19 07:41:30 nitpicking kernel: CPU:0 Jul 19 07:41:30 nitpicking kernel: EIP:0010:[]Not tainted Jul 19 07:41:30 nitpicking kernel: EFLAGS: 00010202 Jul 19 07:41:30 nitpicking kernel: eax: df935efb ebx: 0002

Re: [SOLVED] System freeze after random program crashes associated with kernel oops

On Thu, Jun 12, 2003 at 12:38:20PM +0200, Kristoffer Erlandsson wrote: > I'm guessing time will tell if this memory module was the only/real > problem. I will reply here after I've tested the computer and am sure, > so you all get to know how it went. Hello again, Now my computer has been running

Re: System freeze after random program crashes associated with kernel oops

On Wed, Jun 11, 2003 at 05:12:48PM -0400, Derrick 'dman' Hudson wrote: > On Tue, Jun 10, 2003 at 10:43:55AM +0200, Kristoffer Erlandsson wrote: > [...] > > | Western Digital IDE ATA-100 60GB 7200RPM 2MB cache (WD600BB) (Running > | one ntfs partition and one ext2 with the operating system in quest

Re: System freeze after random program crashes associated with kernel oops

On Tue, Jun 10, 2003 at 10:43:55AM +0200, Kristoffer Erlandsson wrote: [...] | Western Digital IDE ATA-100 60GB 7200RPM 2MB cache (WD600BB) (Running | one ntfs partition and one ext2 with the operating system in question | on) Are you, by any chance, trying to read from the NTFS partit

System freeze after random program crashes associated with kernel oops

efault) -m /usr/src/linux-2.4.20/System.map (specified) Jun 8 15:22:15 n14 kernel: Unable to handle kernel NULL pointer dereference at virtual address 0004 Jun 8 15:22:15 n14 kernel: c01412bb Jun 8 15:22:15 n14 kernel: *pde = Jun 8 15:22:15 n14 kernel: Oops: Jun 8 15:22:15

Re: ALSA: Kernel Oops...

On Sun, 1 Jun 2003 17:57:04 +0200 Stanley Jaddoe <[EMAIL PROTECTED]> wrote: > Yes, that's true. > I did that because a few day's ago it was impossible to compile the kernel > using gcc-3.3. > > (See also this thread: > %

Re: ALSA: Kernel Oops...

Op zondag 1 juni 2003 16:47, schreef Elimar Riesebieter: > Is that because your Kernel was compiled with gcc-2.95 ad the > alsa-modules with te sid standard gcc-3.3? > Yes, that's true. I did that because a few day's ago it was impossible to compile the kernel using gcc-3.3. (See also this threa

Re: ALSA: Kernel Oops...

On Sun, 01 Jun 2003 the mental interface of DJTB told: > Hi, > > I switched to unstable (from testing) a week ago, and since then, I can't get > ALSA working for my ICE1712 chip. > > This is what I did: > - I downloaded alsa-source, to build a kernel module. (using make-kpkg > modules_image)

ALSA: Kernel Oops...

ddress Jun 1 14:43:41 P2 kernel: printing eip: Jun 1 14:43:41 P2 kernel: c0112703 Jun 1 14:43:41 P2 kernel: Oops: Jun 1 14:43:41 P2 kernel: CPU:0 Jun 1 14:43:41 P2 kernel: EIP:0010:[__wake_up+51/160]Not tainted Jun 1 14:43:41 P2 kernel: EFLAGS: 00010097 Jun 1 14:43:41 P2 ke

ALSA: Kernel Oops...

ddress Jun 1 14:43:41 P2 kernel: printing eip: Jun 1 14:43:41 P2 kernel: c0112703 Jun 1 14:43:41 P2 kernel: Oops: Jun 1 14:43:41 P2 kernel: CPU:0 Jun 1 14:43:41 P2 kernel: EIP:0010:[__wake_up+51/160]Not tainted Jun 1 14:43:41 P2 kernel: EFLAGS: 00010097 Jun 1 14:43:41 P2 ke

Re: Where to report kernel Oops in debian-stable?

on Mon, Nov 05, 2001 at 02:32:33PM +0100, Clemens Dumat ([EMAIL PROTECTED]) wrote: > Hi, > > where should i report a kernel oops in debian stable? > > The kernel is compiled by me from the sources in kernel-source-2.2.19-2, > because there is no precompiled kernel in -stable

Re: Where to report kernel Oops in debian-stable?

On Mon, Nov 05, 2001 at 02:32:33PM +0100, Clemens Dumat wrote: > Hi, > > where should i report a kernel oops in debian stable? > > The kernel is compiled by me from the sources in kernel-source-2.2.19-2, > because there is no precompiled kernel in -stable which supports SMP.

Where to report kernel Oops in debian-stable?

Hi, where should i report a kernel oops in debian stable? The kernel is compiled by me from the sources in kernel-source-2.2.19-2, because there is no precompiled kernel in -stable which supports SMP. So: should i report it to a generic kernel bug list (and which one would apply), or should

Re: Kernel Oops

ess c000 > Sep 9 16:48:13 zoroport kernel: current->tss.cr3 = 00101000, %cr3 = > 00101000 > Sep 9 16:48:13 zoroport kernel: *pde = 00102067 > Sep 9 16:48:13 zoroport kernel: *pte = > Sep 9 16:48:13 zoroport kernel: Oops: > Sep 9 16:48:13 zoroport kernel:

Kernel Oops

:48:13 zoroport kernel: *pte = Sep 9 16:48:13 zoroport kernel: Oops: Sep 9 16:48:13 zoroport kernel: CPU:0 and /var/log/messages: Sep 9 12:03:40 zoroport kernel: ttyS00 at 0x03f8 (irq = 4) is a 16450 Sep 9 12:03:40 zoroport kernel: ttyS01 at 0x02f8 (irq = 3) is a 16450

Kernel oops.

Hello, I have sent a question concerning some problems I was having with my machine. As I suspected, the reason was the IDE patch I got from : http://www.kernel.org/pub/linux/kernel/people/hedrick/ It contains an old version of the ALI V driver (beta2). I got a newer one (beta3) from: http://ww

Kernel oops.

19:09:05 leia kernel: Unable to handle kernel NULL pointer dereference at virtual address 007e Jun 14 19:09:05 leia kernel: current->tss.cr3 = 04d4c000, %cr3 = 04d4c000 Jun 14 19:09:05 leia kernel: *pde = 0000 Jun 14 19:09:05 leia kernel: Oops: Jun 14 19:09:05 leia kernel: CPU:0

kernel 'oops'

I recompiled my kernel (2.0.34...straight from the installation) to add sound support (NOT as a module), and when I boot to that kernel, I see, in the rapidly passing stuff, a phrase resembling 'unable to..(something).. ISOLATE ..(something) and then one 'oops' message in it's entirety. dmesg i

Re: Help Kernel Oops!

[EMAIL PROTECTED] wrote: > > How do I interpret this kernel debugging output? > How do I learn to interpret kernel debugging output? > How do I fix my system so I don't need to learn to interpret kernel > debugging output? By UTSL'ing; however > Unable to handle kernel paging request at

Re: Help Kernel Oops!

In article <[EMAIL PROTECTED]> you wrote: : Sorry, there's little to be learned from raw kernel OOPS messages : without seeing the full system and kernel configurations and versions. : (As far as I know.) There's some detail in the kernel documentation about reporting OOPS me

Re: Help Kernel Oops!

ppening? Sorry, there's little to be learned from raw kernel OOPS messages without seeing the full system and kernel configurations and versions. (As far as I know.) -- Ben Pfaff <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Senders of unsolicited commer

Help Kernel Oops!

How do I interpret this kernel debugging output? How do I learn to interpret kernel debugging output? How do I fix my system so I don't need to learn to interpret kernel debugging output? This is infrequently occurring at unknown times on an lightly loaded system, i.e. just debian-distributed cr