Bug#390541: .17-.19-rc1 fails to detect PIONEER DVD-RW DVR-K15, .16 works fine
On Tuesday 10 October 2006 09:31, Jens Axboe wrote: On Tue, Oct 10 2006, Oleg Verych wrote: Jens, please, help to sort out this one. 2.6.19-rc1 was tested with no luck. Bug's thread with more logs is here: http://permalink.gmane.org/gmane.linux.debian.devel.kernel/22903 As nobody seems to have a clue about this so far, I'd suggest you start git bisecting with 2.6.16 as the good kernel and 2.6.17 as the bad kernel to try and narrow the breakage point down a bit. I was about to give this a try, starting with 2.6.17-rc1. Unfortunately, I'm already running into trouble because 2.6.17-rc1 doesn't compile cleanly with Debian's .config neither from 2.6.16 nor 2.6.17. The error I'm getting is: [...] CC security/selinux/xfrm.o security/selinux/xfrm.c: In function 'selinux_socket_getpeer_dgram': security/selinux/xfrm.c:284: error: 'struct sec_path' has no member named 'x' security/selinux/xfrm.c: In function 'selinux_xfrm_sock_rcv_skb': security/selinux/xfrm.c:317: error: 'struct sec_path' has no member named 'x' make[2]: *** [security/selinux/xfrm.o] Error 1 make[1]: *** [security/selinux] Error 2 make: *** [security] Error 2 Am I right in assuming that the correct way to work around this is to disable the related config options? Is this part of the normal git bisecting procedure or should I be using different .config files alltogether? If you could point me to the correct source files of the driver (maybe in drivers/ide/), I wouldn't mind trying a less brute-force approach. Thanks! Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390541: linux-image-2.6.17-2-686: 2.6.17 fails to detect PIONEER DVD-RW DVR-K15, works fine with 2.6.16
Hi Oleg Sorry for taking so long to reply. On Thursday 05 October 2006 06:55, you wrote: On Tue, Oct 03, 2006 at 04:30:13PM +0200, Georg Wittenburg wrote: On Tuesday 03 October 2006 16:24, you wrote: On 2006-10-02, Georg Wittenburg [EMAIL PROTECTED] wrote: [.] Please don't be so selfish ;), attach full bootlog (dmesg + mount output). Here i see hdb, that means device node for your drive set up. What's problem, is not clear. [.] No problem. ;) Please find attached to complete dmesg output of 2.6.16, 2.6.17 and 2.6.18. 2.6.16 works as expected, 2.6.17 and 2.6.18 fail to detect the DVD drive. OK, but before will go further with this, can you give 2.6.19-rc1 a try ? 2.6.18 had very long cycle, maybe that was fixed already. I tried 2.6.19-rc1 with Debian's /boot/config-2.6.18-1-686 and default values for all new options. Unfortunately, even 2.6.19-rc1 fails to detect the DVD drive. I'm attaching the dmesg output to this mail. Linux version 2.6.17-2-686 (Debian 2.6.17-9) ([EMAIL PROTECTED]) (gcc version 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)) #1 SMP Wed Sep 13 16:34:10 UTC 2006 [.] ACPI: PM-Timer IO Port: 0x1008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] *enabled*) Processor #0 6:13 APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] *disabled*) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) BTW, do you have a Core Duo ? If yes, do they both run ? No, this is a plain Pentium M. [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : Intel(R) Pentium(R) M processor 1.86GHz stepping: 8 cpu MHz : 800.000 cache size : 2048 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx est tm2 bogomips: 1599.97 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] *enabled*) Processor #0 6:13 APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] *disabled*) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) I'm unsure whether this helps, but I've observed for all of 2.6.17, 2.6.18, and 2.6.19-rc1 that there is a delay lasting several seconds during boot after the line hda: TOSHIBA MK1031GAS, ATA DISK drive. This delay doesn't happen when booting 2.6.16. Maybe a timeout during the detecting of hdb? Again, thanks for looking into this, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ Linux version 2.6.19-rc1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)) #1 SMP Sun Oct 8 16:19:23 CEST 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009f800 (usable) BIOS-e820: 0009f800 - 000a (reserved) BIOS-e820: 000dc000 - 0010 (reserved) BIOS-e820: 0010 - 3fee (usable) BIOS-e820: 3fee - 3feea000 (ACPI data) BIOS-e820: 3feea000 - 3ff0 (ACPI NVS) BIOS-e820: 3ff0 - 4000 (reserved) BIOS-e820: e000 - f0006000 (reserved) BIOS-e820: f0008000 - f000c000 (reserved) BIOS-e820: fed2 - fed9 (reserved) BIOS-e820: ff00 - 0001 (reserved) 126MB HIGHMEM available. 896MB LOWMEM available. Entering add_active_range(0, 0, 261856) 0 entries of 256 used Zone PFN ranges: DMA 0 - 4096 Normal 4096 - 229376 HighMem229376 - 261856 early_node_map[1] active PFN ranges 0:0 - 261856 On node 0 totalpages: 261856 DMA zone: 32 pages used for memmap DMA zone: 0 pages reserved DMA zone: 4064 pages, LIFO batch:0 Normal zone: 1760 pages used for memmap Normal zone: 223520 pages, LIFO batch:31 HighMem zone: 253 pages used for memmap HighMem zone: 32227 pages, LIFO batch:7 DMI present. ACPI: RSDP (v000 PTLTD ) @ 0x000f7520 ACPI: RSDT (v001 Sony J1 0x20060605 PTL 0x) @ 0x3fee5890 ACPI: MADT (v001 Sony J1 0x20060605 PTL 0x005f) @ 0x3fee9e78 ACPI: FADT (v002 Sony J1 0x20060605 PTL 0x005f) @ 0x3fee9ee0 ACPI: BOOT (v001 Sony J1 0x20060605 PTL 0x0001) @ 0x3fee9fd8 ACPI: MCFG (v001 Sony J1 0x20060605 PTL 0x005f) @ 0x3fee9f9c ACPI: SSDT (v001 Sony J1 0x20060605 PTL 0x20030224) @ 0x3fee614d ACPI: SSDT (v001 Sony J1 0x20060605 PTL 0x20030224) @ 0x3fee5d08 ACPI: SSDT (v001 Sony J1 0x20060605 PTL 0x20030224) @ 0x3fee5aed ACPI: SSDT (v001 Sony J1 0x20060605 PTL 0x20030224) @ 0x3fee58d4 ACPI: DSDT (v001 Sony
Bug#390541: linux-image-2.6.17-2-686: 2.6.17 fails to detect PIONEER DVD-RW DVR-K15, works fine with 2.6.16
Hi Oleg! On Sunday 01 October 2006 23:36, you wrote: On 2006-10-01, Georg Wittenburg [EMAIL PROTECTED] wrote: Package: linux-image-2.6.17-2-686 Version: 2.6.17-9 Severity: normal [-0-] Kernel 2.6.17 (from linux-image-2.6.17-2-686) fails to detect the build-in PIONEER DVD-RW DVR-K15 drive of my Sony VAIO FS295XP laptop. This worked fine with 2.6.16 (from linux-image-2.6.16-2-686) and previous kernels. Related output from dmesg looks as follows: [EMAIL PROTECTED]:~$ egrep ide.?:|hdb dmesg-2.6.1* dmesg-2.6.16:ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx dmesg-2.6.16:ide0: BM-DMA at 0x1880-0x1887, BIOS settings: hda:DMA, hdb:DMA dmesg-2.6.16:hdb: PIONEER DVD-RW DVR-K15, ATAPI CD/DVD-ROM drive dmesg-2.6.16:hdb: ATAPI 31X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(33) dmesg-2.6.17:ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx dmesg-2.6.17:ide0: BM-DMA at 0x1880-0x1887, BIOS settings: hda:DMA, hdb:DMA There isn't much output, but maybe it was fixed in 2.6.18. Try that please. Doesn't seem like it was fixed in 2.6.18 (from linux-image-2.6.18-1-686), unfortunately. [EMAIL PROTECTED]:~$ egrep ide.?:|hdb dmesg-2.6.18 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ide0: BM-DMA at 0x1880-0x1887, BIOS settings: hda:DMA, hdb:DMA This maybe related: git commit: a4f5749ba6e3f23ae4a137cee10324830db4d081, libata patch Thanks for your time. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ pgpvNKwXNvtkb.pgp Description: PGP signature
Bug#281912: udev: Fails to re-created FireWire CDROM device node after reconnecting: Still Present in 2.6.10
Hi David! On Monday 02 January 2006 21:24, David Schmitt wrote: Dear Georg! Could you please retest with a current kernel (testing:2.6.12, unstable:2.6.14) and a current udev (= 0.076). Using initramfs-tools for creating the initrd is probably a good idea too. Unfortunately, I don't have the hardware available for testing anymore and thus can't tell whether the bug still exists in current kernels. I'm sorry. Nevertheless, thank you very much for spending time on this issue. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ pgpT1OhhP5tPI.pgp Description: PGP signature
Bug#304775: kernel-source-2.6.11: OOM but swap is unused
Nevermind, I just noticed that I had /proc/sys/vm/swappiness set to 0 which apparently was OK in 2.6.10, but triggers the OOM killer in 2.6.11. Leaving the swappiness value at the default 60 gives you a perfectly usable system. Please close this bug. Sorry for the trouble, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ pgp6BatScOjhP.pgp Description: PGP signature
Bug#304775: kernel-source-2.6.11: OOM but swap is unused
Package: kernel-source-2.6.11 Version: 2.6.11-3 Severity: important Hi! Under normal desktop usage (KDE with Konqueror, Kontact and amaroK running) the OOM killer kicks in reproducably and kills the klauncher and kwin processes. This occurs with both kernel-image-2.6.11-1-686 and the kernel that I compiled myself to add MPPE support. However, free swap space IS available. /var/log/syslog as follows: Apr 15 14:06:22 vaio kernel: oom-killer: gfp_mask=0x80d2 Apr 15 14:06:23 vaio kernel: DMA per-cpu: Apr 15 14:06:23 vaio kernel: cpu 0 hot: low 2, high 6, batch 1 Apr 15 14:06:23 vaio kernel: cpu 0 cold: low 0, high 2, batch 1 Apr 15 14:06:23 vaio kernel: Normal per-cpu: Apr 15 14:06:23 vaio kernel: cpu 0 hot: low 28, high 84, batch 14 Apr 15 14:06:23 vaio kernel: cpu 0 cold: low 0, high 28, batch 14 Apr 15 14:06:23 vaio kernel: HighMem per-cpu: empty Apr 15 14:06:23 vaio kernel: Apr 15 14:06:23 vaio kernel: Free pages:3592kB (0kB HighMem) Apr 15 14:06:23 vaio kernel: Active:47818 inactive:1669 dirty:0 writeback:14 unstable:0 free:898 slab:3388 mapped:49377 pagetables:777 Apr 15 14:06:23 vaio kernel: DMA free:1080kB min:128kB low:160kB high:192kB active:11844kB inactive:4kB present:16384kB pages_scanned:13231 all_ unreclaimable? yes Apr 15 14:06:23 vaio kernel: lowmem_reserve[]: 0 238 238 Apr 15 14:06:23 vaio kernel: Normal free:2512kB min:1908kB low:2384kB high:2860kB active:179428kB inactive:6672kB present:244224kB pages_scanned :0 all_unreclaimable? no Apr 15 14:06:23 vaio kernel: lowmem_reserve[]: 0 0 0 Apr 15 14:06:23 vaio kernel: HighMem free:0kB min:128kB low:160kB high:192kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimab le? no Apr 15 14:06:23 vaio kernel: lowmem_reserve[]: 0 0 0 Apr 15 14:06:23 vaio kernel: DMA: 0*4kB 1*8kB 1*16kB 1*32kB 0*64kB 0*128kB 0*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 1080kB Apr 15 14:06:23 vaio kernel: Normal: 122*4kB 29*8kB 2*16kB 7*32kB 4*64kB 0*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 2512kB Apr 15 14:06:23 vaio kernel: HighMem: empty Apr 15 14:06:23 vaio kernel: Swap cache: add 725, delete 715, find 0/0, race 0+0 Apr 15 14:06:23 vaio kernel: Free swap = 527204kB Apr 15 14:06:23 vaio kernel: Total swap = 530104kB Apr 15 14:06:23 vaio kernel: Out of Memory: Killed process 7956 (klauncher). Apr 15 14:08:01 vaio /USR/SBIN/CRON[11218]: (mail) CMD ( if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; fi) Apr 15 14:09:27 vaio kernel: oom-killer: gfp_mask=0xd0 Apr 15 14:09:28 vaio kernel: DMA per-cpu: Apr 15 14:09:28 vaio kernel: cpu 0 hot: low 2, high 6, batch 1 Apr 15 14:09:28 vaio kernel: cpu 0 cold: low 0, high 2, batch 1 Apr 15 14:09:28 vaio kernel: Normal per-cpu: Apr 15 14:09:28 vaio kernel: cpu 0 hot: low 28, high 84, batch 14 Apr 15 14:09:28 vaio kernel: cpu 0 cold: low 0, high 28, batch 14 Apr 15 14:09:28 vaio kernel: HighMem per-cpu: empty Apr 15 14:09:28 vaio kernel: Apr 15 14:09:28 vaio kernel: Free pages:3880kB (0kB HighMem) Apr 15 14:09:28 vaio kernel: Active:39358 inactive:10162 dirty:0 writeback:1257 unstable:0 free:970 slab:3317 mapped:48159 pagetables:750 Apr 15 14:09:28 vaio kernel: DMA free:1080kB min:128kB low:160kB high:192kB active:11868kB inactive:0kB present:16384kB pages_scanned:12192 all_ unreclaimable? yes Apr 15 14:09:28 vaio kernel: lowmem_reserve[]: 0 238 238 Apr 15 14:09:28 vaio kernel: Normal free:2800kB min:1908kB low:2384kB high:2860kB active:145564kB inactive:40648kB present:244224kB pages_scanne d:0 all_unreclaimable? no Apr 15 14:09:28 vaio kernel: lowmem_reserve[]: 0 0 0 Apr 15 14:09:28 vaio kernel: HighMem free:0kB min:128kB low:160kB high:192kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimab le? no Apr 15 14:09:28 vaio kernel: lowmem_reserve[]: 0 0 0 Apr 15 14:09:28 vaio kernel: DMA: 0*4kB 1*8kB 1*16kB 1*32kB 0*64kB 0*128kB 0*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 1080kB Apr 15 14:09:28 vaio kernel: Normal: 118*4kB 19*8kB 12*16kB 10*32kB 6*64kB 0*128kB 1*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 2800kB Apr 15 14:09:28 vaio kernel: HighMem: empty Apr 15 14:09:28 vaio kernel: Swap cache: add 2342, delete 1067, find 0/0, race 0+0 Apr 15 14:09:28 vaio kernel: Free swap = 520736kB Apr 15 14:09:28 vaio kernel: Total swap = 530104kB Apr 15 14:09:28 vaio kernel: Out of Memory: Killed process 7982 (kwin). At the same time /proc/meminfo looked like this: Fri Apr 15 14:06:12 CEST 2005 MemTotal: 255264 kB MemFree: 7684 kB Buffers: 860 kB Cached: 52756 kB SwapCached: 0 kB Active: 192256 kB Inactive: 1576 kB HighTotal: 0 kB HighFree:0 kB LowTotal: 255264 kB LowFree: 7684 kB SwapTotal: 530104 kB SwapFree: 527244 kB Dirty: 496 kB Writeback: 0 kB Mapped: 191412 kB Slab:13548 kB CommitLimit:657736 kB Committed_AS: 372396 kB PageTables: 3104 kB VmallocTotal:
Bug#291684: orinoco.c: Error -110 writing Tx descriptor to BAP
Package: kernel-source-2.6.10 Version: 2.6.10-4 Severity: important Hi, I'm seeing the Error -110 writing Tx descriptor to BAP bug as described in FAQ at http://ozlabs.org/people/dgibson/dldwd/ about once every other day. orinoco.c prints to the syslog at such a rate, that the system becomes completely unresponsive and I have to reboot. The lspci output for the chip is: :02:0b.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) Subsystem: AMBIT Microsystem Corp.: Unknown device 0201 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin A routed to IRQ 9 Region 0: Memory at e050 (32-bit, prefetchable) [size=4K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Updating to version 0.15rc2 of the driver (which the author considers stable but doesn't have time to submit to mainline) fixes the problem. Including the new driver in testing is probably too much hassle, but maybe it's worthwhile for stable. Regards, Georg -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-gw1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-source-2.6.10 depends on: ii binutils 2.15-5 The GNU assembler, linker and bina ii bzip2 1.0.2-1A high-quality block-sorting file ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290925: kernel-source-2.6.10: Blank Screen When Using intelfb Module
Package: kernel-source-2.6.10 Version: 2.6.10-3 Severity: normal When the intelfb module is compiled into the kernel all consoles remain blank until the X server starts up. Using it as a module is not an option for non-CRT screens (see http://www.xfree86.org/~dawes/intelfb.html, which I'm assuming not to be outdated on this issue). This makes the driver unusable for laptops. The initialization seems to be OK (from dmesg): Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected an Intel 830M Chipset. agpgart: Maximum main memory to use for agp memory: 202M agpgart: Detected 892K stolen memory. agpgart: AGP aperture is 128M @ 0xe800 intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G chipsets intelfb: Version 0.9.2 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9 PCI: setting IRQ 9 as level-triggered ACPI: PCI interrupt :00:02.0[A] - GSI 9 (level, low) - IRQ 9 intelfb: 00:02.0: Intel(R) 830M, aperture size 128MB, stolen memory 892kB intelfb: Non-CRT device is enabled ( DVO port B ). Disabling mode switching. intelfb: Initial video mode is [EMAIL PROTECTED] I was unable to try vesa modes with a higher resolution than vga=0x311 as my BIOS doesn't support these values. This problem is similar to bug #289810, but I doubt that is directly related as vesafb doesn't figure into this particular configuration. Thanks for looking into this. Georg -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-gw1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-source-2.6.10 depends on: ii binutils 2.15-5 The GNU assembler, linker and bina ii bzip2 1.0.2-1A high-quality block-sorting file ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#281912: Still Present in 2.6.10
Hello! Just a quick note that this bug is still present in 2.6.10, and hence this report should be moved over to that package. Thanks again. Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ pgpjsRSX6UUwZ.pgp Description: PGP signature
Bug#281912: Tested with devfs and static
Hello, Andres! Just out of curiosity, what happens if you enable devfs (devfs=mount; don't forget to install devfsd, also) and try the same thing? I'm getting the same behavior with both devfs and static dev. Output is as follows: DevFS: == [Plug-in FireWire CDROM Drive] Dec 27 17:22:58 tucker kernel: ieee1394: Error parsing configrom for node 0-01:1023 Dec 27 17:22:58 tucker kernel: ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... Dec 27 17:22:59 tucker kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[0800460300e13f1d] Dec 27 17:22:59 tucker kernel: ieee1394: Node changed: 0-00:1023 - 0-01:1023 Dec 27 17:22:59 tucker kernel: sbp2: $Rev: 1219 $ Ben Collins [EMAIL PROTECTED] Dec 27 17:22:59 tucker kernel: scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices Dec 27 17:23:00 tucker kernel: ieee1394: sbp2: Logged into SBP-2 device Dec 27 17:23:00 tucker kernel: ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048] Dec 27 17:23:03 tucker kernel: Vendor: SONY Model: CD-RW CRX820E Rev: 1.5a Dec 27 17:23:03 tucker kernel: Type: CD-ROM ANSI SCSI revision: 02 Dec 27 17:23:03 tucker ieee1394.agent[3940]: sbp2: loaded successfully Dec 27 17:23:03 tucker kernel: sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray Dec 27 17:23:03 tucker kernel: Uniform CD-ROM driver Revision: 3.20 Dec 27 17:23:03 tucker kernel: Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0 Dec 27 17:23:03 tucker kernel: Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 5 Dec 27 17:23:03 tucker devfsd[941]: fixscsigenericperms(scsi/host1/bus0/target0/lun0/generic) Dec 27 17:23:03 tucker devfsd[941]: Changed scsi/host1/bus0/target0/lun0/generic to be 0/24 0660 Dec 27 17:23:04 tucker scsi.agent[3971]: cdrom at /devices/pci:00/:00:1e.0/:02:02.0/fw-host0/0800460300e13f1d/0800460300e13f1d-0/host1/1:0:0:0 [Unplug FireWire CDROM Drive] Dec 27 17:23:21 tucker kernel: ieee1394: Node changed: 0-01:1023 - 0-00:1023 Dec 27 17:23:21 tucker kernel: ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0800460300e13f1d] [Plug-in FireWire CDROM Drive] [Unplug FireWire CDROM Drive] [Plug-in FireWire CDROM Drive] [Unplug FireWire CDROM Drive] Static /dev: === [Plug-in FireWire CDROM Drive] Dec 27 17:30:53 tucker kernel: ieee1394: Error parsing configrom for node 0-01:1023 Dec 27 17:30:53 tucker kernel: ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... Dec 27 17:30:53 tucker kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[0800460300e13f1d] Dec 27 17:30:53 tucker kernel: ieee1394: Node changed: 0-00:1023 - 0-01:1023 Dec 27 17:30:53 tucker kernel: sbp2: $Rev: 1219 $ Ben Collins [EMAIL PROTECTED] Dec 27 17:30:53 tucker kernel: scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices Dec 27 17:30:54 tucker kernel: ieee1394: sbp2: Logged into SBP-2 device Dec 27 17:30:54 tucker kernel: ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048] Dec 27 17:30:58 tucker ieee1394.agent[3947]: sbp2: loaded successfully Dec 27 17:30:58 tucker scsi.agent[3976]: cdrom at /devices/pci:00/:00:1e.0/:02:02.0/fw-host0/0800460300e13f1d/0800460300e13f1d-0/host1/1:0:0:0 Dec 27 17:30:58 tucker kernel: Vendor: SONY Model: CD-RW CRX820E Rev: 1.5a Dec 27 17:30:58 tucker kernel: Type: CD-ROM ANSI SCSI revision: 02 Dec 27 17:30:58 tucker kernel: Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 5 Dec 27 17:30:58 tucker kernel: sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray Dec 27 17:30:58 tucker kernel: Uniform CD-ROM driver Revision: 3.20 Dec 27 17:30:58 tucker kernel: Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0 [Unplug FireWire CDROM Drive] Dec 27 17:31:08 tucker kernel: ieee1394: Node changed: 0-01:1023 - 0-00:1023 Dec 27 17:31:08 tucker kernel: ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0800460300e13f1d] [Plug-in FireWire CDROM Drive] [Unplug FireWire CDROM Drive] [Plug-in FireWire CDROM Drive] [Unplug FireWire CDROM Drive] The problem really seems to be pruly in kernel space. (Could be related to http://bugzilla.kernel.org/show_bug.cgi?id=3266) Similar to this report, I cannot unload the modules sr_mod and sbp2 in all cases. Both rmmod processes hang forever in disk sleep. Thanks for looking into this. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ pgp03DItwRSvY.pgp Description: PGP signature
