Re: Hardware Error Messages

On 6 Jan 2025 10:52 -0500, from d...@djph.net (Dan Purgert): >> Message from syslogd@piglit at Jan 5 02:49:03 ... >> kernel:[1064021.151590] [Hardware Error]: Corrected error, no action >> required. > > This just looks like a notification sent to TTY1 (or where-ever you've > got an active sessio

Re: Hardware Error Messages

On Jan 06, 2025, Michael wrote: >- I have a Debian Bullseye desktop PC. From time to time I receive >several Hardware Error Messages which begin with a Hardware Error Message >of the form :- > > Message from syslogd@piglit at Jan 5 02:49:03 ... > kernel:[1064021

Hardware Error Messages

- I have a Debian Bullseye desktop PC. From time to time I receive several Hardware Error Messages which begin with a Hardware Error Message of the form :- Message from syslogd@piglit at Jan 5 02:49:03 ... kernel:[1064021.151590] [Hardware Error]: Corrected error, no action required

Re: NUT and Eaton UPS produce a lot of error messages

Stefan Schumacher wrote: > Hello > > I recently bought a small UPS by Eaton in order to prevent my > btrfs-fileserver (running Debian 12 Bookworm, which is also the source > of my nut-installation) from shutting down abruptly while writing > something important during a power loss. I have found v

NUT and Eaton UPS produce a lot of error messages

I set and then post the errors of nut-monitor and nut server. I hope someone can help fix the underlying problem behind these error messages. lsusb shows the UPS: Bus 001 Device 003: ID 0463: MGE UPS Systems UPS So I made this changes to ups.conf [Eaton] driver = usbhid-ups port = auto vendorid =

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On 2023-12-14 14:04:08 -0500, Greg Wooledge wrote: > On Thu, Dec 14, 2023 at 05:14:28PM +0100, Vincent Lefevre wrote: > > I have the latest version!!! I recall that this is a Debian/unstable > > machine, which I upgrade regularly. So, everytime I get such an error, > > I have the latest client. >

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On Thu, Dec 14, 2023 at 05:14:28PM +0100, Vincent Lefevre wrote: > I have the latest version!!! I recall that this is a Debian/unstable > machine, which I upgrade regularly. So, everytime I get such an error, > I have the latest client. Just for the record, saying you have the "latest" version of

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

Vincent Lefevre wrote: > I have the latest version!!! I recall that this is a Debian/unstable > machine, which I upgrade regularly. So, everytime I get such an error, > I have the latest client. > > Note also that this is an error that occurs randomly. Then I'm sorry, that I can't help you more o

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On 2023-12-14 17:03:10 +0100, Klaus Singvogel wrote: > Vincent Lefevre wrote: > > Since 2 years (from early 2022 to 2023-11-26), I've got recurrent > > errors like > > > > kex_exchange_identification: read: Connection reset by peer > > Connection reset by x.x.x.x port 22 > > This sounds most like

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

Vincent Lefevre wrote: > Since 2 years (from early 2022 to 2023-11-26), I've got recurrent > errors like > > kex_exchange_identification: read: Connection reset by peer > Connection reset by x.x.x.x port 22 This sounds most likely that your SSH client (program at your local machine) has an outda

openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

Since 2 years (from early 2022 to 2023-11-26), I've got recurrent errors like kex_exchange_identification: read: Connection reset by peer Connection reset by x.x.x.x port 22 or kex_exchange_identification: Connection closed by remote host Connection closed by x.x.x.x port 22 But yesterday, the

Re: broadcast error messages, unofficial Debian 12

Thank you, I'd never heard of Zutty before this Debian turned up using it as a default terminal. Normally I use rxvt, on trying harder rxvt and xterm both installed and don't seem to have the problem. At first I thought I was running under Wayland so I was maybe stuck with Zutty. But there's no

Hardware Error Messages

I have a Desktop PC running Debian 11. A few days ago I found the following error messages on an xterm window running in the background :- Message from syslogd@piglit at Sep 28 09:44:25 ... kernel:[51369.604961] [Hardware Error]: Deferred error, no action required. Message from syslogd@piglit

Re: SMART error messages being sent to the wrong address

On 2023-10-05, Gary Dale wrote: > Other mail from that server is being sent properly. It's just the SMART > messages that are going to the wrong place. smartd.conf can have a -M exec option to call another script instead of simple mail. Do you have one? smartd can get some options from /etc/defau

Re: SMART error messages being sent to the wrong address

in it. This latter attribute led to it being made into a file server and renamed BigData. The problem I'm having is that SMART error messages are being sent to root@fanny. instead of to me. /etc/aliases has all mail to root going to me, but because this addressed to root on a machine with a diff

Re: SMART error messages being sent to the wrong address

On 2023-10-04 03:22, to...@tuxteam.de wrote: On Wed, Oct 04, 2023 at 02:43:36AM -0400, Jeffrey Walton wrote: [...] $ sudo su - ...better spelt these days as "sudo -i" (or "sudo -s"), see sudo(1)'s man page. Or sudo bash - or whatever your preferred shell is.

Re: SMART error messages being sent to the wrong address

On 2023-10-03 22:31, Greg Wooledge wrote: On Tue, Oct 03, 2023 at 09:02:39PM -0500, John Hasler wrote: Add a CNAME record to your DNS. Mail delivery is supposed to ignore CNAME records. Perhaps you meant to say an MX record. But either way, the OP's question is still not answered -- where is

Re: SMART error messages being sent to the wrong address

On 2023-10-03 23:39, Charles Curley wrote: On Tue, 3 Oct 2023 20:57:57 -0400 Gary Dale wrote: I can't find where the e-mail address is being set. Tracing down the smartmontools config files didn't turn up any obvious problems. The email address is set with the -m option in the file /etc/smart

Re: SMART error messages being sent to the wrong address

On Wed, Oct 04, 2023 at 02:43:36AM -0400, Jeffrey Walton wrote: [...] > $ sudo su - ...better spelt these days as "sudo -i" (or "sudo -s"), see sudo(1)'s man page. > $ grep -iIR fanny /etc If you are sudoing just for one command, even better: sudo grep ... will do. Besides saving q

Re: SMART error messages being sent to the wrong address

attribute led to it being made into a file server and renamed > BigData. > > The problem I'm having is that SMART error messages are being sent to > root@fanny. instead of to me. /etc/aliases has all mail to > root going to me, but because this addressed to root on a machine with a

Re: SMART error messages being sent to the wrong address

On Tue, 3 Oct 2023 20:57:57 -0400 Gary Dale wrote: > I can't find where the e-mail address is being set. Tracing down the > smartmontools config files didn't turn up any obvious problems. The email address is set with the -m option in the file /etc/smartd.conf. I'd check that to see if you chan

Re: SMART error messages being sent to the wrong address

On Tue, Oct 03, 2023 at 09:02:39PM -0500, John Hasler wrote: > Add a CNAME record to your DNS. Mail delivery is supposed to ignore CNAME records. Perhaps you meant to say an MX record. But either way, the OP's question is still not answered -- where is the recipient address configured? My guess

Re: SMART error messages being sent to the wrong address

Add a CNAME record to your DNS. -- John Hasler j...@sugarbit.com Elmwood, WI USA

SMART error messages being sent to the wrong address

The problem I'm having is that SMART error messages are being sent to root@fanny. instead of to me. /etc/aliases has all mail to root going to me, but because this addressed to root on a machine with a different name, it goes out and I only get the message when it bounces (because the machi

Re: Error Messages

Is it possible that the CPU or motherboard could cause the problem ?

Re: Cable colors and urban legends (was: Error Messages)

On 6/3/23 15:18, Roy J. Tellason, Sr. wrote: On Friday 02 June 2023 04:03:48 pm gene heskett wrote: And I'll repeat, I am a CET, something that probably less than 5% of the working EE's could pass that test. CET's are a bit rare, I've yet to meet another on the net. Uh, yes you have... (Cert

Re: Cable colors and urban legends (was: Error Messages)

On Friday 02 June 2023 04:03:48 pm gene heskett wrote: > And I'll repeat, I am a CET, something that probably less than 5% of the > working EE's could pass that test. CET's are a bit rare, I've yet to > meet another on the net. Uh, yes you have... (Certificate PA-230 issued in 1981.) -- Memb

Re: Cable colors and urban legends (was: Error Messages)

On 6/2/23 11:33, Stefan Monnier wrote: And, strange as it sounds, replace any "hot red" aka "magenta" sata cable with some other color. I am a CET and known to me since the 1970's, that color of insulation dye will in time, convert the copper of the conductor into a rust colored powder, and that

Re: Cable colors and urban legends (was: Error Messages)

On 6/2/23 15:01, James H. H. Lampert wrote: On 6/2/23 11:33 AM, Stefan Monnier wrote: This is very hard to believe.  I'm willing to believe that there have been insulation dyes that have proved problematic, but if you've encountered those problems in the 70s I find it *really* odd that it would

Re: Cable colors and urban legends (was: Error Messages)

On 6/2/23 11:33 AM, Stefan Monnier wrote: This is very hard to believe. I'm willing to believe that there have been insulation dyes that have proved problematic, but if you've encountered those problems in the 70s I find it *really* odd that it would still affect cables from this century (e.g.

Cable colors and urban legends (was: Error Messages)

> And, strange as it sounds, replace any "hot red" aka "magenta" sata cable > with some other color. I am a CET and known to me since the 1970's, that > color of insulation dye will in time, convert the copper of the conductor > into a rust colored powder, and that is a poor conductor. This is ve

Re: Error Messages

On 6/2/23 09:09, gene heskett wrote: On 6/2/23 06:27, David wrote: On Thu, 1 Jun 2023 at 18:43, Mick Ab wrote: Recently, Hardware error messages such as the following have appeared every few weeks :- Hi, given that you say these sympoms appear and disappear, the first and easy thing I

Re: Error Messages

On 02/06/2023 13:36, Charles Curley wrote: On Fri, 2 Jun 2023 12:01:10 +0100 Mick Ab wrote: Ram :- I don't know the make of the Ram - someone built the PC for me. 16GB DDR4-3200MHz RAM (2 x 8GB sticks, I understand You may be able to get the make of the RAM (and more) with: dmidecode | l

Re: Error Messages

On 6/2/23 06:27, David wrote: On Thu, 1 Jun 2023 at 18:43, Mick Ab wrote: Recently, Hardware error messages such as the following have appeared every few weeks :- Hi, given that you say these sympoms appear and disappear, the first and easy thing I would try, is to re-seat (ie disconnect

Re: Error Messages

On Fri, 2 Jun 2023 12:01:10 +0100 Mick Ab wrote: > Ram :- > > I don't know the make of the Ram - someone built the PC for me. > > 16GB DDR4-3200MHz RAM (2 x 8GB sticks, I understand You may be able to get the make of the RAM (and more) with: dmidecode | less then search ('/') on Memory Devi

Re: Error Messages

On Fri, 2 Jun 2023 at 11:01, Mick Ab wrote: > > Thanks for all the replies to the Error Messages. > > I don't know how you find which disk is referred to by ata5. ls -l /dev/disk/by-path | grep 'ata-5' > I think dm-0 is a reference to a Raid setup. To get the UUI

Re: Error Messages

oting to memtest86+ not always work, especially if you are using EFI booting mode. Ask if you need any assistance with this. On 02/06/2023 12:01, Mick Ab wrote: Thanks for all the replies to the Error Messages. I don't know how you find which disk is referred to by ata5. I think dm-0 is a re

Re: Error Messages

Thanks for all the replies to the Error Messages. I don't know how you find which disk is referred to by ata5. I think dm-0 is a reference to a Raid setup. Other information about my hardware and rebooting :- I have two 1 TB hard drives arranged as a RAID 1 array. The power supply :- Co

Re: Error Messages

On Thu, 1 Jun 2023 at 18:43, Mick Ab wrote: > Recently, Hardware error messages such as the following have > appeared every few weeks :- Hi, given that you say these sympoms appear and disappear, the first and easy thing I would try, is to re-seat (ie disconnect and reconnect) ever

Re: Error Messages

On Fri, 2 Jun 2023 06:32:51 +0200 wrote: > > > > That sounds like your hard drive has run out of space. Running free > > should tell you which one(s)? are out of space. > > Probably typo: "free" tells you about RAM. Try "df", best with option > "-h": > > df -h Yes, a mis-remembering. Apol

Re: Error Messages

On Thu, Jun 01, 2023 at 01:11:55PM -0600, Charles Curley wrote: > On Thu, 1 Jun 2023 19:42:27 +0100 > Mick Ab wrote: > > > May 27 13:58:08 piglit kernel: [2083218.337088] EXT4-fs warning > > (device dm-0): ext4_dirblock_csum_verify:400: inode #53: comm opera: > > No space for directory leaf check

Re: Error Messages

Mick Ab wrote: > I run a desktop PC with Debian 11, Ryzen 5 5600x CPU and > MSI-B550 A Pro motherboard. > > Recently, Hardware error messages such as the following have > appeared every few weeks :- > > And around the time of the error messages on the 22nd May, the

Re: Error Messages

On Thu, 1 Jun 2023 19:42:27 +0100 Mick Ab wrote: > May 27 13:58:08 piglit kernel: [2083218.337088] EXT4-fs warning > (device dm-0): ext4_dirblock_csum_verify:400: inode #53: comm opera: > No space for directory leaf checksum. Please run e2fsck -D. > May 27 13:58:08 piglit kernel: [2083218.337091]

Re: Error Messages

On 01/06/2023 19:42, Mick Ab wrote: Any thoughts about why the above is happening, please ? Everything is failing, from CPU caches, hard drive SATA link, to checksum errors in the filesystem. Could be failing PSU, what make and model is it, how old? Also it could be RAM issues. Motherboard bio

Error Messages

I run a desktop PC with Debian 11, Ryzen 5 5600x CPU and MSI-B550 A Pro motherboard. Recently, Hardware error messages such as the following have appeared every few weeks :- And around the time of the error messages on the 22nd May, the syslog extracts say: May 22 23:11:51 piglit kernel

Re: Data Error Messages

Hi Mick, Attach full dmesg output. On 27/05/2023 19:50, Mick Ab wrote: A desktop PC is running Debian 11 with an AMD Ryzen CPU. The system has been running well, but now the following error messages have been seen :- Message from syslogd@piglit at May 27 13:58:09 ...   kernel

Re: Data Error Messages

Mick Ab wrote: > A desktop PC is running Debian 11 with an AMD Ryzen CPU. > > The system has been running well, but now the following error messages > have been seen :- > > Message from syslogd@piglit at May 27 13:58:09 ... > kernel:[2083218.760570] EXT4-fs (dm-0): fail

Data Error Messages

A desktop PC is running Debian 11 with an AMD Ryzen CPU. The system has been running well, but now the following error messages have been seen :- Message from syslogd@piglit at May 27 13:58:09 ... kernel:[2083218.760570] EXT4-fs (dm-0): failed to convert unwritten extents to written extents

"Failed unmounting "/{root,var/cache} error messages when shutting down

Hi. When I shutdown or halt my laptop, I see error messages like: [FAILED] Failed unmounting /root. [⋮] [FAILED] Failed unmounting /var/cache. [⋮] [ OK ] Reached target Unmount All Filesystems. [ OK ] Reached target Final Step. Starting halt... My

Re: Obscure error messages from ACPI BERT in dmesg

Hi, Semih Ozlem wrote: > whenever I logon and have more than a few pages in > firefox open, suddenly my memory usage (memory is 3.7 GiB as displayed by > ubuntu system monitor) is around 70 and 80 percent. If I open a few more > pages it jumps. If it reaches 100 % the computer freezes. Well, yes,

Obscure error messages from ACPI BERT in dmesg

is a facility where firmware can store error messages which it deems at risk of being not delivered via the normal error message channels of a running OS. [0.006446] ACPI: BERT 0x89F05608 30 (v01 INTEL EDK2 0001 INTL 0001) ... [0.893410] BERT: Error records from pre

Encrypted lvm error messages at boot

bian-buster-vg" It works but I would like to get rid of those error messages. Any thoughts on how to do that is appriciated? -- John Doe

Re: debian NETINST installer problem - Nonsense error messages that don't indicate real problem

On Thu 26 Jan 2017 at 13:34:29 +0100, Jochen Spieker wrote: > Peter Bradstreet: > > Package: installer > > Version: 8.7.1 > > > > This isn’t a ‘package’ per say… not sure what group it goes to > > There's a "debian-installer" pseudo package that you can use to report > bugs. There is also a p

Re: debian NETINST installer problem - Nonsense error messages that don't indicate real problem

Peter Bradstreet: > Package: installer > Version: 8.7.1 > > This isn’t a ‘package’ per say… not sure what group it goes to There's a "debian-installer" pseudo package that you can use to report bugs. J. -- It is not in my power to change anything. [Agree] [Disagree]

debian NETINST installer problem - Nonsense error messages that don't indicate real problem

Package: installer Version: 8.7.1 This isn’t a ‘package’ per say… not sure what group it goes to There’s a class of error messages being returned by the Debian Installer that are totally bogus and misleading. I was doing a NETINST on VirtualBox, version 5.0.32 r112930 on a Apple MacBook

Re: apt-get error messages

On Fri, Dec 11, 2015 at 11:27:15AM -0500, kamaraju kusumanchi wrote: > On Tue, Dec 8, 2015 at 8:47 AM, Tony van der Hoff wrote: > > On 08/12/15 13:41, Chris Bannister wrote: > > > >> *groan* *sigh* ... I wonder why there's not a 'dpkg > >> --print-architectures' which prints out *all* the architec

Re: apt-get error messages

At face value I'd assumed Tony was reflecting on the freedom a user has to make something work how they want. I didn't consider it as demanding, because unless he had offered to create the features or rally the developers himself or point the OP to another list, and assuming Tony wasn't overwhelme

Re: apt-get error messages

On Tue, Dec 8, 2015 at 8:47 AM, Tony van der Hoff wrote: > On 08/12/15 13:41, Chris Bannister wrote: > >> *groan* *sigh* ... I wonder why there's not a 'dpkg >> --print-architectures' which prints out *all* the architectures it knows >> about. >> > Because you haven't written it yet? > IMHO this

Re: apt-get error messages

On Tue, Dec 08, 2015 at 01:47:19PM +, Tony van der Hoff wrote: > On 08/12/15 13:41, Chris Bannister wrote: > > >*groan* *sigh* ... I wonder why there's not a 'dpkg > >--print-architectures' which prints out *all* the architectures it knows > >about. > > > Because you haven't written it yet? N

Re: apt-get error messages

On 08/12/15 13:41, Chris Bannister wrote: *groan* *sigh* ... I wonder why there's not a 'dpkg --print-architectures' which prints out *all* the architectures it knows about. Because you haven't written it yet? -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |

Re: apt-get error messages

On Mon, Dec 07, 2015 at 06:48:45AM +0100, Matthias Bodenbinder wrote: > Am 06.12.2015 um 22:47 schrieb Klaus Jantzen: > > dpkg --remove-architecture i368 > > apt-get update > > > > But I cannot add the correct architecture: > > > > dpkg --add-architecture i386 > > apt-get update > > dpkg --print-

Re: apt-get error messages

Am 06.12.2015 um 22:47 schrieb Klaus Jantzen: > On 12/05/2015 08:56 PM, Myscelus wrote: >> On 12/05/2015 08:55 PM, Klaus Jantzen wrote: >>> Hi, >>> >>> due to a typing error - I wanted to say 'dpkg --add-architecture i386' >>> but wrote '

Re: apt-get error messages

On 12/05/2015 08:56 PM, Myscelus wrote: > On 12/05/2015 08:55 PM, Klaus Jantzen wrote: >> Hi, >> >> due to a typing error - I wanted to say 'dpkg --add-architecture i386' >> but wrote 'i368' - >> I get the following error messages when running a

Re: apt-get error messages

> Hi, > > due to a typing error - I wanted to say 'dpkg --add-architecture i386' > but wrote 'i368' - > I get the following error messages when running apt-get update: > > > ... > > W: Failed to fetch > http://download.virtualbox.org/vi

Re: apt-get error messages

On 12/05/2015 08:55 PM, Klaus Jantzen wrote: Hi, due to a typing error - I wanted to say 'dpkg --add-architecture i386' but wrote 'i368' - I get the following error messages when running apt-get update: ... W: Failed to fetch http://download.virtualbox.org/virtualbo

apt-get error messages

Hi, due to a typing error - I wanted to say 'dpkg --add-architecture i386' but wrote 'i368' - I get the following error messages when running apt-get update: ... W: Failed to fetch http://download.virtualbox.org/virtualbox/debian/dists/vivid/Release Unable to find exp

make-kpkg revision rules not following documentaton, confusing error messages

I was attempting to compile my own kernel as a debian package, following these directions: https://www.debian.org/releases/jessie/i386/ch08s06.html.en When I got to the point where it has you run make-kpkg itself, where it suggests the following command: # fakeroot make-kpkg --initrd --revision

Re: PCIe debugging error messages - kern.log

I have checked to make sure Debug hasn't been redirected; I will ask the debian-kernel list and see if I can find anything there. Thanks for the help folks. --Andrew On Mon, Jul 30, 2012 at 12:51 PM, Henrique de Moraes Holschuh wrote: > On Mon, 30 Jul 2012, Andrew Peng wrote: >> I've been workin

Re: PCIe debugging error messages - kern.log

On Mon, 30 Jul 2012, Andrew Peng wrote: > I've been working with the Intel E1000 development team in trying to > find the cause of a hardware hang in my kern.log: > > Jul 24 02:49:45 gaia kernel: [806292.204500] e1000e :02:00.0: > eth1: Detected Hardware Unit Hang: Meh, we've just seen those

Re: PCIe debugging error messages - kern.log

On Mon, 30 Jul 2012 08:43:56 -0500, Andrew Peng wrote: > I've been working with the Intel E1000 development team in trying to > find the cause of a hardware hang in my kern.log: (...) I've read the report you posted at "e1000-devel" mailing list. > One of the steps to find the cause of this is

PCIe debugging error messages - kern.log

I've been working with the Intel E1000 development team in trying to find the cause of a hardware hang in my kern.log: Jul 24 02:49:45 gaia kernel: [806292.204500] e1000e :02:00.0: eth1: Detected Hardware Unit Hang: Jul 24 02:49:45 gaia kernel: [806292.204503] TDH <8c> Jul 2

Re: Error messages on ".xsession-errors"

On Sun, 08 Jul 2012 03:14:34 -0300, Davi Garcia wrote: > Hey guys, Hello. Please, avoid using html posts, they are badly read from some clients. > After many years, I finally returned to Debian. Now I'm using Debian > Wheeze on my Thinkpad W510 for around 1 week now. The system is updated > and

Error messages on ".xsession-errors"

Hey guys, After many years, I finally returned to Debian. Now I'm using Debian Wheeze on my Thinkpad W510 for around 1 week now. The system is updated and it is being shown as a very stable platform, even though this branch is called Testing. I have being checking the logs, looking for errors and

Re: Warning/error messages

On Sun, 01 Jul 2012 08:11:14 -0400, brian wrote: > On 07/01/2012 05:35 AM, Camaleón wrote: >> On Sun, 01 Jul 2012 04:16:23 -0400, brian wrote: >> >>> I'm getting an occasional error message come up while using my PC. An >>> example is >> >> (...) >> >>> Message from syslogd@brian at Jul 1 03:51:1

Re: Warning/error messages

On 07/01/2012 05:35 AM, Camaleón wrote: On Sun, 01 Jul 2012 04:16:23 -0400, brian wrote: I'm getting an occasional error message come up while using my PC. An example is (...) Message from syslogd@brian at Jul 1 03:51:12 ... kernel:[ 4686.825066] Call Trace: Better if you upload the full

Re: Warning/error messages

On 2012-07-01, brian wrote: > > Does anyone have any ideas, please? The byte string looks a bit > specific to try plugging it into Google, which is my usual approach > for error messages that I don't understand. :) I stuck the string into google anyway (in quotes "code:

Re: Warning/error messages

On Sun, 01 Jul 2012 04:16:23 -0400, brian wrote: > I'm getting an occasional error message come up while using my PC. An > example is (...) > Message from syslogd@brian at Jul 1 03:51:12 ... > kernel:[ 4686.825066] Call Trace: Better if you upload the full segfault at www.pastebin.com so we ca

Warning/error messages

hich is my usual approach for error messages that I don't understand. :) Thanks, Brian. -- 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/4ff00757.5050...@meadows.pair.com

Re: alsa error messages

* Camaleón [111015 17:01 +]: > On Sat, 15 Oct 2011 18:32:36 +0200, Elimar Riesebieter wrote: > [...] > > alsa-tools: > > Installed: (none) > > Candidate: 1.0.24.1-2 > > Version table: > > 1.0.24.1-2 0 > > 990 ftp://ftp.de.debian.org/debian/ unstable/main powerpc > >

Re: alsa error messages

On Sat, 15 Oct 2011 18:32:36 +0200, Elimar Riesebieter wrote: > * Camaleón [111015 15:49 +]: > >> On Sat, 15 Oct 2011 16:28:20 +0100, Richard wrote: (...) >> > Yes that's probably the best thing to do, wait for 1.0.24. where's >> > the best place to watch for package updates on Wheezy ?, al

Re: alsa error messages

* Camaleón [111015 15:49 +]: > On Sat, 15 Oct 2011 16:28:20 +0100, Richard wrote: > > > On Sat, 15 Oct 2011 13:58:12 + (UTC) Camaleón > > wrote: > > (...) > > >> Sorry, I'm afraid I can't be of any help here. > >> > >> If you are not having secondary effects (all works as usual) and i

Re: alsa error messages

On 2011-10-15, Richard wrote: >> >> And are we also meant to infer that something isn't working (what? no >> sound?) or is it only a question of getting rid of the messages (which I >> would describe as informational rather than error messages -- usually >&

Re: alsa error messages

On Sat, 15 Oct 2011 15:49:01 + (UTC) Camaleón wrote: > On Sat, 15 Oct 2011 16:28:20 +0100, Richard wrote: > > > On Sat, 15 Oct 2011 13:58:12 + (UTC) Camaleón > > wrote: > > (...) > > >> Sorry, I'm afraid I can't be of any help here. > >> > >> If you are not having secondary effects (

Re: alsa error messages

On Sat, 15 Oct 2011 16:28:20 +0100, Richard wrote: > On Sat, 15 Oct 2011 13:58:12 + (UTC) Camaleón > wrote: (...) >> Sorry, I'm afraid I can't be of any help here. >> >> If you are not having secondary effects (all works as usual) and it's >> only an annoying output maybe you can wait unti

Re: alsa error messages

On Sat, 15 Oct 2011 13:58:12 + (UTC) Camaleón wrote: > On Sat, 15 Oct 2011 13:30:29 +0100, Richard wrote: > > > On Fri, 14 Oct 2011 15:53:23 + (UTC) Camaleón > > wrote: > > (...) > > >> > Thanks, I'm using the default settings. > >> > >> What a pity... and those messages come from wh

Re: alsa error messages

On Sat, 15 Oct 2011 13:32:16 + (UTC) Curt wrote: > On 2011-10-13, Richard wrote: > > Hi, > > I'm getting some error messages that weren't there in squeeze, they are not > > stopping the application > > from running, but I'd like to get rid of them

Re: alsa error messages

On Sat, 15 Oct 2011 13:30:29 +0100, Richard wrote: > On Fri, 14 Oct 2011 15:53:23 + (UTC) Camaleón > wrote: (...) >> > Thanks, I'm using the default settings. >> >> What a pity... and those messages come from where, exactly? > Hi > its when I start an application called WSJT, which uses a

Re: alsa error messages

On 2011-10-13, Richard wrote: > Hi, > I'm getting some error messages that weren't there in squeeze, they are not > stopping the application > from running, but I'd like to get rid of them. What application would that be? Or am I being stupid or something? An

Re: alsa error messages

On Fri, 14 Oct 2011 15:53:23 + (UTC) Camaleón wrote: > On Fri, 14 Oct 2011 16:34:01 +0100, Richard wrote: > > > On Fri, 14 Oct 2011 15:20:48 + (UTC) Camaleón > > wrote: > > > >> On Thu, 13 Oct 2011 09:40:29 +0100, Richard wrote: > >> &

Re: alsa error messages

On Fri, 14 Oct 2011 16:34:01 +0100, Richard wrote: > On Fri, 14 Oct 2011 15:20:48 + (UTC) Camaleón > wrote: > >> On Thu, 13 Oct 2011 09:40:29 +0100, Richard wrote: >> >> > I'm getting some error messages that weren't there in squeeze, they >> &

Re: alsa error messages

On Fri, 14 Oct 2011 15:20:48 + (UTC) Camaleón wrote: > On Thu, 13 Oct 2011 09:40:29 +0100, Richard wrote: > > > I'm getting some error messages that weren't there in squeeze, they are > > not stopping the application from running, but I'd like to get rid

Re: alsa error messages

On Thu, 13 Oct 2011 09:40:29 +0100, Richard wrote: > I'm getting some error messages that weren't there in squeeze, they are > not stopping the application from running, but I'd like to get rid of > them. Where are the below entries coming from? Are they appearing when

alsa error messages

Hi, I'm getting some error messages that weren't there in squeeze, they are not stopping the application from running, but I'd like to get rid of them. I've use slocate to try and find the file which is being read, but I cant find it. Does anyone known the location and na

Re: Kernel error messages

On 10/09/11 20:36, Mark Panen wrote: Hi, I am getting these kernel error messages in my terminal as well as the pop up window using Squeeze with KDE. Message from syslogd@mark3 at Sep 9 18:58:46 ... kernel:[68340.726914] Oops: [#1] SMP Message from syslogd@mark3 at Sep 9 18:58:46

Re: Kernel error messages

On Sat, 10 Sep 2011 12:36:56 +0200, Mark Panen wrote: > I am getting these kernel error messages in my terminal as well as the > pop up window using Squeeze with KDE. (...) > Message from syslogd@mark3 at Sep 9 18:58:46 ... > kernel:[68340.727092] CR2: fff3 Hum... a

Kernel error messages

Hi, I am getting these kernel error messages in my terminal as well as the pop up window using Squeeze with KDE. Message from syslogd@mark3 at Sep 9 18:58:46 ... kernel:[68340.726914] Oops: [#1] SMP Message from syslogd@mark3 at Sep 9 18:58:46 ... kernel:[68340.726917] last sysfs file

Re: lighttpd: howto move php error messages from error.log to the browser again?

Dirk wrote: > Hello, > > I want the PHP error messages (PHP Notice) to be shown in the browser again. > And not in the error.log file. > > Why? > Because. > > Lighttpd: current version that comes with Debian/Squeeze (x86) > > Thanks > > Dirk > >

lighttpd: howto move php error messages from error.log to the browser again?

Hello, I want the PHP error messages (PHP Notice) to be shown in the browser again. And not in the error.log file. Why? Because. Lighttpd: current version that comes with Debian/Squeeze (x86) Thanks Dirk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of

lighttpd: howto move php error messages from error.log to the browser again?

Hello, I want the PHP error messages (PHP Notice) to be shown in the browser again. And not in the error.log file. Why? Because. Lighttpd: current version that comes with Debian/Squeeze (x86) Thanks Dirk Reply -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a

lighttpd: howto move php error messages from error.log to the browser again?

Hello, I want the PHP error messages (PHP Notice) to be shown in the browser again. And not in the error.log file. Why? Because. Lighttpd: current version that comes with Debian/Squeeze (x86) Thanks Dirk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of

  1   2   3   4   >