Re: SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

[Charles Curley]

On Wed, 24 Jan 2024 07:33:59 +
Tixy  wrote:

> On Tue, 2024-01-23 at 13:34 -0700, Charles Curley wrote:
>  [...]  
> 
> As you've already found out, that's not the latest one, and if I'm not
> mistaken is the one that introduce a wifi bug [1], so that could
> explain it getting stuck in the wifi stuff during shutdown.
> 
> You would probably be OK with the latest Debian 6.1 kernel if you
> don't explicitly want the 6.5 one from backports.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057969
> 

That does indeed sound like the problem I had. Thank you. I think I've
spent enough time on this issue, so I'll stick with the backported
kernel(s) until the next Debian is released (13). Or until something
else goes wrong.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

[Tixy]

On Tue, 2024-01-23 at 13:34 -0700, Charles Curley wrote:
> I went to shut down the machine, and it got stuck trying to shut down
> wpa_supplicant and Network Manager. Ten minutes into the shutdown, I
> finally pulled the plug. A few reboots and shutdowns later, I decided
> to try another kernel. I had recently installed Bookworm from the 12.0
> netinst CD image, so I had the 12.0 kernel, linux-image-6.1.0-9-amd64,
> 6.1.27-1, as my fall-back kernel. I rebooted to that, and was able to
> shut down and boot in quick order.
> 
> So I purged the newer kernel, inux-image-6.1.0-15-amd64, leaving the
> older one in place.

As you've already found out, that's not the latest one, and if I'm not
mistaken is the one that introduce a wifi bug [1], so that could
explain it getting stuck in the wifi stuff during shutdown.

You would probably be OK with the latest Debian 6.1 kernel if you don't
explicitly want the 6.5 one from backports.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057969

-- 
Tixy

Re: SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

[Charles Curley]

On Wed, 24 Jan 2024 09:25:58 +0700
Max Nikulin  wrote:

> On 24/01/2024 03:34, Charles Curley wrote:
> > So I purged the newer kernel, inux-image-6.1.0-15-amd64  
> 
> The current kernel is linux-image-6.1.0-17-amd64
> 
> Perhaps you have not restored your sources.list or apt preferences
> after the accidents with kernel bugs. Check that nothing extra is
> added and nothing is missed in
> 
>  apt policy
> 

Good catch, thank you. I found the problem. sources.list had two src
lines commented out because the installer couldn't verify them. I have
rectified that problem.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

[Max Nikulin]

On 24/01/2024 03:34, Charles Curley wrote:

So I purged the newer kernel, inux-image-6.1.0-15-amd64


The current kernel is linux-image-6.1.0-17-amd64

Perhaps you have not restored your sources.list or apt preferences after 
the accidents with kernel bugs. Check that nothing extra is added and 
nothing is missed in


apt policy

SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

[Charles Curley]

On Sat, 13 Jan 2024 10:19:48 -0700
Charles Curley  wrote:

> I have just installed Bookworm on my ancient Lenovo T520 (2011),
> replacing Bullseye. I suspect the problem is somewhere in the video
> driver chain. Any thoughts on how to proceed further with this?
> 
> Upon trying to run chromium, I get:
> 
> charles@jhegaala:~$ chromium &
> [2] 33609
> charles@jhegaala:~$ libva error:
> /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
> 
> charles@jhegaala:~$

I seem to have solved this problem, entirely by accident.

I went to shut down the machine, and it got stuck trying to shut down
wpa_supplicant and Network Manager. Ten minutes into the shutdown, I
finally pulled the plug. A few reboots and shutdowns later, I decided
to try another kernel. I had recently installed Bookworm from the 12.0
netinst CD image, so I had the 12.0 kernel, linux-image-6.1.0-9-amd64,
6.1.27-1, as my fall-back kernel. I rebooted to that, and was able to
shut down and boot in quick order.

So I purged the newer kernel, inux-image-6.1.0-15-amd64, leaving the
older one in place. I then set up for bookworm backports, and installed
a kernel from backports, linux-image-6.5.0-0.deb12.4-amd64,
6.5.10-1~bpo12+1. Not only does than kernel give me snappy boot and
shutdown, but chromium runs, and show videos. I still get the libva
error message, but chromium runs anyway.

All of which leads me to suspect that the error message was a soviet
herring, as Max Nikulin  suggested elsewhere in
this thread.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

[Max Nikulin]

On 19/01/2024 04:08, Charles Curley wrote:

charles@jhegaala:~$ chromium chrome://gpu
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
^C
Killed
charles@jhegaala:~$

I did a killall -9 in another window to kill it.


Does it happen in the case of a new system user and a new chromium 
profile to ensure settings close to defaults?


Is it possible to create a new tab in the chromium window?

Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

[Max Nikulin]

On 19/01/2024 04:08, Charles Curley wrote:

On Fri, 19 Jan 2024 00:02:44 +0700
Max Nikulin wrote:


Have you faced real issues namely with hardware acceleration?


Other than this, not that I know of.


I do not think the message concerning iHD is related to any real issue. 
I see "oops" in the subject, but perhaps it is caused by something else. 
I recall another thread


SOLVED [was: Chromium under Xfce/bookworm anyone?] Wed, 13 Sep 2023 
20:11:08 +0200

https://lists.debian.org/msgid-search/zqh7peojdoudu...@tuxteam.de


iHD driver is tied first, but your graphics card is too old for it,
so i965 loaded next. I am unsure if it is possible to suppress
attempt to load iHD and so to avoid an error message e.g. by setting
some environment variable.


I see nothing in chromium's rather minimal man page. I also tried
several command line switches in
https://peter.sh/experiments/chromium-command-line-switches/, to no
avail.


The same message is reported by vainfo, so it is not specific to 
chromium. I have not tried a recipe given in


https://wiki.debian.org/HardwareVideoAcceleration#VA-API

Driver selection can be overridden by setting the environment variable
LIBVA_DRIVER_NAME to a specific driver, e.g., LIBVA_DRIVER_NAME=i965 (to
use the driver from i965-va-driver on Bullseye) or LIBVA_DRIVER_NAME=iHD
(to use the driver from intel-media-va-driver on Debian 10/Buster). See
EnvironmentVariables for more details on how to set this environment
variable system-wide or per user.

Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

[Charles Curley]

On Fri, 19 Jan 2024 00:02:44 +0700
Max Nikulin  wrote:

> On 14/01/2024 00:19, Charles Curley wrote:
>  [...]  
> 
>  [...]  
> 
> Have you faced real issues namely with hardware acceleration?

Other than this, not that I know of.

> 
> iHD driver is tied first, but your graphics card is too old for it,
> so i965 loaded next. I am unsure if it is possible to suppress
> attempt to load iHD and so to avoid an error message e.g. by setting
> some environment variable.

I see nothing in chromium's rather minimal man page. I also tried
several command line switches in
https://peter.sh/experiments/chromium-command-line-switches/, to no
avail.

> 
> chrome://gpu may provide more info.
> 

Alas, chromium never gets far enough to deliver useful information.

charles@jhegaala:~$ chromium chrome://gpu
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
^C
Killed
charles@jhegaala:~$ 

I did a killall -9 in another window to kill it.

There are no crash reports.

I looked in the two bug report sites mentioned in the man page for
chromium, and did not see anything that looked relevant.

I tried removing intel-media-va-driver |
intel-media-va-driver-non-free, which required removing va-driver-all.
No go. chromium just sits there as a background process, and I have to
kill it.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

[Max Nikulin]

On 14/01/2024 00:19, Charles Curley wrote:

charles@jhegaala:~$ chromium &
[2] 33609
charles@jhegaala:~$ libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed



charles@jhegaala:~$ vainfo
libva info: VA-API version 1.17.0
libva info: Trying to open
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init
function __vaDriverInit_1_17 libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info:
va_openDriver() returns 1 libva info: Trying to open
/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init
function __vaDriverInit_1_8 libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.17 (libva 2.12.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Sandybridge


Have you faced real issues namely with hardware acceleration?

iHD driver is tied first, but your graphics card is too old for it, so 
i965 loaded next. I am unsure if it is possible to suppress attempt to 
load iHD and so to avoid an error message e.g. by setting some 
environment variable.


chrome://gpu may provide more info.

Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

[Charles Curley]

I have just installed Bookworm on my ancient Lenovo T520 (2011),
replacing Bullseye. I suspect the problem is somewhere in the video
driver chain. Any thoughts on how to proceed further with this?

Upon trying to run chromium, I get:

charles@jhegaala:~$ chromium &
[2] 33609
charles@jhegaala:~$ libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed

charles@jhegaala:~$ ps
PID TTY  TIME CMD
  32502 pts/800:00:00 bash
  32506 pts/800:00:04 emacs
  33609 pts/800:00:00 chromium
  33630 pts/800:00:00 chromium
  33631 pts/800:00:00 chromium
  33633 pts/800:00:00 chromium
  33656 pts/800:00:00 chromium
  33657 pts/800:00:00 chromium
  33688 pts/800:00:00 ps
charles@jhegaala:~$ killall -9 chromium
charles@jhegaala:~$ 
[2]+  Killed  chromium
charles@jhegaala:~$ ps
PID TTY  TIME CMD
  32502 pts/800:00:00 bash
  32506 pts/800:00:04 emacs
  33695 pts/800:00:00 ps
charles@jhegaala:~$ vainfo
libva info: VA-API version 1.17.0
libva info: Trying to open
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init
function __vaDriverInit_1_17 libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info:
va_openDriver() returns 1 libva info: Trying to open
/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init
function __vaDriverInit_1_8 libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.17 (libva 2.12.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Sandybridge
Mobile - 2.4.1 vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264StereoHigh : VAEntrypointVLD
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileNone   : VAEntrypointVideoProc
charles@jhegaala:~$ 

Display is:

root@jhegaala:~# lspci -vs 2.0
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
Core Processor Family Integrated Graphics Controller (rev 09) (prog-if
00 [VGA controller]) Subsystem: Lenovo ThinkPad T520 Flags: bus master,
fast devsel, latency 0, IRQ 28, IOMMU group 0 Memory at f000
(64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit,
prefetchable) [size=256M] I/O ports at 6000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

root@jhegaala:~# grep 'model name' /proc/cpuinfo 
model name  : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
model name  : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
model name  : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
model name  : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
root@jhegaala:~# 



-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: xfce4 widget problem -- oops

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



‐‐‐ Original Message ‐‐‐
On Sunday, September 13, 2020 6:49 PM, ghe2001  wrote:

I'm in ZIP 80303, not 30303.  Weather-util works fine with the correction.  
Sorry...

--
Glenn English


-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAGBQJfXm0+ACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDJ45Qf8CbKZzSD4jbAmAWQLn7k2fV6MgYdB/9QeLIcIlWOu4wowWFgz
eWw0yAwrPS0oq3Q+Rw0+VbkWBTYF6+UiWQsA8vSFLkPl2K7lDZHNBUOPJKa8
fhLW1Jdaw1fvtwoObF2t56qlHZHWvpUUerJ+TeUgpet4evHS92AnYW48cwyk
m+/RsOvm050tZG0mXOW1QMI/VnS1KloQNHMk9IwBTwalc4hkLncAMHeXSOjh
FR0zQjOyisQGAQYA6Ix/sNs+z1xN+oAo/bmuNDnCaZV6fgXqLXPbn5k+WQGo
M0nxqMWYFjiPcTxTzZamnX9suVjtVCMlXQEHtj8ujo0msnCqzZLTWw==
=7tVO
-END PGP SIGNATURE-

Re: Re: linux-image-5.7.0-1-amd64: Oops on kernel (NULL pointer dereference) after NFS is mounted on client

[Robin Gutöhrlein]

Hi,
yes I tried it. I typed the whole "Oops" screen, tried to send it, but
it would not. The report it saved into a file was scrambled...
Best regards

Re: linux-image-5.7.0-1-amd64: Oops on kernel (NULL pointer dereference) after NFS is mounted on client

[riveravaldez]

On 7/24/20, Robin Gutöhrlein  wrote:
> Hello,
>
> my server (Debian bullseye) is crashing after i mount a nfs (with
> kerberos) share on a client machine (same debian). I have no idea how
> to file the bug (and where it belongs). I can't use the reportbug tool
> since I do not have a MTA configured.

Hi, just in case: a little time ago I installed reportbug and reported
a bug and the MTA was not a previous condition. Have you given it a
try?

Best regards

linux-image-5.7.0-1-amd64: Oops on kernel (NULL pointer dereference) after NFS is mounted on client

[Robin Gutöhrlein]

Hello,

my server (Debian bullseye) is crashing after i mount a nfs (with
kerberos) share on a client machine (same debian). I have no idea how
to file the bug (and where it belongs). I can't use the reportbug tool
since I do not have a MTA configured.


BUG: kernel NULL pointer dereference, adress: 10
#PF: supervisor read access in kernel mode
#PF: error_code(0x) -not-present page
PGD0 P4D 0
Oops:  [#1] SMP PTI
...
RIP: 0010:__cgroup_bfp_run_filter_skb+0x26b/0x3d0
...
Call Trace:
  ip_finish_output
  ip_output
  ? __ip_finish_output
  __ip_queue_xmit
  ? __switch_to_asm
  ? __switch_to_asm
  ? __switch_to_asm
  __tcp_transmit_skb
  tcp_write_xmit
  __tcp_push_pending_frames
  inet_shutdown
  svc_delete_xprt
  svc_close_net
  svc_shutdown_net
  nfsd_destroy
  nfsd
  kthread
  ? nfsd_destroy
  ?  kthread_park
  ret_from_fork

Sincerly
Robin

ath10k driver generates kernel oops?

[Bjorn Baron]

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.19.67-2+deb10u2
[   24.412327] Hardware name: LENOVO 80XL/LNVNB161216, BIOS 4WCN29WW
09/30/2017
[   24.412336] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd8/0xf0
[ath10k_core]
[   24.412338] Code: 48 8b 8f 10 02 00 00 48 85 c9 74 27 48 8b 41 28 48
85 c0 74 19 45 31 c0 b9 02 00 00 00 49 8b 31 e8 9d 63 82 dc 48 89 d8 5b
c3 <0f> 0b 31 db 48 89 d8 5b c3 48 8b 0d 68 59 e4 dc eb d0 66 0f 1f 44
[   24.412339] RSP: :a0b9aab03dc0 EFLAGS: 00010246
[   24.412340] RAX:  RBX: a0b9aab03e60 RCX:
a0b9a2621540
[   24.412341] RDX: 85bd8000 RSI: a0b9a2621f2c RDI:
a0b9a2621e38
[   24.412342] RBP:  R08: 0020 R09:

[   24.412343] R10: a0b875c7e420 R11: 01ff R12:
a0b98b1476d0
[   24.412344] R13: a0b9a2621f2c R14: a0b9aab03e48 R15:

[   24.412345] FS:  7fb0bc147780() GS:a0b9aab0()
knlGS:
[   24.412347] CS:  0010 DS:  ES:  CR0: 80050033
[   24.412348] CR2: 7fb0aa004008 CR3: 5d3ce001 CR4:
003606e0
[   24.412348] Call Trace:
[   24.412351]  
[   24.412359]  ath10k_htt_txrx_compl_task+0x363/0xd00 [ath10k_core]
[   24.412365]  ath10k_pci_napi_poll+0x4f/0x100 [ath10k_pci]
[   24.412368]  net_rx_action+0x149/0x3b0
[   24.412372]  __do_softirq+0xde/0x2d8
[   24.412375]  irq_exit+0xba/0xc0
[   24.412377]  do_IRQ+0x7f/0xe0
[   24.412379]  common_interrupt+0xf/0xf
[   24.412380]  
[   24.412382] RIP: 0033:0x7fb0b9cf24ae
[   24.412383] Code: 41 54 c1 ea 08 41 89 f4 31 f6 55 0f b7 d2 53 48 89
fb 48 83 ec 08 e8 c1 f9 ff ff 48 63 e8 85 ed 78 1a 48 03 5b 08 48 03 1c
eb <49> 89 dd 48 83 c4 08 4c 89 e8 5b 5d 41 5c 41 5d c3 90 be 20 00 00
[   24.412384] RSP: 002b:7ffe2f452aa0 EFLAGS: 0207 ORIG_RAX:
ffda
[   24.412386] RAX: 0013 RBX: 7fb0aa004ac0 RCX:
0030
[   24.412387] RDX: 0030 RSI: 0013 RDI:
7fb0aa1f9140
[   24.412387] RBP: 0013 R08: 0013 R09:
0030
[   24.412388] R10: 0014 R11: 7fb0bc30d3e0 R12:
3008
[   24.412389] R13: 7fb0aa1fa48c R14: 303f R15:
3000
[   24.412391] ---[ end trace 2ab80350c843aa30 ]---
[   24.412395] ath10k_pci :02:00.0: failed to pop paddr list: -2
[   32.341851] wlp2s0: deauthenticated from  (Reason:
15=4WAY_HANDSHAKE_TIMEOUT)
[   32.542989] wlp2s0: authenticate with 
[   32.582276] wlp2s0: send auth to  (try 1/3)
[   32.584662] wlp2s0: authenticated
[   32.587723] wlp2s0: associate with  (try 1/3)
[   32.591685] wlp2s0: RX AssocResp from  (capab=0x1411
status=0 aid=1)
[   32.594049] wlp2s0: associated
[   40.523347] wlp2s0: deauthenticated from  (Reason:
15=4WAY_HANDSHAKE_TIMEOUT)
[   45.498442] wlp2s0: authenticate with 
[   45.529899] wlp2s0: send auth to  (try 1/3)
[   45.530535] wlp2s0: authenticated
[   45.537679] wlp2s0: associate with  (try 1/3)
[   45.538877] wlp2s0: RX AssocResp from  (capab=0x1011
status=0 aid=2)
[   45.544682] wlp2s0: associated

I have searched for this issue in the bug tracker at
https://www.debian.org/Bugs/#pkgreport. However I couldn't find another
issue regarding ath10k. Did I search badly, or is this issue not yet
known? If so, should I report this with a package of
linux-image-4.19.0-6-amd64, or firmware-atheros?

Thanks in advance for reply.





NB: Below is some information about my system:

$ uname -a
Linux  4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2
(2019-11-11) x86_64 GNU/Linux

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

$ dpkg --status firmware-atheros
Package: firmware-atheros
Status: install ok installed
Priority: optional
Section: non-free/kernel
Installed-Size: 10856
Maintainer: Debian Kernel Team 
Architecture: all
Multi-Arch: foreign
Source: firmware-nonfree
Version: 20190114-2
Suggests: initramfs-tools
[description omitted]

$ dpkg --status linux-image-4.19.0-6-amd64
Package: linux-image-4.19.0-6-amd64
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 262512
Maintainer: Debian Kernel Team 
Architecture: amd64
Source: linux-signed-amd64 (4.19.67+2+deb10u2)
Version: 4.19.67-2+deb10u2
Replaces: linux-image-4.19.0-6-amd64-unsigned
Depends: kmod, linux-base (>= 4.3~), initramfs-tools (>= 0.120+deb8u2) |
linux-initramfs-tool
Recommends: firmware-linux-free, apparmor
Suggests: li

Re: can't map visual mode copy ("+y) OOPS

[tom arnall]

I forgot to show my debian version. here it is:

:~/$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian


On 7/25/18, tom arnall  wrote:
> bottom line here is that when i map "+y to , it dos not work in
> visual mode. below are the specifics.
>
> Here is output of 'version'
>
> :version
> VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Sep 30 2017 18:21:38)
> Included patches: 1-197, 322, 377-378, 550, 703, 706-707
> Modified by pkg-vim-maintain...@lists.alioth.debian.org
> Compiled by pkg-vim-maintain...@lists.alioth.debian.org
> Huge version without GUI.  Features included (+) or not (-):
>
>
> 1. enter ':vmap  "+y' (to map the visual mode yank)
>
> 2. in blank screen, hit 'i' key (for insert mode)
>
> 3. enter 'now is the time'.
>
> 4. hit  key
>
> 5. hit 'v' key (for visual mode)
>
> 6. hit 'k' key to select the text
>
> 7. do   ( actual result is that editor stays in visual mode;
> expected that it would return to normal mode)
>
> 8. hit 'v' key to exit visual mode
>
> 9. hit 'j' key to move to next line
>
> 10. hit 'p' key to put the selected text (actual result is no change;
> expected that editor would put 'now is the time' in the document)
>

Re: Rien ne se passe après Grub2...oops oubliez la pièce jointe dans le dernier message...

[Sébastien NOBILI]

Bonjour,

Le mardi 03 octobre 2017 à 17:23, lou a écrit :
> J'aimerais savoir ce que fait l'option du noyau "noresume" ?? et si je
> peux laisser l'option au noyau...?

L’option « noresume » dit au noyau de ne pas tenter de reprendre une mise en
veille. Lorsque tu mets en veille (hibernation), l’état de ton système est
enregistré dans la partition swap. Ton noyau va tenter de le restaurer.
J’imagine qu’il y avait des choses incohérentes dedans.

Tu peux laisser l’option, mais dans ce cas, tu ne pourras plus mettre ton
système en veille.

Tu peux aussi tester de redémarrer sans l’option. Normalement ta partition de
swap a dû être réinitialisée…

> Parce que, maintenant, je peux entrer dans ma debian :))

Bonne nouvelle !

Sébastien

Re: Rien ne se passe après Grub2...oops oubliez la pièce jointe dans le dernier message...

[lou]

Le Tue, 3 Oct 2017 17:16:17 +0200,
Sébastien NOBILI  a écrit :

> Le mardi 03 octobre 2017 à 10:48, louis a écrit :
> > Pensez-vous que le screenshot en PJ a à voir avec ce problème?  
> 
> Aaaah, voilà la pièce-jointe :D
> 
> Le « -.mount » est étrange… Un problème avec le contenu de fstab ou
> bien un problème d’interprétation de son contenu par Systemd.
> 
> Pourrais-tu nous envoyer le contenu du fichier « /etc/fstab » de ton
> système Debian (pas celui du LiveCD).
> 
> Si tu as des mots de passe dedans, efface-les avant.
> 
> Sébastien
> 

J'aimerais savoir ce que fait l'option du noyau "noresume" ?? et si je
peux laisser l'option au noyau...?
Parce que, maintenant, je peux entrer dans ma debian :))
MERCI!

Je poste quand même mon fstab... parce que je comprend toujours pas
pourquoi j'étais bloqué au démarrage.???..

Je n'est pas de double entrer UUID ou 2 swap et tout semble normale
pour ma part. J'ai une ligne commenter et s'est une partition chiffré
que je monte au moment où je suis dans ma debian et non au boot. 

> vous n'auriez pas branché un disk ou une vm ou un tail ou une usb
> chiffrée avant en oubliant de déconnectez correctement ?
> ou alors une manipulation de fichiers .conf mal sauvegardée ?
> ou un service par init /systemd toujours ouvert ? fermez le service :
> stop
J'avais une clé usb d'insérée au moment ou j'ai redémarré la machine et
je l'ai pas déconnectée avant le redémarrage j'ai souvent fait ça
et  j'ai jamais eu de soucidevrais-je?

Merci à vous 2 Sebastien & Mizett

Et oui mailoo marche toujours, mais je sais pas pour combien de
temps! ;-)

le fstab est en pièce jointe :D

Re: Rien ne se passe après Grub2...oops oubliez la pièce jointe dans le dernier message...

[Sébastien NOBILI]

Le mardi 03 octobre 2017 à 10:48, louis a écrit :
> Pensez-vous que le screenshot en PJ a à voir avec ce problème?

Aaaah, voilà la pièce-jointe :D

Le « -.mount » est étrange… Un problème avec le contenu de fstab ou bien un
problème d’interprétation de son contenu par Systemd.

Pourrais-tu nous envoyer le contenu du fichier « /etc/fstab » de ton système
Debian (pas celui du LiveCD).

Si tu as des mots de passe dedans, efface-les avant.

Sébastien

Rien ne se passe après Grub2...oops oubliez la pièce jointe dans le dernier message...

[louis]

Bonjour à tous et à toutes!

Le problème est sur une debian Stretch 9.1 stable, xfce4.
Précisément, après le menu grub, j'appuie sur enter pour choisir cette
debian et rien ne se passe...un clignotement, puis un message
disant :Gave up waiting for suspend/resume device

Et avec le mode sans échec, je me heurte
à :Begin /scripts/local-block.Done
Et sa répète cette ligne à l'infini..

J'ai booté un live debian xfce pour monter ma partition affectée ds un
chroot pour voir les erreurs de la commande :dmesg
J'ai attaché à ce mail le screenshot d'une erreur qui me semble être
liée au problème... car cette erreur, je ne l'avais jamais vue
auparavant
Autre fait intéressant et toujours dans ma live session... thunar, qui
liste par défaut les périphériques, ne liste pas cette partition
(dev/sda6), la partition debian à problème...Par contre il liste toutes
les autres:temp,data,etc

J'ai l'impression que lors du dernier redémarrage de celle-ci, elle
n'aurait pas fermé comme à l'habitude (vu le message cité plus
haut : Gave up waiting for suspend/resume device)
Aussi c'est que, la dernière chose que j'ai fait avant de redémarrer
c'est de créer une clé usb bootable avec "cp
firmware-9.0.0-amd64-netinst.iso /dev/sdc && sync" (je n'ai pas
précisé le chemin du iso, car j'étais dans le répertoire...)
et ensuite, lors de mon démarrage en mode live session dans le chroot
le périphérique créé par cp était dans mon /media/pascal/debian 9.0.0
amd64 n.Je sais pas si il y a corrélation et je préférais vous le
dire . Pourtant mon système s'est fermé comme à l'habitude.

Pensez-vous que le screenshot en PJ a à voir avec ce problème?
Sinon, auriez-vous une piste à me suggérer?

Merci

tracking down a kernel oops

[Jim McCloskey]

Hello. I'm responsible for a bunch of debian machines, work-stations
and servers, in an academic/research environment. They co-exist with
OsX machines. Some months ago we were able to get some new hardware
and had wheezy with gnome 3 installed on the new machines. It's been
difficult keeping these machines working day by day -- printing just
stops working, there are apparently random X freezes, and so on; they
seem just generally unstable. This has been overall a frustrating and
disappointing experience.

The worst problem I'm having at present is with a workstation on which
there are regular kernel failures when there is even a moderately
heavy desktop load -- typically when a browser is opened. The screen
goes crazy and the machine becomes unresponsive to input. I can still
ssh in, so this is probably, at bottom, an X server problem. I call
it a kernel failure, though, 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 Debian 3.2.51-1 i686 GNU/Linux

I'm guessing (but truly it is only a guess) that the problem is
graphics related. The GPU is:

  [AMD] nee ATI RS880 [Radeon HD 4250]

and we're using the radeon driver, not the proprietary driver:

  xserver-xorg-video-radeon: Installed: 1:6.14.4-8

from stable.  I could upgrade to a newer version of that driver or to
a newer kernel and hope for the best, but I'd really like to have more
of an idea of what problem it is I'm trying to solve.

Is there anyone here who has seen similar problems or who has a
suggestion about how the specific problem might be tracked down? I've
installed xserver-xorg-video-radeon-dbg in the hope of getting more
information at the next unpleasant event, but in the meantime here is
the log.

Thanks to all,

Jim


Oct 21 14:07:01 chung kernel: [1737005.190329] BUG: unable to handle
kernel NULL pointer dereference at 0008
Oct 21 14:07:01 chung kernel: [1737005.190445] IP: [c10b3f48]
vma_address+0x25/0x4c
Oct 21 14:07:01 chung kernel: [1737005.190521] *pdpt =
 *pde = f000eef3f000eef3
Oct 21 14:07:01 chung kernel: [1737005.190607] Oops:  [#2] SMP
Oct 21 14:07:01 chung kernel: [1737005.190663] Modules linked in:
 btrfs crc32c libcrc32c zlib_deflate ufs qnx4 hfsplus hfs minix ntfs
 vfat msdos fat jfs xfs reiserfs ext3 jbd ext2 efivars dm_mod cpuid ppdev
 lp rfcomm bnep cpufreq_userspace cpufreq_stats bluetooth rfkill
 cpufreq_conservative cpufreq_powersave binfmt_misc fuse nfsd nfs nfs_acl
 auth_rpcgss fscache lockd sunrpc loop snd_hda_codec_realtek
 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq
 snd_seq_device snd_timer radeon snd parport_pc parport ttm
 drm_kms_helper drm power_supply i2c_algo_bit soundcore sp5100_tco k10temp 
i2c_piix4
 i2c_core evdev powernow_k8 pcspkr mperf shpchp wmi processor button
 thermal_sys ext4 crc16 jbd2 mbcache microcode usbhid hid sg sd_mod
 crc_t10dif ata_generic ohci_hcd r8169 pata_atiixp mii ahci libahci
 ehci_hcd libata usbcore scsi_mod usb_common [last unloaded: scsi_wait_scan]
Oct 21 14:07:01 chung kernel: [1737005.192010]
Oct 21 14:07:01 chung kernel: [1737005.192010] Pid: 30, comm: kswapd0
Tainted: G  D  3.2.0-4-686-pae #1 Debian 3.2.46-1+deb7u1 
MICRO-STAR INTERNATIONAL CO.,LTD MS-7596/880GM-E43 (MS-7596)
Oct 21 14:07:01 chung kernel: [1737005.192010] EIP: 0060:[c10b3f48] EFLAGS: 
00010246 CPU: 1
Oct 21 14:07:01 chung kernel: [1737005.192010] EIP is at vma_address+0x25/0x4c
Oct 21 14:07:01 chung kernel: [1737005.192010] EAX:  EBX: cb1158b8 ECX: 
0009 EDX: 
Oct 21 14:07:01 chung kernel: [1737005.192010] ESI: 0001 EDI:f52abf28 EBP: 
 ESP: f502fe7c
Oct 21 14:07:01 chung kernel: [1737005.192010]  DS: 007b ES: 007b FS:00d8 GS: 
00e0 SS: 0068
Oct 21 14:07:01 chung kernel: [1737005.192010] Process kswapd0 (pid: 30, 
ti=f502e000 task=f594f200 task.ti=f502e000)
Oct 21 14:07:01 chung kernel: [1737005.192010] Stack:
Oct 21 14:07:01 chung kernel: [1737005.192010]  f6617c00  c10b52e5 
534b eaf3af98 cb1158b8  f52abf44
Oct 21 14:07:01 chung kernel: [1737005.192010]   0020 f502fef4 
 c1411000 0002 c10a746a 0001
Oct 21 14:07:01 chung kernel: [1737005.192010]  f6617c14 c1410dc0 f502ff64 
 c10a1780 f502ff10 f502fef4 0020
Oct 21 14:07:01 chung kernel: [1737005.192010] Call Trace:
Oct 21 14:07:01 chung kernel: [1737005.192010]  [c10b52e5] ? 
page_referenced+0xcb/0x204
Oct 21 14:07:01 chung kernel: [1737005.192010]  [c10a746a] ? 
zone_page_state_add+0x12/0x1f
Oct 21 14:07:01 chung kernel: [1737005.192010]  [c10a1780] ? 
shrink_active_list.isra.53+0x19d/0x24f
Oct 21 14:07:01 chung kernel: [1737005.192010]  [c10a2ad4] ? 
kswapd+0x347/0x679
Oct 21 14:07:01 chung kernel

Re: Oops - copied iso image to wrong device

[mark ryan]

On Sun, Oct 13, 2013 at 1:55 AM, Ralf Mardorf ralf.mard...@alice-dsl.netwrote:


 The problem is that you didn't delete it, but you've overwritten the
 data, OTOH the ISO is very small, so not very much is overwritten. First
 you need to try to recover the partition table. Assumed this should
 work, then mount the drive read only and use a tool to undelete files
 for the original used file system.


Hi Ralf, and apologies for the delay. I am on the road due to a family
emergency and obviously that has to come first. I was going to try to set
up another family member on a dual boot, the reason I was trying to create
the install stick.

The drive I overwrote the partition table on is an older Wester Digital
external 320 GB drive that I put an ext4 FS on right out of the box. In
trying to recover the partition table gpart only reports finding the
original (I think) NTFS partition table with one primary that covers the
full disk, and three primaries of zero size. So it looks like I am unable
to recover the partition table because there should be a single ext4
partition.

At this point the time required to recover what I wanted off of here for
this trip is probably not going to be worth the effort. I may try to
recover files if I get a chance, but I'm probably going to have to put off
setting up my sister's dual boot until the next trip.

Thanks to you and other responses.

Re: Oops - copied iso image to wrong device

[mark ryan]

On Sun, Oct 13, 2013 at 10:00 AM, Brian a...@cityscape.co.uk wrote:

 On Sun 13 Oct 2013 at 00:54:44 +, mark ryan wrote:

  I was creating a bootable USB stick from an installer image on another
  external hard drive. I did a cat debian-7.1.0-i386-netinst.iso  /dev/sdb
  when I meant /dev/sdc. sdb was my external drive with the iso on it, and
  other files. I am now unable to mount that drive. What, if anything, can
 I
  do to recover that drive?

 The data on the drive are gone. Do

dd if=/dev/zero of=/dev/sdb count=1

 to remove all traces of the iso you put on it and start from scratch.


Thanks Brian, but I can just fdisk and mkfs this one. It is an external
drive that is only used for file storage. I may try scapel, but I'll
probably just reformat and restore when I get home.

Re: Oops - copied iso image to wrong device

[Jonathan Dowland]

On Sun, Oct 13, 2013 at 10:52:33PM +0100, Brian wrote:
 The dd command was recommended on the off-chance GRUB might be put on 
 the drive now or in the future; it will refuse to install.

I see, I didn't know that, thank you. Apparently grub-setup is the
bit that complains, and it can be made to disregard the check with
the '-s' flag; however it seems non-trivial to pass -s through to
grub-setup from install-grub, and if you were using something like
d-i or another installer perhaps impossible. So, using dd is a
sensible, pragmatic suggestion.


-- 
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/20131014083115.GA5923@debian

Re: Oops - copied iso image to wrong device

[Brian]

On Sun 13 Oct 2013 at 00:54:44 +, mark ryan wrote:

 I was creating a bootable USB stick from an installer image on another
 external hard drive. I did a cat debian-7.1.0-i386-netinst.iso  /dev/sdb
 when I meant /dev/sdc. sdb was my external drive with the iso on it, and
 other files. I am now unable to mount that drive. What, if anything, can I
 do to recover that drive?

The data on the drive are gone. Do

   dd if=/dev/zero of=/dev/sdb count=1

to remove all traces of the iso you put on it and start from scratch.


-- 
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/13102013105700.822ab27dc...@desktop.copernicus.demon.co.uk

Re: Oops - copied iso image to wrong device

[Hans]

Am Sonntag, 13. Oktober 2013, 11:00:50 schrieb Brian:
 On Sun 13 Oct 2013 at 00:54:44 +, mark ryan wrote:
  I was creating a bootable USB stick from an installer image on another
  external hard drive. I did a cat debian-7.1.0-i386-netinst.iso  /dev/sdb
  when I meant /dev/sdc. sdb was my external drive with the iso on it, and
  other files. I am now unable to mount that drive. What, if anything, can I
  do to recover that drive?

If some sectors are3 not overwritten, you might eb able to rescue some files 
(pictures, textfiles or similar) by using foremost or scalpel.

Checkout a forensic livefile system. I suggest DEFT-7.2 (32-bit) or DEFT-8.0 
(only 64-bit).

It has got some nioce tools on it, so it might be not everything is lost.

Good luck!

Hans 


-- 
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/2212492.bBjRUiarkX@protheus2

Re: Oops - copied iso image to wrong device

[Jonathan Dowland]

On Sun, Oct 13, 2013 at 11:00:50AM +0100, Brian wrote:
 The data on the drive are gone. Do
 
dd if=/dev/zero of=/dev/sdb count=1
 
 to remove all traces of the iso you put on it and start from scratch.

…why? As things currently stand, the user could possibly reconstruct
the partition table and recover most of their data, or, use forensic
recovery tools that don't rely on the FS being intact to identify and
recover bits past the ISO-length offset into the drive.

If they do as you suggest, they rule out any of the above recovery
options. What do they gain?

If they are to write off the drive, they could plop a new partition
table on top of things as they stand, mkfs on the partitions, and start
over, without  having to wait for the dd to complete.


-- 
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/20131013204940.GB1529@debian

Re: Oops - copied iso image to wrong device

[Brian]

On Sun 13 Oct 2013 at 21:49:40 +0100, Jonathan Dowland wrote:

 On Sun, Oct 13, 2013 at 11:00:50AM +0100, Brian wrote:
  The data on the drive are gone. Do
  
 dd if=/dev/zero of=/dev/sdb count=1
  
  to remove all traces of the iso you put on it and start from scratch.
 
 …why? As things currently stand, the user could possibly reconstruct
 the partition table and recover most of their data, or, use forensic
 recovery tools that don't rely on the FS being intact to identify and
 recover bits past the ISO-length offset into the drive.
 
 If they do as you suggest, they rule out any of the above recovery
 options. What do they gain?

Time to enjoy the finer things in life? The OP would have to weigh up
the benefits of possibly being able to recover data etc as against
definitely being able to restore from a backup.

 If they are to write off the drive, they could plop a new partition
 table on top of things as they stand, mkfs on the partitions, and start
 over, without  having to wait for the dd to complete.

The dd command was recommended on the off-chance GRUB might be put on 
the drive now or in the future; it will refuse to install.


-- 
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/20131013215233.gb22...@copernicus.demon.co.uk

Oops - copied iso image to wrong device

[mark ryan]

Howdy all,

I was creating a bootable USB stick from an installer image on another
external hard drive. I did a cat debian-7.1.0-i386-netinst.iso  /dev/sdb
when I meant /dev/sdc. sdb was my external drive with the iso on it, and
other files. I am now unable to mount that drive. What, if anything, can I
do to recover that drive?

There is nothing on the drive that I can not recover, except I am on the
road and do not have access to the backups at the moment, so I figured I
would ask. Any advice?

Thanks,
Mark

Re: Oops - copied iso image to wrong device

[Ralf Mardorf]

The problem is that you didn't delete it, but you've overwritten the
data, OTOH the ISO is very small, so not very much is overwritten. First
you need to try to recover the partition table. Assumed this should
work, then mount the drive read only and use a tool to undelete files
for the original used file system.



-- 
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/1381629359.765.92.camel@archlinux

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Kailash]

On Sunday 11 August 2013 10:39 AM, Dom wrote:

On 11/08/13 03:43, Patrick Bartek wrote:

On Sun, 11 Aug 2013, Chris Bannister wrote:


On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:

Changing subject as suggested by Chris, and reposting original
question.
-



Still an unhelpful question, esp when one knows the true meaning of
SNAFU


have resulted in Gnome being install, too.  More or less.  So I
just did as root in /root a 'dpkg --download,' and then an
'--unpack' thinking that would uncompress the .deb file in /root
from which I would get the single svg file I needed, and then just
delete everything else.  Simple. Right?  Wrong. Now, I'm stuck with
about 4.5 megs of Gnome data, icons,


AFAIU, a .deb file is just an 'ar' archive.

As to how to recover after an unintentional unpack, ... dunno.
Hopefully someone on this list knows now that the subject explains
your predicament.


Fortunately --unpack just installed files to their appropriate
directories, but didn't trigger or configure anything.  Not all that
up on dpkg. Have always used apt-get.

If I don't hear anything bad to the contrary in the next day or so, I'm
just going to use --purge to remove the package after creating
a copy of the file I need in a safe directory, then copy the copy back
after the purging.  Hopefully, it will work.


Good luck with that, it sounds like it will work.

Alternatively you can get a list of the files contained in the .deb file
using dpkg -c debfile. With a little bit of wrangling that will give
you a list of files and directories to delete - although you should only
delete directories if they are empty.


Hi,

As per the man pages: http://linuxreviews.org/man/dpkg/

dpkg -s package-name

will give you the status of a package. As per the man file, it should 
show the status as unpacked.


dpkg --purge

should work as expected. To make sure that it does work as expected you 
can add add the --no-act option which will ensure that no changes are 
written.


caveat: Be sure to give --no-act before the action-parameter, or you 
might end up with undesirable results. (e.g. dpkg --purge foo --no-act 
will first purge package foo and then try to purge package --no-act, 
even though you probably expected it to actually do nothing)


Sincerely,
Kailash


--
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/5207863f.4060...@gmail.com

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Patrick Bartek]

On Sun, 11 Aug 2013, Dom wrote:

 On 11/08/13 03:43, Patrick Bartek wrote:
  On Sun, 11 Aug 2013, Chris Bannister wrote:
 
  On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:
  Changing subject as suggested by Chris, and reposting original
  question.
  -
 
  Still an unhelpful question, esp when one knows the true meaning of
  SNAFU
 
  have resulted in Gnome being install, too.  More or less.  So I
  just did as root in /root a 'dpkg --download,' and then an
  '--unpack' thinking that would uncompress the .deb file in /root
  from which I would get the single svg file I needed, and then just
  delete everything else.  Simple. Right?  Wrong. Now, I'm stuck
  with about 4.5 megs of Gnome data, icons,
 
  AFAIU, a .deb file is just an 'ar' archive.
 
  As to how to recover after an unintentional unpack, ... dunno.
  Hopefully someone on this list knows now that the subject explains
  your predicament.
 
  Fortunately --unpack just installed files to their appropriate
  directories, but didn't trigger or configure anything.  Not all
  that up on dpkg. Have always used apt-get.
 
  If I don't hear anything bad to the contrary in the next day or so,
  I'm just going to use --purge to remove the package after creating
  a copy of the file I need in a safe directory, then copy the copy
  back after the purging.  Hopefully, it will work.
 
 Good luck with that, it sounds like it will work.
 
 Alternatively you can get a list of the files contained in the .deb
 file using dpkg -c debfile. With a little bit of wrangling that
 will give you a list of files and directories to delete - although
 you should only delete directories if they are empty.

I did that.  Quite a long list.  Too long (and too much trouble) to
manually delete the files and/or directories.  Even thought of
building a script that used the list to automate it.  But one little
mistake and my system could be trashed.  Safer to just use --purge.

Thanks for your advice.

B


-- 
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/20130811091600.1574e...@debian7.boseck208.net

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Patrick Bartek]

On Sun, 11 Aug 2013, Kailash wrote:

 On Sunday 11 August 2013 10:39 AM, Dom wrote:
  On 11/08/13 03:43, Patrick Bartek wrote:
  On Sun, 11 Aug 2013, Chris Bannister wrote:
 
  On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:
  Changing subject as suggested by Chris, and reposting original
  question.
  -
 
 
  Still an unhelpful question, esp when one knows the true meaning
  of SNAFU
 
  have resulted in Gnome being install, too.  More or less.  So I
  just did as root in /root a 'dpkg --download,' and then an
  '--unpack' thinking that would uncompress the .deb file in /root
  from which I would get the single svg file I needed, and then
  just delete everything else.  Simple. Right?  Wrong. Now, I'm
  stuck with about 4.5 megs of Gnome data, icons,
 
  AFAIU, a .deb file is just an 'ar' archive.
 
  As to how to recover after an unintentional unpack, ... dunno.
  Hopefully someone on this list knows now that the subject explains
  your predicament.
 
  Fortunately --unpack just installed files to their appropriate
  directories, but didn't trigger or configure anything.  Not all
  that up on dpkg. Have always used apt-get.
 
  If I don't hear anything bad to the contrary in the next day or
  so, I'm just going to use --purge to remove the package after
  creating a copy of the file I need in a safe directory, then copy
  the copy back after the purging.  Hopefully, it will work.
 
  Good luck with that, it sounds like it will work.
 
  Alternatively you can get a list of the files contained in the .deb
  file using dpkg -c debfile. With a little bit of wrangling that
  will give you a list of files and directories to delete - although
  you should only delete directories if they are empty.
 
 Hi,
 
 As per the man pages: http://linuxreviews.org/man/dpkg/
 
 dpkg -s package-name
 
 will give you the status of a package. As per the man file, it should 
 show the status as unpacked.

Did this first thing after the unpack.  Status is installed
however.  Don't know why.

 
 dpkg --purge
 
 should work as expected. To make sure that it does work as expected
 you can add add the --no-act option which will ensure that no changes
 are written.

Sometimes things don't work as expected, but purge seems the best
option to clean my system of the unneeded files/directories.

Yes, I was going to use --no-act (or similar) with verbose output to
check for problems before doing it for real.

 
 caveat: Be sure to give --no-act before the action-parameter, or you 
 might end up with undesirable results. (e.g. dpkg --purge foo
 --no-act will first purge package foo and then try to purge package
 --no-act, even though you probably expected it to actually do nothing)

Thanks.  That point is made in the dpkg man file.  After the initial
unpack snafu, I read the man more thoroughly.

Thanks for your advice.

B


-- 
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/20130811093621.40d7d...@debian7.boseck208.net

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Bob Proulx]

Patrick Bartek wrote:
   have resulted in Gnome being install, too.  More or less.  So I
   just did as root in /root a 'dpkg --download,' and then an
   '--unpack' thinking that would uncompress the .deb file in /root
   from which I would get the single svg file I needed, and then just

The command you were looking for was 'dpkg-deb -x foo.deb foo-dir'.

   delete everything else.  Simple. Right?  Wrong. Now, I'm stuck with
   about 4.5 megs of Gnome data, icons,
 
 Fortunately --unpack just installed files to their appropriate
 directories, but didn't trigger or configure anything.  Not all that
 up on dpkg. Have always used apt-get.

After a dpkg --unpack the package will be listed like this:

  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version  Architecture Description
  +++-=---===
  iU  foo  2.5-1  amd64  Foo description

That says installed but unpacked.  A long dpkg --status would show:

  Status: install ok unpacked

 If I don't hear anything bad to the contrary in the next day or so, I'm
 just going to use --purge to remove the package after creating
 a copy of the file I need in a safe directory, then copy the copy back
 after the purging.  Hopefully, it will work.

That is the correct thing to do.  The dpkg package manager knows the
state of the installation.  Simply tell it to purge the package.
Simple!  No need to look any further.

  dpkg --purge foo

Bob


signature.asc
Description: Digital signature

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Patrick Bartek]

On Sun, 11 Aug 2013, Bob Proulx wrote:

 Patrick Bartek wrote:
have resulted in Gnome being install, too.  More or less.  So I
just did as root in /root a 'dpkg --download,' and then an
'--unpack' thinking that would uncompress the .deb file in /root
from which I would get the single svg file I needed, and then
just
 
 The command you were looking for was 'dpkg-deb -x foo.deb foo-dir'.

Wish I had know about that a couple days ago.  Would have saved a lot
of time and reading and rereading.

 
delete everything else.  Simple. Right?  Wrong. Now, I'm stuck
with about 4.5 megs of Gnome data, icons,
  
  [snip]
 
  If I don't hear anything bad to the contrary in the next day or so,
  I'm just going to use --purge to remove the package after creating
  a copy of the file I need in a safe directory, then copy the copy
  back after the purging.  Hopefully, it will work.
 
 That is the correct thing to do.  The dpkg package manager knows the
 state of the installation.  Simply tell it to purge the package.
 Simple!  No need to look any further.
 
   dpkg --purge foo

Thanks for the info and the recommendations.

B


-- 
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/20130811191907.2b3a1...@debian7.boseck208.net

Re: Oops!

[Chris Bannister]

On Fri, Aug 09, 2013 at 06:56:56PM -0700, Patrick Bartek wrote:

Nothing to do with subject

Could you please provide a meaningful subject relating to your post.

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
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/20130810065446.GB16974@tal

Re: Oops!

[Patrick Bartek]

On Sat, 10 Aug 2013, Chris Bannister wrote:

 On Fri, Aug 09, 2013 at 06:56:56PM -0700, Patrick Bartek wrote:
 
 Nothing to do with subject
 
 Could you please provide a meaningful subject relating to your post.

This is the second try replying to your post.  The first one failed to
send. Don't know why.

I did.  The original subject was Oops! Dpkg SNAFU, but when I posted
it only Oops! showed up.  Don't know why.

B


-- 
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/20130810100853.71eba...@debian7.boseck208.net

Dpkg SNAFU was Re: Oops!

[Lisi Reisz]

On Saturday 10 August 2013 18:08:53 Patrick Bartek wrote:
 On Sat, 10 Aug 2013, Chris Bannister wrote:
  On Fri, Aug 09, 2013 at 06:56:56PM -0700, Patrick Bartek wrote:
 
  Nothing to do with subject
 
  Could you please provide a meaningful subject relating to your post.

 This is the second try replying to your post.  The first one failed to
 send. Don't know why.

 I did.  The original subject was Oops! Dpkg SNAFU, but when I posted
 it only Oops! showed up.  Don't know why.

Changing subject as suggested by Chris, and reposting original question.
-

Finally got around to installing Pulseaudio-Equalizer on my 64-bit
Wheezy, which by the way is NOT in the Wheezy repos or backports.
However, was able to find a tar.gz file of it from the developer's site,
IIRC. It's been months since I downloaded it.  I've been busy. ;-)

In any case, here's the problem:  the equalizer needs
multimedia-volume-control.svg.  A search turned up it was part of
the gnome-control-center-data package.  Not having Gnome on this
system, just a window manager--Openbox--installing the package would
have resulted in Gnome being install, too.  More or less.  So I just did
as root in /root a 'dpkg --download,' and then an '--unpack' thinking
that would uncompress the .deb file in /root from which I would get the
single svg file I needed, and then just delete everything else.  Simple.
Right?  Wrong. Now, I'm stuck with about 4.5 megs of Gnome data, icons,
and config files scattered all over the system that I want to get rid
of before they cause any problems, if any.

My plan is to copy the file I need to someplace safe, then 'dpkg
--purge' the original package to clean the system of it, and copy the
file back to where it needs to be.  Sound okay?  Any expected gotchas?
Any better alternatives?

Thanks.


-- 
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/201308101813.20627.lisi.re...@gmail.com

How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Chris Bannister]

On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:
 Changing subject as suggested by Chris, and reposting original question.
 -

Still an unhelpful question, esp when one knows the true meaning of
SNAFU

 have resulted in Gnome being install, too.  More or less.  So I just did
 as root in /root a 'dpkg --download,' and then an '--unpack' thinking
 that would uncompress the .deb file in /root from which I would get the
 single svg file I needed, and then just delete everything else.  Simple.
 Right?  Wrong. Now, I'm stuck with about 4.5 megs of Gnome data, icons,

AFAIU, a .deb file is just an 'ar' archive.

As to how to recover after an unintentional unpack, ... dunno. Hopefully
someone on this list knows now that the subject explains your
predicament.

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
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/20130811012017.GB30256@tal

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Patrick Bartek]

On Sun, 11 Aug 2013, Chris Bannister wrote:

 On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:
  Changing subject as suggested by Chris, and reposting original
  question.
  -
 
 Still an unhelpful question, esp when one knows the true meaning of
 SNAFU
 
  have resulted in Gnome being install, too.  More or less.  So I
  just did as root in /root a 'dpkg --download,' and then an
  '--unpack' thinking that would uncompress the .deb file in /root
  from which I would get the single svg file I needed, and then just
  delete everything else.  Simple. Right?  Wrong. Now, I'm stuck with
  about 4.5 megs of Gnome data, icons,
 
 AFAIU, a .deb file is just an 'ar' archive.
 
 As to how to recover after an unintentional unpack, ... dunno.
 Hopefully someone on this list knows now that the subject explains
 your predicament.

Fortunately --unpack just installed files to their appropriate
directories, but didn't trigger or configure anything.  Not all that
up on dpkg. Have always used apt-get.

If I don't hear anything bad to the contrary in the next day or so, I'm
just going to use --purge to remove the package after creating
a copy of the file I need in a safe directory, then copy the copy back
after the purging.  Hopefully, it will work.

B


-- 
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/20130810194301.6ce2c...@debian7.boseck208.net

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Dom]

On 11/08/13 03:43, Patrick Bartek wrote:

On Sun, 11 Aug 2013, Chris Bannister wrote:


On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:

Changing subject as suggested by Chris, and reposting original
question.
-


Still an unhelpful question, esp when one knows the true meaning of
SNAFU


have resulted in Gnome being install, too.  More or less.  So I
just did as root in /root a 'dpkg --download,' and then an
'--unpack' thinking that would uncompress the .deb file in /root
from which I would get the single svg file I needed, and then just
delete everything else.  Simple. Right?  Wrong. Now, I'm stuck with
about 4.5 megs of Gnome data, icons,


AFAIU, a .deb file is just an 'ar' archive.

As to how to recover after an unintentional unpack, ... dunno.
Hopefully someone on this list knows now that the subject explains
your predicament.


Fortunately --unpack just installed files to their appropriate
directories, but didn't trigger or configure anything.  Not all that
up on dpkg. Have always used apt-get.

If I don't hear anything bad to the contrary in the next day or so, I'm
just going to use --purge to remove the package after creating
a copy of the file I need in a safe directory, then copy the copy back
after the purging.  Hopefully, it will work.


Good luck with that, it sounds like it will work.

Alternatively you can get a list of the files contained in the .deb file 
using dpkg -c debfile. With a little bit of wrangling that will give 
you a list of files and directories to delete - although you should only 
delete directories if they are empty.


--
Dom


--
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/52071ca5.9070...@rpdom.net

Oops!

[Patrick Bartek]

Finally got around to installing Pulseaudio-Equalizer on my 64-bit
Wheezy, which by the way is NOT in the Wheezy repos or backports.
However, was able to find a tar.gz file of it from the developer's site,
IIRC. It's been months since I downloaded it.  I've been busy. ;-)

In any case, here's the problem:  the equalizer needs
multimedia-volume-control.svg.  A search turned up it was part of
the gnome-control-center-data package.  Not having Gnome on this
system, just a window manager--Openbox--installing the package would
have resulted in Gnome being install, too.  More or less.  So I just did
as root in /root a 'dpkg --download,' and then an '--unpack' thinking
that would uncompress the .deb file in /root from which I would get the
single svg file I needed, and then just delete everything else.  Simple.
Right?  Wrong. Now, I'm stuck with about 4.5 megs of Gnome data, icons,
and config files scattered all over the system that I want to get rid
of before they cause any problems, if any.

My plan is to copy the file I need to someplace safe, then 'dpkg
--purge' the original package to clean the system of it, and copy the
file back to where it needs to be.  Sound okay?  Any expected gotchas?
Any better alternatives?

Thanks.

B


-- 
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/20130809185656.41869...@debian7.boseck208.net

Re: ESC[4m does not produce underline OOPS

[Chris Bannister]

On Fri, Mar 01, 2013 at 11:46:42AM -0800, Thomas D. Dean wrote:
 On 03/01/13 11:35, Thomas D. Dean wrote:
 The ANSI standard lists ESC[4m as the code to produce an underline
 
   export TERM=ansi80x25
   printf \033[4masdfasdfasdf
 
 produces green text, not underline text as stated in the standard.
 
 If I put the same in c code, it works
 
 #include stdio.h
 int main() {
 fputs(\033[4masdfasdf,stdout);
 return 0;
 }
 
 I get underlined text.
 
 
 I ran the C example in an xterm on Ubuntu!
 
 The question remains.
 
 Why does this produce color rather than underlined text?
 
 The standard says ESC[32m should produce green text and ESC[4m
 should produce underlined text.

It's normally about now that a Mr Thomas Dickey magically appears with
his wisdom, perhaps you could cc him (his address is on the net, but get
a more recent one, I don't think he uses his invisible island address
anymore, although I could be wrong.

-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
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/20130302110421.GD9278@tal

Re: ESC[4m does not produce underline OOPS

[Thomas D. Dean]

On 03/01/13 11:35, Thomas D. Dean wrote:

The ANSI standard lists ESC[4m as the code to produce an underline

  export TERM=ansi80x25
  printf \033[4masdfasdfasdf

produces green text, not underline text as stated in the standard.

If I put the same in c code, it works

#include stdio.h
int main() {
fputs(\033[4masdfasdf,stdout);
return 0;
}

I get underlined text.



I ran the C example in an xterm on Ubuntu!

The question remains.

Why does this produce color rather than underlined text?

The standard says ESC[32m should produce green text and ESC[4m should 
produce underlined text.


Tom Dean


--
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/513105a2.8000...@speakeasy.org

Re: ESC[4m does not produce underline OOPS

[Richard Hector]

On 02/03/13 08:46, Thomas D. Dean wrote:
 On 03/01/13 11:35, Thomas D. Dean wrote:
 The ANSI standard lists ESC[4m as the code to produce an underline

   export TERM=ansi80x25
   printf \033[4masdfasdfasdf

 produces green text, not underline text as stated in the standard.

 If I put the same in c code, it works

 #include stdio.h
 int main() {
 fputs(\033[4masdfasdf,stdout);
 return 0;
 }

 I get underlined text.

 
 I ran the C example in an xterm on Ubuntu!
 
 The question remains.
 
 Why does this produce color rather than underlined text?
 
 The standard says ESC[32m should produce green text and ESC[4m should
 produce underlined text.

Are you doing this on a (colour) linux console, rather than an xterm?
Apparently it can't do underline, and simulates it with a different
colour instead. See 'man console_codes', or here:
https://www.kernel.org/doc/man-pages/online/page/man4/console_codes.4.html

I don't think setting TERM will make any difference; it's your program
that has to interpret that (usually via terminfo and associated
libraries) and send the correct escape sequences - but you're sending
them yourself anyway.

Richard


-- 
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/5131398c.9090...@walnut.gen.nz

Re: ESC[4m does not produce underline OOPS

[Hugo Vanwoerkom]

Richard Hector wrote:

On 02/03/13 08:46, Thomas D. Dean wrote:

On 03/01/13 11:35, Thomas D. Dean wrote:

The ANSI standard lists ESC[4m as the code to produce an underline

  export TERM=ansi80x25
  printf \033[4masdfasdfasdf

produces green text, not underline text as stated in the standard.

If I put the same in c code, it works

#include stdio.h
int main() {
fputs(\033[4masdfasdf,stdout);
return 0;
}

I get underlined text.


I ran the C example in an xterm on Ubuntu!

The question remains.

Why does this produce color rather than underlined text?

The standard says ESC[32m should produce green text and ESC[4m should
produce underlined text.


Are you doing this on a (colour) linux console, rather than an xterm?
Apparently it can't do underline, and simulates it with a different
colour instead. See 'man console_codes', or here:
https://www.kernel.org/doc/man-pages/online/page/man4/console_codes.4.html


404 File not found.

Hugo



I don't think setting TERM will make any difference; it's your program
that has to interpret that (usually via terminfo and associated
libraries) and send the correct escape sequences - but you're sending
them yourself anyway.



--
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/kgrhfg$ols$1...@ger.gmane.org

Re: ESC[4m does not produce underline OOPS

[Glenn English]

On Mar 1, 2013, at 5:34 PM, Hugo Vanwoerkom wrote:

 404 File not found.

Google 'console_codes(4) - Linux manual page'.

-- 
Glenn English





-- 
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/7ff07ec2-5efb-434b-bf3e-5f425256c...@slsware.com

Re: ESC[4m does not produce underline OOPS

[Thomas D. Dean]

On 03/01/13 16:56, Glenn English wrote:

The linux console is a HDMI display attached to a RaspberryPi.

I changed to ncurses5.  Looks like the display does not support underline.

Thanks,

Tom Dean


--
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/513174f0.6030...@speakeasy.org

Re: ESC[4m does not produce underline OOPS

[Richard Hector]

On 02/03/13 13:34, Hugo Vanwoerkom wrote:
 Richard Hector wrote:
 On 02/03/13 08:46, Thomas D. Dean wrote:
 On 03/01/13 11:35, Thomas D. Dean wrote:
 The ANSI standard lists ESC[4m as the code to produce an underline

   export TERM=ansi80x25
   printf \033[4masdfasdfasdf

 produces green text, not underline text as stated in the standard.

 If I put the same in c code, it works

 #include stdio.h
 int main() {
 fputs(\033[4masdfasdf,stdout);
 return 0;
 }

 I get underlined text.

 I ran the C example in an xterm on Ubuntu!

 The question remains.

 Why does this produce color rather than underlined text?

 The standard says ESC[32m should produce green text and ESC[4m should
 produce underlined text.

 Are you doing this on a (colour) linux console, rather than an xterm?
 Apparently it can't do underline, and simulates it with a different
 colour instead. See 'man console_codes', or here:
 https://www.kernel.org/doc/man-pages/online/page/man4/console_codes.4.html

 
 404 File not found.


Sorry - fail with copy/paste and attempting to fix annoying line wraps -
which only appear in my mailer.
https://www.kernel.org/doc/man-pages/online/pages/man4/console_codes.4.html

ie s/page/pages/

Richard


-- 
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/513180ba.4010...@walnut.gen.nz

Re: Kernel Oops during/after rsync

[Camaleón]

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 the last five days) occurred while I was playing Patrician III
 with Wine. I don’t know whether Wine/Patrician III has anything to do
 with that; if anything, I suspect temperature issues, but the same
 machine survives five hours of video encoding just fine (though the CPU
 frequency is sometimes automatically lowered due to high temperature).

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?

 The backup script, attached below, consists of the following stages:
 
 a) log that the backup started
 b) rsync some data
 c) log that the backup finished
 d) call sync
 e) log that the sync finished
 
 a) and c) are logged:
 
 Aug  7 23:30:01 ares Backup_Alix[638]: Backup started. Aug  7 23:30:05
 ares Backup_Alix[648]: Backup finished.
 
 but not e). At the same time, the following is written to kern.log, the
 screen shows part of that message and the computer powers off after a
 while.
 
 Aug  7 23:30:04 ares kernel: [75763.117797] BUG: unable to handle kernel 
 paging request at 8812e5463620 
  ^^^

(...)

Can you reproduce the bug from a Debian kernel? If yes, you can report it 
at the BTS; otherwise you can file a bug report upstream.

(...)

 Unfortunately, googling for anything from the above trace or just kernel
 oopses in relation to rsync turned out unsuccessful, I would hence be
 very thankful if someone could provide me with additional pointers :)

Google points to some user reports about a hardware problem (memory) but of 
course, nothing conclusive.

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/jvu03f$kgo$1...@dough.gmane.org

Re: Kernel Oops during/after rsync

[Claudius Hubig]

Hello Camaleón,

Camaleón noela...@gmail.com 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, at all times, Patrician III had been running. However,
I’ve been playing Patrician III for more than four weeks now (not all
that much to do at the moment…). Hence, I can say that, whenever the
computer crashed, Patrician III was running and a backup had just
finished, but there have been many more times when a backup succeeded
while Patrician III was running and the computer did not crash.

 Can you reproduce the bug from a Debian kernel? If yes, you can report it 
 at the BTS; otherwise you can file a bug report upstream.

The kernel is compiled from Debian sources. I will see into running a
‘standard’ Debian kernel if the problem persists.

 Google points to some user reports about a hardware problem (memory) but of 
 course, nothing conclusive.

I should have mentioned that running memtest86+ didn’t find any
problems :\

Best regards  thank you very much for your reply,

Claudius
-- 
  A board is the planck unit of boredom.
http://chubig.net  telnet nightfall.org 4242


signature.asc
Description: PGP signature

Kernel Oops during/after rsync

[Claudius Hubig]

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. I don’t know whether Wine/Patrician III has anything to do
with that; if anything, I suspect temperature issues, but the same
machine survives five hours of video encoding just fine (though the
CPU frequency is sometimes automatically lowered due to high
temperature).

The backup script, attached below, consists of the following stages:

a) log that the backup started
b) rsync some data
c) log that the backup finished
d) call sync
e) log that the sync finished

a) and c) are logged:

Aug  7 23:30:01 ares Backup_Alix[638]: Backup started.
Aug  7 23:30:05 ares Backup_Alix[648]: Backup finished.

but not e). At the same time, the following is
written to kern.log, the screen shows part of that message and the
computer powers off after a while.

Aug  7 23:30:04 ares kernel: [75763.117797] BUG: unable to handle kernel paging 
request at 8812e5463620
Aug  7 23:30:04 ares kernel: [75763.117844] IP: [810d6985] 
__d_lookup_rcu+0x136/0x156
Aug  7 23:30:04 ares kernel: [75763.117880] PGD 1a0c063 PUD 0 
Aug  7 23:30:04 ares kernel: [75763.117901] Oops:  [#1] SMP 
Aug  7 23:30:04 ares kernel: [75763.117924] CPU 3 
Aug  7 23:30:04 ares kernel: [75763.117934] Modules linked in: e1000e 
tp_smapi(O) thinkpad_ec(O) iwlwifi [last unloaded: e1000e]
Aug  7 23:30:04 ares kernel: [75763.117987] 
Aug  7 23:30:04 ares kernel: [75763.117996] Pid: 641, comm: rsync Tainted: G
   O 3.4.1.a2017.1 #1 LENOVO 291239G/291239G
Aug  7 23:30:04 ares kernel: [75763.118042] RIP: 0010:[810d6985]  
[810d6985] __d_lookup_rcu+0x136/0x156
Aug  7 23:30:04 ares kernel: [75763.118082] RSP: 0018:880143349c48  EFLAGS: 
00010282
Aug  7 23:30:04 ares kernel: [75763.118107] RAX: 0008 RBX: 
8812e5463608 RCX: 0014
Aug  7 23:30:04 ares kernel: [75763.118139] RDX: 0f40 RSI: 
c9002000 RDI: 88011c927a40
Aug  7 23:30:04 ares kernel: [75763.118171] RBP: 88011c927a40 R08: 
0008 R09: 2f2f2f2f2f2f2f2f
Aug  7 23:30:04 ares kernel: [75763.118203] R10: ef94b111 R11: 
8d9093ff R12: 880143349e18
Aug  7 23:30:04 ares kernel: [75763.118235] R13: 880143349d70 R14: 
880143349d70 R15: 880143349e18
Aug  7 23:30:04 ares kernel: [75763.118268] FS:  7fa33fd9f700() 
GS:88023bd8() knlGS:
Aug  7 23:30:04 ares kernel: [75763.118303] CS:  0010 DS:  ES:  CR0: 
80050033
Aug  7 23:30:04 ares kernel: [75763.118330] CR2: 8812e5463620 CR3: 
0001427fd000 CR4: 07e0
Aug  7 23:30:04 ares kernel: [75763.118362] DR0:  DR1: 
 DR2: 
Aug  7 23:30:04 ares kernel: [75763.118393] DR3:  DR6: 
0ff0 DR7: 0400
Aug  7 23:30:04 ares kernel: [75763.118425] Process rsync (pid: 641, threadinfo 
880143348000, task 88023073d980)
Aug  7 23:30:04 ares kernel: [75763.118460] Stack:
Aug  7 23:30:04 ares kernel: [75763.118471]  880115b097d0 0081 
8801e8ce6015 88023073d980
Aug  7 23:30:04 ares kernel: [75763.118511]  88023073d980 8801e8ce6015 
880143349cf4 0008
Aug  7 23:30:04 ares kernel: [75763.118551]  880115b097d0 880143349e08 
880143349d48 88011c927a40
Aug  7 23:30:04 ares kernel: [75763.118590] Call Trace:
Aug  7 23:30:04 ares kernel: [75763.118606]  [810cdac8] ? 
do_lookup+0x41/0x291
Aug  7 23:30:04 ares kernel: [75763.118632]  [810cf160] ? 
path_lookupat+0xe0/0x670
Aug  7 23:30:04 ares kernel: [75763.118660]  [810e709c] ? 
__getblk+0x24/0x245
Aug  7 23:30:04 ares kernel: [75763.118684]  [810cf70e] ? 
do_path_lookup+0x1e/0x9a
Aug  7 23:30:04 ares kernel: [75763.118711]  [810cd876] ? 
getname_flags+0x148/0x1e2
Aug  7 23:30:04 ares kernel: [75763.118738]  [810d0fcb] ? 
user_path_at_empty+0x47/0x7b
Aug  7 23:30:04 ares kernel: [75763.118768]  [81158eb2] ? 
jbd2_journal_stop+0x1f0/0x202
Aug  7 23:30:04 ares kernel: [75763.118797]  [8113a266] ? 
__ext4_journal_stop+0x6e/0x74
Aug  7 23:30:04 ares kernel: [75763.118825]  [81136aa0] ? 
ext4_link+0x121/0x156
Aug  7 23:30:04 ares kernel: [75763.118851]  [810c86e7] ? 
vfs_fstatat+0x32/0x60
Aug  7 23:30:04 ares kernel: [75763.118876]  [810ce9e8] ? 
vfs_link+0x161/0x17f
Aug  7 23:30:04 ares kernel: [75763.118901]  [810c883c] ? 
sys_newlstat+0x12/0x2b
Aug  7 23:30:04 ares kernel: [75763.118928]  [810db57d] ? 
mntput_no_expire+0x10/0xf4
Aug  7 23:30:04 ares kernel: [75763.118955]  [810d1672] ? 
sys_linkat+0x1b8/0x1c7
Aug  7 23:30:04 ares kernel: [75763.118983]  [8159cca2] ? 
system_call_fastpath+0x16

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

[Camaleón]

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 oops

(...)

It seems the OP has already opened a bug report for the issue (@Debian 
BTS #674243), maybe you can track the development of the problem from 
there and also consider in adding your own comments/experience at the 
Freedesktop bug where it has been forwarded.

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/jplko0$a15$1...@dough.gmane.org

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

[Camaleón]

On Wed, 23 May 2012 06:36:24 +0100, elbbit wrote:

 Sorry to hijack the thread, but I suspect this problem may be related to
 mine.  I've checked the Dell website for OP and our specs are similar
 from the same manufacturer.

No problem. There's no hijack when talking on the same issue :-)

 On 22/05/12 17:37, Camaleón wrote:
 On Mon, 21 May 2012 20:57:58 -0400, Sylvain Archenault wrote:
 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.
 
 Same here except my pair of Alienware's run 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

Mmm...

 That's curious because closing the lid and suspending from menu should
 both trigger the same command unless

 That'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 driver in 
the blacklist so it does not enter into suspension. If blacklisting the 
driver makes the suspension works again when closing the lib, at least 
you'd had found the root of the problem.

 When logged into the laptop by OpenSSH the laptop continues to respond,
 and in the log file (see pastebin below) you see me attempting to
 shutdown the computer (around line 616) which succeeds.  However, once
 lid-down-then-up-again the screen is frozen at the Gnome idle/lock
 screen until the system cuts the power.  For me this confirms a screen
 issue.  If I repeatedly press the power button or close the lid again
 still nothing happens.

Your log is very long and I can see gnome-shell oopsing. Just for 
testing purposes, can you reproduce the oops when logged inside a gnome-
classical session?

 what's the action you have configured when closing the lid, to suspend
 or hibernate?

 Mine is set to suspend.

(...)

Okay, the action is consistent then. The only difference I see is that 
suspending when closing the lid involves an ACPI action while suspending 
from the menu doesn't (it's an action directly triggered by the user).
 
 I would report a kernel oops in Debian BTS, eve more if running sid.

 I am reading up on how to submit bugs before blindly submitting them.
 Does anyone know if this bug already has a report created for it?

You can use reportbug and follow the wizard (you can also query for 
similar bug reports already opened from here) but if you're going to 
write a detailed bug report, better save it first in a separate text file 
and then copy/paste the content to reportbug because this tool can 
suddenly crash at any time ;-(

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/jpj19o$kr$1...@dough.gmane.org

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

[elbbit]

On 23/05/12 16:55, Camaleón wrote:
 On Wed, 23 May 2012 06:36:24 +0100, elbbit wrote:
 On 22/05/12 17:37, Camaleón wrote:
 That's curious because closing the lid and suspending from menu should
 both trigger the same command unless

 That'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 driver in 
 the blacklist so it does not enter into suspension. If blacklisting the 
 driver makes the suspension works again when closing the lib, at least 
 you'd had found the root of the problem.

I will try this in the next few hours.  On the one laptop I have full
gnome, the other is xorg/compiz only (no gnome).

 When logged into the laptop by OpenSSH the laptop continues to respond,
 and in the log file (see pastebin below) you see me attempting to
 shutdown the computer (around line 616) which succeeds.  However, once
 lid-down-then-up-again the screen is frozen at the Gnome idle/lock
 screen until the system cuts the power.  For me this confirms a screen
 issue.  If I repeatedly press the power button or close the lid again
 still nothing happens.
 
 Your log is very long and I can see gnome-shell oopsing. Just for 
 testing purposes, can you reproduce the oops when logged inside a gnome-
 classical session?
Will do.

 what's the action you have configured when closing the lid, to suspend
 or hibernate?

 Mine is set to suspend.
 
 Okay, the action is consistent then. The only difference I see is that 
 suspending when closing the lid involves an ACPI action while suspending 
 from the menu doesn't (it's an action directly triggered by the user).

My first thought was ACPI issue.

Thanks,

-- 
elb...@gmail.com


-- 
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/4fbd36e8.4010...@gmail.com

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

[elbbit]

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 logged into the laptop by OpenSSH the laptop continues to respond,

With i915 blacklisted the laptop looks awful on-screen and becomes
completely unresponsive upon lid-close.

I find now that even without Xorg loaded (just getty) the kernel still
oops on lid-close when not blacklisted.

I have tried i915.semaphores=1 on the kernel command line, as
recommended by someone off Google with no difference.

I also tried noapic and acpi=off which didn't help either.

To note, I am getting MTRR allocation failed.  Graphics performance may
suffer. when the i915 kernel module loads during boot-time (drm) and
also *ERROR* MUX INFO call failed -- this last one appears to be fixed
upstream (I read it over two months ago) and the newer driver hasn't
made it to wheezy yet.

According to Intel website, this suspending bug is a major known issue:
S4 suspend-resume may fail on some machines unless 'nomodeset' kernel
parameter is used  http://intellinuxgraphics.org/2011Q4.html
This bug has been known for several driver releases and has recently
been fixed (10-Apr-2012), and seeing as the last driver release was
February this code is only in Intel's git repos?
https://bugs.freedesktop.org/show_bug.cgi?id=35648
https://bugs.freedesktop.org/show_bug.cgi?id=40241

I tested the Intel advised workaround which is nomodeset on the kernel
command line but that didn't work either.

Having completed an exhaustive search, I am considering transitioning my
laptop over to sid and leave the wife's on wheezy for testing.  I guess
we all just keep hitting our power buttons then!

On a side note, I'm not new to GNU but I am new to contributing.  I
realise my next question may be better aimed at debian-dev@ but can I
help in getting a new xserver-xorg-video-intel package built?  I notice
sid has the same as wheezy in this regard.

-- 
elb...@gmail.com


-- 
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/4fbd4bc5.3090...@gmail.com

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

[Sylvain Archenault]

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...@lists.debian.org

Archive: http://lists.debian.org/4fbd9d9d.3090...@laposte.net

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

[Camaleón]

On Mon, 21 May 2012 20:57:58 -0400, Sylvain Archenault wrote:

 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.

That's curious because closing the lid and suspending from menu should 
both trigger the same command unless what's the action you have 
configured when closing the lid, to suspend or hibernate?

 I tried kernel 3.3 trunk and got the same problem.
 
 Intel X driver is 2.18.0-2+b1.
 
 Here is the output from syslog:
 May 21 18:20:15 TichoLaptop kernel: [ 1658.787327] BUG: unable to handle 
 kernel paging request at c9001193396c 
 May 21 18:20:15 TichoLaptop kernel: [ 1658.787415] IP: [812474b8] 
 gen6_write_entry+0x4c/0x4f 
 May 21 18:20:15 TichoLaptop kernel: [ 1658.787493] PGD 1cf023067 PUD 
 1cf024067 PMD 1c89ee067 PTE 0
 May 21 18:20:15 TichoLaptop kernel: [ 1658.787570] Oops: 0002 [#1] SMP
 May 21 18:20:15 TichoLaptop kernel: [ 1658.787614] CPU 1 
 May 21 18:20:15 TichoLaptop kernel: [ 1658.788707] 
 May 21 18:20:15 TichoLaptop kernel: [ 1658.788732] Pid: 9739, comm: Xorg 
 Tainted: G C   3.2.0-2-amd64 #1 Dell Inc. XPS L412Z/008DD8 

(...)

 May 21 18:20:15 TichoLaptop kernel: [ 1658.790058] Call Trace: 
 May 21 18:20:15 TichoLaptop kernel: [ 1658.790097]  [81248526] ? 
 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 Debian BTS, eve more if running sid.

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/jpgfcf$isf$1...@dough.gmane.org

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

[elbbit]

Sorry to hijack the thread, but I suspect this problem may be related to
mine.  I've checked the Dell website for OP and our specs are similar
from the same manufacturer.

On 22/05/12 17:37, Camaleón wrote:
 On Mon, 21 May 2012 20:57:58 -0400, Sylvain Archenault wrote:
 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.

Same here except my pair of Alienware's run 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 suspending from menu 
 should both trigger the same command unless
That'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).

When logged into the laptop by OpenSSH the laptop continues to respond,
and in the log file (see pastebin below) you see me attempting to
shutdown the computer (around line 616) which succeeds.  However, once
lid-down-then-up-again the screen is frozen at the Gnome idle/lock
screen until the system cuts the power.  For me this confirms a screen
issue.  If I repeatedly press the power button or close the lid again
still nothing happens.

 what's the action you have configured when closing the lid, to 
 suspend or hibernate?
Mine is set to suspend.

 I tried kernel 3.3 trunk and got the same problem.
My kernel is 3.2.0, but this issue was not present on kernel 3.0.0 and I
noticed this behaviour start when kernel 3.1.0 was pushed to the testing
repository.

 Intel X driver is 2.18.0-2+b1.
My Intel driver is:  xserver-xorg-video-intel 2:2.18.0-2+b1

 Here is the output from syslog: snip
Mine is at http://paste.debian.net/170716 (3days)

 Looks like the Xorg server is crashing.
Indeed, and I think this is kernel related because when I boot with
kernel 3.0.0 this problem goes away and lid-closing performs a correct
system suspend.  I put the debug flag in pm-suspend and did a diff
comparison between a good suspend and a bad one, and there is no
difference except timestamps.

 I looked online, but I couldn't find a workaround.
 Yes, you did: suspend from the menu instead closing the lid ;-)
Pushing the power button to suspend works without flaw every time.

 Let me know if more information are needed.
Same here.

 I would report a kernel oops in Debian BTS, eve more if running sid.
I am reading up on how to submit bugs before blindly submitting them.
Does anyone know if this bug already has a report created for it?


-- 
elb...@gmail.com


-- 
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/4fbc7758.9050...@gmail.com

Kernel Oops when closing the lid on Dell XPS 14z

[Sylvain Archenault]

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 X driver is 2.18.0-2+b1.

Here is the output from syslog:
May 21 18:20:15 TichoLaptop kernel: [ 1658.787327] BUG: unable to handle 
kernel paging request at c9001193396c
May 21 18:20:15 TichoLaptop kernel: [ 1658.787415] IP: 
[812474b8] gen6_write_entry+0x4c/0x4f
May 21 18:20:15 TichoLaptop kernel: [ 1658.787493] PGD 1cf023067 PUD 
1cf024067 PMD 1c89ee067 PTE 0

May 21 18:20:15 TichoLaptop kernel: [ 1658.787570] Oops: 0002 [#1] SMP
May 21 18:20:15 TichoLaptop kernel: [ 1658.787614] CPU 1
May 21 18:20:15 TichoLaptop kernel: [ 1658.787637] Modules linked in: 
aesni_intel cryptd aes_x86_64 aes_generic acpi_cpufreq mperf 
cpufreq_powersave cpufreq_conservative cpufreq_userspace cpufreq_stats 
bnep rfcomm fuse loop ixgb 8390 8139too mii uvcvideo videodev 
v4l2_compat_ioctl32 media snd_hda_codec_hdmi snd_hda_codec_realtek 
joydev btusb bluetooth crc16 arc4 sr_mod cdrom iwlwifi snd_hda_intel 
i915 snd_hda_codec mac80211 snd_hwdep drm_kms_helper cfg80211 drm 
snd_pcm xhci_hcd snd_page_alloc processor battery dell_wmi dell_laptop 
ehci_hcd usbcore rfkill rts_pstor(C) snd_timer i2c_algo_bit i2c_i801 
dcdbas iTCO_wdt i2c_core iTCO_vendor_support snd ac psmouse 
sparse_keymap serio_raw power_supply button soundcore video atl1c 
usb_common wmi thermal_sys evdev pcspkr ext3 mbcache jbd sd_mod 
crc_t10dif ahci libahci libata scsi_mod

May 21 18:20:15 TichoLaptop kernel: [ 1658.788707]
May 21 18:20:15 TichoLaptop kernel: [ 1658.788732] Pid: 9739, comm: Xorg 
Tainted: G C   3.2.0-2-amd64 #1 Dell Inc. XPS L412Z/008DD8
May 21 18:20:15 TichoLaptop kernel: [ 1658.788847] RIP: 
0010:[812474b8]  [812474b8] gen6_write_entry+0x4c/0x4f
May 21 18:20:15 TichoLaptop kernel: [ 1658.788951] RSP: 
0018:8801c49b3aa0  EFLAGS: 00010202
May 21 18:20:15 TichoLaptop kernel: [ 1658.789017] RAX: 738b2015 
RBX: 0500 RCX: 00010001
May 21 18:20:15 TichoLaptop kernel: [ 1658.789098] RDX: 0001738b2010 
RSI: c9001193396c RDI: 0001738b2000
May 21 18:20:15 TichoLaptop kernel: [ 1658.789178] RBP: ce5b 
R08:  R09: 00049e04
May 21 18:20:15 TichoLaptop kernel: [ 1658.789261] R10: c9001190 
R11: 2d2d R12: 
May 21 18:20:15 TichoLaptop kernel: [ 1658.789328] R13: 00010001 
R14: 8801b0ba2000 R15: 0001
May 21 18:20:15 TichoLaptop kernel: [ 1658.789388] FS: 
7fbff0f5a880() GS:8801cfa4() knlGS:
May 21 18:20:15 TichoLaptop kernel: [ 1658.789456] CS:  0010 DS:  
ES:  CR0: 80050033
May 21 18:20:15 TichoLaptop kernel: [ 1658.789503] CR2: c9001193396c 
CR3: 0001a9c1c000 CR4: 000406e0
May 21 18:20:15 TichoLaptop kernel: [ 1658.789562] DR0:  
DR1:  DR2: 
May 21 18:20:15 TichoLaptop kernel: [ 1658.789622] DR3:  
DR6: 0ff0 DR7: 0400
May 21 18:20:15 TichoLaptop kernel: [ 1658.789681] Process Xorg (pid: 
9739, threadinfo 8801c49b2000, task 8801c644d6d0)

May 21 18:20:15 TichoLaptop kernel: [ 1658.789746] Stack:
May 21 18:20:15 TichoLaptop kernel: [ 1658.789765]  81248526 
8801b0ba2000  12d0
May 21 18:20:15 TichoLaptop kernel: [ 1658.789859]  880161435a00 
00010001 1000 8801c71c
May 21 18:20:15 TichoLaptop kernel: [ 1658.789956]  0500 
0500 a02ec93c 880161435a00

May 21 18:20:15 TichoLaptop kernel: [ 1658.790058] Call Trace:
May 21 18:20:15 TichoLaptop kernel: [ 1658.790097]  [81248526] 
? intel_gtt_insert_sg_entries+0x45/0x8d
May 21 18:20:15 TichoLaptop kernel: [ 1658.790192]  [a02ec93c] 
? i915_gem_gtt_bind_object+0x98/0xc6 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790286]  [a02e6ade] 
? i915_gem_object_bind_to_gtt+0x34c/0x495 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790380]  [812f4d36] 
? sk_wake_async+0x19/0x3c
May 21 18:20:15 TichoLaptop kernel: [ 1658.790458]  [a02e8f0e] 
? i915_gem_object_pin+0xb9/0x12d [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790550]  [a02eb75b] 
? i915_gem_do_execbuffer.isra.6+0x2f3/0x10e2 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790647]  [a02eb32a] 
? i915_gem_execbuffer_reserve.isra.4+0x1b3/0x2e7 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790752]  [a02eb8ad] 
? i915_gem_do_execbuffer.isra.6+0x445/0x10e2 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790847]  [a02ec7b3] 
? i915_gem_execbuffer2+0x4f/0x140 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790933]  [a02ec842

Re: Strange USB issue on 6.0.4 : kernel:[1202001.893158] Oops: 0010 [#5] SMP

[Camaleón]

On Tue, 27 Mar 2012 18:00:10 -0400, Dennis Clarke wrote:

 I have a HP external USB attached disk plugged into a USB port on my
 system.
 
 Periodically, every eight or twelve hours or so, and without any real
 pattern or trigger cause, I see the following message :
 
 root@aster:~#
 Message from syslogd@aster at Mar 26 15:23:02 ...
  kernel:[1202001.893158] Oops: 0010 [#5] SMP

(...)

Being a kernel oops, I would report it in Debian BTS.

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/jkvbj3$hqr$1...@dough.gmane.org

Re: Strange USB issue on 6.0.4 : kernel:[1202001.893158] Oops: 0010 [#5] SMP

[Dennis Clarke]

 On Tue, 27 Mar 2012 18:00:10 -0400, Dennis Clarke wrote:

 I have a HP external USB attached disk plugged into a USB port on my
 system.

 Periodically, every eight or twelve hours or so, and without any real
 pattern or trigger cause, I see the following message :

 root@aster:~#
 Message from syslogd@aster at Mar 26 15:23:02 ...
  kernel:[1202001.893158] Oops: 0010 [#5] SMP

 (...)

 Being a kernel oops, I would report it in Debian BTS.

okay, will do. thanks

-- 
--
http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x1D936C72FA35B44B
+-+---+
| Dennis Clarke   | Solaris and Linux and Open Source |
| dcla...@blastwave.org   | Respect for open standards.   |
+-+---+


-- 
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/35869.10.0.66.17.1332949773.squir...@interact.purplecow.org

Strange USB issue on 6.0.4 : kernel:[1202001.893158] Oops: 0010 [#5] SMP

[Dennis Clarke]

I have a HP external USB attached disk plugged into a USB port on my system.

Periodically, every eight or twelve hours or so, and without any real pattern
or trigger cause, I see the following message :

root@aster:~#
Message from syslogd@aster at Mar 26 15:23:02 ...
 kernel:[1202001.893158] Oops: 0010 [#5] SMP

Message from syslogd@aster at Mar 26 15:23:02 ...
 kernel:[1202001.893165] last sysfs file:
/sys/devices/pci:00/:00:02.0/usb3/3-1/3-1.3/3-1.3:1.0/host8/target8:0:0/8:0:0:0/block/sdc/uevent

Message from syslogd@aster at Mar 26 15:23:02 ...
 kernel:[1202001.893435] Stack:

Message from syslogd@aster at Mar 26 15:23:02 ...
 kernel:[1202001.893469] Call Trace:

Message from syslogd@aster at Mar 26 15:23:02 ...
 kernel:[1202001.893735] Code:  Bad RIP value.

Message from syslogd@aster at Mar 26 15:23:02 ...
 kernel:[1202001.893754] CR2: 00fd0019

The external USB disk is no longer mounted and any attemp to read it ( with a
simple ls ) results in IO errors.

I unplug it.

Wait 30 secs or so.

Plug it back in and then I see in /dev/sd? thus :

root@aster:~# ls -laptr /dev/sd*
brw-rw 1 root disk   8, 16 Mar 12 17:29 /dev/sdb
brw-rw 1 root disk   8,  0 Mar 12 17:29 /dev/sda
brw-rw 1 root disk   8, 17 Mar 12 17:29 /dev/sdb1
brw-rw 1 root disk   8,  3 Mar 12 17:29 /dev/sda3
brw-rw 1 root disk   8,  2 Mar 12 17:29 /dev/sda2
brw-rw 1 root disk   8,  1 Mar 12 17:29 /dev/sda1
brw-rw 1 root disk   8,  4 Mar 12 17:29 /dev/sda4
brw-rw 1 root floppy 8, 33 Mar 12 17:29 /dev/sdc1
brw-rw 1 root floppy 8, 32 Mar 12 17:29 /dev/sdc
brw-rw 1 root floppy 8, 96 Mar 27 21:53 /dev/sdg
brw-rw 1 root floppy 8, 97 Mar 27 21:53 /dev/sdg1

The last entry there /dev/sdg1 would be my external HP disk which I can now
mount :

root@aster:~# /bin/mount -v -t ext4 -o rw /dev/sdg1 /hp

Now the filesystem is usable with no real issues.

I have to repeat this process daily, once or twice, and the message on the
console are generally the same. More or less.

How would I go about debugging this issue if it is caused by the USB driver ?

Thank you in advance for any insights.

Dennis



-- 
--
http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x1D936C72FA35B44B
+-+---+
| Dennis Clarke   | Solaris and Linux and Open Source |
| dcla...@blastwave.org   | Respect for open standards.   |
+-+---+


-- 
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/37271.10.0.66.17.1332885610.squir...@interact.purplecow.org

kernel failure/oops

[Curt]

Booted the machine this afternoon, and in gnome I get a message that
goes something like this: Your kernel has had a failure, do you wish to
send the stack trace to kerneloops.org (or whatever)?  I said yes.  

Here is the oops/trace (if those are the proper terms) from /var/log/kern.log:

Feb  4 14:41:52 einstein kernel: [6.796893] [ cut here 
]
Feb  4 14:41:52 einstein kernel: [6.796913] WARNING: at 
/build/buildd-linux-2.6_2.6.32-41-amd64-ReqhZF
/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/fs-writeback.c:1122 
__mark_inode_dirty+0xe7/0x14a()
Feb  4 14:41:52 einstein kernel: [6.796920] Hardware name: Aspire X1430
Feb  4 14:41:52 einstein kernel: [6.796923] Modules linked in: loop(+) 
snd_hda_codec_realtek snd_hda_c
odec_atihdmi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer 
snd_seq_device rfkill psmouse
 snd i2c_piix4 serio_raw led_class pcspkr evdev soundcore fglrx(P) wmi 
snd_page_alloc i2c_core button proc
essor ext3 jbd mbcache sg sr_mod sd_mod crc_t10dif cdrom ata_generic 
usb_storage r8168 pata_atiixp ohci_hc
d ahci thermal libata ehci_hcd r8169 mii thermal_sys scsi_mod usbcore nls_base 
[last unloaded: scsi_wait_s
can]
Feb  4 14:41:52 einstein kernel: [6.796993] Pid: 763, comm: udisks-part-id 
Tainted: P   2.6.32
-5-amd64 #1
Feb  4 14:41:52 einstein kernel: [6.796998] Call Trace:
Feb  4 14:41:52 einstein kernel: [6.797008]  [811088bb] ? 
__mark_inode_dirty+0xe7/0x14a
Feb  4 14:41:52 einstein kernel: [6.797016]  [811088bb] ? 
__mark_inode_dirty+0xe7/0x14a
Feb  4 14:41:52 einstein kernel: [6.797024]  [8104df9c] ? 
warn_slowpath_common+0x77/0xa3
Feb  4 14:41:52 einstein kernel: [6.797033]  [811088bb] ? 
__mark_inode_dirty+0xe7/0x14a
Feb  4 14:41:52 einstein kernel: [6.797042]  [810ffe04] ? 
touch_atime+0xfe/0x127
Feb  4 14:41:52 einstein kernel: [6.797050]  [810b5b40] ? 
generic_file_aio_read+0x499/0x536
Feb  4 14:41:52 einstein kernel: [6.797058]  [810eee91] ? 
do_sync_read+0xce/0x113
Feb  4 14:41:52 einstein kernel: [6.797066]  [8106502a] ? 
autoremove_wake_function+0x0/0x2e
Feb  4 14:41:52 einstein kernel: [6.797074]  [810ccdd2] ? 
handle_mm_fault+0x35c/0x80f
Feb  4 14:41:52 einstein kernel: [6.797081]  [810ef8b4] ? 
vfs_read+0xa6/0xff
Feb  4 14:41:52 einstein kernel: [6.797087]  [810ef9c9] ? 
sys_read+0x45/0x6e
Feb  4 14:41:52 einstein kernel: [6.797095]  [81010b42] ? 
system_call_fastpath+0x16/0x1b
Feb  4 14:41:52 einstein kernel: [6.797099] ---[ end trace ab2cb3c5007e88c2 
]---

Is there anybody who can tell me what this signifies?  This machine is
two months old.

I have the feeling that nobody will be able to say whether this is
hardware, software, bad karma, or all of the above.  There will be
nothing to do but ensure proper backups have been made and wait.

Anyway.


-- 
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/slrnjiqfgp.24b.cu...@einstein.electron.org

Re: wheezy gdm3 s'arrete en route ??? OOPS

[Jean-Yves F. Barbier]

On Sun, 23 Oct 2011 14:58:09 +0200
Bruno gasc.br...@free.fr wrote:

J'ai posté un peu trop vite et hors sujet!

gdm peut-être intéressant quand il y a plusieurs utilisateurs différents,
mais si c'est une machine uniquement pour toi, laisse tomber: il bouffe
bcp trop de RAM et n'apporte rien dans ce cas.
Logue-toi en mode console et démarre X avec startx (package xinit).

Si tu veux absolument un graphic logger, il existe aussi slim qui est pômal.

Par ailleurs, wheezy n'est sans doute pas une bonne solution pour
quelqu'un qui commence - stable (squeeze) est préférable pour se 
faire la main; ne serais-ce que parce qu'on évite tous les PBs de
packages cassés ou qui disparaissent.

-- 
Falling in love makes smoking pot all day look like the ultimate in restraint.
-- Dave Sim, author of Cerebus.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/20111023155111.7b036fb1@anubis.defcon1

Re: mapage de touche OOPS

[Jean-Yves F. Barbier]

On Tue, 18 Oct 2011 21:39:46 +0200
prego Jérémy jer...@prego-network.net wrote:

Il fallait lire 'Insert' (au lieu du code touche 0xff63) bien entendu.

-- 
The difficult we do today; the impossible takes a little longer.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/20111018224513.0dc46e2b@anubis.defcon1

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

[Curt]

On 2011-09-10, Andrew Reid rei...@bellatlantic.net 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 bug report referenced upthread, I think it's likely to be a fix.


Okey-dokey.


-- 
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/slrnj6p9p1.2bl.cu...@einstein.electron.org

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

[Curt]

On 2011-09-11, Curt cu...@free.fr wrote:
 On 2011-09-10, Andrew Reid rei...@bellatlantic.net 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 bug report referenced upthread, I think it's likely to be a fix.


 Okey-dokey.


No more oops after installing the most recent kernel update. They work
fast these guys.


-- 
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/slrnj6pkeh.2nd.cu...@einstein.electron.org

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

[Curt]

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...@lists.debian.org
Archive: http://lists.debian.org/slrnj6mas0.2k1.cu...@einstein.electron.org

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

[Camaleón]

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.

Can you explain what is the current issue? I mean, does the oops happen 
when launching the browser? What's the content of the oops? I could not 
understand what they were referring to :-?

(searching...)

This can be related:
http://www.google.vu/support/forum/p/Chrome/thread?tid=51f63d2301865cebhl=en

Which fianlly points to this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966

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.2011.09.10.11.19...@gmail.com

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

[Curt]

On 2011-09-10, Camaleón noela...@gmail.com 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 users in the Spanish mailing list are also reporting 
 this.

 Can you explain what is the current issue? I mean, does the oops happen 
 when launching the browser? What's the content of the oops? I could not 

No, thus the word random. Appears to happen randomly (without
predicability) while surfing, effectively crashing the browser.

 understand what they were referring to :-?

Content? 
 
Sep  9 17:40:12 einstein kernel: [22866.749031] BUG: unable to handle kernel 
paging request at fff
3
Sep  9 17:40:12 einstein kernel: [22866.749043] IP: [8112f98d] 
m_stop+0x15/0x4c
Sep  9 17:40:12 einstein kernel: [22866.749060] PGD 1003067 PUD 1004067 PMD 0 
Sep  9 17:40:12 einstein kernel: [22866.749070] Oops:  [#1] SMP 
Sep  9 17:40:12 einstein kernel: [22866.749076] last sysfs file: 
/sys/devices/system/cpu/cpu0/cpufreq/scal
ing_cur_freq
Sep  9 17:40:12 einstein kernel: [22866.749083] CPU 0 
Sep  9 17:40:12 einstein kernel: [22866.749087] Modules linked in: powernow_k8 
cpufreq_conservative cpufre
q_stats cpufreq_powersave cpufreq_userspace parport_pc ppdev lp parport 
binfmt_misc fuse firewire_sbp2 loo
p snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss 
snd_mixer_oss snd_pcm snd_seq_mi
di snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device acer_wmi snd 
rfkill led_class soundcore
 wmi psmouse i2c_nforce2 nvidia(P) k10temp pcspkr i2c_core edac_core evdev 
snd_page_alloc edac_mce_amd ser
io_raw video output button processor ext3 jbd mbcache sg sd_mod sr_mod cdrom 
crc_t10dif usbhid ata_generic
 usb_storage hid ohci_hcd pata_amd ahci firewire_ohci firewire_core fan 
crc_itu_t libata ehci_hcd scsi_mod
 thermal thermal_sys forcedeth usbcore nls_base [last unloaded: scsi_wait_scan]
Sep  9 17:40:12 einstein kernel: [22866.749200] Pid: 2413, comm: chrome 
Tainted: P   2.6.32-5-amd6
4 #1 Aspire X1301

(etc)

 (searching...)

 This can be related:
 http://www.google.vu/support/forum/p/Chrome/thread?tid=51f63d2301865cebhl=en

 Which fianlly points to this:
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966

That's it.  I guess the kernel team is working on it, God bless 'em.

 -- 
 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/slrnj6mmn0.2vl.cu...@einstein.electron.org

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

[Stephen Allen]

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 kernel latest Chrome Developer vs for 
Linux.


-- 
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/20110910161053.ga17...@thinkpad.gateway.2wire.net

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

[Curt]

On 2011-09-10, Stephen Allen marathon.duran...@gmail.com 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?
 
 ---end quoted text---

 No all is fine here on Wheezy 3.0.01 kernel latest Chrome Developer vs for 
 Linux.

I'm talking about the recent kernel security update in stable to:

2.6.32-35squeeze1


-- 
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/slrnj6n6sb.3je.cu...@einstein.electron.org

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

[Andrew Reid]

 On 2011-09-10, Camaleón noela...@gmail.com 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 users in the Spanish mailing list are also reporting
  this.
  
  Can you explain what is the current issue? I mean, does the oops happen
  when launching the browser? What's the content of the oops? I could not
 
 No, thus the word random. Appears to happen randomly (without
 predicability) while surfing, effectively crashing the browser.
 

  I am also seeing this, with Google Chrome Beta 14.0.835.159-r100066,
and the most recent kernel update, 2.6.32-35squeeze1, on 32-bit.

  I am running some fairly flash-heavy stuff, and weirdly in one 
instance, the browser reported that a page had become unresponsive
when the flash content on that page was still fine -- then the
browser exited, and I saw the kernel messages.

  My kern.log entries are similar to those below, they begin with
unable to handle kernel paging request at fff3 (I am on a 32-bit 
system).

  Anecdotally, it seems that it doesn't happen if the browser is
the only thing running on the desktop, but I don't have a lot of data
on that, I only did the kernel update a few hours ago.

-- A.

 
 
 Sep  9 17:40:12 einstein kernel: [22866.749031] BUG: unable to handle
 kernel paging request at fff 3
 Sep  9 17:40:12 einstein kernel: [22866.749043] IP: [8112f98d]
 m_stop+0x15/0x4c Sep  9 17:40:12 einstein kernel: [22866.749060] PGD
 1003067 PUD 1004067 PMD 0 Sep  9 17:40:12 einstein kernel: [22866.749070]
 Oops:  [#1] SMP Sep  9 17:40:12 einstein kernel: [22866.749076] last
 sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scal ing_cur_freq
 Sep  9 17:40:12 einstein kernel: [22866.749083] CPU 0
 Sep  9 17:40:12 einstein kernel: [22866.749087] Modules linked in:
 powernow_k8 cpufreq_conservative cpufre q_stats cpufreq_powersave
 cpufreq_userspace parport_pc ppdev lp parport binfmt_misc fuse
 firewire_sbp2 loo p snd_hda_codec_realtek snd_hda_intel snd_hda_codec
 snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_mi di snd_rawmidi
 snd_seq_midi_event snd_seq snd_timer snd_seq_device acer_wmi snd rfkill
 led_class soundcore wmi psmouse i2c_nforce2 nvidia(P) k10temp pcspkr
 i2c_core edac_core evdev snd_page_alloc edac_mce_amd ser io_raw video
 output button processor ext3 jbd mbcache sg sd_mod sr_mod cdrom crc_t10dif
 usbhid ata_generic usb_storage hid ohci_hcd pata_amd ahci firewire_ohci
 firewire_core fan crc_itu_t libata ehci_hcd scsi_mod thermal thermal_sys
 forcedeth usbcore nls_base [last unloaded: scsi_wait_scan] Sep  9 17:40:12
 einstein kernel: [22866.749200] Pid: 2413, comm: chrome Tainted: P
   2.6.32-5-amd6 4 #1 Aspire X1301
 
 (etc)
 
  (searching...)
  
  This can be related:
  http://www.google.vu/support/forum/p/Chrome/thread?tid=51f63d2301865cebh
  l=en
  
  Which fianlly points to this:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640966
 
 That's it.  I guess the kernel team is working on it, God bless 'em.
--
Andrew Reid / rei...@bellatlantic.net


--
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/201109101340.20782.rei...@bellatlantic.net

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

[Andrew Reid]

 On 2011-09-10, Stephen Allen marathon.duran...@gmail.com 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?
  
  ---end quoted text---
  
  No all is fine here on Wheezy 3.0.01 kernel latest Chrome Developer vs
  for Linux.
 
 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 bug report referenced upthread, I think it's likely to be a fix.

 -- A.
--
Andrew Reid / rei...@bellatlantic.net


-- 
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/201109101748.31722.rei...@bellatlantic.net

Third kernel oops in three days

[Jonathan Hanger]

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 game under Wine that was running really slow
(see my email Dependencies problem with libgl1-mesa-glx a few days
ago). The second happened yesterday and the third today.

I think the three oops are the exact same, as I remember checking the
error log (the last oops is attached under this).

Thanks, Jonathan.



Kernel failure message 1:
[ cut here ]
WARNING: at 
/build/buildd-linux-2.6_2.6.39-2-i386-Ow09ch/linux-2.6-2.6.39/debian/build/source_i386_none/block/genhd.c:1556
disk_clear_events+0xa9/0xd2()
Hardware name: KP236AA-ABF a6460.fr
Modules linked in: snd_seq_dummy isofs nls_utf8 nls_cp437 vfat fat udf
webcamstudio(O) videodev media acpi_cpufreq mperf cpufreq_stats
cpufreq_userspace cpufreq_powersave cpufreq_conservative parport_pc
ppdev lp parport rfcomm bnep bluetooth rfkill snd_hrtimer binfmt_misc
fuse nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc loop
firewire_sbp2 snd_hda_codec_realtek snd_hda_intel nouveau
snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm ttm
drm_kms_helper snd_seq_midi drm snd_rawmidi snd_seq_midi_event snd_seq
evdev i2c_algo_bit power_supply video i2c_i801 processor button
snd_timer snd_seq_device snd psmouse i2c_core serio_raw pcspkr
thermal_sys soundcore snd_page_alloc ext4 mbcache jbd2 crc16 sg sd_mod
sr_mod crc_t10dif cdrom usbhid hid usb_storage uas uhci_hcd ahci
libahci libata firewire_ohci firewire_core scsi_mod ehci_hcd r8169
usbcore crc_itu_t mii [last unloaded: scsi_wait_scan]
Pid: 2601, comm: udisks-daemon Tainted: G   O 2.6.39-2-686-pae #1
Call Trace:
 [c1036b4d] ? warn_slowpath_common+0x6a/0x7b
 [c114ae17] ? disk_clear_events+0xa9/0xd2
 [c1036b6b] ? warn_slowpath_null+0xd/0x10
 [c114ae17] ? disk_clear_events+0xa9/0xd2
 [c10ecccd] ? check_disk_change+0x17/0x45
 [f8350421] ? sd_open+0xc8/0x164 [sd_mod]
 [c10ed7da] ? __blkdev_get+0xb5/0x2f3
 [c10edba4] ? blkdev_get+0x18c/0x270
 [c11204b1] ? fsnotify_perm+0x4f/0x5a
 [c10ed174] ? bd_acquire+0x20/0x8f
 [c10cb191] ? __dentry_open+0x15b/0x236
 [c10cb2ef] ? nameidata_to_filp+0x3a/0x45
 [c10edc88] ? blkdev_get+0x270/0x270
 [c10d5119] ? do_last+0x441/0x51c
 [c10d5681] ? path_openat+0x97/0x27d
 [c10d590b] ? do_filp_open+0x21/0x5d
 [c10caefc] ? do_sys_open+0x58/0xd1
 [c10cafb9] ? sys_open+0x1e/0x23
 [c12b715f] ? sysenter_do_call+0x12/0x28
 [c12b] ? flow_cache_cpu_prepare+0x3f/0x64
---[ end trace 70e99342bef73d5e ]---


-- 
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/CAJE+AHbvFMNBw7QQQr3j7cWC+XrL_s=q4fgobyf6nliarzx...@mail.gmail.com

Re: Third kernel oops in three days

[Camaleón]

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/buildd-linux-2.6_2.6.39-2-i386-Ow09ch/linux-2.6-2.6.39/debian/build/source_i386_none/block/genhd.c:1556
  disk_clear_events+0xa9/0xd2()

(...)

You seem to be hitting this upstream kernel bug:

Warning at block/genhd.c:1556 disk_clear_events 
https://bugzilla.kernel.org/show_bug.cgi?id=34662

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.2011.07.04.14.36...@gmail.com

Re: kernel bug - Lenny 2.6.26-2-amd64 -OOPS

[Jean-Yves F. Barbier]

Le Tue, 10 Aug 2010 23:14:45 +0200,
Alain Vaugham al...@vaugham.com a écrit :

Oops: gros oubli. évidemment, ça peut très bien venir du kernel aussi...

-- 
Live Free or Live in Massachusetts.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/20100810233026.7948d...@anubis.defcon1

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

[Sven Joachim]

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   2.6.32-3-amd64 
 #1  

…is more than four months old.  It is quite possible that the problem
has already been solved.

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.org/87mxtuleuh@turtle.gmx.de

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

[briand]

On Wed, 14 Jul 2010 09:09:10 +0200
Sven Joachim svenj...@gmx.de 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 current
 one…
 
  [24128.816259] Pid: 716, comm: scsi_eh_10 Tainted: P
  2.6.32-3-amd64 #1  
 
 …is more than four months old.  It is quite possible that the problem
 has already been solved.
 

Looks like the latest kernel is -5, is that correct ?

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/20100714183551.52e85...@windy.deldotd.com

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

[Sven Joachim]

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.org/87d3upqudu@turtle.gmx.de

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

[briand]

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 do anything, but I thought I'd ask.  If there's a chance then I'll
go ahead and submit a bug report and do what I can to help figure out
the problem.

I think it has something to do with firewire as I'm getting lots of
messages of all sorts of things being broken, and yet firewire seems to
be working fine.

The question is , submit to Debian or to LKML ?


Thanks

Brian

[24128.816103] IP: [a00afde6] sbp2_scsi_abort+0x19/0x7b 
[firewire_sbp2]
[24128.816121] PGD 1160b3067 PUD 11e490067 PMD 0 
[24128.816129] Oops:  [#1] SMP 
[24128.816135] last sysfs file: /sys/devices/pci:00/:00:0e.0/class
[24128.816141] CPU 0 
[24128.816145] Modules linked in: ip6table_filter ip6_tables iptable_filter 
ip_tables x_tables powernow_k8 cpufreq_stats cpufreq_powersave 
cpufreq_conservative cpufreq_userspace ppdev lp vboxnetadp vboxnetflt vboxdrv 
kvm_amd kvm fuse nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc 
loop dm_mod cp210x usblp usbhid hid usbserial snd_hda_codec_realtek ohci_hcd sg 
firewire_sbp2 ide_cd_mod cdrom snd_hda_intel snd_hda_codec snd_hwdep snd_pcm 
snd_seq snd_timer snd_seq_device snd firewire_ohci nvidia(P) ehci_hcd soundcore 
edac_core i2c_nforce2 usbcore firewire_core ahci forcedeth snd_page_alloc 
k8temp amd74xx i2c_core edac_mce_amd evdev nls_base crc_itu_t pata_jmicron 
parport_pc processor parport pcspkr button ext3 jbd mbcache sd_mod crc_t10dif 
thermal fan thermal_sys ata_generic ide_pci_generic ide_core sata_nv libata 
scsi_mod
[24128.816259] Pid: 716, comm: scsi_eh_10 Tainted: P   2.6.32-3-amd64 
#1  
[24128.816264] RIP: 0010:[a00afde6]  [a00afde6] 
sbp2_scsi_abort+0x19/0x7b [firewire_sbp2]
[24128.816277] RSP: 0018:88011d423d30  EFLAGS: 00010286
[24128.816282] RAX:  RBX: 88011e799c00 RCX: 88011dabece8
[24128.816288] RDX: 88011d423d70 RSI: 2002 RDI: a00b0ec1
[24128.816293] RBP: 8800dfabc500 R08: 88011d422000 R09: 880005a155c0
[24128.816298] R10: 8800bb670700 R11: 0246 R12: 
[24128.816303] R13: 0286 R14: 09c4 R15: 
[24128.816310] FS:  7f7c40cb9720() GS:880005a0() 
knlGS:f4db1710
[24128.816316] CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
[24128.816321] CR2: 0010 CR3: 00011e1ef000 CR4: 06f0
[24128.816326] DR0:  DR1:  DR2: 
[24128.816332] DR3:  DR6: 0ff0 DR7: 0400
[24128.816338] Process scsi_eh_10 (pid: 716, threadinfo 88011d422000, task 
88011dabe9f0)
[24128.816342] Stack:
[24128.816346]  880119ac5000 8800dfabc500  
0286
[24128.816353] 0 880119ac5000 a0003e94  
88020002
[24128.816361] 0 88011d423d70 88011d423d70 00020002 
0006
[24128.816371] Call Trace:
[24128.816390]  [a0003e94] ? scsi_send_eh_cmnd+0x1b7/0x29e [scsi_mod]
[24128.816401]  [a00af84f] ? sbp2_cancel_orbs+0xbb/0xe7 
[firewire_sbp2]
[24128.816417]  [a0003fa3] ? scsi_eh_tur+0x28/0x78 [scsi_mod]
[24128.816433]  [a0004cd2] ? scsi_error_handler+0x328/0x5b5 [scsi_mod]
[24128.816449]  [a00049aa] ? scsi_error_handler+0x0/0x5b5 [scsi_mod]
[24128.816460]  [81064789] ? kthread+0x79/0x81
[24128.816469]  [81011baa] ? child_rip+0xa/0x20
[24128.816476]  [81064710] ? kthread+0x0/0x81
[24128.816482]  [81011ba0] ? child_rip+0x0/0x20
[24128.816486] Code: 02 74 09 c6 83 93 00 00 00 24 31 d2 59 5b 89 d0 5d c3 53 
48 83 ec 20 48 8b 07 48 c7 c7 c1 0e 0b a0 48 8b 98 88 00 00 00 48 8b 03 48 8b 
70 10 31 c0 e8 13 d6 23 e1 48 8b 03 48 8b 40 08 48 8b 30 
[24128.816543] RIP  [a00afde6] sbp2_scsi_abort+0x19/0x7b 
[firewire_sbp2]
[24128.816553]  RSP 88011d423d30
[24128.816557] CR2: 0010
[24128.816562] ---[ end trace f299684bf0dbe66c ]---


-- 
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/20100713193149.04a36...@windy.deldotd.com

oops

[Jean-Yves F. Barbier]

Jean-Yves F. Barbier a écrit :
 Keven Chaussé a écrit :
 ...

avant tout, valide ta conf avec le driver non-accéléré de Xorg: nv
histoire d'éliminer des interractions possibles entre driver proprio
et conf.

-- 
I can't complain, but sometimes I still do.
-- Joe Walsh

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org

oops

[Jean-Yves F. Barbier]

Jean-Yves F. Barbier a écrit :
 (WW) xf86OpenConsole: setsid failed: Operation not permitted
 anormal: le user est-il bien dans le groupe video et les droits de
 /dev/nvidia* (s'ils sont là) sont-ils à root:video c440?

c660

-- 
Spare no expense to save money on this one.
-- Samuel Goldwyn

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org

Kernel Oops.

[Tonio]

Bonjour,

J'ai un soucis avec un vieil ordinateur dédié à la bureautique : celui 
ci plante régulièrement (écran, clavier et souris bloqué), pourtant le 
système tourne toujours puisque j'arrive à me connecter via ssh dessus 
et un vim /var/log/kern.log m'informe de ceci :



Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187548] BUG: unable to 
handle kernel NULL pointer dereference at 0020
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187558] IP: [c0283be9] 
sock_poll+0x9/0xe

Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187572] *pde = 
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187576] Oops:  [#1] SMP
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187580] last sysfs file: 
/sys/devices/pci:00/:00:02.0/usb2/2-2/2-2:1.0/usb/lp0/dev
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187586] Modules linked 
in: usblp nvidia(P) ppdev lp ipt_REJECT xt_tcpudp xt_state iptable_nat 
nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter 
ip_tables x_tables loop snd_wavefront snd_intel8x0 snd_cs4236 
snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_wss_lib 
snd_opl3_lib snd_hwdep snd_pcm snd_mpu401 snd_mpu401_uart snd_seq_midi 
snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd 
evdev ns558 snd_page_alloc shpchp pci_hotplug soundcore gameport pcspkr 
parport_pc parport processor button i2c_nforce2 i2c_core ext3 jbd 
mbcache ide_cd_mod cdrom ide_gd_mod ide_pci_generic usbhid hid amd74xx 
ide_core ata_generic libata ohci_hcd ehci_hcd forcedeth scsi_mod usbcore 
nvidia_agp agpgart floppy thermal fan thermal_sys

Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187656]
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187662] Pid: 2398, comm: 
Xorg Tainted: P   (2.6.30-bpo.1-686 #1) A7N8X-X
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187666] EIP: 
0060:[c0283be9] EFLAGS: 00013246 CPU: 0
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187671] EIP is at 
sock_poll+0x9/0xe
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187674] EAX: f604b4a0 
EBX:  ECX:  EDX: f4f87200
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187678] ESI:  
EDI: f604b4a0 EBP:  ESP: f6511b88
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187682]  DS: 007b ES: 
007b FS: 00d8 GS: 0033 SS: 0068
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187687] Process Xorg 
(pid: 2398, ti=f651 task=f6894c70 task.ti=f651)

Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187690] Stack:
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187692]  2000 
c0198835 0020 f6511f9c f6511f60 01000895 f6511e38 
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187701]  05f5e100 
f6511ec0 f6511ee0 f6511f00 f6511e60 f6511e80 f6511ea0 ffc2783a
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187710]   
 ffc2783a     

Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187718] Call Trace:
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187722]  [c0198835] ? 
do_select+0x286/0x3f9
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187733]  [c0198d4e] ? 
__pollwait+0x0/0x9d
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187738]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187744]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187749]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187755]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187760]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187766]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187771]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187776]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187782]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187787]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187792]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187798]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187803]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187808]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187814]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187819]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187824]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187830]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187835]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187840]  [c0198deb] ? 
pollwake+0x0/0x55
Nov 22 16:29:43 BoucherieSanzoS kernel: [ 9438.187846]  [c0198ae6] ? 
core_sys_select+0x13e/0x1c2
Nov 22 16:29:43

Re: Kernel Oops.

[Jean-Yves F. Barbier]

Tonio a écrit :
 Bonjour,
 
 J'ai un soucis avec un vieil ordinateur dédié à la bureautique : celui
 ci plante régulièrement (écran, clavier et souris bloqué), pourtant le
...

 J'ai testé le matériel avec un certain nombre d'outils qui m'indiquent

quels outils?

 que tout semble correct de ce côté.
 Le problème reste le même avec  un autre noyau.
 J'ai essayé avec des drivers libres et avec des proprios.

Vérifie les températures (CPU  chipset)

Reteste avec l'AGP Gart du kernel

Si ça plante toujours, teste la RAM avec memtest86+ (plusieurs passes ET
intervertion des barettes entre les tests)

-- 
Mate, this parrot wouldn't VOOM if you put four million volts through it!
-- Monty Python

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot
``spam'' dans vos champs From et Reply-To:

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org

Re: Kernel Oops.

[Tonio]

Jean-Yves F. Barbier a écrit :

Tonio a écrit :
  

Bonjour,

J'ai un soucis avec un vieil ordinateur dédié à la bureautique : celui
ci plante régulièrement (écran, clavier et souris bloqué), pourtant le


...

  

J'ai testé le matériel avec un certain nombre d'outils qui m'indiquent



quels outils?

  
Ceux trouvés sur Ultimate Boot Cd, j'ai notamment utilisé StressCpu et 
Memtest86+

que tout semble correct de ce côté.
Le problème reste le même avec  un autre noyau.
J'ai essayé avec des drivers libres et avec des proprios.



Vérifie les températures (CPU  chipset)

Reteste avec l'AGP Gart du kernel
  

Je vais jeter un oeil de ce côté.

Si ça plante toujours, teste la RAM avec memtest86+ (plusieurs passes ET
intervertion des barettes entre les tests)

  
Il y a eu un bip sonore et ça a freezé... Ce qui m'étonne c'est que je 
puisse toujours accéder à la machine via ssh, que l'ensemble des 
processus continuent de fonctionner (d'après ps aux et top). 
Pourtant j'ai beau tuer ceux liés à xserver et xfce, le clavier, la 
souris et l'écran reste bloqué.


Je vais refaire les tests.


Merci pour ces pistes


--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot
``spam'' dans vos champs From et Reply-To:

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org

Re: changement de disque OOPS

[Jean-Yves F. Barbier]

Jean-Yves F. Barbier a écrit :
 démarrer sur un live CD
 monter partoche HD source  partoche HD destination
 cd /pointdemontageHDsource
 cp -a . /pointdemontageHDdestination/

SAUF /proc!

 café, pizza (croissants?)

Recrééer un /proc vide avec les bonnes permissions

 remplacement vieux HD par nouveau
 démarrer sur un live CD
 faire un chroot sur la racine du nouveau HD
 pour lilo: lilo -v
 pour grub: jsais pas (j'aime pas)
 rebooter
 

-- 
No matter where I go, the place is always called here.

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists Vous pouvez aussi ajouter le mot
``spam'' dans vos champs From et Reply-To:

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org

FYI: No X ... oops

[Osamu Aoki]

Hi,

(CCing Carlos Carrero Gutierrez since it may be his problem too)

I did some minor system tweaks and rebooted...  alas, X does not start on 
lenny.  
Careful reading of error message pointed me to missing /dev/agpgart.  My
dual boot system function works OK.  So this is software issue.

 # modprobe intel-agp

Hmmm... does not work. 

I did 

# depmod -a

Then system reboot OK.

I do not have time to find which package or action caused this trouble
but if you find similar problem, recreating  modules.dep and map files
may be good idea.

Osamu


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

vsftpd problem 500 OOPS: cannot change directory

[lau]

Hi everyone,

I've been trying to set up a ftp server using vsftpd. I would like to 
create two accounts, namely ftpmovies and ftpmusic pointing respectively 
to /home/lau/movies and /home/lau/music.

According to my /etc/passwd file, those accounts are like this:
  ftpmusic:x:1001:1001:,,,:/home/lau/music/:/bin/bash
  ftpmovies:x:1002:1002:,,,:/home/lau/movies/:/bin/bash

Here is my vsftpd.conf:

anonymous_enable=YES
local_enable=YES
write_enable=NO
local_umask=022
#anon_upload_enable=YES
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=NO
xferlog_std_format=YES
ftpd_banner=KIKO!!
chroot_local_user=YES
chroot_list_enable=NO
chroot_list_file=/etc/vsftpd.chroot_list
listen=YES
tcp_wrappers=YES
no_anon_password=YES
listen=YES
anon_root=/home/lau

So to start with, i know that the chroot_local_user parameter is not 
relevant here, since changing it to NO doesn't solve the problem. However,


usermod -d /home/ftpmovies ftpmovies

is successful but is not what i'm trying to do. I read that disabling 
SELinux should solve the problem. Here is my config:


# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these two values:
# default - equivalent to the old strict and targeted policies
# mls - Multi-Level Security (for military and educational use)
# src - Custom policy built from source
SELINUXTYPE=default

# SETLOCALDEFS= Check local definition changes
SETLOCALDEFS=0

Unfortunately, setting SELINUX to disabled doesn't change anything.

Anyone has a solution for this? Thanks in advance!



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: vsftpd problem 500 OOPS: cannot change directory

[Jeff D]

On Wed, 29 Oct 2008, lau wrote:

 Hi everyone,

 I've been trying to set up a ftp server using vsftpd. I would like to create
 two accounts, namely ftpmovies and ftpmusic pointing respectively to
 /home/lau/movies and /home/lau/music.
 According to my /etc/passwd file, those accounts are like this:
   ftpmusic:x:1001:1001:,,,:/home/lau/music/:/bin/bash
   ftpmovies:x:1002:1002:,,,:/home/lau/movies/:/bin/bash

 Here is my vsftpd.conf:

 anonymous_enable=YES
 local_enable=YES
 write_enable=NO
 local_umask=022
 #anon_upload_enable=YES
 dirmessage_enable=YES
 xferlog_enable=YES
 connect_from_port_20=NO
 xferlog_std_format=YES
 ftpd_banner=KIKO!!
 chroot_local_user=YES
 chroot_list_enable=NO
 chroot_list_file=/etc/vsftpd.chroot_list
 listen=YES
 tcp_wrappers=YES
 no_anon_password=YES
 listen=YES
 anon_root=/home/lau

 So to start with, i know that the chroot_local_user parameter is not relevant
 here, since changing it to NO doesn't solve the problem. However,

 usermod -d /home/ftpmovies ftpmovies


So, I'm unclear here, above you show the home dir for ftpmovies being in
/home/lau/movies/ and here you change it to /home/ftpmovies.  Does
/home/ftpmovies exist and have the proper permissions set for ftpmovies?


Jeff


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Kernel oops on Lenny, when opening tabs in Firefox

[Carl Fink]

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 005a RIP: 
Aug 10 11:22:47 NitpickingHP2 kernel:  [c200013a4454]
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 nf_nat
nf_conntrack_ipv4 nf_conntrack ip_tables x_tables vmnet(P) vmblock vmmon(P) b
infmt_misc rfcomm l2cap bluetooth ipv6 ppdev parport_pc lp parport powernow_k8 
cpufreq_userspace cpufreq_powersave
cpufreq_ondemand cpufreq_stats freq_table cpufreq_conservative nt
fs nls_iso8859_1 nls_cp437 vfat fat dm_snapshot dm_mirror dm_mod vboxdrv 
firewire_sbp2 loop joydev snd_hda_intel
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd psmouse soundcore p
cspkr serio_raw snd_page_alloc k8temp i2c_nforce2 i2c_core video output battery 
button ac evdev ext3 jbd mbcache sd_mod
ide_cd cdrom generic sata_nv amd74xx ide_core sdhci firewire
_ohci ata_generic ricoh_mmc firewire_core crc_itu_t mmc_core ehci_hcd libata 
scsi_mod forcedeth ohci_hcd thermal
processor fan
Aug 10 11:22:47 NitpickingHP2 kernel: Pid: 3628, comm: ntos_wq Tainted: P   
 2.6.24-1-amd64 #1
Aug 10 11:22:47 NitpickingHP2 kernel: RIP: 0010:[c200013a4454]  
[c200013a4454]
Aug 10 11:22:47 NitpickingHP2 kernel: RSP: 0018:8100644ebc88  EFLAGS: 
00010246
Aug 10 11:22:47 NitpickingHP2 kernel: RAX: 0001 RBX: 
c235c000 RCX: c235c000
Aug 10 11:22:47 NitpickingHP2 kernel: RDX: 000a RSI: 
810026d32000 RDI: 0002
Aug 10 11:22:47 NitpickingHP2 kernel: RBP: 0006 R08: 
0006 R09: 0006
Aug 10 11:22:47 NitpickingHP2 kernel: R10: 8100151896d8 R11: 
8039da04 R12: 
Aug 10 11:22:47 NitpickingHP2 kernel: R13:  R14: 
0017 R15: 0001
Aug 10 11:22:47 NitpickingHP2 kernel: FS:  2b4cc58f3b20() 
GS:80514000() knlGS:f22cab90
Aug 10 11:22:47 NitpickingHP2 kernel: CS:  0010 DS: 0018 ES: 0018 CR0: 
8005003b
Aug 10 11:22:47 NitpickingHP2 kernel: CR2: 005a CR3: 
6f57e000 CR4: 06e0
Aug 10 11:22:47 NitpickingHP2 kernel: DR0:  DR1: 
 DR2: 
Aug 10 11:22:47 NitpickingHP2 kernel: DR3:  DR6: 
0ff0 DR7: 0400
Aug 10 11:22:47 NitpickingHP2 kernel: Process ntos_wq (pid: 3628, threadinfo 
8100644ea000, task 8100794c5000)
Aug 10 11:22:47 NitpickingHP2 kernel: Stack:  8023e0ea 0009 
81006f5ff248 8873bba5
Aug 10 11:22:47 NitpickingHP2 kernel:  c235e3a0 0286 
8023e280 c235e3a0
Aug 10 11:22:47 NitpickingHP2 kernel:  0286 c23497e0 
8873bba5 c235e3a0
Aug 10 11:22:47 NitpickingHP2 kernel: Call Trace:
Aug 10 11:22:47 NitpickingHP2 kernel:  [8023e0ea] 
lock_timer_base+0x26/0x4c
Aug 10 11:22:47 NitpickingHP2 kernel:  [8873bba5] 
:ndiswrapper:kdpc_worker+0x0/0x132
Aug 10 11:22:47 NitpickingHP2 kernel:  [8023e280] 
__mod_timer+0xc3/0xd1
Aug 10 11:22:47 NitpickingHP2 kernel:  [8873bba5] 
:ndiswrapper:kdpc_worker+0x0/0x132
Aug 10 11:22:47 NitpickingHP2 kernel:  [8873b9b1] 
:ndiswrapper:wrap_set_timer+0x2d/0x37
Aug 10 11:22:47 NitpickingHP2 kernel:  [88748ac7] 
:ndiswrapper:win2lin2+0xe/0x11
Aug 10 11:22:47 NitpickingHP2 kernel:  [8873bba5] 
:ndiswrapper:kdpc_worker+0x0/0x132
Aug 10 11:22:47 NitpickingHP2 kernel:  [88748adb] 
:ndiswrapper:win2lin3+0x11/0x14
Aug 10 11:22:47 NitpickingHP2 kernel:  [8022d336] 
dequeue_entity+0x12/0x3c
Aug 10 11:22:47 NitpickingHP2 kernel:  [8873bba5] 
:ndiswrapper:kdpc_worker+0x0/0x132
Aug 10 11:22:47 NitpickingHP2 kernel:  [88748ab6] 
:ndiswrapper:win2lin1+0xb/0xe
Aug 10 11:22:47 NitpickingHP2 kernel:  [80413f4b] 
thread_return+0x3d/0xab
Aug 10 11:22:47 NitpickingHP2 kernel:  [8873bc78] 
:ndiswrapper:kdpc_worker+0xd3/0x132
Aug 10 11:22:47 NitpickingHP2 kernel:  [8873db98] 
:ndiswrapper:ntos_work_worker+0x0/0x67
Aug 10 11:22:47 NitpickingHP2 kernel:  [8873bc5f] 
:ndiswrapper:kdpc_worker+0xba/0x132
Aug 10 11:22:47 NitpickingHP2 kernel:  [8024470d] 
run_workqueue+0x7f/0x10b
Aug 10 11:22:47 NitpickingHP2 kernel:  [8024501f] 
worker_thread+0x0/0xe4
Aug 10 11:22:47 NitpickingHP2 kernel:  [802450f9] 
worker_thread+0xda/0xe4
Aug 10 11:22:47 NitpickingHP2 kernel:  [80248022] 
autoremove_wake_function+0x0/0x2e
Aug 10 11:22:47 NitpickingHP2 kernel:  [80247f03] kthread+0x47/0x74
Aug 10 11:22:47

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

[Ron Johnson]

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 005a RIP: 
Aug 10 11:22:47 NitpickingHP2 kernel:  [c200013a4454]

[snip]

Aug 10 11:22:47 NitpickingHP2 kernel: CR2: 005a
Aug 10 11:22:47 NitpickingHP2 kernel: ---[ end trace 3f2c79fa6fe087ed ]---

After this event, the mouse will still move in X, but the keyboard is ignored
(including Ctrl-Alt-Backspace and Ctrl-Alt-F1). Program menus (e.g. Firefox)
still work, but GNOME's own menus don't. I have to power off to shut down.

System is an HP DV6100 series using a Turion 64.  Kernel version is
linux-image-2.6.24-1-amd64.  Modules are listed in the log above.

Any suggestions?  Maybe just upgrade to 2.6.25?


Presumably this is repeatable?

--
Ron Johnson, Jr.
Jefferson LA  USA

Scientists are people, too.  IOW, they also crave power, money,
respect, and influence, and they also fear for their jobs. Each
can be a healthy motivator, but each has the ability to turn a
good scientist into a bad one; and in some cases, they can turn
a good scientist into a charlatan.
http://thefutureofthings.com/book/3/the-bomb-that-never-was.html


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Carl Fink]

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 at blog.nitpicking.com.  Reviews!  Observations!
Stupid mistakes you can correct!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

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

[Ron Johnson]

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?  IOW, does it still happen if 5 simple 
static pages are loaded?


Do you open them all quickly, or does it still happen if you wait 
for one to finish before loading the next?


What if you load them in separate windows?

What if you put some other stress on ndiswrapper, like 5 large ftp GETs?

How old is this installation?

When did it start happening?

When did you last run $PACKAGE_MANAGER or upgrade the kernel?

--
Ron Johnson, Jr.
Jefferson LA  USA

Scientists are people, too.  IOW, they also crave power, money,
respect, and influence, and they also fear for their jobs. Each
can be a healthy motivator, but each has the ability to turn a
good scientist into a bad one; and in some cases, they can turn
a good scientist into a charlatan.
http://thefutureofthings.com/book/3/the-bomb-that-never-was.html


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Oops (was: System umstellen i386-AMD64)

[Arnd Münzebrock]

Sorry, wrong list.

Arnd


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Oops in Etch 40r3

[digbyt]

On Sun, Apr 13, 2008 at 05:55:36AM +0200, NN_il_Confusionario wrote:
 On Sat, Apr 12, 2008 at 11:23:48PM +, [EMAIL PROTECTED] wrote:
  [EMAIL PROTECTED]:~$ free -b
   total   used   free sharedbuffers cached
  Mem:1061478400  311463936  750014464  0  100552704  105132032
  -/+ buffers/cache:  105779200  955699200
  Swap:699138048  0  699138048
   . .Detected 1495.263 MHz processor.

 For my standards this is a very modern and powerful box.

 If memterst86 (or memtest from memtester package, if you cannot spare
 the box) and the check of logs does not show anything, I will
 _temporarilly_ try another kernel (a newer one from etch-and-half,
 backports and/or an older one from sarge; or even the suse kernel that
 was running fine before) to understand if a bug report agaisnt the
 current kernel in etch is needed


memtester is an interesting idea (since my next opportunity to shutdown
is about a week away). I assume that it won't really be able to rule out
the possibility of a memory problem as it can only test a sufficiently
small amount of free memory so as not to interfere with the running of
the system.
 
That gives rise to another question. I just repeated the free command
above to see how much memory can be spared, and see that my memory usage
has steadily climbed despite having no users on the system, and nothing
running other than the standard packages from a server install:
 
 total   used   free sharedbuffers cached
Mem:1061478400  860430336  201048064  0  374857728  164020224
-/+ buffers/cache:  321552384  739926016
Swap:699138048  0  699138048
 
Clearly about half of this increase (270M) is due to the buffer chache,
which is a reasonable use for spare memory capacity. Any idea how to
find out where the rest has gone? I'd rather not push the system into
excessive swapping if disk i/o is a potentially implicated in the
original crash.
 
Regards,
DigbyT
--
Digby R. S. Tarvin  digbyt(at)digbyt.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Oops in Etch 40r3 - again!

[digbyt]

On Sun, Apr 13, 2008 at 05:55:36AM +0200, NN_il_Confusionario wrote:
 On Sat, Apr 12, 2008 at 11:23:48PM +, [EMAIL PROTECTED] wrote:
  [EMAIL PROTECTED]:~$ free -b
   total   used   free sharedbuffers cached
  Mem:1061478400  311463936  750014464  0  100552704  105132032
  -/+ buffers/cache:  105779200  955699200
  Swap:699138048  0  699138048
   . .Detected 1495.263 MHz processor.

 For my standards this is a very modern and powerful box.

 If memterst86 (or memtest from memtester package, if you cannot spare
 the box) and the check of logs does not show anything, I will
 _temporarilly_ try another kernel (a newer one from etch-and-half,
 backports and/or an older one from sarge; or even the suse kernel that
 was running fine before) to understand if a bug report agaisnt the
 current kernel in etch is needed

Further to my previous, I gave it a try with 300M:

[EMAIL PROTECTED]:~$ sudo memtest 300M -l
memtest v. 2.93.1
(C) 2000 Charles Cazabon [EMAIL PROTECTED]
Original v.1 (C) 1999 Simon Kirby [EMAIL PROTECTED] [EMAIL PROTECTED]

Current limits:
  RLIMIT_RSS  0x
  RLIMIT_VMEM 0x
Raising limits...
Allocated 314572800 bytes...trying mlock...success.  Starting tests...

Testing 314568704 bytes at 0xa51da000 (4088 bytes lost to page alignment).

Run1:
  Test  1: Stuck Address:  Testing...Passed.
  Test  2:  Random value:  Setting...Testing...Passed.
  Test  3:XOR comparison:  Setting...Testing...Passed.
  Test  4:SUB comparison:  Setting...Testing...Passed.
  Test  5:MUL comparison:  Setting...Testing...Passed.
  Test  6:DIV comparison:  Setting...Testing...Passed.
  Test  7: OR comparison:  Setting...Testing...Passed.
  Test  8:AND comparison:  Setting...Testing...Passed.
  Test  9:  Sequential Increment:  Setting...Testing...Passed.
  Test 10:Solid Bits:  Testing...Passed.
  Test 11:  Block Sequential:  Testing...  15

free showed a reasonable amount of memory still in the buffer pool:
[EMAIL PROTECTED]:/var/log$ free -b
 total   used   free sharedbuffers cached
Mem:1061478400 1045397504   16080896  0  269635584  139096064
-/+ buffers/cache:  636665856  424812544
Swap:699138048  0  699138048

So I tried upping the memtest to 500M.

Received signal 2 (Interrupt)
munlock'ed memory.
0 runs completed.  0 errors detected.  Total runtime:  130 seconds.

Exiting...
[EMAIL PROTECTED]:~$ sudo memtest 500M -l
memtest v. 2.93.1
(C) 2000 Charles Cazabon [EMAIL PROTECTED]
Original v.1 (C) 1999 Simon Kirby [EMAIL PROTECTED] [EMAIL PROTECTED]

Current limits:
  RLIMIT_RSS  0x
  RLIMIT_VMEM 0x
Raising limits...
Allocated 524288000 bytes...trying mlock...
Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel: Oops: 0002 [#1]

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel: EIP is at _spin_lock+0x1/0xf

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel: eax: 0044   ebx:    ecx: 0001   edx: e7893d98

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel: esi: e7893d98   edi: 0025   ebp: 0025   esp: dfa67f00

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel: ds: 007b   es: 007b   ss: 0068

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel: Process kswapd0 (pid: 122, ti=dfa66000 task=dff98550 
task.ti=dfa66000)

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel: Stack: c015e27d e7893ca4  c016f31e 0080 e7893ea4 
e7887ab4 0001a004 

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel:dfffeac0 0088 00d0 c0148ca8 00680100  
00680100 00031357 

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel:0080   c02ccec0 c02ccec0 0003 
c0149053  

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel: Call Trace:

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel: Code: 05 90 ff 02 30 c9 89 c8 c3 89 c2 90 81 28 00 00 00 01 0f 94 
c0 84 c0 b9 01 00 00 00 75 09 90 81 02 00 00 00 01 30 c9 89 c8 c3 90 fe 08 79 
09 f3 90 80 38 00 7e f9 eb f2 c3 90 81 28 00 00 00 01 

Message from [EMAIL PROTECTED] at Sun Apr 13 15:38:38 2008 ...
tuko kernel: EIP: [c028091a] _spin_lock+0x1/0xf SS:ESP 0068:dfa67f00


Same error instantly... so I am guessing that a memory error would have
been detected more gracefully, and this is more likely to indicate something
going seriously wrong when kswapd becomes active...

It looks like the system is still running, but any attempt to access the
hard drive gets stuck in an uninteruptible sleep.

At least the problem seems to be easily reproduced...

Regards,
DigbyT


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject

Re: Oops in Etch 40r3

[NN_il_Confusionario]

On Sun, Apr 13, 2008 at 02:35:25PM +, [EMAIL PROTECTED] wrote:
 my memory usage
 has steadily climbed despite having no users on the system,

perhaps htop memstat sysatat or similar things can help

smartmontools hdparm (and badblocks, later) for the HD

Also, how much (kernel) memory is used by netfilter (activated by
iptables rules) to track connections? (it might be somewhere in /proc
but I do not remember)

-- 
Chi usa software non libero avvelena anche te. Digli di smettere.
Informatica=arsenico: minime dosi in rari casi patologici, altrimenti letale.
Informatica=bomba: intelligente solo per gli stupidi che ci credono.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Oops in Etch 40r3 - again!

[NN_il_Confusionario]

On Sun, Apr 13, 2008 at 02:51:10PM +, [EMAIL PROTECTED] wrote:
 It looks like the system is still running, but any attempt to access the
 hard drive gets stuck in an uninteruptible sleep.

you might consider the following sysctl settings (if you want to
automatically reboot the system):

  find /proc/ -iname \*panic\*
/proc/sys/vm/panic_on_oom
/proc/sys/kernel/panic_on_oops
/proc/sys/kernel/panic

-- 
Chi usa software non libero avvelena anche te. Digli di smettere.
Informatica=arsenico: minime dosi in rari casi patologici, altrimenti letale.
Informatica=bomba: intelligente solo per gli stupidi che ci credono.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]