date:20120101

Processing commands for cont...@bugs.debian.org:

> severity 627019 important
Bug #627019 [linux-2.6] linux-image-2.6.39-rc7-686-pae: several kernel hangs 
before geting to login
Bug #649304 [linux-2.6] linux-image-3.1.0-1-686-pae:  needed 
for 686-pae kernels
Severity set to 'important' from 'normal'

Severity set to 'important' from 'normal'

> found 627019 linux-2.6/3.1.6-1
Bug #627019 [linux-2.6] linux-image-2.6.39-rc7-686-pae: several kernel hangs 
before geting to login
Bug #649304 [linux-2.6] linux-image-3.1.0-1-686-pae:  needed 
for 686-pae kernels
Bug Marked as found in versions linux-2.6/3.1.6-1.
Bug Marked as found in versions linux-2.6/3.1.6-1.
> # > Yes, when I disable hyperthreading in the BIOS the machine boots normally.
> forwarded 627019 https://bugzilla.kernel.org/show_bug.cgi?id=38262
Bug #627019 [linux-2.6] linux-image-2.6.39-rc7-686-pae: several kernel hangs 
before geting to login
Bug #649304 [linux-2.6] linux-image-3.1.0-1-686-pae:  needed 
for 686-pae kernels
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=38262'.
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=38262'.
> merge 627019 631597
Bug#627019: linux-image-2.6.39-rc7-686-pae: several kernel hangs before geting 
to login
Bug#631597: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot
Bug#649304: linux-image-3.1.0-1-686-pae:  needed for 686-pae 
kernels
Bug#630031: linux-image-2.6.39-2-686-pae: Kernel boots, but dmesg contains 
kernel bug trace
Bug#632734: linux-image-2.6.39-2-686-pae: Kernel boots but OOPs found in syslog
Merged 627019 630031 631597 632734 649304.

>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
649304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649304
627019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627019
630031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630031
632734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632734
631597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132540638922902.transcr...@bugs.debian.org

Bug#627372: Console turns black during boot.

Hi,

AlanKim Zimmerman wrote:

> BTW, I hope there is enough detail there. Seems the i915 debug info ended
> up empty, and the detailed dmesg seems to have junk.
>
> Not sure I have the will right now to reinstall the driver, shut down and
> reboot in the flaky mode.
>
> I will if required, though. Let me know.

Unfortunately the upstream bug seems to be stalled.  Do you have any
idea what happened to the error state?  E.g., was there any message
when trying to mount debugfs or trying to capture the error state with
"cat"?

Testing should be as simple as booting with the i915.modeset=1
parameter on the kernel command line (choose the kernel in grub, hit
"e" for detailed options, move to the line starting with "linux", and
you can add parameters to the end of the line and hit ctrl-x to boot)
--- no need to install the intel X driver again.  Does 3.2-rc7 from
experimental show the same symptoms?



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101083455.ge2...@elie.hsd1.il.comcast.net

Bug#597817: base: Realtek RTL8111/8168B doesn't always work

tags 597817 + moreinfo
quit

Jonathan Nieder wrote:
> Aniruddha wrote:

>> Every other boot I don't have internet access
[...]
>  - Please provide output from
>
>   reportbug --template linux-image-$(uname -r)
>
>so we can get to know your hardware better.

Ping.  Do you still have access to this machine to run tests?

Sorry for the trouble,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101084419.ga4...@elie.hsd1.il.comcast.net

Processed: Re: base: Realtek RTL8111/8168B doesn't always work

Processing commands for cont...@bugs.debian.org:

> tags 597817 + moreinfo
Bug #597817 [linux-2.6] base: Realtek RTL8111/8168B doesn't always work
Added tag(s) moreinfo.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
597817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132540747227673.transcr...@bugs.debian.org

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

2012-01-01 Thread Geert Uytterhoeven

Hi Thorsten,

On Sat, Dec 31, 2011 at 23:55, Thorsten Glaser  wrote:
> Dixi quod…
>
>>This one does work:
>>http://lists.debian.org/debian-kernel/2011/12/msg00474.html
>
> Geert, would you please apply the attached patch, independent of
> whether we are able to find a solution in aufs, as it avoids an
> entire problem class?

Sorry, static inline functions are preferred over macros, unless there's
a really good reason. Out-of-tree kernel code doing stupid things doesn't
count.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMuHMdWoJYkRJ8NnS8xLnmBF9+tyNYew+O9+0O=v6td0mzz...@mail.gmail.com

Bug#599582: [2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi laptop unless headphones plugged in

retitle 599582 [2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi laptop 
unless headphones plugged in
tags 599582 + moreinfo
quit

Jean-Louis Biasini wrote:

> No sound from the speaker but if I plug a jack into my laptop's
> headphone plug I get the sound from it.
>
> My driver is HDA intel on a pi 1505 fujitsu laptop

Summary of this bug so far:

 - All reporters got no sound unless something is plugged into the
   headphone jack.  When headphones are plugged in, sound only goes
   through the headphones, as you'd hope.

 - Jean-Louis Biasini is using a Fujitsu Pi 1505 laptop.

   A 2.6.32-5-amd64 kernel from 2010-10-09 exhibits the problem.
   A 2.6.35-trunk-amd64 kernel from the same time does not exhibit the problem.

 - Jose Manuel Castroagudin is using a Fujitsu Pi 2515.

   A 2.6.32-5-686 kernel from 2010-10-29 exhibits the problem.
   A 2.6.30 kernel does not.

 - Stas Zytkiewicz is using a Dell Inspiron 15.

   2.6.32-27 exhibits the problem.
   2.6.36 from experimental does not exhibit the problem.

   snd-hda-intel.model=hp-dv5 also avoids trouble.

 - Rafael Varela Pet is using a Fujitsu-Siemens Amilo Pi 1505.

   2.6.32-30 exhibits the problem.
   A 2.6.26-2-amd64 kernel from the same time does not.

Next steps to move this forward:

 1. Please attach output from the alsa-info.sh script with and without
headphones plugged in.

 2. Trying some kernels between 2.6.32 and 2.6.35 from
http://snapshot.debian.org/ would help narrow down when the fix
was introduced.

Thanks again, and sorry for the trouble,
Jonathan

-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101091142.ga4...@elie.hsd1.il.comcast.net

Bug#599582: [2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi laptop unless headphones plugged in

Jonathan Nieder wrote:

> Next steps to move this forward:
>
>  1. Please attach output from the alsa-info.sh script with and without
> headphones plugged in.

Silly me --- forgot to mention where[1] the alsa-info.sh script can be
found.

Sorry for the noise.
Jonathan

[1] http://www.alsa-project.org/alsa-info.sh



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101091324.gb4...@elie.hsd1.il.comcast.net

Bug#622325: linux-image-2.6.38-2-orion5x: Problem With I2C

2012-01-01 Thread Roman Mamedov

On Sun, 1 Jan 2012 01:42:36 -0600
Jonathan Nieder  wrote:

> Passed upstream.  But now I notice that there has been some upstream
> work in this area recently (v3.2-rc7~23^2~1, rtc: m41t80: Workaround
> broken alarm functionality, 2011-12-12).
> 
> Please test v3.2-rc7 from experimental and let the upstream folks
> know how it fares (by replying-to-all on the other side thread).

Hello,

Thank you for looking into this and for the information about the 3.2 possible 
fix.
Unfortunately I can't try that kernel easily at the moment, as there doesn't 
seem to be an orion5x variant of the package in experimental.

Some more info:

- During my testing I have found that after booting with a 'bad' kernel, a full 
power-off of the device including disconnecting the power supply from the mains 
might be required, before a 'good' kernel will work properly.

- This might have been mentioned, but the main reason this bug concerns me, is 
that the temperature sensor and the fan PWM control do not work on the 'bad' 
kernels (i.e. it's not just the periodic dmesg error). The fan does not turn 
on, which risks overheating the device and/or drives.

-- 
With respect,
Roman

~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."


signature.asc
Description: PGP signature

Processed: [2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi laptop unless headphones plugged in

Processing commands for cont...@bugs.debian.org:

> retitle 599582 [2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi laptop 
> unless headphones plugged in
Bug #599582 [linux-2.6] [linux-2.6.32-5-amd64] problem with sound 
(pulseaudio/alsa broken?)
Bug #601727 [linux-2.6] alsa-base: No sound through speakers on newer kernels
Bug #601728 [linux-2.6] alsa-base: No sound through laptop speakers in newer 
kernels (hda intel)
Bug #613271 [linux-2.6] linux-image-2.6.32-5-amd64: No sound through speakers 
after upgrading to Squeeze
Changed Bug title to '[2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi 
laptop unless headphones plugged in' from '[linux-2.6.32-5-amd64] problem with 
sound (pulseaudio/alsa broken?)'
Changed Bug title to '[2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi 
laptop unless headphones plugged in' from 'alsa-base: No sound through speakers 
on newer kernels'
Changed Bug title to '[2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi 
laptop unless headphones plugged in' from 'alsa-base: No sound through laptop 
speakers in newer kernels (hda intel)'
Changed Bug title to '[2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi 
laptop unless headphones plugged in' from 'linux-image-2.6.32-5-amd64: No sound 
through speakers after upgrading to Squeeze'
> tags 599582 + moreinfo
Bug #599582 [linux-2.6] [2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi 
laptop unless headphones plugged in
Bug #601727 [linux-2.6] [2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi 
laptop unless headphones plugged in
Bug #601728 [linux-2.6] [2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi 
laptop unless headphones plugged in
Bug #613271 [linux-2.6] [2.6.30 -> 2.6.32 regression] no sound from Fujitsu Pi 
laptop unless headphones plugged in
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
599582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13254091194848.transcr...@bugs.debian.org

Bug#622325: linux-image-2.6.38-2-orion5x: Problem With I2C

severity 622325 important
quit

Roman Mamedov wrote:

> Unfortunately I can't try that kernel easily at the moment, as there
> doesn't seem to be an orion5x variant of the package in
> experimental.

Oh, right.[1]  Let's wait to hear what the developers come up with, then.

Thanks,
Jonathan

[1] https://buildd.debian.org/status/package.php?p=linux-2.6&suite=experimental



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101091729.gc4...@elie.hsd1.il.comcast.net

Processed: Re: linux-image-2.6.38-2-orion5x: Problem With I2C

Processing commands for cont...@bugs.debian.org:

> severity 622325 important
Bug #622325 [linux-2.6] linux-image-2.6.38-2-orion5x: Problem With I2C
Severity set to 'important' from 'normal'

> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
622325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13254094636440.transcr...@bugs.debian.org

Bug#603469: ERROR atombios stuck executing F6D8

tags 603469 + patch
quit

Jonathan Nieder wrote:

> | [7.120450] [drm] Initialized radeon 2.0.0 20080528 for :01:00.0 on 
> minor 0
> | [  949.420558] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more 
> than 1sec aborting
> | [  949.420570] [drm:atom_execute_table_locked] *ERROR* atombios stuck 
> executing F6D8 (len 487, WS 0, PS 4) @ 0xF719
>
> This doesn't look like the standard squeeze kernel, since squeeze
> doesn't contain v2.6.34-rc4~12^2~50^2~17 (drm/radeon/kms: catch
> atombios infinite loop and break out of it, 2010-03-02).

Never mind --- commit 030849199dbe ("Backport radeon r800 modesetting
support", 2010-04-08) from 2.6.32-12 includes that change.  So the
two commits I mentioned (v2.6.36-rc3~9^2~79^2~24, v2.6.37-rc8~26^2~2)
could be worth cherry-picking after all.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101095208.ga5...@elie.hsd1.il.comcast.net

Processed: Re: ERROR atombios stuck executing F6D8

Processing commands for cont...@bugs.debian.org:

> tags 603469 + patch
Bug #603469 [linux-2.6] radeon: atombios stuck executing F6D8 (screen randomly 
goes black with no way to get it back)
Added tag(s) patch.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
603469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132541154617251.transcr...@bugs.debian.org

Processed: Re: ERROR atombios stuck executing F6D8

Processing commands for cont...@bugs.debian.org:

> # untested
> tags 603469 + moreinfo
Bug #603469 [linux-2.6] radeon: atombios stuck executing F6D8 (screen randomly 
goes black with no way to get it back)
Added tag(s) moreinfo.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
603469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132541196019070.transcr...@bugs.debian.org

Bug#534545: marked as done (linux-image-2.6.26-2-openvz-686: server is hangs on ?heavy? disk io on ocfs2)

Your message dated Sun, 1 Jan 2012 03:58:01 -0600
with message-id <20120101095801.ga5...@elie.hsd1.il.comcast.net>
and subject line Re: linux-image-2.6.26-2-openvz-686: server is hangs on 
?heavy? disk io on ocfs2
has caused the Debian Bug report #534545,
regarding linux-image-2.6.26-2-openvz-686: server is hangs on ?heavy? disk io 
on ocfs2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
534545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-2-openvz-686
Version: 2.6.26-15lenny3
Severity: critical
Justification: breaks the whole system

I use openvz on ocfs2 fs which is on drbd on sw mirror raid.

Once or twice a day the server froze.

I got a lot of:
Jun 24 08:30:03 hoster-dmz-1 kernel: [116049.348676] (10868,0):dlmunlock_common:
128 ERROR: lockres F28c8f0c0517267: Someone is calling dlmunlock
 while waiting for an ast!<3>(10868,0):dlmunlock:685 ERROR: dlm status = DLM_BAD
PARAM
Jun 24 08:30:03 hoster-dmz-1 kernel: [116049.348676] (10868,0):ocfs2_cancel_conv
ert:3001 ERROR: DLM error -22 while calling ocfs2_dlm_unlock on resource F00
0028c8f0c0517267
Jun 24 08:30:03 hoster-dmz-1 kernel: [116049.348676] (10868,0):ocfs2_flock_handl
e_signal:1505 ERROR: status = -22
Jun 24 08:30:03 hoster-dmz-1 kernel: [116049.348676] 
(10868,0):ocfs2_do_flock:79 ERROR: status = -22

but it seem to be non-fatal.

before the server hangs:
Jun 25 00:21:48 hoster-dmz-1 kernel: [88.239258] 
(4197,3):dlmunlock_common:128 ERROR: lockres F2e601561c073e7: 
Someone is calling dlmunlock while waiting for an ast!<3>(4197,3):dlmunlock:685 
ERROR: dlm status = DLM_BADPARAM
Jun 25 00:21:48 hoster-dmz-1 kernel: [88.239258] 
(4197,3):ocfs2_cancel_convert:3001 ERROR: DLM error -22 while calling 
ocfs2_dlm_unlock on resource F2e601561c073e7
Jun 25 00:21:48 hoster-dmz-1 kernel: [88.239258] 
(4197,3):ocfs2_flock_handle_signal:1505 ERROR: status = -22
Jun 25 00:21:48 hoster-dmz-1 kernel: [88.239258] (4197,3):ocfs2_do_flock:79 
ERROR: status = -22
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] 
(4197,2):dlmunlock_common:128 ERROR: lockres F2e5ffb61c07a97: 
Someone is calling dlmunlock 
while waiting for an ast!<3>(4197,2):dlmunlock:685 ERROR: dlm status = 
DLM_BADPARAM
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] 
(4197,2):ocfs2_cancel_convert:3001 ERROR: DLM error -22 while calling 
ocfs2_dlm_unlock on resource F2e5ffb61c07a97
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] 
(4197,2):ocfs2_flock_handle_signal:1505 ERROR: status = -22
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] (4197,2):ocfs2_do_flock:79 
ERROR: status = -22
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] [ cut here 
]
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] kernel BUG at 
fs/ocfs2/dlmglue.c:678!
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] invalid opcode:  [#1] 
SMP 
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] Modules linked in: ocfs2 
ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 
configfs nfs lockd nfs_acl sunrpc vzethdev vznetdev simfs vzrst vzcpt tun 
vzdquota vzmon vzdev xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS 
iptable_mangle iptable_filter xt_multiport xt_limit xt_dscp ipt_REJECT 
ip_tables x_tables ipv6 sha1_generic drbd cn loop psmouse i2c_i801 rng_core 
serio_raw i2c_core pcspkr iTCO_wdt button shpchp i3000_edac pci_hotplug 
edac_core evdev dcdbas ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod 
raid1 md_mod ide_cd_mod cdrom ata_generic libata dock sd_mod piix usb_storage 
floppy ide_pci_generic ide_core mptsas mptscsih mptbase scsi_transport_sas 
ehci_hcd scsi_mod uhci_hcd usbcore tg3 thermal processor fan thermal_sys
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] 
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] Pid: 2044, comm: 
dlm_thread Not tainted (2.6.26-2-openvz-686 #1 036test001)
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] EIP: 0060:[] 
EFLAGS: 00010046 CPU: 2
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] EIP is at 
ocfs2_locking_ast+0x210/0x44a [ocfs2]
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] EAX: 0241 EBX: 
da123394 ECX: 0286 EDX: 0002
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131] ESI: 0002 EDI: 
da12339c EBP: f7008000 ESP: f716ff50
Jun 25 00:22:03 hoster-dmz-1 kernel: [222310.043131]  DS: 007b ES: 007b FS: 
00d8 GS:  SS: 0068
Jun 25 00:22:03 hoster-dmz-1

Bug#538158: BUG: soft lockup - CPU#5 stuck for 62s with 2.6.26-2-686-bigmem kernel

Jonathan Nieder wrote:
> Jonathan Nieder wrote:

>>  - Arcady, are you still experiencing the soft lockups in default_idle?
>>If so, can you confirm Juan's finding that 2.6.32 from
>>lenny-backports avoids trouble?
>
> Ping.  If you no longer have access to a system that produced these
> problems or time to debug it, that's fine, but please let us know so
> we can stop tracking it.

Trying again with a different email address.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101100237.ga5...@elie.hsd1.il.comcast.net

Processed: Re: [linux-image-2.6.30-1-amd64] VIA-Rhine II network interface lost connectivity

Processing commands for cont...@bugs.debian.org:

> tags 549606 - moreinfo
Bug #549606 [linux-2.6] [linux-image-2.6.30-1-amd64] VIA-Rhine II network 
interface lost connectivity
Bug #575833 [linux-2.6] BUG: scheduling while atomic oops on Alix 3D2 and 3D3
Bug #641919 [linux-2.6] linux-image-3.0.0-1-amd64: VIA-Rhine II resetting: 
network connectivity lost
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
549606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132541229120736.transcr...@bugs.debian.org

Processed: Re: firmware-atheros doesn't load for Atheros AR3011

Processing commands for cont...@bugs.debian.org:

> found 641749 linux-2.6/3.1.4-1
Bug #641749 [linux-2.6] firmware-atheros doesn't load for Atheros AR3011
Bug Marked as found in versions linux-2.6/3.1.4-1.
> tags 641749 - moreinfo
Bug #641749 [linux-2.6] firmware-atheros doesn't load for Atheros AR3011
Removed tag(s) moreinfo.
> severity 605030 important
Bug #605030 [linux-2.6] general: bluetooth adapter ar3011 on acer aspire 5553g 
don't start after shutdown
Severity set to 'important' from 'normal'

> merge 641749 605030
Bug#605030: general: bluetooth adapter ar3011 on acer aspire 5553g don't start 
after shutdown
Bug#641749: firmware-atheros doesn't load for Atheros AR3011
Merged 605030 641749.

>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
641749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641749
605030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132541275422430.transcr...@bugs.debian.org

Bug#653913: linux-image-3.1.0-1-amd64: ASUS k53U audio detect but no output

2012-01-01 Thread Wade Jan Barclay Donk

Package: linux-2.6
Version: 3.1.5-1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

upgraded stable to wheezy.
audio chipset detects but there is no audio output.
the card is configurable from alsamixer but no is sound heard.

-- Package-specific info:
** Version:
Linux version 3.1.0-1-amd64 (Debian 3.1.5-1) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-7) ) #1 SMP Sun Dec 11 20:36:41 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 
root=UUID=53cfc19c-21c0-472c-9072-801eefe31dfe ro quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[8.375166] snd_hda_intel :00:14.2: PCI INT A -> GSI 16 (level, low) -> 
IRQ 16
[8.489719] hda_codec: ALC269VB: BIOS auto-probing.
[8.494092] input: HDA ATI SB Mic as 
/devices/pci:00/:00:14.2/sound/card1/input13
[8.494373] input: HDA ATI SB Headphone as 
/devices/pci:00/:00:14.2/sound/card1/input14
[9.406764] input: PS/2 Logitech Wheel Mouse as 
/devices/platform/i8042/serio1/input/input15
[   10.498812] Adding 7809020k swap on /dev/sda6.  Priority:-1 extents:1 
across:7809020k 
[   10.817189] EXT3-fs (sda5): using internal journal
[   10.970462] loop: module loaded
[   13.065086] r8169 :03:00.0: eth0: link down
[   13.065108] r8169 :03:00.0: eth0: link down
[   13.066484] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   14.736318] r8169 :03:00.0: eth0: link up
[   14.737477] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   15.397511] input: ACPI Virtual Keyboard Device as 
/devices/virtual/input/input16
[   16.249616] lp: driver loaded but no devices found
[   16.397780] ppdev: user-space parallel port driver
[   18.189153] Bluetooth: Core ver 2.16
[   18.189213] NET: Registered protocol family 31
[   18.189218] Bluetooth: HCI device and connection manager initialized
[   18.189225] Bluetooth: HCI socket layer initialized
[   18.189229] Bluetooth: L2CAP socket layer initialized
[   18.189242] Bluetooth: SCO socket layer initialized
[   18.212349] Bluetooth: RFCOMM TTY layer initialized
[   18.212363] Bluetooth: RFCOMM socket layer initialized
[   18.212367] Bluetooth: RFCOMM ver 1.11
[   18.301413] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   18.301421] Bluetooth: BNEP filters: protocol multicast
[   20.308654] [fglrx] ATIF platform detected with notification ID: 0x81
[   21.797102] powernow-k8: Found 1 AMD C-60 APU with Radeon(tm) HD Graphics (2 
cpu cores) (version 2.20.00)
[   21.797131] powernow-k8: Core Performance Boosting: on.
[   21.797227] powernow-k8:0 : pstate 0 (1000 MHz)
[   21.797233] powernow-k8:1 : pstate 1 (800 MHz)
[   22.778606] fglrx_pci :00:01.0: irq 42 for MSI/MSI-X
[   22.780352] [fglrx] Firegl kernel thread PID: 1809
[   22.780551] [fglrx] Firegl kernel thread PID: 1810
[   22.780731] [fglrx] Firegl kernel thread PID: 1811
[   22.780940] [fglrx] IRQ 42 Enabled
[   23.194734] [fglrx] Gart USWC size:1116 M.
[   23.194748] [fglrx] Gart cacheable size:442 M.
[   23.194766] [fglrx] Reserved FB block: Shared offset:0, size:100 
[   23.194777] [fglrx] Reserved FB block: Unshared offset:fc81000, size:37f000 
[   23.194787] [fglrx] Reserved FB block: Unshared offset:17ff4000, size:c000 
[   24.944101] eth0: no IPv6 routers present
[   24.976683] ACPI Error: Needed [Integer/String/Buffer], found [Reference] 
88013a0ac588 (20110623/exresop-422)
[   24.976701] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands 
for [OpcodeName unavailable] (20110623/dswexec-460)
[   24.976714] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.AF03] 
(Node 88013a673ce0), AE_AML_OPERAND_TYPE (20110623/psparse-536)
[   24.976736] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.ATIF] 
(Node 88013a673f60), AE_AML_OPERAND_TYPE (20110623/psparse-536)
[  301.066703] [fglrx] IRQ 42 Disabled
[  310.845072] [fglrx] ATIF platform detected with notification ID: 0x81
[  312.924807] fglrx_pci :00:01.0: irq 42 for MSI/MSI-X
[  312.926958] [fglrx] Firegl kernel thread PID: 3208
[  312.927352] [fglrx] Firegl kernel thread PID: 3209
[  312.927837] [fglrx] Firegl kernel thread PID: 3210
[  312.928116] [fglrx] IRQ 42 Enabled
[  313.092917] [fglrx] Gart USWC size:1116 M.
[  313.092928] [fglrx] Gart cacheable size:442 M.
[  313.092943] [fglrx] Reserved FB block: Shared offset:0, size:100 
[  313.092952] [fglrx] Reserved FB block: Unshared offset:fc81000, size:37f000 
[  313.092960] [fglrx] Reserved FB block: Unshared offset:17ff4000, size:c000 
[  314.564610] ACPI Error: Needed [Integer/String/Buffer], found [Reference] 
88013768bb70 (20110623/exresop-422)
[  314.564634] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands 
for [OpcodeName unavailable] (20110623/dswexec-460)
[  314.564651] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.AF03] 
(Node 88013a673ce0), AE_AML_OPERAND_TYPE (20110623/psp

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

Geert Uytterhoeven dixit:

>Sorry, static inline functions are preferred over macros, unless there's

Can I have reasons? (Also out of curiosity.)

>a really good reason. Out-of-tree kernel code doing stupid things doesn't

I see it like this:

EVERY file that, directly or indirectly, includes hardirq.h has the
overhead of having GCC compile that static inline function, even if
it’s never used (and thus never emitted into the object file). Also,
redefining pr_fmt appears to be a desired thing, not a stupid thing;
if a static inline function uses pr_fmt in the timeframe between it
being redefined and the redefined one’s prerequisites being availab-
le, it would necessarily fail.

In contrast to that, a cpp macro is only evaluated when it’s actual-
ly needed, and by then, the prerequisites would probably be availab-
le. It also has less compile-time overhead (in this case, since the
hardirq.h file is probably included in more files than it is needed,
whereas macros slow down when you use them more than once in all fi-
les they’re defined in.

bye,
//mirabilos
-- 
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the program, which is as sensible as putting all the prepositions
in English text in bold font.   -- Rob Pike in "Notes on Programming in C"


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1201011442550.20...@herc.mirbsd.org

Processed: Reassigning to maintained package

Processing commands for cont...@bugs.debian.org:

> reassign 622887 linux-tools 3.1+41
Bug #622887 [linux-tools-2.6.38] /usr/bin/perf_2.6.38: "perf list" lists 
unsupported events
Warning: Unknown package 'linux-tools-2.6.38'
Bug reassigned from package 'linux-tools-2.6.38' to 'linux-tools'.
Bug No longer marked as found in versions linux-2.6/2.6.38-3.
Bug #622887 [linux-tools] /usr/bin/perf_2.6.38: "perf list" lists unsupported 
events
Bug Marked as found in versions linux-latest-2.6/41.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
622887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132543623614472.transcr...@bugs.debian.org

Bug#627372: Console turns black during boot.

2012-01-01 Thread AlanKim Zimmerman

Solved, properly this time.

The prior dmesg log showed the backlight being set to 0.

This article rwfers to the problem, half way down the page
http://en.gentoo-wiki.com/wiki/Intel_GMA

" Backlight off at boot on 4500M

There is an issue for Acer Aspire 5736z with a GMA 4500M graphics chip,
this seems to affect other laptops too. When you boot this laptop the
screen is blank because the backlight is extinguished (you can read it with
a good flashlight). This issue is present in at least kernels 2.6.39 and
3.0.3, but seems to affect other versions also. The issue arises when you
configure the kernel with the i915 drivers and kernel mode setting.You can
get a display by appending "nomodeset" to the Grub boot command, but this
may stop X from working and you will only have low resolution.One solution
is given here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/752165 :
run "setpci -s 00:02.0 F4.B=00" as root to turn the backlight back on. You
may be able to do this over ssh, depending on your setup, otherwise you
will have to do this with the dark screen."

The setpci solves the issue, and by following  the ubuntu bug fix the
command is put into /etc/rc.local

Alan
On Jan 1, 2012 2:55 PM, "AlanKim Zimmerman"  wrote:

Bug#627372: Console turns black during boot.

AlanKim Zimmerman wrote:

> The setpci solves the issue, and by following  the ubuntu bug fix the
> command is put into /etc/rc.local

Yuck.  Marking as a duplicate of fdo bug 40455.  We can undo that
later if a fix for 40455 doesn't help. :)  Thanks for investigating.

A good next step would be to try 3.2-rc6 or newer from experimental,
since there have been some backlight fixes upstream recently.  Though
I'm not too optimistic yet.

Thanks much,
Jonathan

-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101185353.ga7...@elie.hsd1.il.comcast.net

Bug#627372: Console turns black during boot.

found 627372 linux-2.6/3.2~rc7-1~experimental.1
quit

Jonathan Nieder wrote:

> A good next step would be to try 3.2-rc6 or newer from experimental,

My bad --- you already tested.  Thanks for that, and sorry for the
noise.

If you have time for it, could you try a few intermediate kernels
halfway between 2.6.32 and 3.0 from http://snapshot.debian.org to find
when the bug was introduced?



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101185657.gb7...@elie.hsd1.il.comcast.net

Processed: Re: Console turns black during boot.

Processing commands for cont...@bugs.debian.org:

> found 627372 linux-2.6/3.2~rc7-1~experimental.1
Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during 
boot
Bug Marked as found in versions linux-2.6/3.2~rc7-1~experimental.1.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
627372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132544422618359.transcr...@bugs.debian.org

Processed: reassign 622887 to src:linux-tools, found 622887 in linux-2.6/2.6.38-3

Processing commands for cont...@bugs.debian.org:

> reassign 622887 src:linux-tools 3.1.1-1
Bug #622887 [linux-tools] /usr/bin/perf_2.6.38: "perf list" lists unsupported 
events
Bug reassigned from package 'linux-tools' to 'src:linux-tools'.
Bug No longer marked as found in versions linux-latest-2.6/41.
Bug #622887 [src:linux-tools] /usr/bin/perf_2.6.38: "perf list" lists 
unsupported events
Bug Marked as found in versions linux-tools/3.1.1-1.
> found 622887 linux-2.6/2.6.38-3
Bug #622887 [src:linux-tools] /usr/bin/perf_2.6.38: "perf list" lists 
unsupported events
Bug Marked as found in versions linux-2.6/2.6.38-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
622887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132544465720008.transcr...@bugs.debian.org

Bug#648963: drbd8-modules-2.6.26-2-xen-amd64: initial sync failed for new drbd device

2012-01-01 Thread Giovanni Vaitinadapoule

Hello,

happy New Year !

> De: "Ben Hutchings" 
> À: "Giovanni V." , 648...@bugs.debian.org
> Envoyé: Vendredi 30 Décembre 2011 21:38:41
> Objet: Re: Bug#648963: drbd8-modules-2.6.26-2-xen-amd64: initial sync failed 
> for new drbd device
> On Wed, 2011-11-16 at 16:54 +0400, Giovanni V. wrote:
> > Package: drbd8-modules-2.6.26-2-xen-amd64
> > Version: 2.6.26+8.0.14-6+lenny3
> > Severity: normal
> >
> > Hello,
> >
> > I am using Debian GNU/Linux "Lenny" on servers with xen and drbd.
> > Since upgrade to 5.0.9, it's impossible to synchronise a new drbd
> > device.
> > All works well until upgrade to 5.0.9.
> 
> Are you using a RAID or LVM device under drbd?

Yes I am using software RAID and LVM on sata devices in the order : 
sd[abcd]0 > md0 > lvm > drbdxx

> 
> I applied fixes to the way the md and dm drivers determine I/O limits,
> which in some cases will reduce those limits (and avoid the potential
> for data loss). This appears to have exposed a bug in drbd.
> 
> [...]
> 
> I wonder whether drbd assumes that the I/O limits are the same on both
> machines. Were both machines using the drbd device upgraded?
> 

On previous test, both machines were exactly the sames : hardware and packages 

Regards, Giovanni



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/766083342.9053.1325444734987.JavaMail.root@zimbra

Bug#653913: ASUS k53U audio detect but no output

Hi,

Wade Jan Barclay Donk wrote:

> upgraded stable to wheezy.
> audio chipset detects but there is no audio output.
> the card is configurable from alsamixer but no is sound heard.

Three quick hints:

 - please test without the fglrx driver
 - could you attach output from acpidump and from the alsa-info.sh[1]
   script?
 - if you have time for it, testing a few versions between 2.6.32 and
   3.1 from http://snapshot.debian.org/ would be very helpful.

Thanks and hope that helps,
Jonathan

[1] http://www.alsa-project.org/alsa-info.sh



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101191740.gd7...@elie.hsd1.il.comcast.net

Bug#627372: Console turns black during boot.

2012-01-01 Thread AlanKim Zimmerman

Additional info: the screen needs to be turned on again after lid closure
or screensaver timeout.

It seems to be achieved by creating a file called

/etc/acpi/local/lid.sh.post with the following contents
---
#!/bin/sh

# To fix video-intel backlight off on start bug
setpci -s 00:02.0 F4.B=00
---

and chmod +x /etc/acpi/local/lid.sh.post

Alan

Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen

2012-01-01 Thread Bastian Blank

found 637234 2.6.32-40
severity 637234 serious
thanks

This is unfixed in -40. Almost all mounts goes wrong now with a 3.0 and
3.1 guest.

| [6.420630] blkfront: barrier: write xvdb op failed
| [6.420645] blkfront: xvdb: barrier or flush: disabled
| [6.421088] end_request: I/O error, dev xvdb, sector 128
| [6.421099] end_request: I/O error, dev xvdb, sector 128
| [6.421106] lost page write due to I/O error on xvdb
| [6.421126] btrfs: 1 errors while writing supers

Bastian

-- 
Killing is wrong.
-- Losira, "That Which Survives", stardate unknown



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101205744.ga6...@wavehammer.waldi.eu.org

Processed: Re: Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen

Processing commands for cont...@bugs.debian.org:

> found 637234 2.6.32-40
Bug #637234 {Done: dann frazier } [linux-2.6] 
linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen (also affects ext3 
as of linux-image-3.1.0-1-amd64 et al)
There is no source info for the package 'linux-2.6' at version '2.6.32-40' with 
architecture ''
Unable to make a source version for version '2.6.32-40'
Bug Marked as found in versions 2.6.32-40; no longer marked as fixed in 
versions linux-2.6/2.6.32-40 and reopened.
> severity 637234 serious
Bug #637234 [linux-2.6] linux-image-3.0.0-1-686-pae: I/O errors using ext4 
under xen (also affects ext3 as of linux-image-3.1.0-1-amd64 et al)
Severity set to 'serious' from 'important'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
637234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132545148018579.transcr...@bugs.debian.org

Processed: Re: echo mia crashes

Processing commands for cont...@bugs.debian.org:

> found 597897 firmware-nonfree/0.34
Bug #597897 [firmware-linux-nonfree] RFP: alsa-firmware -- firmware binaries 
used by each alsa-firmware-loader program
Bug #627153 [firmware-linux-nonfree] RFP: alsa-firmware -- firmware binaries 
used by each alsa-firmware-loader program
Bug Marked as found in versions firmware-nonfree/0.34.
Bug Marked as found in versions firmware-nonfree/0.34.
> tags 614610 - wontfix
Bug #614610 [alsa-base] [alsa-base] after feb 22, 2011 Squeeze "upgrade," alsa 
will not load my sound module (echo mia). NO sound.
Removed tag(s) wontfix.
> block 614610 by 597897
Bug #614610 [alsa-base] [alsa-base] after feb 22, 2011 Squeeze "upgrade," alsa 
will not load my sound module (echo mia). NO sound.
Was not blocked by any bugs.
Added blocking bug(s) of 614610: 597897 and 627153
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
614610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132545161519749.transcr...@bugs.debian.org

[m68k] partial success but does not boot: 3.2~rc7

Hi,

I have good and bad news: I got 3.2~rc7 compiled with some
patches, but it’s panicking.

I’ve attached a .tgz with the following content:

a) patches against (a git copy of) the linux-2.6 trunk SVN:

• patches/0001-distinguish-level-of-xz-compression-to-use-for-packa.patch

This is for waldi:

Use varying levels of xz compression for the packages, not always
dpkg-deb’s default of -6, and add a comment for what levels to use
once we can depend on dpkg-deb 1.16.2 after Guillem told me that
it will support -e (extreme). See #652636 for discussion. This was
primarily added here so I had a bit of speedup for building… change
to suit taste, then please commit.

• patches/0002-switch-m68k-to-gcc-4.6.patch

This is for debian-68k:

This is a tendency, our userspace was switched already. It builds,
but I have no idea whether this is a/the cause of it panicking.

Might be useful to commit, though, unless it _is_ the culprit.

• patches/0003-fix-the-aufs-pr_fmt-FTBFS-issue.patch

This is for bwh:

This is the same patch as I sent out in the mail to the AUFS thread
with mid (the
second version, with #undef pr_fmt – the kernel was built with the
first version though, which only differs by generating cpp redefine
warnings, which don’t change the code).

The AUFS module builds, links, but I cannot test whether it loads,
since the kernel doesn’t come up.

Since Geert does not want my other patch, I suppose we’ll need it.

• patches/0004-fix-passing-CFLAGS_KERNEL-to-kbuild.patch

This is for debian-kernel (waldi, probably):

Fix the way a debian/*/defines 'cflags' is passed to kbuild.
Please do commit.

• patches/0005-use-cflags-ffreestanding-at-least-on-m68k-maybe-Clos.patch

This is for waldi and linux-m68k:

Your suggestion to use -ffreestanding indeed Closes: #648996
Please do commit. Depends on 0004.

• patches/0006-Bastian-Blank-do-not-error-out-when-kernel-wedge-ret.patch

This is _from_ waldi via IRC:

18:10⎜ kernel-wedge install-files 3.2.0-rc7
18:10⎜ could not find kernel image at
/usr/share/kernel-wedge/commands/install-files line 103,
⎜ line 2.
18:11⎜ make[2]: *** [install-udeb_m68k] Error 2
18:11⎜«waldi» ich dachte die fehler werden ignoriert …#

19:03⎜ find: ebian/kernel-image-3.2.0-rc7-atari-di': No such file
or directory
19:03⎜ kernel-image-3.2.0-rc7-atari-di will be empty
19:03⎜ find: ebian/nic-shared-modules-3.2.0-rc7-atari-di': No such
file or directory
19:03⎜ nic-shared-modules-3.2.0-rc7-atari-di will be empty
19:03⎜ hrm.
19:03⎜ waldi, was ist da kaputt?
19:03⎜ ich wars nicht

I just wonder why this seems to have been needed in the first place.

18:50⎜ -rw-r--r-- 1 root root 1845989 Jan 1 18:32
⎜
/var/cache/pbuilder/build/cow.937/tmp/buildd/linux-2.6-3.2~rc7/debian/linux-image-3.2.0-rc7-atari/boo
⎜t/vmlinuz-3.2.0-rc7-atari

$sourcedir wrong? $installedname wrong?

No idea whether this should be committed.

• patches/0007-defines-and-changelog-for-my-personal-testing-image.patch

This is for me, just included for the sake of completeness: when I
test-build (not for uploading), I run source and arch:all builds on
an amd64 domU sponsored by zigo, and only arch:any stuff on m68k,
for speed. I disable the amd64 debugging package and other stuff,
and m68k flavours except the one I need (atari) for my tests. It
also shows the changelog entry. It doesn’t show the regeneration
of generated files by d/rules clean.

• work and fail

This is for debian-68k, linux-68k and debian-kernel:

ARAnyM “console” output of a working (3.0) and failing (3.2) boot,
for your debugging pleasure. I can run arbitrary tests against the
failing kernel, as long as they’re limited to [LILO].Args or make
it boot ;-)

I can also provide the files on request:

-rw-r--r-- 1 pbuilder 1234 7951926 Jan 1 18:42
linux-image-3.2.0-rc7-atari_3.2~rc7-1~experimental.1tg1_m68k.deb
and linux-headers* and linux-libc-dev* which are less useful.

bye,
//mirabilos
--
you introduced a merge commit│ % g rebase -i HEAD^^
sorry, no idea and rebasing just fscked │ Segmentation
should have cloned into a clean repo │ fault (core dumped)
if I rebase that now, it's really ugh │ wuahh

blakernl.tgz
Description: Binary data

Bug#627372: Console turns black during boot.

2012-01-01 Thread AlanKim Zimmerman

Hi

Just reflecting on this. I was following Debian testing, and installing the
kernels as they came through. The last one that worked for me was
linux-image-2.6.32-5-686

Alan

On Sun, Jan 1, 2012 at 8:56 PM, Jonathan Nieder  wrote:

> found 627372 linux-2.6/3.2~rc7-1~experimental.1
> quit
>
> Jonathan Nieder wrote:
>
> > A good next step would be to try 3.2-rc6 or newer from experimental,
>
> My bad --- you already tested.  Thanks for that, and sorry for the
> noise.
>
> If you have time for it, could you try a few intermediate kernels
> halfway between 2.6.32 and 3.0 from http://snapshot.debian.org to find
> when the bug was introduced?
>

Bug#627372: Console turns black during boot.

found 627372 linux-2.6/2.6.38-3
quit

AlanKim Zimmerman wrote:

> Just reflecting on this. I was following Debian testing, and installing the
> kernels as they came through. The last one that worked for me was
> linux-image-2.6.32-5-686

FWIW: Debian testing didn't change much during the squeeze freeze, and
then at the start of the wheezy cycle there was a big jump.

  2011-04-01[1]:2.6.32-31 → 2.6.38-3
  2011-05-14[2]:2.6.38-3 → 2.6.38-5
  etc

[1] http://thread.gmane.org/gmane.linux.debian.devel.changes.testing/322
[2] http://thread.gmane.org/gmane.linux.debian.devel.changes.testing/377



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101214059.gg7...@elie.hsd1.il.comcast.net

Processed: Re: Console turns black during boot.

Processing commands for cont...@bugs.debian.org:

> found 627372 linux-2.6/2.6.38-3
Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during 
boot
Bug Marked as found in versions linux-2.6/2.6.38-3.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
627372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132545408130875.transcr...@bugs.debian.org

Bug#602095: [nouveau] black screen after reboot

Hey again,

Julien Tailleur wrote:

> I can't do that. If I unblacklist nouveau and remove the nvidia driver, I
> just get a black screen right after grub and do not have access to dmesg.

Ah, that makes sense.

When you get the black screen, is the machine still usable?  E.g., can
you ssh into it, or can you run commands "blindly"?  Does ctrl-alt-delete
work?  Does the magic sysrq key work?  Can you see text on the screen
if you use a bright flashlight to look at it?

Hopefully something like the following can work:

dmesg >log.before && modprobe nouveau && dmesg >log.after

It might also be possible to get the relevant information from
/var/log/dmesg or /var/log/dmesg.0 after rebooting.

Sorry for the slow response, and hope that helps.
Jonathan

-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120101221617.gc25...@elie.hsd1.il.comcast.net

Bug#653913: partial workaround

2012-01-01 Thread meta spike

under /dev/snd/ - pcmC1D0p is a workin interfaceg for ATI R6xx HDMI, but
apps look for pcmC0D0p, I can ln it, which works for speaker output, but
not headphones, mic etc.

here is the output of ln /dev/snd/

bcontrolC1  hwC1D0pcmC0D3p  pcmC1D0p  timer
controlC0  hwC0D0pcmC1D0c  seq

under alsamixer, there are two devices: 0 HD-Audio generic 1: HDA AT SB. If
I ln /dev/snd/pcmC1D0p /dev/pcmC0D0p - then pcm appears under HD-Audio
Generic and applications can use that channel. Is ?there a way to configure
this properly?

thanks.

Bug#648996: linux-2.6: FTBFS [m68k] in modpost: "strlen" [iscsi_target_mod.ko] undefined! (and others)

Dixi quod…

>So, please, compile the Linux kernel with -ffreestanding, too.

Just to keep this bugreport in the loop: that fixes the FTBFS error.
http://lists.debian.org/debian-68k/2012/01/msg0.html

bye,
//mirabilos
-- 
 ch: good, you corrected yourself. ppl tend to tweet such news
immediately, sth. like "grml devs seem to be buyable" dileks: we
_are_. if you throw enough money in our direction, things will happen
 everyone is buyable, it's just a matter of priceand now
comes [mira] and uses this as a signature ;0   -- they asked for it…



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1201012310590.20...@herc.mirbsd.org

Re: [m68k] partial success but does not boot: 3.2~rc7

On Sun, 2012-01-01 at 21:16 +, Thorsten Glaser wrote:
[...]
> • patches/0006-Bastian-Blank-do-not-error-out-when-kernel-wedge-ret.patch
> 
> This is _from_ waldi via IRC:
>
> 18:10⎜ kernel-wedge install-files 3.2.0-rc7
> 18:10⎜ could not find kernel image at 
> /usr/share/kernel-wedge/commands/install-files line 103,
>  ⎜ line 2.
> 18:11⎜ make[2]: *** [install-udeb_m68k] Error 2
> 18:11⎜«waldi» ich dachte die fehler werden ignoriert …#
> 
> 19:03⎜ find: ebian/kernel-image-3.2.0-rc7-atari-di': No such file 
> or directory
> 19:03⎜ kernel-image-3.2.0-rc7-atari-di will be empty
> 19:03⎜ find: ebian/nic-shared-modules-3.2.0-rc7-atari-di': No 
> such file or directory
> 19:03⎜ nic-shared-modules-3.2.0-rc7-atari-di will be empty
> 19:03⎜ hrm.
> 19:03⎜ waldi, was ist da kaputt?
> 19:03⎜ ich wars nicht
> 
> I just wonder why this seems to have been needed in the first place.

It is quite possible that m68k kernel udebs have not been built for some
years, though the configuration has been updated along with other
architectures.

The module list for nic-shared-modules on m68k looks wrong in that there
are several driver modules listed there; those belong in nic-modules or
nic-extra-modules.  If m68k doesn't have any network drivers using the
library modules such as mii then the package should be disabled by
removing the module list file.

> 18:50⎜ -rw-r--r-- 1 root root 1845989 Jan  1 18:32
>  ⎜
> /var/cache/pbuilder/build/cow.937/tmp/buildd/linux-2.6-3.2~rc7/debian/linux-image-3.2.0-rc7-atari/boo
>  ⎜t/vmlinuz-3.2.0-rc7-atari
> 
> $sourcedir wrong? $installedname wrong?

Did you also build the amiga and mac flavours?  The kernel-versions file
for m68k lists all three flavours.

> No idea whether this should be committed.

Hell no.  We must either fix or remove the kernel-wedge configuration
for m68k.  (I already did the latter for alpha.)

[...]
> • work and fail
> 
> This is for debian-68k, linux-68k and debian-kernel:
> 
> ARAnyM “console” output of a working (3.0) and failing (3.2) boot,
> for your debugging pleasure. I can run arbitrary tests against the
> failing kernel, as long as they’re limited to [LILO].Args or make
> it boot ;-)

This is presumably triggered by enabling CPU topology information in
sysfs on UP systems.  This is a Debian patch for 3.2
(features/all/topology-Provide-CPU-topology-in-sysfs-in-SMP-configura.patch) 
but has been accepted upstream for 3.3.

My guess is that on m68k get_cpu_sysdev(0) returns NULL and thus
topology_add_dev() passes an invalid pointer into sysfs_create_group().
So either m68k (and maybe some other architectures with no SMP support)
need to be fixed or the CPU topology code needs to allow for this.

Ben.

-- 
Ben Hutchings
Humour is the best antidote to reality.

signature.asc
Description: This is a digitally signed message part

Bug#653913: partial workaround

On Mon, 2012-01-02 at 12:06 +1300, meta spike wrote:
> under /dev/snd/ - pcmC1D0p is a workin interfaceg for ATI R6xx HDMI,
> but apps look for pcmC0D0p, I can ln it, which works for speaker
> output, but not headphones, mic etc. 
> 
> here is the output of ln /dev/snd/
> 
> bcontrolC1  hwC1D0pcmC0D3p  pcmC1D0p  timer
> controlC0  hwC0D0pcmC1D0c  seq
> 
> 
> under alsamixer, there are two devices: 0 HD-Audio generic 1: HDA AT
> SB. If I ln /dev/snd/pcmC1D0p /dev/pcmC0D0p - then pcm appears under
> HD-Audio Generic and applications can use that channel. Is ?there a
> way to configure this properly?

Yes, see  and
/usr/share/doc/libasound2/examples/asoundrc.txt.gz

Ben.

-- 
Ben Hutchings
Humour is the best antidote to reality.


signature.asc
Description: This is a digitally signed message part

Processed: Re: FTBFS [m68k] in modpost: "strlen" [iscsi_target_mod.ko] undefined! (and others)

Processing commands for cont...@bugs.debian.org:

> tags 648996 + upstream
Bug #648996 [linux-2.6] linux-2.6: FTBFS [m68k] in modpost: "strlen" 
[iscsi_target_mod.ko] undefined! (and others)
Added tag(s) upstream.
> found 648996 linux-2.6/3.2~rc7-1~experimental.1
Bug #648996 [linux-2.6] linux-2.6: FTBFS [m68k] in modpost: "strlen" 
[iscsi_target_mod.ko] undefined! (and others)
Bug Marked as found in versions linux-2.6/3.2~rc7-1~experimental.1.
> forwarded 648996 http://thread.gmane.org/gmane.linux.kernel/1234214
Bug #648996 [linux-2.6] linux-2.6: FTBFS [m68k] in modpost: "strlen" 
[iscsi_target_mod.ko] undefined! (and others)
Set Bug forwarded-to-address to 
'http://thread.gmane.org/gmane.linux.kernel/1234214'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
648996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132546142231370.transcr...@bugs.debian.org

Re: [m68k] partial success but does not boot: 3.2~rc7

On Sun, 2012-01-01 at 23:27 +, Ben Hutchings wrote:
> On Sun, 2012-01-01 at 21:16 +, Thorsten Glaser wrote:
[...]
> > • work and fail
> > 
> > This is for debian-68k, linux-68k and debian-kernel:
> > 
> > ARAnyM “console” output of a working (3.0) and failing (3.2) boot,
> > for your debugging pleasure. I can run arbitrary tests against the
> > failing kernel, as long as they’re limited to [LILO].Args or make
> > it boot ;-)
> 
> This is presumably triggered by enabling CPU topology information in
> sysfs on UP systems.  This is a Debian patch for 3.2
> (features/all/topology-Provide-CPU-topology-in-sysfs-in-SMP-configura.patch) 
> but has been accepted upstream for 3.3.
> 
> My guess is that on m68k get_cpu_sysdev(0) returns NULL and thus
> topology_add_dev() passes an invalid pointer into sysfs_create_group().
> So either m68k (and maybe some other architectures with no SMP support)
> need to be fixed or the CPU topology code needs to allow for this.

None of these architectures appears to call register_cpu():

c6x frv h8300 m68k microblaze openrisc score um xtensa

and therefore they will all panic at boot following this change (commit
ccbc60d3e19a1b6ae66ca0d89b3da02dde62088b).  So either I can try to fix
them or else it must be reverted for now.

Ben.

-- 
Ben Hutchings
Humour is the best antidote to reality.


signature.asc
Description: This is a digitally signed message part

Re: [m68k] partial success but does not boot: 3.2~rc7

Ben Hutchings dixit:

>It is quite possible that m68k kernel udebs have not been built for some
>years, though the configuration has been updated along with other
>architectures.

I don’t think that is it, as the last upload had this in .changes:

[…]
 4b1a4046ca58561cc6c94d020a9f10f4 1997696 debian-installer extra 
kernel-image-3.0.0-2-amiga-di_3.0.0-6_m68k.udeb
 af52e25d6186c6fd5c9b20888221f97a 35168 debian-installer standard 
nic-shared-modules-3.0.0-2-amiga-di_3.0.0-6_m6
 808da40f5886053613dceae960cc64f8 38508 debian-installer optional 
ppp-modules-3.0.0-2-amiga-di_3.0.0-6_m68k.udeb
 e664ddcea14d6a5f341a8cdfefefac2e 10918 debian-installer standard 
cdrom-core-modules-3.0.0-2-amiga-di_3.0.0-6_m6
 8f1fa83300a63dc0017eafc97da549cd 15636 debian-installer standard 
scsi-modules-3.0.0-2-amiga-di_3.0.0-6_m68k.ude
 1ceac41404a52273068c08d02d993557 305086 debian-installer extra 
btrfs-modules-3.0.0-2-amiga-di_3.0.0-6_m68k.udeb
 f37e385c35fbae32f93d78312054009f 18960 debian-installer standard 
isofs-modules-3.0.0-2-amiga-di_3.0.0-6_m68k.ud
[…]

>The module list for nic-shared-modules on m68k looks wrong in that there
>are several driver modules listed there; those belong in nic-modules or
>nic-extra-modules.  If m68k doesn't have any network drivers using the
>library modules such as mii then the package should be disabled by
>removing the module list file.

 d4ef87ebeac4a5177f560a7627d9ea52 13250 debian-installer standard 
nic-shared-modules-3.0.0-2-atari-di_3.0.0-6_m6

It built last time and seems to have some content.

>> 18:50⎜ -rw-r--r-- 1 root root 1845989 Jan  1 18:32
>>  ⎜
>> /var/cache/pbuilder/build/cow.937/tmp/buildd/linux-2.6-3.2~rc7/debian/linux-image-3.2.0-rc7-atari/boo
>>  ⎜t/vmlinuz-3.2.0-rc7-atari
>> 
>> $sourcedir wrong? $installedname wrong?
>
>Did you also build the amiga and mac flavours?  The kernel-versions file
>for m68k lists all three flavours.

Ah, that might be it. On the other hand, I seem to recall it erroring out
on the atari part. Not too sure.

>> No idea whether this should be committed.
>
>Hell no.  We must either fix or remove the kernel-wedge configuration
>for m68k.  (I already did the latter for alpha.)

OK. I hope “we” (and maybe, when^Wif they wake up, the m68k porters)
can fix it, instead. Wouter’s built a d-i during DebĆevapčićiConf,
after all.

>My guess is that on m68k get_cpu_sysdev(0) returns NULL and thus
>topology_add_dev() passes an invalid pointer into sysfs_create_group().
>So either m68k (and maybe some other architectures with no SMP support)
>need to be fixed or the CPU topology code needs to allow for this.

@linux-m68k, are you listening in? ;-)

Goodnight, and happy new year,
//mirabilos
-- 
> Hi, does anyone sell openbsd stickers by themselves and not packaged
> with other products?
No, the only way I've seen them sold is for $40 with a free OpenBSD CD.
-- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/pine.bsm.4.64l.1201012337470.20...@herc.mirbsd.org

[Fwd: Patch Upstream: drm/radeon/kms: bail on BTC parts if MC ucode is missing]

As I suggested a while back, radeon really doesn't work without firmware
on some chips.

Ben.

 Forwarded Message 
From: Gregs git-bot 
To: g...@kroah.com, sta...@vger.kernel.org
Subject: Patch Upstream: drm/radeon/kms: bail on BTC parts if MC ucode is 
missing
Date: Sun, 1 Jan 2012 13:20:53 -0500 (EST)

commit: 77e00f2ea94abee1ad13bdfde19cf7aa25992b0e
From: Alex Deucher 
Date: Wed, 21 Dec 2011 11:58:17 -0500
Subject: drm/radeon/kms: bail on BTC parts if MC ucode is missing

We already do this for cayman, need to also do it for
BTC parts.  The default memory and voltage setup is not
adequate for advanced operation.  Continuing will
result in an unusable display.

Signed-off-by: Alex Deucher 
Cc: sta...@kernel.org
Cc: Jean Delvare 
Signed-off-by: Dave Airlie 
---
 drivers/gpu/drm/radeon/evergreen.c |   12 
 1 files changed, 12 insertions(+), 0 deletions(-)

diff --git a/drivers/gpu/drm/radeon/evergreen.c 
b/drivers/gpu/drm/radeon/evergreen.c
index 5e00d16..92c9628 100644
--- a/drivers/gpu/drm/radeon/evergreen.c
+++ b/drivers/gpu/drm/radeon/evergreen.c
@@ -3276,6 +3276,18 @@ int evergreen_init(struct radeon_device *rdev)
rdev->accel_working = false;
}
}
+
+   /* Don't start up if the MC ucode is missing on BTC parts.
+* The default clocks and voltages before the MC ucode
+* is loaded are not suffient for advanced operations.
+*/
+   if (ASIC_IS_DCE5(rdev)) {
+   if (!rdev->mc_fw && !(rdev->flags & RADEON_IS_IGP)) {
+   DRM_ERROR("radeon: MC ucode required for NI+.\n");
+   return -EINVAL;
+   }
+   }
+
return 0;
 }
 
-- 
1.7.3.4
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Ben Hutchings
All the simple programs have been written, and all the good names taken.


signature.asc
Description: This is a digitally signed message part

Bug#653913:

2012-01-01 Thread meta spike

~/.asoundrc

pcm.!default
type hw
card 1
}

ctl.!default {
type hw
card 1
}

now the HDA ATI SB is recognized by programs as the default interface as
opposed to HD-Audio Generic and everything works fine. thanks for your help,

Processed: reassign 653913 to src:alsa-lib ...

Processing commands for cont...@bugs.debian.org:

> reassign 653913 src:alsa-lib
Bug #653913 [linux-2.6] linux-image-3.1.0-1-amd64: ASUS k53U audio detect but 
no output
Bug reassigned from package 'linux-2.6' to 'src:alsa-lib'.
Bug No longer marked as found in versions 3.1.5-1.
> retitle 653913 Default device selection is unpredictable and poorly documented
Bug #653913 [src:alsa-lib] linux-image-3.1.0-1-amd64: ASUS k53U audio detect 
but no output
Changed Bug title to 'Default device selection is unpredictable and poorly 
documented' from 'linux-image-3.1.0-1-amd64: ASUS k53U audio detect but no 
output'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
653913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13254682021633.transcr...@bugs.debian.org

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt


Geert Uytterhoeven:
> If the Makefile refers to the macro, perhaps the Makefile should
> define it, and pass it with -D?

??
Instead of defining it in Makefile, "-imacros linux/aufs_name.h" is
added. Or do you mean -imacros is useless?


J. R. Okajima


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5496.1325469852@jrobl

Processed: tagging 653776

Processing commands for cont...@bugs.debian.org:

> tags 653776 + pending
Bug #653776 [src:linux-2.6] please enable DVB_USB_IT913X in kernels >= 3.2
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
653776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.132547308122479.transcr...@bugs.debian.org

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt


Thorsten Glaser:
> >It introduces a new separated file include/linux/aufs_name.h.
>
> Isn=E2=80=99t that a bit overkill?

Hmm, I may have to agree with that.
Honestly speaking, I don't like this approach.
But embedding (expanding) AUFS_NAME is worse for me.


> >If the Makefile refers to the macro, perhaps the Makefile should
> >define it, and pass it with -D?
>
> Indeed. I like Ben=E2=80=99s patch better. But if it must be a separate
> file, please move the pr_fmt definition out of the Makefile and
> into that file, too. Code doesn=E2=80=99t belong into a Makefile IMHO.

You guys don't see "-imacros linux/aufs_name.h" in Makefile?
Or do I totaly miunderstand -imacros?

--
> Ben Hutchings dixit:
>
> >-ccflags-y +=3D -D'pr_fmt(fmt)=3DAUFS_NAME"\040%s:%d:%s[%d]:\040"fmt,__fun=
> c__,__LINE__,current->comm,current->pid'
> >+ccflags-y +=3D -D'pr_fmt(fmt)=3D"aufs\040%s:%d:%s[%d]:\040"fmt,__func__,_=
> _LINE__,current->comm,current->pid'
>
> Sadly, this doesn=E2=80=99t work either:
:::
> /tmp/buildd/linux-2.6-3.2~rc7/debian/build/source_m68k_none/arch/m68k/inclu=
> de/asm/hardirq.h:23:2: error: dereferencing pointer to incomplete type
:::
> The difference between a static inline function and a pr=C3=A6processor
> macro makes the difference. I know, now, why I never used the former
> myself =E2=98=BA I guess =E2=80=9Ccurrent=E2=80=9D is not defined there.

That must be an error around the "current" macro which I was afraid.

--

> What do you think of this (untested)? I omitted the Documentation/**
> patch as that part it not present in the Debian Linux kernel.
:::
+#define AUFS_NAME  "aufs"
+#define pr_fmt(fmt)
AUFS_NAME"\040%s:%d:%s[%d]:\040"fmt,__func__,__LINE__,current->comm,current->pid

Here are the comments from me.
- aufs_name.h is used both in kernel-space and user-space, so we need
  "#ifdef __KERNEL__"
- the macro may already be defined, so we need "#ifndef pr_fmt"
  now we should decide which we force (choose), the pr_fmt macro we
  define in aufs or the one previously defined somewhere else.
And I chose "defined aufs aufs".
These are also reasons to put it in Makefile.

--

> well, it compiles (with warnings, see below). I=E2=80=99ll know if it links
> and loads tomorrow, I guess (unless the other problems are still
> there).
>
> /tmp/buildd/linux-2.6-3.2~rc7/debian/build/source_m68k_none/include/linux/a=
> ufs_name.h:27:0: warning: "pr_fmt" redefined [enabled by default]
> /tmp/buildd/linux-2.6-3.2~rc7/debian/build/source_m68k_none/include/linux/p=
> rintk.h:152:0: note: this is the location of the previous definition
>
> Version 2 of this patch (attached) fixes this by #undef pr_fmt
> before defining it. Please decide whether you want to fix it

Yes, undefining will be necessary if we move the macro difinition into
the header file. Or we may add a condition "#ifndef pr_fmt" when we
define the macro in the header. In other words,
- adding a condition means giving precedence to the difinition in
  somewhere else.
- undefining means forcing the definition in aufs.
But this "forcing" is not enough since the macro can be defined _before_
including the header. I know you put "-include linux/aufs_name.h" in
Makefile, but it is not enough either since the macro _may_ be defined
in sched.h or somewhere else which will be included before aufs_name.h.
Also I understand it is not a big problem. But I hope you would agree
that unconditionally or blindly defined macro is effective (or less
subject to bug) in a single module.

So I still think it is better to define it in Makefile.
If I remove refering the "current" macro in the definition, then the
life will be easier, but it is still useful and I want to keep
it. Additonally it is not a essential problem I think.
Finally I'd like to add sched.h between aufs_name and pr_fmt (see the
attached patch).
How do you think?


J. R. Okajima

--- a/fs/aufs/Makefile
+++ b/fs/aufs/Makefile
@@ -10,6 +10,7 @@ endif
 ccflags-y += -DDEBUG
 # sparse doesn't allow spaces
 ccflags-y += -imacros linux/aufs_name.h
+ccflags-y += -include linux/sched.h
 ccflags-y += 
-D'pr_fmt(fmt)=AUFS_NAME"\040%s:%d:%s[%d]:\040"fmt,__func__,__LINE__,current->comm,current->pid'
 
 obj-$(CONFIG_AUFS_FS) += aufs.o


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5968.1325473093@jrobl

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt

On Mon, 2012-01-02 at 11:58 +0900, sf...@users.sourceforge.net wrote:
> Thorsten Glaser:
> > >It introduces a new separated file include/linux/aufs_name.h.
> >
> > Isn=E2=80=99t that a bit overkill?
> 
> Hmm, I may have to agree with that.
> Honestly speaking, I don't like this approach.
> But embedding (expanding) AUFS_NAME is worse for me.

Why, how often do you expect to change AUFS_NAME?

[...]
> So I still think it is better to define it in Makefile.
> If I remove refering the "current" macro in the definition, then the
> life will be easier, but it is still useful and I want to keep
> it. Additonally it is not a essential problem I think.
> Finally I'd like to add sched.h between aufs_name and pr_fmt (see the
> attached patch).
> How do you think?

I think it would be much better to put this in fs/aufs/aufs.h and make
each of fs/aufs/*.c include that first.

> J. R. Okajima
> 
> --- a/fs/aufs/Makefile
> +++ b/fs/aufs/Makefile
> @@ -10,6 +10,7 @@ endif
>  ccflags-y += -DDEBUG
>  # sparse doesn't allow spaces
>  ccflags-y += -imacros linux/aufs_name.h
> +ccflags-y += -include linux/sched.h
>  ccflags-y += 
> -D'pr_fmt(fmt)=AUFS_NAME"\040%s:%d:%s[%d]:\040"fmt,__func__,__LINE__,current->comm,current->pid'
>  
>  obj-$(CONFIG_AUFS_FS) += aufs.o

The comment about sparse belongs immediately before the definition of
pr_fmt.

Ben.

-- 
Ben Hutchings
All the simple programs have been written, and all the good names taken.


signature.asc
Description: This is a digitally signed message part

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt


Ben Hutchings:
> Why, how often do you expect to change AUFS_NAME?

I don't know.
I just don't want call myself idiot when it happens.


> I think it would be much better to put this in fs/aufs/aufs.h and make
> each of fs/aufs/*.c include that first.

Yes, that is my another option I have considered.
Also I am considering to move AUFS_NAME back into aufs_type.h.

In aufs_type.h:
(at the top)
#define AUFS_NAME ...
#if KERNEL
#define pr_fmt ...
#include sched.h
#endif

and include aufs_type.h at the top of source files.


> The comment about sparse belongs immediately before the definition of
> pr_fmt.

Yes, I am changing like this.

--- a/fs/aufs/Makefile
+++ b/fs/aufs/Makefile
@@ -8,9 +8,10 @@ endif
 # cf. include/linux/kernel.h
 # enable pr_debug
 ccflags-y += -DDEBUG
+# sparse requires the fullpath
+ccflags-y += -imacros ${srctree}/include/linux/aufs_name.h
+ccflags-y += -include ${srctree}/include/linux/sched.h
 # sparse doesn't allow spaces
-ccflags-y += -imacros linux/aufs_name.h
-ccflags-y += -include linux/sched.h
 ccflags-y += 
-D'pr_fmt(fmt)=AUFS_NAME"\040%s:%d:%s[%d]:\040"fmt,__func__,__LINE__,current->comm,current->pid'
 
 obj-$(CONFIG_AUFS_FS) += aufs.o


J. R. Okajima


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/7012.1325476910@jrobl

Processed: Re: __unused in libbsd. workaround for #522773 (linux) and #522774 (libc)

Processing commands for cont...@bugs.debian.org:

> tags 522773 + upstream
Bug #522773 [linux-libc-dev] linux-libc-dev: uses "__unused" as identifier, 
which is traditionally used by BSD as macro
Added tag(s) upstream.
> found 522773 linux-2.6/3.2~rc7-1~experimental.1
Bug #522773 [linux-libc-dev] linux-libc-dev: uses "__unused" as identifier, 
which is traditionally used by BSD as macro
Bug Marked as found in versions linux-2.6/3.2~rc7-1~experimental.1.
> # see also 
> https://lists.linux-foundation.org/pipermail/bugme-new/2009-September/022869.html
> forwarded 522773 http://thread.gmane.org/gmane.linux.kernel/1234225
Bug #522773 [linux-libc-dev] linux-libc-dev: uses "__unused" as identifier, 
which is traditionally used by BSD as macro
Changed Bug forwarded-to-address to 
'http://thread.gmane.org/gmane.linux.kernel/1234225' from 
'http://bugzilla.kernel.org/show_bug.cgi?id=14186'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
522773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13254777279336.transcr...@bugs.debian.org

Re: [PATCH] aufs: Do not refer to AUFS_NAME in pr_fmt