From: Greg KH <gregkh@suse.de>
To: Mark Lord <lkml@rtr.ca>, jkosina@suse.cz
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org, Pavel Machek <pavel@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.25-rc7: Ugh.
Date: Thu, 27 Mar 2008 09:07:00 -0700 [thread overview]
Message-ID: <20080327160700.GB828@suse.de> (raw)
In-Reply-To: <47EBBD57.30902@rtr.ca>
On Thu, Mar 27, 2008 at 11:29:27AM -0400, Mark Lord wrote:
> It is with great reluctance when I attempt moving my main "desktop"
> over to a new kernel version -- because the USB subsystem seems to
> break every single time.
That's not good, why not tell the linux-usb developers this? (added to
the cc:)
> So today I tried 2.6.25-rc7 on it for the first time.
> Not good.
>
> It boots, but just a simple suspend/resume (RAM) was enough to kill it.
> It comes back on resume, with an X desktop again,
> but with no USB functionality -- no mouse.
>
> The keyboard still works, so I dropped to a console and tried:
>
> rmmod usbhid
> insmod usbhid
>
> And the console hung at 100% CPU on the insmod.
Haven't heard of this one before sorry. Jiri, have you?
> Back to 2.6.24.3 again, for now -- I've got work to do.
>
> The specs of this machine have been posted with great regularity
> in the past, every new kernel revision it seems. So here we go again:
>
> Dell Inspiron 9400 notebook, Intel Core2Duo T7400, 2GB SDRAM.
>
> Suspend/Resume have worked perfectly (after kernel fixes, mostly USB)
> for all kernels in the past since 2.6.20 or so.
>
> Here's the /var/log/messages from the suspend/resume.
> That's it for now. I've got work to do, and I'm tired of
> seeing this break with each new revision.
>
>
> logger: /usr/local/bin/suspend.sh kernel: [ 107.491762] PM: Syncing
> filesystems ... done.
> kernel: [ 107.492274] Freezing user space processes ... (elapsed 0.00
> seconds) done.
> kernel: [ 107.493016] Freezing remaining freezable tasks ... (elapsed 0.00
> seconds) done.
> kernel: [ 107.499129] ACPI: Preparing to enter system sleep state S3
> kernel: [ 107.499656] Suspending console(s)
> kernel: [ 107.524879] b44: eth0: powering down PHY
> kernel: [ 108.011326] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> kernel: [ 108.011473] sd 0:0:0:0: [sda] Stopping disk
> kernel: [ 110.058446] pciehp_suspend ENTRY
> last message repeated 2 times
> kernel: [ 110.058446] ricoh-mmc: Suspending.
> kernel: [ 110.058446] ricoh-mmc: Controller is now re-enabled.
> kernel: [ 110.058446] ACPI handle has no context!
> kernel: [ 110.058446] ACPI: PCI interrupt for device 0000:03:01.1 disabled
> kernel: [ 110.058446] ACPI handle has no context!
> kernel: [ 110.089544] ACPI: PCI interrupt for device 0000:03:00.0 disabled
> kernel: [ 110.089554] ACPI handle has no context!
> kernel: [ 110.102988] ACPI: PCI interrupt for device 0000:00:1f.2 disabled
> kernel: [ 110.116231] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
> kernel: [ 110.129385] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
> kernel: [ 110.129433] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
> kernel: [ 110.129480] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
> kernel: [ 110.129526] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
> kernel: [ 110.129533] pciehp_suspend ENTRY
> kernel: [ 110.129601] pciehp_suspend ENTRY
> kernel: [ 110.129668] pciehp_suspend ENTRY
> kernel: [ 110.142697] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> kernel: [ 110.155936] Disabling non-boot CPUs ...
> kernel: [ 110.159155] CPU 1 is now offline
> kernel: [ 110.159159] SMP alternatives: switching to UP code
> kernel: [ 110.161085] CPU1 is down
> kernel: [ 110.161085] Back to C!
> kernel: [ 110.161498] Enabling non-boot CPUs ...
> kernel: [ 110.161854] SMP alternatives: switching to SMP code
> kernel: [ 110.162467] Booting processor 1/1 ip 4000
> kernel: [ 110.162471] CPU 1 irqstacks, hard=c037f000 soft=c037d000
> kernel: [ 111.314889] Initializing CPU#1
> kernel: [ 111.314889] Calibrating delay using timer specific routine..
> 4321.52 BogoMIPS (lpj=7199246)
> kernel: [ 111.314889] CPU: L1 I cache: 32K, L1 D cache: 32K
> kernel: [ 111.314889] CPU: L2 cache: 4096K
> kernel: [ 111.314889] CPU: Physical Processor ID: 0
> kernel: [ 111.314889] CPU: Processor Core ID: 1
> kernel: [ 110.256366] CPU1: Intel(R) Core(TM)2 CPU T7400 @
> 2.16GHz stepping 06
> kernel: [ 111.314889] CPU1 is up
> kernel: [ 111.314896] Switched to high resolution mode on CPU 1
> kernel: [ 111.349610] PM: Writing back config space on device 0000:00:01.0
> at offset a (was f, writing 0)
> kernel: [ 111.349618] PM: Writing back config space on device 0000:00:01.0
> at offset 3 (was 10000, writing 10010)
> kernel: [ 111.349629] PCI: Setting latency timer of device 0000:00:01.0 to
> 64
> kernel: [ 111.360769] PM: Writing back config space on device 0000:00:1b.0
> at offset f (was 100, writing 10b)
> kernel: [ 111.360795] PM: Writing back config space on device 0000:00:1b.0
> at offset 4 (was ffa7c004, writing efffc004)
> kernel: [ 111.360804] PM: Writing back config space on device 0000:00:1b.0
> at offset 3 (was 0, writing 10)
> kernel: [ 111.360814] PM: Writing back config space on device 0000:00:1b.0
> at offset 1 (was 100000, writing 100102)
> kernel: [ 111.360845] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 21
> (level, low) -> IRQ 21
> kernel: [ 111.360856] PCI: Setting latency timer of device 0000:00:1b.0 to
> 64
> kernel: [ 111.360892] PM: Writing back config space on device 0000:00:1c.0
> at offset f (was 100, writing 20100)
> kernel: [ 111.360910] PM: Writing back config space on device 0000:00:1c.0
> at offset 9 (was 10001, writing 1fff1)
> kernel: [ 111.360917] PM: Writing back config space on device 0000:00:1c.0
> at offset 8 (was 0, writing fff0)
> kernel: [ 111.360925] PM: Writing back config space on device 0000:00:1c.0
> at offset 7 (was 0, writing 200000f0)
> kernel: [ 111.360932] PM: Writing back config space on device 0000:00:1c.0
> at offset 6 (was 0, writing b0b00)
> kernel: [ 111.360944] PM: Writing back config space on device 0000:00:1c.0
> at offset 3 (was 810000, writing 810010)
> kernel: [ 111.360954] PM: Writing back config space on device 0000:00:1c.0
> at offset 1 (was 100000, writing 100007)
> kernel: [ 111.360982] PCI: Setting latency timer of device 0000:00:1c.0 to
> 64
> kernel: [ 111.360989] pciehp_resume ENTRY
> kernel: [ 111.361035] PM: Writing back config space on device 0000:00:1c.1
> at offset f (was 200, writing 20200)
> kernel: [ 111.361047] PM: Writing back config space on device 0000:00:1c.1
> at offset 9 (was 10001, writing 1fff1)
> kernel: [ 111.361052] PM: Writing back config space on device 0000:00:1c.1
> at offset 8 (was 0, writing efc0efc0)
> kernel: [ 111.361056] PM: Writing back config space on device 0000:00:1c.1
> at offset 7 (was 20000000, writing 200000f0)
> kernel: [ 111.361061] PM: Writing back config space on device 0000:00:1c.1
> at offset 6 (was 0, writing c0c00)
> kernel: [ 111.361068] PM: Writing back config space on device 0000:00:1c.1
> at offset 3 (was 810000, writing 810010)
> kernel: [ 111.361075] PM: Writing back config space on device 0000:00:1c.1
> at offset 1 (was 100000, writing 100107)
> kernel: [ 111.361095] PCI: Setting latency timer of device 0000:00:1c.1 to
> 64
> kernel: [ 111.361099] pciehp_resume ENTRY
> kernel: [ 112.362047] pciehp: Device 0000:0c:00.0 already exists at c:0,
> cannot hot-add
> kernel: [ 112.362052] pciehp: Cannot add device 0xc:0
> kernel: [ 112.362085] PM: Writing back config space on device 0000:00:1c.3
> at offset f (was 400, writing 20400)
> kernel: [ 112.362102] PM: Writing back config space on device 0000:00:1c.3
> at offset 9 (was 10001, writing e011e001)
> kernel: [ 112.362110] PM: Writing back config space on device 0000:00:1c.3
> at offset 8 (was 0, writing efb0efa0)
> kernel: [ 112.362117] PM: Writing back config space on device 0000:00:1c.3
> at offset 7 (was 0, writing d0d0)
> kernel: [ 112.362125] PM: Writing back config space on device 0000:00:1c.3
> at offset 6 (was 0, writing e0d00)
> kernel: [ 112.362136] PM: Writing back config space on device 0000:00:1c.3
> at offset 3 (was 810000, writing 810010)
> kernel: [ 112.362146] PM: Writing back config space on device 0000:00:1c.3
> at offset 1 (was 100000, writing 100007)
> kernel: [ 112.362174] PCI: Setting latency timer of device 0000:00:1c.3 to
> 64
> kernel: [ 112.362181] pciehp_resume ENTRY
> kernel: [ 112.362213] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20
> (level, low) -> IRQ 20
> kernel: [ 112.362222] PCI: Setting latency timer of device 0000:00:1d.0 to
> 64
> kernel: [ 112.362287] usb usb1: root hub lost power or was reset
> kernel: [ 112.362311] PCI: Enabling device 0000:00:1d.1 (0000 -> 0001)
> kernel: [ 112.362316] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 21
> (level, low) -> IRQ 21
> kernel: [ 112.362326] PCI: Setting latency timer of device 0000:00:1d.1 to
> 64
> kernel: [ 112.362335] PM: Writing back config space on device 0000:00:1d.1
> at offset f (was 200, writing 20b)
> kernel: [ 112.362353] PM: Writing back config space on device 0000:00:1d.1
> at offset 8 (was 1, writing bf61)
> kernel: [ 112.362399] usb usb2: root hub lost power or was reset
> kernel: [ 112.362421] PCI: Enabling device 0000:00:1d.2 (0000 -> 0001)
> kernel: [ 112.362426] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 22
> (level, low) -> IRQ 22
> kernel: [ 112.362436] PCI: Setting latency timer of device 0000:00:1d.2 to
> 64
> kernel: [ 112.362445] PM: Writing back config space on device 0000:00:1d.2
> at offset f (was 300, writing 309)
> kernel: [ 112.362464] PM: Writing back config space on device 0000:00:1d.2
> at offset 8 (was 1, writing bf41)
> kernel: [ 112.362509] usb usb3: root hub lost power or was reset
> kernel: [ 112.362532] PCI: Enabling device 0000:00:1d.3 (0000 -> 0001)
> kernel: [ 112.362537] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 23
> (level, low) -> IRQ 23
> kernel: [ 112.362547] PCI: Setting latency timer of device 0000:00:1d.3 to
> 64
> kernel: [ 112.362556] PM: Writing back config space on device 0000:00:1d.3
> at offset f (was 400, writing 407)
> kernel: [ 112.362574] PM: Writing back config space on device 0000:00:1d.3
> at offset 8 (was 1, writing bf21)
> kernel: [ 112.362619] usb usb4: root hub lost power or was reset
> kernel: [ 112.375278] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 20
> (level, low) -> IRQ 20
> kernel: [ 112.375286] PCI: Setting latency timer of device 0000:00:1d.7 to
> 64
> kernel: [ 112.375379] PM: Writing back config space on device 0000:00:1e.0
> at offset 9 (was 100f1, writing 1fff1)
> kernel: [ 112.375390] PM: Writing back config space on device 0000:00:1e.0
> at offset 8 (was 90, writing ef90ef90)
> kernel: [ 112.375400] PM: Writing back config space on device 0000:00:1e.0
> at offset 7 (was 2280e0f0, writing 228000f0)
> kernel: [ 112.375418] PM: Writing back config space on device 0000:00:1e.0
> at offset 1 (was 100007, writing 100107)
> kernel: [ 112.375446] PCI: Setting latency timer of device 0000:00:1e.0 to
> 64
> kernel: [ 112.375495] PM: Writing back config space on device 0000:00:1f.0
> at offset 1 (was 2100007, writing 2100107)
> kernel: [ 112.388552] PM: Writing back config space on device 0000:00:1f.2
> at offset f (was 200, writing 205)
> kernel: [ 112.388602] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 17
> (level, low) -> IRQ 17
> kernel: [ 112.388610] PCI: Setting latency timer of device 0000:00:1f.2 to
> 64
> kernel: [ 112.388636] PM: Writing back config space on device 0000:00:1f.3
> at offset f (was 200, writing 205)
> kernel: [ 111.330331] ata2.00: _GTF evaluation failed (AE 0x1001)
> kernel: [ 111.330331] ata2.01: _GTF evaluation failed (AE 0x1001)
> kernel: [ 112.388678] PM: Writing back config space on device 0000:00:1f.3
> at offset 1 (was 2800001, writing 2800101)
> kernel: [ 112.388751] PM: Writing back config space on device 0000:01:00.0
> at offset f (was 1ff, writing 104)
> kernel: [ 112.388838] PM: Writing back config space on device 0000:01:00.0
> at offset 3 (was 0, writing 10)
> kernel: [ 111.330331] ata1.01: _GTF evaluation failed (AE 0x1001)
> kernel: [ 112.417656] PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
> kernel: [ 112.417662] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17
> (level, low) -> IRQ 17
> kernel: [ 112.417677] PM: Writing back config space on device 0000:03:00.0
> at offset f (was 100, writing 105)
> kernel: [ 112.417702] PM: Writing back config space on device 0000:03:00.0
> at offset 4 (was 0, writing ef9fe000)
> kernel: [ 112.417710] PM: Writing back config space on device 0000:03:00.0
> at offset 3 (was 0, writing 4000)
> kernel: [ 112.417720] PM: Writing back config space on device 0000:03:00.0
> at offset 1 (was 100002, writing 100106)
> kernel: [ 112.431706] PM: Writing back config space on device 0000:03:01.0
> at offset f (was 4020100, writing 4020103)
> kernel: [ 112.431734] PM: Writing back config space on device 0000:03:01.0
> at offset 4 (was 0, writing ef9fd800)
> kernel: [ 112.431742] PM: Writing back config space on device 0000:03:01.0
> at offset 3 (was 800000, writing 804000)
> kernel: [ 112.431751] PM: Writing back config space on device 0000:03:01.0
> at offset 1 (was 2100000, writing 2100106)
> kernel: [ 112.517139] PM: Writing back config space on device 0000:03:01.1
> at offset f (was 200, writing 209)
> kernel: [ 112.517168] PM: Writing back config space on device 0000:03:01.1
> at offset 4 (was 0, writing ef9fd400)
> kernel: [ 112.517176] PM: Writing back config space on device 0000:03:01.1
> at offset 3 (was 800000, writing 804000)
> kernel: [ 112.517186] PM: Writing back config space on device 0000:03:01.1
> at offset 1 (was 2100000, writing 2100106)
> kernel: [ 112.517211] ACPI: PCI Interrupt 0000:03:01.1[B] -> GSI 18
> (level, low) -> IRQ 18
> kernel: [ 112.517234] ricoh-mmc: Resuming.
> kernel: [ 112.517245] ricoh-mmc: Controller is now disabled.
> kernel: [ 112.517259] PM: Writing back config space on device 0000:03:01.3
> at offset f (was 200, writing 209)
> kernel: [ 112.517286] PM: Writing back config space on device 0000:03:01.3
> at offset 4 (was 0, writing ef9fd700)
> kernel: [ 112.517298] PM: Writing back config space on device 0000:03:01.3
> at offset 1 (was 2100000, writing 2100102)
> kernel: [ 112.517382] pciehp_resume ENTRY
> kernel: [ 112.517410] pciehp_resume ENTRY
> kernel: [ 111.839425] ata2.00: configured for UDMA/33
> kernel: [ 113.520191] pciehp: Device 0000:0c:00.0 already exists at c:0,
> cannot hot-add
> kernel: [ 113.520197] pciehp: Cannot add device 0xc:0
> kernel: [ 113.520214] pciehp_resume ENTRY
> kernel: [ 113.520461] sd 0:0:0:0: [sda] Starting disk
> kernel: [ 113.727280] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
> kernel: [ 113.746993] ata1.00: configured for UDMA/133
> kernel: [ 113.770650] sd 0:0:0:0: [sda] 312581808 512-byte hardware
> sectors (160042 MB)
> kernel: [ 113.770650] sd 0:0:0:0: [sda] Write Protect is off
> kernel: [ 113.770650] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> kernel: [ 113.770650] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> kernel: [ 114.901667] Restarting tasks ... <6>usb 5-1: USB disconnect,
> address 2
> kernel: [ 114.933424] done.
> kernel: [ 115.128131] usb 5-1: new high speed USB device using ehci_hcd
> and address 5
This looks like your usb device should be up and working.
Do you have CONFIG_USB_SUSPEND enabled in your .config?
> ## Note: these are "normal" and harmless on this machine,
> ## and the reason for them has never been tracked down:
> kernel: [ 115.198514] Uhhuh. NMI received for unknown reason 90 on CPU 0.
> kernel: [ 115.198519] You have some hardware problem, likely on the PCI
> bus.
> kernel: [ 115.198521] Dazed and confused, but trying to continue
Not very nice "harmless" messages :(
>
> kernel: [ 117.690742] b44: eth0: Link is up at 100 Mbps, full duplex.
> kernel: [ 117.690750] b44: eth0: Flow control is off for TX and off for
> RX.
> login[3020]: (pam_unix) session opened for user root by (uid=0)
> login[4507]: ROOT LOGIN on 'tty1'
> root: reloading usbhid module
> kernel: [ 225.955054] usbcore: deregistering interface driver usbhid
> kernel: [ 225.966118] usbcore: deregistering interface driver hiddev
> root: session hung on insmod
> kernel: [ 248.875843] SysRq : Emergency Sync
> kernel: [ 248.876629] Emergency Sync complete
> kernel: [ 249.535815] SysRq : Emergency Remount R/O
next prev parent reply other threads:[~2008-03-27 16:15 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 15:29 2.6.25-rc7: Ugh Mark Lord
2008-03-27 16:07 ` Greg KH [this message]
2008-03-28 0:32 ` Jiri Kosina
2008-03-28 1:57 ` Mark Lord
2008-03-28 3:12 ` David Miller
2008-03-28 4:42 ` Bob Tracy
2008-03-28 4:56 ` David Miller
2008-03-28 5:17 ` Mark Lord
2008-03-28 6:01 ` david
2008-03-28 16:34 ` Bob Tracy
2008-04-05 18:23 ` Bill Davidsen
2008-03-28 5:36 ` Mike Galbraith
2008-03-28 5:46 ` Mark Lord
2008-03-28 5:52 ` Mark Lord
2008-03-28 6:05 ` Mark Lord
2008-03-28 6:58 ` David Brownell
2008-03-28 9:16 ` Ingo Molnar
2008-03-28 9:49 ` David Brownell
2008-03-28 10:20 ` Ingo Molnar
2008-03-28 11:01 ` Pavel Machek
2008-03-28 15:03 ` Jan Engelhardt
2008-03-28 20:14 ` David Brownell
2008-03-28 12:51 ` Kconfig RTC selection (was: 2.6.25-rc7: Ugh.) Tilman Schmidt
2008-03-28 13:49 ` Kconfig RTC selection Mark Lord
2008-03-28 19:22 ` Kconfig RTC selection (was: 2.6.25-rc7: Ugh.) David Brownell
2008-03-29 12:55 ` Kconfig RTC selection Tilman Schmidt
2008-03-28 13:47 ` 2.6.25-rc7: Ugh Mark Lord
2008-03-28 20:04 ` Kconfig RTC selection (was: 2.6.25-rc7: Ugh.) David Brownell
2008-03-28 21:06 ` Adrian Bunk
2008-03-28 21:23 ` David Brownell
2008-03-28 21:33 ` Adrian Bunk
2008-03-28 21:45 ` David Brownell
2008-03-28 21:59 ` Adrian Bunk
2008-03-28 22:18 ` David Brownell
2008-03-28 22:36 ` Adrian Bunk
2008-03-29 11:40 ` [rtc-linux] " Alessandro Zummo
2008-03-28 14:56 ` 2.6.25-rc7: Ugh Jan Engelhardt
2008-03-28 17:47 ` Adrian Bunk
2008-03-29 3:58 ` Mark Lord
2008-03-28 1:51 ` Mark Lord
2008-03-28 2:11 ` Mark Lord
2008-03-28 2:13 ` Mark Lord
2008-03-28 14:34 ` Alan Stern
2008-03-28 14:57 ` Mark Lord
2008-03-27 22:00 ` Rafael J. Wysocki
2008-03-28 5:22 ` Mark Lord
2008-03-28 2:14 ` Mark Lord
2008-03-28 9:24 ` Pavel Machek
2008-03-30 21:04 ` Mark Lord
2008-03-30 21:09 ` Mark Lord
2008-03-31 11:55 ` Oliver Neukum
2008-03-31 14:39 ` Mark Lord
2008-03-31 15:04 ` Oliver Neukum
2008-03-31 15:04 ` Mark Lord
2008-03-31 15:14 ` Mark Lord
2008-03-31 16:37 ` Oliver Neukum
2008-03-31 17:03 ` Mark Lord
2008-03-31 17:06 ` Mark Lord
2008-03-31 17:15 ` Mark Lord
2008-03-31 17:21 ` Mark Lord
2008-03-31 17:30 ` Mark Lord
2008-03-31 18:05 ` Oliver Neukum
2008-03-31 19:21 ` Mark Lord
2008-04-02 8:04 ` Oliver Neukum
2008-04-02 14:38 ` Mark Lord
2008-04-02 14:38 ` Mark Lord
2008-04-02 15:05 ` 2.6.25-rc7/rc8 USB dead on resume Mark Lord
2008-04-02 15:21 ` Oliver Neukum
2008-04-02 15:08 ` 2.6.25-rc7: Ugh Alan Stern
2008-04-02 15:44 ` 2.6.25-rc7: Ugh. ---> PATCH Mark Lord
2008-04-02 15:47 ` Mark Lord
2008-04-02 15:49 ` Mark Lord
2008-04-02 20:09 ` Alan Stern
2008-04-02 16:04 ` 2.6.25-rc7: Ugh David Brownell
2008-04-02 16:09 ` Mark Lord
2008-04-02 20:22 ` David Brownell
2008-04-02 16:20 ` [PATCH] usb ehci_iaa_watchdog fix Mark Lord
2008-04-02 16:48 ` Alan Stern
2008-04-02 17:34 ` Mark Lord
2008-04-02 18:08 ` Mark Lord
2008-04-02 19:20 ` Alan Stern
2008-04-02 20:42 ` David Brownell
2008-04-02 21:08 ` Alan Stern
2008-04-07 23:37 ` David Brownell
2008-04-08 2:13 ` Alan Stern
2008-04-02 20:31 ` David Brownell
2008-04-02 20:55 ` Alan Stern
2008-04-02 23:07 ` David Brownell
2008-04-02 16:56 ` David Brownell
2008-04-01 9:59 ` 2.6.25-rc7: Ugh Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080327160700.GB828@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=pavel@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox