<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0">
  <channel>
    <title>DLFP - Entrées de forums de Syrion</title>
    <link>http://linuxfr.org/~Syrion/</link>
     
    <description>LinuxFr</description>
    <language>fr</language>
    <image>
      <title>DLFP - Entrées de forums de Syrion</title>
      <link>http://linuxfr.org/~Syrion/</link>
      <url>http://linuxfr.org/images/favicon.png</url>
    </image>
    <ttl>30</ttl>
    

    <item>
      <title>
	Écouter flux diffusé en multicast</title>
      <author>null@linuxfr.org (Syrion)</author>
      <pubDate>Mon, 29 Sep 2008 17:23:34 +0200</pubDate>
      <link>http://linuxfr.org/forums/31/25937.html</link>
      <guid>http://linuxfr.org/forums/31/25937.html</guid>
      <category>autre</category>
      <description>
	Bonjour,&lt;br /&gt;
&lt;br /&gt;
j'ai pulseaudio qui diffuse un flux en multicast :&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;$ sudo tcpdump -n net 224.0.0.0/8 -c 10&lt;br /&gt;
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode&lt;br /&gt;
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes&lt;br /&gt;
00:58:12.486334 IP 192.168.1.21.48338 &gt; 224.0.0.56.46056: UDP, length 1284&lt;br /&gt;
00:58:12.486343 IP 192.168.1.21.48338 &gt; 224.0.0.56.46056: UDP, length 1284&lt;br /&gt;
00:58:12.486547 IP 192.168.1.21.48338 &gt; 224.0.0.56.46056: UDP, length 1284&lt;br /&gt;
00:58:12.486554 IP 192.168.1.21.48338 &gt; 224.0.0.56.46056: UDP, length 1284&lt;br /&gt;
00:58:12.496220 IP 192.168.1.21.48338 &gt; 224.0.0.56.46056: UDP, length 1284&lt;br /&gt;
00:58:12.496231 IP 192.168.1.21.48338 &gt; 224.0.0.56.46056: UDP, length 1284&lt;br /&gt;
00:58:12.496834 IP 192.168.1.21.48338 &gt; 224.0.0.56.46056: UDP, length 1284&lt;br /&gt;
00:58:12.497027 IP 192.168.1.21.48338 &gt; 224.0.0.56.46056: UDP, length 1284&lt;br /&gt;
00:58:12.497053 IP 192.168.1.21.48338 &gt; 224.0.0.56.46056: UDP, length 1284&lt;br /&gt;
00:58:12.506566 IP 192.168.1.21.48338 &gt; 224.0.0.56.46056: UDP, length 1284&lt;br /&gt;
10 packets captured&lt;br /&gt;
13 packets received by filter&lt;br /&gt;
0 packets dropped by kernel&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
Or ni vlc ni des programmes que je fait ne lisent de données sur 224.0.0.56:46056&lt;br /&gt;
- VLC ne lit rien, et quand je force la fermeture il dit qu'il n'avait aucune données pour &quot;prefill buffer&quot;&lt;br /&gt;
- un simple programme Java qui s'inscrit au groupe  224.0.0.56 sur port 46056 bloque en lecture (en attente de données à lire). J'ai essayé un programme à moi et un sur le net qui est censé fonctionner&lt;br /&gt;
&lt;br /&gt;
Y a-t-il quelque chose qui m'a échappé ? Une config à activer ??</description>
    </item>
    <item>
      <title>
	cpufreq ne voit pas tous les throttling states</title>
      <author>null@linuxfr.org (Syrion)</author>
      <pubDate>Sun, 08 Jun 2008 22:05:25 +0200</pubDate>
      <link>http://linuxfr.org/forums/12/25308.html</link>
      <guid>http://linuxfr.org/forums/12/25308.html</guid>
      <category>general</category>
      <description>
	Bonjour,&lt;br /&gt;
J'ai un Core 2 Duo E8400 (3GHz) en governor OnDemand (noyau 2.6.24-18 de Ubuntu). La fréquence est bien modifiée en fonction de l'activité et des scaling_available_frequencies.&lt;br /&gt;
&lt;br /&gt;
Le problème : il y a bizarrement trop peu de fréquences disponibles.&lt;br /&gt;
dmesg signale bien 8 niveaux :&lt;br /&gt;
&lt;code&gt;[   28.230252] ACPI: Processor [CPU0] (supports 8 throttling states)&lt;br /&gt;
[   28.230417] ACPI: Processor [CPU1] (supports 8 throttling states)&lt;/code&gt;&lt;br /&gt;
8 niveaux confirmés par /proc/acpi/processor/CPU1/throttling et /proc/acpi/processor/CPU0/throttling, indiquant tous les 2 &lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
state count:             8&lt;br /&gt;
active state:            T0&lt;br /&gt;
state available: T0 to T7&lt;br /&gt;
states:&lt;br /&gt;
   *T0:                  100%&lt;br /&gt;
    T1:                  87%&lt;br /&gt;
    T2:                  75%&lt;br /&gt;
    T3:                  62%&lt;br /&gt;
    T4:                  50%&lt;br /&gt;
    T5:                  37%&lt;br /&gt;
    T6:                  25%&lt;br /&gt;
    T7:                  12%&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
Le throttling est à yes dans les 2 /proc/acpi/processor/CPUx/info&lt;br /&gt;
&lt;br /&gt;
1) Pourquoi alors les infos des dossiers /sys/devices/system/cpu/cpu1/cpufreq et /sys/devices/system/cpu/cpu0/cpufreq ne reportent que 2 fréquences dispos, le min et le max (2GHz et 3GHz respectivement, le min me semble énorme) ?&lt;br /&gt;
&lt;br /&gt;
2) Sachant que pour un bon vieux P4 à 2,8 GHZ j'ai de 300 et quelques à 2,8GHz en passant par une palanquée de fréquences intermédiaires, est-ce un support sur mon noyau ?&lt;br /&gt;
Le P4 utilise le module p4-clockmod et mon Core 2 Duo utilise acpi-cpufreq.&lt;br /&gt;
&lt;br /&gt;
3)Y a-t-il un meilleur module ?&lt;br /&gt;
&lt;br /&gt;
Merci de vos éclairages...</description>
    </item>
    <item>
      <title>
	usplash ubuntu qui cède la place au texte</title>
      <author>null@linuxfr.org (Syrion)</author>
      <pubDate>Thu, 29 May 2008 00:03:27 +0200</pubDate>
      <link>http://linuxfr.org/forums/10/25252.html</link>
      <guid>http://linuxfr.org/forums/10/25252.html</guid>
      <category>general</category>
      <description>
	Bonjour,&lt;br /&gt;
&lt;br /&gt;
je me suis récemment amusé à changer le usplash de mon Ubuntu 8.04 (Linux 2.6.24-17), et après quelque errances, ça marche royal.&lt;br /&gt;
&lt;br /&gt;
Cependant, chose qui se produisait déjà juste avant de changer le usplash, le usplash de démarrage apparaît, puis cède la place au mode texte au bout de quelques secondes.&lt;br /&gt;
&lt;br /&gt;
La doc d'ubuntu-fr sur ce genre de problème (&lt;a href=&quot;http://doc.ubuntu-fr.org/problemes_usplash#symptome_l_usplash_s_affiche_au_debut_puis_laisse_place_a_un_mode_texte&quot;&gt;problème usplash&lt;/a&gt;) indique 2-3 manips à faire dans le cas où on a redimensionné son swap. Comme c'était mon cas, j'ai fais les manips, mais sans succès : mon beau usplash se fait couper la parole par le mode texte ; comble : certains arrivent même à intégrer ce texte en petit sous le usplash.&lt;br /&gt;
&lt;br /&gt;
Est-ce que certains auraient une expérience du usplash ?</description>
    </item>
    <item>
      <title>
	Freeze dy system et swap tainted : ça recomence</title>
      <author>null@linuxfr.org (Syrion)</author>
      <pubDate>Tue, 20 May 2008 01:14:35 +0200</pubDate>
      <link>http://linuxfr.org/forums/36/25197.html</link>
      <guid>http://linuxfr.org/forums/36/25197.html</guid>
      <category>noyau</category>
      <description>
	Toujours en 2.6.24-16 sous Ubuntu 8.04, alors que repartitionner le swap et l'agrandir, j'ai à nouveau des freezes avec la suite de message suivant jusqu'à ce que ke reboote.&lt;br /&gt;
Aucune log dans les 30min pécédent l'incident, et la fin de cette log correspond au reboot:&lt;br /&gt;
&lt;code&gt;May 20 00:51:48 Syrion kernel: [16634.395463] irq 16: nobody cared (try booting with the &quot;irqpoll&quot; option)&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395468] Pid: 0, comm: swapper Tainted: P        2.6.24-16-generic #1&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395470] &lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395470] Call Trace:&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395472]    [__report_bad_irq+0x1e/0x80] __report_bad_irq+0x1e/0x80&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395490]  [note_interrupt+0x2ad/0x2e0] note_interrupt+0x2ad/0x2e0&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395495]  [handle_fasteoi_irq+0xa1/0x110] handle_fasteoi_irq+0xa1/0x110&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395498]  [do_IRQ+0x7b/0x100] do_IRQ+0x7b/0x100&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395500]  [mwait_idle+0x0/0x50] mwait_idle+0x0/0x50&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395502]  [default_idle+0x0/0x40] default_idle+0x0/0x40&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395504]  [ret_from_intr+0x0/0x0a] ret_from_intr+0x0/0xa&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395505]    [mwait_idle+0x42/0x50] mwait_idle+0x42/0x50&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395512]  [cpu_idle+0x6f/0xc0] cpu_idle+0x6f/0xc0&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395516]  [start_kernel+0x2b5/0x340] start_kernel+0x2b5/0x340&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395519]  [x86_64_start_kernel+0x12e/0x140] _sinittext+0x12e/0x140&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395522] &lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395523] handlers:&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395523] [usbcore:usb_hcd_irq+0x0/0x60] (usb_hcd_irq+0x0/0x60 [usbcore])&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395535] [ata_generic:ata_interrupt+0x0/0x240] (ata_interrupt+0x0/0x240 [libata])&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395546] [nvidia:nv_kern_isr+0x0/0xd0] (nv_kern_isr+0x0/0xd0 [nvidia])&lt;br /&gt;
May 20 00:51:48 Syrion kernel: [16634.395641] Disabling IRQ #16&lt;br /&gt;
May 20 00:52:00 Syrion kernel: [16646.549777] NVRM: Xid (0001:00): 8, Channel 00000003&lt;br /&gt;
May 20 00:52:01 Syrion kernel: [16647.552745] NVRM: Xid (0001:00): 16, Head 00000000 Count 00273373&lt;br /&gt;
May 20 00:52:08 Syrion kernel: [16654.545504] NVRM: Xid (0001:00): 8, Channel 0000001e&lt;br /&gt;
May 20 00:52:09 Syrion kernel: [16655.548457] NVRM: Xid (0001:00): 16, Head 00000000 Count 00273374&lt;br /&gt;
May 20 00:52:20 Syrion kernel: [16665.574097] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen&lt;br /&gt;
May 20 00:52:20 Syrion kernel: [16665.574104] ata9.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0&lt;br /&gt;
May 20 00:52:20 Syrion kernel: [16665.574104]          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00&lt;br /&gt;
May 20 00:52:20 Syrion kernel: [16665.574105]          res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)&lt;br /&gt;
May 20 00:52:20 Syrion kernel: [16665.574107] ata9.00: status: { DRDY }&lt;br /&gt;
May 20 00:52:20 Syrion kernel: [16665.574127] ata9: soft resetting link&lt;br /&gt;
May 20 00:52:20 Syrion kernel: [16666.230839] ata9.00: configured for UDMA/33&lt;br /&gt;
May 20 00:52:20 Syrion kernel: [16666.394451] ata9.01: configured for UDMA/66&lt;br /&gt;
May 20 00:52:20 Syrion kernel: [16666.394455] ata9: EH complete&lt;br /&gt;
May 20 00:52:29 Syrion kernel: [16675.527798] NVRM: Xid (0001:00): 8, Channel 00000000&lt;br /&gt;
May 20 00:52:32 Syrion kernel: [16678.528674] NVRM: Xid (0001:00): 16, Head 00000000 Count 002737c7&lt;br /&gt;
May 20 00:52:37 Syrion kernel: [16683.523508] NVRM: Xid (0001:00): 8, Channel 00000020&lt;br /&gt;
May 20 00:52:40 Syrion kernel: [16686.524396] NVRM: Xid (0001:00): 16, Head 00000000 Count 002737c8&lt;br /&gt;
May 20 00:52:50 Syrion kernel: [16696.362732] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen&lt;br /&gt;
May 20 00:52:50 Syrion kernel: [16696.362740] ata9.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0&lt;br /&gt;
May 20 00:52:50 Syrion kernel: [16696.362741]          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00&lt;br /&gt;
May 20 00:52:50 Syrion kernel: [16696.362742]          res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)&lt;br /&gt;
May 20 00:52:50 Syrion kernel: [16696.362744] ata9.00: status: { DRDY }&lt;br /&gt;
May 20 00:52:50 Syrion kernel: [16696.362766] ata9: soft resetting link&lt;br /&gt;
May 20 00:52:51 Syrion kernel: [16697.018975] ata9.00: configured for UDMA/33&lt;br /&gt;
May 20 00:52:51 Syrion kernel: [16697.182584] ata9.01: configured for UDMA/66&lt;br /&gt;
May 20 00:52:51 Syrion kernel: [16697.182590] ata9: EH complete&lt;br /&gt;
May 20 00:53:21 Syrion kernel: [16727.150863] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen&lt;br /&gt;
May 20 00:53:21 Syrion kernel: [16727.150871] ata9.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0&lt;br /&gt;
May 20 00:53:21 Syrion kernel: [16727.150872]          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00&lt;br /&gt;
May 20 00:53:21 Syrion kernel: [16727.150873]          res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)&lt;br /&gt;
May 20 00:53:21 Syrion kernel: [16727.150875] ata9.00: status: { DRDY }&lt;br /&gt;
May 20 00:53:21 Syrion kernel: [16727.150896] ata9: soft resetting link&lt;br /&gt;
May 20 00:53:22 Syrion kernel: [16727.807095] ata9.00: configured for UDMA/33&lt;br /&gt;
May 20 00:53:22 Syrion kernel: [16727.970730] ata9.01: configured for UDMA/66&lt;br /&gt;
May 20 00:53:22 Syrion kernel: [16727.970735] ata9: EH complete&lt;br /&gt;
May 20 00:53:52 Syrion kernel: [16757.938998] ata9.00: limiting speed to UDMA/25:PIO4&lt;br /&gt;
May 20 00:53:52 Syrion kernel: [16757.939002] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen&lt;br /&gt;
May 20 00:53:52 Syrion kernel: [16757.939008] ata9.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0&lt;br /&gt;
May 20 00:53:52 Syrion kernel: [16757.939009]          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00&lt;br /&gt;
May 20 00:53:52 Syrion kernel: [16757.939010]          res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)&lt;br /&gt;
May 20 00:53:52 Syrion kernel: [16757.939012] ata9.00: status: { DRDY }&lt;br /&gt;
May 20 00:53:52 Syrion kernel: [16757.939033] ata9: soft resetting link&lt;br /&gt;
May 20 00:53:53 Syrion kernel: [16758.595228] ata9.00: configured for UDMA/25&lt;br /&gt;
May 20 00:53:53 Syrion kernel: [16758.758863] ata9.01: configured for UDMA/66&lt;br /&gt;
May 20 00:53:53 Syrion kernel: [16758.758872] ata9: EH complete&lt;br /&gt;
May 20 00:54:23 Syrion kernel: [16788.727129] ata9.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen&lt;br /&gt;
May 20 00:54:23 Syrion kernel: [16788.727137] ata9.01: cmd a0/00:00:00:00:00/00:00:00:00:00/b0 tag 0&lt;br /&gt;
May 20 00:54:23 Syrion kernel: [16788.727138]          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00&lt;br /&gt;
May 20 00:54:23 Syrion kernel: [16788.727139]          res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)&lt;br /&gt;
May 20 00:54:23 Syrion kernel: [16788.727141] ata9.01: status: { DRDY }&lt;br /&gt;
May 20 00:54:23 Syrion kernel: [16788.727163] ata9: soft resetting link&lt;br /&gt;
May 20 00:54:23 Syrion kernel: [16789.383361] ata9.00: configured for UDMA/25&lt;br /&gt;
May 20 00:54:24 Syrion kernel: [16789.546996] ata9.01: configured for UDMA/66&lt;br /&gt;
May 20 00:54:24 Syrion kernel: [16789.547003] ata9: EH complete&lt;br /&gt;
May 20 00:54:54 Syrion kernel: [16819.515262] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen&lt;br /&gt;
May 20 00:54:54 Syrion kernel: [16819.515270] ata9.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0&lt;br /&gt;
May 20 00:54:54 Syrion kernel: [16819.515271]          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00&lt;br /&gt;
May 20 00:54:54 Syrion kernel: [16819.515272]          res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)&lt;br /&gt;
May 20 00:54:54 Syrion kernel: [16819.515274] ata9.00: status: { DRDY }&lt;br /&gt;
May 20 00:54:54 Syrion kernel: [16819.515295] ata9: soft resetting link&lt;br /&gt;
May 20 00:54:54 Syrion kernel: [16820.171504] ata9.00: configured for UDMA/25&lt;br /&gt;
May 20 00:54:54 Syrion kernel: [16820.335131] ata9.01: configured for UDMA/66&lt;br /&gt;
May 20 00:54:54 Syrion kernel: [16820.335136] ata9: EH complete&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
le résultat de &lt;code&gt;cat /proc/interrupts&lt;/code&gt; pour l'irq16  est :&lt;br /&gt;
&lt;code&gt;16:      30255      30051   IO-APIC-fasteoi   uhci_hcd:usb1, libata, nvidia&lt;/code&gt;</description>
    </item>
    <item>
      <title>
	Freeze dy system et swap tainted</title>
      <author>null@linuxfr.org (Syrion)</author>
      <pubDate>Thu, 15 May 2008 01:04:00 +0200</pubDate>
      <link>http://linuxfr.org/forums/36/25168.html</link>
      <guid>http://linuxfr.org/forums/36/25168.html</guid>
      <category>noyau</category>
      <description>
	Bonjour,&lt;br /&gt;
&lt;br /&gt;
Voici ma log système au moment où mon Ubuntu 8.04 (Linux 2.6.24-16) freeze, ne laissant bouger que la souris :&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;May 15 00:42:57 Syrion kernel: [15972.317443] irq 16: nobody cared (try booting with the &quot;irqpoll&quot; option)&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317449] Pid: 0, comm: swapper Tainted: P        2.6.24-16-generic #1&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317450] &lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317451] Call Trace:&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317452]    [__report_bad_irq+0x1e/0x80] __report_bad_irq+0x1e/0x80&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317472]  [note_interrupt+0x2ad/0x2e0] note_interrupt+0x2ad/0x2e0&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317476]  [handle_fasteoi_irq+0xa1/0x110] handle_fasteoi_irq+0xa1/0x110&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317480]  [do_IRQ+0x7b/0x100] do_IRQ+0x7b/0x100&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317481]  [mwait_idle+0x0/0x50] mwait_idle+0x0/0x50&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317483]  [default_idle+0x0/0x40] default_idle+0x0/0x40&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317485]  [ret_from_intr+0x0/0x0a] ret_from_intr+0x0/0xa&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317486]    [mwait_idle+0x42/0x50] mwait_idle+0x42/0x50&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317493]  [cpu_idle+0x6f/0xc0] cpu_idle+0x6f/0xc0&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317496]  [start_kernel+0x2b5/0x340] start_kernel+0x2b5/0x340&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317499]  [x86_64_start_kernel+0x12e/0x140] _sinittext+0x12e/0x140&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317502] &lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317503] handlers:&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317504] [usbcore:usb_hcd_irq+0x0/0x60] (usb_hcd_irq+0x0/0x60 [usbcore])&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317516] [ata_generic:ata_interrupt+0x0/0x240] (ata_interrupt+0x0/0x240 [libata])&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317526] [nvidia:nv_kern_isr+0x0/0xd0] (nv_kern_isr+0x0/0xd0 [nvidia])&lt;br /&gt;
May 15 00:42:57 Syrion kernel: [15972.317623] Disabling IRQ #16&lt;br /&gt;
May 15 00:43:05 Syrion kernel: [15980.756503] NVRM: Xid (0001:00): 16, Head 00000000 Count 00292ad5&lt;br /&gt;
May 15 00:43:07 Syrion kernel: [15982.754441] NVRM: Xid (0001:00): 8, Channel 00000002&lt;br /&gt;
May 15 00:43:13 Syrion kernel: [15988.752220] NVRM: Xid (0001:00): 16, Head 00000000 Count 00292ad6&lt;br /&gt;
May 15 00:43:15 Syrion kernel: [15990.750154] NVRM: Xid (0001:00): 8, Channel 0000001e&lt;br /&gt;
May 15 00:43:21 Syrion kernel: [15996.747938] NVRM: Xid (0001:00): 16, Head 00000000 Count 00292ad7&lt;br /&gt;
May 15 00:43:23 Syrion kernel: [15998.745871] NVRM: Xid (0001:00): 8, Channel 00000020&lt;br /&gt;
May 15 00:43:28 Syrion kernel: [16003.161310] ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen&lt;br /&gt;
May 15 00:43:28 Syrion kernel: [16003.161317] ata3.01: cmd a0/00:00:00:00:00/00:00:00:00:00/b0 tag 0&lt;br /&gt;
May 15 00:43:28 Syrion kernel: [16003.161318]          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00&lt;br /&gt;
May 15 00:43:28 Syrion kernel: [16003.161319]          res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)&lt;br /&gt;
May 15 00:43:28 Syrion kernel: [16003.161322] ata3.01: status: { DRDY }&lt;br /&gt;
May 15 00:43:28 Syrion kernel: [16003.161338] ata3: soft resetting link&lt;br /&gt;
May 15 00:43:28 Syrion kernel: [16003.817368] ata3.00: configured for UDMA/33&lt;br /&gt;
May 15 00:43:28 Syrion kernel: [16003.989170] ata3.01: configured for UDMA/66&lt;br /&gt;
May 15 00:43:28 Syrion kernel: [16003.989180] ata3: EH complete&lt;br /&gt;
May 15 00:43:33 Syrion kernel: [16008.739520] NVRM: Xid (0001:00): 16, Head 00000000 Count 00292ad8&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
Ceci semble arriver lors de la première écriture dans le swap, qui est actif sur une partition.&lt;br /&gt;
Ceci est-il purement matériel ou un bug du noyau ?</description>
    </item>
    <item>
      <title>
	Update driver du noyau pour disque dur ??</title>
      <author>null@linuxfr.org (Syrion)</author>
      <pubDate>Tue, 13 May 2008 23:43:08 +0200</pubDate>
      <link>http://linuxfr.org/forums/36/25155.html</link>
      <guid>http://linuxfr.org/forums/36/25155.html</guid>
      <category>noyau</category>
      <description>
	Bonjour,&lt;br /&gt;
suite à des pbs de freeze au moment de la création de la première entrée dans le swap (swap tainted dans les logs), je regarde mon BIOS, et je vois que les disques SATA sont en legcay IDE au lieu de native IDE. Je corrige ça, je reboote... voici un extrait des logs de reboot :&lt;br /&gt;
&lt;code&gt;&lt;br /&gt;
May 13 22:59:09 Syrion kernel: [   33.056935] ata7: SATA link down (SStatus 0 SControl 300)&lt;br /&gt;
May 13 22:59:09 Syrion kernel: [   33.376602] ata8: SATA link down (SStatus 0 SControl 300)&lt;br /&gt;
May 13 22:59:09 Syrion kernel: [   33.379501] Driver 'sd' needs updating - please use bus_type methods&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
Alors question : qu'est-ce que ça signifie et comment corriger ce &quot;Driver 'sd' need updating&quot; ?</description>
    </item>
    <item>
      <title>Comportement étrange de /bin/more</title>
      <author>null@linuxfr.org (Syrion)</author>
      <pubDate>Wed, 22 Aug 2007 22:05:55 +0200</pubDate>
      <link>http://linuxfr.org/forums/26/22888.html</link>
      <guid>http://linuxfr.org/forums/26/22888.html</guid>
      <category>shell</category>
      <description>Voilà, je me demandais pourquoi /bin/more, intégré dans un script bash, se comportait différemment lorsque ledit script est lancé depuis un lanceur/menu du bureau (en l'occurence Gnome) oubien dans un terminal.&lt;br /&gt;
&lt;br /&gt;
Dans un terminal (dont le shell est bash), /bin/more m'affiche bien le contenu du fichier passé en argument.&lt;br /&gt;
Depuis un raccourci, il rajoute en première ligne &quot;::::::::::: /chemin/du/fichier :::::::::::&quot;.&lt;br /&gt;
&lt;br /&gt;
C'est d'autant plus embêtant que ça ne le faisait pas avant !&lt;br /&gt;
Avant quoi ? récemment je suis passé de kdm à gdm, mais que dire d'autre.... je ne vois pas le rapport...&lt;br /&gt;
&lt;br /&gt;
Quelqu'un aurait une explication ?</description>
    </item>  </channel>
</rss>
