usb 1-1: USB disconnect, address 2
usb 1-1: new full speed USB device using address 3

$ cd /tmp
$ wget http://files.xvid.org/downloads/xvidcore-1.0.0-rc4.tar.bz2
$ tar xvjf xvidcore-1.0.0-rc4.tar.bz2
$ cd xvidcore-1.0.0-rc4
$ dpkg-buildpackage -rfakeroot
$ cd ..
$ su
# dpkg -i libxvidcore4_1.0-0cvs_i386.deb
# dpkg -i libxvidcore4-dev_1.0-0cvs_i386.deb

<style TYPE="text/css">
<!--

div#esim-040513-1 {
  white-space: pre-wrap;
  color: white;
}

-->
<div id="esim-040513-1">
foo bar foo bar foo bar foo
tähän asti sisentämätöntä tekstiä
   tämä rivi on sisennetty kolmella välillä
tämä rivi on taas sisentämätön
</div>

Setting up python2.3 (2.3.3-7) ...
Compiling python modules in /usr/lib/python2.3 ...
Compiling optimized python modules in /usr/lib/python2.3 ...
/var/lib/dpkg/info/python2.3.postinst: line 49: 3554 Muistialueen ylitys \
/usr/bin/python2.3 -O /usr/lib/python2.3/compileall.py -q $i
dpkg: error processing python2.3 (--configure):
subprocess post-installation script returned error exit status 139

jani@sargeX:~$ free
total used free shared buffers cached
Mem: 515644 509200 6444 0 15012 157536
-/+ buffers/cache: 336652 178992
Swap: 1991976 0 1991976

invalid operand: 0000 [#1]
PREEMPT
CPU: 0
EIP: 0060:[] Not tainted
EFLAGS: 00013202 (2.6.5)
EIP is at radeon_cp_idle+0x49/0xa0 [radeon]
eax: dc8ca440 ebx: dec5e800 ecx: e0c34179 edx: e0c43a70
esi: dfeca740 edi: 00000044 ebp: dd2fd080 esp: dd30df68
ds: 007b es: 007b ss: 0068
Process XFree86 (pid: 2163, threadinfo=dd30c000 task=dd3353e0)
Stack: e0c2e81d dc8ca440 dd2fd080 00006444 00000000 00000001 00001000 c7bed0e0
dd2fd080 00006444 ffffffe7 dd30c000 c01676cf dc8ca440 dd2fd080 00006444
00000000 00001000 c7bed0e0 00000006 0862ed18 08651bc8 c0109377 00000006
Call Trace:
[] radeon_ioctl+0xcd/0x150 [radeon]
[] sys_ioctl+0xef/0x2a0
[] syscall_call+0x7/0xb

Code: c5 c3 e0 c7 04 24 60 df c3 e0 e8 88 d3 4e df 8b 7c 24 14 8b

sargeX:/home/jani# apt-get --purge remove gtkam gphoto2
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages will be REMOVED:
gphoto2* gtkam*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 1163kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 110872 files and directories currently installed.)
Removing gtkam ...
Purging configuration files for gtkam ...
Removing gphoto2 ...
sargeX:/home/jani#

sargeX:/home/jani# dpkg -i opera_7.50-20040422.5-shared-qt_en_i386.deb
Selecting previously deselected package opera.
(Reading database ... 110655 files and directories currently installed.)
Unpacking opera (from opera_7.50-20040422.5-shared-qt_en_i386.deb) ...
Setting up opera (7.50-20040422.5) ...
sargeX:/home/jani#

sargeX:/home/jani# sed -n 28,60p /var/log/syslog
May 11 09:54:00 sargeX syslogd 1.4.1#10: restart.
May 11 09:54:00 sargeX kernel: klogd 1.4.1#10, log source = /proc/kmsg started.
May 11 09:54:00 sargeX kernel: Inspecting /boot/System.map-2.6.5
May 11 09:54:00 sargeX kernel: Loaded 23255 symbols from /boot/System.map-2.6.5.
May 11 09:54:00 sargeX kernel: Symbols match kernel version 2.6.5.
May 11 09:54:00 sargeX kernel: No module symbols loaded - kernel modules not enabled.
May 11 09:54:00 sargeX kernel: 8259A ... failed.
May 11 09:54:00 sargeX kernel: ...trying to set up timer as Virtual Wire IRQ... failed.
May 11 09:54:00 sargeX kernel: ...trying to set up timer as ExtINT IRQ... works.
May 11 09:54:00 sargeX kernel: Using local APIC timer interrupts.
May 11 09:54:00 sargeX kernel: calibrating APIC timer ...
May 11 09:54:00 sargeX kernel: ..... CPU clock speed is 1912.0941 MHz.
May 11 09:54:00 sargeX kernel: ..... host bus clock speed is 332.0685 MHz.
May 11 09:54:00 sargeX kernel: NET: Registered protocol family 16
May 11 09:54:00 sargeX kernel: EISA bus registered
May 11 09:54:00 sargeX kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb790, last bus=3
May 11 09:54:00 sargeX kernel: PCI: Using configuration type 1
May 11 09:54:00 sargeX kernel: mtrr: v2.0 (20020519)
May 11 09:54:00 sargeX kernel: ACPI: Subsystem revision 20040326
May 11 09:54:00 sargeX kernel: ACPI: Interpreter enabled
May 11 09:54:00 sargeX kernel: ACPI: Using IOAPIC for interrupt routing
May 11 09:54:00 sargeX kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
May 11 09:54:00 sargeX kernel: PCI: Probing PCI hardware (bus 00)
May 11 09:54:00 sargeX kernel: PCI: nForce2 C1 Halt Disconnect fixup
May 11 09:54:00 sargeX kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
May 11 09:54:00 sargeX kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
May 11 09:54:00 sargeX kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
May 11 09:54:00 sargeX kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 12 14 15)

sed -n 36024,36191p patch-2.6.6

diff -Nru a/arch/i386/pci/fixup.c b/arch/i386/pci/fixup.c
--- a/arch/i386/pci/fixup.c	Sun May  9 19:33:46 2004
+++ b/arch/i386/pci/fixup.c	Sun May  9 19:33:46 2004
@@ -187,6 +187,42 @@
 		dev->transparent = 1;
 }
 
+/*
+ * Fixup for C1 Halt Disconnect problem on nForce2 systems.
+ *
+ * From information provided by "Allen Martin" :
+ *
+ * A hang is caused when the CPU generates a very fast CONNECT/HALT cycle
+ * sequence.  Workaround is to set the SYSTEM_IDLE_TIMEOUT to 80 ns.
+ * This allows the state-machine and timer to return to a proper state within
+ * 80 ns of the CONNECT and probe appearing together.  Since the CPU will not
+ * issue another HALT within 80 ns of the initial HALT, the failure condition
+ * is avoided.
+ */
+static void __init pci_fixup_nforce2(struct pci_dev *dev)
+{
+	u32 val, fixed_val;
+	u8 rev;
+
+	pci_read_config_byte(dev, PCI_REVISION_ID, &rev);
+
+	/*
+	 * Chip  Old value   New value
+	 * C17   0x1F0FFF01  0x1F01FF01
+	 * C18D  0x9F0FFF01  0x9F01FF01
+	 *
+	 * Northbridge chip version may be determined by
+	 * reading the PCI revision ID (0xC1 or greater is C18D).
+	 */
+	fixed_val = rev < 0xC1 ? 0x1F01FF01 : 0x9F01FF01;
+
+	pci_read_config_dword(dev, 0x6c, &val);
+	if (val != fixed_val) {
+		printk(KERN_WARNING "PCI: nForce2 C1 Halt Disconnect fixup\n");
+		pci_write_config_dword(dev, 0x6c, fixed_val);
+	}
+}
+
 struct pci_fixup pcibios_fixups[] = {
 	{
 		.pass		= PCI_FIXUP_HEADER,
@@ -289,6 +325,12 @@
 		.vendor		= PCI_VENDOR_ID_INTEL,
 		.device		= PCI_ANY_ID,
 		.hook		= pci_fixup_transparent_bridge
+	},
+	{
+		.pass		= PCI_FIXUP_HEADER,
+		.vendor		= PCI_VENDOR_ID_NVIDIA,
+		.device		= PCI_DEVICE_ID_NVIDIA_NFORCE2,
+		.hook		= pci_fixup_nforce2
 	},
 	{ .pass = 0 }
 };

jani@sargeX:~$ while [ 0 ] ; do ping -c 3 lkml.org && play /mnt/media2/audio/sounds/human/femeek2.wav -v 0.3 ; done
PING lkml.org (212.79.244.34): 56 data bytes

<B.Zolnierkiewicz@elka.pw.edu.pl>
	[PATCH] fixup for C1 Halt Disconnect problem on nForce2 chipsets
	
	Based on information provided by "Allen Martin" :
	
	A hang is caused when the CPU generates a very fast CONNECT/HALT cycle
	sequence.  Workaround is to set the SYSTEM_IDLE_TIMEOUT to 80 ns.
	This allows the state-machine and timer to return to a proper state within
	80 ns of the CONNECT and probe appearing together.  Since the CPU will not
	issue another HALT within 80 ns of the initial HALT, the failure condition
	is avoided.

sargeX:/dev# ls -l cdrom*
lrwxr-xr-x 1 root cdrom 11 2004-03-22 10:20 cdrom -> /dev/cdrom0
lrwxr-xr-x 1 root cdrom 10 2004-05-10 17:46 cdrom0 -> cdrom0.ide
lrwxr-xr-x 1 root cdrom 3 2004-05-10 17:45 cdrom0.ide -> hdc
lrwxr-xr-x 1 root cdrom 9 2004-03-22 10:20 cdrom0.scsi -> /dev/scd0

/dev/sda1    /mnt/Sony    vfat    user,gid=1001     0