Bug#599254: linux-image-2.6.36-rc5-686: icedove causes BUG when trying to open mail with very large attachments on i915

[Willi Mann]

Package: linux-2.6
Version: 2.6.36~rc5-1~experimental.1
Severity: important

When trying to open a mail with with large images (e.g. 3 images with 
4368x2912) in icedove the screen freezes and after a few seconds, a beep
 occurs (this is probably the kerneloops daemon) and the following messages 
occur in the kernel log:

Oct  6 09:19:58 hostname kernel: [  257.454598] [ cut here 
]
Oct  6 09:19:58 hostname kernel: [  257.454660] kernel BUG at 
/build/buildd-linux-2.6_2.6.36~rc5-1~experimental.1-i386-I9JHPF/linux-2.6-2.6.36~rc5/debian/build/source_i386_none/drivers/gpu/drm/i915/i915_gem.c:1444!
Oct  6 09:19:58 hostname kernel: [  257.454810] invalid opcode:  [#1] SMP 
Oct  6 09:19:58 hostname kernel: [  257.454858] last sysfs file: 
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/energy_full
Oct  6 09:19:58 hostname kernel: [  257.454975] Modules linked in: inet_diag 
acpi_cpufreq mperf cpufreq_powersave cpufreq_conservative cpufreq_stats 
cpufreq_userspace ppdev lp tun sco bridge stp bnep rfcomm l2cap crc16 bluetooth 
uinput fuse nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc 
firewire_sbp2 loop arc4 ecb snd_hda_codec_conexant snd_hda_intel iwlagn 
snd_hda_codec iwlcore snd_hwdep thinkpad_acpi snd_pcm_oss snd_mixer_oss snd_pcm 
pcmcia r852 sm_common nand nand_ids nand_ecc snd_seq_midi mac80211 parport_pc 
snd_rawmidi mtd parport snd_seq_midi_event cfg80211 yenta_socket pcmcia_rsrc 
pcmcia_core snd_seq snd_timer snd_seq_device psmouse joydev snd tpm_tis tpm 
soundcore i2c_i801 wmi rfkill battery evdev serio_raw ac processor 
snd_page_alloc tpm_bios nvram ext3 jbd mbcache netconsole configfs hid_cherry 
usbhid hid sg sd_mod crc_t10dif sr_mod cdrom i915 ahci libahci drm_kms_helper 
uhci_hcd sdhci_pci sdhci libata drm ehci_hcd i2c_algo_bit i2c_core scsi_mod 
mmc_core
  firewire_ohci video led_class firewire
Oct  6 09:19:58 hostname kernel: _core crc_itu_t thermal usbcore thermal_sys 
output e1000e nls_base button [last unloaded: scsi_wait_scan]
Oct  6 09:19:58 hostname kernel: [  257.456386] 
Oct  6 09:19:58 hostname kernel: [  257.456406] Pid: 1841, comm: Xorg Not 
tainted 2.6.36-rc5-686 #1 208252G/208252G
Oct  6 09:19:58 hostname kernel: [  257.456478] EIP: 0060:[] EFLAGS: 
00213246 CPU: 0
Oct  6 09:19:58 hostname kernel: [  257.456549] EIP is at 
i915_gem_object_put_pages+0x13/0xb2 [i915]
Oct  6 09:19:58 hostname kernel: [  257.456608] EAX: f4912302 EBX: f49123c0 
ECX: 0001 EDX: 0001
Oct  6 09:19:58 hostname kernel: [  257.456669] ESI: f6a39c00 EDI: f73c2000 
EBP: 0001 ESP: f6445dec
Oct  6 09:19:58 hostname kernel: [  257.456730]  DS: 007b ES: 007b FS: 00d8 GS: 
00e0 SS: 0068
Oct  6 09:19:58 hostname kernel: [  257.456783] Process Xorg (pid: 1841, 
ti=f6444000 task=f692dac0 task.ti=f6444000)
Oct  6 09:19:58 hostname kernel: [  257.456853] Stack:
Oct  6 09:19:58 hostname kernel: [  257.456875]  f49123c0 f6a39c00 f73c2000 
 f8a99c66 f4995cc0 f6445e30 f6445e28
Oct  6 09:19:58 hostname kernel: [  257.456979] <0> f6445e30 f8a9d588 f6445e28 
f73c2fd8 0500 1000 f73c3030 f4b2b1e8
Oct  6 09:19:58 hostname kernel: [  257.457092] <0> f4ab6c68 f4912428 f4ae52a8 
f4ae5f00 f6a39c14 f6a39c00 f73c2000 f8a991e5
Oct  6 09:19:58 hostname kernel: [  257.457206] Call Trace:
Oct  6 09:19:58 hostname kernel: [  257.457252]  [] ? 
i915_gem_object_unbind+0x96/0x129 [i915]
Oct  6 09:19:58 hostname kernel: [  257.457332]  [] ? 
i915_gem_evict_something+0x311/0x359 [i915]
Oct  6 09:19:58 hostname kernel: [  257.457412]  [] ? 
i915_gem_object_bind_to_gtt+0x1dc/0x261 [i915]
Oct  6 09:19:58 hostname kernel: [  257.457494]  [] ? 
i915_gem_mmap_gtt_ioctl+0x180/0x1ad [i915]
Oct  6 09:19:58 hostname kernel: [  257.457577]  [] ? 
drm_ioctl+0x224/0x2d5 [drm]
Oct  6 09:19:58 hostname kernel: [  257.457646]  [] ? 
i915_gem_mmap_gtt_ioctl+0x0/0x1ad [i915]
Oct  6 09:19:58 hostname kernel: [  257.457712]  [] ? 
restore_i387_fxsave+0x5c/0x6d
Oct  6 09:19:58 hostname kernel: [  257.457781]  [] ? 
drm_ioctl+0x0/0x2d5 [drm]
Oct  6 09:19:58 hostname kernel: [  257.457833]  [] ? 
do_vfs_ioctl+0x49e/0x4e9
Oct  6 09:19:58 hostname kernel: [  257.457883]  [] ? 
restore_i387_xstate+0x19e/0x1d5
Oct  6 09:19:58 hostname kernel: [  257.457939]  [] ? 
fsnotify_access+0x49/0x50
Oct  6 09:19:58 hostname kernel: [  257.457987]  [] ? 
sys_ioctl+0x44/0x64
Oct  6 09:19:58 hostname kernel: [  257.458034]  [] ? 
sysenter_do_call+0x12/0x28
Oct  6 09:19:58 hostname kernel: [  257.458084] Code: 00 00 00 89 d8 ff b1 80 
00 00 00 b9 01 00 00 00 e8 b3 fc ff ff 5b 5b c3 55 57 56 53 89 c3 8b 68 38 8a 
40 71 c1 ed 0c a8 0c 75 04 <0f> 0b eb fe 88 c2 83 e2 03 80 fa 02 75 04 0f 0b eb 
fe 88 c2 83 
Oct  6 09:19:58 hostname kernel: [  257.458295] EIP: [] 
i915_gem_object_put_pages+0x13/0xb2 [i915] SS:ESP 0068:f6445dec

I haven't tested yet whether this problem also occurs in the squeeze kernel. 
Also, this problem is not an "always" problem so far, because after a re

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

[Mark Adams]

Hi Ben, Thanks for your response. See my responses inline.

On Wed, Oct 06, 2010 at 03:35:23AM +0100, Ben Hutchings wrote:
> On Tue, 2010-10-05 at 09:31 +0100, Mark Adams wrote:
> > Package: xen-linux-system-2.6.32-5-xen-amd64
> > Version: 2.6.32-21
> > Severity: important
> > 
> > 
> > Hi, Did you receive this bug report? I hadn't received a bug ID even
> > though receiving the copy of the original report.
> 
> We don't have any other bug report with this description.
> 
> > Likely because the address it was sent from originally was invalid.
> 
> That would explain it.
> 
> > -
> > 
> > Hi All, 
> >   
> > 
> >   
> > Im running Xen 4.0.1-rc6 Debian squeeze with pvops 2.6.32-21 kernel.
> >   
> > Today I noticed (when kerberos to the domain controllers stopped
> >   
> > working..) that the clock was 50 minutes out in dom0 -- This caused the 
> >   
> > HVM windows domain controllers to have the wrong time.  
> >   
> 
> Since you appear to be in the UK, is it possible that the real-time
> clock is set to local time (GMT+1) while Xen expects it to be GMT, or
> vice versa?

The clock is set with tzdata as BST yes, it is also set to this in the
Windows server 2008 domU. We are using localtime=1 to match the clock
in dom0 to domU.

> 
> (This doesn't explain why it's 50 minutes out rather than 1 hour.  But
> ntpd will refuse to correct a large difference and the local clock may
> then drift further.)
> 
> [...]
> > Can anyone confirm whether xen controls the time or the kernel? Also
> >   
> > when I corrected the time in dom0 it was still wrong in HVM domU -- How 
> >   
> > long does it take for this to propogate? (I rebooted the VM's to correct
> >   
> > it immediately).
> >   
> [...]
> 
> For HVM guests, the hypervisor emulates a standard PC real-time clock
> and the guest uses that to initialise the system time, but there is no
> way to force an update after the guest has booted unless the guest has
> specific support for Xen; I assume Citrix does provide such software for
> Windows but I don't know whether it is free software.

The citrix WHQL drivers might have this functionality, I don't use them
though - prefer the GPL PV drivers! (which don't have any clock support
as far as I can tell)

> 
> For PV guests, I assume you can force an update to the guest time using
> the Xen management tools.
> 
> Note, I'm just a general kernel maintainer and don't have any great
> knowledge of Xen.

All good, I have a feeling it might be a kernel issue rather than xen,
but I'm still not sure what actually -controls- the time, is it the
kernel? I think the key is in the log

Oct  2 18:50:33 havhost1 kernel: [623480.977748] Clocksource tsc unstable 
(delta = -2999660303788 ns)
> 
As this is when the clock went from 18:00 to 18:50 and started the chain
of events (restarted the 2008 domU). Any ideas why this log occurred?

> Ben.

Regards,
Mark
> 
> -- 
> Ben Hutchings
> Once a job is fouled up, anything done to improve it makes it worse.






-- 
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/20101006083331.ga27...@campbell-lange.net

Bug#599089: linux-image-2.6.32-5-xen-686: Kernel Panics when using NFS from DomU to Dom0

[Ian Campbell]

On Tue, 2010-10-05 at 22:14 -0400, Jason Kendall wrote:
> Where do you guys commit? I didn't see it on the kernel git tree, and 
> can't find a debian one.

Jeremy is the upstream xen kernel maintainer so he has put it in his
tree at git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
specifically
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=7ed8586dd2ba2340a28a5d3d21f3f531a5bd30f8

I'm just about to pull it into the Debian kernel SVN
svn://svn.debian.org/kernel/dists/trunk/linux-2.6. From there it will go
into unstable/sid whenever 2.6.32-25 is uploaded and then it will
propagate to testing/squeeze some time after that in the usual way.

However once it is in unstable there should be nothing to stop you
installing the package on a squeeze system.

I don't control the upload to sid schedule I'm afraid so I can't really
say when it will happen. Perhaps someone on debian-kernel will chime in.

Ian.

> Would this happen to make it into Squeeze soon? ETA?
> 
> Save me the trouble of a recompile :)
> 
> Cheers,
> Jay
> 
> 
> On 10-10-05 06:39 PM, Jeremy Fitzhardinge wrote:
> >   On 10/05/2010 11:22 AM, Ian Campbell wrote:
> >
> >> On Tue, 2010-10-05 at 09:54 -0700, Jeremy Fitzhardinge wrote:
> >>  
> >>> On 10/05/2010 02:52 AM, Ian Campbell wrote:
> >>>
>  On Tue, 2010-10-05 at 10:47 +0100, Ian Campbell wrote:
>   
> > In addition to the kernel logging of the error I get this from the
> > hypervisor:
> > (XEN) mm.c:2062:d0 Error pfn 16d99: rd=83011fefa000,
> > od=, caf=180, taf=
> > (XEN) mm.c:658:d0 Could not get page ref for pfn 16d99
> > (XEN) mm.c:3621:d0 Could not get page for mach->phys update
> >
>  Adding a bit more logging to the kernel I get:
>  gnttb_copy_grant_page old c22ebcd8 P:0x1ec8e M:0xc499d F:0x4100
>  gnttb_copy_grant_page new c2324ce0 P:0x1fe18 M:0x11cd32 F:0x4000
>  (XEN) mm.c:2062:d0 Error pfn 1cd32: rd=83011fefa000, 
>  od=, caf=180, taf=
>  (XEN) mm.c:658:d0 Could not get page ref for pfn 1cd32
>  (XEN) mm.c:3621:d0 Could not get page for mach->phys update
> 
>  Notice how MFN 0x11cd32 has become 0x1cd32 by the time it gets to the
>  hypervisor!
>   
> >>> Oy, more of these.  It might be better to use PFN_PHYS().
> >>>
> >> I thought there ought to be a helper but couldn't find one, PFN_PHYS
> >> sounds like a good bet, unless we want to alias it as MFN_MACH or
> >> something?
> >>  
> > Doesn't really seem worth it, unless phys_addr_t ends up not being large
> > enough for a machine address.  But I think we rely on that pretty
> > heavily anyway.
> >
> > I've committed it with that change.
> >
> >  J
> >
> 

-- 
Ian Campbell

Friendships last when each friend thinks he has a slight superiority
over the other.
-- Honore DeBalzac




-- 
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/1286356905.23155.11899.ca...@zakaz.uk.xensource.com

Processed: Re: Bug#599121: Acknowledgement (linux-2.6: [m68k] nfeth driver vanished? no network connectivity!)

[Debian Bug Tracking System]

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

> notfound 599121 2.6.29-5
Bug #599121 [src:linux-2.6] linux-2.6: [m68k] nfeth driver vanished? no network 
connectivity!
Ignoring request to alter found versions of bug #599121 to the same values 
previously set
> notfound 599121 2.6.26-13
Bug #599121 [src:linux-2.6] linux-2.6: [m68k] nfeth driver vanished? no network 
connectivity!
Ignoring request to alter found versions of bug #599121 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
599121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599121
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.12863574754958.transcr...@bugs.debian.org

Processed: tagging 599089

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 599089 + pending
Bug #599089 [linux-2.6] linux-image-2.6.32-5-xen-686: Kernel Panics when using 
NFS from DomU to Dom0
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
599089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599089
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.12863575645350.transcr...@bugs.debian.org

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

[Ian Campbell]

On Wed, 2010-10-06 at 09:33 +0100, Mark Adams wrote:
> Hi Ben, Thanks for your response. See my responses inline.
> 
> On Wed, Oct 06, 2010 at 03:35:23AM +0100, Ben Hutchings wrote:
> > On Tue, 2010-10-05 at 09:31 +0100, Mark Adams wrote:
> > > Package: xen-linux-system-2.6.32-5-xen-amd64
> > > Version: 2.6.32-21
> > > Severity: important
> > > 
> > > 
> > > Hi, Did you receive this bug report? I hadn't received a bug ID even
> > > though receiving the copy of the original report.
> > 
> > We don't have any other bug report with this description.
> > 
> > > Likely because the address it was sent from originally was invalid.
> > 
> > That would explain it.
> > 
> > > -
> > > 
> > > Hi All,   
> > > 
> > >   
> > > 
> > > Im running Xen 4.0.1-rc6 Debian squeeze with pvops 2.6.32-21 kernel.  
> > > 
> > > Today I noticed (when kerberos to the domain controllers stopped  
> > > 
> > > working..) that the clock was 50 minutes out in dom0 -- This caused the   
> > > 
> > > HVM windows domain controllers to have the wrong time.
> > > 
> > 
> > Since you appear to be in the UK, is it possible that the real-time
> > clock is set to local time (GMT+1) while Xen expects it to be GMT, or
> > vice versa?
> 
> The clock is set with tzdata as BST yes, it is also set to this in the
> Windows server 2008 domU. We are using localtime=1 to match the clock
> in dom0 to domU.
> 
> > 
> > (This doesn't explain why it's 50 minutes out rather than 1 hour.  But
> > ntpd will refuse to correct a large difference and the local clock may
> > then drift further.)
> > 
> > [...]
> > > Can anyone confirm whether xen controls the time or the kernel? Also  
> > > 
> > > when I corrected the time in dom0 it was still wrong in HVM domU -- How   
> > > 
> > > long does it take for this to propogate? (I rebooted the VM's to correct  
> > > 
> > > it immediately).  
> > > 
> > [...]
> > 
> > For HVM guests, the hypervisor emulates a standard PC real-time clock
> > and the guest uses that to initialise the system time, but there is no
> > way to force an update after the guest has booted unless the guest has
> > specific support for Xen; I assume Citrix does provide such software for
> > Windows but I don't know whether it is free software.
> 
> The citrix WHQL drivers might have this functionality, I don't use them
> though - prefer the GPL PV drivers! (which don't have any clock support
> as far as I can tell)

I think you can run a regular NTP client (assuming one exists for
Windows) in an HVM guest to keep wallclock time in sync.

> > For PV guests, I assume you can force an update to the guest time using
> > the Xen management tools.
> > 
> > Note, I'm just a general kernel maintainer and don't have any great
> > knowledge of Xen.

I should know but time handling (particularly for HVM guests) is
something where I basically know enough to know that there is lots I
don't know ;-)

Mark, you may find you get better answers/support from the xen-users
mailing list, or failing that, xen-devel.

> All good, I have a feeling it might be a kernel issue rather than xen,
> but I'm still not sure what actually -controls- the time, is it the
> kernel? I think the key is in the log
> 
> Oct  2 18:50:33 havhost1 kernel: [623480.977748] Clocksource tsc unstable 
> (delta = -2999660303788 ns)
> > 
> As this is when the clock went from 18:00 to 18:50 and started the chain
> of events (restarted the 2008 domU). Any ideas why this log occurred?

The TSC appeared to go backwards by a fairly significant amount, which
has upset the kernel.

The behaviour of the virtual TSC as seen by an HVM guest is controlled
by a combination of the tsc_mode setting in your domain configuration
and, I think, by the features of your specific hardware (some have
constant rate TSC, others advertise varying levels of synchronisation
between cores etc). It's then up to the guest kernel whether it even
uses TSC as a timesource at all and how it handles instability etc and
how it derives other time sources (such as the wallclock time) from

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

[Mark Adams]

On Wed, Oct 06, 2010 at 11:47:05AM +0100, Ian Campbell wrote:
> On Wed, 2010-10-06 at 09:33 +0100, Mark Adams wrote:
> > Hi Ben, Thanks for your response. See my responses inline.
> > 
> > On Wed, Oct 06, 2010 at 03:35:23AM +0100, Ben Hutchings wrote:
> > > On Tue, 2010-10-05 at 09:31 +0100, Mark Adams wrote:
> > > > Package: xen-linux-system-2.6.32-5-xen-amd64
> > > > Version: 2.6.32-21
> > > > Severity: important
> > > > 
> > > > 
> > > > Hi, Did you receive this bug report? I hadn't received a bug ID even
> > > > though receiving the copy of the original report.
> > > 
> > > We don't have any other bug report with this description.
> > > 
> > > > Likely because the address it was sent from originally was invalid.
> > > 
> > > That would explain it.
> > > 
> > > > -
> > > > 
> > > > Hi All, 
> > > > 
> > > >   
> > > > 
> > > > 
> > > >   
> > > > Im running Xen 4.0.1-rc6 Debian squeeze with pvops 2.6.32-21 kernel.
> > > > 
> > > >   
> > > > Today I noticed (when kerberos to the domain controllers stopped
> > > > 
> > > >   
> > > > working..) that the clock was 50 minutes out in dom0 -- This caused the 
> > > > 
> > > >   
> > > > HVM windows domain controllers to have the wrong time.  
> > > > 
> > > >   
> > > 
> > > Since you appear to be in the UK, is it possible that the real-time
> > > clock is set to local time (GMT+1) while Xen expects it to be GMT, or
> > > vice versa?
> > 
> > The clock is set with tzdata as BST yes, it is also set to this in the
> > Windows server 2008 domU. We are using localtime=1 to match the clock
> > in dom0 to domU.
> > 
> > > 
> > > (This doesn't explain why it's 50 minutes out rather than 1 hour.  But
> > > ntpd will refuse to correct a large difference and the local clock may
> > > then drift further.)
> > > 
> > > [...]
> > > > Can anyone confirm whether xen controls the time or the kernel? Also
> > > > 
> > > >   
> > > > when I corrected the time in dom0 it was still wrong in HVM domU -- How 
> > > > 
> > > >   
> > > > long does it take for this to propogate? (I rebooted the VM's to 
> > > > correct 
> > > >  
> > > > it immediately).
> > > > 
> > > >   
> > > [...]
> > > 
> > > For HVM guests, the hypervisor emulates a standard PC real-time clock
> > > and the guest uses that to initialise the system time, but there is no
> > > way to force an update after the guest has booted unless the guest has
> > > specific support for Xen; I assume Citrix does provide such software for
> > > Windows but I don't know whether it is free software.
> > 
> > The citrix WHQL drivers might have this functionality, I don't use them
> > though - prefer the GPL PV drivers! (which don't have any clock support
> > as far as I can tell)
> 
> I think you can run a regular NTP client (assuming one exists for
> Windows) in an HVM guest to keep wallclock time in sync.
> 
> > > For PV guests, I assume you can force an update to the guest time using
> > > the Xen management tools.
> > > 
> > > Note, I'm just a general kernel maintainer and don't have any great
> > > knowledge of Xen.
> 
> I should know but time handling (particularly for HVM guests) is
> something where I basically know enough to know that there is lots I
> don't know ;-)
> 
> Mark, you may find you get better answers/support from the xen-users
> mailing list, or failing that, xen-devel.
> 
> > All good, I have a feeling it might be a kernel issue rather than xen,
> > but I'm still not sure what actually -controls- the time, is it the
> > kernel? I think the key is in the log
> > 
> > Oct  2 18:50:33 havhost1 kernel: [623480.977748] Clocksource tsc unstable 
> > (delta = -2999660303788 ns)
> > > 
> > As this is when the clock went from 18:00 to 18:50 and started the chain
> > of events (restarted the 2008 domU). Any ideas why this log occurred?
> 
> The TSC appeared to go backwards by a fairly significant amount, which
> has upset the kernel.
> 
> The behaviour of the virtual TSC as seen by an HVM guest is controlled
> by a combination of the tsc_mode setting in your domain configur

Bug#599254: linux-image-2.6.36-rc5-686: icedove causes BUG when trying to open mail with very large attachments on i915

[Ben Hutchings]

On Wed, 2010-10-06 at 09:40 +0200, Willi Mann wrote:
> Package: linux-2.6
> Version: 2.6.36~rc5-1~experimental.1
> Severity: important
> 
> When trying to open a mail with with large images (e.g. 3 images with 
> 4368x2912) in icedove the screen freezes and after a few seconds, a beep
>  occurs (this is probably the kerneloops daemon) and the following messages 
> occur in the kernel log:

Please report this upstream at  under
product 'DRI', component 'DRM/Intel'.   Let us know the bug number or
URL so we can track it.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#599254: linux-image-2.6.36-rc5-686: icedove causes BUG when trying to open mail with very large attachments on i915

[maximilian attems]

On Wed, Oct 06, 2010 at 12:06:57PM +0100, Ben Hutchings wrote:
> On Wed, 2010-10-06 at 09:40 +0200, Willi Mann wrote:
> > Package: linux-2.6
> > Version: 2.6.36~rc5-1~experimental.1
> > Severity: important
> > 
> > When trying to open a mail with with large images (e.g. 3 images with 
> > 4368x2912) in icedove the screen freezes and after a few seconds, a beep
> >  occurs (this is probably the kerneloops daemon) and the following messages 
> > occur in the kernel log:
> 
> Please report this upstream at  under
> product 'DRI', component 'DRM/Intel'.   Let us know the bug number or
> URL so we can track it.

it could very well be fixed in rc6 please test that first, thanks.



-- 
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/2010100658.gf5...@vostochny.stro.at

Bug#599254: linux-image-2.6.36-rc5-686: icedove causes BUG when trying to open mail with very large attachments on i915

[Willi Mann]

Am 2010-10-06 13:11, schrieb maximilian attems:
> it could very well be fixed in rc6 please test that first, thanks.

Hi!

Is the i386 version of rc6 already somewhere available? The offical ones
are currently waiting in NEW.

thanks
WM



-- 
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/4cac5c51.1020...@wm1.at

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

[Bastian Blank]

On Sat, Oct 02, 2010 at 08:46:08PM +, Thorsten Glaser wrote:
> Please see to that -fno-omit-frame-pointer is used during compilation
> of a Debian m68k kernel as long as it is built with gcc-4.3 (I think
> defining CONFIG_FRAME_POINTER should be enough, I have yet to build
> any kernel at all though and have not tested this).

m68k is not a release architecture. Also all newer kernels uses gcc 4.4.

Bastian

-- 
Is truth not truth for all?
-- Natira, "For the World is Hollow and I have Touched
   the Sky", stardate 5476.4.



-- 
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/20101006112835.gb28...@wavehammer.waldi.eu.org

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

[Thorsten Glaser]

Bastian Blank dixit:

>m68k is not a release architecture. Also all newer kernels uses gcc 4.4.

It doesn’t happen in gcc-4.4 but the kernel currently in sid uses gcc-4.3.

bye,
//mirabilos
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.  -- Coywolf Qi Hunt



--
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.1010061625150.7...@herc.mirbsd.org

Bug#595187: linux-2.6: lots of OOPses on resume (NULL pointer dereference in file_ra_state_init)

[Vagrant Cascadian]

On Mon, Sep 27, 2010 at 09:29:28AM -0700, Vagrant Cascadian wrote:
> On Tue, Sep 21, 2010 at 01:37:42PM -0700, Vagrant Cascadian wrote:
> > On Mon, Sep 20, 2010 at 02:04:23AM +0100, Ben Hutchings wrote:
> > > Please add 'memory_corruption_check=1' to the kernel parameters and
> > > report whether that fixes the problem and whether it results in any new
> > > log messages.
> > 
> > added this now, will reboot and see if that fixes it... presuming it just
> > doesn't hide itself for another several weeks.
> 
> ok, didn't have to wait for weeks, apparently.

still getting crashes every week or two, but not sure if they're related to the
initial problem...

so i've been running with memory_corruption_check=1:

cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/mneme-rwt ro quiet 
memory_corruption_check=1


Oct  5 19:14:30 mneme kernel: [ 8525.133061] BUG: unable to handle kernel NULL 
pointer dereference at (null)
Oct  5 19:14:30 mneme kernel: [ 8525.133072] IP: [] strlen+0x8/0x11
Oct  5 19:14:30 mneme kernel: [ 8525.133083] *pde = 
Oct  5 19:14:30 mneme kernel: [ 8525.133088] Oops:  [#1] SMP
Oct  5 19:14:30 mneme kernel: [ 8525.133094] last sysfs file: 
/sys/devices/pci:00/:00:02.1/resource
Oct  5 19:14:30 mneme kernel: [ 8525.133099] Modules linked in: usbhid hid tun 
ip6table_filter ip6_tables iptable_filter ip_tables x_tables sco bridge stp bnep
rfcomm l2cap crc16 bluetooth acpi_cpufreq parport_pc ppdev lp cpufreq_stats 
cpufreq_powersave parport cpufreq_conservative cpufreq_userspace kvm_intel kvm 
uinpu
t fuse dm_snapshot firewire_sbp2 loop snd_hda_codec_idt snd_hda_intel 
snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi 
snd_rawmidi snd_seq
_midi_event i915 snd_seq arc4 drm_kms_helper ecb snd_timer b43 snd_seq_device 
drm snd yenta_socket rsrc_nonstatic i2c_i801 i2c_algo_bit soundcore mac80211 
rng_c
ore snd_page_alloc dell_laptop joydev i2c_core cfg80211 rfkill video battery 
processor button output dcdbas psmouse ac evdev serio_raw ext3 jbd mbcache 
sha256_g
eneric aes_i586 aes_generic cbc dm_crypt dm_mod sd_mod crc_t10dif ata_generic 
ata_piix sdhci_pci sdhci thermal ssb firewire_ohci pcmcia libata mmc_core tg3 
uhci
_hcd firewire_core crc_itu_t pcmcia_core scsi_mod led_class ehci_h
Oct  5 19:14:30 mneme kernel: cd thermal_sys libphy usbcore nls_base [last 
unloaded: scsi_wait_scan]
Oct  5 19:14:30 mneme kernel: [ 8525.133242]
Oct  5 19:14:30 mneme kernel: [ 8525.133248] Pid: 10491, comm: Xorg Not tainted 
(2.6.32-5-686 #1) Latitude D420
Oct  5 19:14:30 mneme kernel: [ 8525.133254] EIP: 0060:[] EFLAGS: 
00213246 CPU: 0
Oct  5 19:14:30 mneme kernel: [ 8525.133259] EIP is at strlen+0x8/0x11
Oct  5 19:14:30 mneme kernel: [ 8525.133263] EAX:  EBX: 0fd4 ECX: 
 EDX: 0005
Oct  5 19:14:30 mneme kernel: [ 8525.133268] ESI:  EDI:  EBP: 
f6f533f0 ESP: d5871f4c
Oct  5 19:14:30 mneme kernel: [ 8525.133272]  DS: 007b ES: 007b FS: 00d8 GS: 
00e0 SS: 0068
Oct  5 19:14:30 mneme kernel: [ 8525.133278] Process Xorg (pid: 10491, 
ti=d587 task=f335d540 task.ti=d587)
Oct  5 19:14:30 mneme kernel: [ 8525.133282] Stack:
Oct  5 19:14:30 mneme kernel: [ 8525.133285]  f0790e00 c10f2aee c10bd768 
d5871f90  c128167c f0790e00 e0537d88
Oct  5 19:14:30 mneme kernel: [ 8525.133295] <0> e0537e00 c10bd9fb d5871f90 
c10bd768 fff7 f0790e00  8000
Oct  5 19:14:30 mneme kernel: [ 8525.133306] <0> c10bda8b 0a0882a8 0a088288 
7d28 ffea 000c 0a087fd0 b76afff4
Oct  5 19:14:30 mneme kernel: [ 8525.133318] Call Trace:
Oct  5 19:14:30 mneme kernel: [ 8525.133328]  [] ? 
sysfs_readdir+0xe0/0x13a
Oct  5 19:14:30 mneme kernel: [ 8525.16]  [] ? filldir64+0x0/0xc5
Oct  5 19:14:30 mneme kernel: [ 8525.133342]  [] ? 
vfs_readdir+0x62/0x8c
Oct  5 19:14:30 mneme kernel: [ 8525.133349]  [] ? filldir64+0x0/0xc5
Oct  5 19:14:30 mneme kernel: [ 8525.133355]  [] ? 
sys_getdents64+0x66/0xa5
Oct  5 19:14:30 mneme kernel: [ 8525.133363]  [] ? 
sysenter_do_call+0x12/0x28
Oct  5 19:14:30 mneme kernel: [ 8525.133367] Code: eb 04 19 c0 0c 01 5e 5f c3 
56 89 c6 89 d0 88 c4 ac 38 e0 74 09 84 c0 75 f7 be 01 00 00 00 89 f0 48 5e c3 
57 8
3 c9 ff 89 c7 31 c0  ae f7 d1 49 89 c8 5f c3 57 31 ff 85 c9 74 0e 89 c7 89 
d0 f2
Oct  5 19:14:30 mneme kernel: [ 8525.133427] EIP: [] strlen+0x8/0x11 
SS:ESP 0068:d5871f4c
Oct  5 19:14:30 mneme kernel: [ 8525.133434] CR2: 
Oct  5 19:14:30 mneme kernel: [ 8525.133439] ---[ end trace e4f8adeee260d138 
]---

and again today:

Oct  6 08:20:00 mneme kernel: [ 5643.886857] BUG: unable to handle kernel NULL 
pointer dereference at 0010
Oct  6 08:20:00 mneme kernel: [ 5643.887055] IP: [] 
file_ra_state_init+0x3/0x18
Oct  6 08:20:00 mneme kernel: [ 5643.890573] *pde =  
Oct  6 08:20:00 mneme kernel: [ 5643.890573] Oops:  [#1] SMP 
Oct  6 08:20:00state_init+0x3/0x18
Oct  6 08:20:00 mneme kernel: [ 5643.890573] EAX: ef4e1fc8 EBX:  ECX: 
f3710800 EDX: 
Oct

Bug#598518: linux-image-2.6-686: ata_piix module loaded before ahci module deactivate hotplug support (regression from lenny)

[Thomas DEBESSE]

2010/10/4 maximilian attems :
> we do shipp modules.order in initramfs.

> hmm thomas what are your MODULES settings, please post output of
>  egrep MODULES -r /etc/initramfs-tools/

> you can check any initramfs if it has the relevant modules with
> lsinitramfs /boot/initrd.img-2.6.35-trunk-amd64 | grep ahci

2010/10/5 maximilian attems :
> please also report which initramfs-tools version you are using,
> since lenny there had been ton of fixes:
> dpkg -l initramfs-tools
>
> you should be running 0.98.4

Somes checks, playing with system configuration,

On Lenny:

# egrep MODULES -r /etc/initramfs-tools/
/etc/initramfs-tools/initramfs.conf:# MODULES: [ most | netboot | dep | list ]
/etc/initramfs-tools/initramfs.conf:MODULES=most

# lspci -vv -s 00:1f.2 | grep Kernel
Kernel driver in use: ahci
Kernel modules: ahci, ata_piix

# dpkg -l initramfs-tools | grep ^ii
ii  initramfs-tools   0.92o  tools
for generating an initramfs

# find / -iname "modules.order"

On Squeeze :

# egrep MODULES -r /etc/initramfs-tools/
/etc/initramfs-tools/initramfs.conf:# MODULES: [ most | netboot | dep | list ]
/etc/initramfs-tools/initramfs.conf:MODULES=most

# lspci -vv -s 00:1f.2 | grep Kernel
Kernel driver in use: ata_piix

# dpkg -l initramfs-tools | grep ^ii
ii  initramfs-tools   0.98.4
tools for generating an initramfs

# find / -iname "modules.order"

Nothing seems to be interesting here.

Playing with initrd,

On Lenny :

# lsinitramfs initrd.img-2.6.26-2-686 | grep 'ahci\|ata_piix'
lib/modules/2.6.26-2-686/kernel/drivers/ata/ahci.ko
lib/modules/2.6.26-2-686/kernel/drivers/ata/ata_piix.ko

# gunzip < initrd.img-2.6.26-2-686 | cpio -i --make-directories
# find . -iname '*module*'
./conf/modules
./lib/modules

On Squeeze (unmodified):

# lsinitramfs initrd.img-2.6.32-5-686 | grep 'ahci\|ata_piix'
lib/modules/2.6.32-5-686/kernel/drivers/ata/ahci.ko
lib/modules/2.6.32-5-686/kernel/drivers/ata/ata_piix.ko

# gunzip < initrd.img-2.6.32-5-686 | cpio -i --make-directories
# find . -iname '*module*'
./conf/modules
./lib/modules
./lib/modules/2.6.32-5-686/modules.symbols
./lib/modules/2.6.32-5-686/modules.dep
./lib/modules/2.6.32-5-686/modules.alias.bin
./lib/modules/2.6.32-5-686/modules.symbols.bin
./lib/modules/2.6.32-5-686/modules.alias
./lib/modules/2.6.32-5-686/modules.devname
./lib/modules/2.6.32-5-686/modules.dep.bin
./lib/modules/2.6.32-5-686/modules.softdep

On Squeeze (modified, with blacklist ata_piix):

# lsinitramfs initrd.img-2.6.32-5-686 | grep 'ahci\|ata_piix'
lib/modules/2.6.32-5-686/kernel/drivers/ata/ahci.ko
lib/modules/2.6.32-5-686/kernel/drivers/ata/ata_piix.ko

# gunzip < initrd.img-2.6.32-5-686 | cpio -i --make-directories
# find . -iname '*module*'
./conf/modules
./lib/modules
./lib/modules/2.6.32-5-686/modules.symbols
./lib/modules/2.6.32-5-686/modules.dep
./lib/modules/2.6.32-5-686/modules.alias.bin
./lib/modules/2.6.32-5-686/modules.symbols.bin
./lib/modules/2.6.32-5-686/modules.alias
./lib/modules/2.6.32-5-686/modules.devname
./lib/modules/2.6.32-5-686/modules.dep.bin
./lib/modules/2.6.32-5-686/modules.softdep

Comparing file 'conf/module' which is common to Lenny and Squeeze

# diff lenny/conf/modules squeeze-unmodified/conf/modules
# diff squeeze-unmodified/conf/modules squeeze-blacklist/conf/modules

Comparing somes Squeeze modified and unmodified initrds contents :

# for i in modules.symbols \
   modules.dep \
   modules.alias.bin \
   modules.symbols.bin \
   modules.alias \
   modules.devname \
   modules.dep.bin \
   modules.softdep
do diff squeeze-unmodified/lib/modules/2.6.32-5-686/$i \
squeeze-blacklist/lib/modules/2.6.32-5-686/$i
done

# diff squeeze-unmodified/etc/modprobe.d/blacklist.conf
squeeze-blacklist/etc/modprobe.d/blacklist.conf
24a25
> blacklist ata_piix

# diff squeeze-blacklist/etc/modprobe.d/aliases.conf
squeeze-unmodified/etc/modprobe.d/aliases.conf
# diff lenny/etc/modprobe.d/aliases
squeeze-unmodified/etc/modprobe.d/aliases.conf
4,5c4,5
< # Please file a bug against module-init-tools if a package needs a entry
< # in this file.
---
> # No new aliases should be added to this file, please file a bug against
> # the kernel for any aliases which are still not built-in.
14c14
< alias net-pf-7  bridge
---
> # 7 BRIDGE
30c30
< alias net-pf-25 wanrouter
---
> # 25 WANROUTER
57,59d56
< alias block-major-8-*  sd_mod
< alias block-major-9-*  md
< alias block-major-11-* sr_mod
78d74
< alias char-major-9-* st
141,146c137,142
< alias bt-proto-0 l2cap
< alias bt-proto-2 sco
< alias bt-proto-3 rfcomm
< alias bt-proto-4 bnep
< alias bt-proto-5 cmtp
< alias bt-proto-6 hidp
---
> #alias bt-proto-0 l2cap
> #alias bt-proto-2 sco
> #alias bt-proto-3 rfcomm
> #alias bt-proto-4 bnep
> #alias bt-proto-5 cmtp
> #alias bt-proto-6 hidp
165a162,167
> # work around other kernel issues 
> # The EHCI driver should be loaded b

Bug#599339: linux-headers-2.6.32-5-amd64: cant load kvm_intel module

[Tomas Pelka]

Package: linux-headers-2.6.32-5-amd64
Version: 2.6.32-23
Severity: important



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-headers-2.6.32-5-amd64 depends on:
ii  gcc-4.3   4.3.5-4The GNU C compiler
ii  linux-headers-2.6.32-5-common 2.6.32-23  Common header files for Linux 2.6.
ii  linux-kbuild-2.6.32   2.6.32-1   Kbuild infrastructure for Linux 2.
ii  kvm   1:0.12.5+dfsg-3   
  dummy transitional package from kvm to qemu-kvm
ii  qemu-kvm  0.12.5+dfsg-3 
  Full virtualization on x86 hardware

linux-headers-2.6.32-5-amd64 recommends no packages.

linux-headers-2.6.32-5-amd64 suggests no packages.

-- no debconf information

Not able to load kvm_intel module. 
$ modprobe kvm_intel
FATAL: Error inserting kvm_intel 
(/lib/modules/2.6.32-5-amd64/kernel/arch/x86/kvm/kvm-intel.ko): Operation not 
supported

Dmesg says 
kvm: disabled by bios

Even if vm technologies are enabled in bios. It is ThinkStation E20, lspci 
output attachet. 



-- 
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/20101006181335.8951.24231.report...@localhost.localdomain

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

[Ben Hutchings]

On Wed, Oct 06, 2010 at 04:25:43PM +, Thorsten Glaser wrote:
> Bastian Blank dixit:
> 
> >m68k is not a release architecture. Also all newer kernels uses gcc 4.4.
> 
> It doesn’t happen in gcc-4.4 but the kernel currently in sid uses gcc-4.3.
 
But we aren't going to release with m68k, so why not concentrate on
trunk/experimental?

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus



-- 
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/20101006182022.gt13...@decadent.org.uk

Bug#598518: linux-image-2.6-686: ata_piix module loaded before ahci module deactivate hotplug support (regression from lenny)

[Ben Hutchings]

On Wed, Oct 06, 2010 at 07:04:48PM +0200, Thomas DEBESSE wrote:
[...]
> Nothing seems to be interesting here...
> 
> Where can I find modules.order ?
> Or where write it and how ?
 
modules.order is generated during the kernel build process and will be
copied into the initramfs by update-initramfs if present.

However, we currently delete modules.* when creating the image packages,
because we assume all those files are generated by depmod.  Oops.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus



-- 
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/20101006183321.gu13...@decadent.org.uk

Bug#599339: marked as done (linux-headers-2.6.32-5-amd64: cant load kvm_intel module)

[Debian Bug Tracking System]

Your message dated Wed, 6 Oct 2010 19:35:26 +0100
with message-id <20101006183526.gv13...@decadent.org.uk>
and subject line Re: Bug#599339: linux-headers-2.6.32-5-amd64: cant load 
kvm_intel module
has caused the Debian Bug report #599339,
regarding linux-headers-2.6.32-5-amd64: cant load kvm_intel module
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.)


-- 
599339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-2.6.32-5-amd64
Version: 2.6.32-23
Severity: important



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-headers-2.6.32-5-amd64 depends on:
ii  gcc-4.3   4.3.5-4The GNU C compiler
ii  linux-headers-2.6.32-5-common 2.6.32-23  Common header files for Linux 2.6.
ii  linux-kbuild-2.6.32   2.6.32-1   Kbuild infrastructure for Linux 2.
ii  kvm   1:0.12.5+dfsg-3   
  dummy transitional package from kvm to qemu-kvm
ii  qemu-kvm  0.12.5+dfsg-3 
  Full virtualization on x86 hardware

linux-headers-2.6.32-5-amd64 recommends no packages.

linux-headers-2.6.32-5-amd64 suggests no packages.

-- no debconf information

Not able to load kvm_intel module. 
$ modprobe kvm_intel
FATAL: Error inserting kvm_intel 
(/lib/modules/2.6.32-5-amd64/kernel/arch/x86/kvm/kvm-intel.ko): Operation not 
supported

Dmesg says 
kvm: disabled by bios

Even if vm technologies are enabled in bios. It is ThinkStation E20, lspci 
output attachet. 


--- End Message ---
--- Begin Message ---
On Wed, Oct 06, 2010 at 08:13:35PM +0200, Tomas Pelka wrote:
[...]
> Not able to load kvm_intel module. 
> $ modprobe kvm_intel
> FATAL: Error inserting kvm_intel 
> (/lib/modules/2.6.32-5-amd64/kernel/arch/x86/kvm/kvm-intel.ko): Operation not 
> supported
> 
> Dmesg says 
> kvm: disabled by bios
> 
> Even if vm technologies are enabled in bios. It is ThinkStation E20, lspci 
> output attachet. 
 
You probably need to turn the power off and on again.  (This is not a joke.)
In any case, this is a firmware problem and not a kernel bug.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus

--- End Message ---

Bug#598893: linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)

[Thorsten Glaser]

Ben Hutchings dixit:

>On Wed, Oct 06, 2010 at 04:25:43PM +, Thorsten Glaser wrote:
>> Bastian Blank dixit:
>> 
>> >m68k is not a release architecture. Also all newer kernels uses gcc 4.4.
>> 
>> It doesnb 
>But we aren't going to release with m68k, so why not concentrate on
>trunk/experimental?

Makes sense, although I was trying to get something from unstable to
build, so that I could upload it to unstable (instead of unreleased)
on debian-ports.org (which has strict rules in that regard, and is
tightly coupled to Debian proper).

Except for the gcc-4.3 workaround, the issues I found both apply to
the experimental package too. Stephen Marenka, though, is working on
it (thanks).

bye,
//mirabilos
-- 
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.  -- Coywolf Qi Hunt



-- 
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.1010061837080.11...@herc.mirbsd.org

Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

[Julien Cristau]

Package: linux-2.6
Version: 2.6.32-23
Severity: normal

iwlagn decided 2 weeks of uptime was enough and it wanted me to reboot,
because it was unhappy after resume.

Bit of kern.log:

Oct  6 21:05:02 radis kernel: [378665.326381] NetworkManager: page allocation 
failure. order:4, mode:0x40d0
Oct  6 21:05:02 radis kernel: [378665.326393] Pid: 2, comm: NetworkManager 
Not tainted 2.6.32-5-amd64 #1
Oct  6 21:05:02 radis kernel: [378665.326398] Call Trace:
Oct  6 21:05:02 radis kernel: [378665.326417]  [] ? 
__alloc_pages_nodemask+0x55b/0x5cf
Oct  6 21:05:02 radis kernel: [378665.326427]  [] ? 
__get_free_pages+0x9/0x46
Oct  6 21:05:02 radis kernel: [378665.326461]  [] ? 
iwl_tx_queue_init+0xf1/0x2e6 [iwlcore]
Oct  6 21:05:02 radis kernel: [378665.326477]  [] ? 
_iwl_grab_nic_access+0x39/0xbe [iwlcore]
Oct  6 21:05:02 radis kernel: [378665.326493]  [] ? 
iwl_txq_ctx_reset+0x177/0x1fc [iwlcore]
Oct  6 21:05:02 radis kernel: [378665.326510]  [] ? 
iwl_hw_nic_init+0x123/0x142 [iwlcore]
Oct  6 21:05:02 radis kernel: [378665.326524]  [] ? 
__iwl_up+0x179/0x321 [iwlagn]
Oct  6 21:05:02 radis kernel: [378665.326534]  [] ? 
_cond_resched+0x24/0x2f
Oct  6 21:05:02 radis kernel: [378665.326547]  [] ? 
iwl_mac_start+0x684/0x7f6 [iwlagn]
Oct  6 21:05:02 radis kernel: [378665.326558]  [] ? 
pollwake+0x53/0x59
Oct  6 21:05:02 radis kernel: [378665.326569]  [] ? 
default_wake_function+0x0/0x9
Oct  6 21:05:02 radis kernel: [378665.326578]  [] ? 
__wake_up+0x30/0x44
Oct  6 21:05:02 radis kernel: [378665.326587]  [] ? 
netlink_broadcast+0x266/0x29d
Oct  6 21:05:02 radis kernel: [378665.326611]  [] ? 
ieee80211_open+0x27b/0x653 [mac80211]
Oct  6 21:05:02 radis kernel: [378665.326629]  [] ? 
cfg80211_netdev_notifier_call+0x391/0x3a7 [cfg80211]
Oct  6 21:05:02 radis kernel: [378665.326642]  [] ? 
dev_open+0xa4/0xe6
Oct  6 21:05:02 radis kernel: [378665.326651]  [] ? 
dev_change_flags+0xaf/0x16d
Oct  6 21:05:02 radis kernel: [378665.326661]  [] ? 
do_setlink+0x284/0x351
Oct  6 21:05:02 radis kernel: [378665.326670]  [] ? 
rtnl_setlink+0x12f/0x144
Oct  6 21:05:02 radis kernel: [378665.326680]  [] ? 
rtnetlink_rcv_msg+0x64/0x1f5
Oct  6 21:05:02 radis kernel: [378665.326688]  [] ? 
rtnetlink_rcv_msg+0x0/0x1f5
Oct  6 21:05:02 radis kernel: [378665.326696]  [] ? 
netlink_rcv_skb+0x34/0x7c
Oct  6 21:05:02 radis kernel: [378665.326704]  [] ? 
rtnetlink_rcv+0x1f/0x25
Oct  6 21:05:02 radis kernel: [378665.326711]  [] ? 
netlink_unicast+0xe2/0x148
Oct  6 21:05:02 radis kernel: [378665.326719]  [] ? 
__alloc_skb+0x69/0x15a
Oct  6 21:05:02 radis kernel: [378665.326727]  [] ? 
netlink_sendmsg+0x242/0x255
Oct  6 21:05:02 radis kernel: [378665.326738]  [] ? 
sock_sendmsg+0xa3/0xbb
Oct  6 21:05:02 radis kernel: [378665.326746]  [] ? 
sock_recvmsg+0xa6/0xbe
Oct  6 21:05:02 radis kernel: [378665.326755]  [] ? 
autoremove_wake_function+0x0/0x2e
Oct  6 21:05:02 radis kernel: [378665.326763]  [] ? 
autoremove_wake_function+0x0/0x2e
Oct  6 21:05:02 radis kernel: [378665.326772]  [] ? 
verify_iovec+0x46/0x82
Oct  6 21:05:02 radis kernel: [378665.326780]  [] ? 
sys_sendmsg+0x22a/0x2b5
Oct  6 21:05:02 radis kernel: [378665.326789]  [] ? 
lock_sock_nested+0xa0/0xab
Oct  6 21:05:02 radis kernel: [378665.326797]  [] ? 
set_next_entity+0x34/0x56
Oct  6 21:05:02 radis kernel: [378665.326807]  [] ? 
system_call_fastpath+0x16/0x1b
Oct  6 21:05:02 radis kernel: [378665.326814] Mem-Info:
Oct  6 21:05:02 radis kernel: [378665.326818] Node 0 DMA per-cpu:
Oct  6 21:05:02 radis kernel: [378665.326825] CPU0: hi:0, btch:   1 
usd:   0
Oct  6 21:05:02 radis kernel: [378665.326831] CPU1: hi:0, btch:   1 
usd:   0
Oct  6 21:05:02 radis kernel: [378665.326835] Node 0 DMA32 per-cpu:
Oct  6 21:05:02 radis kernel: [378665.326841] CPU0: hi:  186, btch:  31 
usd:   0
Oct  6 21:05:02 radis kernel: [378665.326847] CPU1: hi:  186, btch:  31 
usd:   0
Oct  6 21:05:02 radis kernel: [378665.326860] active_anon:160995 
inactive_anon:81502 isolated_anon:1
Oct  6 21:05:02 radis kernel: [378665.326863]  active_file:175919 
inactive_file:132273 isolated_file:0
Oct  6 21:05:02 radis kernel: [378665.326866]  unevictable:26 dirty:167 
writeback:0 unstable:0
Oct  6 21:05:02 radis kernel: [378665.326869]  free:90365 
slab_reclaimable:83403 slab_unreclaimable:19585
Oct  6 21:05:02 radis kernel: [378665.326872]  mapped:14852 shmem:8390 
pagetables:6025 bounce:0
Oct  6 21:05:02 radis kernel: [378665.326878] Node 0 DMA free:11908kB min:32kB 
low:40kB high:48kB active_anon:0kB inactive_anon:0kB active_file:424kB 
inactive_file:28kB unevictable:0kB isolated(anon):0kB isolated(file):0kB 
present:15332kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB 
slab_reclaimable:3172kB slab_unreclaimable:48kB kernel_stack:8kB pagetables:0kB 
unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
Oct  6 21:05:02 radis kernel: [378665.326907] lowmem_reserve[]: 0 2967 2967 2967
Oct  6 21:05:02 radis kernel: [378665.326916] Node 0 DMA32 free:349552kB 
min:

Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds

[brian m. carlson]

Package: linux-2.6
Version: 2.6.36~rc6-1~experimental.1
Severity: normal

When browsing the web, I experienced a lockup of Xorg.  It did not
respond further (including to Ctrl-Alt-F1), but I was able to SSH in
from another machine on the network.  Killing Xorg was ineffective: the
screen did not change.  I rebooted the machine and found the following
in the kernel log:

Oct  6 19:26:19 lakeview kernel: [71400.520086] INFO: task Xorg:4165 blocked 
for more than 120 seconds.
Oct  6 19:26:19 lakeview kernel: [71400.520092] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct  6 19:26:19 lakeview kernel: [71400.520097] Xorg  D 
880037afe028 0  4165   1819 0x0044
Oct  6 19:26:19 lakeview kernel: [71400.520106]  8800988f4420 
0082 88009dd01fd8 8800bcdd4af0
Oct  6 19:26:19 lakeview kernel: [71400.520115]  00014940 
00014940 88009dd01fd8 00014940
Oct  6 19:26:19 lakeview kernel: [71400.520123]  00014940 
8800988f46f8 8800988f4700 8800988f4420
Oct  6 19:26:19 lakeview kernel: [71400.520131] Call Trace:
Oct  6 19:26:19 lakeview kernel: [71400.520144]  [] ? 
__mutex_lock_common+0x127/0x193
Oct  6 19:26:19 lakeview kernel: [71400.520151]  [] ? 
mutex_lock+0x1a/0x33
Oct  6 19:26:19 lakeview kernel: [71400.520189]  [] ? 
i915_gem_fault+0x4b/0x17d [i915]
Oct  6 19:26:19 lakeview kernel: [71400.520197]  [] ? 
__do_fault+0x52/0x3f3
Oct  6 19:26:19 lakeview kernel: [71400.520206]  [] ? 
default_wake_function+0x0/0xf
Oct  6 19:26:19 lakeview kernel: [71400.520213]  [] ? 
handle_mm_fault+0x427/0x9f4
Oct  6 19:26:19 lakeview kernel: [71400.520220]  [] ? 
__wake_up_sync_key+0x3f/0x57
Oct  6 19:26:19 lakeview kernel: [71400.520227]  [] ? 
sk_wake_async+0x19/0x3c
Oct  6 19:26:19 lakeview kernel: [71400.520234]  [] ? 
pollwake+0x0/0x4e
Oct  6 19:26:19 lakeview kernel: [71400.520240]  [] ? 
unix_destruct_scm+0x6d/0x74
Oct  6 19:26:19 lakeview kernel: [71400.520248]  [] ? 
do_page_fault+0x2b9/0x2ce
Oct  6 19:26:19 lakeview kernel: [71400.520255]  [] ? 
page_fault+0x25/0x30
Oct  6 19:26:19 lakeview kernel: [71400.520264]  [] ? 
__copy_user_nocache+0x55/0xb8
Oct  6 19:26:19 lakeview kernel: [71400.520283]  [] ? 
i915_gem_pwrite_ioctl+0x1d1/0x5d7 [i915]
Oct  6 19:26:19 lakeview kernel: [71400.520291]  [] ? 
__sock_recvmsg_nosec+0x29/0x69
Oct  6 19:26:19 lakeview kernel: [71400.520298]  [] ? 
sock_aio_read+0xb6/0xc5
Oct  6 19:26:19 lakeview kernel: [71400.520317]  [] ? 
drm_ioctl+0x24e/0x322 [drm]
Oct  6 19:26:19 lakeview kernel: [71400.520335]  [] ? 
i915_gem_pwrite_ioctl+0x0/0x5d7 [i915]
Oct  6 19:26:19 lakeview kernel: [71400.520342]  [] ? 
do_vfs_ioctl+0x4a2/0x4ef
Oct  6 19:26:19 lakeview kernel: [71400.520348]  [] ? 
sys_ioctl+0x4b/0x6f
Oct  6 19:26:19 lakeview kernel: [71400.520356]  [] ? 
sys_read+0x5f/0x6b
Oct  6 19:26:19 lakeview kernel: [71400.520363]  [] ? 
system_call_fastpath+0x16/0x1b
Oct  6 19:26:19 lakeview kernel: [71400.520380] INFO: task compiz:4322 blocked 
for more than 120 seconds.
Oct  6 19:26:19 lakeview kernel: [71400.520384] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct  6 19:26:19 lakeview kernel: [71400.520389] compizD 
880037afe028 0  4322   4193 0x
Oct  6 19:26:19 lakeview kernel: [71400.520396]  8800bb984420 
0082 dead00200200 8800bd90b680
Oct  6 19:26:19 lakeview kernel: [71400.520404]  00014940 
00014940 88009de37fd8 00014940
Oct  6 19:26:19 lakeview kernel: [71400.520411]  00014940 
8800bb9846f8 8800bb984700 8800bb984420
Oct  6 19:26:19 lakeview kernel: [71400.520419] Call Trace:
Oct  6 19:26:19 lakeview kernel: [71400.520426]  [] ? 
__mutex_lock_common+0x127/0x193
Oct  6 19:26:19 lakeview kernel: [71400.520445]  [] ? 
i915_gem_object_set_to_gtt_domain+0x8d/0x9c [i915]
Oct  6 19:26:19 lakeview kernel: [71400.520452]  [] ? 
mutex_lock+0x1a/0x33
Oct  6 19:26:19 lakeview kernel: [71400.520470]  [] ? 
i915_gem_busy_ioctl+0x4f/0xbf [i915]
Oct  6 19:26:19 lakeview kernel: [71400.520487]  [] ? 
drm_ioctl+0x24e/0x322 [drm]
Oct  6 19:26:19 lakeview kernel: [71400.520505]  [] ? 
i915_gem_busy_ioctl+0x0/0xbf [i915]
Oct  6 19:26:19 lakeview kernel: [71400.520512]  [] ? 
do_vfs_ioctl+0x4a2/0x4ef
Oct  6 19:26:19 lakeview kernel: [71400.520519]  [] ? 
ktime_get_ts+0x66/0xab
Oct  6 19:26:19 lakeview kernel: [71400.520525]  [] ? 
sys_ioctl+0x4b/0x6f
Oct  6 19:26:19 lakeview kernel: [71400.520531]  [] ? 
sys_poll+0x45/0xaf
Oct  6 19:26:19 lakeview kernel: [71400.520537]  [] ? 
system_call_fastpath+0x16/0x1b
Oct  6 19:26:19 lakeview kernel: [71400.520558] INFO: task kworker/u:1:24777 
blocked for more than 120 seconds.
Oct  6 19:26:19 lakeview kernel: [71400.520562] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct  6 19:26:19 lakeview kernel: [71400.520567] kworker/u:1   D 
880037afe028 0 24777  2 0x
Oct  6 19:26:19 lakeview kerne

Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

[Ben Hutchings]

On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote:
> Package: linux-2.6
> Version: 2.6.32-23
> Severity: normal
> 
> iwlagn decided 2 weeks of uptime was enough and it wanted me to reboot,
> because it was unhappy after resume.

You also told me that this machine had no swap enabled, which is an
unusual configuration and restricts the ability of the VM to defragment
memory.  I would recommend adding a small swap file/partition.  However:

> Bit of kern.log:
> 
> Oct  6 21:05:02 radis kernel: [378665.326381] NetworkManager: page allocation 
> failure. order:4, mode:0x40d0
> Oct  6 21:05:02 radis kernel: [378665.326393] Pid: 2, comm: 
> NetworkManager Not tainted 2.6.32-5-amd64 #1
[...]
> Oct  6 21:05:02 radis kernel: [378665.363630] iwlagn :0c:00.0: kmalloc 
> for auxiliary BD structures failed
[...]

This particular allocation is for an array which is not used for DMA and
therefore could be stored in non-contiguous pages allocated with
vmalloc().  But there may be some good reason not to do this.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds

[Ben Hutchings]

On Wed, 2010-10-06 at 19:59 +, brian m. carlson wrote:
> Package: linux-2.6
> Version: 2.6.36~rc6-1~experimental.1
> Severity: normal
> 
> When browsing the web, I experienced a lockup of Xorg.  It did not
> respond further (including to Ctrl-Alt-F1), but I was able to SSH in
> from another machine on the network.  Killing Xorg was ineffective: the
> screen did not change.  I rebooted the machine and found the following
> in the kernel log:
[...]

Please report this upstream at  under
product 'DRI', component 'DRM/Intel'.  Let us know the bug number or URL
so we can track it.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Processed: severity of 599345 is minor

[Debian Bug Tracking System]

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

> severity 599345 minor
Bug #599345 [linux-2.6] linux-image-2.6.32-5-amd64: iwlagn allocation failure
Severity set to 'minor' from 'normal'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
599345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599345
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.128640207311542.transcr...@bugs.debian.org

CONFIG_SCSI_PROC_FS

[Sam Vilain]

I know this option is labelled as "legacy", but it is still required
for, eg, scsitools' rescan-scsi-bus.sh script - as far as I know there
is no other way to force Linux to notice that a device has been plugged
or a RAID controller configured to make a device accessible.  Can it be
enabled in future Debian kernels?

I'm unfortunately getting to the point where I need to build custom
kernels; however the old systems I've built are based on kernel-package
which seems to be deprecated.  Is there a simple piece of documentation
I can be pointed at for the best way to build customised kernels based
on Debian's ones?

Cheers,
Sam


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

Bug#599368: NMI watchdog failed to create perf event on cpu0: ffffffa1

[Michael Biebl]

Package: linux-2.6
Version: 2.6.36~rc6-1~experimental.1
Severity: minor
File: /boot/vmlinuz-2.6.36-rc6-686

Hi,

since the upgrade from rc5 to rc6, I get the following error message on
the console during boot:
NMI watchdog failed to create perf event on cpu0: ffa1

With a bit more context:
[0.008303] Performance Events:
[0.008306] no APIC, boot with the "lapic" boot parameter to
force-enable it.
[0.008309] no hardware sampling interrupt available.
[0.008311] p6 PMU driver.
[0.008319] ... version:0
[0.008321] ... bit width:  32
[0.008324] ... generic registers:  2
[0.008326] ... value mask: 
[0.008329] ... max period: 7fff
[0.008331] ... fixed-purpose events:   0
[0.008334] ... event mask: 0003
[0.008815] SMP alternatives: switching to UP code
[0.013737] Freeing SMP alternatives: 16k freed
[0.013743] ACPI: Core revision 20100702
[0.021860] ACPI: setting ELCR to 0200 (from 0c20)
[0.024070] weird, boot CPU (#0) not listed by the BIOS.
[0.024073] SMP motherboard not detected.
[0.024076] Local APIC not detected. Using dummy APIC emulation.
[0.024078] SMP disabled
[0.024189] NMI watchdog failed to create perf event on cpu0:
ffa1
[0.028266] Brought up 1 CPUs
[0.028270] Total of 1 processors activated (3189.83 BogoMIPS).



-- Package-specific info:
** Version:
Linux version 2.6.36-rc6-686 (Debian 2.6.36~rc6-1~experimental.1) 
(b...@decadent.org.uk) (gcc version 4.4.5 20100902 (prerelease) (Debian 
4.4.4-13) ) #1 SMP Mon Oct 4 10:25:13 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.36-rc6-686 
root=UUID=9a6d2bd2-58d1-4a75-baff-166b8637e3cc ro quiet

** Not tainted

** Kernel log:
[4.301432] init[1]: systemd 10 running in system mode. (+PAM +LIBWRAP 
-AUDIT +SELINUX +SYSVINIT; debian)
[4.557097] init[1]: Set hostname to .
[5.749668] init[1]: hostname.service lacks ExecStart setting. Refusing.
[6.010413] init[1]: x11-common.service lacks ExecStart setting. Refusing.
[   17.410690] udev: starting version 161
[   17.773447] input: PC Speaker as /devices/platform/pcspkr/input/input5
[   17.789846] ACPI: AC Adapter [C134] (on-line)
[   17.841354] i801_smbus :00:1f.3: PCI INT B -> Link[C0C3] -> GSI 10 
(level, low) -> IRQ 10
[   17.891393] intel_rng: FWH not detected
[   17.939770] ACPI: acpi_idle registered with cpuidle
[   17.939929] Marking TSC unstable due to TSC halts in idle
[   17.959641] Switching to clocksource acpi_pm
[   18.045347] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   18.118568] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   18.464425] ACPI: Battery Slot [C11F] (battery present)
[   18.512881] parport_pc 00:05: reported by Plug and Play ACPI
[   18.512934] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[   18.671247] NET: Registered protocol family 23
[   18.721710] Synaptics Touchpad, model: 1, fw: 5.9, id: 0x236eb3, caps: 
0x904713/0x10008/0x0
[   18.743763] Detected unconfigured Compaq x1000 family SMSC IrDA chip, 
pre-configuring device.
[   18.743768] Setting up Intel 82801 controller and SMSC device
[   18.743902] found SMC SuperIO Chip (devid=0x5a rev=00 base=0x002e): LPC47N227
[   18.743918] smsc_superio_flat(): fir: 0x2f8, sir: 0x2e8, dma: 03, irq: 7, 
mode: 0x0e
[   18.743935] SMsC IrDA Controller found
[   18.743936]  IrCC version 2.0, firport 0x2f8, sirport 0x2e8 dma=3, irq=7
[   18.744042] No transceiver found. Defaulting to Fast pin select
[   18.760098] lib80211: common routines for IEEE802.11 drivers
[   18.760104] lib80211_crypt: registered algorithm 'NULL'
[   18.761327] IrDA: Registered device irda0
[   18.776289] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio4/input/input6
[   19.073755] yenta_cardbus :02:04.0: CardBus bridge found [0e11:0860]
[   19.073778] yenta_cardbus :02:04.0: Using CSCINT to route CSC interrupts 
to PCI
[   19.073782] yenta_cardbus :02:04.0: Routing CardBus interrupts to PCI
[   19.073788] yenta_cardbus :02:04.0: TI: mfunc 0x001c1112, devctl 0x44
[   19.116501] Bluetooth: Core ver 2.15
[   19.116534] NET: Registered protocol family 31
[   19.116537] Bluetooth: HCI device and connection manager initialized
[   19.116541] Bluetooth: HCI socket layer initialized
[   19.163789] Bluetooth: Generic Bluetooth USB driver ver 0.6
[   19.167829] usbcore: registered new interface driver btusb
[   19.191233] cfg80211: Calling CRDA to update world regulatory domain
[   19.230169] libipw: 802.11 data/management/control stack, git-1.1.13
[   19.230173] libipw: Copyright (C) 2004-2005 Intel Corporation 

[   19.304638] yenta_cardbus :02:04.0: ISA IRQ mask 0x0818, PCI irq 5
[   19.304644] yenta_cardbus :02:04.0: Socket status: 3006
[   19.304650] pci_bus :02: Raising subordinate bus# of parent bus (#02) 
from #03 to #06
[   19.304664] yenta_cardbus :02:04

Re: CONFIG_SCSI_PROC_FS

[Ben Hutchings]

On Thu, 2010-10-07 at 11:16 +1300, Sam Vilain wrote:
> I know this option is labelled as "legacy", but it is still required
> for, eg, scsitools' rescan-scsi-bus.sh script - as far as I know there
> is no other way to force Linux to notice that a device has been plugged
> or a RAID controller configured to make a device accessible.

There is - write to /sys/bus/scsi/devices/host/scsi_host/host/scan
(substituting the SCSI host number for ).  If the 'squeeze' version
of scsitools still makes use of /proc/scsi, please report this as a bug
in that package.

> Can it be enabled in future Debian kernels?

It will not be enabled.

> I'm unfortunately getting to the point where I need to build custom
> kernels; however the old systems I've built are based on kernel-package
> which seems to be deprecated.  Is there a simple piece of documentation
> I can be pointed at for the best way to build customised kernels based
> on Debian's ones?

http://kernel-handbook.alioth.debian.org/

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Processed: tagging 598518

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 598518 + pending
Bug #598518 [linux-2.6] linux-image-2.6-686: ata_piix module loaded before ahci 
module deactivate hotplug support (regression from lenny)
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
598518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598518
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.128641103519701.transcr...@bugs.debian.org

Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds

[brian m. carlson]

On Wed, Oct 06, 2010 at 10:38:48PM +0100, Ben Hutchings wrote:
> Please report this upstream at  under
> product 'DRI', component 'DRM/Intel'.  Let us know the bug number or URL
> so we can track it.

It's my opinion that the maintainers should forward bugs.  I have no
interest in yet another bugzilla account and with several papers that
must be written *now* I simply don't have the time to forward bugs
manually.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds

[Ben Hutchings]

On Thu, 2010-10-07 at 00:37 +, brian m. carlson wrote:
> On Wed, Oct 06, 2010 at 10:38:48PM +0100, Ben Hutchings wrote:
> > Please report this upstream at  under
> > product 'DRI', component 'DRM/Intel'.  Let us know the bug number or URL
> > so we can track it.
> 
> It's my opinion that the maintainers should forward bugs.  I have no
> interest in yet another bugzilla account and with several papers that
> must be written *now* I simply don't have the time to forward bugs
> manually.

I can't reproduce your bug, so I can't answer any further questions that
upstream has for you.  If you don't wish to do that, I will simply close
it and stop wasting your time.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds

[brian m. carlson]

On Thu, Oct 07, 2010 at 01:53:27AM +0100, Ben Hutchings wrote:
> I can't reproduce your bug, so I can't answer any further questions that
> upstream has for you.  If you don't wish to do that, I will simply close
> it and stop wasting your time.

I'm not trying to be rude here.  If you decide you want to forward it,
I'm happy to be on the CC list so the fd.o maintainers can ask me
questions if they need to.  But it's not fair to users to force them to
acquire huge numbers (at least 20 I can think of) of bugzilla accounts
in order to report bugs in Debian.  In general, I only take the time to
forward bugs upstream when there's a specific patch that I really want
to push.  I am, unfortunately, unfamiliar with the DRI infrastructure
and therefore will not be providing a patch in this case.

If you want to close it, fine.  There's nothing I can do to stop you.  I
figured the responsible thing to do was file a bug report instead of
just complaining.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#599368: marked as done (NMI watchdog failed to create perf event on cpu0: ffffffa1)

[Debian Bug Tracking System]

Your message dated Thu, 07 Oct 2010 03:18:52 +0100
with message-id <1286417932.2955.101.ca...@localhost>
and subject line Re: Bug#599368: NMI watchdog failed to create perf event on 
cpu0: ffa1
has caused the Debian Bug report #599368,
regarding NMI watchdog failed to create perf event on cpu0: ffa1
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.)


-- 
599368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.36~rc6-1~experimental.1
Severity: minor
File: /boot/vmlinuz-2.6.36-rc6-686

Hi,

since the upgrade from rc5 to rc6, I get the following error message on
the console during boot:
NMI watchdog failed to create perf event on cpu0: ffa1

With a bit more context:
[0.008303] Performance Events:
[0.008306] no APIC, boot with the "lapic" boot parameter to
force-enable it.
[0.008309] no hardware sampling interrupt available.
[0.008311] p6 PMU driver.
[0.008319] ... version:0
[0.008321] ... bit width:  32
[0.008324] ... generic registers:  2
[0.008326] ... value mask: 
[0.008329] ... max period: 7fff
[0.008331] ... fixed-purpose events:   0
[0.008334] ... event mask: 0003
[0.008815] SMP alternatives: switching to UP code
[0.013737] Freeing SMP alternatives: 16k freed
[0.013743] ACPI: Core revision 20100702
[0.021860] ACPI: setting ELCR to 0200 (from 0c20)
[0.024070] weird, boot CPU (#0) not listed by the BIOS.
[0.024073] SMP motherboard not detected.
[0.024076] Local APIC not detected. Using dummy APIC emulation.
[0.024078] SMP disabled
[0.024189] NMI watchdog failed to create perf event on cpu0:
ffa1
[0.028266] Brought up 1 CPUs
[0.028270] Total of 1 processors activated (3189.83 BogoMIPS).



-- Package-specific info:
** Version:
Linux version 2.6.36-rc6-686 (Debian 2.6.36~rc6-1~experimental.1) 
(b...@decadent.org.uk) (gcc version 4.4.5 20100902 (prerelease) (Debian 
4.4.4-13) ) #1 SMP Mon Oct 4 10:25:13 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.36-rc6-686 
root=UUID=9a6d2bd2-58d1-4a75-baff-166b8637e3cc ro quiet

** Not tainted

** Kernel log:
[4.301432] init[1]: systemd 10 running in system mode. (+PAM +LIBWRAP 
-AUDIT +SELINUX +SYSVINIT; debian)
[4.557097] init[1]: Set hostname to .
[5.749668] init[1]: hostname.service lacks ExecStart setting. Refusing.
[6.010413] init[1]: x11-common.service lacks ExecStart setting. Refusing.
[   17.410690] udev: starting version 161
[   17.773447] input: PC Speaker as /devices/platform/pcspkr/input/input5
[   17.789846] ACPI: AC Adapter [C134] (on-line)
[   17.841354] i801_smbus :00:1f.3: PCI INT B -> Link[C0C3] -> GSI 10 
(level, low) -> IRQ 10
[   17.891393] intel_rng: FWH not detected
[   17.939770] ACPI: acpi_idle registered with cpuidle
[   17.939929] Marking TSC unstable due to TSC halts in idle
[   17.959641] Switching to clocksource acpi_pm
[   18.045347] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   18.118568] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   18.464425] ACPI: Battery Slot [C11F] (battery present)
[   18.512881] parport_pc 00:05: reported by Plug and Play ACPI
[   18.512934] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[   18.671247] NET: Registered protocol family 23
[   18.721710] Synaptics Touchpad, model: 1, fw: 5.9, id: 0x236eb3, caps: 
0x904713/0x10008/0x0
[   18.743763] Detected unconfigured Compaq x1000 family SMSC IrDA chip, 
pre-configuring device.
[   18.743768] Setting up Intel 82801 controller and SMSC device
[   18.743902] found SMC SuperIO Chip (devid=0x5a rev=00 base=0x002e): LPC47N227
[   18.743918] smsc_superio_flat(): fir: 0x2f8, sir: 0x2e8, dma: 03, irq: 7, 
mode: 0x0e
[   18.743935] SMsC IrDA Controller found
[   18.743936]  IrCC version 2.0, firport 0x2f8, sirport 0x2e8 dma=3, irq=7
[   18.744042] No transceiver found. Defaulting to Fast pin select
[   18.760098] lib80211: common routines for IEEE802.11 drivers
[   18.760104] lib80211_crypt: registered algorithm 'NULL'
[   18.761327] IrDA: Registered device irda0
[   18.776289] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio4/input/input6
[   19.073755] yenta_cardbus :02:04.0: CardBus bridge found [0e11:0860]
[   19.073778] yenta_cardbus :02:04.0: Using CSCINT to route CSC interrupts 
to PCI
[   19.073782] yenta_cardbus :02:04.0: Routing CardBus interrupts to PCI
[   19

Processed: Re: Bug#578763: pm-utils: Switches vt despite use of KMS (intel i915)

[Debian Bug Tracking System]

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

> reassign 578763 linux-2.6
Bug #578763 [pm-utils] pm-utils: Switches vt despite use of KMS (intel i915)
Bug reassigned from package 'pm-utils' to 'linux-2.6'.
Bug No longer marked as found in versions pm-utils/1.3.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
578763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578763
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.128641898614957.transcr...@bugs.debian.org

Bug#599368: closed by Ben Hutchings (Re: Bug#599368: NMI watchdog failed to create perf event on cpu0: ffffffa1)

[Michael Biebl]

>> since the upgrade from rc5 to rc6, I get the following error message on
>> > the console during boot:
>> > NMI watchdog failed to create perf event on cpu0: ffa1
> [...]
> 
> This error comes from the new code for hard lockup detection, which
> relies on using a CPU performance counter to trigger an NMI.  The system
> you're using apparently doesn't have a suitable performance counter;
> this is not a bug.

If this just an informative message and not an error, then this message should
not be logged to the console.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: tagging 598503

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 598503 + pending
Bug #598503 [src:linux-2.6] linux-2.6: FTBFS: (powerpc) 
drivers/scsi/qla4xxx/ql4_nx.c:716: error: implicit declaration of function 
'readq'
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
598503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598503
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.128641915515435.transcr...@bugs.debian.org

Bug#599373: Installing kernel changes hard drive hda to sda, etc.

[David Lawyer]

Package: linux-image
Version: 2.6.32-5-486

Installing this updated kernel (my old one was 2.6.30) changed my hard
drive designations in /dev from hdxx to sdxx.  For example hda2 became
sda2.  There was no warning that this was happening.  Now sda2 is
supposed to be a SATA drive and mine are ATA (non-serial) drives.  I
guess they now still work OK but I should have gotten some notice or
explanation of the name change.  Do I need to put the sd notation in
lilo.conf?

The installation recommended that I should use the UUID designation for
harddrives.  I responded OK and now my /etc/fstab table is nearly
impossible to read since the UUID device numbers are so long that they
take up almost an entire line on the screen, so other data on the
line wraps over to the next line.  Can they be replaced with sd.. ?
I manually modify the /etc/fstab table from time to time and need to
keep it simple like it was before it was messed up with long UUIDs.

David Lawyer


-- 
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/20101006235557.ga2...@davespc

Processed: Re: Bug#599373: Installing kernel changes hard drive hda to sda, etc.

[Debian Bug Tracking System]

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

> reassign 599373 linux-2.6
Bug #599373 [linux-image] Installing kernel changes hard drive hda to sda, etc.
Warning: Unknown package 'linux-image'
Bug reassigned from package 'linux-image' to 'linux-2.6'.
Bug No longer marked as found in versions 2.6.32-5-486.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
599373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599373
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.128641947216829.transcr...@bugs.debian.org

Bug#599373: marked as done (Installing kernel changes hard drive hda to sda, etc.)

[Debian Bug Tracking System]

Your message dated Thu, 07 Oct 2010 03:50:09 +0100
with message-id <1286419809.2955.106.ca...@localhost>
and subject line Re: Bug#599373: Installing kernel changes hard drive hda to 
sda, etc.
has caused the Debian Bug report #599373,
regarding Installing kernel changes hard drive hda to sda, etc.
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.)


-- 
599373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image
Version: 2.6.32-5-486

Installing this updated kernel (my old one was 2.6.30) changed my hard
drive designations in /dev from hdxx to sdxx.  For example hda2 became
sda2.  There was no warning that this was happening.  Now sda2 is
supposed to be a SATA drive and mine are ATA (non-serial) drives.  I
guess they now still work OK but I should have gotten some notice or
explanation of the name change.  Do I need to put the sd notation in
lilo.conf?

The installation recommended that I should use the UUID designation for
harddrives.  I responded OK and now my /etc/fstab table is nearly
impossible to read since the UUID device numbers are so long that they
take up almost an entire line on the screen, so other data on the
line wraps over to the next line.  Can they be replaced with sd.. ?
I manually modify the /etc/fstab table from time to time and need to
keep it simple like it was before it was messed up with long UUIDs.

David Lawyer


--- End Message ---
--- Begin Message ---
On Wed, 2010-10-06 at 16:55 -0700, David Lawyer wrote:
> Package: linux-image  
> Version: 2.6.32-5-486
> 
> Installing this updated kernel (my old one was 2.6.30) changed my hard
> drive designations in /dev from hdxx to sdxx.  For example hda2 became
> sda2.  There was no warning that this was happening.
[...]

This is not true.  There is a clear notice during the upgrade that
device names will change.

> The installation recommended that I should use the UUID designation for
> harddrives.  I responded OK and now my /etc/fstab table is nearly
> impossible to read since the UUID device numbers are so long that they
> take up almost an entire line on the screen, so other data on the
> line wraps over to the next line.  Can they be replaced with sd.. ?
[...]

We recommend that you avoid doing that, since these device names can
change if you add a USB storage device, which will also be treated as a
SCSI disk.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#598504: ..yoho, linux-headers-4|686|amd64 whines about "[UNAVAILABLE]" linux-kbuild-2.6.36

[Arnt Karlsen]

On Wed, 29 Sep 2010 15:49:23 +0200, Arnt wrote in message 
<20100929134923.30235.7056.report...@a45.fmb.no>:

> Package: linux-kbuild-2.6.36
> Version: ..yoho, linux-headers-4|686|amd64 whines about
> "[UNAVAILABLE]" linux-kbuild-2.6.36 Severity: normal
> 
> 
> ...yoho, linux-headers

..here I missed the important "2.6.36-rc5" version ID

> -4|686|amd64 whines about "[UNAVAILABLE]"
> linux-kbuild-2.6.36
> 
> -- System Information:
> Debian Release: squeeze/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
> 
> Kernel: Linux 2.6.36-rc5-686 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> 
> 
> 

..close, (as I moved on to 2.6.36-rc6) or move bug to 
linux-kbuild-2.6, there is no linux-kbuild-2.6.36 yet.

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.



-- 
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/20101007061651.71700...@a45.fmb.no

Re: CONFIG_SCSI_PROC_FS

[Sam Vilain]

On Thu, 2010-10-07 at 00:27 +0100, Ben Hutchings wrote:
> > Can it be enabled in future Debian kernels?
> 
> It will not be enabled.

Ben, this comment is poor communication, almost dismissive of my real
integration issues with the Debian kernels.

Why has this option been disabled in the first place?  Does it make
sense that this configuration change has made it to the lenny-backports
kernels?  Some insight into that would be far more useful and social
than your blanket, unjustified decree.

The "legacy" label should be treated with caution; legacy has an
implication - that there are some people who are depending on it to
work.  In this case, people who are using Debian on reasonably high-end
hardware, integrating it into production systems for real customers.
There is a pretty basic requirement here; we plug a disk into the system
and we want the system to pick it up.  Already, we have to install a
package which has a dozen unnecessary dependencies for this one shell
script.

Please, spare a thought for users before turning off legacy
compatibility options in the kernel.  Systems need to work; legacy
options need deprecation cycles and testing before they can just be
removed, for the good of the Debian project as a whole.

Anyway, thank-you for your other comments, they were helpful and I will
log a bug against that package, and at least now I know where I need to
start reading about how to build a custom kernel.

Sam


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