Re: mkinitrd module detection

2004-12-06 Thread Ake
On Sun, Dec 05, 2004 at 12:55:14AM +0100, Erik van Konijnenburg wrote:
 This is a proposal to improve mkinitrd by reusing code from the hotplug
 project to determine which modules are needed on the initrd image to
 support block devices.

While in the process of rewriting mkinitrd, could a method of selecting
modules that should be excluded from the initrd.img be added.

-- 
Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden
Internet: [EMAIL PROTECTED] Phone: +46 90 7866134 Fax: +46 90 7866126
Mobile: +46 70 7716134 WWW: http://www.hpc2n.umu.se




Bug#284294: mkinitrd module detection

2004-12-06 Thread Erik van Konijnenburg
Following Harri's suggestion, I made a wishlist bug on initrd-tools
for this.  I'm forwarding your suggestion there; let's take this
off hotplug-devel.

Perhaps simply honouring the hotplug blacklists would be sufficient,
assuming a dependency from initrd-tools to hotplug is acceptable.

On Mon, Dec 06, 2004 at 08:02:20AM +0100, Ake wrote:
 On Sun, Dec 05, 2004 at 12:55:14AM +0100, Erik van Konijnenburg wrote:
  This is a proposal to improve mkinitrd by reusing code from the hotplug
  project to determine which modules are needed on the initrd image to
  support block devices.
 
 While in the process of rewriting mkinitrd, could a method of selecting
 modules that should be excluded from the initrd.img be added.
 
 -- 
 Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden
 Internet: [EMAIL PROTECTED]   Phone: +46 90 7866134 Fax: +46 90 7866126
 Mobile: +46 70 7716134 WWW: http://www.hpc2n.umu.se




Bug#284477: kernel-image-2.6.8-1-686: IBM ThinkCentre sometimes goes to extremely sluggish state

2004-12-06 Thread Tapio Lehtonen
Subject: kernel-image-2.6.8-1-686: IBM ThinkCentre sometimes goes to extremely 
sluggish state
Package: kernel-image-2.6.8-1-686
Version: 2.6.8-10
Severity: normal

*** Please type your report below this line ***

Sometimes IBM ThinkCentre MT-M 8183-35G goes to some strange state where
the whole computer is extremely slow. Any command takes about one minute
to execute, so the computer is so slow it is unusable. Only way to
recover seems to reboot, but even shutdown takes about 15 minutes.

I have tried setting acpi=off, and checked acpi was not available when
running so I did that correctly. It did not help, still the sluggishness
happened.

I have maintained this classroom of 13 machines since August, same
problem has been all the time. I have tried different kernel versions,
but it is hard to say if the problem has been better or worse, since it
seems completely random. No matter if a student is using the machine or
it is just idling, it may go to this sluggish state. In a two hour
session, about 2 machines go to this state and they have to be rebooted. 

More info available from http://people.debian.org/~tale/IBM/

The PNG image is from ssh session where I ran apt-get update and host
nttv37 claims it took 49710 days to fetch the files. Other hosts did
it in 4 seconds. So time runs wrong on nttv37, which happened to go to
this sluggish state.


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages kernel-image-2.6.8-1-686 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  initrd-tools  0.1.74 tools to create initrd image for p
ii  module-init-tools 3.1-rel-2  tools for managing Linux kernel mo

-- no debconf information




Bug#284484: After Update: kernel setup stack overlaps lilo second stage

2004-12-06 Thread Nölle, Christian
Package: kernel-image-2.6.8-i386 
Version: 2.6.8-10

Hi all!

I have a severe problem after an upgrade to the package mentioned
above. The update went fine, the package installed with apt, LILO
was updated and I did a reboot. After that, the system won't boot again,
saying: EBDA is big, kernel setup stack overlaps lilo second stage.

I booted into a rescue system and tried to run lilo again to see
the output. But LILO complained about missing sysmlinks to initrd, 
as mentioned here for older packages. Is this still an issue in 
2.6.8-10? Would it be the same workaround as for the older packages
(create a symlink to /boot/initrd[version]?)

Any help appreciated.

Thanks and take care!
--
 
Mit freundlichem Gruß

Christian Nölle

--
Christian Nöllemailto:[EMAIL PROTECTED]
 Tel : +49(202)4392451
CIP im Web:  http://www.wiwi.uni-wuppertal.de/cip/
  mailto:[EMAIL PROTECTED]
--




Processed: severity of 284356 is grave

2004-12-06 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.8.5
 severity 284356 grave
Bug#284356: incompatability with modules from -2 version of same package
Bug#284181: alsa-modules-2.4.27-1-686: plenty of unresolved symbols
Bug#284371: kernel-image-2.4.27-1-k7: broken i2c modules
Bug#284463: Alsa modules no longer load after minor kernel update
Severity set to `grave'.


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




Bug#284356: New release changed symbols thus rendering modules unloadable

2004-12-06 Thread Joey Hess
This bug is release critical. Please do not downgrade it. (But thanks for
reopening it.)

-- 
see shy jo


signature.asc
Description: Digital signature


Processed: severity of 284253 is grave, reassign 284253 to kernel-image-2.4.27-1-386, merging 284253 284356

2004-12-06 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.8.5
 severity 284253 grave
Bug#284253: debian-installer: [netboot-x86] there is a module versioning issue 
in 2.6 and 2.4 netboot images.
Severity set to `grave'.

 reassign 284253 kernel-image-2.4.27-1-386
Bug#284253: debian-installer: [netboot-x86] there is a module versioning issue 
in 2.6 and 2.4 netboot images.
Bug reassigned from package `debian-installer' to `kernel-image-2.4.27-1-386'.

 merge 284253 284356
Bug#284253: debian-installer: [netboot-x86] there is a module versioning issue 
in 2.6 and 2.4 netboot images.
Bug#284356: incompatability with modules from -2 version of same package
Mismatch - only Bugs in same state can be merged:
Values for `package' don't match:
 #284253 has `kernel-image-2.4.27-1-386';
 #284356 has `kernel-image-2.4.27-i386'


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




Processed: Re: [Pkg-alsa-devel] Bug#284485: failed loading alsa driver

2004-12-06 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 284356 grave
Bug#284356: incompatability with modules from -2 version of same package
Bug#284181: alsa-modules-2.4.27-1-686: plenty of unresolved symbols
Bug#284371: kernel-image-2.4.27-1-k7: broken i2c modules
Bug#284463: Alsa modules no longer load after minor kernel update
Severity set to `grave'.

 tags 284356 d-i
Bug#284356: incompatability with modules from -2 version of same package
Tags were: d-i
Bug#284181: alsa-modules-2.4.27-1-686: plenty of unresolved symbols
Bug#284371: kernel-image-2.4.27-1-k7: broken i2c modules
Bug#284463: Alsa modules no longer load after minor kernel update
Tags added: d-i

 reassign 284356 kernel-image-2.4.27-i386
Bug#284356: incompatability with modules from -2 version of same package
Bug#284181: alsa-modules-2.4.27-1-686: plenty of unresolved symbols
Bug#284371: kernel-image-2.4.27-1-k7: broken i2c modules
Bug#284463: Alsa modules no longer load after minor kernel update
Bug reassigned from package `kernel-image-2.4.27-i386' to 
`kernel-image-2.4.27-i386'.

 merge 284485 284356
Bug#284356: incompatability with modules from -2 version of same package
Bug#284485: failed loading alsa driver
Mismatch - only Bugs in same state can be merged:
Values for `package' don't match:
 #284356 has `kernel-image-2.4.27-i386';
 #284485 has `alsa-modules-2.4.27-1-k7'
Values for `severity' don't match:
 #284356 has `grave';
 #284485 has `important'

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




Processed: severity of 284230 is important, reassign 284230 to initrd-tools, merging 284230 278887

2004-12-06 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.8.5
 severity 284230 important
Bug#284230: megaraid2 issue
Severity set to `important'.

 reassign 284230 initrd-tools
Bug#284230: megaraid2 issue
Bug reassigned from package `debian-installer' to `initrd-tools'.

 merge 284230 278887
Bug#278887: does not include megaraid2 module on initrd, which makes booting 
fail after debian install on several Dell machines
Bug#284230: megaraid2 issue
Bug#282793: initial reboot fails with Dell PERC4i RAID Controller
Merged 278887 282793 284230.


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




Processed: merge

2004-12-06 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 284253 grave
Bug#284253: debian-installer: [netboot-x86] there is a module versioning issue 
in 2.6 and 2.4 netboot images.
Severity set to `grave'.

 reassign 284253 kernel-image-2.4.27-i386
Bug#284253: debian-installer: [netboot-x86] there is a module versioning issue 
in 2.6 and 2.4 netboot images.
Bug reassigned from package `kernel-image-2.4.27-1-386' to 
`kernel-image-2.4.27-i386'.

 merge 284253 284356
Bug#284253: debian-installer: [netboot-x86] there is a module versioning issue 
in 2.6 and 2.4 netboot images.
Bug#284356: incompatability with modules from -2 version of same package
Bug#284181: alsa-modules-2.4.27-1-686: plenty of unresolved symbols
Bug#284371: kernel-image-2.4.27-1-k7: broken i2c modules
Bug#284463: Alsa modules no longer load after minor kernel update
Bug#284485: failed loading alsa driver
Merged 284181 284253 284356 284371 284463 284485.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




Processed: reassign 284356 to kernel-image-2.4.27-1-386, merging 284356 284253

2004-12-06 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.8.5
 reassign 284356 kernel-image-2.4.27-1-386
Bug#284356: incompatability with modules from -2 version of same package
Bug#284181: alsa-modules-2.4.27-1-686: plenty of unresolved symbols
Bug#284253: debian-installer: [netboot-x86] there is a module versioning issue 
in 2.6 and 2.4 netboot images.
Bug#284371: kernel-image-2.4.27-1-k7: broken i2c modules
Bug#284463: Alsa modules no longer load after minor kernel update
Bug#284485: failed loading alsa driver
Bug reassigned from package `kernel-image-2.4.27-i386' to 
`kernel-image-2.4.27-1-386'.

 merge 284356 284253
Bug#284253: debian-installer: [netboot-x86] there is a module versioning issue 
in 2.6 and 2.4 netboot images.
Bug#284356: incompatability with modules from -2 version of same package
Bug#284181: alsa-modules-2.4.27-1-686: plenty of unresolved symbols
Bug#284371: kernel-image-2.4.27-1-k7: broken i2c modules
Bug#284463: Alsa modules no longer load after minor kernel update
Bug#284485: failed loading alsa driver
Merged 284181 284253 284356 284371 284463 284485.


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




Processing of kernel-patch-powerpc-2.6.9_2.6.9-2_powerpc.changes

2004-12-06 Thread Archive Administrator
kernel-patch-powerpc-2.6.9_2.6.9-2_powerpc.changes uploaded successfully to 
localhost
along with the files:
  kernel-patch-powerpc-2.6.9_2.6.9-2.dsc
  kernel-patch-powerpc-2.6.9_2.6.9-2.tar.gz
  kernel-patch-powerpc-2.6.9_2.6.9-2_all.deb
  kernel-headers-2.6.9_2.6.9-2_powerpc.deb
  kernel-image-power3_2.6.9-2_powerpc.deb
  kernel-image-2.6.9-power3_2.6.9-2_powerpc.deb
  kernel-build-2.6.9-power3_2.6.9-2_powerpc.deb
  kernel-image-power3-smp_2.6.9-2_powerpc.deb
  kernel-image-2.6.9-power3-smp_2.6.9-2_powerpc.deb
  kernel-build-2.6.9-power3-smp_2.6.9-2_powerpc.deb
  kernel-image-power4_2.6.9-2_powerpc.deb
  kernel-image-2.6.9-power4_2.6.9-2_powerpc.deb
  kernel-build-2.6.9-power4_2.6.9-2_powerpc.deb
  kernel-image-power4-smp_2.6.9-2_powerpc.deb
  kernel-image-2.6.9-power4-smp_2.6.9-2_powerpc.deb
  kernel-build-2.6.9-power4-smp_2.6.9-2_powerpc.deb
  kernel-image-powerpc_2.6.9-2_powerpc.deb
  kernel-image-2.6.9-powerpc_2.6.9-2_powerpc.deb
  kernel-build-2.6.9-powerpc_2.6.9-2_powerpc.deb
  kernel-image-powerpc-smp_2.6.9-2_powerpc.deb
  kernel-image-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb
  kernel-build-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb

Greetings,

Your Debian queue daemon




kernel-patch-powerpc-2.6.9_2.6.9-2_powerpc.changes ACCEPTED

2004-12-06 Thread Debian Installer

Accepted:
kernel-build-2.6.9-power3-smp_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-build-2.6.9-power3-smp_2.6.9-2_powerpc.deb
kernel-build-2.6.9-power3_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-build-2.6.9-power3_2.6.9-2_powerpc.deb
kernel-build-2.6.9-power4-smp_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-build-2.6.9-power4-smp_2.6.9-2_powerpc.deb
kernel-build-2.6.9-power4_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-build-2.6.9-power4_2.6.9-2_powerpc.deb
kernel-build-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-build-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb
kernel-build-2.6.9-powerpc_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-build-2.6.9-powerpc_2.6.9-2_powerpc.deb
kernel-headers-2.6.9_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-headers-2.6.9_2.6.9-2_powerpc.deb
kernel-image-2.6.9-power3-smp_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-2.6.9-power3-smp_2.6.9-2_powerpc.deb
kernel-image-2.6.9-power3_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-2.6.9-power3_2.6.9-2_powerpc.deb
kernel-image-2.6.9-power4-smp_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-2.6.9-power4-smp_2.6.9-2_powerpc.deb
kernel-image-2.6.9-power4_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-2.6.9-power4_2.6.9-2_powerpc.deb
kernel-image-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb
kernel-image-2.6.9-powerpc_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-2.6.9-powerpc_2.6.9-2_powerpc.deb
kernel-image-power3-smp_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-power3-smp_2.6.9-2_powerpc.deb
kernel-image-power3_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-power3_2.6.9-2_powerpc.deb
kernel-image-power4-smp_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-power4-smp_2.6.9-2_powerpc.deb
kernel-image-power4_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-power4_2.6.9-2_powerpc.deb
kernel-image-powerpc-smp_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-powerpc-smp_2.6.9-2_powerpc.deb
kernel-image-powerpc_2.6.9-2_powerpc.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-image-powerpc_2.6.9-2_powerpc.deb
kernel-patch-powerpc-2.6.9_2.6.9-2.dsc
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-patch-powerpc-2.6.9_2.6.9-2.dsc
kernel-patch-powerpc-2.6.9_2.6.9-2.tar.gz
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-patch-powerpc-2.6.9_2.6.9-2.tar.gz
kernel-patch-powerpc-2.6.9_2.6.9-2_all.deb
  to 
pool/main/k/kernel-patch-powerpc-2.6.9/kernel-patch-powerpc-2.6.9_2.6.9-2_all.deb
Announcing to debian-devel-changes@lists.debian.org


Thank you for your contribution to Debian.




Bug#284535: kernel / usb bug

2004-12-06 Thread Dave Bingham
Package: kernel
Version  : 2.6.8-1-386
(New install of sarge)

Connected a TwinMOS 7 in 1 card reader which was detected fine. It had a 64Mb 
CF card in the first slot.
I mounted it using mount -t vfat /dev/sda /mnt/twinmos_cf

Created a directory and then tried to copy a 22Mb file to it.
Looks like the cards u/s, but kernel BUG showed up twice.

dmesg showed the following:

scsi0 (0:0): rejecting I/O to offline device
cut *lots* of the same
scsi0 (0:0): rejecting I/O to offline device
printk: 36045 messages suppressed.
Buffer I/O error on device sda, logical block 24741
lost page write due to I/O error on sda
scsi0 (0:0): rejecting I/O to offline device
scsi0 (0:0): rejecting I/O to offline device
scsi0 (0:0): rejecting I/O to offline device
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed

scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 24741) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 24741) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 24741) failed
FAT: Directory bread(block 24741) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: bread(block 61) in fat_access failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 24741) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: unable to read inode block for updating (i_pos 3879)
scsi0 (0:0): rejecting I/O to offline device
printk: 75 messages suppressed.
Buffer I/O error on device sda, logical block 24742
lost page write due to I/O error on sda
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
Buffer I/O error on device sda, logical block 243
lost page write due to I/O error on sda
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 243) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 243) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 243) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 243) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 243) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: bread(block 61) in fat_access failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 242) failed
scsi0 (0:0): rejecting I/O to offline device
FAT: Directory bread(block 243) failed
scsi0 (0:0): rejecting I/O to offline device
Buffer I/O error on device sda, logical block 244
lost page write due to I/O error on sda
usb 1-2.1: USB disconnect, address 3
slab error in kmem_cache_destroy(): cache `scsi_cmd_cache': Can't free all 
objects
 [c0133cb2] kmem_cache_destroy+0x79/0xe0
 [caa82373] scsi_destroy_command_freelist+0x64/0x76 [scsi_mod]
 [caa83127] scsi_host_dev_release+0x59/0x72 [scsi_mod]
 [c01d2a55] device_release+0x14/0x44
 [c018ba98] kobject_cleanup+0x40/0x65
 [caa5f2e9] usb_stor_release_resources+0x98/0xc0 [usb_storage]
 [caa5f555] storage_disconnect+0x56/0x62 [usb_storage]
 [ca9b9077] usb_unbind_interface+0x31/0x5b [usbcore]
 [c01d3705] device_release_driver+0x40/0x4b
 [c01d38a7] bus_remove_device+0x39/0x68
 [c01d2cec] device_del+0x43/0x67
 [ca9be439] usb_disable_device+0x72/0xe4 [usbcore]
 [ca9baa4f] usb_disconnect+0x95/0x10c [usbcore]
 [ca9bb440] hub_port_connect_change+0x5e/0x313 [usbcore]
 [ca9bb919] hub_events+0x224/0x2da [usbcore]
 [ca9bb9cf] hub_thread+0x0/0xe4 [usbcore]
 [ca9bb9ec] hub_thread+0x1d/0xe4 [usbcore]
 [c0116fb4] autoremove_wake_function+0x0/0x3a
 [c0105e6e] ret_from_fork+0x6/0x14
 [ca9bb9cf] hub_thread+0x0/0xe4 [usbcore]
 [c0116fb4] autoremove_wake_function+0x0/0x3a
 [c01041e1] kernel_thread_helper+0x5/0xb
usb 1-2.1: new full speed USB device using address 4
kmem_cache_create: duplicate cache scsi_cmd_cache
[ cut here ]
kernel BUG at mm/slab.c:1382!
invalid operand:  [#1]
PREEMPT
Modules linked in: nls_iso8859_1 nls_cp437 vfat fat sd_mod usb_storage 
scsi_mod snd_pcm_oss snd_pcm snd_page_alloc snd_timer snd_mixer_oss snd 
soundcore ipv6 uhci_hcd usbcore pci_hotplug intel_agp pcspkr tsdev mousedev 
psmouse floppy parport_pc parport evdev 3c59x agpgart capability 

Bug#245398: Old bugzilla report

2004-12-06 Thread Christophe Combelles
Still bad news,
I have tried with the default kernel 2.6.9-1-k7 of Debian Experimental on 
both ends, and I still get the same bad bug.

Please note this has nothing to do with FD or HD, because I get the bug as 
well through my hub, as with a direct connexion.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245398
regards
Christophe
Alexander Nyberg a écrit :
Hi!
Have the problems indicated in
http://bugme.osdl.org/show_bug.cgi?id=2119
been solved by later kernels?
Thanks
Alexander