[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224


akpm@osdl.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Regression|0                           |1




-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #1 from anonymous@kernel-bugs.osdl.org  2008-12-14 14:30 -------
Reply-To: akpm@linux-foundation.org


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Sun, 14 Dec 2008 11:39:34 -0800 (PST) bugme-daemon@bugzilla.kernel.org
wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=12224
> 
>            Summary: journal activity on inactive partition causes inactive
>                     harddrive spinup
>            Product: File System
>            Version: 2.5
>      KernelVersion: 2.6.27.6
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: low
>           Priority: P1
>          Component: ext3
>         AssignedTo: fs_ext3@kernel-bugs.osdl.org
>         ReportedBy: csights@fastmail.fm
> 
> 
> Latest working kernel version: 2.6.27.5
> Earliest failing kernel version: 2.6.27.6

Thanks for being this specific.

> Distribution: Debian stable with custom compiled vanilla kernel
> 
> Problem Description:
>     Activity on one partition (hda1) causes kjournald to also write to another
> partition (sda1).  This in turn causes the harddrive which contains sda1 to
> spinup or not spindown.
>     I've activated laptop-mode using laptop-mode-tools. hda1 and sda1 are both
> formatted with ext3.
>     On unaffected kernels (e.g. 2.6.27.5) btrace produces no output.  On
> affected kernels (e.g. 2.6.27.6, 2.6.27-rc7) btrace produces output as below.

I think I've seen other reports of this.  Maybe it was you.

> /dev/hda1 on / type ext3 (rw,noatime,errors=remount-ro,commit=1209600)
> tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
> udev on /dev type tmpfs (rw,mode=0755)
> tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
> debugfs on /sys/kernel/debug type debugfs (rw)
> 
> Steps to reproduce:
>     1. start "btrace /dev/sda"
>     2. begin compiling kernel
>     3. within seconds btrace begins output similar to below.
> 
> 
> Thanks for all your work!  Sorry if I've misplaced blame for this undesirable
> change in behavior.
> 
> Using 2.6.27.8, btrace of /dev/sda while compiling on /dev/hda1

OK, that's a huge mess because bugzilla went and wordwrapped it.  Let
me fix it:

> Dec   9 11:15:32 localhost logger:    8,0      0            1       0.000000000    1109   A   WS 14375 + 8 <- (8,1) 14312
> Dec   9 11:15:32 localhost logger:    8,0      0            2       0.000006705   1109   Q   WS 14375 + 8 [kjournald]
> Dec   9 11:15:32 localhost logger:    8,0      0            3       0.000043581   1109   G   WS 14375 + 8 [kjournald] 
> Dec   9 11:15:32 localhost logger:    8,0      0            4       0.000065651   1109   P    N [kjournald]
> Dec   9 11:15:32 localhost logger:    8,0      0            5       0.000076267   1109   I    W 14375 + 8 [kjournald]
> Dec   9 11:15:32 localhost logger:    8,0      0            6       0.000300318   1109   D    W 14375 + 8 [kjournald]
> Dec   9 11:15:32 localhost logger:    8,0      0            7       0.000423518   1109   U    N [kjournald] 1
> Dec   9 11:15:32 localhost logger:    8,0      0            8       0.010028373      3   C    W 14375 + 8 [0]
> Dec   9 11:15:35 localhost logger:    8,0      0            9       3.219049689   1109   A   WS 14383 + 8 <- (8,1) 14320
> Dec   9 11:15:35 localhost logger:    8,0      0           10       3.219058350   1109   Q   WS 14383 + 8 [kjournald]
> Dec   9 11:15:35 localhost logger:    8,0      0           11       3.219095505   1109   G   WS 14383 + 8 [kjournald]
> Dec   9 11:15:35 localhost logger:    8,0      0           12       3.219115061   1109   P    N [kjournald]
> Dec   9 11:15:35 localhost logger:    8,0      0           13       3.219127074   1109   I    W 14383 + 8 [kjournald]
> Dec   9 11:15:35 localhost logger:    8,0      0           14       3.219344699   1109   D    W 14383 + 8 [kjournald]
> Dec   9 11:15:35 localhost logger:    8,0      0           15       3.219543607   1109   U    N [kjournald] 1
> Dec   9 11:15:35 localhost logger:    8,0      0           16       3.229477275       3   C    W 14383 + 8 [0]

I'm not familar with btrace.  What are we looking at here?

The only likely commit I see in
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27.6 is "ext3:
wait on all pending commits in ext3_sync_fs", but I don't see how it
could cause this.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Re: [Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[Eric Sandeen]

bugme-daemon@bugzilla.kernel.org wrote:

> OK, that's a huge mess because bugzilla went and wordwrapped it.  Let
> me fix it:
> 
>> Dec   9 11:15:32 localhost logger:    8,0      0            1       0.000000000    1109   A   WS 14375 + 8 <- (8,1) 14312
>> Dec   9 11:15:32 localhost logger:    8,0      0            2       0.000006705   1109   Q   WS 14375 + 8 [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            3       0.000043581   1109   G   WS 14375 + 8 [kjournald] 
>> Dec   9 11:15:32 localhost logger:    8,0      0            4       0.000065651   1109   P    N [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            5       0.000076267   1109   I    W 14375 + 8 [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            6       0.000300318   1109   D    W 14375 + 8 [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            7       0.000423518   1109   U    N [kjournald] 1
>> Dec   9 11:15:32 localhost logger:    8,0      0            8       0.010028373      3   C    W 14375 + 8 [0]
>> Dec   9 11:15:35 localhost logger:    8,0      0            9       3.219049689   1109   A   WS 14383 + 8 <- (8,1) 14320
>> Dec   9 11:15:35 localhost logger:    8,0      0           10       3.219058350   1109   Q   WS 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           11       3.219095505   1109   G   WS 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           12       3.219115061   1109   P    N [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           13       3.219127074   1109   I    W 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           14       3.219344699   1109   D    W 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           15       3.219543607   1109   U    N [kjournald] 1
>> Dec   9 11:15:35 localhost logger:    8,0      0           16       3.229477275       3   C    W 14383 + 8 [0]
> 
> I'm not familar with btrace.  What are we looking at here?

Andrew, it's blktrace/blkparse output, basically.  blkparse(1) manpage
has the details.

maj,min cpu  seq  time           pid   act rwbs off+len
8,0      0    1   0.000000000    1109   A   WS 14375 + 8 <- (8,1) 14312

... etc

I'm not sure it gives us enough info; all we see is that there was an IO
on sdb (from sdb1)

I might suggest

# sysctl -w vm.block_dump=1

to see if you get any info about inodes on sda1 being dirtied.

(Also, I didn't see any info about sda1 in the posted fstab...)

-Eric

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #2 from sandeen@redhat.com  2008-12-14 15:10 -------
bugme-daemon@bugzilla.kernel.org wrote:

> OK, that's a huge mess because bugzilla went and wordwrapped it.  Let
> me fix it:
> 
>> Dec   9 11:15:32 localhost logger:    8,0      0            1       0.000000000    1109   A   WS 14375 + 8 <- (8,1) 14312
>> Dec   9 11:15:32 localhost logger:    8,0      0            2       0.000006705   1109   Q   WS 14375 + 8 [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            3       0.000043581   1109   G   WS 14375 + 8 [kjournald] 
>> Dec   9 11:15:32 localhost logger:    8,0      0            4       0.000065651   1109   P    N [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            5       0.000076267   1109   I    W 14375 + 8 [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            6       0.000300318   1109   D    W 14375 + 8 [kjournald]
>> Dec   9 11:15:32 localhost logger:    8,0      0            7       0.000423518   1109   U    N [kjournald] 1
>> Dec   9 11:15:32 localhost logger:    8,0      0            8       0.010028373      3   C    W 14375 + 8 [0]
>> Dec   9 11:15:35 localhost logger:    8,0      0            9       3.219049689   1109   A   WS 14383 + 8 <- (8,1) 14320
>> Dec   9 11:15:35 localhost logger:    8,0      0           10       3.219058350   1109   Q   WS 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           11       3.219095505   1109   G   WS 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           12       3.219115061   1109   P    N [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           13       3.219127074   1109   I    W 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           14       3.219344699   1109   D    W 14383 + 8 [kjournald]
>> Dec   9 11:15:35 localhost logger:    8,0      0           15       3.219543607   1109   U    N [kjournald] 1
>> Dec   9 11:15:35 localhost logger:    8,0      0           16       3.229477275       3   C    W 14383 + 8 [0]
> 
> I'm not familar with btrace.  What are we looking at here?

Andrew, it's blktrace/blkparse output, basically.  blkparse(1) manpage
has the details.

maj,min cpu  seq  time           pid   act rwbs off+len
8,0      0    1   0.000000000    1109   A   WS 14375 + 8 <- (8,1) 14312

... etc

I'm not sure it gives us enough info; all we see is that there was an IO
on sdb (from sdb1)

I might suggest

# sysctl -w vm.block_dump=1

to see if you get any info about inodes on sda1 being dirtied.

(Also, I didn't see any info about sda1 in the posted fstab...)

-Eric


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Re: [Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[Goswin von Brederlow]

Eric Sandeen <sandeen@redhat.com> writes:

> maj,min cpu  seq  time           pid   act rwbs off+len
> 8,0      0    1   0.000000000    1109   A   WS 14375 + 8 <- (8,1) 14312
>
> ... etc
>
> I'm not sure it gives us enough info; all we see is that there was an IO
> on sdb (from sdb1)
>
> I might suggest
>
> # sysctl -w vm.block_dump=1
>
> to see if you get any info about inodes on sda1 being dirtied.

Like atime/diratime updates?

> (Also, I didn't see any info about sda1 in the posted fstab...)
>
> -Eric

MfG
        Goswin

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #3 from anonymous@kernel-bugs.osdl.org  2008-12-14 17:22 -------
Reply-To: goswin-v-b@web.de

Eric Sandeen <sandeen@redhat.com> writes:

> maj,min cpu  seq  time           pid   act rwbs off+len
> 8,0      0    1   0.000000000    1109   A   WS 14375 + 8 <- (8,1) 14312
>
> ... etc
>
> I'm not sure it gives us enough info; all we see is that there was an IO
> on sdb (from sdb1)
>
> I might suggest
>
> # sysctl -w vm.block_dump=1
>
> to see if you get any info about inodes on sda1 being dirtied.

Like atime/diratime updates?

> (Also, I didn't see any info about sda1 in the posted fstab...)
>
> -Eric

MfG
        Goswin


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 19950 bytes --]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #4 from csights@fastmail.fm  2008-12-14 17:25 -------
http://bugzilla.kernel.org/show_bug.cgi?id=12224

> I think I've seen other reports of this.  Maybe it was you.

Yes, that was me.  :)

> # sysctl -w vm.block_dump=1
>
> to see if you get any info about inodes on sda1 being dirtied.

        I waited until 20:02, then ran:

# sysctl -w vm.block_dump=1; btrace /dev/sda | logger -s

        and switched to a different terminal and ran in the linux kernel
directory 
(on hda1):

# make clean

        I waited until "btrace" indicated activity on sda1, then stopped the
"make 
clean".  If you would like me let it run a few more seconds let me know.
        Below is the output from /var/log/syslog.  The btrace and block_dump
output 
is interleaved.  Lines containing "logger" are from btrace.

Dec 14 20:02:11 localhost kernel: cc1(2825): dirtied inode 550552 (.2823.tmp) 
on hda1
Dec 14 20:02:12 localhost kernel: cc1(2831): dirtied inode 550552 (.2829.tmp) 
on hda1
Dec 14 20:02:12 localhost kernel: cc1(2831): dirtied inode 550552 (.2829.tmp) 
on hda1
Dec 14 20:02:12 localhost kernel: as(2851): dirtied inode 550552 (.2847.tmp) 
on hda1
Dec 14 20:02:12 localhost kernel: as(2857): dirtied inode 550552 (.2853.tmp) 
on hda1
Dec 14 20:02:13 localhost kernel: cc1(2861): dirtied inode 550552 (.2859.tmp) 
on hda1
Dec 14 20:02:13 localhost kernel: cc1(2866): dirtied inode 550552 (.2864.tmp) 
on hda1
Dec 14 20:02:14 localhost kernel: cc1(2870): dirtied inode 550552 (.2868.tmp) 
on hda1
Dec 14 20:02:14 localhost kernel: cc1(2874): dirtied inode 667799 (cc7UOalO.s) 
on hda1
Dec 14 20:02:15 localhost kernel: as(2875): dirtied inode 667800 (cco6Z96S.o) 
on hda1
Dec 14 20:02:15 localhost kernel: collect2(2876): dirtied inode 678207 
(ccDA8hIA.ld) on hda1
Dec 14 20:02:15 localhost kernel: collect2(2876): dirtied inode 678208 
(cc8CSPAJ.le) on hda1
Dec 14 20:02:15 localhost kernel: ld(2877): dirtied inode 550552 (.2872.tmp) 
on hda1
Dec 14 20:02:15 localhost kernel: cc1(2889): dirtied inode 667799 (ccpOcjsE.s) 
on hda1
Dec 14 20:02:15 localhost kernel: as(2890): dirtied inode 667800 (ccswKxcx.o) 
on hda1
Dec 14 20:02:15 localhost kernel: collect2(2891): dirtied inode 678207 
(ccUNFhhm.ld) on hda1
Dec 14 20:02:15 localhost kernel: collect2(2891): dirtied inode 678208 
(ccmKXZiq.le) on hda1
Dec 14 20:02:16 localhost kernel: ld(2892): dirtied inode 550552 (.2887.tmp) 
on hda1
Dec 14 20:02:16 localhost kernel: ld(2892): dirtied inode 550552 (.2887.tmp) 
on hda1
Dec 14 20:02:16 localhost kernel: make(2898): READ block 10191456 on hda1
Dec 14 20:02:16 localhost kernel: make(2898): READ block 10909096 on hda1
Dec 14 20:02:16 localhost kernel: cc1(2901): dirtied inode 667799 (cc6hy8wW.s) 
on hda1
Dec 14 20:02:17 localhost kernel: as(2902): dirtied inode 667800 (ccNZWld0.o) 
on hda1
Dec 14 20:02:17 localhost kernel: collect2(2903): dirtied inode 678207 
(ccQ6Vp5L.ld) on hda1
Dec 14 20:02:17 localhost kernel: collect2(2903): dirtied inode 678208 
(cc4aaKMY.le) on hda1
Dec 14 20:02:17 localhost kernel: ld(2904): dirtied inode 550552 (.2899.tmp) 
on hda1
Dec 14 20:02:17 localhost kernel: cc1(2915): dirtied inode 667799 (ccvjO98E.s) 
on hda1
Dec 14 20:02:17 localhost kernel: as(2916): dirtied inode 667800 (ccGHSTjA.o) 
on hda1
Dec 14 20:02:17 localhost kernel: collect2(2917): dirtied inode 678207 
(cc6n7Vqv.ld) on hda1
Dec 14 20:02:17 localhost kernel: collect2(2917): dirtied inode 678208 
(ccAnMFjC.le) on hda1
Dec 14 20:02:18 localhost kernel: ld(2918): dirtied inode 550552 (.2913.tmp) 
on hda1
Dec 14 20:02:18 localhost kernel: cc1(2927): dirtied inode 667799 (ccgXoLEp.s) 
on hda1
Dec 14 20:02:18 localhost kernel: pdflush(132): WRITE block 378016 on hda1
Dec 14 20:02:18 localhost kernel: pdflush(132): WRITE block 378024 on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16189 (syslog) 
on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16189 (syslog) 
on hda1
Dec 14 20:02:18 localhost kernel: pdflush(132): WRITE block 329472 on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16531 
(kern.log) on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16531 
(kern.log) on hda1
Dec 14 20:02:18 localhost kernel: pdflush(132): WRITE block 329480 on hda1
Dec 14 20:02:18 localhost kernel: pdflush(132): WRITE block 492056 on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16537 (debug) 
on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16537 (debug) 
on hda1
Dec 14 20:02:18 localhost kernel: pdflush(132): WRITE block 1851400 on hda1
Dec 14 20:02:18 localhost kernel: pdflush(132): WRITE block 10993664 on hda1
Dec 14 20:02:18 localhost kernel: as(2928): dirtied inode 667800 (cc0KvDl5.o) 
on hda1
Dec 14 20:02:18 localhost kernel: pdflush(133): WRITE block 378024 on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16189 (syslog) 
on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16189 (syslog) 
on hda1
Dec 14 20:02:18 localhost kernel: pdflush(133): WRITE block 329464 on hda1
Dec 14 20:02:18 localhost kernel: pdflush(133): WRITE block 329472 on hda1
Dec 14 20:02:18 localhost kernel: collect2(2929): dirtied inode 678207 
(ccf6U3lS.ld) on hda1
Dec 14 20:02:18 localhost kernel: collect2(2929): dirtied inode 678208 
(cciOTsnM.le) on hda1
Dec 14 20:02:18 localhost kernel: pdflush(133): WRITE block 329480 on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16531 
(kern.log) on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16531 
(kern.log) on hda1
Dec 14 20:02:18 localhost kernel: pdflush(133): WRITE block 492048 on hda1
Dec 14 20:02:18 localhost kernel: pdflush(133): WRITE block 492056 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 378024 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 329480 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 10752024 on hda1
Dec 14 20:02:18 localhost kernel: ld(2930): dirtied inode 550552 (.2925.tmp) 
on hda1
Dec 14 20:02:18 localhost kernel: gcc(2926): dirtied inode 667799 (?) on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16537 (debug) 
on hda1
Dec 14 20:02:18 localhost kernel: rsyslogd(2827): dirtied inode 16537 (debug) 
on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8384 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8392 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8400 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8408 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8416 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8424 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8432 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8440 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8448 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8456 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8464 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8472 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8480 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8488 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8496 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8504 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8512 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8520 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8528 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8536 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8544 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8552 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8560 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(305): WRITE block 8568 on hda1
Dec 14 20:02:18 localhost kernel: kjournald(1109): WRITE block 12520 on sda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 327960 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 1835024 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 1835048 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 378024 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 378032 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 329480 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 492056 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 492064 on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16189 (syslog) 
on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16189 (syslog) 
on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16189 (syslog) 
on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16531 
(kern.log) on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16531 
(kern.log) on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16531 
(kern.log) on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16537 (debug) 
on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16537 (debug) 
on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16537 (debug) 
on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 378032 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 329480 on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16189 (syslog) 
on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16189 (syslog) 
on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): WRITE block 329488 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 492064 on hda1
Dec 14 20:02:19 localhost logger:   8,0    0        1     0.000000000  1109  A  
WS 12583 + 8 <- (8,1) 12520
Dec 14 20:02:19 localhost logger:   8,0    0        2     0.000006426  1109  Q  
WS 12583 + 8 [kjournald]
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8576 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8584 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8592 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8600 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8608 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8616 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8624 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8632 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8640 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8648 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8656 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8664 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8672 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8680 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8688 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8696 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8704 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8712 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8720 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8728 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8736 on hda1
Dec 14 20:02:19 localhost logger:   8,0    0        3     0.000039670  1109  G  
WS 12583 + 8 [kjournald]
Dec 14 20:02:19 localhost logger:   8,0    0        4     0.000061461  1109  P  
N [kjournald]
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16535 
(user.log) on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16535 
(user.log) on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16535 
(user.log) on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16539 
(messages) on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16539 
(messages) on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16539 
(messages) on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8744 on hda1
Dec 14 20:02:19 localhost logger:   8,0    0        5     0.000071797  1109  I  
W 12583 + 8 [kjournald]
Dec 14 20:02:19 localhost logger:   8,0    0        6     0.000272381  1109  D  
W 12583 + 8 [kjournald]
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 329488 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 378032 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 492064 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 328464 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 329208 on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16531 
(kern.log) on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16531 
(kern.log) on hda1
Dec 14 20:02:19 localhost logger:   8,0    0        7     0.000381893  1109  U  
N [kjournald] 1
Dec 14 20:02:19 localhost logger:   8,0    0        8     0.028911225     3  C  
W 12583 + 8 [0]
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8752 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8760 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8768 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8776 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 492064 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 492072 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 378032 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 329488 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 378040 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 328464 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 329208 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 329496 on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16537 (debug) 
on hda1
Dec 14 20:02:19 localhost kernel: rsyslogd(2827): dirtied inode 16537 (debug) 
on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8784 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8792 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8800 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8808 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8816 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8824 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8832 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8840 on hda1
Dec 14 20:02:19 localhost kernel: kjournald(305): WRITE block 8848 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 0 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 327960 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 376984 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 491760 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 8912896 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 8912904 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 8913064 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 8913184 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 8994816 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 10747904 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 10747912 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 10747920 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 10749224 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 10749384 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 10751824 on hda1
Dec 14 20:02:19 localhost kernel: pdflush(133): WRITE block 10752520 on hda1
Dec 14 20:02:19 localhost kernel: cc1(2945): dirtied inode 667799 (ccvt36ES.s) 
on hda1
Dec 14 20:02:20 localhost kernel: as(2946): dirtied inode 667800 (ccM4g5ZY.o) 
on hda1
Dec 14 20:02:20 localhost kernel: collect2(2947): dirtied inode 678207 
(ccjYE2NG.ld) on hda1
Dec 14 20:02:20 localhost kernel: collect2(2947): dirtied inode 678208 
(ccEzo3JR.le) on hda1
Dec 14 20:02:20 localhost kernel: ld(2948): dirtied inode 550552 (.2943.tmp) 
on hda1
Dec 14 20:02:20 localhost kernel: cc1(2957): dirtied inode 667799 (cc6ZPFDy.s) 
on hda1
Dec 14 20:02:20 localhost kernel: as(2958): dirtied inode 667800 (ccAj2mWp.o) 
on hda1
Dec 14 20:02:20 localhost kernel: collect2(2959): dirtied inode 678207 
(ccpJQzdj.ld) on hda1
Dec 14 20:02:20 localhost kernel: collect2(2959): dirtied inode 678208 
(ccU1Uk0l.le) on hda1
Dec 14 20:02:20 localhost kernel: ld(2960): dirtied inode 550552 (.2955.tmp) 
on hda1
Dec 14 20:02:21 localhost kernel: cc1(2969): dirtied inode 667799 (cc7lUzdi.s) 
on hda1
Dec 14 20:02:21 localhost kernel: as(2970): dirtied inode 667800 (cc2KnxYS.o) 
on hda1
Dec 14 20:02:21 localhost kernel: collect2(2971): dirtied inode 678207 
(ccYyMJRv.ld) on hda1
Dec 14 20:02:21 localhost kernel: collect2(2971): dirtied inode 678208 
(cc0coqFi.le) on hda1
Dec 14 20:02:21 localhost kernel: ld(2972): dirtied inode 550552 (.2967.tmp) 
on hda1
Dec 14 20:02:22 localhost kernel: cc1(2981): dirtied inode 667799 (ccnYuG29.s) 
on hda1
Dec 14 20:02:22 localhost kernel: as(2982): dirtied inode 667800 (ccLRJ3tt.o) 
on hda1
Dec 14 20:02:22 localhost kernel: collect2(2985): dirtied inode 678207 
(cc39KpHM.ld) on hda1
Dec 14 20:02:22 localhost kernel: collect2(2985): dirtied inode 678208 
(ccKCIBak.le) on hda1
Dec 14 20:02:22 localhost kernel: ld(2986): dirtied inode 550552 (.2979.tmp) 
on hda1



>
> (Also, I didn't see any info about sda1 in the posted fstab...)

Oops!  copied the "mount" output when sda wasn't mounted.  Here is the output 
of "mount" current when the above output was generated:

/dev/hda1 on / type ext3 (rw,noatime,errors=remount-ro,commit=1209600)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sda1 on /mnt/sda type ext3 (rw,noatime,commit=1209600)
debugfs on /sys/kernel/debug type debugfs (rw)


C.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #5 from tytso@mit.edu  2008-12-14 18:47 -------
>     Activity on one partition (hda1) causes kjournald to also write
> to another partition (sda1).  This in turn causes the harddrive
> which contains sda1 to spinup or not spindown.  I've activated
> laptop-mode using laptop-mode-tools. hda1 and sda1 are both
> formatted with ext3.  On unaffected kernels (e.g. 2.6.27.5) btrace
> produces no output.  On affected kernels (e.g. 2.6.27.6, 2.6.27-rc7)
> btrace produces output as below.

I've looked at the changes between 2.6.27.5 and 2.6.27.6, and I don't
see anything that might explain such a regression.  Indeed, there's
only one patch between .5 and .6 that even touches ext3, and the patch
seems pretty innocent.

Is /dev/sda1 even mounted?  It doesn't included up in your /etc/mtab
listing.

The only thing I can suggest is to try 2.6.27.6 with the only patch
that touches ext3 reverted (i.e., unapply it with patch -R).  If the
problem still shows up, I would suggest getting the linux-2.6.27.y
tree from:

git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.27.y.git

And then doing a git bisection search to try to find the guilty
commit.

Regards,

                                        - Ted
commit a0b8bfb34743b6e6c2bb06ad5a270590d90270f7
Author: Arthur Jones <ajones@riverbed.com>
Date:   Fri Nov 7 00:05:17 2008 +0000

    ext3: wait on all pending commits in ext3_sync_fs

    commit c87591b719737b4e91eb1a9fa8fd55a4ff1886d6 upstream

    In ext3_sync_fs, we only wait for a commit to finish if we started it, but
    there may be one already in progress which will not be synced.

    In the case of a data=ordered umount with pending long symlinks which are
    delayed due to a long list of other I/O on the backing block device, this
    causes the buffer associated with the long symlinks to not be moved to the
    inode dirty list in the second phase of fsync_super.  Then, before they
    can be dirtied again, kjournald exits, seeing the UMOUNT flag and the
    dirty pages are never written to the backing block device, causing long
    symlink corruption and exposing new or previously freed block data to
    userspace.

    This can be reproduced with a script created
    by Eric Sandeen <sandeen@redhat.com>:

        #!/bin/bash

        umount /mnt/test2
        mount /dev/sdb4 /mnt/test2
        rm -f /mnt/test2/*
        dd if=/dev/zero of=/mnt/test2/bigfile bs=1M count=512
        touch
       
/mnt/test2/thisisveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryverylongfilename
        ln -s
       
/mnt/test2/thisisveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryverylongfilename
        /mnt/test2/link
        umount /mnt/test2
        mount /dev/sdb4 /mnt/test2
        ls /mnt/test2/
        umount /mnt/test2

    To ensure all commits are synced, we flush all journal commits now when
    sync_fs'ing ext3.

    Signed-off-by: Arthur Jones <ajones@riverbed.com>
    Cc: Eric Sandeen <sandeen@redhat.com>
    Cc: Theodore Ts'o <tytso@mit.edu>
    Cc: <linux-ext4@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

diff --git a/fs/ext3/super.c b/fs/ext3/super.c
index f38a5af..810bf7c 100644
--- a/fs/ext3/super.c
+++ b/fs/ext3/super.c
@@ -2365,13 +2365,12 @@ static void ext3_write_super (struct super_block * sb)

 static int ext3_sync_fs(struct super_block *sb, int wait)
 {
-       tid_t target;

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #6 from sandeen@redhat.com  2008-12-14 21:07 -------
Dec 14 20:02:18 localhost kernel: kjournald(1109): WRITE block 12520 on sda1

is the first thing I see in the log above, with no indication of anything else
on sda1 before that.

If you let the system just sit idle, do you get sda1 hits from the sysctl
and/or blktrace?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 8345 bytes --]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #7 from csights@fastmail.fm  2008-12-15 13:49 -------
Hi,
        Following Ted's suggestion, I began with 2.6.27.6 and then reversed the
patch 
for commit a0b8bfb34743b6e6c2bb06ad5a270590d90270f7.  This "fixed" the 
problem such that activity on hda1 no longer caused kjournald to write to 
sda1.




> Is /dev/sda1 even mounted?  It doesn't included up in your /etc/mtab
> listing.

Just to confirm, I posted the wrong mtab previously.  sda1 is mounted during 
my tests.  This is how it looks:

/dev/hda1 on / type ext3 (rw,noatime,errors=remount-ro,commit=1209600)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sda1 on /mnt/sda type ext3 (rw,noatime,commit=1209600)
debugfs on /sys/kernel/debug type debugfs (rw)



> ------- Comment #6 from sandeen@redhat.com  2008-12-14 21:07 -------
>
> Dec 14 20:02:18 localhost kernel: kjournald(1109): WRITE block 12520 on
> sda1
>
> is the first thing I see in the log above, with no indication of anything
> else on sda1 before that.

        I only copied the lines from the log during the short compile "test".
        Here is another test which is a little more clean, using 2.6.27.6
(without 
the commit mentioned above reverted). 

        First unmount, then remount /dev/sda1 to flush the filesystem caches:
# umount /dev/sda1; mount /mnt/sda; btrace /dev/sda | logger -s

        then switch to another console and restart laptop mode (to change the
commit 
time on sda1):
#/etc/init.d/laptop-mode restart

        Finally generate some activity on hda1.  ("make menuconfig")
        The following is syslog from the mount of /dev/sda1 (on /mnt/sda) until
"make 
clean" finished:

Dec 15 16:34:48 localhost kernel: kjournald starting.  Commit interval 5 
seconds
Dec 15 16:34:48 localhost kernel: EXT3 FS on sda1, internal journal
Dec 15 16:34:48 localhost kernel: EXT3-fs: mounted filesystem with ordered 
data mode.
Dec 15 16:34:54 localhost kernel: hda: cache flushes not supported
Dec 15 16:34:56 localhost kernel: hda: cache flushes not supported
Dec 15 16:34:57 localhost logger:   8,0    0        1     0.000000000  4140  A  
WS 12423 + 8 <- (8,1) 12360
Dec 15 16:34:57 localhost logger:   8,0    0        2     0.000006146  4140  Q  
WS 12423 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0        3     0.000114819  4140  G  
WS 12423 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0        4     0.000143314  4140  P  
N [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0        5     0.000159797  4140  I  
W 12423 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0        6     0.000348089  4140  D  
W 12423 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0        7     0.000463746  4140  U  
N [kjournald] 1
Dec 15 16:34:57 localhost logger:   8,0    0        8     0.010034518     3  C  
W 12423 + 8 [0]
Dec 15 16:34:57 localhost logger:   8,0    0        9     0.010557490  4140  A  
WS 12431 + 8 <- (8,1) 12368
Dec 15 16:34:57 localhost logger:   8,0    0       10     0.010563916  4140  Q  
WS 12431 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0       11     0.010589617  4140  G  
WS 12431 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0       12     0.010606658  4140  P  
N [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0       13     0.010616157  4140  I  
W 12431 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0       14     0.010749414  4140  D  
W 12431 + 8 [kjournald]
Dec 15 16:34:57 localhost logger:   8,0    0       15     0.010836297  4140  U  
N [kjournald] 1
Dec 15 16:34:57 localhost logger:   8,0    0       16     0.021000161     3  C  
W 12431 + 8 [0]
Dec 15 16:34:59 localhost logger:   8,0    0       17     2.350235673  4140  A  
WS 12439 + 8 <- (8,1) 12376
Dec 15 16:34:59 localhost logger:   8,0    0       18     2.350244612  4140  Q  
WS 12439 + 8 [kjournald]
Dec 15 16:34:59 localhost logger:   8,0    0       19     2.350278974  4140  G  
WS 12439 + 8 [kjournald]
Dec 15 16:34:59 localhost logger:   8,0    0       20     2.350301044  4140  P  
N [kjournald]
Dec 15 16:34:59 localhost logger:   8,0    0       21     2.350316130  4140  I  
W 12439 + 8 [kjournald]
Dec 15 16:34:59 localhost logger:   8,0    0       22     2.350568397  4140  D  
W 12439 + 8 [kjournald]
Dec 15 16:34:59 localhost logger:   8,0    0       23     2.350684333  4140  U  
N [kjournald] 1
Dec 15 16:34:59 localhost logger:   8,0    0       24     2.360609899     3  C  
W 12439 + 8 [0]
Dec 15 16:35:52 localhost logger:   8,0    0       25    55.121164875  4140  A  
WS 12447 + 8 <- (8,1) 12384
Dec 15 16:35:52 localhost logger:   8,0    0       26    55.121172697  4140  Q  
WS 12447 + 8 [kjournald]
Dec 15 16:35:52 localhost logger:   8,0    0       27    55.121203707  4140  G  
WS 12447 + 8 [kjournald]
Dec 15 16:35:52 localhost logger:   8,0    0       28    55.121221865  4140  P  
N [kjournald]
Dec 15 16:35:52 localhost logger:   8,0    0       29    55.121232202  4140  I  
W 12447 + 8 [kjournald]
Dec 15 16:35:52 localhost logger:   8,0    0       30    55.121458767  4140  D  
W 12447 + 8 [kjournald]
Dec 15 16:35:52 localhost logger:   8,0    0       31    55.121571910  4140  U  
N [kjournald] 1
Dec 15 16:35:52 localhost logger:   8,0    0       32    55.131824892     3  C  
W 12447 + 8 [0]
Dec 15 16:35:57 localhost logger:   8,0    0       33    59.696845185  4140  A  
WS 12455 + 8 <- (8,1) 12392
Dec 15 16:35:57 localhost logger:   8,0    0       34    59.696853566  4140  Q  
WS 12455 + 8 [kjournald]
Dec 15 16:35:57 localhost logger:   8,0    0       35    59.696888486  4140  G  
WS 12455 + 8 [kjournald]
Dec 15 16:35:57 localhost logger:   8,0    0       36    59.696908880  4140  P  
N [kjournald]
Dec 15 16:35:57 localhost logger:   8,0    0       37    59.696920334  4140  I  
W 12455 + 8 [kjournald]
Dec 15 16:35:57 localhost logger:   8,0    0       38    59.697142709  4140  D  
W 12455 + 8 [kjournald]
Dec 15 16:35:57 localhost logger:   8,0    0       39    59.697256410  4140  U  
N [kjournald] 1
Dec 15 16:35:57 localhost logger:   8,0    0       40    59.707057938     3  C  
W 12455 + 8 [0]
Dec 15 16:36:04 localhost logger:   8,0    0       41    67.363585697  4140  A  
WS 12463 + 8 <- (8,1) 12400
Dec 15 16:36:04 localhost logger:   8,0    0       42    67.363595196  4140  Q  
WS 12463 + 8 [kjournald]
Dec 15 16:36:04 localhost logger:   8,0    0       43    67.363627043  4140  G  
WS 12463 + 8 [kjournald]
Dec 15 16:36:04 localhost logger:   8,0    0       44    67.363646319  4140  P  
N [kjournald]
Dec 15 16:36:04 localhost logger:   8,0    0       45    67.363657215  4140  I  
W 12463 + 8 [kjournald]
Dec 15 16:36:04 localhost logger:   8,0    0       46    67.363869253  4140  D  
W 12463 + 8 [kjournald]
Dec 15 16:36:04 localhost logger:   8,0    0       47    67.363980161  4140  U  
N [kjournald] 1
Dec 15 16:36:04 localhost logger:   8,0    0       48    67.373786717     3  C  
W 12463 + 8 [0]

>
> If you let the system just sit idle, do you get sda1 hits from the sysctl
> and/or blktrace?

        If I let the system sit idle using 2.6.27.5 (the last unaffected 
version) 'btrace /dev/sda' shows no activity, even if there is activity on 
hda1.
        If I let the system sit idle using 2.6.27.6 (the first affected 
version) 'btrace /dev/sda' shows kjournald doing something with sda1 if there 
is activity on hda1.  If hda1 is inactive then there is also no activity on 
sda1.

Thanks!
        C.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #8 from csights@fastmail.fm  2008-12-16 12:35 -------
http://bugzilla.kernel.org/show_bug.cgi?id=12224

Hi all,
        You might be interested to know that this problem can be reproduced by
using 
an ext3 image file mounted loopback.  (I.e. You don't need a separate 
harddrive or partition in order to reproduce the problem.)

C.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #9 from sandeen@redhat.com  2008-12-16 14:01 -------
Are the laptop-mode tools doing remounts behind your back?

The only way I see this is if I do "mount -o remount /"; then I see kjournald
activity on other ext3 filesystems.  I'll dig into that.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #10 from csights@fastmail.fm  2008-12-16 18:30 -------
On Tuesday 16 December 2008 17:01:27 bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12224


> ------- Comment #9 from sandeen@redhat.com  2008-12-16 14:01 -------
> Are the laptop-mode tools doing remounts behind your back?
>
> The only way I see this is if I do "mount -o remount /"; then I see
> kjournald activity on other ext3 filesystems.  I'll dig into that.

I don't think so: I was able to reproduce this bug using an ext3 loopback 
mounted file.  laptop-mode-tools does not touch loopback devices as far as I 
can tell.  Here is my laptop-mode.conf:

> #
> # The drives that laptop mode controls.
> # Separate them by a space, e.g. HD="/dev/hda /dev/hdb". The default is a
> # wildcard, which will get you all your IDE and SCSI/SATA drives.
> #
> HD="/dev/[hs]d[abcdefgh]"

        And here is the loopback mount:

/tmp/ext3Image on /mnt/loop type ext3 
(rw,noatime,loop=/dev/loop/0,commit=1209600)

        (I set the commit=1209600 and noatime by hand on the loopback mounted
ext3 
image file.)

        Since I'm not a kernel hacker, I don't know how the code is structured.
 It 
feels like the kernel commit code is not fully separated by device (or 
partition). When the active partition's journal is "synced" it triggers 
activity on other partitions, even if the other partitions aren't active.

C.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224


csights@fastmail.fm changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|                            |11808
              nThis|                            |




-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #11 from rjw@sisk.pl  2008-12-18 12:41 -------
Handled-By : Eric Sandeen <sandeen@redhat.com>
Notify-Also : Theodore Tso <tytso@mit.edu>
First-Bad-Commit : c87591b719737b4e91eb1a9fa8fd55a4ff1886d6


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #12 from sandeen@redhat.com  2008-12-18 15:02 -------
In a nutshell, with laptop mode on, we go down this path:

static void laptop_timer_fn(unsigned long unused)
{
        pdflush_operation(laptop_flush, 0);
}

static void laptop_flush(unsigned long unused)
{
        sys_sync();
}

which gets us to the new 

static int ext3_sync_fs(struct super_block *sb, int wait)
{
        sb->s_dirt = 0;
        if (wait)
                ext3_force_commit(sb);
...

which is then committing empty transactions.  Seems like we should be smart
enough to skip committing transactions w/ nothing in them...?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.27.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
Date		: 2008-12-14 11:39 (7 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

[Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.27.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights@fastmail.fm>
Date		: 2008-12-14 11:39 (7 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen@redhat.com>

[Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
Date		: 2008-12-14 11:39 (29 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

[Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights@fastmail.fm>
Date		: 2008-12-14 11:39 (29 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen@redhat.com>

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #13 from sandeen@redhat.com  2009-01-13 14:17 -------
Care to test the patch at http://patchwork.ozlabs.org/patch/14755/ ?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #14 from csights@fastmail.fm  2009-01-14 12:35 -------
http://bugzilla.kernel.org/show_bug.cgi?id=12224

>
>
>
> ------- Comment #13 from sandeen@redhat.com  2009-01-13 14:17 -------
> Care to test the patch at http://patchwork.ozlabs.org/patch/14755/ ?

Sure!
        I manually patched 2.6.28.  btrace showed lots of output as above. 
However, 
I didn't wait to see if the observed activity affected the drive spinup/down 
b/c I thought maybe patching 2.6.28 was not proper.
        I don't know how to git the right kernel sources to patch.  Could you
prepare 
a patch against an RC (or in some other way hold my hand)?  Or I could wait 
for some RC which includes the patch already.

Sorry for my gimpiness,
        C.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #15 from sandeen@redhat.com  2009-01-14 12:44 -------
Sure, I'll gladly attach a patch.  You tell me a specific kernel version, I'll
attach a patch.  :)  2.6.28?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #16 from csights@fastmail.fm  2009-01-14 14:37 -------
http://bugzilla.kernel.org/show_bug.cgi?id=12224


> ------- Comment #15 from sandeen@redhat.com  2009-01-14 12:44 -------
> Sure, I'll gladly attach a patch.  You tell me a specific kernel version,
> I'll attach a patch.  :)  2.6.28?


Yes, please! :)


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #17 from sandeen@redhat.com  2009-01-14 14:58 -------
Created an attachment (id=19805)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=19805&action=view)
patch reverting old change & adding Jan's proposed fix

Here you go!


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #18 from csights@fastmail.fm  2009-01-14 17:09 -------
http://bugzilla.kernel.org/show_bug.cgi?id=12224

        I applied the patch to 2.6.28....
        However there is still activity on the inactive partition (sda) if
there is 
activity on the other partition (hda).
        I've pasted the current output of 'btrace /dev/sda' in case it has
changed 
from before.



Jan 14 19:51:29 localhost logger:   8,0    0        1     0.000000000  1138  A  
WS 12599 + 8 <- (8,1) 12536
Jan 14 19:51:29 localhost logger:   8,0    0        2     0.000006426  1138  Q  
WS 12599 + 8 [kjournald]
Jan 14 19:51:29 localhost logger:   8,0    0        3     0.000044978  1138  G  
WS 12599 + 8 [kjournald]
Jan 14 19:51:29 localhost logger:   8,0    0        4     0.000066489  1138  P  
N [kjournald]
Jan 14 19:51:29 localhost logger:   8,0    0        5     0.000081295  1138  I  
W 12599 + 8 [kjournald]
Jan 14 19:51:29 localhost logger:   8,0    0        6     0.000300597  1138  D  
W 12599 + 8 [kjournald]
Jan 14 19:51:29 localhost logger:   8,0    0        7     0.000492521  1138  U  
N [kjournald] 1
Jan 14 19:51:29 localhost logger:   8,0    0        8     0.041120321     3  C  
W 12599 + 8 [0]
Jan 14 19:51:51 localhost logger:   8,0    0        9    21.646946652  1138  A  
WS 12607 + 8 <- (8,1) 12544
Jan 14 19:51:51 localhost logger:   8,0    0       10    21.646955591  1138  Q  
WS 12607 + 8 [kjournald]
Jan 14 19:51:51 localhost logger:   8,0    0       11    21.646991071  1138  G  
WS 12607 + 8 [kjournald]
Jan 14 19:51:51 localhost logger:   8,0    0       12    21.647011464  1138  P  
N [kjournald]
Jan 14 19:51:51 localhost logger:   8,0    0       13    21.647027109  1138  I  
W 12607 + 8 [kjournald]
Jan 14 19:51:51 localhost logger:   8,0    0       14    21.647229369  1138  D  
W 12607 + 8 [kjournald]
Jan 14 19:51:51 localhost logger:   8,0    0       15    21.647339439  1138  U  
N [kjournald] 1
Jan 14 19:51:51 localhost logger:   8,0    0       16    21.688494962     3  C  
W 12607 + 8 [0]
Jan 14 19:51:55 localhost logger:   8,0    0       17    26.471770149  1138  A  
WS 12615 + 8 <- (8,1) 12552
Jan 14 19:51:55 localhost logger:   8,0    0       18    26.471779368  1138  Q  
WS 12615 + 8 [kjournald]
Jan 14 19:51:55 localhost logger:   8,0    0       19    26.471812613  1138  G  
WS 12615 + 8 [kjournald]
Jan 14 19:51:55 localhost logger:   8,0    0       20    26.471831889  1138  P  
N [kjournald]
Jan 14 19:51:55 localhost logger:   8,0    0       21    26.471846136  1138  I  
W 12615 + 8 [kjournald]
Jan 14 19:51:55 localhost logger:   8,0    0       22    26.472050632  1138  D  
W 12615 + 8 [kjournald]
Jan 14 19:51:55 localhost logger:   8,0    0       23    26.472162099  1138  U  
N [kjournald] 1
Jan 14 19:51:55 localhost logger:   8,0    0       24    26.481685099     3  C  
W 12615 + 8 [0]


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #19 from csights@fastmail.fm  2009-01-15 07:48 -------
http://bugzilla.kernel.org/show_bug.cgi?id=12224

> ------- Comment #17 from sandeen@redhat.com  2009-01-14 14:58 -------
> Created an attachment (id=19805)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=19805&action=view)
>  --> (http://bugzilla.kernel.org/attachment.cgi?id=19805&action=view)
> patch reverting old change & adding Jan's proposed fix

Does this patch "revert the old change"?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224


sandeen@redhat.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #19805|0                           |1
        is obsolete|                            |




------- Comment #20 from sandeen@redhat.com  2009-01-15 08:12 -------
Created an attachment (id=19814)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=19814&action=view)
Updated patch

sorry, didn't drive quilt right last time!


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224





------- Comment #21 from csights@fastmail.fm  2009-01-15 13:03 -------
http://bugzilla.kernel.org/show_bug.cgi?id=12224

> ------- Comment #20 from sandeen@redhat.com  2009-01-15 08:12 -------
> Created an attachment (id=19814)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=19814&action=view)
>  --> (http://bugzilla.kernel.org/attachment.cgi?id=19814&action=view)
> Updated patch

With the latest patch the problem seems to be fixed.  btrace /dev/sda output 
nothing after several minutes of activity on hda.

Thanks!
        C.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
Date		: 2008-12-14 11:39 (37 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

[Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights@fastmail.fm>
Date		: 2008-12-14 11:39 (37 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen@redhat.com>

Re: [Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Theodore Tso]

On Mon, Jan 19, 2009 at 10:45:38PM +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
> Subject		: journal activity on inactive partition causes inactive harddrive spinup
> Submitter	: C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
> Date		: 2008-12-14 11:39 (37 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
> Handled-By	: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> 

Yes, this should still be listed.  We have a proposed patch that
should fix this, but it still needs to be finalized and tested.

              	   	     	      - Ted

Re: [Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Theodore Tso]

On Mon, Jan 19, 2009 at 10:45:38PM +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
> Subject		: journal activity on inactive partition causes inactive harddrive spinup
> Submitter	: C Sights <csights@fastmail.fm>
> Date		: 2008-12-14 11:39 (37 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
> Handled-By	: Eric Sandeen <sandeen@redhat.com>
> 

Yes, this should still be listed.  We have a proposed patch that
should fix this, but it still needs to be finalized and tested.

              	   	     	      - Ted

WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Philipp Matthias Hahn]

Hello!

Somewhere between 2.6.26 and 2.6.27 WOL stopped working on my MS-7350
motherboard with an "nVidia Corporation MCP51 Ethernet Controller (rev a3)".
	"etherwake 00:19:db:f2:e1:35" did not work
	"etherwake 35:e1:f2:db:19:00" did work
Since I did a BIOS update during the same time window I (wrongly) put
the fault on the BIOS. (See /sys/class/dmi/id/modalias for yourself:
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd07/29/2008:svnMSI:pnMS-7350:pvr1.0:rvnMSI:rnMS-7350:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
)

Today I finally found the time to test various old versions of
"drivers/net/forcedeth.c" and also did a "git-bisect v2.6.26 v2.6.27"
which lead to the following culprit:

f55c21fd9a92a444e55ad1ca4e4732d56661bf2e is first bad commit
commit f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
Author: Yinghai Lu <yhlu.kernel@gmail.com>
Date:   Sat Sep 13 13:10:31 2008 -0700

    forcedeth: call restore mac addr in nv_shutdown path
    
    after
    
    | commit f735a2a1a4f2a0f5cd823ce323e82675990469e2
    | Author: Tobias Diedrich <ranma+kernel@tdiedrich.de>
    | Date:   Sun May 18 15:02:37 2008 +0200
    |
    |    [netdrvr] forcedeth: setup wake-on-lan before shutting down
    |
    |    When hibernating in 'shutdown' mode, after saving the image the suspend hook
    |    is not called again.
    |    However, if the device is in promiscous mode, wake-on-lan will not work.
    |    This adds a shutdown hook to setup wake-on-lan before the final shutdown.
    |
    |    Signed-off-by: Tobias Diedrich <ranma+kernel@tdiedrich.de>
    |    Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
    
    my servers with nvidia ck804 and mcp55 will reverse mac address with kexec.
    
    it turns out that we need to restore the mac addr in nv_shutdown().
    
    [akpm@linux-foundation.org: fix typo in printk]
    Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
    Cc: Tobias Diedrich <ranma+kernel@tdiedrich.de>
    Cc: Ayaz Abdulla <aabdulla@nvidia.com>
    Cc: Jeff Garzik <jeff@garzik.org>
    Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Jeff Garzik <jgarzik@redhat.com>

diff --git a/drivers/net/forcedeth.c b/drivers/net/forcedeth.c
index 0b6ecef..eeb55ed 100644
--- a/drivers/net/forcedeth.c
+++ b/drivers/net/forcedeth.c
@@ -5643,6 +5643,7 @@ static int __devinit nv_probe(struct pci_dev *pci_dev, const struct pci_device_i
 		dev->dev_addr[4] = (np->orig_mac[0] >>  8) & 0xff;
 		dev->dev_addr[5] = (np->orig_mac[0] >>  0) & 0xff;
 		writel(txreg|NVREG_TRANSMITPOLL_MAC_ADDR_REV, base + NvRegTransmitPoll);
+		printk(KERN_DEBUG "nv_probe: set workaround bit for reversed mac addr\n");
 	}
 	memcpy(dev->perm_addr, dev->dev_addr, dev->addr_len);
 
@@ -5890,14 +5891,12 @@ static void nv_restore_phy(struct net_device *dev)
 	}
 }
 
-static void __devexit nv_remove(struct pci_dev *pci_dev)
+static void nv_restore_mac_addr(struct pci_dev *pci_dev)
 {
 	struct net_device *dev = pci_get_drvdata(pci_dev);
 	struct fe_priv *np = netdev_priv(dev);
 	u8 __iomem *base = get_hwbase(dev);
 
-	unregister_netdev(dev);
-
 	/* special op: write back the misordered MAC address - otherwise
 	 * the next nv_probe would see a wrong address.
 	 */
@@ -5905,6 +5904,15 @@ static void __devexit nv_remove(struct pci_dev *pci_dev)
 	writel(np->orig_mac[1], base + NvRegMacAddrB);
 	writel(readl(base + NvRegTransmitPoll) & ~NVREG_TRANSMITPOLL_MAC_ADDR_REV,
 	       base + NvRegTransmitPoll);
+}
+
+static void __devexit nv_remove(struct pci_dev *pci_dev)
+{
+	struct net_device *dev = pci_get_drvdata(pci_dev);
+
+	unregister_netdev(dev);
+
+	nv_restore_mac_addr(pci_dev);
 
 	/* restore any phy related changes */
 	nv_restore_phy(dev);
@@ -5975,6 +5983,8 @@ static void nv_shutdown(struct pci_dev *pdev)
 	if (netif_running(dev))
 		nv_close(dev);
 
+	nv_restore_mac_addr(pdev);
+
 	pci_disable_device(pdev);
 	if (system_state == SYSTEM_POWER_OFF) {
 		if (pci_enable_wake(pdev, PCI_D3cold, np->wolenabled))

:040000 040000 8c603aa1f71b79f3f4a94bef066a830a249c8d2a e85d84f3c509421a33fd4b71bacddeb4b9fbe896 M drivers

Reverting that patch on top of drivers/net/forcedeth.c from 2.6.28.2
resolves the problem for me.
I DON'T use kexec, just simple poweroff.

BYtE
Philipp
-- 
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Yinghai Lu]

On Wed, Jan 28, 2009 at 10:31 PM, Philipp Matthias Hahn
<pmhahn@titan.lahn.de> wrote:
> Hello!
>
> Somewhere between 2.6.26 and 2.6.27 WOL stopped working on my MS-7350
> motherboard with an "nVidia Corporation MCP51 Ethernet Controller (rev a3)".
>        "etherwake 00:19:db:f2:e1:35" did not work
>        "etherwake 35:e1:f2:db:19:00" did work
> Since I did a BIOS update during the same time window I (wrongly) put
> the fault on the BIOS. (See /sys/class/dmi/id/modalias for yourself:
> dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd07/29/2008:svnMSI:pnMS-7350:pvr1.0:rvnMSI:rnMS-7350:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
> )
>
> Today I finally found the time to test various old versions of
> "drivers/net/forcedeth.c" and also did a "git-bisect v2.6.26 v2.6.27"
> which lead to the following culprit:
>

can not find the reason why the WOL doesn't work...

please post
1. boot log for just after AC is pluged-in... ===> you should have
"nv_probe: set workaround bit for reversed mac addr"
2. and boot log after boot from WOL...==> you have have "nv_probe: set
workaround bit for reversed mac addr" too.

YH

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Yinghai Lu]

[-- Attachment #1: Type: text/plain, Size: 567 bytes --]

On Thu, Jan 29, 2009 at 10:53 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> On Wed, Jan 28, 2009 at 10:31 PM, Philipp Matthias Hahn
> <pmhahn@titan.lahn.de> wrote:
>> Hello!
>>
>> Somewhere between 2.6.26 and 2.6.27 WOL stopped working on my MS-7350
>> motherboard with an "nVidia Corporation MCP51 Ethernet Controller (rev a3)".
>>        "etherwake 00:19:db:f2:e1:35" did not work
>>        "etherwake 35:e1:f2:db:19:00" did work

looks like your BIOS, already reverse the MAC addr...

please check attached ... Rafael, wonder if will break suspend/resume...

YH

[-- Attachment #2: restore_mac_orig.patch --]
[-- Type: text/x-patch, Size: 4209 bytes --]

[PATCH] forcedeth: keep mac addr to orignal

Impact: fix mac reverse for wol

some BIOS may already reverse that, try to don't touch the mac addr, so don't
confuse the WOL

Signed-off-by: Yinghai Lu <yinghai@kernel.org>

---
 drivers/net/forcedeth.c |   50 +++++++++++++++++++++++++++++-------------------
 1 file changed, 31 insertions(+), 19 deletions(-)

Index: linux-2.6/drivers/net/forcedeth.c
===================================================================
--- linux-2.6.orig/drivers/net/forcedeth.c
+++ linux-2.6/drivers/net/forcedeth.c
@@ -748,6 +748,8 @@ struct fe_priv {
 	/* General data: RO fields */
 	dma_addr_t ring_addr;
 	struct pci_dev *pci_dev;
+	/* wonder if bios already reverse that */
+	int orig_mac_status;
 	u32 orig_mac[2];
 	u32 irqmask;
 	u32 desc_ver;
@@ -5639,14 +5641,17 @@ static int __devinit nv_probe(struct pci
 	/* check the workaround bit for correct mac address order */
 	txreg = readl(base + NvRegTransmitPoll);
 	if (id->driver_data & DEV_HAS_CORRECT_MACADDR) {
-		/* mac address is already in correct order */
-		dev->dev_addr[0] = (np->orig_mac[0] >>  0) & 0xff;
-		dev->dev_addr[1] = (np->orig_mac[0] >>  8) & 0xff;
-		dev->dev_addr[2] = (np->orig_mac[0] >> 16) & 0xff;
-		dev->dev_addr[3] = (np->orig_mac[0] >> 24) & 0xff;
-		dev->dev_addr[4] = (np->orig_mac[1] >>  0) & 0xff;
-		dev->dev_addr[5] = (np->orig_mac[1] >>  8) & 0xff;
+		np->orig_mac_status = -1;
 	} else if (txreg & NVREG_TRANSMITPOLL_MAC_ADDR_REV) {
+		np->orig_mac_status = 1;
+		printk(KERN_DEBUG "nv_probe: workaround bit for reversed mac addr is set\n");
+	} else {
+		np->orig_mac_status = 0;
+		writel(txreg|NVREG_TRANSMITPOLL_MAC_ADDR_REV,
+			 base + NvRegTransmitPoll);
+		printk(KERN_DEBUG "nv_probe: set workaround bit for reversed mac addr\n");
+	}
+	if (np->orig_mac_status) {
 		/* mac address is already in correct order */
 		dev->dev_addr[0] = (np->orig_mac[0] >>  0) & 0xff;
 		dev->dev_addr[1] = (np->orig_mac[0] >>  8) & 0xff;
@@ -5654,14 +5659,6 @@ static int __devinit nv_probe(struct pci
 		dev->dev_addr[3] = (np->orig_mac[0] >> 24) & 0xff;
 		dev->dev_addr[4] = (np->orig_mac[1] >>  0) & 0xff;
 		dev->dev_addr[5] = (np->orig_mac[1] >>  8) & 0xff;
-		/*
-		 * Set orig mac address back to the reversed version.
-		 * This flag will be cleared during low power transition.
-		 * Therefore, we should always put back the reversed address.
-		 */
-		np->orig_mac[0] = (dev->dev_addr[5] << 0) + (dev->dev_addr[4] << 8) +
-			(dev->dev_addr[3] << 16) + (dev->dev_addr[2] << 24);
-		np->orig_mac[1] = (dev->dev_addr[1] << 0) + (dev->dev_addr[0] << 8);
 	} else {
 		/* need to reverse mac address to correct order */
 		dev->dev_addr[0] = (np->orig_mac[1] >>  8) & 0xff;
@@ -5670,8 +5667,6 @@ static int __devinit nv_probe(struct pci
 		dev->dev_addr[3] = (np->orig_mac[0] >> 16) & 0xff;
 		dev->dev_addr[4] = (np->orig_mac[0] >>  8) & 0xff;
 		dev->dev_addr[5] = (np->orig_mac[0] >>  0) & 0xff;
-		writel(txreg|NVREG_TRANSMITPOLL_MAC_ADDR_REV, base + NvRegTransmitPoll);
-		printk(KERN_DEBUG "nv_probe: set workaround bit for reversed mac addr\n");
 	}
 	memcpy(dev->perm_addr, dev->dev_addr, dev->addr_len);
 
@@ -5923,14 +5918,31 @@ static void nv_restore_mac_addr(struct p
 {
 	struct net_device *dev = pci_get_drvdata(pci_dev);
 	struct fe_priv *np = netdev_priv(dev);
-	u8 __iomem *base = get_hwbase(dev);
+	u8 __iomem *base;
+	u32 txreg;
+
+	if (np->orig_mac_status == -1)
+		return;
+
+	base = get_hwbase(dev);
+	txreg = readl(base + NvRegTransmitPoll);
+	if (np->orig_mac_status == 1) {
+		/*
+		 * Set orig mac address back to the reversed version.
+		 * This flag will be cleared during low power transition.
+		 * Therefore, set that bit don't confuse other...
+		 */
+		writel(txreg | NVREG_TRANSMITPOLL_MAC_ADDR_REV,
+		       base + NvRegTransmitPoll);
+		return;
+	}
 
 	/* special op: write back the misordered MAC address - otherwise
 	 * the next nv_probe would see a wrong address.
 	 */
 	writel(np->orig_mac[0], base + NvRegMacAddrA);
 	writel(np->orig_mac[1], base + NvRegMacAddrB);
-	writel(readl(base + NvRegTransmitPoll) & ~NVREG_TRANSMITPOLL_MAC_ADDR_REV,
+	writel(txreg & ~NVREG_TRANSMITPOLL_MAC_ADDR_REV,
 	       base + NvRegTransmitPoll);
 }
 

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Rafael J. Wysocki]

On Friday 30 January 2009, Yinghai Lu wrote:
> On Thu, Jan 29, 2009 at 10:53 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> > On Wed, Jan 28, 2009 at 10:31 PM, Philipp Matthias Hahn
> > <pmhahn@titan.lahn.de> wrote:
> >> Hello!
> >>
> >> Somewhere between 2.6.26 and 2.6.27 WOL stopped working on my MS-7350
> >> motherboard with an "nVidia Corporation MCP51 Ethernet Controller (rev a3)".
> >>        "etherwake 00:19:db:f2:e1:35" did not work
> >>        "etherwake 35:e1:f2:db:19:00" did work
> 
> looks like your BIOS, already reverse the MAC addr...
> 
> please check attached ... Rafael, wonder if will break suspend/resume...

Well, it doesn't look like it's going to, but testing is necessary.

Thanks,
Rafael

2.6.29-rc3-git6: Reported regressions 2.6.27 -> 2.6.28

[Rafael J. Wysocki]

This message contains a list of some regressions introduced between 2.6.27 and
2.6.28, for which there are no fixes in the mainline I know of.  If any of them
have been fixed already, please let me know.

If you know of any other unresolved regressions introduced between 2.6.27
and 2.6.28, please let me know either and I'll add them to the list.
Also, please let me know if any of the entries below are invalid.

Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2009-02-04      149       33          30
  2009-01-20      144       30          27
  2009-01-11      139       33          30
  2008-12-21      120       19          17
  2008-12-13      111       14          13
  2008-12-07      106       20          17
  2008-12-04      106       29          21
  2008-11-22       93       25          15
  2008-11-16       89       32          18
  2008-11-09       73       40          27
  2008-11-02       55       41          29
  2008-10-25       26       25          20



Unresolved regressions
----------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12619
Subject		: Regression 2.6.28 and last - boot failed
Submitter	: jan sonnek <ha2nny@gmail.com>
Date		: 2009-02-01 19:59 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=123351836213969&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12612
Subject		: hard lockup when interrupting cdda2wav
Submitter	: Matthias Reichl <hias@horus.com>
Date		: 2009-01-28 16:41 (8 days old)
References	: http://marc.info/?l=linux-kernel&m=123316111415677&w=4
Handled-By	: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12559
Subject		: Huawei E169 doesn't work as mass storage anymore
Submitter	: kpalberg <kpalberg@gmail.com>
Date		: 2009-01-28 02:34 (8 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12520
Subject		: Cannot boot 2.6.28 under Dell OptiPlex 960
Submitter	: Denis Scherbakov <denis_scherbakov@yahoo.com>
Date		: 2009-01-22 04:37 (14 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12500
Subject		: r8169: NETDEV WATCHDOG: eth0 (r8169): transmit timed out
Submitter	: Justin Piszcz <jpiszcz@lucidpixels.com>
Date		: 2009-01-13 21:19 (23 days old)
References	: http://marc.info/?l=linux-kernel&m=123188160811322&w=4
Handled-By	: Francois Romieu <romieu@fr.zoreil.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12465
Subject		: KVM guests stalling on 2.6.28 (bisected)
Submitter	: Kevin Shanahan <kmshanah@ucwb.org.au>
Date		: 2009-01-17 03:37 (19 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
Subject		: TMDC Joystick no longer works in kernel 2.6.28
Submitter	: Andrew S. Johnson <andy@asjohnson.com>
Date		: 2009-01-10 21:53 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=123162486415366&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12421
Subject		: GPF on 2.6.28 &amp; 2.6.28-rc9-git3    e1000e / e1000 issues
Submitter	: Doug Bazarnic <doug@bazarnic.net>
Date		: 2009-01-09 21:26 (27 days old)
References	: http://marc.info/?l=linux-kernel&m=123153653120204&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12411
Subject		: 2.6.28: BUG in r8169
Submitter	: Andrey Vul <andrey.vul@gmail.com>
Date		: 2008-12-31 18:37 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=123074869611409&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12409
Subject		: NULL pointer dereference at get_stats()
Submitter	: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Date		: 2008-12-30 12:53 (37 days old)
References	: http://marc.info/?l=linux-kernel&m=123064167008695&w=4
Handled-By	: Frederik Deweerdt <frederik.deweerdt@xprog.eu>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12408
Subject		: Funny problem with 2.6.28: Kernel stalls
Submitter	: Michael Roth <mroth@nessie.de>
Date		: 2008-12-25 15:14 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=123021931714282&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12407
Subject		: Kernel 2.6.28 regression: Hang after hibernate
Submitter	: Frank Groeneveld <frankgroeneveld@gmail.com>
Date		: 2008-12-28 20:34 (39 days old)
References	: http://marc.info/?l=linux-kernel&m=123049651906081&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12405
Subject		: oops in __bounce_end_io_read under kvm
Submitter	: Christoph Hellwig <hch@lst.de>
Date		: 2008-12-26 17:36 (41 days old)
References	: http://marc.info/?l=linux-kernel&m=123031303400676&w=4
Handled-By	: Jens Axboe <jens.axboe@oracle.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12404
Subject		: Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e
Submitter	: Kernel <kernel@bazarnic.net>
Date		: 2008-12-22 9:37 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=122993873320150&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12403
Subject		: TTY problem on linux-2.6.28-rc7
Submitter	: sasa sasa <sasak.1983@gmail.com>
Date		: 2008-12-22 4:23 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=122991914600390&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12401
Subject		: 2.6.28 regression: xbacklight broken on ThinkPad X61s
Submitter	: Tino Keitel <tino.keitel@gmx.de>
Date		: 2009-01-05 8:39 (31 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=22c13f9d8179f4c9caecfcb60a95214562b9addc
References	: http://marc.info/?l=linux-kernel&m=123114479110314&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12395
Subject		: 2.6.28-rc9: oprofile regression
Submitter	: Tim Blechmann <tim@klingt.org>
Date		: 2008-12-21 14:23 (46 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b99170288421c79f0c2efa8b33e26e65f4bb7fb8
References	: http://marc.info/?l=linux-kernel&m=122986946614791&w=4
Handled-By	: Andi Kleen <ak@linux.intel.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12393
Subject		: debugging in dosemu causes lots of 'scheduling while atomic'
Submitter	: Michal Suchanek <hramrach@centrum.cz>
Date		: 2009-01-09 07:28 (27 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12391
Subject		: Processor does not go below C2 state until usb.autosuspend is enabled
Submitter	: Gergely Imreh <imrehg@gmail.com>
Date		: 2009-01-09 02:35 (27 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12337
Subject		: ~100 extra wakeups reported by powertop
Submitter	: Alberto Gonzalez <luis6674@yahoo.com>
Date		: 2008-12-31 12:25 (36 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12265
Subject		: FPU emulation broken in 2.6.28-rc8 ?
Submitter	: Rogier Wolff <R.E.Wolff@bitwizard.nl>
Date		: 2008-12-17 8:56 (50 days old)
References	: http://marc.info/?l=linux-kernel&m=122950463030747&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12264
Subject		: i915: switching from kwin in opengl mode to a VT then back to x11, x11 freezes
Submitter	: Caleb Cushing <xenoterracide@gmail.com>
Date		: 2008-12-16 11:40 (51 days old)
References	: http://marc.info/?l=linux-kernel&m=122942777030666&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12263
Subject		: Sata soft reset filling log
Submitter	: Justin Madru <bevicm@dslextreme.com>
Date		: 2008-12-13 2:07 (54 days old)
References	: http://marc.info/?l=linux-kernel&m=122913412608533&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights@fastmail.fm>
Date		: 2008-12-14 11:39 (53 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen@redhat.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12209
Subject		: oldish top core dumps (in its meminfo() function)
Submitter	: Andreas Mohr <andi@lisas.de>
Date		: 2008-12-12 18:49 (55 days old)
References	: http://marc.info/?l=linux-kernel&m=122910784006472&w=4
		  http://marc.info/?l=linux-kernel&m=122907511319288&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12208
Subject		: uml is very slow on 2.6.28 host
Submitter	: Miklos Szeredi <miklos@szeredi.hu>
Date		: 2008-12-12 9:35 (55 days old)
References	: http://marc.info/?l=linux-kernel&m=122907463518593&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12160
Subject		: networking oops after resume from s2ram (2.6.28-rc6)
Submitter	: Marcin Slusarz <marcin.slusarz@gmail.com>
Date		: 2008-11-28 21:15 (69 days old)
References	: http://marc.info/?l=linux-kernel&m=122790701615723&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12159
Subject		: 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2008-11-27 20:33 (70 days old)
References	: http://marc.info/?l=linux-kernel&m=122781805620212&w=4
Handled-By	: Takashi Iwai <tiwai@suse.de>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12061
Subject		: snd_hda_intel: power_save: sound cracks on powerdown
Submitter	: Jens Weibler <bugzilla-kernel@jensthebrain.de>
Date		: 2008-11-18 12:07 (79 days old)
Handled-By	: Takashi Iwai <tiwai@suse.de>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=11849
Subject		: default IRQ affinity change in v2.6.27 (breaking several SMP PPC based systems)
Submitter	: Kumar Gala <galak@kernel.crashing.org>
Date		: 2008-10-24 12:45 (104 days old)
References	: http://marc.info/?l=linux-kernel&m=122485245924125&w=4


Regressions with patches
------------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12614
Subject		: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
Submitter	: Philipp Matthias Hahn <pmhahn@titan.lahn.de>
Date		: 2009-01-29 6:31 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=123321232825316&w=4
Handled-By	: Yinghai Lu <yinghai@kernel.org>
Patch		: http://marc.info/?l=linux-kernel&m=123330459229248&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12406
Subject		: 2.6.28 thinks that my PS/2 mouse is a touchpad
Submitter	: Alexander E. Patrakov <patrakov@gmail.com>
Date		: 2008-12-27 9:06 (40 days old)
References	: http://marc.info/?l=linux-kernel&m=123036893817280&w=4
Handled-By	: Arjan Opmeer <arjan@opmeer.net>
Patch		: http://marc.info/?l=linux-kernel&m=123092147703236&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12396
Subject		: hwinfo problem since 2.6.28
Submitter	: Beschorner Daniel <Daniel.Beschorner@facton.com>
Date		: 2009-01-06 8:53 (30 days old)
References	: http://marc.info/?l=linux-kernel&m=123123277800835&w=4
Handled-By	: Suresh Siddha <suresh.b.siddha@intel.com>
Patch		: http://marc.info/?l=linux-kernel&m=123154005127497&w=4


For details, please visit the bug entries and follow the links given in
references.

As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions introduced
between 2.6.27 and 2.6.28, unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=11808

Please let me know if there are any Bugzilla entries that should be added to
the list in there.

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

2.6.29-rc3-git6: Reported regressions 2.6.27 -> 2.6.28

[Rafael J. Wysocki]

This message contains a list of some regressions introduced between 2.6.27 and
2.6.28, for which there are no fixes in the mainline I know of.  If any of them
have been fixed already, please let me know.

If you know of any other unresolved regressions introduced between 2.6.27
and 2.6.28, please let me know either and I'll add them to the list.
Also, please let me know if any of the entries below are invalid.

Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2009-02-04      149       33          30
  2009-01-20      144       30          27
  2009-01-11      139       33          30
  2008-12-21      120       19          17
  2008-12-13      111       14          13
  2008-12-07      106       20          17
  2008-12-04      106       29          21
  2008-11-22       93       25          15
  2008-11-16       89       32          18
  2008-11-09       73       40          27
  2008-11-02       55       41          29
  2008-10-25       26       25          20



Unresolved regressions
----------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12619
Subject		: Regression 2.6.28 and last - boot failed
Submitter	: jan sonnek <ha2nny@gmail.com>
Date		: 2009-02-01 19:59 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=123351836213969&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12612
Subject		: hard lockup when interrupting cdda2wav
Submitter	: Matthias Reichl <hias@horus.com>
Date		: 2009-01-28 16:41 (8 days old)
References	: http://marc.info/?l=linux-kernel&m=123316111415677&w=4
Handled-By	: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12559
Subject		: Huawei E169 doesn't work as mass storage anymore
Submitter	: kpalberg <kpalberg@gmail.com>
Date		: 2009-01-28 02:34 (8 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12520
Subject		: Cannot boot 2.6.28 under Dell OptiPlex 960
Submitter	: Denis Scherbakov <denis_scherbakov@yahoo.com>
Date		: 2009-01-22 04:37 (14 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12500
Subject		: r8169: NETDEV WATCHDOG: eth0 (r8169): transmit timed out
Submitter	: Justin Piszcz <jpiszcz@lucidpixels.com>
Date		: 2009-01-13 21:19 (23 days old)
References	: http://marc.info/?l=linux-kernel&m=123188160811322&w=4
Handled-By	: Francois Romieu <romieu@fr.zoreil.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12465
Subject		: KVM guests stalling on 2.6.28 (bisected)
Submitter	: Kevin Shanahan <kmshanah@ucwb.org.au>
Date		: 2009-01-17 03:37 (19 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
Subject		: TMDC Joystick no longer works in kernel 2.6.28
Submitter	: Andrew S. Johnson <andy@asjohnson.com>
Date		: 2009-01-10 21:53 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=123162486415366&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12421
Subject		: GPF on 2.6.28 &amp; 2.6.28-rc9-git3    e1000e / e1000 issues
Submitter	: Doug Bazarnic <doug@bazarnic.net>
Date		: 2009-01-09 21:26 (27 days old)
References	: http://marc.info/?l=linux-kernel&m=123153653120204&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12411
Subject		: 2.6.28: BUG in r8169
Submitter	: Andrey Vul <andrey.vul@gmail.com>
Date		: 2008-12-31 18:37 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=123074869611409&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12409
Subject		: NULL pointer dereference at get_stats()
Submitter	: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Date		: 2008-12-30 12:53 (37 days old)
References	: http://marc.info/?l=linux-kernel&m=123064167008695&w=4
Handled-By	: Frederik Deweerdt <frederik.deweerdt@xprog.eu>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12408
Subject		: Funny problem with 2.6.28: Kernel stalls
Submitter	: Michael Roth <mroth@nessie.de>
Date		: 2008-12-25 15:14 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=123021931714282&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12407
Subject		: Kernel 2.6.28 regression: Hang after hibernate
Submitter	: Frank Groeneveld <frankgroeneveld@gmail.com>
Date		: 2008-12-28 20:34 (39 days old)
References	: http://marc.info/?l=linux-kernel&m=123049651906081&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12405
Subject		: oops in __bounce_end_io_read under kvm
Submitter	: Christoph Hellwig <hch@lst.de>
Date		: 2008-12-26 17:36 (41 days old)
References	: http://marc.info/?l=linux-kernel&m=123031303400676&w=4
Handled-By	: Jens Axboe <jens.axboe@oracle.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12404
Subject		: Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e
Submitter	: Kernel <kernel@bazarnic.net>
Date		: 2008-12-22 9:37 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=122993873320150&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12403
Subject		: TTY problem on linux-2.6.28-rc7
Submitter	: sasa sasa <sasak.1983@gmail.com>
Date		: 2008-12-22 4:23 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=122991914600390&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12401
Subject		: 2.6.28 regression: xbacklight broken on ThinkPad X61s
Submitter	: Tino Keitel <tino.keitel@gmx.de>
Date		: 2009-01-05 8:39 (31 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=22c13f9d8179f4c9caecfcb60a95214562b9addc
References	: http://marc.info/?l=linux-kernel&m=123114479110314&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12395
Subject		: 2.6.28-rc9: oprofile regression
Submitter	: Tim Blechmann <tim@klingt.org>
Date		: 2008-12-21 14:23 (46 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b99170288421c79f0c2efa8b33e26e65f4bb7fb8
References	: http://marc.info/?l=linux-kernel&m=122986946614791&w=4
Handled-By	: Andi Kleen <ak@linux.intel.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12393
Subject		: debugging in dosemu causes lots of 'scheduling while atomic'
Submitter	: Michal Suchanek <hramrach@centrum.cz>
Date		: 2009-01-09 07:28 (27 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12391
Subject		: Processor does not go below C2 state until usb.autosuspend is enabled
Submitter	: Gergely Imreh <imrehg@gmail.com>
Date		: 2009-01-09 02:35 (27 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12337
Subject		: ~100 extra wakeups reported by powertop
Submitter	: Alberto Gonzalez <luis6674@yahoo.com>
Date		: 2008-12-31 12:25 (36 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12265
Subject		: FPU emulation broken in 2.6.28-rc8 ?
Submitter	: Rogier Wolff <R.E.Wolff@bitwizard.nl>
Date		: 2008-12-17 8:56 (50 days old)
References	: http://marc.info/?l=linux-kernel&m=122950463030747&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12264
Subject		: i915: switching from kwin in opengl mode to a VT then back to x11, x11 freezes
Submitter	: Caleb Cushing <xenoterracide@gmail.com>
Date		: 2008-12-16 11:40 (51 days old)
References	: http://marc.info/?l=linux-kernel&m=122942777030666&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12263
Subject		: Sata soft reset filling log
Submitter	: Justin Madru <bevicm@dslextreme.com>
Date		: 2008-12-13 2:07 (54 days old)
References	: http://marc.info/?l=linux-kernel&m=122913412608533&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights@fastmail.fm>
Date		: 2008-12-14 11:39 (53 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen@redhat.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12209
Subject		: oldish top core dumps (in its meminfo() function)
Submitter	: Andreas Mohr <andi@lisas.de>
Date		: 2008-12-12 18:49 (55 days old)
References	: http://marc.info/?l=linux-kernel&m=122910784006472&w=4
		  http://marc.info/?l=linux-kernel&m=122907511319288&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12208
Subject		: uml is very slow on 2.6.28 host
Submitter	: Miklos Szeredi <miklos@szeredi.hu>
Date		: 2008-12-12 9:35 (55 days old)
References	: http://marc.info/?l=linux-kernel&m=122907463518593&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12160
Subject		: networking oops after resume from s2ram (2.6.28-rc6)
Submitter	: Marcin Slusarz <marcin.slusarz@gmail.com>
Date		: 2008-11-28 21:15 (69 days old)
References	: http://marc.info/?l=linux-kernel&m=122790701615723&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12159
Subject		: 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2008-11-27 20:33 (70 days old)
References	: http://marc.info/?l=linux-kernel&m=122781805620212&w=4
Handled-By	: Takashi Iwai <tiwai@suse.de>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12061
Subject		: snd_hda_intel: power_save: sound cracks on powerdown
Submitter	: Jens Weibler <bugzilla-kernel@jensthebrain.de>
Date		: 2008-11-18 12:07 (79 days old)
Handled-By	: Takashi Iwai <tiwai@suse.de>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=11849
Subject		: default IRQ affinity change in v2.6.27 (breaking several SMP PPC based systems)
Submitter	: Kumar Gala <galak@kernel.crashing.org>
Date		: 2008-10-24 12:45 (104 days old)
References	: http://marc.info/?l=linux-kernel&m=122485245924125&w=4


Regressions with patches
------------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12614
Subject		: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
Submitter	: Philipp Matthias Hahn <pmhahn@titan.lahn.de>
Date		: 2009-01-29 6:31 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=123321232825316&w=4
Handled-By	: Yinghai Lu <yinghai@kernel.org>
Patch		: http://marc.info/?l=linux-kernel&m=123330459229248&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12406
Subject		: 2.6.28 thinks that my PS/2 mouse is a touchpad
Submitter	: Alexander E. Patrakov <patrakov@gmail.com>
Date		: 2008-12-27 9:06 (40 days old)
References	: http://marc.info/?l=linux-kernel&m=123036893817280&w=4
Handled-By	: Arjan Opmeer <arjan@opmeer.net>
Patch		: http://marc.info/?l=linux-kernel&m=123092147703236&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12396
Subject		: hwinfo problem since 2.6.28
Submitter	: Beschorner Daniel <Daniel.Beschorner@facton.com>
Date		: 2009-01-06 8:53 (30 days old)
References	: http://marc.info/?l=linux-kernel&m=123123277800835&w=4
Handled-By	: Suresh Siddha <suresh.b.siddha@intel.com>
Patch		: http://marc.info/?l=linux-kernel&m=123154005127497&w=4


For details, please visit the bug entries and follow the links given in
references.

As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions introduced
between 2.6.27 and 2.6.28, unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=11808

Please let me know if there are any Bugzilla entries that should be added to
the list in there.

Thanks,
Rafael

[Bug #11849] default IRQ affinity change in v2.6.27 (breaking several SMP PPC based systems)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=11849
Subject		: default IRQ affinity change in v2.6.27 (breaking several SMP PPC based systems)
Submitter	: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Date		: 2008-10-24 12:45 (104 days old)
References	: http://marc.info/?l=linux-kernel&m=122485245924125&w=4

[Bug #11849] default IRQ affinity change in v2.6.27 (breaking several SMP PPC based systems)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=11849
Subject		: default IRQ affinity change in v2.6.27 (breaking several SMP PPC based systems)
Submitter	: Kumar Gala <galak@kernel.crashing.org>
Date		: 2008-10-24 12:45 (104 days old)
References	: http://marc.info/?l=linux-kernel&m=122485245924125&w=4

[Bug #12061] snd_hda_intel: power_save: sound cracks on powerdown

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12061
Subject		: snd_hda_intel: power_save: sound cracks on powerdown
Submitter	: Jens Weibler <bugzilla-kernel-6hJTtV8wudIr9FUcG+3rRQ@public.gmane.org>
Date		: 2008-11-18 12:07 (79 days old)
Handled-By	: Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>

[Bug #12061] snd_hda_intel: power_save: sound cracks on powerdown

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12061
Subject		: snd_hda_intel: power_save: sound cracks on powerdown
Submitter	: Jens Weibler <bugzilla-kernel@jensthebrain.de>
Date		: 2008-11-18 12:07 (79 days old)
Handled-By	: Takashi Iwai <tiwai@suse.de>

[Bug #12159] 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12159
Subject		: 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver
Submitter	: Miles Lane <miles.lane-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2008-11-27 20:33 (70 days old)
References	: http://marc.info/?l=linux-kernel&m=122781805620212&w=4
Handled-By	: Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>

[Bug #12160] networking oops after resume from s2ram (2.6.28-rc6)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12160
Subject		: networking oops after resume from s2ram (2.6.28-rc6)
Submitter	: Marcin Slusarz <marcin.slusarz@gmail.com>
Date		: 2008-11-28 21:15 (69 days old)
References	: http://marc.info/?l=linux-kernel&m=122790701615723&w=4

[Bug #12159] 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12159
Subject		: 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver
Submitter	: Miles Lane <miles.lane@gmail.com>
Date		: 2008-11-27 20:33 (70 days old)
References	: http://marc.info/?l=linux-kernel&m=122781805620212&w=4
Handled-By	: Takashi Iwai <tiwai@suse.de>

[Bug #12208] uml is very slow on 2.6.28 host

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12208
Subject		: uml is very slow on 2.6.28 host
Submitter	: Miklos Szeredi <miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org>
Date		: 2008-12-12 9:35 (55 days old)
References	: http://marc.info/?l=linux-kernel&m=122907463518593&w=4

[Bug #12208] uml is very slow on 2.6.28 host

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12208
Subject		: uml is very slow on 2.6.28 host
Submitter	: Miklos Szeredi <miklos@szeredi.hu>
Date		: 2008-12-12 9:35 (55 days old)
References	: http://marc.info/?l=linux-kernel&m=122907463518593&w=4

[Bug #12209] oldish top core dumps (in its meminfo() function)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12209
Subject		: oldish top core dumps (in its meminfo() function)
Submitter	: Andreas Mohr <andi-5+Cda9B46AM@public.gmane.org>
Date		: 2008-12-12 18:49 (55 days old)
References	: http://marc.info/?l=linux-kernel&m=122910784006472&w=4
		  http://marc.info/?l=linux-kernel&m=122907511319288&w=4

[Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
Date		: 2008-12-14 11:39 (53 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

[Bug #12209] oldish top core dumps (in its meminfo() function)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12209
Subject		: oldish top core dumps (in its meminfo() function)
Submitter	: Andreas Mohr <andi@lisas.de>
Date		: 2008-12-12 18:49 (55 days old)
References	: http://marc.info/?l=linux-kernel&m=122910784006472&w=4
		  http://marc.info/?l=linux-kernel&m=122907511319288&w=4

[Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights@fastmail.fm>
Date		: 2008-12-14 11:39 (53 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen@redhat.com>

[Bug #12265] FPU emulation broken in 2.6.28-rc8 ?

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12265
Subject		: FPU emulation broken in 2.6.28-rc8 ?
Submitter	: Rogier Wolff <R.E.Wolff-bu/CaDbLbdHGjfRZg6uqBA@public.gmane.org>
Date		: 2008-12-17 8:56 (50 days old)
References	: http://marc.info/?l=linux-kernel&m=122950463030747&w=4

[Bug #12264] i915: switching from kwin in opengl mode to a VT then back to x11, x11 freezes

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12264
Subject		: i915: switching from kwin in opengl mode to a VT then back to x11, x11 freezes
Submitter	: Caleb Cushing <xenoterracide-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2008-12-16 11:40 (51 days old)
References	: http://marc.info/?l=linux-kernel&m=122942777030666&w=4

[Bug #12263] Sata soft reset filling log

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12263
Subject		: Sata soft reset filling log
Submitter	: Justin Madru <bevicm-QP1aEjBt37AFQeE35raUng@public.gmane.org>
Date		: 2008-12-13 2:07 (54 days old)
References	: http://marc.info/?l=linux-kernel&m=122913412608533&w=4

[Bug #12265] FPU emulation broken in 2.6.28-rc8 ?

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12265
Subject		: FPU emulation broken in 2.6.28-rc8 ?
Submitter	: Rogier Wolff <R.E.Wolff@bitwizard.nl>
Date		: 2008-12-17 8:56 (50 days old)
References	: http://marc.info/?l=linux-kernel&m=122950463030747&w=4

[Bug #12264] i915: switching from kwin in opengl mode to a VT then back to x11, x11 freezes

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12264
Subject		: i915: switching from kwin in opengl mode to a VT then back to x11, x11 freezes
Submitter	: Caleb Cushing <xenoterracide@gmail.com>
Date		: 2008-12-16 11:40 (51 days old)
References	: http://marc.info/?l=linux-kernel&m=122942777030666&w=4

[Bug #12263] Sata soft reset filling log

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12263
Subject		: Sata soft reset filling log
Submitter	: Justin Madru <bevicm@dslextreme.com>
Date		: 2008-12-13 2:07 (54 days old)
References	: http://marc.info/?l=linux-kernel&m=122913412608533&w=4

[Bug #12337] ~100 extra wakeups reported by powertop

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12337
Subject		: ~100 extra wakeups reported by powertop
Submitter	: Alberto Gonzalez <luis6674-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Date		: 2008-12-31 12:25 (36 days old)

[Bug #12391] Processor does not go below C2 state until usb.autosuspend is enabled

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12391
Subject		: Processor does not go below C2 state until usb.autosuspend is enabled
Submitter	: Gergely Imreh <imrehg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-09 02:35 (27 days old)

[Bug #12337] ~100 extra wakeups reported by powertop

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12337
Subject		: ~100 extra wakeups reported by powertop
Submitter	: Alberto Gonzalez <luis6674@yahoo.com>
Date		: 2008-12-31 12:25 (36 days old)

[Bug #12391] Processor does not go below C2 state until usb.autosuspend is enabled

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12391
Subject		: Processor does not go below C2 state until usb.autosuspend is enabled
Submitter	: Gergely Imreh <imrehg@gmail.com>
Date		: 2009-01-09 02:35 (27 days old)

[Bug #12395] 2.6.28-rc9: oprofile regression

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12395
Subject		: 2.6.28-rc9: oprofile regression
Submitter	: Tim Blechmann <tim-xpEK/MU0Hawdnm+yROfE0A@public.gmane.org>
Date		: 2008-12-21 14:23 (46 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b99170288421c79f0c2efa8b33e26e65f4bb7fb8
References	: http://marc.info/?l=linux-kernel&m=122986946614791&w=4
Handled-By	: Andi Kleen <ak-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>

[Bug #12393] debugging in dosemu causes lots of 'scheduling while atomic'

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12393
Subject		: debugging in dosemu causes lots of 'scheduling while atomic'
Submitter	: Michal Suchanek <hramrach-aRb0bU7PRFPrBKCeMvbIDA@public.gmane.org>
Date		: 2009-01-09 07:28 (27 days old)

[Bug #12393] debugging in dosemu causes lots of 'scheduling while atomic'

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12393
Subject		: debugging in dosemu causes lots of 'scheduling while atomic'
Submitter	: Michal Suchanek <hramrach@centrum.cz>
Date		: 2009-01-09 07:28 (27 days old)

[Bug #12395] 2.6.28-rc9: oprofile regression

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12395
Subject		: 2.6.28-rc9: oprofile regression
Submitter	: Tim Blechmann <tim@klingt.org>
Date		: 2008-12-21 14:23 (46 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b99170288421c79f0c2efa8b33e26e65f4bb7fb8
References	: http://marc.info/?l=linux-kernel&m=122986946614791&w=4
Handled-By	: Andi Kleen <ak@linux.intel.com>

[Bug #12396] hwinfo problem since 2.6.28

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12396
Subject		: hwinfo problem since 2.6.28
Submitter	: Beschorner Daniel <Daniel.Beschorner-cdG02ZADnvLQT0dZR+AlfA@public.gmane.org>
Date		: 2009-01-06 8:53 (30 days old)
References	: http://marc.info/?l=linux-kernel&m=123123277800835&w=4
Handled-By	: Suresh Siddha <suresh.b.siddha-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=123154005127497&w=4

[Bug #12396] hwinfo problem since 2.6.28

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12396
Subject		: hwinfo problem since 2.6.28
Submitter	: Beschorner Daniel <Daniel.Beschorner@facton.com>
Date		: 2009-01-06 8:53 (30 days old)
References	: http://marc.info/?l=linux-kernel&m=123123277800835&w=4
Handled-By	: Suresh Siddha <suresh.b.siddha@intel.com>
Patch		: http://marc.info/?l=linux-kernel&m=123154005127497&w=4

[Bug #12401] 2.6.28 regression: xbacklight broken on ThinkPad X61s

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12401
Subject		: 2.6.28 regression: xbacklight broken on ThinkPad X61s
Submitter	: Tino Keitel <tino.keitel-Mmb7MZpHnFY@public.gmane.org>
Date		: 2009-01-05 8:39 (31 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=22c13f9d8179f4c9caecfcb60a95214562b9addc
References	: http://marc.info/?l=linux-kernel&m=123114479110314&w=4

[Bug #12401] 2.6.28 regression: xbacklight broken on ThinkPad X61s

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12401
Subject		: 2.6.28 regression: xbacklight broken on ThinkPad X61s
Submitter	: Tino Keitel <tino.keitel@gmx.de>
Date		: 2009-01-05 8:39 (31 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=22c13f9d8179f4c9caecfcb60a95214562b9addc
References	: http://marc.info/?l=linux-kernel&m=123114479110314&w=4

[Bug #12406] 2.6.28 thinks that my PS/2 mouse is a touchpad

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12406
Subject		: 2.6.28 thinks that my PS/2 mouse is a touchpad
Submitter	: Alexander E. Patrakov <patrakov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2008-12-27 9:06 (40 days old)
References	: http://marc.info/?l=linux-kernel&m=123036893817280&w=4
Handled-By	: Arjan Opmeer <arjan-OssVvNj1wBysTnJN9+BGXg@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=123092147703236&w=4

[Bug #12403] TTY problem on linux-2.6.28-rc7

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12403
Subject		: TTY problem on linux-2.6.28-rc7
Submitter	: sasa sasa <sasak.1983-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2008-12-22 4:23 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=122991914600390&w=4

[Bug #12405] oops in __bounce_end_io_read under kvm

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12405
Subject		: oops in __bounce_end_io_read under kvm
Submitter	: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Date		: 2008-12-26 17:36 (41 days old)
References	: http://marc.info/?l=linux-kernel&m=123031303400676&w=4
Handled-By	: Jens Axboe <jens.axboe-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>

[Bug #12404] Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12404
Subject		: Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e
Submitter	: Kernel <kernel-nOyj/A09A+/k1uMJSBkQmQ@public.gmane.org>
Date		: 2008-12-22 9:37 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=122993873320150&w=4

[Bug #12403] TTY problem on linux-2.6.28-rc7

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12403
Subject		: TTY problem on linux-2.6.28-rc7
Submitter	: sasa sasa <sasak.1983@gmail.com>
Date		: 2008-12-22 4:23 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=122991914600390&w=4

[Bug #12404] Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12404
Subject		: Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e
Submitter	: Kernel <kernel@bazarnic.net>
Date		: 2008-12-22 9:37 (45 days old)
References	: http://marc.info/?l=linux-kernel&m=122993873320150&w=4

[Bug #12406] 2.6.28 thinks that my PS/2 mouse is a touchpad

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12406
Subject		: 2.6.28 thinks that my PS/2 mouse is a touchpad
Submitter	: Alexander E. Patrakov <patrakov@gmail.com>
Date		: 2008-12-27 9:06 (40 days old)
References	: http://marc.info/?l=linux-kernel&m=123036893817280&w=4
Handled-By	: Arjan Opmeer <arjan@opmeer.net>
Patch		: http://marc.info/?l=linux-kernel&m=123092147703236&w=4

[Bug #12405] oops in __bounce_end_io_read under kvm

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12405
Subject		: oops in __bounce_end_io_read under kvm
Submitter	: Christoph Hellwig <hch@lst.de>
Date		: 2008-12-26 17:36 (41 days old)
References	: http://marc.info/?l=linux-kernel&m=123031303400676&w=4
Handled-By	: Jens Axboe <jens.axboe@oracle.com>

[Bug #12408] Funny problem with 2.6.28: Kernel stalls

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12408
Subject		: Funny problem with 2.6.28: Kernel stalls
Submitter	: Michael Roth <mroth-+8Z3Oe2AQjqzQB+pC5nmwQ@public.gmane.org>
Date		: 2008-12-25 15:14 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=123021931714282&w=4

[Bug #12407] Kernel 2.6.28 regression: Hang after hibernate

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12407
Subject		: Kernel 2.6.28 regression: Hang after hibernate
Submitter	: Frank Groeneveld <frankgroeneveld-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2008-12-28 20:34 (39 days old)
References	: http://marc.info/?l=linux-kernel&m=123049651906081&w=4

[Bug #12407] Kernel 2.6.28 regression: Hang after hibernate

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12407
Subject		: Kernel 2.6.28 regression: Hang after hibernate
Submitter	: Frank Groeneveld <frankgroeneveld@gmail.com>
Date		: 2008-12-28 20:34 (39 days old)
References	: http://marc.info/?l=linux-kernel&m=123049651906081&w=4

[Bug #12408] Funny problem with 2.6.28: Kernel stalls

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12408
Subject		: Funny problem with 2.6.28: Kernel stalls
Submitter	: Michael Roth <mroth@nessie.de>
Date		: 2008-12-25 15:14 (42 days old)
References	: http://marc.info/?l=linux-kernel&m=123021931714282&w=4

[Bug #12409] NULL pointer dereference at get_stats()

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12409
Subject		: NULL pointer dereference at get_stats()
Submitter	: Tetsuo Handa <penguin-kernel-1yMVhJb1mP/7nzcFbJAaVXf5DAMn2ifp@public.gmane.org>
Date		: 2008-12-30 12:53 (37 days old)
References	: http://marc.info/?l=linux-kernel&m=123064167008695&w=4
Handled-By	: Frederik Deweerdt <frederik.deweerdt-kjvbsxwSFqI@public.gmane.org>

[Bug #12411] 2.6.28: BUG in r8169

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12411
Subject		: 2.6.28: BUG in r8169
Submitter	: Andrey Vul <andrey.vul-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2008-12-31 18:37 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=123074869611409&w=4

[Bug #12411] 2.6.28: BUG in r8169

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12411
Subject		: 2.6.28: BUG in r8169
Submitter	: Andrey Vul <andrey.vul@gmail.com>
Date		: 2008-12-31 18:37 (36 days old)
References	: http://marc.info/?l=linux-kernel&m=123074869611409&w=4

[Bug #12409] NULL pointer dereference at get_stats()

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12409
Subject		: NULL pointer dereference at get_stats()
Submitter	: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Date		: 2008-12-30 12:53 (37 days old)
References	: http://marc.info/?l=linux-kernel&m=123064167008695&w=4
Handled-By	: Frederik Deweerdt <frederik.deweerdt@xprog.eu>

[Bug #12426] TMDC Joystick no longer works in kernel 2.6.28

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
Subject		: TMDC Joystick no longer works in kernel 2.6.28
Submitter	: Andrew S. Johnson <andy-9eXmkf4BiQ2aMJb+Lgu22Q@public.gmane.org>
Date		: 2009-01-10 21:53 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=123162486415366&w=4

[Bug #12426] TMDC Joystick no longer works in kernel 2.6.28

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
Subject		: TMDC Joystick no longer works in kernel 2.6.28
Submitter	: Andrew S. Johnson <andy@asjohnson.com>
Date		: 2009-01-10 21:53 (26 days old)
References	: http://marc.info/?l=linux-kernel&m=123162486415366&w=4

[Bug #12465] KVM guests stalling on 2.6.28 (bisected)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12465
Subject		: KVM guests stalling on 2.6.28 (bisected)
Submitter	: Kevin Shanahan <kmshanah-biM/RbsGxha6c6uEtOJ/EA@public.gmane.org>
Date		: 2009-01-17 03:37 (19 days old)

[Bug #12465] KVM guests stalling on 2.6.28 (bisected)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12465
Subject		: KVM guests stalling on 2.6.28 (bisected)
Submitter	: Kevin Shanahan <kmshanah@ucwb.org.au>
Date		: 2009-01-17 03:37 (19 days old)

[Bug #12500] r8169: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12500
Subject		: r8169: NETDEV WATCHDOG: eth0 (r8169): transmit timed out
Submitter	: Justin Piszcz <jpiszcz-BP4nVm5VUdNhbmWW9KSYcQ@public.gmane.org>
Date		: 2009-01-13 21:19 (23 days old)
References	: http://marc.info/?l=linux-kernel&m=123188160811322&w=4
Handled-By	: Francois Romieu <romieu-W8zweXLXuWQS+FvcfC7Uqw@public.gmane.org>

[Bug #12500] r8169: NETDEV WATCHDOG: eth0 (r8169): transmit timed out

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12500
Subject		: r8169: NETDEV WATCHDOG: eth0 (r8169): transmit timed out
Submitter	: Justin Piszcz <jpiszcz@lucidpixels.com>
Date		: 2009-01-13 21:19 (23 days old)
References	: http://marc.info/?l=linux-kernel&m=123188160811322&w=4
Handled-By	: Francois Romieu <romieu@fr.zoreil.com>

[Bug #12520] Cannot boot 2.6.28 under Dell OptiPlex 960

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12520
Subject		: Cannot boot 2.6.28 under Dell OptiPlex 960
Submitter	: Denis Scherbakov <denis_scherbakov-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-22 04:37 (14 days old)

[Bug #12520] Cannot boot 2.6.28 under Dell OptiPlex 960

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12520
Subject		: Cannot boot 2.6.28 under Dell OptiPlex 960
Submitter	: Denis Scherbakov <denis_scherbakov@yahoo.com>
Date		: 2009-01-22 04:37 (14 days old)

[Bug #12559] Huawei E169 doesn't work as mass storage anymore

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12559
Subject		: Huawei E169 doesn't work as mass storage anymore
Submitter	: kpalberg <kpalberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-28 02:34 (8 days old)

[Bug #12559] Huawei E169 doesn't work as mass storage anymore

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12559
Subject		: Huawei E169 doesn't work as mass storage anymore
Submitter	: kpalberg <kpalberg@gmail.com>
Date		: 2009-01-28 02:34 (8 days old)

[Bug #12612] hard lockup when interrupting cdda2wav

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12612
Subject		: hard lockup when interrupting cdda2wav
Submitter	: Matthias Reichl <hias-vtPv7MOkFPkAvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-28 16:41 (8 days old)
References	: http://marc.info/?l=linux-kernel&m=123316111415677&w=4
Handled-By	: FUJITA Tomonori <fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>

[Bug #12612] hard lockup when interrupting cdda2wav

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12612
Subject		: hard lockup when interrupting cdda2wav
Submitter	: Matthias Reichl <hias@horus.com>
Date		: 2009-01-28 16:41 (8 days old)
References	: http://marc.info/?l=linux-kernel&m=123316111415677&w=4
Handled-By	: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>

[Bug #12614] WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12614
Subject		: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
Submitter	: Philipp Matthias Hahn <pmhahn-u4khhh1J0LzF41mA0N3lWw@public.gmane.org>
Date		: 2009-01-29 6:31 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=123321232825316&w=4
Handled-By	: Yinghai Lu <yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=123330459229248&w=4

[Bug #12614] WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12614
Subject		: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
Submitter	: Philipp Matthias Hahn <pmhahn@titan.lahn.de>
Date		: 2009-01-29 6:31 (7 days old)
References	: http://marc.info/?l=linux-kernel&m=123321232825316&w=4
Handled-By	: Yinghai Lu <yinghai@kernel.org>
Patch		: http://marc.info/?l=linux-kernel&m=123330459229248&w=4

[Bug #12619] Regression 2.6.28 and last - boot failed

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12619
Subject		: Regression 2.6.28 and last - boot failed
Submitter	: jan sonnek <ha2nny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-01 19:59 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=123351836213969&w=4

[Bug #12619] Regression 2.6.28 and last - boot failed

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12619
Subject		: Regression 2.6.28 and last - boot failed
Submitter	: jan sonnek <ha2nny@gmail.com>
Date		: 2009-02-01 19:59 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=123351836213969&w=4

Re: [Bug #12159] 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver

[Miles Lane]

This bug is fixed in Linus' tree, afaict.

On Wed, Feb 4, 2009 at 5:58 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12159
> Subject         : 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver
> Submitter       : Miles Lane <miles.lane-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date            : 2008-11-27 20:33 (70 days old)
> References      : http://marc.info/?l=linux-kernel&m=122781805620212&w=4
> Handled-By      : Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>
>
>
>

Re: [Bug #12159] 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver

[Miles Lane]

This bug is fixed in Linus' tree, afaict.

On Wed, Feb 4, 2009 at 5:58 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12159
> Subject         : 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver
> Submitter       : Miles Lane <miles.lane@gmail.com>
> Date            : 2008-11-27 20:33 (70 days old)
> References      : http://marc.info/?l=linux-kernel&m=122781805620212&w=4
> Handled-By      : Takashi Iwai <tiwai@suse.de>
>
>
>

Re: [Bug #12426] TMDC Joystick no longer works in kernel 2.6.28

[Jiri Kosina]

On Wed, 4 Feb 2009, Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
> Subject		: TMDC Joystick no longer works in kernel 2.6.28
> Submitter	: Andrew S. Johnson <andy-9eXmkf4BiQ2aMJb+Lgu22Q@public.gmane.org>
> Date		: 2009-01-10 21:53 (26 days old)
> References	: http://marc.info/?l=linux-kernel&m=123162486415366&w=4

I asked [1] the Submitter some time ago to check whether reverting a 
particular commit fixes the issue, but never heard back.

[1] http://lkml.org/lkml/2009/1/26/70

-- 
Jiri Kosina
SUSE Labs

Re: [Bug #12426] TMDC Joystick no longer works in kernel 2.6.28

[Jiri Kosina]

On Wed, 4 Feb 2009, Rafael J. Wysocki wrote:

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
> Subject		: TMDC Joystick no longer works in kernel 2.6.28
> Submitter	: Andrew S. Johnson <andy@asjohnson.com>
> Date		: 2009-01-10 21:53 (26 days old)
> References	: http://marc.info/?l=linux-kernel&m=123162486415366&w=4

I asked [1] the Submitter some time ago to check whether reverting a 
particular commit fixes the issue, but never heard back.

[1] http://lkml.org/lkml/2009/1/26/70

-- 
Jiri Kosina
SUSE Labs

Re: [Bug #12396] hwinfo problem since 2.6.28

[Beschorner Daniel]

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it 
> still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12396
> Subject		: hwinfo problem since 2.6.28
> Submitter	: Beschorner Daniel <Daniel.Beschorner-cdG02ZADnvLQT0dZR+AlfA@public.gmane.org>
> Date		: 2009-01-06 8:53 (30 days old)
> References	: http://marc.info/?l=linux-kernel&m=123123277800835&w=4
> Handled-By	: Suresh Siddha <suresh.b.siddha-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Patch		: http://marc.info/?l=linux-kernel&m=123154005127497&w=4

Fixed with 2.6.28.3.

Daniel

Re: [Bug #12396] hwinfo problem since 2.6.28

[Beschorner Daniel]

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it 
> still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12396
> Subject		: hwinfo problem since 2.6.28
> Submitter	: Beschorner Daniel <Daniel.Beschorner@facton.com>
> Date		: 2009-01-06 8:53 (30 days old)
> References	: http://marc.info/?l=linux-kernel&m=123123277800835&w=4
> Handled-By	: Suresh Siddha <suresh.b.siddha@intel.com>
> Patch		: http://marc.info/?l=linux-kernel&m=123154005127497&w=4

Fixed with 2.6.28.3.

Daniel

Re: [Bug #12159] 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver

[Rafael J. Wysocki]

On Wednesday 04 February 2009, Miles Lane wrote:
> This bug is fixed in Linus' tree, afaict.

Closed already.

Thanks,
Rafael


> On Wed, Feb 4, 2009 at 5:58 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12159
> > Subject         : 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver
> > Submitter       : Miles Lane <miles.lane-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Date            : 2008-11-27 20:33 (70 days old)
> > References      : http://marc.info/?l=linux-kernel&m=122781805620212&w=4
> > Handled-By      : Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>

Re: [Bug #12159] 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver

[Rafael J. Wysocki]

On Wednesday 04 February 2009, Miles Lane wrote:
> This bug is fixed in Linus' tree, afaict.

Closed already.

Thanks,
Rafael


> On Wed, Feb 4, 2009 at 5:58 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12159
> > Subject         : 2.6.28-rc6-git1 -- No sound produced from Intel HDA ALSA driver
> > Submitter       : Miles Lane <miles.lane@gmail.com>
> > Date            : 2008-11-27 20:33 (70 days old)
> > References      : http://marc.info/?l=linux-kernel&m=122781805620212&w=4
> > Handled-By      : Takashi Iwai <tiwai@suse.de>

Re: [Bug #12396] hwinfo problem since 2.6.28

[Rafael J. Wysocki]

On Wednesday 04 February 2009, Beschorner Daniel wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it 
> > still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12396
> > Subject		: hwinfo problem since 2.6.28
> > Submitter	: Beschorner Daniel <Daniel.Beschorner-cdG02ZADnvLQT0dZR+AlfA@public.gmane.org>
> > Date		: 2009-01-06 8:53 (30 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123123277800835&w=4
> > Handled-By	: Suresh Siddha <suresh.b.siddha-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > Patch		: http://marc.info/?l=linux-kernel&m=123154005127497&w=4
> 
> Fixed with 2.6.28.3.

Thanks, closed.

Rafael

Re: [Bug #12396] hwinfo problem since 2.6.28

[Rafael J. Wysocki]

On Wednesday 04 February 2009, Beschorner Daniel wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it 
> > still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12396
> > Subject		: hwinfo problem since 2.6.28
> > Submitter	: Beschorner Daniel <Daniel.Beschorner@facton.com>
> > Date		: 2009-01-06 8:53 (30 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123123277800835&w=4
> > Handled-By	: Suresh Siddha <suresh.b.siddha@intel.com>
> > Patch		: http://marc.info/?l=linux-kernel&m=123154005127497&w=4
> 
> Fixed with 2.6.28.3.

Thanks, closed.

Rafael

Re: [Bug #12426] TMDC Joystick no longer works in kernel 2.6.28

[Rafael J. Wysocki]

On Wednesday 04 February 2009, Jiri Kosina wrote:
> On Wed, 4 Feb 2009, Rafael J. Wysocki wrote:
> 
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
> > Subject		: TMDC Joystick no longer works in kernel 2.6.28
> > Submitter	: Andrew S. Johnson <andy-9eXmkf4BiQ2aMJb+Lgu22Q@public.gmane.org>
> > Date		: 2009-01-10 21:53 (26 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123162486415366&w=4
> 
> I asked [1] the Submitter some time ago to check whether reverting a 
> particular commit fixes the issue, but never heard back.
> 
> [1] http://lkml.org/lkml/2009/1/26/70

Rejected as "insufficient data" and closed.

Thanks,
Rafael

Re: [Bug #12426] TMDC Joystick no longer works in kernel 2.6.28

[Rafael J. Wysocki]

On Wednesday 04 February 2009, Jiri Kosina wrote:
> On Wed, 4 Feb 2009, Rafael J. Wysocki wrote:
> 
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
> > Subject		: TMDC Joystick no longer works in kernel 2.6.28
> > Submitter	: Andrew S. Johnson <andy@asjohnson.com>
> > Date		: 2009-01-10 21:53 (26 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123162486415366&w=4
> 
> I asked [1] the Submitter some time ago to check whether reverting a 
> particular commit fixes the issue, but never heard back.
> 
> [1] http://lkml.org/lkml/2009/1/26/70

Rejected as "insufficient data" and closed.

Thanks,
Rafael

Re: [Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Theodore Tso]

On Wed, Feb 04, 2009 at 11:58:33AM +0100, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
> Subject		: journal activity on inactive partition causes inactive harddrive spinup
> Submitter	: C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
> Date		: 2008-12-14 11:39 (53 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
> Handled-By	: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Patches against ext3 have been posted by Jan Kara and have been sucked
into the mm tree.  I don't know if Andrew is planning on waiting until
the next merge window, or is planning on pushing it sooner given that
it is a regression.  (These supercede the ones currently posted by
Eric in the BZ entry.)

Similar patches have been posted against ext4, and I will be handling
them in the ext4 tree.

						- Ted

Re: [Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Theodore Tso]

On Wed, Feb 04, 2009 at 11:58:33AM +0100, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
> Subject		: journal activity on inactive partition causes inactive harddrive spinup
> Submitter	: C Sights <csights@fastmail.fm>
> Date		: 2008-12-14 11:39 (53 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
> Handled-By	: Eric Sandeen <sandeen@redhat.com>

Patches against ext3 have been posted by Jan Kara and have been sucked
into the mm tree.  I don't know if Andrew is planning on waiting until
the next merge window, or is planning on pushing it sooner given that
it is a regression.  (These supercede the ones currently posted by
Eric in the BZ entry.)

Similar patches have been posted against ext4, and I will be handling
them in the ext4 tree.

						- Ted

Re: [Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Andrew Morton]

On Wed, 4 Feb 2009 21:00:13 -0500 Theodore Tso <tytso-3s7WtUTddSA@public.gmane.org> wrote:

> On Wed, Feb 04, 2009 at 11:58:33AM +0100, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
> > Subject		: journal activity on inactive partition causes inactive harddrive spinup
> > Submitter	: C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
> > Date		: 2008-12-14 11:39 (53 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
> > Handled-By	: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> 
> Patches against ext3 have been posted by Jan Kara and have been sucked
> into the mm tree.  I don't know if Andrew is planning on waiting until
> the next merge window, or is planning on pushing it sooner given that
> it is a regression.

Yes, I have jbd-fix-return-value-of-journal_start_commit.patch and
revert-ext3-wait-on-all-pending-commits-in-ext3_sync_fs.patch queued
for 2.6.29.

The secret algorithm for determining this is to peek in the series file
(http://userweb.kernel.org/~akpm/mmotm/series) and see where I positioned the
patch:

   #
-> # more 2.6.29 queue:
   #
   # me:
   #
   migration-migrate_vmas-should-check-vma.patch
   rtc-update-maintainership-of-pxa-rtc-driver.patch
   lxfb-properly-alloc-cmap-in-all-cases-and-dont-leak-the-memory.patch
   gxfb-properly-alloc-cmap-and-plug-cmap-leak.patch
   gx1fb-properly-alloc-cmap-and-plug-cmap-leak.patch
   mm-fix-dirty_bytes-dirty_background_bytes-sysctls-on-64bit-arches.patch
   mm-fix-dirty_bytes-dirty_background_bytes-sysctls-on-64bit-arches-fix.patch
-> jbd-fix-return-value-of-journal_start_commit.patch
-> revert-ext3-wait-on-all-pending-commits-in-ext3_sync_fs.patch
   writeback-fix-nr_to_write-counter.patch
   
   

Re: [Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Andrew Morton]

On Wed, 4 Feb 2009 21:00:13 -0500 Theodore Tso <tytso@mit.edu> wrote:

> On Wed, Feb 04, 2009 at 11:58:33AM +0100, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
> > Subject		: journal activity on inactive partition causes inactive harddrive spinup
> > Submitter	: C Sights <csights@fastmail.fm>
> > Date		: 2008-12-14 11:39 (53 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
> > Handled-By	: Eric Sandeen <sandeen@redhat.com>
> 
> Patches against ext3 have been posted by Jan Kara and have been sucked
> into the mm tree.  I don't know if Andrew is planning on waiting until
> the next merge window, or is planning on pushing it sooner given that
> it is a regression.

Yes, I have jbd-fix-return-value-of-journal_start_commit.patch and
revert-ext3-wait-on-all-pending-commits-in-ext3_sync_fs.patch queued
for 2.6.29.

The secret algorithm for determining this is to peek in the series file
(http://userweb.kernel.org/~akpm/mmotm/series) and see where I positioned the
patch:

   #
-> # more 2.6.29 queue:
   #
   # me:
   #
   migration-migrate_vmas-should-check-vma.patch
   rtc-update-maintainership-of-pxa-rtc-driver.patch
   lxfb-properly-alloc-cmap-in-all-cases-and-dont-leak-the-memory.patch
   gxfb-properly-alloc-cmap-and-plug-cmap-leak.patch
   gx1fb-properly-alloc-cmap-and-plug-cmap-leak.patch
   mm-fix-dirty_bytes-dirty_background_bytes-sysctls-on-64bit-arches.patch
   mm-fix-dirty_bytes-dirty_background_bytes-sysctls-on-64bit-arches-fix.patch
-> jbd-fix-return-value-of-journal_start_commit.patch
-> revert-ext3-wait-on-all-pending-commits-in-ext3_sync_fs.patch
   writeback-fix-nr_to_write-counter.patch
   
   

Re: [Bug #12393] debugging in dosemu causes lots of 'scheduling while atomic'

[Michal Suchanek]

As I said earlier I have received a patch that I applied locally and
that fixes the problem.

As to if and when the patch actually appears in the kernel is out of
my control, and nobody told me that it was applied.

If you believe it was applied to a kernel version that is readily
available for download I am wiling to test such version.

Thanks

Michal

2009/2/4 Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12393
> Subject         : debugging in dosemu causes lots of 'scheduling while atomic'
> Submitter       : Michal Suchanek <hramrach-aRb0bU7PRFPrBKCeMvbIDA@public.gmane.org>
> Date            : 2009-01-09 07:28 (27 days old)
>
>
>

Re: [Bug #12393] debugging in dosemu causes lots of 'scheduling while atomic'

[Michal Suchanek]

As I said earlier I have received a patch that I applied locally and
that fixes the problem.

As to if and when the patch actually appears in the kernel is out of
my control, and nobody told me that it was applied.

If you believe it was applied to a kernel version that is readily
available for download I am wiling to test such version.

Thanks

Michal

2009/2/4 Rafael J. Wysocki <rjw@sisk.pl>:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12393
> Subject         : debugging in dosemu causes lots of 'scheduling while atomic'
> Submitter       : Michal Suchanek <hramrach@centrum.cz>
> Date            : 2009-01-09 07:28 (27 days old)
>
>
>

Re: [Bug #12612] hard lockup when interrupting cdda2wav

[Matthias Reichl]

On Wed, Feb 04, 2009 at 11:58:51AM +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12612
> Subject		: hard lockup when interrupting cdda2wav
> Submitter	: Matthias Reichl <hias-vtPv7MOkFPkAvxtiuMwx3w@public.gmane.org>
> Date		: 2009-01-28 16:41 (8 days old)
> References	: http://marc.info/?l=linux-kernel&m=123316111415677&w=4
> Handled-By	: FUJITA Tomonori <fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>

This bug is still present in 2.6.28.3.

so long,

Hias

=============================================
[ INFO: possible recursive locking detected ]
2.6.28.3-dbg #1
---------------------------------------------
swapper/0 is trying to acquire lock:
 (&q->__queue_lock){.+..}, at: [<ffffffff8040e5f5>] blk_put_request+0x25/0x60

but task is already holding lock:
 (&q->__queue_lock){.+..}, at: [<ffffffff8040e4da>] blk_end_io+0x5a/0xa0

other info that might help us debug this:
1 lock held by swapper/0:
 #0:  (&q->__queue_lock){.+..}, at: [<ffffffff8040e4da>] blk_end_io+0x5a/0xa0

stack backtrace:
Pid: 0, comm: swapper Not tainted 2.6.28.3-dbg #1
Call Trace:
 <IRQ>  [<ffffffff8026cc87>] __lock_acquire+0x1797/0x1930
 [<ffffffff806abd7b>] error_exit+0x29/0xa9
 [<ffffffff80521e20>] sg_rq_end_io+0x0/0x2e0
 [<ffffffff8026ceba>] lock_acquire+0x9a/0xe0
 [<ffffffff8040e5f5>] blk_put_request+0x25/0x60
 [<ffffffff806ab763>] _spin_lock_irqsave+0x43/0x90
 [<ffffffff8040e5f5>] blk_put_request+0x25/0x60
 [<ffffffff8040e5f5>] blk_put_request+0x25/0x60
 [<ffffffff80520974>] sg_finish_rem_req+0xa4/0x100
 [<ffffffff80522098>] sg_rq_end_io+0x278/0x2e0
 [<ffffffff8040e281>] end_that_request_last+0x61/0x260
 [<ffffffff8040e4e8>] blk_end_io+0x68/0xa0
 [<ffffffff80508061>] scsi_end_request+0x41/0xd0
 [<ffffffff80508750>] scsi_io_completion+0x130/0x470
 [<ffffffff804133e5>] blk_done_softirq+0x75/0x90
 [<ffffffff802488ab>] __do_softirq+0x9b/0x180
 [<ffffffff80213df3>] native_sched_clock+0x13/0x70
 [<ffffffff8020d6ec>] call_softirq+0x1c/0x30
 [<ffffffff8020f175>] do_softirq+0x65/0xa0
 [<ffffffff80248345>] irq_exit+0xa5/0xb0
 [<ffffffff8020f467>] do_IRQ+0x107/0x1d0
 [<ffffffff8020c7fb>] ret_from_intr+0x0/0xf
 <EOI>  [<ffffffff80214ba6>] mwait_idle+0x56/0x60
 [<ffffffff80214b9d>] mwait_idle+0x4d/0x60
 [<ffffffff8020b353>] cpu_idle+0x63/0xc0

Re: [Bug #12612] hard lockup when interrupting cdda2wav

[Matthias Reichl]

On Wed, Feb 04, 2009 at 11:58:51AM +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12612
> Subject		: hard lockup when interrupting cdda2wav
> Submitter	: Matthias Reichl <hias@horus.com>
> Date		: 2009-01-28 16:41 (8 days old)
> References	: http://marc.info/?l=linux-kernel&m=123316111415677&w=4
> Handled-By	: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>

This bug is still present in 2.6.28.3.

so long,

Hias

=============================================
[ INFO: possible recursive locking detected ]
2.6.28.3-dbg #1
---------------------------------------------
swapper/0 is trying to acquire lock:
 (&q->__queue_lock){.+..}, at: [<ffffffff8040e5f5>] blk_put_request+0x25/0x60

but task is already holding lock:
 (&q->__queue_lock){.+..}, at: [<ffffffff8040e4da>] blk_end_io+0x5a/0xa0

other info that might help us debug this:
1 lock held by swapper/0:
 #0:  (&q->__queue_lock){.+..}, at: [<ffffffff8040e4da>] blk_end_io+0x5a/0xa0

stack backtrace:
Pid: 0, comm: swapper Not tainted 2.6.28.3-dbg #1
Call Trace:
 <IRQ>  [<ffffffff8026cc87>] __lock_acquire+0x1797/0x1930
 [<ffffffff806abd7b>] error_exit+0x29/0xa9
 [<ffffffff80521e20>] sg_rq_end_io+0x0/0x2e0
 [<ffffffff8026ceba>] lock_acquire+0x9a/0xe0
 [<ffffffff8040e5f5>] blk_put_request+0x25/0x60
 [<ffffffff806ab763>] _spin_lock_irqsave+0x43/0x90
 [<ffffffff8040e5f5>] blk_put_request+0x25/0x60
 [<ffffffff8040e5f5>] blk_put_request+0x25/0x60
 [<ffffffff80520974>] sg_finish_rem_req+0xa4/0x100
 [<ffffffff80522098>] sg_rq_end_io+0x278/0x2e0
 [<ffffffff8040e281>] end_that_request_last+0x61/0x260
 [<ffffffff8040e4e8>] blk_end_io+0x68/0xa0
 [<ffffffff80508061>] scsi_end_request+0x41/0xd0
 [<ffffffff80508750>] scsi_io_completion+0x130/0x470
 [<ffffffff804133e5>] blk_done_softirq+0x75/0x90
 [<ffffffff802488ab>] __do_softirq+0x9b/0x180
 [<ffffffff80213df3>] native_sched_clock+0x13/0x70
 [<ffffffff8020d6ec>] call_softirq+0x1c/0x30
 [<ffffffff8020f175>] do_softirq+0x65/0xa0
 [<ffffffff80248345>] irq_exit+0xa5/0xb0
 [<ffffffff8020f467>] do_IRQ+0x107/0x1d0
 [<ffffffff8020c7fb>] ret_from_intr+0x0/0xf
 <EOI>  [<ffffffff80214ba6>] mwait_idle+0x56/0x60
 [<ffffffff80214b9d>] mwait_idle+0x4d/0x60
 [<ffffffff8020b353>] cpu_idle+0x63/0xc0

Re: [Bug #12393] debugging in dosemu causes lots of 'scheduling while atomic'

[Rafael J. Wysocki]

On Thursday 05 February 2009, Michal Suchanek wrote:
> As I said earlier I have received a patch that I applied locally and
> that fixes the problem.
> 
> As to if and when the patch actually appears in the kernel is out of
> my control, and nobody told me that it was applied.
> 
> If you believe it was applied to a kernel version that is readily
> available for download I am wiling to test such version.

I don't at the moment.

Can you send me a URL to the patch, please?

Rafael

Re: [Bug #12612] hard lockup when interrupting cdda2wav

[Rafael J. Wysocki]

On Thursday 05 February 2009, Matthias Reichl wrote:
> On Wed, Feb 04, 2009 at 11:58:51AM +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12612
> > Subject		: hard lockup when interrupting cdda2wav
> > Submitter	: Matthias Reichl <hias@horus.com>
> > Date		: 2009-01-28 16:41 (8 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123316111415677&w=4
> > Handled-By	: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> 
> This bug is still present in 2.6.28.3.
> 
> =============================================
> [ INFO: possible recursive locking detected ]
> 2.6.28.3-dbg #1
> ---------------------------------------------
> swapper/0 is trying to acquire lock:
>  (&q->__queue_lock){.+..}, at: [<ffffffff8040e5f5>] blk_put_request+0x25/0x60
> 
> but task is already holding lock:
>  (&q->__queue_lock){.+..}, at: [<ffffffff8040e4da>] blk_end_io+0x5a/0xa0
> 
> other info that might help us debug this:
> 1 lock held by swapper/0:
>  #0:  (&q->__queue_lock){.+..}, at: [<ffffffff8040e4da>] blk_end_io+0x5a/0xa0
> 
> stack backtrace:
> Pid: 0, comm: swapper Not tainted 2.6.28.3-dbg #1
> Call Trace:
>  <IRQ>  [<ffffffff8026cc87>] __lock_acquire+0x1797/0x1930
>  [<ffffffff806abd7b>] error_exit+0x29/0xa9
>  [<ffffffff80521e20>] sg_rq_end_io+0x0/0x2e0
>  [<ffffffff8026ceba>] lock_acquire+0x9a/0xe0
>  [<ffffffff8040e5f5>] blk_put_request+0x25/0x60
>  [<ffffffff806ab763>] _spin_lock_irqsave+0x43/0x90
>  [<ffffffff8040e5f5>] blk_put_request+0x25/0x60
>  [<ffffffff8040e5f5>] blk_put_request+0x25/0x60
>  [<ffffffff80520974>] sg_finish_rem_req+0xa4/0x100
>  [<ffffffff80522098>] sg_rq_end_io+0x278/0x2e0
>  [<ffffffff8040e281>] end_that_request_last+0x61/0x260
>  [<ffffffff8040e4e8>] blk_end_io+0x68/0xa0
>  [<ffffffff80508061>] scsi_end_request+0x41/0xd0
>  [<ffffffff80508750>] scsi_io_completion+0x130/0x470
>  [<ffffffff804133e5>] blk_done_softirq+0x75/0x90
>  [<ffffffff802488ab>] __do_softirq+0x9b/0x180
>  [<ffffffff80213df3>] native_sched_clock+0x13/0x70
>  [<ffffffff8020d6ec>] call_softirq+0x1c/0x30
>  [<ffffffff8020f175>] do_softirq+0x65/0xa0
>  [<ffffffff80248345>] irq_exit+0xa5/0xb0
>  [<ffffffff8020f467>] do_IRQ+0x107/0x1d0
>  [<ffffffff8020c7fb>] ret_from_intr+0x0/0xf
>  <EOI>  [<ffffffff80214ba6>] mwait_idle+0x56/0x60
>  [<ffffffff80214b9d>] mwait_idle+0x4d/0x60
>  [<ffffffff8020b353>] cpu_idle+0x63/0xc0

Thanks for the update.

Rafael

Re: [Bug #12393] debugging in dosemu causes lots of 'scheduling while atomic'

[Ray Lee]

On Thu, Feb 5, 2009 at 8:09 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> On Thursday 05 February 2009, Michal Suchanek wrote:
>> As I said earlier I have received a patch that I applied locally and
>> that fixes the problem.
>>
>> As to if and when the patch actually appears in the kernel is out of
>> my control, and nobody told me that it was applied.
>>
>> If you believe it was applied to a kernel version that is readily
>> available for download I am wiling to test such version.
>
> I don't at the moment.
>
> Can you send me a URL to the patch, please?

http://lkml.org/lkml/2009/1/13/445

Re: [Bug #12393] debugging in dosemu causes lots of 'scheduling while atomic'

[Ray Lee]

On Thu, Feb 5, 2009 at 8:09 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Thursday 05 February 2009, Michal Suchanek wrote:
>> As I said earlier I have received a patch that I applied locally and
>> that fixes the problem.
>>
>> As to if and when the patch actually appears in the kernel is out of
>> my control, and nobody told me that it was applied.
>>
>> If you believe it was applied to a kernel version that is readily
>> available for download I am wiling to test such version.
>
> I don't at the moment.
>
> Can you send me a URL to the patch, please?

http://lkml.org/lkml/2009/1/13/445

Re: [Bug #12465] KVM guests stalling on 2.6.28 (bisected)

[Kevin Shanahan]

On Wed, 2009-02-04 at 11:58 +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12465
> Subject		: KVM guests stalling on 2.6.28 (bisected)
> Submitter	: Kevin Shanahan <kmshanah-biM/RbsGxha6c6uEtOJ/EA@public.gmane.org>
> Date		: 2009-01-17 03:37 (19 days old)

Yes, this should still be listed.

Please remove kmshanah-IiIpDuVlHfMLO379cgqW9odd74u8MsAO@public.gmane.org from the CC list.

Thanks,
Kevin.

Re: [Bug #12465] KVM guests stalling on 2.6.28 (bisected)

[Kevin Shanahan]

On Wed, 2009-02-04 at 11:58 +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.27 and 2.6.28.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> be listed and let me know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12465
> Subject		: KVM guests stalling on 2.6.28 (bisected)
> Submitter	: Kevin Shanahan <kmshanah@ucwb.org.au>
> Date		: 2009-01-17 03:37 (19 days old)

Yes, this should still be listed.

Please remove kmshanah@flexo.wumi.org.au from the CC list.

Thanks,
Kevin.

Re: [Bug #12465] KVM guests stalling on 2.6.28 (bisected)

[Rafael J. Wysocki]

On Thursday 05 February 2009, Kevin Shanahan wrote:
> On Wed, 2009-02-04 at 11:58 +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12465
> > Subject		: KVM guests stalling on 2.6.28 (bisected)
> > Submitter	: Kevin Shanahan <kmshanah-biM/RbsGxha6c6uEtOJ/EA@public.gmane.org>
> > Date		: 2009-01-17 03:37 (19 days old)
> 
> Yes, this should still be listed.

Thanks for the update.
 
> Please remove kmshanah-IiIpDuVlHfMLO379cgqW9odd74u8MsAO@public.gmane.org from the CC list.

It gets added because it is present in the Author: field in
http://bugzilla.kernel.org/show_bug.cgi?id=12465#c5

This is how the script works, sorry for the inconvenience.

Rafael


> 
> Thanks,
> Kevin.
> 
> 
> 
> 


-- 
Everyone knows that debugging is twice as hard as writing a program
in the first place.  So if you're as clever as you can be when you write it,
how will you ever debug it? --- Brian Kernighan

Re: [Bug #12465] KVM guests stalling on 2.6.28 (bisected)

[Rafael J. Wysocki]

On Thursday 05 February 2009, Kevin Shanahan wrote:
> On Wed, 2009-02-04 at 11:58 +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12465
> > Subject		: KVM guests stalling on 2.6.28 (bisected)
> > Submitter	: Kevin Shanahan <kmshanah@ucwb.org.au>
> > Date		: 2009-01-17 03:37 (19 days old)
> 
> Yes, this should still be listed.

Thanks for the update.
 
> Please remove kmshanah@flexo.wumi.org.au from the CC list.

It gets added because it is present in the Author: field in
http://bugzilla.kernel.org/show_bug.cgi?id=12465#c5

This is how the script works, sorry for the inconvenience.

Rafael


> 
> Thanks,
> Kevin.
> 
> 
> 
> 


-- 
Everyone knows that debugging is twice as hard as writing a program
in the first place.  So if you're as clever as you can be when you write it,
how will you ever debug it? --- Brian Kernighan

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Philipp Matthias Hahn]

Hello!

On Thu, Jan 29, 2009 at 10:53:40PM -0800, Yinghai Lu wrote:
> can not find the reason why the WOL doesn't work...
> 
> please post
> 1. boot log for just after AC is pluged-in... ===> you should have
> "nv_probe: set workaround bit for reversed mac addr"
> 2. and boot log after boot from WOL...==> you have have "nv_probe: set
> workaround bit for reversed mac addr" too.

On Wed, Feb 04, 2009 at 11:58:53AM +0100, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12614
> Subject		: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
> Submitter	: Philipp Matthias Hahn <pmhahn@titan.lahn.de>
> Date		: 2009-01-29 6:31 (7 days old)
> References	: http://marc.info/?l=linux-kernel&m=123321232825316&w=4
> Handled-By	: Yinghai Lu <yinghai@kernel.org>
> Patch		: http://marc.info/?l=linux-kernel&m=123330459229248&w=4

Strage, at the moment I can't seem to reproduce the problem. I've
switched back to the version of 2.6.28.3 and now it seems to work.
I'll continue with tesing.

Some additional data:
The BIOS-upgrade tool (Afud408.exe) resets the MAC address. I had to run
the tool a second time to re-programm the MAC-address using its /M
option. I useed the unreversed MAC-address back than.
I also tried the reversed address once, but after that forcedeth.c
complained about a wrong MAC-address.

If I completely turn off the power (pull the plug), WOL doesn't work,
even when it's enabled in the BIOS.

Only after I'v started Linux, do "echo NMAC > /proc/acpi/wakeup" and
"ethtool -s eth0 wol g" does it work again.

Nether the less here's the output of dmesg:
        forcedeth: Reverse Engineered nFoce ethernet driver. Version 0.61.
        ACPI: PCI Interrupt Link [LMAC] enables at IRQ 23
        forcedeth: 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
        forcedeth: 0000:00:14.0: setting latency timer to 64
*       nv_probe: MAC_ADDR_REV ELSE
        nv_probe: set workaround bit for reversed mac addr
        forcedeth: 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:db:f2:e1:35
        forcedeth: 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3
The line maked * was inserted by me in the source file for my debugging.

BYtE
Philipp Hahn
-- 
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Yinghai Lu]

On Thu, Feb 5, 2009 at 3:23 PM, Philipp Matthias Hahn
<pmhahn-u4khhh1J0LzF41mA0N3lWw@public.gmane.org> wrote:
> Hello!
>
> On Thu, Jan 29, 2009 at 10:53:40PM -0800, Yinghai Lu wrote:
>> can not find the reason why the WOL doesn't work...
>>
>> please post
>> 1. boot log for just after AC is pluged-in... ===> you should have
>> "nv_probe: set workaround bit for reversed mac addr"
>> 2. and boot log after boot from WOL...==> you have have "nv_probe: set
>> workaround bit for reversed mac addr" too.
>
> On Wed, Feb 04, 2009 at 11:58:53AM +0100, Rafael J. Wysocki wrote:
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=12614
>> Subject               : WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
>> Submitter     : Philipp Matthias Hahn <pmhahn-u4khhh1J0LzF41mA0N3lWw@public.gmane.org>
>> Date          : 2009-01-29 6:31 (7 days old)
>> References    : http://marc.info/?l=linux-kernel&m=123321232825316&w=4
>> Handled-By    : Yinghai Lu <yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>> Patch         : http://marc.info/?l=linux-kernel&m=123330459229248&w=4
>
> Strage, at the moment I can't seem to reproduce the problem. I've
> switched back to the version of 2.6.28.3 and now it seems to work.
> I'll continue with tesing.
>
> Some additional data:
> The BIOS-upgrade tool (Afud408.exe) resets the MAC address. I had to run
> the tool a second time to re-programm the MAC-address using its /M
> option. I useed the unreversed MAC-address back than.
> I also tried the reversed address once, but after that forcedeth.c
> complained about a wrong MAC-address.
>
> If I completely turn off the power (pull the plug), WOL doesn't work,
> even when it's enabled in the BIOS.
>
> Only after I'v started Linux, do "echo NMAC > /proc/acpi/wakeup" and
> "ethtool -s eth0 wol g" does it work again.
>
> Nether the less here's the output of dmesg:
>        forcedeth: Reverse Engineered nFoce ethernet driver. Version 0.61.
>        ACPI: PCI Interrupt Link [LMAC] enables at IRQ 23
>        forcedeth: 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
>        forcedeth: 0000:00:14.0: setting latency timer to 64
> *       nv_probe: MAC_ADDR_REV ELSE
>        nv_probe: set workaround bit for reversed mac addr

that means your BIOS doesn't reverse mac addr.
this is the one for new BIOS or old BIOS?

YH

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Yinghai Lu]

On Thu, Feb 5, 2009 at 3:23 PM, Philipp Matthias Hahn
<pmhahn@titan.lahn.de> wrote:
> Hello!
>
> On Thu, Jan 29, 2009 at 10:53:40PM -0800, Yinghai Lu wrote:
>> can not find the reason why the WOL doesn't work...
>>
>> please post
>> 1. boot log for just after AC is pluged-in... ===> you should have
>> "nv_probe: set workaround bit for reversed mac addr"
>> 2. and boot log after boot from WOL...==> you have have "nv_probe: set
>> workaround bit for reversed mac addr" too.
>
> On Wed, Feb 04, 2009 at 11:58:53AM +0100, Rafael J. Wysocki wrote:
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=12614
>> Subject               : WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
>> Submitter     : Philipp Matthias Hahn <pmhahn@titan.lahn.de>
>> Date          : 2009-01-29 6:31 (7 days old)
>> References    : http://marc.info/?l=linux-kernel&m=123321232825316&w=4
>> Handled-By    : Yinghai Lu <yinghai@kernel.org>
>> Patch         : http://marc.info/?l=linux-kernel&m=123330459229248&w=4
>
> Strage, at the moment I can't seem to reproduce the problem. I've
> switched back to the version of 2.6.28.3 and now it seems to work.
> I'll continue with tesing.
>
> Some additional data:
> The BIOS-upgrade tool (Afud408.exe) resets the MAC address. I had to run
> the tool a second time to re-programm the MAC-address using its /M
> option. I useed the unreversed MAC-address back than.
> I also tried the reversed address once, but after that forcedeth.c
> complained about a wrong MAC-address.
>
> If I completely turn off the power (pull the plug), WOL doesn't work,
> even when it's enabled in the BIOS.
>
> Only after I'v started Linux, do "echo NMAC > /proc/acpi/wakeup" and
> "ethtool -s eth0 wol g" does it work again.
>
> Nether the less here's the output of dmesg:
>        forcedeth: Reverse Engineered nFoce ethernet driver. Version 0.61.
>        ACPI: PCI Interrupt Link [LMAC] enables at IRQ 23
>        forcedeth: 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
>        forcedeth: 0000:00:14.0: setting latency timer to 64
> *       nv_probe: MAC_ADDR_REV ELSE
>        nv_probe: set workaround bit for reversed mac addr

that means your BIOS doesn't reverse mac addr.
this is the one for new BIOS or old BIOS?

YH

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Rafael J. Wysocki]

On Friday 06 February 2009, Philipp Matthias Hahn wrote:
> Hello!
> 
> On Thu, Jan 29, 2009 at 10:53:40PM -0800, Yinghai Lu wrote:
> > can not find the reason why the WOL doesn't work...
> > 
> > please post
> > 1. boot log for just after AC is pluged-in... ===> you should have
> > "nv_probe: set workaround bit for reversed mac addr"
> > 2. and boot log after boot from WOL...==> you have have "nv_probe: set
> > workaround bit for reversed mac addr" too.
> 
> On Wed, Feb 04, 2009 at 11:58:53AM +0100, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12614
> > Subject		: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
> > Submitter	: Philipp Matthias Hahn <pmhahn-u4khhh1J0LzF41mA0N3lWw@public.gmane.org>
> > Date		: 2009-01-29 6:31 (7 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123321232825316&w=4
> > Handled-By	: Yinghai Lu <yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> > Patch		: http://marc.info/?l=linux-kernel&m=123330459229248&w=4
> 
> Strage, at the moment I can't seem to reproduce the problem. I've
> switched back to the version of 2.6.28.3 and now it seems to work.
> I'll continue with tesing.

OK, but for now I'll close the bug as unreproducible.

> Some additional data:
> The BIOS-upgrade tool (Afud408.exe) resets the MAC address. I had to run
> the tool a second time to re-programm the MAC-address using its /M
> option. I useed the unreversed MAC-address back than.
> I also tried the reversed address once, but after that forcedeth.c
> complained about a wrong MAC-address.
> 
> If I completely turn off the power (pull the plug), WOL doesn't work,
> even when it's enabled in the BIOS.
> 
> Only after I'v started Linux, do "echo NMAC > /proc/acpi/wakeup" and
> "ethtool -s eth0 wol g" does it work again.

The "echo NMAC > /proc/acpi/wakeup" thing shouldn't be necessary if you do
"ethtool -s eth0 wol g".

Thanks,
Rafael

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Rafael J. Wysocki]

On Friday 06 February 2009, Philipp Matthias Hahn wrote:
> Hello!
> 
> On Thu, Jan 29, 2009 at 10:53:40PM -0800, Yinghai Lu wrote:
> > can not find the reason why the WOL doesn't work...
> > 
> > please post
> > 1. boot log for just after AC is pluged-in... ===> you should have
> > "nv_probe: set workaround bit for reversed mac addr"
> > 2. and boot log after boot from WOL...==> you have have "nv_probe: set
> > workaround bit for reversed mac addr" too.
> 
> On Wed, Feb 04, 2009 at 11:58:53AM +0100, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12614
> > Subject		: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
> > Submitter	: Philipp Matthias Hahn <pmhahn@titan.lahn.de>
> > Date		: 2009-01-29 6:31 (7 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123321232825316&w=4
> > Handled-By	: Yinghai Lu <yinghai@kernel.org>
> > Patch		: http://marc.info/?l=linux-kernel&m=123330459229248&w=4
> 
> Strage, at the moment I can't seem to reproduce the problem. I've
> switched back to the version of 2.6.28.3 and now it seems to work.
> I'll continue with tesing.

OK, but for now I'll close the bug as unreproducible.

> Some additional data:
> The BIOS-upgrade tool (Afud408.exe) resets the MAC address. I had to run
> the tool a second time to re-programm the MAC-address using its /M
> option. I useed the unreversed MAC-address back than.
> I also tried the reversed address once, but after that forcedeth.c
> complained about a wrong MAC-address.
> 
> If I completely turn off the power (pull the plug), WOL doesn't work,
> even when it's enabled in the BIOS.
> 
> Only after I'v started Linux, do "echo NMAC > /proc/acpi/wakeup" and
> "ethtool -s eth0 wol g" does it work again.

The "echo NMAC > /proc/acpi/wakeup" thing shouldn't be necessary if you do
"ethtool -s eth0 wol g".

Thanks,
Rafael

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Philipp Matthias Hahn]

Hello!

On Fri, Feb 06, 2009 at 01:13:30AM +0100, Rafael J. Wysocki wrote:
...
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12614
> > > Subject		: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
...
> > Strage, at the moment I can't seem to reproduce the problem. I've
> > switched back to the version of 2.6.28.3 and now it seems to work.
> > I'll continue with tesing.
> 
> OK, but for now I'll close the bug as unreproducible.

Just this morning I had to use the reverted address to wake up my
desktop PC after 6 hours of poweroff.

Yesterdays tests were domething like the following:
	Grub: Linux "loglevel=9 ignore_loglevel break=modules"
	dmesg -c > /dev/null
	modprobe forcedeth
	dmesg
	ethtool -s eth0 wol g
	echo NMAC > /proc/acpi/wakeup
	reboot to Grub using Alt-SysRq-B
	Grub: "halt"
I have to reboot back to Grub, since doing a "poweroff" from initrd or
pressing Alt-SysRq-O seems to turn of WOL.

...
> The "echo NMAC > /proc/acpi/wakeup" thing shouldn't be necessary if you do
> "ethtool -s eth0 wol g".

Will try.

On Thu, Feb 05, 2009 at 03:35:25PM -0800, Yinghai Lu wrote:
> > Nether the less here's the output of dmesg:
> >        forcedeth: Reverse Engineered nFoce ethernet driver. Version 0.61.
> >        ACPI: PCI Interrupt Link [LMAC] enables at IRQ 23
> >        forcedeth: 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
> >        forcedeth: 0000:00:14.0: setting latency timer to 64
> > *       nv_probe: MAC_ADDR_REV ELSE
> >        nv_probe: set workaround bit for reversed mac addr
> 
> that means your BIOS doesn't reverse mac addr.
> this is the one for new BIOS or old BIOS?

This is the new BIOS.

BYtE
Philipp Hahn
-- 
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn-u4khhh1J0LzF41mA0N3lWw@public.gmane.org

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Philipp Matthias Hahn]

Hello!

On Fri, Feb 06, 2009 at 01:13:30AM +0100, Rafael J. Wysocki wrote:
...
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12614
> > > Subject		: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e
...
> > Strage, at the moment I can't seem to reproduce the problem. I've
> > switched back to the version of 2.6.28.3 and now it seems to work.
> > I'll continue with tesing.
> 
> OK, but for now I'll close the bug as unreproducible.

Just this morning I had to use the reverted address to wake up my
desktop PC after 6 hours of poweroff.

Yesterdays tests were domething like the following:
	Grub: Linux "loglevel=9 ignore_loglevel break=modules"
	dmesg -c > /dev/null
	modprobe forcedeth
	dmesg
	ethtool -s eth0 wol g
	echo NMAC > /proc/acpi/wakeup
	reboot to Grub using Alt-SysRq-B
	Grub: "halt"
I have to reboot back to Grub, since doing a "poweroff" from initrd or
pressing Alt-SysRq-O seems to turn of WOL.

...
> The "echo NMAC > /proc/acpi/wakeup" thing shouldn't be necessary if you do
> "ethtool -s eth0 wol g".

Will try.

On Thu, Feb 05, 2009 at 03:35:25PM -0800, Yinghai Lu wrote:
> > Nether the less here's the output of dmesg:
> >        forcedeth: Reverse Engineered nFoce ethernet driver. Version 0.61.
> >        ACPI: PCI Interrupt Link [LMAC] enables at IRQ 23
> >        forcedeth: 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
> >        forcedeth: 0000:00:14.0: setting latency timer to 64
> > *       nv_probe: MAC_ADDR_REV ELSE
> >        nv_probe: set workaround bit for reversed mac addr
> 
> that means your BIOS doesn't reverse mac addr.
> this is the one for new BIOS or old BIOS?

This is the new BIOS.

BYtE
Philipp Hahn
-- 
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Philipp Matthias Hahn]

Hello again!

On Fri, Feb 06, 2009 at 06:33:20AM +0100, Philipp Matthias Hahn wrote:
> Just this morning I had to use the reverted address to wake up my
> desktop PC after 6 hours of poweroff.

I did some structured tesing:

1. WOL does _not_ work at all when I do:
	(grub) boot into initrd
	(initrd) modprobe forcedeth
	(initrd) ethtool -s eth0 wol g
*	(initrd) poweroff

2. WOL does _not_ work at all when I do:
	(grub) boot into initrd
	(initrd) modprobe forcedeth
	(initrd) ethtool -s eth0 wol g
*	(initrd) Alt-SysRq-O

3. WOL works using the _un-reversed_ MAC when I do:
	(grub) boot into initrd
	(initrd) modprobe forcedeth
	(initrd) ethtool -s eth0 wol g
*	(initrd) Alt-SysRq-B
*	(grub) halt

4. WOL works using the _reversed_ MAC when I do:
	(grub) boot into initrd
	(initrd) modprobe forcedeth
	(initrd) ethtool -s eth0 wol g
	(initrd) exit
*	(Debian) poweroff

If I do the poweroff from linux (either initrd or Debian), forcedeth
seems to display some messages just before poweroff. I'll try to get
hands on a Serial-USB-Converter and a NULL-modem-cable to capture it,
since my laptop is legacy-free :-(

BYtE
Philipp Hahn

PS: initrd is actually initramfs, before somebody wonders.
-- 
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn-u4khhh1J0LzF41mA0N3lWw@public.gmane.org

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Philipp Matthias Hahn]

Hello again!

On Fri, Feb 06, 2009 at 06:33:20AM +0100, Philipp Matthias Hahn wrote:
> Just this morning I had to use the reverted address to wake up my
> desktop PC after 6 hours of poweroff.

I did some structured tesing:

1. WOL does _not_ work at all when I do:
	(grub) boot into initrd
	(initrd) modprobe forcedeth
	(initrd) ethtool -s eth0 wol g
*	(initrd) poweroff

2. WOL does _not_ work at all when I do:
	(grub) boot into initrd
	(initrd) modprobe forcedeth
	(initrd) ethtool -s eth0 wol g
*	(initrd) Alt-SysRq-O

3. WOL works using the _un-reversed_ MAC when I do:
	(grub) boot into initrd
	(initrd) modprobe forcedeth
	(initrd) ethtool -s eth0 wol g
*	(initrd) Alt-SysRq-B
*	(grub) halt

4. WOL works using the _reversed_ MAC when I do:
	(grub) boot into initrd
	(initrd) modprobe forcedeth
	(initrd) ethtool -s eth0 wol g
	(initrd) exit
*	(Debian) poweroff

If I do the poweroff from linux (either initrd or Debian), forcedeth
seems to display some messages just before poweroff. I'll try to get
hands on a Serial-USB-Converter and a NULL-modem-cable to capture it,
since my laptop is legacy-free :-(

BYtE
Philipp Hahn

PS: initrd is actually initramfs, before somebody wonders.
-- 
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de

Re: [Bug #12612] hard lockup when interrupting cdda2wav

[FUJITA Tomonori]

On Thu, 5 Feb 2009 14:16:44 +0100
Matthias Reichl <hias-vtPv7MOkFPkAvxtiuMwx3w@public.gmane.org> wrote:

> On Wed, Feb 04, 2009 at 11:58:51AM +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12612
> > Subject		: hard lockup when interrupting cdda2wav
> > Submitter	: Matthias Reichl <hias-vtPv7MOkFPkAvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-01-28 16:41 (8 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123316111415677&w=4
> > Handled-By	: FUJITA Tomonori <fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
> 
> This bug is still present in 2.6.28.3.

There is a fix against scsi-misc:

http://marc.info/?l=linux-scsi&m=123371501613019&w=2

I might need to fix it in a different way though.

There are other pending patches to fix other sg oops in scsi-misc so
the above fix can't be cleanly applied to 2.6.28.X. I'll send a patch
for 2.6.28.X once I get SCSI maintainer's ACK on it.

Sorry for the inconvenience,

Re: [Bug #12612] hard lockup when interrupting cdda2wav

[FUJITA Tomonori]

On Thu, 5 Feb 2009 14:16:44 +0100
Matthias Reichl <hias@horus.com> wrote:

> On Wed, Feb 04, 2009 at 11:58:51AM +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.27 and 2.6.28.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.27 and 2.6.28.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12612
> > Subject		: hard lockup when interrupting cdda2wav
> > Submitter	: Matthias Reichl <hias@horus.com>
> > Date		: 2009-01-28 16:41 (8 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123316111415677&w=4
> > Handled-By	: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> 
> This bug is still present in 2.6.28.3.

There is a fix against scsi-misc:

http://marc.info/?l=linux-scsi&m=123371501613019&w=2

I might need to fix it in a different way though.

There are other pending patches to fix other sg oops in scsi-misc so
the above fix can't be cleanly applied to 2.6.28.X. I'll send a patch
for 2.6.28.X once I get SCSI maintainer's ACK on it.

Sorry for the inconvenience,

Re: [Bug #12405] oops in __bounce_end_io_read under kvm

[Christoph Hellwig]

On Wed, Feb 04, 2009 at 11:58:40AM +0100, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12405
> Subject		: oops in __bounce_end_io_read under kvm
> Submitter	: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
> Date		: 2008-12-26 17:36 (41 days old)
> References	: http://marc.info/?l=linux-kernel&m=123031303400676&w=4
> Handled-By	: Jens Axboe <jens.axboe-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>

Still around.  Btw, I'm not sure it's a regression as I only started
using virtio_blk heavily during the 2.6.28 cycle.

Re: [Bug #12405] oops in __bounce_end_io_read under kvm

[Christoph Hellwig]

On Wed, Feb 04, 2009 at 11:58:40AM +0100, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12405
> Subject		: oops in __bounce_end_io_read under kvm
> Submitter	: Christoph Hellwig <hch@lst.de>
> Date		: 2008-12-26 17:36 (41 days old)
> References	: http://marc.info/?l=linux-kernel&m=123031303400676&w=4
> Handled-By	: Jens Axboe <jens.axboe@oracle.com>

Still around.  Btw, I'm not sure it's a regression as I only started
using virtio_blk heavily during the 2.6.28 cycle.

Re: [Bug #12426] TMDC Joystick no longer works in kernel 2.6.28

[Andrew S. Johnson]

On Wednesday 04 February 2009 07:34:55 pm Rafael J. Wysocki wrote:
> On Wednesday 04 February 2009, Jiri Kosina wrote:
> > On Wed, 4 Feb 2009, Rafael J. Wysocki wrote:
> > > This message has been generated automatically as a part of a
> > > report of regressions introduced between 2.6.27 and 2.6.28.
> > >
> > > The following bug entry is on the current list of known
> > > regressions introduced between 2.6.27 and 2.6.28.  Please
> > > verify if it still should be listed and let me know (either
> > > way).
> > >
> > >
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
> > > Subject		: TMDC Joystick no longer works in kernel 2.6.28
> > > Submitter	: Andrew S. Johnson <andy-9eXmkf4BiQ2aMJb+Lgu22Q@public.gmane.org>
> > > Date		: 2009-01-10 21:53 (26 days old)
> > > References	:
> > > http://marc.info/?l=linux-kernel&m=123162486415366&w=4
> >
> > I asked [1] the Submitter some time ago to check whether
> > reverting a particular commit fixes the issue, but never heard
> > back.
> >
> > [1] http://lkml.org/lkml/2009/1/26/70
>
> Rejected as "insufficient data" and closed.

I never received the email referring to a particular commit because
I am not subscribed to LKML.  The commit revert seemed to work OK on 
gameport.c, but I get an error that gameport.h requires merge 
resolution.

Can you send the gameport.c and gameport.h files to me with the
reverted commit, or tell me how to get this resolved?

Please CC me directly.

Thanks,

Andy Johnson

>
> Thanks,
> Rafael

Re: [Bug #12426] TMDC Joystick no longer works in kernel 2.6.28

[Andrew S. Johnson]

On Wednesday 04 February 2009 07:34:55 pm Rafael J. Wysocki wrote:
> On Wednesday 04 February 2009, Jiri Kosina wrote:
> > On Wed, 4 Feb 2009, Rafael J. Wysocki wrote:
> > > This message has been generated automatically as a part of a
> > > report of regressions introduced between 2.6.27 and 2.6.28.
> > >
> > > The following bug entry is on the current list of known
> > > regressions introduced between 2.6.27 and 2.6.28.  Please
> > > verify if it still should be listed and let me know (either
> > > way).
> > >
> > >
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
> > > Subject		: TMDC Joystick no longer works in kernel 2.6.28
> > > Submitter	: Andrew S. Johnson <andy@asjohnson.com>
> > > Date		: 2009-01-10 21:53 (26 days old)
> > > References	:
> > > http://marc.info/?l=linux-kernel&m=123162486415366&w=4
> >
> > I asked [1] the Submitter some time ago to check whether
> > reverting a particular commit fixes the issue, but never heard
> > back.
> >
> > [1] http://lkml.org/lkml/2009/1/26/70
>
> Rejected as "insufficient data" and closed.

I never received the email referring to a particular commit because
I am not subscribed to LKML.  The commit revert seemed to work OK on 
gameport.c, but I get an error that gameport.h requires merge 
resolution.

Can you send the gameport.c and gameport.h files to me with the
reverted commit, or tell me how to get this resolved?

Please CC me directly.

Thanks,

Andy Johnson

>
> Thanks,
> Rafael

Re: [Bug #12426] TMDC Joystick no longer works in kernel 2.6.28

[Jiri Kosina]

On Fri, 6 Feb 2009, Andrew S. Johnson wrote:

> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
> > > > Subject		: TMDC Joystick no longer works in kernel 2.6.28
> > > > Submitter	: Andrew S. Johnson <andy-9eXmkf4BiQ2aMJb+Lgu22Q@public.gmane.org>
> > > > Date		: 2009-01-10 21:53 (26 days old)
> > > > References	:
> > > > http://marc.info/?l=linux-kernel&m=123162486415366&w=4
> > > I asked [1] the Submitter some time ago to check whether
> > > reverting a particular commit fixes the issue, but never heard
> > > back.
> > > [1] http://lkml.org/lkml/2009/1/26/70
> > Rejected as "insufficient data" and closed.
> I never received the email referring to a particular commit because I am 
> not subscribed to LKML.  

I CCed you, but your ISP blacklisted both of my SMTP servers I have tried 
for no apparent reason.

> The commit revert seemed to work OK on gameport.c, but I get an error 
> that gameport.h requires merge resolution.

Please try the patch below. It's not a simple revert of 6902c0be, needed 
some manual tweaking.

diff --git a/drivers/input/gameport/gameport.c b/drivers/input/gameport/gameport.c
index ebf4be5..5f2e729 100644
--- a/drivers/input/gameport/gameport.c
+++ b/drivers/input/gameport/gameport.c
@@ -231,7 +231,6 @@ static void gameport_find_driver(struct gameport *gameport)
 enum gameport_event_type {
 	GAMEPORT_REGISTER_PORT,
 	GAMEPORT_REGISTER_DRIVER,
-	GAMEPORT_ATTACH_DRIVER,
 };
 
 struct gameport_event {
@@ -246,12 +245,11 @@ static LIST_HEAD(gameport_event_list);
 static DECLARE_WAIT_QUEUE_HEAD(gameport_wait);
 static struct task_struct *gameport_task;
 
-static int gameport_queue_event(void *object, struct module *owner,
-				enum gameport_event_type event_type)
+static void gameport_queue_event(void *object, struct module *owner,
+			      enum gameport_event_type event_type)
 {
 	unsigned long flags;
 	struct gameport_event *event;
-	int retval = 0;
 
 	spin_lock_irqsave(&gameport_event_lock, flags);
 
@@ -270,34 +268,24 @@ static int gameport_queue_event(void *object, struct module *owner,
 		}
 	}
 
-	event = kmalloc(sizeof(struct gameport_event), GFP_ATOMIC);
-	if (!event) {
-		printk(KERN_ERR
-			"gameport: Not enough memory to queue event %d\n",
-			event_type);
-		retval = -ENOMEM;
-		goto out;
-	}
-
-	if (!try_module_get(owner)) {
-		printk(KERN_WARNING
-			"gameport: Can't get module reference, dropping event %d\n",
-			event_type);
-		kfree(event);
-		retval = -EINVAL;
-		goto out;
-	}
-
-	event->type = event_type;
-	event->object = object;
-	event->owner = owner;
+	if ((event = kmalloc(sizeof(struct gameport_event), GFP_ATOMIC))) {
+		if (!try_module_get(owner)) {
+			printk(KERN_WARNING "gameport: Can't get module reference, dropping event %d\n", event_type);
+			kfree(event);
+			goto out;
+		}
 
-	list_add_tail(&event->node, &gameport_event_list);
-	wake_up(&gameport_wait);
+		event->type = event_type;
+		event->object = object;
+		event->owner = owner;
 
+		list_add_tail(&event->node, &gameport_event_list);
+		wake_up(&gameport_wait);
+	} else {
+		printk(KERN_ERR "gameport: Not enough memory to queue event %d\n", event_type);
+	}
 out:
 	spin_unlock_irqrestore(&gameport_event_lock, flags);
-	return retval;
 }
 
 static void gameport_free_event(struct gameport_event *event)
@@ -390,10 +378,9 @@ static void gameport_handle_event(void)
 }
 
 /*
- * Remove all events that have been submitted for a given object,
- * be it a gameport port or a driver.
+ * Remove all events that have been submitted for a given gameport port.
  */
-static void gameport_remove_pending_events(void *object)
+static void gameport_remove_pending_events(struct gameport *gameport)
 {
 	struct list_head *node, *next;
 	struct gameport_event *event;
@@ -403,7 +390,7 @@ static void gameport_remove_pending_events(void *object)
 
 	list_for_each_safe(node, next, &gameport_event_list) {
 		event = list_entry(node, struct gameport_event, node);
-		if (event->object == object) {
+		if (event->object == gameport) {
 			list_del_init(node);
 			gameport_free_event(event);
 		}
@@ -717,40 +704,10 @@ static void gameport_add_driver(struct gameport_driver *drv)
 			drv->driver.name, error);
 }
 
-int __gameport_register_driver(struct gameport_driver *drv, struct module *owner,
-				const char *mod_name)
+void __gameport_register_driver(struct gameport_driver *drv, struct module *owner)
 {
-	int error;
-
 	drv->driver.bus = &gameport_bus;
-	drv->driver.owner = owner;
-	drv->driver.mod_name = mod_name;
-
-	/*
-	 * Temporarily disable automatic binding because probing
-	 * takes long time and we are better off doing it in kgameportd
-	 */
-	drv->ignore = 1;
-
-	error = driver_register(&drv->driver);
-	if (error) {
-		printk(KERN_ERR
-			"gameport: driver_register() failed for %s, error: %d\n",
-			drv->driver.name, error);
-		return error;
-	}
-
-	/*
-	 * Reset ignore flag and let kgameportd bind the driver to free ports
-	 */
-	drv->ignore = 0;
-	error = gameport_queue_event(drv, NULL, GAMEPORT_ATTACH_DRIVER);
-	if (error) {
-		driver_unregister(&drv->driver);
-		return error;
-	}
-
-	return 0;
+	gameport_queue_event(drv, owner, GAMEPORT_REGISTER_DRIVER);
 }
 
 void gameport_unregister_driver(struct gameport_driver *drv)
@@ -758,9 +715,7 @@ void gameport_unregister_driver(struct gameport_driver *drv)
 	struct gameport *gameport;
 
 	mutex_lock(&gameport_mutex);
-
 	drv->ignore = 1;	/* so gameport_find_driver ignores it */
-	gameport_remove_pending_events(drv);
 
 start_over:
 	list_for_each_entry(gameport, &gameport_list, node) {
@@ -773,7 +728,6 @@ start_over:
 	}
 
 	driver_unregister(&drv->driver);
-
 	mutex_unlock(&gameport_mutex);
 }
 
diff --git a/drivers/input/joystick/a3d.c b/drivers/input/joystick/a3d.c
index 6489f40..92498d4 100644
--- a/drivers/input/joystick/a3d.c
+++ b/drivers/input/joystick/a3d.c
@@ -414,7 +414,8 @@ static struct gameport_driver a3d_drv = {
 
 static int __init a3d_init(void)
 {
-	return gameport_register_driver(&a3d_drv);
+	gameport_register_driver(&a3d_drv);
+	return 0;
 }
 
 static void __exit a3d_exit(void)
diff --git a/drivers/input/joystick/adi.c b/drivers/input/joystick/adi.c
index 89c4c08..d1ca8a1 100644
--- a/drivers/input/joystick/adi.c
+++ b/drivers/input/joystick/adi.c
@@ -572,7 +572,8 @@ static struct gameport_driver adi_drv = {
 
 static int __init adi_init(void)
 {
-	return gameport_register_driver(&adi_drv);
+	gameport_register_driver(&adi_drv);
+	return 0;
 }
 
 static void __exit adi_exit(void)
diff --git a/drivers/input/joystick/analog.c b/drivers/input/joystick/analog.c
index 356b3a2..708c5ae 100644
--- a/drivers/input/joystick/analog.c
+++ b/drivers/input/joystick/analog.c
@@ -761,7 +761,9 @@ static struct gameport_driver analog_drv = {
 static int __init analog_init(void)
 {
 	analog_parse_options();
-	return gameport_register_driver(&analog_drv);
+	gameport_register_driver(&analog_drv);
+
+	return 0;
 }
 
 static void __exit analog_exit(void)
diff --git a/drivers/input/joystick/cobra.c b/drivers/input/joystick/cobra.c
index 3497b87..639b975 100644
--- a/drivers/input/joystick/cobra.c
+++ b/drivers/input/joystick/cobra.c
@@ -263,7 +263,8 @@ static struct gameport_driver cobra_drv = {
 
 static int __init cobra_init(void)
 {
-	return gameport_register_driver(&cobra_drv);
+	gameport_register_driver(&cobra_drv);
+	return 0;
 }
 
 static void __exit cobra_exit(void)
diff --git a/drivers/input/joystick/gf2k.c b/drivers/input/joystick/gf2k.c
index 67c207f..cb6eef1 100644
--- a/drivers/input/joystick/gf2k.c
+++ b/drivers/input/joystick/gf2k.c
@@ -375,7 +375,8 @@ static struct gameport_driver gf2k_drv = {
 
 static int __init gf2k_init(void)
 {
-	return gameport_register_driver(&gf2k_drv);
+	gameport_register_driver(&gf2k_drv);
+	return 0;
 }
 
 static void __exit gf2k_exit(void)
diff --git a/drivers/input/joystick/grip.c b/drivers/input/joystick/grip.c
index fc55899..684e07c 100644
--- a/drivers/input/joystick/grip.c
+++ b/drivers/input/joystick/grip.c
@@ -426,7 +426,8 @@ static struct gameport_driver grip_drv = {
 
 static int __init grip_init(void)
 {
-	return gameport_register_driver(&grip_drv);
+	gameport_register_driver(&grip_drv);
+	return 0;
 }
 
 static void __exit grip_exit(void)
diff --git a/drivers/input/joystick/grip_mp.c b/drivers/input/joystick/grip_mp.c
index 2d47baf..8279481 100644
--- a/drivers/input/joystick/grip_mp.c
+++ b/drivers/input/joystick/grip_mp.c
@@ -689,7 +689,8 @@ static struct gameport_driver grip_drv = {
 
 static int __init grip_init(void)
 {
-	return gameport_register_driver(&grip_drv);
+	gameport_register_driver(&grip_drv);
+	return 0;
 }
 
 static void __exit grip_exit(void)
diff --git a/drivers/input/joystick/guillemot.c b/drivers/input/joystick/guillemot.c
index 4058d4b..25ec3fa 100644
--- a/drivers/input/joystick/guillemot.c
+++ b/drivers/input/joystick/guillemot.c
@@ -283,7 +283,8 @@ static struct gameport_driver guillemot_drv = {
 
 static int __init guillemot_init(void)
 {
-	return gameport_register_driver(&guillemot_drv);
+	gameport_register_driver(&guillemot_drv);
+	return 0;
 }
 
 static void __exit guillemot_exit(void)
diff --git a/drivers/input/joystick/interact.c b/drivers/input/joystick/interact.c
index 2478289..8c3290b 100644
--- a/drivers/input/joystick/interact.c
+++ b/drivers/input/joystick/interact.c
@@ -317,7 +317,8 @@ static struct gameport_driver interact_drv = {
 
 static int __init interact_init(void)
 {
-	return gameport_register_driver(&interact_drv);
+	gameport_register_driver(&interact_drv);
+	return 0;
 }
 
 static void __exit interact_exit(void)
diff --git a/drivers/input/joystick/joydump.c b/drivers/input/joystick/joydump.c
index cd894a0..2a1b82c 100644
--- a/drivers/input/joystick/joydump.c
+++ b/drivers/input/joystick/joydump.c
@@ -161,7 +161,8 @@ static struct gameport_driver joydump_drv = {
 
 static int __init joydump_init(void)
 {
-	return gameport_register_driver(&joydump_drv);
+	gameport_register_driver(&joydump_drv);
+	return 0;
 }
 
 static void __exit joydump_exit(void)
diff --git a/drivers/input/joystick/sidewinder.c b/drivers/input/joystick/sidewinder.c
index ca13a6b..7b4865f 100644
--- a/drivers/input/joystick/sidewinder.c
+++ b/drivers/input/joystick/sidewinder.c
@@ -818,7 +818,8 @@ static struct gameport_driver sw_drv = {
 
 static int __init sw_init(void)
 {
-	return gameport_register_driver(&sw_drv);
+	gameport_register_driver(&sw_drv);
+	return 0;
 }
 
 static void __exit sw_exit(void)
diff --git a/drivers/input/joystick/tmdc.c b/drivers/input/joystick/tmdc.c
index d6c6098..60c37bc 100644
--- a/drivers/input/joystick/tmdc.c
+++ b/drivers/input/joystick/tmdc.c
@@ -438,7 +438,8 @@ static struct gameport_driver tmdc_drv = {
 
 static int __init tmdc_init(void)
 {
-	return gameport_register_driver(&tmdc_drv);
+	gameport_register_driver(&tmdc_drv);
+	return 0;
 }
 
 static void __exit tmdc_exit(void)
diff --git a/include/linux/gameport.h b/include/linux/gameport.h
index 0cd825f..f64e29c 100644
--- a/include/linux/gameport.h
+++ b/include/linux/gameport.h
@@ -146,11 +146,10 @@ static inline void gameport_unpin_driver(struct gameport *gameport)
 	mutex_unlock(&gameport->drv_mutex);
 }
 
-int __gameport_register_driver(struct gameport_driver *drv,
-				struct module *owner, const char *mod_name);
-static inline int __must_check gameport_register_driver(struct gameport_driver *drv)
+void __gameport_register_driver(struct gameport_driver *drv, struct module *owner);
+static inline void gameport_register_driver(struct gameport_driver *drv)
 {
-	return __gameport_register_driver(drv, THIS_MODULE, KBUILD_MODNAME);
+	__gameport_register_driver(drv, THIS_MODULE);
 }
 
 void gameport_unregister_driver(struct gameport_driver *drv);

Re: [Bug #12426] TMDC Joystick no longer works in kernel 2.6.28

[Jiri Kosina]

On Fri, 6 Feb 2009, Andrew S. Johnson wrote:

> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12426
> > > > Subject		: TMDC Joystick no longer works in kernel 2.6.28
> > > > Submitter	: Andrew S. Johnson <andy@asjohnson.com>
> > > > Date		: 2009-01-10 21:53 (26 days old)
> > > > References	:
> > > > http://marc.info/?l=linux-kernel&m=123162486415366&w=4
> > > I asked [1] the Submitter some time ago to check whether
> > > reverting a particular commit fixes the issue, but never heard
> > > back.
> > > [1] http://lkml.org/lkml/2009/1/26/70
> > Rejected as "insufficient data" and closed.
> I never received the email referring to a particular commit because I am 
> not subscribed to LKML.  

I CCed you, but your ISP blacklisted both of my SMTP servers I have tried 
for no apparent reason.

> The commit revert seemed to work OK on gameport.c, but I get an error 
> that gameport.h requires merge resolution.

Please try the patch below. It's not a simple revert of 6902c0be, needed 
some manual tweaking.

diff --git a/drivers/input/gameport/gameport.c b/drivers/input/gameport/gameport.c
index ebf4be5..5f2e729 100644
--- a/drivers/input/gameport/gameport.c
+++ b/drivers/input/gameport/gameport.c
@@ -231,7 +231,6 @@ static void gameport_find_driver(struct gameport *gameport)
 enum gameport_event_type {
 	GAMEPORT_REGISTER_PORT,
 	GAMEPORT_REGISTER_DRIVER,
-	GAMEPORT_ATTACH_DRIVER,
 };
 
 struct gameport_event {
@@ -246,12 +245,11 @@ static LIST_HEAD(gameport_event_list);
 static DECLARE_WAIT_QUEUE_HEAD(gameport_wait);
 static struct task_struct *gameport_task;
 
-static int gameport_queue_event(void *object, struct module *owner,
-				enum gameport_event_type event_type)
+static void gameport_queue_event(void *object, struct module *owner,
+			      enum gameport_event_type event_type)
 {
 	unsigned long flags;
 	struct gameport_event *event;
-	int retval = 0;
 
 	spin_lock_irqsave(&gameport_event_lock, flags);
 
@@ -270,34 +268,24 @@ static int gameport_queue_event(void *object, struct module *owner,
 		}
 	}
 
-	event = kmalloc(sizeof(struct gameport_event), GFP_ATOMIC);
-	if (!event) {
-		printk(KERN_ERR
-			"gameport: Not enough memory to queue event %d\n",
-			event_type);
-		retval = -ENOMEM;
-		goto out;
-	}
-
-	if (!try_module_get(owner)) {
-		printk(KERN_WARNING
-			"gameport: Can't get module reference, dropping event %d\n",
-			event_type);
-		kfree(event);
-		retval = -EINVAL;
-		goto out;
-	}
-
-	event->type = event_type;
-	event->object = object;
-	event->owner = owner;
+	if ((event = kmalloc(sizeof(struct gameport_event), GFP_ATOMIC))) {
+		if (!try_module_get(owner)) {
+			printk(KERN_WARNING "gameport: Can't get module reference, dropping event %d\n", event_type);
+			kfree(event);
+			goto out;
+		}
 
-	list_add_tail(&event->node, &gameport_event_list);
-	wake_up(&gameport_wait);
+		event->type = event_type;
+		event->object = object;
+		event->owner = owner;
 
+		list_add_tail(&event->node, &gameport_event_list);
+		wake_up(&gameport_wait);
+	} else {
+		printk(KERN_ERR "gameport: Not enough memory to queue event %d\n", event_type);
+	}
 out:
 	spin_unlock_irqrestore(&gameport_event_lock, flags);
-	return retval;
 }
 
 static void gameport_free_event(struct gameport_event *event)
@@ -390,10 +378,9 @@ static void gameport_handle_event(void)
 }
 
 /*
- * Remove all events that have been submitted for a given object,
- * be it a gameport port or a driver.
+ * Remove all events that have been submitted for a given gameport port.
  */
-static void gameport_remove_pending_events(void *object)
+static void gameport_remove_pending_events(struct gameport *gameport)
 {
 	struct list_head *node, *next;
 	struct gameport_event *event;
@@ -403,7 +390,7 @@ static void gameport_remove_pending_events(void *object)
 
 	list_for_each_safe(node, next, &gameport_event_list) {
 		event = list_entry(node, struct gameport_event, node);
-		if (event->object == object) {
+		if (event->object == gameport) {
 			list_del_init(node);
 			gameport_free_event(event);
 		}
@@ -717,40 +704,10 @@ static void gameport_add_driver(struct gameport_driver *drv)
 			drv->driver.name, error);
 }
 
-int __gameport_register_driver(struct gameport_driver *drv, struct module *owner,
-				const char *mod_name)
+void __gameport_register_driver(struct gameport_driver *drv, struct module *owner)
 {
-	int error;
-
 	drv->driver.bus = &gameport_bus;
-	drv->driver.owner = owner;
-	drv->driver.mod_name = mod_name;
-
-	/*
-	 * Temporarily disable automatic binding because probing
-	 * takes long time and we are better off doing it in kgameportd
-	 */
-	drv->ignore = 1;
-
-	error = driver_register(&drv->driver);
-	if (error) {
-		printk(KERN_ERR
-			"gameport: driver_register() failed for %s, error: %d\n",
-			drv->driver.name, error);
-		return error;
-	}
-
-	/*
-	 * Reset ignore flag and let kgameportd bind the driver to free ports
-	 */
-	drv->ignore = 0;
-	error = gameport_queue_event(drv, NULL, GAMEPORT_ATTACH_DRIVER);
-	if (error) {
-		driver_unregister(&drv->driver);
-		return error;
-	}
-
-	return 0;
+	gameport_queue_event(drv, owner, GAMEPORT_REGISTER_DRIVER);
 }
 
 void gameport_unregister_driver(struct gameport_driver *drv)
@@ -758,9 +715,7 @@ void gameport_unregister_driver(struct gameport_driver *drv)
 	struct gameport *gameport;
 
 	mutex_lock(&gameport_mutex);
-
 	drv->ignore = 1;	/* so gameport_find_driver ignores it */
-	gameport_remove_pending_events(drv);
 
 start_over:
 	list_for_each_entry(gameport, &gameport_list, node) {
@@ -773,7 +728,6 @@ start_over:
 	}
 
 	driver_unregister(&drv->driver);
-
 	mutex_unlock(&gameport_mutex);
 }
 
diff --git a/drivers/input/joystick/a3d.c b/drivers/input/joystick/a3d.c
index 6489f40..92498d4 100644
--- a/drivers/input/joystick/a3d.c
+++ b/drivers/input/joystick/a3d.c
@@ -414,7 +414,8 @@ static struct gameport_driver a3d_drv = {
 
 static int __init a3d_init(void)
 {
-	return gameport_register_driver(&a3d_drv);
+	gameport_register_driver(&a3d_drv);
+	return 0;
 }
 
 static void __exit a3d_exit(void)
diff --git a/drivers/input/joystick/adi.c b/drivers/input/joystick/adi.c
index 89c4c08..d1ca8a1 100644
--- a/drivers/input/joystick/adi.c
+++ b/drivers/input/joystick/adi.c
@@ -572,7 +572,8 @@ static struct gameport_driver adi_drv = {
 
 static int __init adi_init(void)
 {
-	return gameport_register_driver(&adi_drv);
+	gameport_register_driver(&adi_drv);
+	return 0;
 }
 
 static void __exit adi_exit(void)
diff --git a/drivers/input/joystick/analog.c b/drivers/input/joystick/analog.c
index 356b3a2..708c5ae 100644
--- a/drivers/input/joystick/analog.c
+++ b/drivers/input/joystick/analog.c
@@ -761,7 +761,9 @@ static struct gameport_driver analog_drv = {
 static int __init analog_init(void)
 {
 	analog_parse_options();
-	return gameport_register_driver(&analog_drv);
+	gameport_register_driver(&analog_drv);
+
+	return 0;
 }
 
 static void __exit analog_exit(void)
diff --git a/drivers/input/joystick/cobra.c b/drivers/input/joystick/cobra.c
index 3497b87..639b975 100644
--- a/drivers/input/joystick/cobra.c
+++ b/drivers/input/joystick/cobra.c
@@ -263,7 +263,8 @@ static struct gameport_driver cobra_drv = {
 
 static int __init cobra_init(void)
 {
-	return gameport_register_driver(&cobra_drv);
+	gameport_register_driver(&cobra_drv);
+	return 0;
 }
 
 static void __exit cobra_exit(void)
diff --git a/drivers/input/joystick/gf2k.c b/drivers/input/joystick/gf2k.c
index 67c207f..cb6eef1 100644
--- a/drivers/input/joystick/gf2k.c
+++ b/drivers/input/joystick/gf2k.c
@@ -375,7 +375,8 @@ static struct gameport_driver gf2k_drv = {
 
 static int __init gf2k_init(void)
 {
-	return gameport_register_driver(&gf2k_drv);
+	gameport_register_driver(&gf2k_drv);
+	return 0;
 }
 
 static void __exit gf2k_exit(void)
diff --git a/drivers/input/joystick/grip.c b/drivers/input/joystick/grip.c
index fc55899..684e07c 100644
--- a/drivers/input/joystick/grip.c
+++ b/drivers/input/joystick/grip.c
@@ -426,7 +426,8 @@ static struct gameport_driver grip_drv = {
 
 static int __init grip_init(void)
 {
-	return gameport_register_driver(&grip_drv);
+	gameport_register_driver(&grip_drv);
+	return 0;
 }
 
 static void __exit grip_exit(void)
diff --git a/drivers/input/joystick/grip_mp.c b/drivers/input/joystick/grip_mp.c
index 2d47baf..8279481 100644
--- a/drivers/input/joystick/grip_mp.c
+++ b/drivers/input/joystick/grip_mp.c
@@ -689,7 +689,8 @@ static struct gameport_driver grip_drv = {
 
 static int __init grip_init(void)
 {
-	return gameport_register_driver(&grip_drv);
+	gameport_register_driver(&grip_drv);
+	return 0;
 }
 
 static void __exit grip_exit(void)
diff --git a/drivers/input/joystick/guillemot.c b/drivers/input/joystick/guillemot.c
index 4058d4b..25ec3fa 100644
--- a/drivers/input/joystick/guillemot.c
+++ b/drivers/input/joystick/guillemot.c
@@ -283,7 +283,8 @@ static struct gameport_driver guillemot_drv = {
 
 static int __init guillemot_init(void)
 {
-	return gameport_register_driver(&guillemot_drv);
+	gameport_register_driver(&guillemot_drv);
+	return 0;
 }
 
 static void __exit guillemot_exit(void)
diff --git a/drivers/input/joystick/interact.c b/drivers/input/joystick/interact.c
index 2478289..8c3290b 100644
--- a/drivers/input/joystick/interact.c
+++ b/drivers/input/joystick/interact.c
@@ -317,7 +317,8 @@ static struct gameport_driver interact_drv = {
 
 static int __init interact_init(void)
 {
-	return gameport_register_driver(&interact_drv);
+	gameport_register_driver(&interact_drv);
+	return 0;
 }
 
 static void __exit interact_exit(void)
diff --git a/drivers/input/joystick/joydump.c b/drivers/input/joystick/joydump.c
index cd894a0..2a1b82c 100644
--- a/drivers/input/joystick/joydump.c
+++ b/drivers/input/joystick/joydump.c
@@ -161,7 +161,8 @@ static struct gameport_driver joydump_drv = {
 
 static int __init joydump_init(void)
 {
-	return gameport_register_driver(&joydump_drv);
+	gameport_register_driver(&joydump_drv);
+	return 0;
 }
 
 static void __exit joydump_exit(void)
diff --git a/drivers/input/joystick/sidewinder.c b/drivers/input/joystick/sidewinder.c
index ca13a6b..7b4865f 100644
--- a/drivers/input/joystick/sidewinder.c
+++ b/drivers/input/joystick/sidewinder.c
@@ -818,7 +818,8 @@ static struct gameport_driver sw_drv = {
 
 static int __init sw_init(void)
 {
-	return gameport_register_driver(&sw_drv);
+	gameport_register_driver(&sw_drv);
+	return 0;
 }
 
 static void __exit sw_exit(void)
diff --git a/drivers/input/joystick/tmdc.c b/drivers/input/joystick/tmdc.c
index d6c6098..60c37bc 100644
--- a/drivers/input/joystick/tmdc.c
+++ b/drivers/input/joystick/tmdc.c
@@ -438,7 +438,8 @@ static struct gameport_driver tmdc_drv = {
 
 static int __init tmdc_init(void)
 {
-	return gameport_register_driver(&tmdc_drv);
+	gameport_register_driver(&tmdc_drv);
+	return 0;
 }
 
 static void __exit tmdc_exit(void)
diff --git a/include/linux/gameport.h b/include/linux/gameport.h
index 0cd825f..f64e29c 100644
--- a/include/linux/gameport.h
+++ b/include/linux/gameport.h
@@ -146,11 +146,10 @@ static inline void gameport_unpin_driver(struct gameport *gameport)
 	mutex_unlock(&gameport->drv_mutex);
 }
 
-int __gameport_register_driver(struct gameport_driver *drv,
-				struct module *owner, const char *mod_name);
-static inline int __must_check gameport_register_driver(struct gameport_driver *drv)
+void __gameport_register_driver(struct gameport_driver *drv, struct module *owner);
+static inline void gameport_register_driver(struct gameport_driver *drv)
 {
-	return __gameport_register_driver(drv, THIS_MODULE, KBUILD_MODNAME);
+	__gameport_register_driver(drv, THIS_MODULE);
 }
 
 void gameport_unregister_driver(struct gameport_driver *drv);

Re: [Bug #12405] oops in __bounce_end_io_read under kvm

[Rafael J. Wysocki]

On Friday 06 February 2009, Christoph Hellwig wrote:
> On Wed, Feb 04, 2009 at 11:58:40AM +0100, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12405
> > Subject		: oops in __bounce_end_io_read under kvm
> > Submitter	: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
> > Date		: 2008-12-26 17:36 (41 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123031303400676&w=4
> > Handled-By	: Jens Axboe <jens.axboe-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
> 
> Still around.  Btw, I'm not sure it's a regression as I only started
> using virtio_blk heavily during the 2.6.28 cycle.

Well, assuming that it is a regression raises its chances to be fixed faster. ;-)

Re: [Bug #12405] oops in __bounce_end_io_read under kvm

[Rafael J. Wysocki]

On Friday 06 February 2009, Christoph Hellwig wrote:
> On Wed, Feb 04, 2009 at 11:58:40AM +0100, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12405
> > Subject		: oops in __bounce_end_io_read under kvm
> > Submitter	: Christoph Hellwig <hch@lst.de>
> > Date		: 2008-12-26 17:36 (41 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123031303400676&w=4
> > Handled-By	: Jens Axboe <jens.axboe@oracle.com>
> 
> Still around.  Btw, I'm not sure it's a regression as I only started
> using virtio_blk heavily during the 2.6.28 cycle.

Well, assuming that it is a regression raises its chances to be fixed faster. ;-)

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Philipp Matthias Hahn]

HellO!

On Fri, Feb 06, 2009 at 07:59:12AM +0100, Philipp Matthias Hahn wrote:
> I did some structured tesing:

Here are my captured console logs:
scout=Desktop with nVidia Corporation MCP51 Ethernet Controller (rev a3)
euro=Laptop used for capturing and wakeup

(initramfs) modprobe forcedeth
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
forcedeth 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
forcedeth 0000:00:14.0: setting latency timer to 64
nv_probe: MAC_ADDR_REV ELSE
nv_probe: set workaround bit for reversed mac addr
forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:db:f2:e1:35
forcedeth 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3
(initramfs) ethtool -s eth0 wol g
(initramfs) poweroff
...
forcedeth 0000:00:14.0: PCI INT A disabled
forcedeth 0000:00:14.0: PME# enabled
forcedeth 0000:00:14.0: wake-up capability enabled by ACPI
ACPI: Preparing to enter system sleep state S5
...
Power down.
acpi_power_off called

euro:~# etherwake -i eth0 00:19:db:f2:e1:35 # FAIL
euro:~# etherwake -i eth0 35:e1:f2:db:19:00 # FAIL


(initramfs) modprobe forcedeth
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
forcedeth 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
forcedeth 0000:00:14.0: setting latency timer to 64
nv_probe: MAC_ADDR_REV ELSE
nv_probe: set workaround bit for reversed mac addr
forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:db:f2:e1:35
forcedeth 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3
(initramfs) ethtool -s eth0 wol g
(initramfs) echo o > /proc/sysrq-trigger
SysRq : Power Off
...
forcedeth 0000:00:14.0: PCI INT A disabled
forcedeth 0000:00:14.0: PME# enabled
forcedeth 0000:00:14.0: wake-up capability enabled by ACPI
ACPI: Preparing to enter system sleep state S5
...
Power down.
acpi_power_off called

euro:~# etherwake -i eth0 00:19:db:f2:e1:35 # FAIL
euro:~# etherwake -i eth0 35:e1:f2:db:19:00 # FAIL


(initramfs) modprobe forcedeth
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
forcedeth 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
forcedeth 0000:00:14.0: setting latency timer to 64
nv_probe: MAC_ADDR_REV ELSE
nv_probe: set workaround bit for reversed mac addr
forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:db:f2:e1:35
forcedeth 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3
(initramfs) ethtool -s eth0 wol g
(initramfs) echo b > /proc/sysrq-trigger
SysRq : Resetting
(grub) halt

euro:~# etherwake -i eth0 35:e1:f2:db:19:00 # FAIL
euro:~# etherwake -i eth0 00:19:db:f2:e1:35 # SUCCESS


(initramfs) modprobe forcedeth
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
forcedeth 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
forcedeth 0000:00:14.0: setting latency timer to 64
nv_probe: MAC_ADDR_REV ELSE
nv_probe: set workaround bit for reversed mac addr
forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:db:f2:e1:35
forcedeth 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3
(initramfs) ethtool -s eth0 wol g
(initramfs) exit
...
scout:~# poweroff
...
forcedeth 0000:00:14.0: PCI INT A disabled
forcedeth 0000:00:14.0: PME# enabled
forcedeth 0000:00:14.0: wake-up capability enabled by ACPI
ACPI: Preparing to enter system sleep state S5
...
Power down.
acpi_power_off called

euro:~# etherwake -i eth0 00:19:db:f2:e1:35 # FAIL
euro:~# etherwake -i eth0 35:e1:f2:db:19:00 # SUCCESS

BYtE
Philipp Hahn
-- 
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn-u4khhh1J0LzF41mA0N3lWw@public.gmane.org

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Philipp Matthias Hahn]

HellO!

On Fri, Feb 06, 2009 at 07:59:12AM +0100, Philipp Matthias Hahn wrote:
> I did some structured tesing:

Here are my captured console logs:
scout=Desktop with nVidia Corporation MCP51 Ethernet Controller (rev a3)
euro=Laptop used for capturing and wakeup

(initramfs) modprobe forcedeth
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
forcedeth 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
forcedeth 0000:00:14.0: setting latency timer to 64
nv_probe: MAC_ADDR_REV ELSE
nv_probe: set workaround bit for reversed mac addr
forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:db:f2:e1:35
forcedeth 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3
(initramfs) ethtool -s eth0 wol g
(initramfs) poweroff
...
forcedeth 0000:00:14.0: PCI INT A disabled
forcedeth 0000:00:14.0: PME# enabled
forcedeth 0000:00:14.0: wake-up capability enabled by ACPI
ACPI: Preparing to enter system sleep state S5
...
Power down.
acpi_power_off called

euro:~# etherwake -i eth0 00:19:db:f2:e1:35 # FAIL
euro:~# etherwake -i eth0 35:e1:f2:db:19:00 # FAIL


(initramfs) modprobe forcedeth
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
forcedeth 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
forcedeth 0000:00:14.0: setting latency timer to 64
nv_probe: MAC_ADDR_REV ELSE
nv_probe: set workaround bit for reversed mac addr
forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:db:f2:e1:35
forcedeth 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3
(initramfs) ethtool -s eth0 wol g
(initramfs) echo o > /proc/sysrq-trigger
SysRq : Power Off
...
forcedeth 0000:00:14.0: PCI INT A disabled
forcedeth 0000:00:14.0: PME# enabled
forcedeth 0000:00:14.0: wake-up capability enabled by ACPI
ACPI: Preparing to enter system sleep state S5
...
Power down.
acpi_power_off called

euro:~# etherwake -i eth0 00:19:db:f2:e1:35 # FAIL
euro:~# etherwake -i eth0 35:e1:f2:db:19:00 # FAIL


(initramfs) modprobe forcedeth
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
forcedeth 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
forcedeth 0000:00:14.0: setting latency timer to 64
nv_probe: MAC_ADDR_REV ELSE
nv_probe: set workaround bit for reversed mac addr
forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:db:f2:e1:35
forcedeth 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3
(initramfs) ethtool -s eth0 wol g
(initramfs) echo b > /proc/sysrq-trigger
SysRq : Resetting
(grub) halt

euro:~# etherwake -i eth0 35:e1:f2:db:19:00 # FAIL
euro:~# etherwake -i eth0 00:19:db:f2:e1:35 # SUCCESS


(initramfs) modprobe forcedeth
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
forcedeth 0000:00:14.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
forcedeth 0000:00:14.0: setting latency timer to 64
nv_probe: MAC_ADDR_REV ELSE
nv_probe: set workaround bit for reversed mac addr
forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:db:f2:e1:35
forcedeth 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3
(initramfs) ethtool -s eth0 wol g
(initramfs) exit
...
scout:~# poweroff
...
forcedeth 0000:00:14.0: PCI INT A disabled
forcedeth 0000:00:14.0: PME# enabled
forcedeth 0000:00:14.0: wake-up capability enabled by ACPI
ACPI: Preparing to enter system sleep state S5
...
Power down.
acpi_power_off called

euro:~# etherwake -i eth0 00:19:db:f2:e1:35 # FAIL
euro:~# etherwake -i eth0 35:e1:f2:db:19:00 # SUCCESS

BYtE
Philipp Hahn
-- 
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Tobias Diedrich]

Philipp Matthias Hahn wrote:
> Somewhere between 2.6.26 and 2.6.27 WOL stopped working on my MS-7350
> motherboard with an "nVidia Corporation MCP51 Ethernet Controller (rev a3)".
> 	"etherwake 00:19:db:f2:e1:35" did not work
> 	"etherwake 35:e1:f2:db:19:00" did work
> Since I did a BIOS update during the same time window I (wrongly) put
> the fault on the BIOS. (See /sys/class/dmi/id/modalias for yourself:
> dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd07/29/2008:svnMSI:pnMS-7350:pvr1.0:rvnMSI:rnMS-7350:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
> )

Hmm, I had not tried WOL for some time.
With 2.6.29-rc3 is see the following behaviour:

State            WOL Behaviour
------------------------------
shutdown         reversed MAC
disk/shutdown    reversed MAC
disk/platform    OK

Apparently nv_restore_mac_addr() restores the MAC in the wrong order
for WOL (at least for my PCI_DEVICE_ID_NVIDIA_NVENET_15).  platform
works, because the MAC is not touched in the nv_suspend() path.

A possible fix might be to only call nv_restore_mac_addr() if
system_state != SYSTEM_POWER_OFF.

-- 
Tobias						PGP: http://9ac7e0bc.uguu.de
このメールは十割再利用されたビットで作られています。

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Tobias Diedrich]

Tobias Diedrich wrote:
> Philipp Matthias Hahn wrote:
> > Somewhere between 2.6.26 and 2.6.27 WOL stopped working on my MS-7350
> > motherboard with an "nVidia Corporation MCP51 Ethernet Controller (rev a3)".
> > 	"etherwake 00:19:db:f2:e1:35" did not work
> > 	"etherwake 35:e1:f2:db:19:00" did work
> > Since I did a BIOS update during the same time window I (wrongly) put
> > the fault on the BIOS. (See /sys/class/dmi/id/modalias for yourself:
> > dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd07/29/2008:svnMSI:pnMS-7350:pvr1.0:rvnMSI:rnMS-7350:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
> > )
> 
> Hmm, I had not tried WOL for some time.
> With 2.6.29-rc3 is see the following behaviour:
> 
> State            WOL Behaviour
> ------------------------------
> shutdown         reversed MAC
> disk/shutdown    reversed MAC
> disk/platform    OK
> 
> Apparently nv_restore_mac_addr() restores the MAC in the wrong order
> for WOL (at least for my PCI_DEVICE_ID_NVIDIA_NVENET_15).  platform
> works, because the MAC is not touched in the nv_suspend() path.
> 
> A possible fix might be to only call nv_restore_mac_addr() if
> system_state != SYSTEM_POWER_OFF.

With the following patch:
shutdown         OK
disk/shutdown    OK
disk/platform    OK
kexec            OK

Signed-off-by: Tobias Diedrich <ranma+kernel@tdiedrich.de>

Index: linux-2.6.29-rc3/drivers/net/forcedeth.c
===================================================================
--- linux-2.6.29-rc3.orig/drivers/net/forcedeth.c	2009-02-08 16:31:29.000000000 +0100
+++ linux-2.6.29-rc3/drivers/net/forcedeth.c	2009-02-08 16:39:58.000000000 +0100
@@ -6011,9 +6011,20 @@
 	if (netif_running(dev))
 		nv_close(dev);
 
-	nv_restore_mac_addr(pdev);
+	/*
+	 * Restore the MAC so a kernel started by kexec won't get confused.
+	 * If we really go for poweroff, we must not restore the MAC,
+	 * otherwise the MAC for WOL will be reversed at least on some boards.
+	 */
+	if (system_state != SYSTEM_POWER_OFF) {
+		nv_restore_mac_addr(pdev);
+	}
 
 	pci_disable_device(pdev);
+	/*
+	 * Apparently it is not possible to reinitialise from D3 hot,
+	 * only put the device into D3 if we really go for poweroff.
+	 */
 	if (system_state == SYSTEM_POWER_OFF) {
 		if (pci_enable_wake(pdev, PCI_D3cold, np->wolenabled))
 			pci_enable_wake(pdev, PCI_D3hot, np->wolenabled);

-- 
Tobias						PGP: http://9ac7e0bc.uguu.de
このメールは十割再利用されたビットで作られています。

Re: WOL with forcedeth broken since f55c21fd9a92a444e55ad1ca4e4732d56661bf2e

[Philipp Matthias Hahn]

Hello!

On Sun, Feb 08, 2009 at 05:52:17PM +0100, Tobias Diedrich wrote:
> Tobias Diedrich wrote:
> > Philipp Matthias Hahn wrote:
> > > Somewhere between 2.6.26 and 2.6.27 WOL stopped working on my MS-7350
> > > motherboard with an "nVidia Corporation MCP51 Ethernet Controller (rev a3)".
> > > 	"etherwake 00:19:db:f2:e1:35" did not work
> > > 	"etherwake 35:e1:f2:db:19:00" did work
...
> With the following patch:
> shutdown         OK
> disk/shutdown    OK
> disk/platform    OK
> kexec            OK

Your patch seems to work for my system, too. (Expect for the case where
I do "poweroff" from busybox or do Alt-SysRq-O; Debians version works,
as long as I remove the '-i' option:
	-i     Shut down all network interfaces just before halt or reboot.

> Signed-off-by: Tobias Diedrich <ranma+kernel@tdiedrich.de>
Tested-by: Philipp Matthias Hahn <pmhahn@titan.lahn.de>

BYtE
Philipp
-- 
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de

[Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
Date		: 2008-12-14 11:39 (63 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

[Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of regressions introduced between 2.6.27 and 2.6.28.

The following bug entry is on the current list of known regressions
introduced between 2.6.27 and 2.6.28.  Please verify if it still should
be listed and let me know (either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
Subject		: journal activity on inactive partition causes inactive harddrive spinup
Submitter	: C Sights <csights@fastmail.fm>
Date		: 2008-12-14 11:39 (63 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
Handled-By	: Eric Sandeen <sandeen@redhat.com>

[Bug 12224] journal activity on inactive partition causes inactive harddrive spinup

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=12224


tytso@mit.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|                            |CODE_FIX




------- Comment #22 from tytso@mit.edu  2009-02-23 04:22 -------
The fix for this has landed in mainline as commit 02ac59 for ext3, and  
commit 9eddac for ext4.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Re: [Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Theodore Tso]

On Sat, Feb 14, 2009 at 09:50:20PM +0100, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
> Subject		: journal activity on inactive partition causes inactive harddrive spinup
> Submitter	: C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
> Date		: 2008-12-14 11:39 (63 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
> Handled-By	: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> 

The fix for this has landed in mainline as commit 02ac59 for ext3, and
commit 9eddac for ext4.

Rafael, I've marked the bug closed in BZ for your convenience.

    	    	     	       	  	      	 - Ted

Re: [Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Theodore Tso]

On Sat, Feb 14, 2009 at 09:50:20PM +0100, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
> Subject		: journal activity on inactive partition causes inactive harddrive spinup
> Submitter	: C Sights <csights@fastmail.fm>
> Date		: 2008-12-14 11:39 (63 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
> Handled-By	: Eric Sandeen <sandeen@redhat.com>
> 

The fix for this has landed in mainline as commit 02ac59 for ext3, and
commit 9eddac for ext4.

Rafael, I've marked the bug closed in BZ for your convenience.

    	    	     	       	  	      	 - Ted

Re: [Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

On Monday 23 February 2009, Theodore Tso wrote:
> On Sat, Feb 14, 2009 at 09:50:20PM +0100, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
> > Subject		: journal activity on inactive partition causes inactive harddrive spinup
> > Submitter	: C Sights <csights-97jfqw80gc6171pxa8y+qA@public.gmane.org>
> > Date		: 2008-12-14 11:39 (63 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
> > Handled-By	: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > 
> 
> The fix for this has landed in mainline as commit 02ac59 for ext3, and
> commit 9eddac for ext4.
> 
> Rafael, I've marked the bug closed in BZ for your convenience.

Thanks a lot!

Best,
Rafael

Re: [Bug #12224] journal activity on inactive partition causes inactive harddrive spinup

[Rafael J. Wysocki]

On Monday 23 February 2009, Theodore Tso wrote:
> On Sat, Feb 14, 2009 at 09:50:20PM +0100, Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12224
> > Subject		: journal activity on inactive partition causes inactive harddrive spinup
> > Submitter	: C Sights <csights@fastmail.fm>
> > Date		: 2008-12-14 11:39 (63 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c87591b719737b4e91eb1a9fa8fd55a4ff1886d6
> > Handled-By	: Eric Sandeen <sandeen@redhat.com>
> > 
> 
> The fix for this has landed in mainline as commit 02ac59 for ext3, and
> commit 9eddac for ext4.
> 
> Rafael, I've marked the bug closed in BZ for your convenience.

Thanks a lot!

Best,
Rafael